[Geoserver-users] 1.6.3 Beta 3 war in JBoss 4.0.5

Andy_Dale · October 25, 2007, 8:55am

Hi,

I am trying to deploy geoserver as a war archive within JBoss-4.0.5.GA, but unfortunately it will not deploy at all . The first error that appears is the following :

2007-10-25 10:59:23,886 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] Using session cookies default setting
2007-10-25 10:59:24,396 ERROR [STDERR] log4j:ERROR A “org.jboss.logging.util.OnlyOnceErrorHandler” object is not assignable to a " org.apache.log4j.spi.Error
Handler" variable.
2007-10-25 10:59:24,397 ERROR [STDERR] log4j:ERROR The class “org.apache.log4j.spi.ErrorHandler” was loaded by
2007-10-25 10:59:24,397 ERROR [STDERR] log4j:ERROR [WebappClassLoader
delegate: false
repositories:
/WEB-INF/classes/
----------> Parent Classloader:
java.net.FactoryURLClassLoader@anonymised.com
] whereas object of type
2007-10-25 10:59:24,398 ERROR [STDERR] log4j:ERROR " org.jboss.logging.util.OnlyOnceErrorHandler" was loaded by [org.jboss.system.server.NoAnnotationURLClass
Loader@anonymised.com].
2007-10-25 10:59:24,532 ERROR [STDERR] log4j:ERROR Could not create an Appender. Reported error follows.
2007-10-25 10:59:24,532 ERROR [STDERR] java.lang.ClassCastException: org.jboss.logging.appender.DailyRollingFileAppender
2007-10-25 10:59:24,534 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parseAppender (DOMConfigurator.java:175)
2007-10-25 10:59:24,535 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:150)
2007-10-25 10:59:24,535 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.findAppenderByReference (DOMConfigurator.java:163)
2007-10-25 10:59:24,536 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:425)
2007-10-25 10:59:24,536 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parseRoot (DOMConfigurator.java:394)
2007-10-25 10:59:24,536 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:829)
2007-10-25 10:59:24,537 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.doConfigure (DOMConfigurator.java:712)
2007-10-25 10:59:24,537 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:618)
2007-10-25 10:59:24,537 ERROR [STDERR] at org.apache.log4j.helpers.OptionConverter.selectAndConfigure (OptionConverter.java:470)
2007-10-25 10:59:24,538 ERROR [STDERR] at org.apache.log4j.LogManager.(LogManager.java:122)

This then has a knock on effect, and the next exception is:

Initialization of bean failed; nested exception is java.lang.NullPointerException: null
org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘config’ defined in URL [jar:file:/usr/local/jboss-4.0.5.GA_NO_IMS/se
rver/default/tmp/deploy/tmp54840geoserver- exp.war/WEB-INF/lib/main-1.6-beta3.jar!/applicationContext.xml]: Initialization of bean failed; nested exception i
s java.lang.NullPointerException: null
java.lang.NullPointerException
at java.io.FileInputStream .(FileInputStream.java:103)
at org.vfny.geoserver.global.xml.XMLConfigReader.loadServices(XMLConfigReader.java:241)
at org.vfny.geoserver.global.xml.XMLConfigReader.load(XMLConfigReader.java :205)
at org.vfny.geoserver.global.xml.XMLConfigReader.(XMLConfigReader.java:169)
at org.vfny.geoserver.global.Config.setApplicationContext(Config.java:70)
at org.springframework.context.support.ApplicationContextAwareProcessor.postProcessBeforeInitialization (ApplicationContextAwareProcessor.java:84)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableB
eanFactory.java :248)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:362)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean (AbstractBeanFactory.java:226)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:147)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference (BeanDefinitionValueResolver.java:176)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:105)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFacto

Has anybody also encountered this error ? I think it is related (the first error at least) to the log4j setup.

Any help is appreciated.

Cheers,

Andy

Andrea_Aime3 · October 25, 2007, 9:10am

Andy Dale ha scritto:

Hi,

I am trying to deploy geoserver as a war archive within JBoss-4.0.5.GA <http://JBoss-4.0.5.GA>, but unfortunately it will not deploy at all . The first error that appears is the following :

