[Geoserver-devel] ArcSDE raster URL syntax

[Bob_Nutsch]

Hi,

I'm trying to access raster data from ArcSDE 9.2 (with has a backend of
Oracle 10g). I select 'ArcSDE Raster Format' from the list when starting to
set up a new coverage store. I supply a Coverage Data Set ID and then
click on the New button.

I must be doing something wrong for the URL syntax because after entering
the URL information and clicking on the Submit button I get the following on
the left side of the GeoServer admin page:

"Invalid url:
'sde://myuser:mypwd@anonymised.com:5198/#NDHUB.NGS_DRG24K;LZERO_ORIGIN_TILE=0,0'
for format type:'ArcSDE Raster'.

I've looked at the example shown on
http://docs.codehaus.org/display/GEOTDOC/ArcSDE+DataStore. I'm too dumb to
figure out what I'm missing.

Here's my information:

User: myuser
Pwd: mypwd
Server: myserver.state.nd.us
ArcSDE instance: 5198
raster layer: NDHUB.NGS_DRG24K (where 'NDHUB' is the schema owner)

There's something wrong with the syntax around the '#' area I think. It's
been my experience that when using ArcSDE with Oracle, there is not a
database or instance name, simply the server and port number (along with the
userid and password). For SQL Server, I would enter the name of the
database but there is no database name for Oracle. So when using ESRI tools
I generally leave the database name blank or enter a "#" for that field.
I'm thinking that perhaps this is the issue with the URL that I'm using, but
I'm not sure.

Any thoughts would be greatly appreciated!

Thanks, Bob

--
View this message in context: http://www.nabble.com/ArcSDE-raster-URL-syntax-tf4635131.html#a13236680
Sent from the GeoServer - Dev mailing list archive at Nabble.com.

[Farber_Saul_EEA]

Bob,

What happens if you add in the instance name, just to make the sde parser
happy? I think that what you've written *should* work, but if the sde url
parser isn't taking it, maybe just try something in that slot that's
sensible (like the DB name or instance name?)

Let me know if that gets you any further, and if it doesn't then i'll try
and dig a little deeper into that code to figure out what's up.

--saul

Bob Nutsch wrote:

Hi,

I'm trying to access raster data from ArcSDE 9.2 (with has a backend of
Oracle 10g). I select 'ArcSDE Raster Format' from the list when starting
to set up a new coverage store. I supply a Coverage Data Set ID and then
click on the New button.

I must be doing something wrong for the URL syntax because after entering
the URL information and clicking on the Submit button I get the following
on the left side of the GeoServer admin page:

"Invalid url:
'sde://myuser:mypwd@anonymised.com:5198/#NDHUB.NGS_DRG24K;LZERO_ORIGIN_TILE=0,0'
for format type:'ArcSDE Raster'.

I've looked at the example shown on
http://docs.codehaus.org/display/GEOTDOC/ArcSDE+DataStore. I'm too dumb
to figure out what I'm missing.

Here's my information:

User: myuser
Pwd: mypwd
Server: myserver.state.nd.us
ArcSDE instance: 5198
raster layer: NDHUB.NGS_DRG24K (where 'NDHUB' is the schema owner)

There's something wrong with the syntax around the '#' area I think. It's
been my experience that when using ArcSDE with Oracle, there is not a
database or instance name, simply the server and port number (along with
the userid and password). For SQL Server, I would enter the name of the
database but there is no database name for Oracle. So when using ESRI
tools I generally leave the database name blank or enter a "#" for that
field. I'm thinking that perhaps this is the issue with the URL that I'm
using, but I'm not sure.

Any thoughts would be greatly appreciated!

Thanks, Bob

--
View this message in context: http://www.nabble.com/ArcSDE-raster-URL-syntax-tf4635131.html#a13239369
Sent from the GeoServer - Dev mailing list archive at Nabble.com.

[Bob_Nutsch]

Hi Saul,

I've tried several combinations including those that you suggest. But I
just now tried again to be sure. Here's the latest:

sde://myuserid:mypwd@anonymised.com:5198/GISEDIT#NDHUB.NGS_DRG24K

where GISEDIT is the name of the instance.

Thanks, Bob

sfarber wrote:

Bob,

What happens if you add in the instance name, just to make the sde parser
happy? I think that what you've written *should* work, but if the sde url
parser isn't taking it, maybe just try something in that slot that's
sensible (like the DB name or instance name?)

Let me know if that gets you any further, and if it doesn't then i'll try
and dig a little deeper into that code to figure out what's up.

--saul

Bob Nutsch wrote:

Hi,

I'm trying to access raster data from ArcSDE 9.2 (with has a backend of
Oracle 10g). I select 'ArcSDE Raster Format' from the list when starting
to set up a new coverage store. I supply a Coverage Data Set ID and
then click on the New button.

I must be doing something wrong for the URL syntax because after entering
the URL information and clicking on the Submit button I get the following
on the left side of the GeoServer admin page:

"Invalid url:
'sde://myuser:mypwd@anonymised.com:5198/#NDHUB.NGS_DRG24K;LZERO_ORIGIN_TILE=0,0'
for format type:'ArcSDE Raster'.

I've looked at the example shown on
http://docs.codehaus.org/display/GEOTDOC/ArcSDE+DataStore. I'm too dumb
to figure out what I'm missing.

Here's my information:

User: myuser
Pwd: mypwd
Server: myserver.state.nd.us
ArcSDE instance: 5198
raster layer: NDHUB.NGS_DRG24K (where 'NDHUB' is the schema owner)

There's something wrong with the syntax around the '#' area I think.
It's been my experience that when using ArcSDE with Oracle, there is not
a database or instance name, simply the server and port number (along
with the userid and password). For SQL Server, I would enter the name of
the database but there is no database name for Oracle. So when using
ESRI tools I generally leave the database name blank or enter a "#" for
that field. I'm thinking that perhaps this is the issue with the URL
that I'm using, but I'm not sure.

Any thoughts would be greatly appreciated!

Thanks, Bob

--
View this message in context: http://www.nabble.com/ArcSDE-raster-URL-syntax-tf4635131.html#a13239564
Sent from the GeoServer - Dev mailing list archive at Nabble.com.

[Farber_Saul_EEA]

Bob,

I've tried to replicate your failure by parsing the SDE url, and it seems to
parse ok in my tests. Can you send an email to the list with the stack
trace of the error? You'll have to look in your geoserver logfiles to see
it. If I can see that then I'll have more info to figure out what's going
wrong and where.

--saul

Bob Nutsch wrote:

Hi Saul,

I've tried several combinations including those that you suggest. But I
just now tried again to be sure. Here's the latest:

sde://myuserid:mypwd@anonymised.com:5198/GISEDIT#NDHUB.NGS_DRG24K

where GISEDIT is the name of the instance.

Thanks, Bob

--
View this message in context: http://www.nabble.com/ArcSDE-raster-URL-syntax-tf4635131.html#a13261014
Sent from the GeoServer - Dev mailing list archive at Nabble.com.

[Bob_Nutsch]

Hi Saul,

I seem to have a problem getting the logging to be switched on. In
Config->Server I place the check marks into 'Verbose' and
'VerboseExceptions' and then click apply and save but when I come back those
check marks are missing. I also noticed that:

Logging Profile
Suppress StdOut logging
Log Location

are grayed out and I can't click them.

The log file in C:\Program Files\GeoServer 1.6-beta3\webapps\geoserver\logs
is empty and the C:\Program Files\GeoServer
1.6-beta3\logs\2007_10_17.request.log contains only info such as:

127.0.0.1 - - [17/10/2007:20:56:49 +0000] "GET /geoserver/images/gs.ico
HTTP/1.1" 404 1400

no errors.

There must be a place where I can switch on full verbose logging someplace?

Thanks, Bob

sfarber wrote:

Bob,

I've tried to replicate your failure by parsing the SDE url, and it seems
to parse ok in my tests. Can you send an email to the list with the stack
trace of the error? You'll have to look in your geoserver logfiles to see
it. If I can see that then I'll have more info to figure out what's going
wrong and where.

--saul

Bob Nutsch wrote:

Hi Saul,

I've tried several combinations including those that you suggest. But I
just now tried again to be sure. Here's the latest:

sde://myuserid:mypwd@anonymised.com:5198/GISEDIT#NDHUB.NGS_DRG24K

