File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes JBoss/WildFly and the fly likes Strange JBoss start behaviour Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of OCA/OCP Java SE 7 Programmer I & II Study Guide this week in the OCPJP forum!
JavaRanch » Java Forums » Products » JBoss/WildFly
Bookmark "Strange JBoss start behaviour" Watch "Strange JBoss start behaviour" New topic
Author

Strange JBoss start behaviour

sumit murarka
Greenhorn

Joined: Oct 06, 2004
Posts: 3
When I start jboss on my laptop at office, it starts fine with no errors but when I start jboss on the same laptop at home, I get the following error.


2006-06-17 19:18:29,271 WARN [org.jboss.mq.il.uil2.UILServerILService] Failed to setup client connection
java.net.SocketException: socket closed
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
at java.net.ServerSocket.implAccept(ServerSocket.java:450)
at java.net.ServerSocket.accept(ServerSocket.java:421)
at org.jboss.mq.il.uil2.UILServerILService.run(UILServerILService.java:123)
at java.lang.Thread.run(Thread.java:595)
2006-06-17 19:18:29,291 ERROR [org.apache.commons.logging.impl.Log4JLogger] Error while setting up connection to durable topic topic/EmailMessages
2006-06-17 19:18:29,291 INFO [STDOUT] javax.naming.NameNotFoundException: ejb not bound
2006-06-17 19:18:29,291 INFO [STDOUT] at org.jnp.server.NamingServer.getBinding(NamingServer.java:491)
2006-06-17 19:18:29,291 INFO [STDOUT] at org.jnp.server.NamingServer.getBinding(NamingServer.java:499)
2006-06-17 19:18:29,291 INFO [STDOUT] at org.jnp.server.NamingServer.getObject(NamingServer.java:505)
2006-06-17 19:18:29,291 INFO [STDOUT] at org.jnp.server.NamingServer.lookup(NamingServer.java:249)
2006-06-17 19:18:29,291 INFO [STDOUT] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:544)
2006-06-17 19:18:29,291 INFO [STDOUT] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:520)
2006-06-17 19:18:29,301 INFO [STDOUT] at javax.naming.InitialContext.lookup(InitialContext.java:351)
2006-06-17 19:18:29,301 INFO [STDOUT] at com.wfsc.pki.cms.common.dataaccess.EJBDataAccessManager.getLocalInterface(EJBDataAccessManager.java:291)
2006-06-17 19:18:29,301 INFO [STDOUT] at com.wfsc.pki.cms.common.dataaccess.EJBDataAccessManager.insertRow(EJBDataAccessManager.java:57)
2006-06-17 19:18:29,301 INFO [STDOUT] at com.wfsc.pki.cms.common.dataaccess.DataAccessManager.insertRow(DataAccessManager.java:81)
2006-06-17 19:18:29,301 INFO [STDOUT] at com.wfsc.pki.cms.common.log.CMSDBLogger.storeToDB(CMSDBLogger.java:244)
2006-06-17 19:18:29,301 INFO [STDOUT] at com.wfsc.pki.cms.common.log.CMSDBLogger.logException(CMSDBLogger.java:180)
2006-06-17 19:18:29,301 INFO [STDOUT] at com.wfsc.pki.cms.common.jms.JMSMessageProducer.(JMSMessageProducer.java:29)
2006-06-17 19:18:29,301 INFO [STDOUT] at com.wfsc.pki.cms.services.main.AbstractServices.startService(AbstractServices.java:61)
2006-06-17 19:18:29,301 INFO [STDOUT] at com.wfsc.pki.cms.services.smtp.SMTPListMailerJMX.startService(SMTPListMailerJMX.java:105)
2006-06-17 19:18:29,301 INFO [STDOUT] at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
2006-06-17 19:18:29,301 INFO [STDOUT] at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
2006-06-17 19:18:29,301 INFO [STDOUT] at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
2006-06-17 19:18:29,301 INFO [STDOUT] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
2006-06-17 19:18:29,301 INFO [STDOUT] at java.lang.reflect.Method.invoke(Method.java:585)
2006-06-17 19:18:29,301 INFO [STDOUT] at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
2006-06-17 19:18:29,301 INFO [STDOUT] at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
2006-06-17 19:18:29,301 INFO [STDOUT] at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
2006-06-17 19:18:29,301 INFO [STDOUT] at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
2006-06-17 19:18:29,301 INFO [STDOUT] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
2006-06-17 19:18:29,301 INFO [STDOUT] at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
2006-06-17 19:18:29,301 INFO [STDOUT] at $Proxy0.start(Unknown Source)
2006-06-17 19:18:29,301 INFO [STDOUT] at org.jboss.system.ServiceController.start(ServiceController.java:416)
2006-06-17 19:18:29,301 INFO [STDOUT] at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
2006-06-17 19:18:29,301 INFO [STDOUT] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
2006-06-17 19:18:29,301 INFO [STDOUT] at java.lang.reflect.Method.invoke(Method.java:585)
2006-06-17 19:18:29,301 INFO [STDOUT] at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
2006-06-17 19:18:29,301 INFO [STDOUT] at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
2006-06-17 19:18:29,301 INFO [STDOUT] at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
2006-06-17 19:18:29,301 INFO [STDOUT] at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
2006-06-17 19:18:29,301 INFO [STDOUT] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
2006-06-17 19:18:29,301 INFO [STDOUT] at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
2006-06-17 19:18:29,301 INFO [STDOUT] at $Proxy4.start(Unknown Source)
2006-06-17 19:18:29,301 INFO [STDOUT] at org.jboss.deployment.SARDeployer.start(SARDeployer.java:261)
2006-06-17 19:18:29,301 INFO [STDOUT] at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964)
2006-06-17 19:18:29,301 INFO [STDOUT] at org.jboss.deployment.MainDeployer.start(MainDeployer.java:956)
2006-06-17 19:18:29,301 INFO [STDOUT] at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
2006-06-17 19:18:29,311 INFO [STDOUT] at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
2006-06-17 19:18:29,311 INFO [STDOUT] at sun.reflect.GeneratedMethodAccessor47.invoke(Unknown Source)
2006-06-17 19:18:29,311 INFO [STDOUT] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
2006-06-17 19:18:29,311 INFO [STDOUT] at java.lang.reflect.Method.invoke(Method.java:585)
2006-06-17 19:18:29,311 INFO [STDOUT] at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
Mark Spritzler
ranger
Sheriff

Joined: Feb 05, 2001
Posts: 17258
    
    6

Your JMS is set to use a database that you are no longer connected to. It sounds like at home you aren't connected to your work network, and therefore do not have access to the database that resides there.

Mark


Perfect World Programming, LLC - Two Laptop Bag - Tube Organizer
How to Ask Questions the Smart Way FAQ
sumit murarka
Greenhorn

Joined: Oct 06, 2004
Posts: 3
I connect through the vpn to the work network wherein the DB resides and I have been able to access DB thru TOAD and sqlplus. Do I need to change any jboss configuration?
Mark Spritzler
ranger
Sheriff

Joined: Feb 05, 2001
Posts: 17258
    
    6

Good question. What might be happening is that your VPN only allows access through certain ports, and the SocketCOnnection that it is trying to establish is using a port that is not allowed. This is why they have the HttpTunneling solution for times like these.

Now, I don't know if that is your exact problem.

Mark
 
jQuery in Action, 2nd edition
 
subject: Strange JBoss start behaviour