This week's book giveaway is in the Servlets forum.
We're giving away four copies of Murach's Java Servlets and JSP and have Joel Murach on-line!
See this thread for details.
The moose likes JBoss/WildFly and the fly likes Really AMAZING Problem with Jboss Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Products » JBoss/WildFly
Bookmark "Really AMAZING Problem with Jboss" Watch "Really AMAZING Problem with Jboss" New topic
Author

Really AMAZING Problem with Jboss

Anurag Mishra
Ranch Hand

Joined: Sep 27, 2001
Posts: 133
Hi Guys!!!
This is one of the very amazing problem i am facing right now, I am Config. my external Context in Jboss TO ACCESS resources from Weblogic-6.1 Server.

Entries in jboss-service.xml file
--------------------------------------------------------------------------

<mbean code="org.jboss.naming.ExternalContext"
name="jboss.jndi:service=ExternalContext, JndiName=external/WLSContext">
<attribute name="JndiName">external/WLSContext</attribute>
<!--attribute name="InitialContext">weblogic.jndi.internal.WLInternalContext</attribute-->
<attribute name="InitialContext">javax.naming.InitialContext</attribute>
<attribute name="Properties">wlsjndi.properties</attribute>
<attribute name="RemoteAccess">false</attribute>
</mbean>

------------------------------------------------------------------

After Running my Jboss-3.2.5 server i am getting the following exception, Do anyone have any idea.

-----------------------------------------------------------------------
19:45:35,148 INFO [Server] Core system initialized
19:45:40,054 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resour
ce:log4j.xml
19:45:50,601 ERROR [ExternalContext] Starting failed jboss.jndi:service=External
Context, JndiName=external/WLSContext
javax.naming.CommunicationException: Receive timed out. Root exception is
java.io.InterruptedIOException: Receive timed out
at java.net.PlainDatagramSocketImpl.receive(Native Method)
at java.net.DatagramSocket.receive(DatagramSocket.java:387)
at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:10
89)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1227)
at org.jnp.interfaces.NamingContext.createSubcontext(NamingContext.java:
845)
at org.jnp.interfaces.NamingContext.createSubcontext(NamingContext.java:
835)
at javax.naming.InitialContext.createSubcontext(InitialContext.java:411)

at org.jboss.naming.ExternalContext.createContext(ExternalContext.java:2
43)
at org.jboss.naming.ExternalContext.rebind(ExternalContext.java:273)
at org.jboss.naming.ExternalContext.startService(ExternalContext.java:21
6)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
upport.java:271)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
eanSupport.java:221)
at java.lang.reflect.Method.invoke(Native Method)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.
java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:185)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
ler.java:837)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:367)
at java.lang.reflect.Method.invoke(Native Method)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.
java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:185)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:251)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:836)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:645)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:608)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:592)
at java.lang.reflect.Method.invoke(Native Method)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.
java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:185)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:407)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:311)
at org.jboss.Main.boot(Main.java:145)
at org.jboss.Main$1.run(Main.java:399)
at java.lang.Thread.run(Thread.java:479)
19:45:50,726 WARN [ServiceController] Problem starting service jboss.jndi:servi
ce=ExternalContext, JndiName=external/WLSContext
MBeanException: javax.naming.CommunicationException: Receive timed out [Root exc
eption is java.io.InterruptedIOException: Receive timed out]
Cause: javax.naming.CommunicationException: Receive timed out [Root exception is
java.io.InterruptedIOException: Receive timed out]
at org.jboss.mx.server.ReflectedDispatcher.handleInvocationExceptions(Re
flectedDispatcher.java:91)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.
java:64)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:185)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
ler.java:837)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:367)
at java.lang.reflect.Method.invoke(Native Method)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.
java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.

Regards

Anurag
soundar rajan
Greenhorn

Joined: May 08, 2013
Posts: 16
This issue has been resolved by adding fscontext.jar into /jboss/production/lib folder.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
 
subject: Really AMAZING Problem with Jboss
 
Similar Threads
unable to configure JMS queue on mySQL DB
migration from MS sql 2000 to MS sql 2008
JasperException: File "/WEB-INF/struts-bean.tld" not found
Twist on server/packaged library problem - Jboss/Packaging
JBoss Running Exception in Eclipse IDE