where GISEDIT is the name of the instance.

Thanks, Bob

--
View this message in context: http://www.nabble.com/ArcSDE-raster-URL-syntax-tf4635131.html#a13262725
Sent from the GeoServer - Dev mailing list archive at Nabble.com.

[Farber_Saul_EEA]

Bob,

Can you check that there's a file called 'commons-logging.properties' in the
WEB-INF/classes directory? If not, can you add one? It's a one-line text
file with the following contents:

org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger

--saul

Bob Nutsch wrote:

Logging Profile
Suppress StdOut logging
Log Location

are grayed out and I can't click them.

--
View this message in context: http://www.nabble.com/ArcSDE-raster-URL-syntax-tf4635131.html#a13262782
Sent from the GeoServer - Dev mailing list archive at Nabble.com.

[Bob_Nutsch]

Hi,

I was just looking at that. I noted in the console (after sending the last
email) that there was this message:

139255 [btpool0-6] WARN org.vfny.geoserver.global - Error figuring out
GeoServer logging configuration: java.io.FileNotFoundException:
C:\Program%20Files\GeoServer%201.6-beta3\webapps\geoserver\WEB-INF\classes\commons-logging.properties
(The system cannot find the path specified)

So I went looking and found that file:

C:\Program Files\GeoServer
1.6-beta3\webapps\geoserver\WEB-INF\classes\commons-logging.properties

which has the contents of:

org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger

Does this imply that I need to have something set up in Apache? There are
no current logs in Apache's log directory.

I did discover a user problem on my end, that I had failed to click the
Submit button after clicking the Verbose options in the Server Configuration
page. Those are now in place, sorry. But the other logging options are
still grayed out and there is still no content in the log files.

Thanks, Bob

sfarber wrote:

Bob,

Can you check that there's a file called 'commons-logging.properties' in
the WEB-INF/classes directory? If not, can you add one? It's a one-line
text file with the following contents:

org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger

--saul

Bob Nutsch wrote:

Logging Profile
Suppress StdOut logging
Log Location

are grayed out and I can't click them.

--
View this message in context: http://www.nabble.com/ArcSDE-raster-URL-syntax-tf4635131.html#a13262808
Sent from the GeoServer - Dev mailing list archive at Nabble.com.

[Farber_Saul_EEA]

Hmm. I've got an idea.

Can you run geoserver from a path with NO spaces in it?

Something like this:

c:\geoserver-1.6-beta3\...

Then see if that same error message comes up.

--saul

Bob Nutsch wrote:

Hi,

I was just looking at that. I noted in the console (after sending the
last email) that there was this message:

139255 [btpool0-6] WARN org.vfny.geoserver.global - Error figuring out
GeoServer logging configuration: java.io.FileNotFoundException:
C:\Program%20Files\GeoServer%201.6-beta3\webapps\geoserver\WEB-INF\classes\commons-logging.properties
(The system cannot find the path specified)

So I went looking and found that file:

C:\Program Files\GeoServer
1.6-beta3\webapps\geoserver\WEB-INF\classes\commons-logging.properties

which has the contents of:

org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger

Does this imply that I need to have something set up in Apache? There are
no current logs in Apache's log directory.

I did discover a user problem on my end, that I had failed to click the
Submit button after clicking the Verbose options in the Server
Configuration page. Those are now in place, sorry. But the other logging
options are still grayed out and there is still no content in the log
files.

Thanks, Bob

sfarber wrote:

Bob,

Can you check that there's a file called 'commons-logging.properties' in
the WEB-INF/classes directory? If not, can you add one? It's a one-line
text file with the following contents:

org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger

--saul

Bob Nutsch wrote:

Logging Profile
Suppress StdOut logging
Log Location

are grayed out and I can't click them.

--
View this message in context: http://www.nabble.com/ArcSDE-raster-URL-syntax-tf4635131.html#a13262988
Sent from the GeoServer - Dev mailing list archive at Nabble.com.

[Bob_Nutsch]

Ah blast it anyway! Kicked in the teeth by that issue, argh!

I made the change and now the logging options are not grayed out! Still
having the same issue with the raster URL not being accepted. Which is the
correct logging option to select from the Logging Profile list? I'm still
not getting any output to
"C:\GeoServer1.6-beta3\webapps\geoserver\logs\geoserver.log"

Thanks, Bob

sfarber wrote:

Hmm. I've got an idea.

Can you run geoserver from a path with NO spaces in it?

Something like this:

c:\geoserver-1.6-beta3\...

Then see if that same error message comes up.

--saul

Bob Nutsch wrote:

Hi,

I was just looking at that. I noted in the console (after sending the
last email) that there was this message:

139255 [btpool0-6] WARN org.vfny.geoserver.global - Error figuring out
GeoServer logging configuration: java.io.FileNotFoundException:
C:\Program%20Files\GeoServer%201.6-beta3\webapps\geoserver\WEB-INF\classes\commons-logging.properties
(The system cannot find the path specified)

So I went looking and found that file:

C:\Program Files\GeoServer
1.6-beta3\webapps\geoserver\WEB-INF\classes\commons-logging.properties

which has the contents of:

org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger

Does this imply that I need to have something set up in Apache? There
are no current logs in Apache's log directory.

I did discover a user problem on my end, that I had failed to click the
Submit button after clicking the Verbose options in the Server
Configuration page. Those are now in place, sorry. But the other
logging options are still grayed out and there is still no content in the
log files.

Thanks, Bob

sfarber wrote:

Bob,

Can you check that there's a file called 'commons-logging.properties' in
the WEB-INF/classes directory? If not, can you add one? It's a
one-line text file with the following contents:

org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger

--saul

Bob Nutsch wrote:

Logging Profile
Suppress StdOut logging
Log Location

are grayed out and I can't click them.

--
View this message in context: http://www.nabble.com/ArcSDE-raster-URL-syntax-tf4635131.html#a13263165
Sent from the GeoServer - Dev mailing list archive at Nabble.com.

[Farber_Saul_EEA]

Hmm. That's strange that you're not getting any output at all to
geoserver.log

Is that the file set up as the 'logfile name' in your configuration?

As for logging configs, I'd choose 'geotools_development' or else 'verbose'
or whatever. Both should give you a decent stacktrace for the failure to
connect to ArcSDE.

--saul

Bob Nutsch wrote:

Ah blast it anyway! Kicked in the teeth by that issue, argh!

I made the change and now the logging options are not grayed out! Still
having the same issue with the raster URL not being accepted. Which is
the correct logging option to select from the Logging Profile list? I'm
still not getting any output to
"C:\GeoServer1.6-beta3\webapps\geoserver\logs\geoserver.log"

Thanks, Bob

sfarber wrote:

Hmm. I've got an idea.

Can you run geoserver from a path with NO spaces in it?

Something like this:

c:\geoserver-1.6-beta3\...

Then see if that same error message comes up.

--saul

Bob Nutsch wrote:

Hi,

I was just looking at that. I noted in the console (after sending the
last email) that there was this message:

139255 [btpool0-6] WARN org.vfny.geoserver.global - Error figuring out
GeoServer logging configuration: java.io.FileNotFoundException:
C:\Program%20Files\GeoServer%201.6-beta3\webapps\geoserver\WEB-INF\classes\commons-logging.properties
(The system cannot find the path specified)

So I went looking and found that file:

C:\Program Files\GeoServer
1.6-beta3\webapps\geoserver\WEB-INF\classes\commons-logging.properties

which has the contents of:

org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger

Does this imply that I need to have something set up in Apache? There
are no current logs in Apache's log directory.

I did discover a user problem on my end, that I had failed to click the
Submit button after clicking the Verbose options in the Server
Configuration page. Those are now in place, sorry. But the other
logging options are still grayed out and there is still no content in
the log files.

Thanks, Bob

sfarber wrote:

Bob,

Can you check that there's a file called 'commons-logging.properties'
in the WEB-INF/classes directory? If not, can you add one? It's a
one-line text file with the following contents:

org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger

--saul

Bob Nutsch wrote:

Logging Profile
Suppress StdOut logging
Log Location

are grayed out and I can't click them.

--
View this message in context: http://www.nabble.com/ArcSDE-raster-URL-syntax-tf4635131.html#a13263166
Sent from the GeoServer - Dev mailing list archive at Nabble.com.