2007-10-25 10:59:23,886 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] Using session cookies default setting
2007-10-25 10:59:24,396 ERROR [STDERR] log4j:ERROR A "org.jboss.logging.util.OnlyOnceErrorHandler" object is not assignable to a " org.apache.log4j.spi.Error
Handler" variable.
2007-10-25 10:59:24,397 ERROR [STDERR] log4j:ERROR The class "org.apache.log4j.spi.ErrorHandler" was loaded by
2007-10-25 10:59:24,397 ERROR [STDERR] log4j:ERROR [WebappClassLoader
  delegate: false
  repositories:
    /WEB-INF/classes/
----------> Parent Classloader:
java.net.FactoryURLClassLoader@anonymised.com
] whereas object of type
2007-10-25 10:59:24,398 ERROR [STDERR] log4j:ERROR " org.jboss.logging.util.OnlyOnceErrorHandler" was loaded by [org.jboss.system.server.NoAnnotationURLClass
Loader@anonymised.com].
2007-10-25 10:59:24,532 ERROR [STDERR] log4j:ERROR Could not create an Appender. Reported error follows.
2007-10-25 10:59:24,532 ERROR [STDERR] java.lang.ClassCastException: org.jboss.logging.appender.DailyRollingFileAppender
2007-10-25 10:59:24,534 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parseAppender (DOMConfigurator.java:175)
2007-10-25 10:59:24,535 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:150)
2007-10-25 10:59:24,535 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.findAppenderByReference (DOMConfigurator.java:163)
2007-10-25 10:59:24,536 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:425)
2007-10-25 10:59:24,536 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parseRoot (DOMConfigurator.java:394)
2007-10-25 10:59:24,536 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:829)
2007-10-25 10:59:24,537 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.doConfigure (DOMConfigurator.java:712)
2007-10-25 10:59:24,537 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:618)
2007-10-25 10:59:24,537 ERROR [STDERR] at org.apache.log4j.helpers.OptionConverter.selectAndConfigure (OptionConverter.java:470)
2007-10-25 10:59:24,538 ERROR [STDERR] at org.apache.log4j.LogManager.<clinit>(LogManager.java:122)

This one I've never seen, but does not seem to be fatal.

This then has a knock on effect, and the next exception is:

Initialization of bean failed; nested exception is java.lang.NullPointerException: null
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'config' defined in URL [jar:file:/usr/local/jboss-4.0.5.GA_NO_IMS/se
rver/default/tmp/deploy/tmp54840geoserver- exp.war/WEB-INF/lib/main-1.6-beta3.jar!/applicationContext.xml]: Initialization of bean failed; nested exception i
s java.lang.NullPointerException: null
java.lang.NullPointerException
        at java.io.FileInputStream .<init>(FileInputStream.java:103)
        at org.vfny.geoserver.global.xml.XMLConfigReader.loadServices(XMLConfigReader.java:241)
        at org.vfny.geoserver.global.xml.XMLConfigReader.load(XMLConfigReader.java :205)
        at org.vfny.geoserver.global.xml.XMLConfigReader.<init>(XMLConfigReader.java:169)
        at org.vfny.geoserver.global.Config.setApplicationContext(Config.java:70)
        at org.springframework.context.support.ApplicationContextAwareProcessor.postProcessBeforeInitialization (ApplicationContextAwareProcessor.java:84)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableB
eanFactory.java :248)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:362)
        at org.springframework.beans.factory.support.AbstractBeanFactory.getBean (AbstractBeanFactory.java:226)
        at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:147)
        at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference (BeanDefinitionValueResolver.java:176)
        at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:105)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFacto

This usually happens when GeoServer war is not unpacked
during deploy. If you don't set the GEOSERVER_DATA_DIR environment
variable GeoServer will try to use the data_dir we ship
inside the war, and fail if the war is not unpacked.

Hope this helps
Cheers
Andrea

Andy_Dale · October 25, 2007, 9:36am

Hi,

I have carried out a bit of testing, with a config I know works (JBoss-4.0.4.GA and geoserver-1.5.1.war) without the data dir being set and it works fine, but when i try to deploy the 1.6 war i get the same errors as in the JBoss-4.0.5.GA environment. This leads me to believe that the data dir is not the cause/solution to the problem.

Thanks,

Andy

On 25/10/2007, Andrea Aime <aaime@anonymised.com> wrote:

Andy Dale ha scritto:

Hi,

