Hi,
We have installed WmJBoss package on IS (Solaris). The test JMS program that worked perfectly with JBoss 3.2.0 (stand alone) does not seem to work with embedded JBoss.
We have following code segment for getting the JNDI Context
private static Context jndiContext = null;
Properties env = new Properties();
env.put(Context.INITIAL_CONTEXT_FACTORY,“org.jnp.interfaces.NamingContextFactory”);
env.put(Context.PROVIDER_URL,“jnp://172.24.6.29:1099”);
jndiContext = new InitialContext(env);
try{
obj = jndiContext.lookup(name);
} catch (NamingException e) {
System.out.println("JNDI lookup failed: " + e.toString());
throw e;
}
return obj;
On JBoss stand alone we had used the following settings of jbossmq-service.xml
<mbean code=“org.jboss.mq.il.oil.OILServerILService” name=“jboss.mq:service=InvocationLayer,type=OIL”>
<depends optional-attribute-name=“Invoker”>jboss.mq:service=Invoker</depends>
<attribute name=“ConnectionFactoryJNDIRef”>QueueConnectionFactory</attribute>
<attribute name=“XAConnectionFactoryJNDIRef”>XAConnectionFactory</attribute>
<attribute name=“ServerBindPort”>8090</attribute>
<attribute name=“PingPeriod”>60000</attribute>
<attribute name=“EnableTcpNoDelay”>true</attribute>
</mbean>
On JBoss of webMethods, this is commented in jbossmq-service.xml (by webMethods)
<!–
webMethods removed. Make port configuration and startup part of IS listener config.
<mbean code=“org.jboss.mq.il.oil.OILServerILService”
name=“jboss.mq:service=InvocationLayer,type=OIL”>
<depends optional-attribute-name=“Invoker”>jboss.mq:service=Invoker</depends>
<attribute name=“ConnectionFactoryJNDIRef”>ConnectionFactory</attribute>
<attribute name=“XAConnectionFactoryJNDIRef”>XAConnectionFactory</attribute>
<attribute name=“ServerBindPort”>8090</attribute>
<attribute name=“PingPeriod”>60000</attribute>
<attribute name=“EnableTcpNoDelay”>true</attribute>
</mbean>
–>
If so then where to configure the Invoker to get my program working which is currently giving error on lookup throwing java.naming.CommunicationException: Receive timed out.
Hope the info provided helps to pinpoint the problem.
Regards
Ashok