9:43 a.m.
My JMS client fails to connect with the following stack trace:
[ERROR]@[01 Apr 2008 08:53:33,802] [org.twia.jms.JMSProxy] : connectToJMS() - Exception
occured:
org.jboss.jms.exception.MessagingJMSException: Failed to invoke
at
org.jboss.jms.client.delegate.DelegateSupport.handleThrowable(DelegateSupport.java:271)
at
org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:187)
at
org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
at
org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:83)
at
org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect0.invoke(StateCreationAspect0.java)
at
org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
at
org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java)
at
org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:205)
at
org.jboss.jms.client.JBossConnectionFactory.createConnection(JBossConnectionFactory.java:87)
at
org.jboss.jms.client.JBossConnectionFactory.createConnection(JBossConnectionFactory.java:82)
at org.twia.jms.JMSProxy.connectToJMS(JMSProxy.java:453)
at org.twia.jms.JMSProxy.(JMSProxy.java:70)
at org.twia.jms.JMSProxy.getInstance(JMSProxy.java:64)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.jnbridge.jnbcore.JNBDispatcher.objectStaticCall(Unknown Source)
at com.jnbridge.jnbcore.JNBDispatcher.call(Unknown Source)
at com.jnbridge.jnbcore.server.sharedmem.SharedMemRequestHandler.a(Unknown Source)
at com.jnbridge.jnbcore.server.sharedmem.SharedMemRequestHandler.handleRequest(Unknown
Source)
Caused by: java.lang.RuntimeException: Error setting up client lease upon performing
connect.
at org.jboss.remoting.Client.connect(Client.java:1529)
at org.jboss.remoting.Client.connect(Client.java:462)
at
org.jboss.jms.client.remoting.JMSRemotingConnection$1.run(JMSRemotingConnection.java:319)
at java.security.AccessController.doPrivileged(Native Method)
at
org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:315)
at
org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:154)
... 19 more
Caused by: java.lang.Exception: Error setting up client lease
at
org.jboss.remoting.MicroRemoteClientInvoker.establishLease(MicroRemoteClientInvoker.java:405)
at org.jboss.remoting.Client.setupClientLease(Client.java:1625)
at org.jboss.remoting.Client.connect(Client.java:1525)
... 24 more
Caused by: org.jboss.remoting.marshal.InvalidMarshallingResource: Can not find a valid
marshaller for data type: jms
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:79)
at
org.jboss.remoting.MicroRemoteClientInvoker.establishLease(MicroRemoteClientInvoker.java:373)
... 26 more
My environment includes the following:
JBoss 4.2.2 with patched JBM 1.4.0 SP3
Single node, no clustering/failover
Standalone JMS client
Java 1.5.0_06 (client and server)
Client and Server classpaths include the following:
jboss-messaging-client.jar (1.4.0 SP3)
jboss-remoting.jar (2.2.2 SP4)
jboss-aop-jdk50.jar (1.5.6 GA from Jboss 4.2.2)
trove.jar (? from Jboss 4.2.2)
javassist.jar (3.6.0 GA from Jboss 4.2.2)
Client code that fails:
private void connectToJMS()
{
// Check to see if already connected
if (JMSProxy.connected == true)
return;
try
{
// Use jndi.properties for configuration
jndi = new InitialContext();
// Log the JNDI properties
if (log.isDebugEnabled())
{
Hashtable props = jndi.getEnvironment();
Enumeration keys = props.keys();
log.debug("JNDI properties:");
log.debug("----------------");
while (keys.hasMoreElements())
{
Object key = keys.nextElement();
log.debug(key.toString() + "=" + props.get(key));
}
log.debug("----------------");
}
// Get a JMS Connection
ConnectionFactory cf = getConnectionFactory();
connection = cf.createConnection(); // <-------------FAILS HERE!!
connection.start();
connected = true;
if (log.isDebugEnabled())
log.debug("connectToJMS() - connected");
}
catch (Exception e)
{
JMSProxy.connected = false;
log.error("connectToJMS() - Exception occured:", e);
}
}
I have successfully run the JBM 1.4.0 queue example against another config so I'm
wondering if this is a server-side configuration issue.
Anyone have any ideas?
Thanks.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4140552#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...