I am trying to deploy geoserver as a war archive within JBoss-4.0.5.GA
<http://JBoss-4.0.5.GA >, but unfortunately it will not deploy at all
. The first error that appears is the following :

2007-10-25 10:59:23,886 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer]
Using session cookies default setting
2007-10-25 10:59:24,396 ERROR [STDERR] log4j:ERROR A
“org.jboss.logging.util.OnlyOnceErrorHandler” object is not assignable
to a " org.apache.log4j.spi.Error
Handler" variable.
2007-10-25 10:59:24,397 ERROR [STDERR] log4j:ERROR The class
“org.apache.log4j.spi.ErrorHandler” was loaded by
2007-10-25 10:59:24,397 ERROR [STDERR] log4j:ERROR [WebappClassLoader
delegate: false
repositories:
/WEB-INF/classes/
----------> Parent Classloader:
java.net.FactoryURLClassLoader@anonymised.com
] whereas object of type
2007-10-25 10:59:24,398 ERROR [STDERR] log4j:ERROR "
org.jboss.logging.util.OnlyOnceErrorHandler" was loaded by
[org.jboss.system.server.NoAnnotationURLClass
Loader@anonymised.com].
2007-10-25 10:59:24,532 ERROR [STDERR] log4j:ERROR Could not create an
Appender. Reported error follows.
2007-10-25 10:59:24,532 ERROR [STDERR] java.lang.ClassCastException:
org.jboss.logging.appender.DailyRollingFileAppender
2007-10-25 10:59:24,534 ERROR [STDERR] at
org.apache.log4j.xml.DOMConfigurator.parseAppender
(DOMConfigurator.java:175)
2007-10-25 10:59:24,535 ERROR [STDERR] at
org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java :150)
2007-10-25 10:59:24,535 ERROR [STDERR] at
org.apache.log4j.xml.DOMConfigurator.findAppenderByReference
(DOMConfigurator.java:163)
2007-10-25 10:59:24,536 ERROR [STDERR] at
org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement (DOMConfigurator.java:425)
2007-10-25 10:59:24,536 ERROR [STDERR] at
org.apache.log4j.xml.DOMConfigurator.parseRoot (DOMConfigurator.java:394)
2007-10-25 10:59:24,536 ERROR [STDERR] at
org.apache.log4j.xml.DOMConfigurator.parse (DOMConfigurator.java:829)
2007-10-25 10:59:24,537 ERROR [STDERR] at
org.apache.log4j.xml.DOMConfigurator.doConfigure (DOMConfigurator.java:712)
2007-10-25 10:59:24,537 ERROR [STDERR] at
org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:618)
2007-10-25 10:59:24,537 ERROR [STDERR] at
org.apache.log4j.helpers.OptionConverter.selectAndConfigure
(OptionConverter.java :470)
2007-10-25 10:59:24,538 ERROR [STDERR] at
org.apache.log4j.LogManager.(LogManager.java:122)

This one I’ve never seen, but does not seem to be fatal.

This then has a knock on effect, and the next exception is:

Initialization of bean failed; nested exception is
java.lang.NullPointerException: null
org.springframework.beans.factory.BeanCreationException: Error creating
bean with name ‘config’ defined in URL
[jar:file:/usr/local/jboss-4.0.5.GA_NO_IMS/se
rver/default/tmp/deploy/tmp54840geoserver-
exp.war/WEB-INF/lib/main-1.6-beta3.jar!/applicationContext.xml]:
Initialization of bean failed; nested exception i
s java.lang.NullPointerException: null
java.lang.NullPointerException
at java.io.FileInputStream .(FileInputStream.java:103)
at
org.vfny.geoserver.global.xml.XMLConfigReader.loadServices (XMLConfigReader.java:241)
at
org.vfny.geoserver.global.xml.XMLConfigReader.load(XMLConfigReader.java
:205)
at
org.vfny.geoserver.global.xml.XMLConfigReader.( XMLConfigReader.java:169)
at
org.vfny.geoserver.global.Config.setApplicationContext(Config.java:70)
at
org.springframework.context.support.ApplicationContextAwareProcessor.postProcessBeforeInitialization
(ApplicationContextAwareProcessor.java:84)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableB
eanFactory.java :248)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:362)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean
(AbstractBeanFactory.java:226)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:147)
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference
(BeanDefinitionValueResolver.java:176)
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:105)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFacto

