Error When Starting jboss-4.0.3RC2

[mduffy_lists]

I just downloaded RC2.

Stuff that worked in RC1, no longer works. Very frustrating.

Here is one of the errors I now get on startup:

javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out]
at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1302)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1431)
at org.jnp.interfaces.NamingContext.bind(NamingContext.java:523)
at org.jnp.interfaces.NamingContext.bind(NamingContext.java:516)
at javax.naming.InitialContext.bind(InitialContext.java:359)
at org.jboss.naming.Util.bind(Util.java:85)
at org.jboss.naming.Util.bind(Util.java:72)
at org.jboss.naming.LinkRefPairService.startService(LinkRefPairService.java:89)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:287)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:236)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:974)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:453)
at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy4.start(Unknown Source)

Thx.

Mike

[mduffy_lists]

If I install JBoss RC2 by using the installer and then try to start the server (without installing my web app) I get the error detailed in my previous post.

I am runnning on RH Linux 9.0.

Thx.

Mike

[mduffy_lists]

Has anyone been able to get RC2 up and running without an error message?

Thx.

Mike

[goeh]

No, my RC2 windows installation gives me errors to.
But it works for me since I'm not doing any JMS stuff (yet). So I haven't bothered to find out whats wrong.

--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.jms:alias=QueueConnectionFactory
 State: FAILED
 Reason: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out]

ObjectName: jboss.jms:alias=TopicConnectionFactory
 State: FAILED
 Reason: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out]

[pabry]

I also have this problem. The same trace as above.

Furthermore I can't deploy my application that worked on RC1. I get a
java.lang.NullPointerException
at org.hibernate.mapping.UniqueKey.sqlConstraintString(UniqueKey.java:20)

Perhaps this has to to with the timeout exception... Anyway it's very frustrating!

/Patrik

[huber]

I also had the same troubles (with same error trace as in the first posting to this issue) when using the graphical installer.

But then I tried out installing RC2 in the convential way:
download jboss-4.0.3RC2.zip and jboss-EJB_3.0_RC1.zip separately and following the installation instruction as described in http://docs.jboss.org/ejb3/app-server/tutorial/installing.html

Doing it in the convential way all worked fine.
Maybe you can try the same

Johannes

[boga.alexa]

Hello,

I've encountered too the error related to [ServiceController] Problem starting service jboss.jms:alias=QueueConnectionFactory and a believe one answer can be found at:

http://wiki.jboss.org/wiki/Wiki.jsp?page=UsingJBossBehindAFirewall

Alex,
Have fun.

[boga.alexa]

Hello,

If you do not deal with jms service you can rename
...\jboss-4.0.3RC2\server\default\deploy\jms\uil2-service.xml

something like

...\jboss-4.0.3RC2\server\default\deploy\jms\uil2-service_.xml

and the error will show no more.

Alex.

Have fun.

[gemig]

The problem seems to have disappeared when I:
- installed 4.0.3 RC2, non-installer version
- installed JBoss EJB3, RC2 according to http://docs.jboss.com/ejb3/app-server/tutorial/installing.html