[Andrea_Aime3]

sfarber ha scritto:

Hmm. I've got an idea.

Can you run geoserver from a path with NO spaces in it?

Something like this:

c:\geoserver-1.6-beta3\...

This looks like a bug to me... we should investigate and figure
out what part of GeoServer is no happy with the spaces...
Cheers
Andrea

[Bob_Nutsch]

Hi Saul,

Still having a problem getting info written to the log file. In the Server
Configuration window, I've used
GEOSERVER_DEVELOPER_LOGGING
VERBOSE_LOGGING
GEOTOOLS_DEVELOPER_LOGGING

and have the log location set to

C:\GeoServer1.6-beta3\webapps\geoserver\logs\geoserver.log

and have tried \logs\geoserver.log

With GEOSERVER_DEVELOPER_LOGGING set and saved, and when re-starting
GeoServer, in the console I see:

log4j:WARN File option not set for appender [geoserverlogfile].
log4j:WARN Are you using FileAppender instead of ConsoleAppender?10282
[main] INFO org.vfny.geoserver.global - StdOut logging enabled. Log file
also output to 'C:\GeoServer1.6-beta3\webapps\geoserver\logs\geoserver.log'

Is there an environment variable that needs to be set and/or a config file
that I should manually tweak to enable logging?

Thanks, Bob

sfarber wrote:

Hmm. That's strange that you're not getting any output at all to
geoserver.log

Is that the file set up as the 'logfile name' in your configuration?

As for logging configs, I'd choose 'geotools_development' or else
'verbose' or whatever. Both should give you a decent stacktrace for the
failure to connect to ArcSDE.

--saul

Bob Nutsch wrote:

Ah blast it anyway! Kicked in the teeth by that issue, argh!

I made the change and now the logging options are not grayed out! Still
having the same issue with the raster URL not being accepted. Which is
the correct logging option to select from the Logging Profile list? I'm
still not getting any output to
"C:\GeoServer1.6-beta3\webapps\geoserver\logs\geoserver.log"

Thanks, Bob

sfarber wrote:

Hmm. I've got an idea.

Can you run geoserver from a path with NO spaces in it?

Something like this:

c:\geoserver-1.6-beta3\...

Then see if that same error message comes up.

--saul

Bob Nutsch wrote:

Hi,

I was just looking at that. I noted in the console (after sending the
last email) that there was this message:

139255 [btpool0-6] WARN org.vfny.geoserver.global - Error figuring out
GeoServer logging configuration: java.io.FileNotFoundException:
C:\Program%20Files\GeoServer%201.6-beta3\webapps\geoserver\WEB-INF\classes\commons-logging.properties
(The system cannot find the path specified)

So I went looking and found that file:

C:\Program Files\GeoServer
1.6-beta3\webapps\geoserver\WEB-INF\classes\commons-logging.properties

which has the contents of:

org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger

Does this imply that I need to have something set up in Apache? There
are no current logs in Apache's log directory.

I did discover a user problem on my end, that I had failed to click the
Submit button after clicking the Verbose options in the Server
Configuration page. Those are now in place, sorry. But the other
logging options are still grayed out and there is still no content in
the log files.

Thanks, Bob

sfarber wrote:

Bob,

Can you check that there's a file called 'commons-logging.properties'
in the WEB-INF/classes directory? If not, can you add one? It's a
one-line text file with the following contents:

org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger

--saul

Bob Nutsch wrote:

Logging Profile
Suppress StdOut logging
Log Location

are grayed out and I can't click them.

--
View this message in context: http://www.nabble.com/ArcSDE-raster-URL-syntax-tf4635131.html#a13277458
Sent from the GeoServer - Dev mailing list archive at Nabble.com.

[Farber_Saul_EEA]

Bob,

The lines you're showing are actually just a side-effect message that can be
ignored. Basically, when starting up the logging, geoserver has it start up
without setting a logfile first and then injects the right logfile right
after longing is enabled. This works, but causes that error you see (so
that error can be ignored).

After the startup, do you see anything in that logfile
(c:\..\geoserver.log)? Or is that logfile empty?

How about the console? Do you have 'suppress stdout logging' UN-checked?

--saul

Bob Nutsch wrote:

Hi Saul,

Still having a problem getting info written to the log file. In the
Server Configuration window, I've used
GEOSERVER_DEVELOPER_LOGGING
VERBOSE_LOGGING
GEOTOOLS_DEVELOPER_LOGGING

and have the log location set to

C:\GeoServer1.6-beta3\webapps\geoserver\logs\geoserver.log

and have tried \logs\geoserver.log

With GEOSERVER_DEVELOPER_LOGGING set and saved, and when re-starting
GeoServer, in the console I see:

log4j:WARN File option not set for appender [geoserverlogfile].
log4j:WARN Are you using FileAppender instead of ConsoleAppender?10282
[main] INFO org.vfny.geoserver.global - StdOut logging enabled. Log file
also output to
'C:\GeoServer1.6-beta3\webapps\geoserver\logs\geoserver.log'

Is there an environment variable that needs to be set and/or a config file
that I should manually tweak to enable logging?

Thanks, Bob

sfarber wrote:

Hmm. That's strange that you're not getting any output at all to
geoserver.log

Is that the file set up as the 'logfile name' in your configuration?

As for logging configs, I'd choose 'geotools_development' or else
'verbose' or whatever. Both should give you a decent stacktrace for the
failure to connect to ArcSDE.

--saul

Bob Nutsch wrote:

Ah blast it anyway! Kicked in the teeth by that issue, argh!

I made the change and now the logging options are not grayed out! Still
having the same issue with the raster URL not being accepted. Which is
the correct logging option to select from the Logging Profile list? I'm
still not getting any output to
"C:\GeoServer1.6-beta3\webapps\geoserver\logs\geoserver.log"

Thanks, Bob

sfarber wrote:

Hmm. I've got an idea.

Can you run geoserver from a path with NO spaces in it?

Something like this:

c:\geoserver-1.6-beta3\...

Then see if that same error message comes up.

--saul

Bob Nutsch wrote:

Hi,

I was just looking at that. I noted in the console (after sending the
last email) that there was this message:

139255 [btpool0-6] WARN org.vfny.geoserver.global - Error figuring out
GeoServer logging configuration: java.io.FileNotFoundException:
C:\Program%20Files\GeoServer%201.6-beta3\webapps\geoserver\WEB-INF\classes\commons-logging.properties
(The system cannot find the path specified)

So I went looking and found that file:

C:\Program Files\GeoServer
1.6-beta3\webapps\geoserver\WEB-INF\classes\commons-logging.properties

which has the contents of:

org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger

Does this imply that I need to have something set up in Apache? There
are no current logs in Apache's log directory.

I did discover a user problem on my end, that I had failed to click
the Submit button after clicking the Verbose options in the Server
Configuration page. Those are now in place, sorry. But the other
logging options are still grayed out and there is still no content in
the log files.

Thanks, Bob

sfarber wrote:

Bob,

Can you check that there's a file called 'commons-logging.properties'
in the WEB-INF/classes directory? If not, can you add one? It's a
one-line text file with the following contents:

org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger

--saul

Bob Nutsch wrote:

Logging Profile
Suppress StdOut logging
Log Location

are grayed out and I can't click them.

--
View this message in context: http://www.nabble.com/ArcSDE-raster-URL-syntax-tf4635131.html#a13277466
Sent from the GeoServer - Dev mailing list archive at Nabble.com.

[Bob_Nutsch]

Hi,

Thanks for the info. The logfile still remains empty, nothing in there.
The date/time stamp remains at the original install date, it hasn't been
touched.

Nothing in the console other than what I've cut and pasted below. The
'suppress stdout logging' UN-checked is unchecked.

I went and looked at C:\GeoServer1.6-beta3\data_dir\services.xml. I think
everything looks OK, the first few lines look like this:

<?config.xml version="1.0" encoding="UTF-8"?>
<!--
  Service level configuration
-->
<serverConfiguration >
  <global >
   
<log4jConfigFile>GEOSERVER_DEVELOPER_LOGGING.properties</log4jConfigFile>
    <suppressStdOutLogging value = "false" />
   