This usually happens when GeoServer war is not unpacked
during deploy. If you don’t set the GEOSERVER_DATA_DIR environment
variable GeoServer will try to use the data_dir we ship
inside the war, and fail if the war is not unpacked.

Hope this helps
Cheers
Andrea

Andy_Dale · October 26, 2007, 8:24am

Hi,

I managed to get 1.5.1 to work with JBoss 4.0.5 with it’s own data directory after a bit of work, I had to deploy it without the data dir being set , then copyied the contents of the default data dir created (located in the /tmp JBoss directory) to elsewhere on the hard drive.

The problem is that I still cannot get 1.6 Beta 3 to deploy as i can never get it to deploy without the data dir being set, this would allow me to copy it to elsewhere on the hard drive and then set the data dir to that location. I even tried copying the contents of the 1.5.1 data dir into the 1.6 dat dir but it still fails to deploy.

Cheers,

Andy

On 25/10/2007, Andy Dale < andy.dale@anonymised.com> wrote:

Hi,

I have carried out a bit of testing, with a config I know works ( JBoss-4.0.4.GA and geoserver-1.5.1.war) without the data dir being set and it works fine, but when i try to deploy the 1.6 war i get the same errors as in the JBoss-4.0.5.GA environment. This leads me to believe that the data dir is not the cause/solution to the problem.

Thanks,

Andy

On 25/10/2007, Andrea Aime <aaime@anonymised.com > wrote:

Andy Dale ha scritto:

Hi,

I am trying to deploy geoserver as a war archive within JBoss-4.0.5.GA
<http://JBoss-4.0.5.GA >, but unfortunately it will not deploy at all
. The first error that appears is the following :

2007-10-25 10:59:23,886 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer]
Using session cookies default setting
2007-10-25 10:59:24,396 ERROR [STDERR] log4j:ERROR A
“org.jboss.logging.util.OnlyOnceErrorHandler” object is not assignable
to a " org.apache.log4j.spi.Error
Handler" variable.
2007-10-25 10:59:24,397 ERROR [STDERR] log4j:ERROR The class
“org.apache.log4j.spi.ErrorHandler” was loaded by
2007-10-25 10:59:24,397 ERROR [STDERR] log4j:ERROR [WebappClassLoader
delegate: false
repositories:
/WEB-INF/classes/
----------> Parent Classloader:
java.net.FactoryURLClassLoader@anonymised.com
] whereas object of type
2007-10-25 10:59:24,398 ERROR [STDERR] log4j:ERROR "
org.jboss.logging.util.OnlyOnceErrorHandler" was loaded by
[org.jboss.system.server.NoAnnotationURLClass
Loader@anonymised.com].
2007-10-25 10:59:24,532 ERROR [STDERR] log4j:ERROR Could not create an
Appender. Reported error follows.
2007-10-25 10:59:24,532 ERROR [STDERR] java.lang.ClassCastException:
org.jboss.logging.appender.DailyRollingFileAppender
2007-10-25 10:59:24,534 ERROR [STDERR] at
org.apache.log4j.xml.DOMConfigurator.parseAppender
(DOMConfigurator.java:175)
2007-10-25 10:59:24,535 ERROR [STDERR] at
org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java :150)
2007-10-25 10:59:24,535 ERROR [STDERR] at
org.apache.log4j.xml.DOMConfigurator.findAppenderByReference
(DOMConfigurator.java:163)
2007-10-25 10:59:24,536 ERROR [STDERR] at
org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement (DOMConfigurator.java:425)
2007-10-25 10:59:24,536 ERROR [STDERR] at
org.apache.log4j.xml.DOMConfigurator.parseRoot (DOMConfigurator.java:394)
2007-10-25 10:59:24,536 ERROR [STDERR] at
org.apache.log4j.xml.DOMConfigurator.parse (DOMConfigurator.java:829)
2007-10-25 10:59:24,537 ERROR [STDERR] at
org.apache.log4j.xml.DOMConfigurator.doConfigure (DOMConfigurator.java:712)
2007-10-25 10:59:24,537 ERROR [STDERR] at
org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:618)
2007-10-25 10:59:24,537 ERROR [STDERR] at
org.apache.log4j.helpers.OptionConverter.selectAndConfigure
(OptionConverter.java :470)
2007-10-25 10:59:24,538 ERROR [STDERR] at
org.apache.log4j.LogManager.(LogManager.java:122)

