Duke's Bank Deployment Problem
johnwtn2005 Oct 6, 2005 8:31 PMHello,
I searched back into February but could not find a problem the same as mine. For background, I am running JBoss 4.0.2 on a Win XP machine. I had to change the main port for running JBoss from 8080 to 8180. There seems to be an Oracle service that uses port 8080. I was able to build the application with no errors. However, when I try to deploy, I receive the following error messages:
18:08:24,062 INFO [EjbModule] Deploying CustomerBean
18:08:30,140 INFO [EjbModule] Deploying AccountBean
18:08:36,046 INFO [EjbModule] Deploying TxBean
18:08:41,953 INFO [EjbModule] Deploying NextIdBean
18:08:47,875 INFO [EjbModule] Deploying AccountControllerBean
18:08:53,984 INFO [EjbModule] Deploying CustomerControllerBean
18:09:00,000 INFO [EjbModule] Deploying TxControllerBean
18:09:12,140 ERROR [MainDeployer] could not start deployment: file:/C:/JBoss-4.0
.2/server/default/tmp/deploy/tmp29166JBossDukesBank.ear-contents/app-client.jar
org.jboss.deployment.DeploymentException: Failed to setup client ENC; - nested throwable: (javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out])
at org.jboss.deployment.ClientDeployer.start(ClientDeployer.java:156)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:956)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
at sun.reflect.GeneratedMethodAccessor51.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:121)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:127)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:249)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
at $Proxy8.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen
tScanner.java:325)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS
canner.java:483)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
doScan(AbstractDeploymentScanner.java:204)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
loop(AbstractDeploymentScanner.java:215)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
run(AbstractDeploymentScanner.java:194)
Caused by: javax.naming.CommunicationException: Receive timed out [Root exceptio
n is java.net.SocketTimeoutException: Receive timed out]
at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:13
02)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1382)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:579)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:572)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at org.jboss.naming.Util.createSubcontext(Util.java:52)
at org.jboss.naming.Util.createSubcontext(Util.java:35)
at org.jboss.deployment.ClientDeployer.setupEnvironment(ClientDeployer.j
ava:202)
at org.jboss.deployment.ClientDeployer.start(ClientDeployer.java:152)
... 22 more
Caused by: java.net.SocketTimeoutException: Receive timed out
at java.net.PlainDatagramSocketImpl.receive(Native Method)
at java.net.DatagramSocket.receive(DatagramSocket.java:711)
at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:12
72)
... 30 more
It may be something simple because of the port change but I cannot see it.
Thanks for any help,
John