<logLocation>C:\GeoServer1.6-beta3\webapps\geoserver\logs\geoserver.log</logLocation>
    <JaiMemoryCapacity value = "0.5" />
    <JaiMemoryThreshold value = "0.75" />
    <JaiTileThreads value = "7" />
    <JaiTilePriority value = "5" />
    <JaiRecycling value = "true" />
    <ImageIOCache value = "false" />
    <JaiJPEGNative value = "true" />
    <JaiPNGNative value = "true" />

Thanks, Bob

sfarber wrote:

Bob,

The lines you're showing are actually just a side-effect message that can
be ignored. Basically, when starting up the logging, geoserver has it
start up without setting a logfile first and then injects the right
logfile right after longing is enabled. This works, but causes that error
you see (so that error can be ignored).

After the startup, do you see anything in that logfile
(c:\..\geoserver.log)? Or is that logfile empty?

How about the console? Do you have 'suppress stdout logging' UN-checked?

--saul

Bob Nutsch wrote:

Hi Saul,

Still having a problem getting info written to the log file. In the
Server Configuration window, I've used
GEOSERVER_DEVELOPER_LOGGING
VERBOSE_LOGGING
GEOTOOLS_DEVELOPER_LOGGING

and have the log location set to

C:\GeoServer1.6-beta3\webapps\geoserver\logs\geoserver.log

and have tried \logs\geoserver.log

With GEOSERVER_DEVELOPER_LOGGING set and saved, and when re-starting
GeoServer, in the console I see:

log4j:WARN File option not set for appender [geoserverlogfile].
log4j:WARN Are you using FileAppender instead of ConsoleAppender?10282
[main] INFO org.vfny.geoserver.global - StdOut logging enabled. Log file
also output to
'C:\GeoServer1.6-beta3\webapps\geoserver\logs\geoserver.log'

Is there an environment variable that needs to be set and/or a config
file that I should manually tweak to enable logging?

Thanks, Bob

sfarber wrote:

Hmm. That's strange that you're not getting any output at all to
geoserver.log

Is that the file set up as the 'logfile name' in your configuration?

As for logging configs, I'd choose 'geotools_development' or else
'verbose' or whatever. Both should give you a decent stacktrace for the
failure to connect to ArcSDE.

--saul

Bob Nutsch wrote:

Ah blast it anyway! Kicked in the teeth by that issue, argh!

I made the change and now the logging options are not grayed out!
Still having the same issue with the raster URL not being accepted.
Which is the correct logging option to select from the Logging Profile
list? I'm still not getting any output to
"C:\GeoServer1.6-beta3\webapps\geoserver\logs\geoserver.log"

Thanks, Bob

sfarber wrote:

Hmm. I've got an idea.

Can you run geoserver from a path with NO spaces in it?

Something like this:

c:\geoserver-1.6-beta3\...

Then see if that same error message comes up.

--saul

Bob Nutsch wrote:

Hi,

I was just looking at that. I noted in the console (after sending
the last email) that there was this message:

139255 [btpool0-6] WARN org.vfny.geoserver.global - Error figuring
out GeoServer logging configuration: java.io.FileNotFoundException:
C:\Program%20Files\GeoServer%201.6-beta3\webapps\geoserver\WEB-INF\classes\commons-logging.properties
(The system cannot find the path specified)

So I went looking and found that file:

C:\Program Files\GeoServer
1.6-beta3\webapps\geoserver\WEB-INF\classes\commons-logging.properties

which has the contents of:

org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger

Does this imply that I need to have something set up in Apache?
There are no current logs in Apache's log directory.

I did discover a user problem on my end, that I had failed to click
the Submit button after clicking the Verbose options in the Server
Configuration page. Those are now in place, sorry. But the other
logging options are still grayed out and there is still no content in
the log files.

Thanks, Bob

sfarber wrote:

Bob,

Can you check that there's a file called
'commons-logging.properties' in the WEB-INF/classes directory? If
not, can you add one? It's a one-line text file with the following
contents:

org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger

--saul

Bob Nutsch wrote:

Logging Profile
Suppress StdOut logging
Log Location

are grayed out and I can't click them.

--
View this message in context: http://www.nabble.com/ArcSDE-raster-URL-syntax-tf4635131.html#a13278159
Sent from the GeoServer - Dev mailing list archive at Nabble.com.

[Farber_Saul_EEA]

Bob,

That's really weird that the logfile is still empty. Can you go to
http://rafb.net/paste/ and paste in the entire contents of the console?

Then send us the links to those pages, and I'll try and see what's going on.

You might try doing some activity on geoserver to really generate events.
Open up a map, zoom around, etc.

Also try to have the URL fail to load and see if anything shows up when you
do that.

--saul

Bob Nutsch wrote:

Hi,

Thanks for the info. The logfile still remains empty, nothing in there.
The date/time stamp remains at the original install date, it hasn't been
touched.

Nothing in the console other than what I've cut and pasted below. The
'suppress stdout logging' UN-checked is unchecked.

I went and looked at C:\GeoServer1.6-beta3\data_dir\services.xml. I think
everything looks OK, the first few lines look like this:

<?config.xml version="1.0" encoding="UTF-8"?>
<!--
  Service level configuration
-->
<serverConfiguration >
  <global >
   
<log4jConfigFile>GEOSERVER_DEVELOPER_LOGGING.properties</log4jConfigFile>
    <suppressStdOutLogging value = "false" />
   
<logLocation>C:\GeoServer1.6-beta3\webapps\geoserver\logs\geoserver.log</logLocation>
    <JaiMemoryCapacity value = "0.5" />
    <JaiMemoryThreshold value = "0.75" />
    <JaiTileThreads value = "7" />
    <JaiTilePriority value = "5" />
    <JaiRecycling value = "true" />
    <ImageIOCache value = "false" />
    <JaiJPEGNative value = "true" />
    <JaiPNGNative value = "true" />

Thanks, Bob

sfarber wrote:

Bob,

The lines you're showing are actually just a side-effect message that can
be ignored. Basically, when starting up the logging, geoserver has it
start up without setting a logfile first and then injects the right
logfile right after longing is enabled. This works, but causes that
error you see (so that error can be ignored).

After the startup, do you see anything in that logfile
(c:\..\geoserver.log)? Or is that logfile empty?

How about the console? Do you have 'suppress stdout logging' UN-checked?

--saul

Bob Nutsch wrote:

Hi Saul,

Still having a problem getting info written to the log file. In the
Server Configuration window, I've used
GEOSERVER_DEVELOPER_LOGGING
VERBOSE_LOGGING
GEOTOOLS_DEVELOPER_LOGGING

and have the log location set to

C:\GeoServer1.6-beta3\webapps\geoserver\logs\geoserver.log

and have tried \logs\geoserver.log

With GEOSERVER_DEVELOPER_LOGGING set and saved, and when re-starting
GeoServer, in the console I see:

log4j:WARN File option not set for appender [geoserverlogfile].
log4j:WARN Are you using FileAppender instead of ConsoleAppender?10282
[main] INFO org.vfny.geoserver.global - StdOut logging enabled. Log
file also output to
'C:\GeoServer1.6-beta3\webapps\geoserver\logs\geoserver.log'

Is there an environment variable that needs to be set and/or a config
file that I should manually tweak to enable logging?

Thanks, Bob

sfarber wrote:

Hmm. That's strange that you're not getting any output at all to
geoserver.log

Is that the file set up as the 'logfile name' in your configuration?

As for logging configs, I'd choose 'geotools_development' or else
'verbose' or whatever. Both should give you a decent stacktrace for
the failure to connect to ArcSDE.

--saul

Bob Nutsch wrote:

Ah blast it anyway! Kicked in the teeth by that issue, argh!

I made the change and now the logging options are not grayed out!
Still having the same issue with the raster URL not being accepted.
Which is the correct logging option to select from the Logging Profile
list? I'm still not getting any output to
"C:\GeoServer1.6-beta3\webapps\geoserver\logs\geoserver.log"

Thanks, Bob

sfarber wrote:

Hmm. I've got an idea.

Can you run geoserver from a path with NO spaces in it?

Something like this:

c:\geoserver-1.6-beta3\...

Then see if that same error message comes up.

--saul

Bob Nutsch wrote:

Hi,

I was just looking at that. I noted in the console (after sending
the last email) that there was this message:

139255 [btpool0-6] WARN org.vfny.geoserver.global - Error figuring
out GeoServer logging configuration: java.io.FileNotFoundException:
C:\Program%20Files\GeoServer%201.6-beta3\webapps\geoserver\WEB-INF\classes\commons-logging.properties
(The system cannot find the path specified)