This one I’ve never seen, but does not seem to be fatal.

This then has a knock on effect, and the next exception is:

Initialization of bean failed; nested exception is
java.lang.NullPointerException: null
org.springframework.beans.factory.BeanCreationException: Error creating
bean with name ‘config’ defined in URL
[jar:file:/usr/local/jboss-4.0.5.GA_NO_IMS/se
rver/default/tmp/deploy/tmp54840geoserver-
exp.war/WEB-INF/lib/main-1.6-beta3.jar!/applicationContext.xml]:
Initialization of bean failed; nested exception i
s java.lang.NullPointerException: null
java.lang.NullPointerException
at java.io.FileInputStream .(FileInputStream.java:103)
at
org.vfny.geoserver.global.xml.XMLConfigReader.loadServices (XMLConfigReader.java:241)
at
org.vfny.geoserver.global.xml.XMLConfigReader.load(XMLConfigReader.java
:205)
at
org.vfny.geoserver.global.xml.XMLConfigReader.( XMLConfigReader.java:169)
at
org.vfny.geoserver.global.Config.setApplicationContext(Config.java:70)
at
org.springframework.context.support.ApplicationContextAwareProcessor.postProcessBeforeInitialization
(ApplicationContextAwareProcessor.java:84)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableB
eanFactory.java :248)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:362)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean
(AbstractBeanFactory.java:226)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:147)
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference
(BeanDefinitionValueResolver.java:176)
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:105)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFacto

This usually happens when GeoServer war is not unpacked
during deploy. If you don’t set the GEOSERVER_DATA_DIR environment
variable GeoServer will try to use the data_dir we ship
inside the war, and fail if the war is not unpacked.

Hope this helps
Cheers
Andrea

Andrea_Aime3 · October 26, 2007, 9:01am

Andy Dale ha scritto:

Hi,

I managed to get 1.5.1 to work with JBoss 4.0.5 with it's own data directory after a bit of work, I had to deploy it without the data dir being set , then copyied the contents of the default data dir created (located in the /tmp JBoss directory) to elsewhere on the hard drive.

The problem is that I still cannot get 1.6 Beta 3 to deploy as i can never get it to deploy without the data dir being set, this would allow me to copy it to elsewhere on the hard drive and then set the data dir to that location. I even tried copying the contents of the 1.5.1 data dir into the 1.6 dat dir but it still fails to deploy.

The error is caused by GeoServer not being able to find the data directory or not being able to reach out to it because of security
lock downs. Can you try again with the data dir set and send me the
whole log file generated by that failed startup?

In the meantime, can you test if you're running in a security locked
down environment? What did you do to setup jboss? Which operating
system are you running on?
Also, may it be possible that the data dir you're using has spaces
inside the path?

I've tried deploying GeoServer on 4.0.5GA (the version I happen to
have on my PC) and I had no real problems... the only thing that
got me is that setting the GEOSERVER_DATA_DIR environment variable
wasn't enough, I had to pass it to the JBoss run.bat starter
as:
run.bat -DGEOSERVER_DATA_DIR=xxxx
in order to make it see it...

Cheers
Andrea

Andy_Dale · October 26, 2007, 9:33am

Hi,

I will send you the logfile later on today, but just to answer a few of your questions first.

In the meantime, can you test if you’re running in a security locked down environment?

I am running in Fedora Core 5, and seems as the GeoServer 1.5.1 works i cannot see the environment being the cause of the problem

What did you do to setup jboss?

It is a stock ejb3 clustered install

Which operating system are you running on?

Fedora Core 5

Also, may it be possible that the data dir you’re using has spaces
inside the path?

I tend to avoid this as spaces in Linux are a pain. The path to the data dir is /var/geoserver_1.6, and the user i run jboss with has write access to this file and executable to /var (the path for 1.5.1 is /var/geoserver with the same permissions)

run.bat -DGEOSERVER_DATA_DIR=xxxx

In the run.conf file i have this line, this adds it to the vmargs on startup of JBoss

Cheers,

Andy

On 26/10/2007, Andrea Aime <aaime@anonymised.com> wrote:

Andy Dale ha scritto:

