Multiple servers on one network

[cacantil]

We have multiple developers on the same network trying to run the 3.0 beta or later at the same time. Unfortunately, we have been experiencing the JBOSS server on different hosts hangs up during startup. To fix this, we had to kill servers, leaving only one server running on our network. This is annoying since, we are trying to develop in parallel (and test) our EJBs. I did read from one post-it, that trying to load servers on the same network causes the servers to try and cluster with each other. Is this a clustering problem? How to we fix this???


-Chris

[slaboure]

When upgrading to jboss 3.2.6RC2 the jboss.net module doesn't work anymore. I might be because it is using the new version of axis. When calling a webservice I have the following stack trace:

13:53:58,455 ERROR [Engine] StandardWrapperValve[JBossAxisServlet]: Servlet.service() for servlet JBossAxisServlet threw exception
java.lang.NullPointerException
at org.jboss.net.axis.Deployment.oldGetService(Deployment.java:255)
at org.jboss.net.axis.Deployment.getService(Deployment.java:275)
at org.apache.axis.configuration.FileProvider.getService(FileProvider.java:290)
at org.apache.axis.AxisEngine.getService(AxisEngine.java:302)
at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:900)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:372)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:66)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:158)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:540)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
at java.lang.Thread.run(Thread.java:534)

Any help is welcome.

Regards,

Nicolas Leroux
Software Developer
Lunatech Research

[slaboure]

1°) Don't use beta, use final.
2°) When you use final, by default clustering is disabled so you don't have any problem like this one.

If you *have* to use beta, simply remove cluster-service.xml from server/default/deploy from all jboss instances.

[feroz]

Hi,

I'm facing a similar problem. The servers hang when there are other JBoss 3.0 (final release) servers running in "all" configuration on the network. The problem is that in this case I want to get them to discover each other and cluster together. Can any of you throw some light on why the server is hanging. I'm using NT 4.0 workstations. As such I haven't made any changes to any of the config/deploy files. Is it some kind of network config problem or with JBoss config.

Thanks
Feroz