So I went looking and found that file:

C:\Program Files\GeoServer
1.6-beta3\webapps\geoserver\WEB-INF\classes\commons-logging.properties

which has the contents of:

org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger

Does this imply that I need to have something set up in Apache?
There are no current logs in Apache's log directory.

I did discover a user problem on my end, that I had failed to click
the Submit button after clicking the Verbose options in the Server
Configuration page. Those are now in place, sorry. But the other
logging options are still grayed out and there is still no content
in the log files.

Thanks, Bob

sfarber wrote:

Bob,

Can you check that there's a file called
'commons-logging.properties' in the WEB-INF/classes directory? If
not, can you add one? It's a one-line text file with the following
contents:

org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger

--saul

Bob Nutsch wrote:

Logging Profile
Suppress StdOut logging
Log Location

are grayed out and I can't click them.

--
View this message in context: http://www.nabble.com/ArcSDE-raster-URL-syntax-tf4635131.html#a13278844
Sent from the GeoServer - Dev mailing list archive at Nabble.com.

[Bob_Nutsch]

Hi,

Nifty tool! Here's the console just after starting GeoServer, nothing done
after the start: http://rafb.net/p/ArVftd54.html

Here's the console after logging in and then trying to use the ArcSDE URL:
http://rafb.net/p/ecC4FY39.html

I see those same two lines again:

log4j:WARN File option not set for appender [geoserverlogfile].
log4j:WARN Are you using FileAppender instead of ConsoleAppender?

These are not to be worried about?

Thanks, Bob

sfarber wrote:

Bob,

That's really weird that the logfile is still empty. Can you go to
http://rafb.net/paste/ and paste in the entire contents of the console?

Then send us the links to those pages, and I'll try and see what's going
on.

You might try doing some activity on geoserver to really generate events.
Open up a map, zoom around, etc.

Also try to have the URL fail to load and see if anything shows up when
you do that.

--saul

Bob Nutsch wrote:

Hi,

Thanks for the info. The logfile still remains empty, nothing in there.
The date/time stamp remains at the original install date, it hasn't been
touched.

Nothing in the console other than what I've cut and pasted below. The
'suppress stdout logging' UN-checked is unchecked.

I went and looked at C:\GeoServer1.6-beta3\data_dir\services.xml. I
think everything looks OK, the first few lines look like this:

<?config.xml version="1.0" encoding="UTF-8"?>
<!--
  Service level configuration
-->
<serverConfiguration >
  <global >
   
<log4jConfigFile>GEOSERVER_DEVELOPER_LOGGING.properties</log4jConfigFile>
    <suppressStdOutLogging value = "false" />
   
<logLocation>C:\GeoServer1.6-beta3\webapps\geoserver\logs\geoserver.log</logLocation>
    <JaiMemoryCapacity value = "0.5" />
    <JaiMemoryThreshold value = "0.75" />
    <JaiTileThreads value = "7" />
    <JaiTilePriority value = "5" />
    <JaiRecycling value = "true" />
    <ImageIOCache value = "false" />
    <JaiJPEGNative value = "true" />
    <JaiPNGNative value = "true" />

Thanks, Bob

sfarber wrote:

Bob,

The lines you're showing are actually just a side-effect message that
can be ignored. Basically, when starting up the logging, geoserver has
it start up without setting a logfile first and then injects the right
logfile right after longing is enabled. This works, but causes that
error you see (so that error can be ignored).

After the startup, do you see anything in that logfile
(c:\..\geoserver.log)? Or is that logfile empty?

How about the console? Do you have 'suppress stdout logging'
UN-checked?

--saul

Bob Nutsch wrote:

Hi Saul,

Still having a problem getting info written to the log file. In the
Server Configuration window, I've used
GEOSERVER_DEVELOPER_LOGGING
VERBOSE_LOGGING
GEOTOOLS_DEVELOPER_LOGGING

and have the log location set to

C:\GeoServer1.6-beta3\webapps\geoserver\logs\geoserver.log

and have tried \logs\geoserver.log

With GEOSERVER_DEVELOPER_LOGGING set and saved, and when re-starting
GeoServer, in the console I see:

log4j:WARN File option not set for appender [geoserverlogfile].
log4j:WARN Are you using FileAppender instead of ConsoleAppender?10282
[main] INFO org.vfny.geoserver.global - StdOut logging enabled. Log
file also output to
'C:\GeoServer1.6-beta3\webapps\geoserver\logs\geoserver.log'

Is there an environment variable that needs to be set and/or a config
file that I should manually tweak to enable logging?

Thanks, Bob

sfarber wrote:

Hmm. That's strange that you're not getting any output at all to
geoserver.log

Is that the file set up as the 'logfile name' in your configuration?

As for logging configs, I'd choose 'geotools_development' or else
'verbose' or whatever. Both should give you a decent stacktrace for
the failure to connect to ArcSDE.

--saul

Bob Nutsch wrote:

Ah blast it anyway! Kicked in the teeth by that issue, argh!

I made the change and now the logging options are not grayed out!
Still having the same issue with the raster URL not being accepted.
Which is the correct logging option to select from the Logging
Profile list? I'm still not getting any output to
"C:\GeoServer1.6-beta3\webapps\geoserver\logs\geoserver.log"

Thanks, Bob

sfarber wrote:

Hmm. I've got an idea.

Can you run geoserver from a path with NO spaces in it?

Something like this:

c:\geoserver-1.6-beta3\...

Then see if that same error message comes up.

--saul

Bob Nutsch wrote:

Hi,

I was just looking at that. I noted in the console (after sending
the last email) that there was this message:

139255 [btpool0-6] WARN org.vfny.geoserver.global - Error figuring
out GeoServer logging configuration: java.io.FileNotFoundException:
C:\Program%20Files\GeoServer%201.6-beta3\webapps\geoserver\WEB-INF\classes\commons-logging.properties
(The system cannot find the path specified)

So I went looking and found that file:

C:\Program Files\GeoServer
1.6-beta3\webapps\geoserver\WEB-INF\classes\commons-logging.properties

which has the contents of:

org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger

Does this imply that I need to have something set up in Apache?
There are no current logs in Apache's log directory.

I did discover a user problem on my end, that I had failed to click
the Submit button after clicking the Verbose options in the Server
Configuration page. Those are now in place, sorry. But the other
logging options are still grayed out and there is still no content
in the log files.

Thanks, Bob

sfarber wrote:

Bob,

Can you check that there's a file called
'commons-logging.properties' in the WEB-INF/classes directory? If
not, can you add one? It's a one-line text file with the
following contents:

org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger

--saul

Bob Nutsch wrote:

Logging Profile
Suppress StdOut logging
Log Location

are grayed out and I can't click them.

--
View this message in context: http://www.nabble.com/ArcSDE-raster-URL-syntax-tf4635131.html#a13280001
Sent from the GeoServer - Dev mailing list archive at Nabble.com.

[Farber_Saul_EEA]

Strangely, I only see messages at the INFO level or above in your logfile
output Bob, and that's weird.

Can you try enabling the "GEOTOOLS_DEVELOPER.properties" profile and doing
the same thing again?

What I'm really trying to do is cause an exception of *some sort* to show up
as you get your sde raster url failure. Can you keep poking at the various
logging settings till you get an exception in the logfile when you try and
enter that URL? Don't forget to hit 'apply' and 'save' (although your
services.xml file looks totally fine).

Something with a stack trace is definitely necessary, cause otherwise I
don't know where to look!

--saul

Bob Nutsch wrote:

Hi,

Nifty tool! Here's the console just after starting GeoServer, nothing
done after the start: http://rafb.net/p/ArVftd54.html

Here's the console after logging in and then trying to use the ArcSDE URL:
http://rafb.net/p/ecC4FY39.html

I see those same two lines again:

log4j:WARN File option not set for appender [geoserverlogfile].
log4j:WARN Are you using FileAppender instead of ConsoleAppender?

These are not to be worried about?

Thanks, Bob

sfarber wrote:

Bob,

That's really weird that the logfile is still empty. Can you go to
http://rafb.net/paste/ and paste in the entire contents of the console?

Then send us the links to those pages, and I'll try and see what's going
on.

You might try doing some activity on geoserver to really generate events.
Open up a map, zoom around, etc.