Hi,

I managed to get 1.5.1 to work with JBoss 4.0.5 with it’s own data
directory after a bit of work, I had to deploy it without the data dir
being set , then copyied the contents of the default data dir created
(located in the /tmp JBoss directory) to elsewhere on the hard drive.

The problem is that I still cannot get 1.6 Beta 3 to deploy as i can
never get it to deploy without the data dir being set, this would allow
me to copy it to elsewhere on the hard drive and then set the data dir
to that location. I even tried copying the contents of the 1.5.1 data
dir into the 1.6 dat dir but it still fails to deploy.

The error is caused by GeoServer not being able to find the data
directory or not being able to reach out to it because of security
lock downs. Can you try again with the data dir set and send me the
whole log file generated by that failed startup?

In the meantime, can you test if you’re running in a security locked
down environment? What did you do to setup jboss? Which operating
system are you running on?
Also, may it be possible that the data dir you’re using has spaces
inside the path?

I’ve tried deploying GeoServer on 4.0.5GA (the version I happen to
have on my PC) and I had no real problems… the only thing that
got me is that setting the GEOSERVER_DATA_DIR environment variable
wasn’t enough, I had to pass it to the JBoss run.bat starter
as:
run.bat -DGEOSERVER_DATA_DIR=xxxx
in order to make it see it…

Cheers
Andrea

Andy_Dale · October 30, 2007, 1:17pm

Hi,

I have just attempted to deploy GeoServer-1.6-BETA4 as a war archive within JBoss-4.0.5 and it deploys ok.

When i deploy it without the any data dir specified it defaults to the tmp dir of the JBoss server, which is what I expected, and i also get 2 non fatal exceptions (log4j exception and a NPE when attempting to load the plugins).

I then copied the contents of the data directory to somewhere on my local HD and the restarted JBoss point to the copy location as the property GEOSERVER_DATA_DIR. On restart it again deploys fine, but there seems to now be some more new non-fatal exceptions being thrown like below:

30 Oct 10:02:26 DEBUG [org.geotools.data.property] - can’t process parameters
java.io.IOException: Parameter directory is required:Directory containting property files
at org.geotools.data.DataStoreFactorySpi$Param.lookUp (DataStoreFactorySpi.java:392)
at org.geotools.data.property.PropertyDataStoreFactory.directoryLookup(PropertyDataStoreFactory.java:187)
at org.geotools.data.property.PropertyDataStoreFactory.canProcess (PropertyDataStoreFactory.java:156)
at org.geotools.data.DataStoreFinder.getDataStore(DataStoreFinder.java:90)
at org.vfny.geoserver.util.DataStoreUtils.getDataStore(DataStoreUtils.java:62)
at org.vfny.geoserver.global.DataStoreInfo.getDataStore(DataStoreInfo.java:207)
at org.vfny.geoserver.global.Data.loadFeatureTypes(Data.java:552)
at org.vfny.geoserver.global.Data.load(Data.java:233)
at org.vfny.geoserver.global.Data.(Data.java:176)
at org.vfny.geoserver.global.Data.(Data.java:186)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:100)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate (SimpleInstantiationStrategy.java:75)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:669)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean (AbstractAutowireCapableBeanFactory.java:329)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:226)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean (AbstractBeanFactory.java:147)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:176)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary (BeanDefinitionValueResolver.java:105)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.resolveConstructor

Is the above exception with the parameters a know problem, and does anyone know how to resolve this problem ?

Cheers,

Andy

On 26/10/2007, Andy Dale < andy.dale@anonymised.com> wrote:

I have attached the server.log file, and jboss was started with the following command

sh run.sh -b 127.0.0.1 -g test -u 235.53.35.53

which produced the folow env output

=========================================================================

JBoss Bootstrap Environment

JBOSS_HOME: /usr/local/jboss-4.0.5.GA_NEW

JAVA: /usr/java/jdk1.5.0_06/bin/java

JAVA_OPTS: -Dprogram.name=run.sh -server -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -XX:PermSize=128m -XX:MaxPermSize=256m -DGEOSERVER_DATA_DIR=/var/geoserver_1.6/

CLASSPATH: /usr/local/jboss-4.0.5.GA_NEW/bin/run.jar:/usr/java/jdk1.5.0_06/lib/tools.jar

