JBoss Startup Freeze

[D Skiles]

I'm running into some odd behavior when trying to start JBoss using the YAJSW on a 32-bit WinXP system.  I reach the point where it states " Server Home URL:", but then it halts at that point until I kill it.

Has anyone else seen this behavior?  If you haven't, could someone please post an example config file?

[Nobody/Anonymous]

hello,

is this happening when you run it as console or as service ?

• Ron

[D Skiles]

It's happening when I run it as a console app.

java -jar wrapper.jar -c path/to/wrapper.conf

[Nobody/Anonymous]

thanks for the response

i will check this out and get back to you.

• Ron

[Nobody/Anonymous]

hi,

did you generate the conf file using genconfig ?

if yes, there is a bug in the current version.

you should split the property

wrapper.java.additional.1 =

as follows

wrapper.java.additional.1 = -Dprogram.name=run.bat

wrapper.java.additional.2 = -Xms128M

wrapper.java.additional.3 = -Xmx512M

wrapper.java.additional.4 = -XX:MaxPermSize=256M

wrapper.java.additional.5 = -Dsun.rmi.dgc.client.gcInterval=3600000

wrapper.java.additional.6 = -Dsun.rmi.dgc.server.gcInterval=3600000

wrapper.java.additional.7 = -Dorg.jboss.resolver.warning=true

wrapper.java.additional.8 = -Djava.endorsed.dirs=Z:\\dev\\jboss\\jboss-5.1.0.GA\\lib\\endorsed

• Ron

[D Skiles]

Here's my wrapper.java.additional block.  Does anything look out of place?  I just added the endorsed dirs line and it got me one step farther to the line below.

Controller State: ESTABLISHED -> LOGGED_ON

    wrapper.java.additional.1=-server
    wrapper.java.additional.2=-Dprogram.name=run.bat
    wrapper.java.additional.3=-Dsun.rmi.dgc.client.gcInterval=3600000
    wrapper.java.additional.4=-Dsun.rmi.dgc.server.gcInterval=3600000
    wrapper.java.additional.5=-Djavax.xml.transform.TransformerFactory=org.apache.xalan.xsltc.trax.TransformerFactoryImpl
    wrapper.java.additional.6=-Dcom.sun.media.jai.disableMediaLib=true
    wrapper.java.additional.7=-Dorg.apache.cxf.Logger=org.apache.cxf.common.logging.Log4jLogger
    wrapper.java.additional.8=-XX:MaxPermSize=128M
    wrapper.java.additional.9=-XX:+UseParallelGC
    wrapper.java.additional.10=-Dcold2streams.path=COLD
    wrapper.java.additional.11=-Djava.awt.headless=true
    wrapper.java.additional.12=-Dcom.sun.media.jai.disableMediaLib=true
    wrapper.java.additional.13=-Dlogging.home=logs
    wrapper.java.additional.14=-Djava.endorsed.dirs=../lib/endorsed

[Nobody/Anonymous]

LOGGED_ON means that the application is up and has connected to the wrapper. the configuration seems to be ok.

is it now running as expected ?

• ron

[D Skiles]

It's not quite running as expected.  JBoss is up and running, but it isn't actually serving any of the web applications in the server folder.  You can access the root app, but that's it.

[Nobody/Anonymous]

I do not have experience with jboss, so it is diffcult for me to help further. I will look into this and get back to you when I have found something.

• Ron

[Nobody/Anonymous]

one more idea:

try commenting out wrapper.tray, or set it to false.

per default the tray icon is using port 1099, which is also used by jboss.

• Ron

[Nobody/Anonymous]

PS:

alternatively, that is instead of commenting out wrapper.tray, you may set

wrapper.jmx.rmi.port=1999

i just found out that this property is missing in the documentation.

• Ron

[D Skiles]

I didn't use genconfig to build the wrapper.  If those values aren't there, do they default to 1099 and 1999, respectively?

When I try to set wrapper.tray to another value, I receive the following stack trace.  Is that the right property? It seems to be expecting a boolean.

    java.lang.reflect.InvocationTargetException
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
            at java.lang.reflect.Method.invoke(Method.java:623)
            at org.rzo.yajsw.boot.WrapperExeBooter.main(WrapperExeBooter.java:35)
    Caused by: org.apache.commons.configuration.ConversionException: 'wrapper.tray' doesn't map to a Boolean object
            at org.apache.commons.configuration.AbstractConfiguration.getBoolean(AbstractConfiguration.java:698)
            at org.apache.commons.configuration.AbstractConfiguration.getBoolean(AbstractConfiguration.java:667)
            at org.rzo.yajsw.wrapper.AbstractWrappedProcess.init(AbstractWrappedProcess.java:243)
            at org.rzo.yajsw.wrapper.WrappedJavaProcess.init(WrappedJavaProcess.java:53)
            at org.rzo.yajsw.WrapperExe.doConsole(WrapperExe.java:334)
            at org.rzo.yajsw.WrapperExe.executeCommand(WrapperExe.java:155)
            at org.rzo.yajsw.WrapperExe.main(WrapperExe.java:138)
            … 5 more
    Caused by: org.apache.commons.configuration.ConversionException: The value 1456 can't be converted to a Boolean object
            at org.apache.commons.configuration.PropertyConverter.toBoolean(PropertyConverter.java:201)
            at org.apache.commons.configuration.AbstractConfiguration.getBoolean(AbstractConfiguration.java:694)
            … 11 more

[D Skiles]

It works.  I had a configuration error on my end that was preventing the war from deploying.

[Nobody/Anonymous]

hello,

wrapper.tray is required to be boolean.

the suggestion was to :

either

wrapper.tray = false

or

wrapper.jmx.rmi.port=1999

• Ron

[Nobody/Anonymous]

thanks for the information,

i was afraid that there are issues with jboss.

• ron