Also try to have the URL fail to load and see if anything shows up when
you do that.

--saul

Bob Nutsch wrote:

Hi,

Thanks for the info. The logfile still remains empty, nothing in there.
The date/time stamp remains at the original install date, it hasn't been
touched.

Nothing in the console other than what I've cut and pasted below. The
'suppress stdout logging' UN-checked is unchecked.

I went and looked at C:\GeoServer1.6-beta3\data_dir\services.xml. I
think everything looks OK, the first few lines look like this:

<?config.xml version="1.0" encoding="UTF-8"?>
<!--
  Service level configuration
-->
<serverConfiguration >
  <global >
   
<log4jConfigFile>GEOSERVER_DEVELOPER_LOGGING.properties</log4jConfigFile>
    <suppressStdOutLogging value = "false" />
   
<logLocation>C:\GeoServer1.6-beta3\webapps\geoserver\logs\geoserver.log</logLocation>
    <JaiMemoryCapacity value = "0.5" />
    <JaiMemoryThreshold value = "0.75" />
    <JaiTileThreads value = "7" />
    <JaiTilePriority value = "5" />
    <JaiRecycling value = "true" />
    <ImageIOCache value = "false" />
    <JaiJPEGNative value = "true" />
    <JaiPNGNative value = "true" />

Thanks, Bob

sfarber wrote:

Bob,

The lines you're showing are actually just a side-effect message that
can be ignored. Basically, when starting up the logging, geoserver has
it start up without setting a logfile first and then injects the right
logfile right after longing is enabled. This works, but causes that
error you see (so that error can be ignored).

After the startup, do you see anything in that logfile
(c:\..\geoserver.log)? Or is that logfile empty?

How about the console? Do you have 'suppress stdout logging'
UN-checked?

--saul

Bob Nutsch wrote:

Hi Saul,

Still having a problem getting info written to the log file. In the
Server Configuration window, I've used
GEOSERVER_DEVELOPER_LOGGING
VERBOSE_LOGGING
GEOTOOLS_DEVELOPER_LOGGING

and have the log location set to

C:\GeoServer1.6-beta3\webapps\geoserver\logs\geoserver.log

and have tried \logs\geoserver.log

With GEOSERVER_DEVELOPER_LOGGING set and saved, and when re-starting
GeoServer, in the console I see:

log4j:WARN File option not set for appender [geoserverlogfile].
log4j:WARN Are you using FileAppender instead of ConsoleAppender?10282
[main] INFO org.vfny.geoserver.global - StdOut logging enabled. Log
file also output to
'C:\GeoServer1.6-beta3\webapps\geoserver\logs\geoserver.log'

Is there an environment variable that needs to be set and/or a config
file that I should manually tweak to enable logging?

Thanks, Bob

sfarber wrote:

Hmm. That's strange that you're not getting any output at all to
geoserver.log

Is that the file set up as the 'logfile name' in your configuration?

As for logging configs, I'd choose 'geotools_development' or else
'verbose' or whatever. Both should give you a decent stacktrace for
the failure to connect to ArcSDE.

--saul

Bob Nutsch wrote:

Ah blast it anyway! Kicked in the teeth by that issue, argh!

I made the change and now the logging options are not grayed out!
Still having the same issue with the raster URL not being accepted.
Which is the correct logging option to select from the Logging
Profile list? I'm still not getting any output to
"C:\GeoServer1.6-beta3\webapps\geoserver\logs\geoserver.log"

Thanks, Bob

sfarber wrote:

Hmm. I've got an idea.

Can you run geoserver from a path with NO spaces in it?

Something like this:

c:\geoserver-1.6-beta3\...

Then see if that same error message comes up.

--saul

Bob Nutsch wrote:

Hi,

I was just looking at that. I noted in the console (after sending
the last email) that there was this message:

139255 [btpool0-6] WARN org.vfny.geoserver.global - Error figuring
out GeoServer logging configuration:
java.io.FileNotFoundException:
C:\Program%20Files\GeoServer%201.6-beta3\webapps\geoserver\WEB-INF\classes\commons-logging.properties
(The system cannot find the path specified)

So I went looking and found that file:

C:\Program Files\GeoServer
1.6-beta3\webapps\geoserver\WEB-INF\classes\commons-logging.properties

which has the contents of:

org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger

Does this imply that I need to have something set up in Apache?
There are no current logs in Apache's log directory.

I did discover a user problem on my end, that I had failed to
click the Submit button after clicking the Verbose options in the
Server Configuration page. Those are now in place, sorry. But
the other logging options are still grayed out and there is still
no content in the log files.

Thanks, Bob

sfarber wrote:

Bob,

Can you check that there's a file called
'commons-logging.properties' in the WEB-INF/classes directory?
If not, can you add one? It's a one-line text file with the
following contents:

org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger

--saul

Bob Nutsch wrote:

Logging Profile
Suppress StdOut logging
Log Location

are grayed out and I can't click them.

--
View this message in context: http://www.nabble.com/ArcSDE-raster-URL-syntax-tf4635131.html#a13280012
Sent from the GeoServer - Dev mailing list archive at Nabble.com.

[Bob_Nutsch]

Hi,

Here's the steps I took to create the exception - something that I
discovered the other day. I'm using a versioned layer (ArcSDE 9.2, Oracle
10g) to create this crash:

1) log in
2) enabled GEOTOOLS_DEVELOPER logging and use Apply/Save buttons
3) go to Map Preview and click on the OpenLayers link across from the
'Counties_Poly' layer
4) the data displays fine, no problem. I can generally pan/zoom
tiled/untiled just fine.
5) to cause the crash (before or after panning/zooming) I click on one of
the counties, expecting to see that county's attributes (which happens with
the same non-versioned, ArcSDE 9.0 layer just fine). Right below the map,
instead of seeing the attributes I see:

java.lang.IndexOutOfBoundsException java.lang.IndexOutOfBoundsException
Details: org.geoserver.platform.ServiceException:
java.lang.IndexOutOfBoundsException at
org.geoserver.ows.Dispatcher.exception(Dispatcher.java:1146) at
org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:198) at
org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:139)
at
org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:44)
at

and other lines.

I then captured the entire console contents in:
http://rafb.net/p/ZusFiy88.html

C:\GeoServer1.6-beta3\webapps\geoserver\logs\geoserver.log is still empty.

Thanks, Bob

sfarber wrote:

Strangely, I only see messages at the INFO level or above in your logfile
output Bob, and that's weird.

Can you try enabling the "GEOTOOLS_DEVELOPER.properties" profile and doing
the same thing again?

What I'm really trying to do is cause an exception of *some sort* to show
up as you get your sde raster url failure. Can you keep poking at the
various logging settings till you get an exception in the logfile when you
try and enter that URL? Don't forget to hit 'apply' and 'save' (although
your services.xml file looks totally fine).

Something with a stack trace is definitely necessary, cause otherwise I
don't know where to look!

--saul

Bob Nutsch wrote:

Hi,

Nifty tool! Here's the console just after starting GeoServer, nothing
done after the start: http://rafb.net/p/ArVftd54.html

Here's the console after logging in and then trying to use the ArcSDE
URL: http://rafb.net/p/ecC4FY39.html

I see those same two lines again:

log4j:WARN File option not set for appender [geoserverlogfile].
log4j:WARN Are you using FileAppender instead of ConsoleAppender?

These are not to be worried about?

Thanks, Bob

sfarber wrote:

Bob,

That's really weird that the logfile is still empty. Can you go to
http://rafb.net/paste/ and paste in the entire contents of the console?

Then send us the links to those pages, and I'll try and see what's going
on.

You might try doing some activity on geoserver to really generate
events. Open up a map, zoom around, etc.

Also try to have the URL fail to load and see if anything shows up when
you do that.

--saul

Bob Nutsch wrote:

Hi,

Thanks for the info. The logfile still remains empty, nothing in
there. The date/time stamp remains at the original install date, it
hasn't been touched.

Nothing in the console other than what I've cut and pasted below. The
'suppress stdout logging' UN-checked is unchecked.

I went and looked at C:\GeoServer1.6-beta3\data_dir\services.xml. I
think everything looks OK, the first few lines look like this:

<?config.xml version="1.0" encoding="UTF-8"?>
<!--
  Service level configuration
-->
<serverConfiguration >
  <global >
   