=========================================================================

Cheers,

Andy

On 26/10/2007, Andy Dale <andy.dale@anonymised.com> wrote:

Hi,

I will send you the logfile later on today, but just to answer a few of your questions first.

In the meantime, can you test if you’re running in a security locked down environment?

I am running in Fedora Core 5, and seems as the GeoServer 1.5.1 works i cannot see the environment being the cause of the problem

What did you do to setup jboss?

It is a stock ejb3 clustered install

Which operating system are you running on?

Fedora Core 5

Also, may it be possible that the data dir you’re using has spaces
inside the path?

I tend to avoid this as spaces in Linux are a pain. The path to the data dir is /var/geoserver_1.6, and the user i run jboss with has write access to this file and executable to /var (the path for 1.5.1 is /var/geoserver with the same permissions)

run.bat -DGEOSERVER_DATA_DIR=xxxx

In the run.conf file i have this line, this adds it to the vmargs on startup of JBoss

Cheers,

Andy

On 26/10/2007, Andrea Aime <aaime@anonymised.com > wrote:

Andy Dale ha scritto:

Hi,

I managed to get 1.5.1 to work with JBoss 4.0.5 with it’s own data
directory after a bit of work, I had to deploy it without the data dir
being set , then copyied the contents of the default data dir created
(located in the /tmp JBoss directory) to elsewhere on the hard drive.

The problem is that I still cannot get 1.6 Beta 3 to deploy as i can
never get it to deploy without the data dir being set, this would allow
me to copy it to elsewhere on the hard drive and then set the data dir
to that location. I even tried copying the contents of the 1.5.1 data
dir into the 1.6 dat dir but it still fails to deploy.

The error is caused by GeoServer not being able to find the data
directory or not being able to reach out to it because of security
lock downs. Can you try again with the data dir set and send me the
whole log file generated by that failed startup?

In the meantime, can you test if you’re running in a security locked
down environment? What did you do to setup jboss? Which operating
system are you running on?
Also, may it be possible that the data dir you’re using has spaces
inside the path?

I’ve tried deploying GeoServer on 4.0.5GA (the version I happen to
have on my PC) and I had no real problems… the only thing that
got me is that setting the GEOSERVER_DATA_DIR environment variable
wasn’t enough, I had to pass it to the JBoss run.bat starter
as:
run.bat -DGEOSERVER_DATA_DIR=xxxx
in order to make it see it…

Cheers
Andrea

Andrea_Aime3 · October 30, 2007, 1:26pm

Andy Dale ha scritto:

Hi,

I have just attempted to deploy GeoServer-1.6-BETA4 as a war archive within JBoss-4.0.5 and it deploys ok.

When i deploy it without the any data dir specified it defaults to the tmp dir of the JBoss server, which is what I expected, and i also get 2 non fatal exceptions (log4j exception and a NPE when attempting to load the plugins).

The second one is addressed already, the first one I can't do anything
about it (but it's not fatal)

I then copied the contents of the data directory to somewhere on my local HD and the restarted JBoss point to the copy location as the property GEOSERVER_DATA_DIR. On restart it again deploys fine, but there seems to now be some more new non-fatal exceptions being thrown like below:

30 Oct 10:02:26 DEBUG [org.geotools.data.property] - can't process parameters
java.io.IOException: Parameter directory is required:Directory containting property files
        at org.geotools.data.DataStoreFactorySpi$Param.lookUp (DataStoreFactorySpi.java:392)
        at org.geotools.data.property.PropertyDataStoreFactory.directoryLookup(PropertyDataStoreFactory.java:187)
        at org.geotools.data.property.PropertyDataStoreFactory.canProcess (PropertyDataStoreFactory.java:156)
        at org.geotools.data.DataStoreFinder.getDataStore(DataStoreFinder.java:90)
        at org.vfny.geoserver.util.DataStoreUtils.getDataStore(DataStoreUtils.java:62)
        at org.vfny.geoserver.global.DataStoreInfo.getDataStore(DataStoreInfo.java:207)
        at org.vfny.geoserver.global.Data.loadFeatureTypes(Data.java:552)
        at org.vfny.geoserver.global.Data.load(Data.java:233)
        at org.vfny.geoserver.global.Data.<init>(Data.java:176)
        at org.vfny.geoserver.global.Data.<init>(Data.java:186)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)

        at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
        at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:100)
        at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate (SimpleInstantiationStrategy.java:75)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:669)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean (AbstractAutowireCapableBeanFactory.java:329)
        at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:226)
        at org.springframework.beans.factory.support.AbstractBeanFactory.getBean (AbstractBeanFactory.java:147)
        at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:176)
        at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary (BeanDefinitionValueResolver.java:105)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.resolveConstructor