<log4jConfigFile>GEOSERVER_DEVELOPER_LOGGING.properties</log4jConfigFile>
    <suppressStdOutLogging value = "false" />
   
<logLocation>C:\GeoServer1.6-beta3\webapps\geoserver\logs\geoserver.log</logLocation>
    <JaiMemoryCapacity value = "0.5" />
    <JaiMemoryThreshold value = "0.75" />
    <JaiTileThreads value = "7" />
    <JaiTilePriority value = "5" />
    <JaiRecycling value = "true" />
    <ImageIOCache value = "false" />
    <JaiJPEGNative value = "true" />
    <JaiPNGNative value = "true" />

Thanks, Bob

sfarber wrote:

Bob,

The lines you're showing are actually just a side-effect message that
can be ignored. Basically, when starting up the logging, geoserver
has it start up without setting a logfile first and then injects the
right logfile right after longing is enabled. This works, but causes
that error you see (so that error can be ignored).

After the startup, do you see anything in that logfile
(c:\..\geoserver.log)? Or is that logfile empty?

How about the console? Do you have 'suppress stdout logging'
UN-checked?

--saul

Bob Nutsch wrote:

Hi Saul,

Still having a problem getting info written to the log file. In the
Server Configuration window, I've used
GEOSERVER_DEVELOPER_LOGGING
VERBOSE_LOGGING
GEOTOOLS_DEVELOPER_LOGGING

and have the log location set to

C:\GeoServer1.6-beta3\webapps\geoserver\logs\geoserver.log

and have tried \logs\geoserver.log

With GEOSERVER_DEVELOPER_LOGGING set and saved, and when re-starting
GeoServer, in the console I see:

log4j:WARN File option not set for appender [geoserverlogfile].
log4j:WARN Are you using FileAppender instead of
ConsoleAppender?10282 [main] INFO org.vfny.geoserver.global - StdOut
logging enabled. Log file also output to
'C:\GeoServer1.6-beta3\webapps\geoserver\logs\geoserver.log'

Is there an environment variable that needs to be set and/or a config
file that I should manually tweak to enable logging?

Thanks, Bob

sfarber wrote:

Hmm. That's strange that you're not getting any output at all to
geoserver.log

Is that the file set up as the 'logfile name' in your configuration?

As for logging configs, I'd choose 'geotools_development' or else
'verbose' or whatever. Both should give you a decent stacktrace for
the failure to connect to ArcSDE.

--saul

Bob Nutsch wrote:

Ah blast it anyway! Kicked in the teeth by that issue, argh!

I made the change and now the logging options are not grayed out!
Still having the same issue with the raster URL not being accepted.
Which is the correct logging option to select from the Logging
Profile list? I'm still not getting any output to
"C:\GeoServer1.6-beta3\webapps\geoserver\logs\geoserver.log"

Thanks, Bob

sfarber wrote:

Hmm. I've got an idea.

Can you run geoserver from a path with NO spaces in it?

Something like this:

c:\geoserver-1.6-beta3\...

Then see if that same error message comes up.

--saul

Bob Nutsch wrote:

Hi,

I was just looking at that. I noted in the console (after
sending the last email) that there was this message:

139255 [btpool0-6] WARN org.vfny.geoserver.global - Error
figuring out GeoServer logging configuration:
java.io.FileNotFoundException:
C:\Program%20Files\GeoServer%201.6-beta3\webapps\geoserver\WEB-INF\classes\commons-logging.properties
(The system cannot find the path specified)

So I went looking and found that file:

C:\Program Files\GeoServer
1.6-beta3\webapps\geoserver\WEB-INF\classes\commons-logging.properties

which has the contents of:

org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger

Does this imply that I need to have something set up in Apache?
There are no current logs in Apache's log directory.

I did discover a user problem on my end, that I had failed to
click the Submit button after clicking the Verbose options in the
Server Configuration page. Those are now in place, sorry. But
the other logging options are still grayed out and there is still
no content in the log files.

Thanks, Bob

sfarber wrote:

Bob,

Can you check that there's a file called
'commons-logging.properties' in the WEB-INF/classes directory?
If not, can you add one? It's a one-line text file with the
following contents:

org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger

--saul

Bob Nutsch wrote:

Logging Profile
Suppress StdOut logging
Log Location

are grayed out and I can't click them.

--
View this message in context: http://www.nabble.com/ArcSDE-raster-URL-syntax-tf4635131.html#a13280650
Sent from the GeoServer - Dev mailing list archive at Nabble.com.

[Farber_Saul_EEA]

Bob,

Yes, there's a bug open right now
(http://jira.codehaus.org/browse/GEOT-1522) about using the ArcSDE plugin
with versioned tables. In addition, you may find that your back-end
gsrvr(.exe) process has crashed. Right now there's not much you can do
about this, other than not use versioned layers. There's been some interest
in sponsoring development to get this fixed. If you're interested in
helping with that, please drop me a line off-list.

--saul

Bob Nutsch wrote:

Hi,

Here's the steps I took to create the exception - something that I
discovered the other day. I'm using a versioned layer (ArcSDE 9.2, Oracle
10g) to create this crash:

1) log in
2) enabled GEOTOOLS_DEVELOPER logging and use Apply/Save buttons
3) go to Map Preview and click on the OpenLayers link across from the
'Counties_Poly' layer
4) the data displays fine, no problem. I can generally pan/zoom
tiled/untiled just fine.
5) to cause the crash (before or after panning/zooming) I click on one of
the counties, expecting to see that county's attributes (which happens
with the same non-versioned, ArcSDE 9.0 layer just fine). Right below the
map, instead of seeing the attributes I see:

java.lang.IndexOutOfBoundsException java.lang.IndexOutOfBoundsException
Details: org.geoserver.platform.ServiceException:
java.lang.IndexOutOfBoundsException at
org.geoserver.ows.Dispatcher.exception(Dispatcher.java:1146) at
org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:198) at
org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:139)
at
org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:44)
at

and other lines.

I then captured the entire console contents in:
http://rafb.net/p/ZusFiy88.html

C:\GeoServer1.6-beta3\webapps\geoserver\logs\geoserver.log is still empty.

Thanks, Bob

sfarber wrote:

Strangely, I only see messages at the INFO level or above in your logfile
output Bob, and that's weird.

Can you try enabling the "GEOTOOLS_DEVELOPER.properties" profile and
doing the same thing again?

What I'm really trying to do is cause an exception of *some sort* to show
up as you get your sde raster url failure. Can you keep poking at the
various logging settings till you get an exception in the logfile when
you try and enter that URL? Don't forget to hit 'apply' and 'save'
(although your services.xml file looks totally fine).

Something with a stack trace is definitely necessary, cause otherwise I
don't know where to look!

--saul

Bob Nutsch wrote:

Hi,

Nifty tool! Here's the console just after starting GeoServer, nothing
done after the start: http://rafb.net/p/ArVftd54.html

Here's the console after logging in and then trying to use the ArcSDE
URL: http://rafb.net/p/ecC4FY39.html

I see those same two lines again:

log4j:WARN File option not set for appender [geoserverlogfile].
log4j:WARN Are you using FileAppender instead of ConsoleAppender?

These are not to be worried about?

Thanks, Bob

sfarber wrote:

Bob,

That's really weird that the logfile is still empty. Can you go to
http://rafb.net/paste/ and paste in the entire contents of the console?

Then send us the links to those pages, and I'll try and see what's
going on.

You might try doing some activity on geoserver to really generate
events. Open up a map, zoom around, etc.

Also try to have the URL fail to load and see if anything shows up when
you do that.

--saul

Bob Nutsch wrote:

Hi,

Thanks for the info. The logfile still remains empty, nothing in
there. The date/time stamp remains at the original install date, it
hasn't been touched.

Nothing in the console other than what I've cut and pasted below. The
'suppress stdout logging' UN-checked is unchecked.

I went and looked at C:\GeoServer1.6-beta3\data_dir\services.xml. I
think everything looks OK, the first few lines look like this:

<?config.xml version="1.0" encoding="UTF-8"?>
<!--
  Service level configuration
-->
<serverConfiguration >
  <global >
   
<log4jConfigFile>GEOSERVER_DEVELOPER_LOGGING.properties</log4jConfigFile>
    <suppressStdOutLogging value = "false" />
   