Is the above exception with the parameters a know problem, and does anyone know how to resolve this problem ?

Nah, it's just the property data store being too chatty + you having
debug level logging activated. I'd suggest you use default or production
logging unless you really need that level of info because such a detailed logging will slow down geoserver significantly.

Cheers
Andrea

Andy_Dale · October 30, 2007, 1:56pm

Thanks for the tip about the logging, it does seem to be running a bit fast with the logging turned down to a sensible level. I have seen the first error/exception before with an old version of a webapp, and I think the solution was to not pack the log4j.jar file in WEB-INF/libs, i willl have to experiment with this.

Cheers,

Andy

On 30/10/2007, Andrea Aime < aaime@anonymised.com> wrote:

Andy Dale ha scritto:

Hi,

I have just attempted to deploy GeoServer-1.6-BETA4 as a war archive
within JBoss-4.0.5 and it deploys ok.

When i deploy it without the any data dir specified it defaults to the
tmp dir of the JBoss server, which is what I expected, and i also get 2
non fatal exceptions (log4j exception and a NPE when attempting to load
the plugins).

The second one is addressed already, the first one I can’t do anything
about it (but it’s not fatal)

I then copied the contents of the data directory to somewhere on my
local HD and the restarted JBoss point to the copy location as the
property GEOSERVER_DATA_DIR. On restart it again deploys fine, but
there seems to now be some more new non-fatal exceptions being thrown
like below:

30 Oct 10:02:26 DEBUG [org.geotools.data.property] - can’t process
parameters
java.io.IOException : Parameter directory is required:Directory
containting property files
at org.geotools.data.DataStoreFactorySpi$Param.lookUp
(DataStoreFactorySpi.java:392)
at
org.geotools.data.property.PropertyDataStoreFactory.directoryLookup (PropertyDataStoreFactory.java:187)
at
org.geotools.data.property.PropertyDataStoreFactory.canProcess
(PropertyDataStoreFactory.java:156)
at
org.geotools.data.DataStoreFinder.getDataStore (DataStoreFinder.java:90)
at
org.vfny.geoserver.util.DataStoreUtils.getDataStore(DataStoreUtils.java:62)
at
org.vfny.geoserver.global.DataStoreInfo.getDataStore(DataStoreInfo.java :207)
at org.vfny.geoserver.global.Data.loadFeatureTypes(Data.java:552)
at org.vfny.geoserver.global.Data.load(Data.java:233)
at org.vfny.geoserver.global.Data.( Data.java:176)
at org.vfny.geoserver.global.Data.(Data.java:186)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance (NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)

at java.lang.reflect.Constructor.newInstance (Constructor.java:494)
at
org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:100)
at
org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate
(SimpleInstantiationStrategy.java:75)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:669)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean
(AbstractAutowireCapableBeanFactory.java:329)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean (AbstractBeanFactory.java:226)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean
(AbstractBeanFactory.java:147)
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference (BeanDefinitionValueResolver.java:176)
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary
(BeanDefinitionValueResolver.java:105)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.resolveConstructor

Is the above exception with the parameters a know problem, and does
anyone know how to resolve this problem ?

Nah, it’s just the property data store being too chatty + you having
debug level logging activated. I’d suggest you use default or production
logging unless you really need that level of info because such a
detailed logging will slow down geoserver significantly.

Cheers
Andrea

Andrea_Aime3 · October 30, 2007, 2:04pm

Andy Dale ha scritto:

Thanks for the tip about the logging, it does seem to be running a bit fast with the logging turned down to a sensible level. I have seen the first error/exception before with an old version of a webapp, and I think the solution was to not pack the log4j.jar file in WEB-INF/libs, i willl have to experiment with this.

If you do that you won't be able to change the log levels from the UI anymore and you'll fall back on java loggging and its system wide
configuration file (located somewhere in the jdk install).

Cheers
Andrea