<logLocation>C:\GeoServer1.6-beta3\webapps\geoserver\logs\geoserver.log</logLocation>
    <JaiMemoryCapacity value = "0.5" />
    <JaiMemoryThreshold value = "0.75" />
    <JaiTileThreads value = "7" />
    <JaiTilePriority value = "5" />
    <JaiRecycling value = "true" />
    <ImageIOCache value = "false" />
    <JaiJPEGNative value = "true" />
    <JaiPNGNative value = "true" />

Thanks, Bob

sfarber wrote:

Bob,

The lines you're showing are actually just a side-effect message that
can be ignored. Basically, when starting up the logging, geoserver
has it start up without setting a logfile first and then injects the
right logfile right after longing is enabled. This works, but causes
that error you see (so that error can be ignored).

After the startup, do you see anything in that logfile
(c:\..\geoserver.log)? Or is that logfile empty?

How about the console? Do you have 'suppress stdout logging'
UN-checked?

--saul

Bob Nutsch wrote:

Hi Saul,

Still having a problem getting info written to the log file. In the
Server Configuration window, I've used
GEOSERVER_DEVELOPER_LOGGING
VERBOSE_LOGGING
GEOTOOLS_DEVELOPER_LOGGING

and have the log location set to

C:\GeoServer1.6-beta3\webapps\geoserver\logs\geoserver.log

and have tried \logs\geoserver.log

With GEOSERVER_DEVELOPER_LOGGING set and saved, and when re-starting
GeoServer, in the console I see:

log4j:WARN File option not set for appender [geoserverlogfile].
log4j:WARN Are you using FileAppender instead of
ConsoleAppender?10282 [main] INFO org.vfny.geoserver.global - StdOut
logging enabled. Log file also output to
'C:\GeoServer1.6-beta3\webapps\geoserver\logs\geoserver.log'

Is there an environment variable that needs to be set and/or a
config file that I should manually tweak to enable logging?

Thanks, Bob

sfarber wrote:

Hmm. That's strange that you're not getting any output at all to
geoserver.log

Is that the file set up as the 'logfile name' in your
configuration?

As for logging configs, I'd choose 'geotools_development' or else
'verbose' or whatever. Both should give you a decent stacktrace
for the failure to connect to ArcSDE.

--saul

Bob Nutsch wrote:

Ah blast it anyway! Kicked in the teeth by that issue, argh!

I made the change and now the logging options are not grayed out!
Still having the same issue with the raster URL not being
accepted. Which is the correct logging option to select from the
Logging Profile list? I'm still not getting any output to
"C:\GeoServer1.6-beta3\webapps\geoserver\logs\geoserver.log"

Thanks, Bob

sfarber wrote:

Hmm. I've got an idea.

Can you run geoserver from a path with NO spaces in it?

Something like this:

c:\geoserver-1.6-beta3\...

Then see if that same error message comes up.

--saul

Bob Nutsch wrote:

Hi,

I was just looking at that. I noted in the console (after
sending the last email) that there was this message:

139255 [btpool0-6] WARN org.vfny.geoserver.global - Error
figuring out GeoServer logging configuration:
java.io.FileNotFoundException:
C:\Program%20Files\GeoServer%201.6-beta3\webapps\geoserver\WEB-INF\classes\commons-logging.properties
(The system cannot find the path specified)

So I went looking and found that file:

C:\Program Files\GeoServer
1.6-beta3\webapps\geoserver\WEB-INF\classes\commons-logging.properties

which has the contents of:

org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger

Does this imply that I need to have something set up in Apache?
There are no current logs in Apache's log directory.

I did discover a user problem on my end, that I had failed to
click the Submit button after clicking the Verbose options in
the Server Configuration page. Those are now in place, sorry.
But the other logging options are still grayed out and there is
still no content in the log files.

Thanks, Bob

sfarber wrote:

Bob,

Can you check that there's a file called
'commons-logging.properties' in the WEB-INF/classes directory?
If not, can you add one? It's a one-line text file with the
following contents:

org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger

--saul

Bob Nutsch wrote:

Logging Profile
Suppress StdOut logging
Log Location

are grayed out and I can't click them.

--
View this message in context: http://www.nabble.com/ArcSDE-raster-URL-syntax-tf4635131.html#a13281047
Sent from the GeoServer - Dev mailing list archive at Nabble.com.

[Bob_Nutsch]

Hi,

Just a note that I found what is causing the problem.

When I use the GeoServer GUI and enter

sde://bnutsch:password@anonymised.com:5151/#NDHUB.AERIALPHOTOS_6INCH

I get the 'invalid url' error that I first reported.

When I manually edit the catalog.xml and enter this info, e.g.,

    <format namespace = "NDHUB" enabled = "true" id = "NDHUB_aerialphotos" >
       <type>ArcSDE Raster</type>
      
<url>sde://bnutsch:password@anonymised.com:5151/#NDHUB.AERIALPHOTOS_6INCH</url>
    </format>

I get a crash. In the logs I see:

26 Oct 14:48:45 WARN [org.geotools.arcsde.gce] - connectiong via file-hack
to ArcSDE Raster: sde:\bnutsch:pass@anonymised.com:5151\#NDHUB.AERIALPHOTOS_6INCH
26 Oct 14:48:45 WARN [org.geotools.arcsde.gce] - connectiong via file-hack
to ArcSDE Raster: sde:\bnutsch:pass@anonymised.com:5151\#NDHUB.AERIALPHOTOS_6INCH
26 Oct 14:48:45 WARN [org.apache.struts.action.RequestProcessor] - Unhandled
Exception thrown: class java.lang.IllegalArgumentException
26 Oct 14:48:45 ERROR
[org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/geoserver].[action]]
- Servlet.service() for servlet action threw exception
java.lang.IllegalArgumentException: ArcSDE Raster URL must be of the form
sde://user:pass@anonymised.com:port/[dbname]#rasterTableName -- Got
sde:\bnutsch:pass@anonymised.com:5151\#NDHUB.AERIALPHOTOS_6INCH
  at
org.geotools.arcsde.gce.ArcSDERasterGridCoverage2DReader.sdeURLToConnectionConfig(ArcSDERasterGridCoverage2DReader.java:453)
  at
org.geotools.arcsde.gce.ArcSDERasterGridCoverage2DReader.setupConnectionPool(ArcSDERasterGridCoverage2DReader.java:604)
  at
org.geotools.arcsde.gce.ArcSDERasterGridCoverage2DReader.<init>(ArcSDERasterGridCoverage2DReader.java:172)

From visiting with Saul off-line, it appears that this is a case of windows

- unix slash directions.

I plan to try my hand at entering this bug into jira.codehaus.org

Regards, Bob

Bob Nutsch wrote:

Hi,

I'm trying to access raster data from ArcSDE 9.2 (with has a backend of
Oracle 10g). I select 'ArcSDE Raster Format' from the list when starting
to set up a new coverage store. I supply a Coverage Data Set ID and then
click on the New button.

I must be doing something wrong for the URL syntax because after entering
the URL information and clicking on the Submit button I get the following
on the left side of the GeoServer admin page:

"Invalid url:
'sde://myuser:mypwd@anonymised.com:5198/#NDHUB.NGS_DRG24K;LZERO_ORIGIN_TILE=0,0'
for format type:'ArcSDE Raster'.

I've looked at the example shown on
http://docs.codehaus.org/display/GEOTDOC/ArcSDE+DataStore. I'm too dumb
to figure out what I'm missing.

Here's my information:

User: myuser
Pwd: mypwd
Server: myserver.state.nd.us
ArcSDE instance: 5198
raster layer: NDHUB.NGS_DRG24K (where 'NDHUB' is the schema owner)

There's something wrong with the syntax around the '#' area I think. It's
been my experience that when using ArcSDE with Oracle, there is not a
database or instance name, simply the server and port number (along with
the userid and password). For SQL Server, I would enter the name of the
database but there is no database name for Oracle. So when using ESRI
tools I generally leave the database name blank or enter a "#" for that
field. I'm thinking that perhaps this is the issue with the URL that I'm
using, but I'm not sure.

Any thoughts would be greatly appreciated!

Thanks, Bob

--
View this message in context: http://www.nabble.com/ArcSDE-raster-URL-syntax-tf4635131.html#a13434681
Sent from the GeoServer - Dev mailing list archive at Nabble.com.