WL6.1 Assertion error when closing QueueReceiver

[Alain Rogister]

Hi,

We have a problem on WL6.1 with an application that used to work fine on WL
6.0 SP2. We have a JMS queue in the server, and a client process connects to
this queue. The application works fine, i.e. the client can both send and
receive messages on the queue without any problem. However, when the client
disconnects through the following bit of code:

public void stop() throws TransportException {
synchronized (jmsSync) {
try {
receiver.close();
session.close();
connection.close();
} catch (Exception e) {
throw new TransportException(e);
}
}
}

WL throws an AssertionError - see full trace below.

weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Assertion
violated ]
at weblogic.utils.Debug.assert(Debug.java:74)
at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:107)
at
weblogic.rjvm.MsgAbbrevInputStream.readClassDescriptor(MsgAbbrevInputStream.
java:211)
at
weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectIn
putStream.java:83)
at
weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectIn
putStream.java:115)
at weblogic.rmi.internal.ObjectIO.readObject(ObjectIO.java:56)
at
weblogic.rmi.internal.BasicRemoteRef.unmarshalReturn(BasicRemoteRef.java:230
)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:134)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy2.dispatchSyncNoTranFuture(Unknown Source)
at
weblogic.jms.dispatcher.DispatcherWrapperState.dispatchSyncNoTran(Dispatcher
WrapperState.java:341)
at weblogic.jms.client.JMSSession.consumerClose(JMSSession.java:1331)
at weblogic.jms.client.JMSConsumer.close(JMSConsumer.java:329)
at ubiquity.dc.JMSComputer.stop(JMSComputer.java:112)
at ubiquity.rapids.matlab.Engine.stop(Engine.java:57)
at ubiquity.rapids.matlab.Engine.stopApplication(Engine.java:371)
--------------- nested within: ------------------
weblogic.rmi.extensions.RemoteRuntimeException - with nested exception:
[weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Assertion
violated ]]
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:60)
at $Proxy2.dispatchSyncNoTranFuture(Unknown Source)
at
weblogic.jms.dispatcher.DispatcherWrapperState.dispatchSyncNoTran(Dispatcher
WrapperState.java:341)
at weblogic.jms.client.JMSSession.consumerClose(JMSSession.java:1331)
at weblogic.jms.client.JMSConsumer.close(JMSConsumer.java:329)
at ubiquity.dc.JMSComputer.stop(JMSComputer.java:112)
at ubiquity.rapids.matlab.Engine.stop(Engine.java:57)
at ubiquity.rapids.matlab.Engine.stopApplication(Engine.java:371)

Thanks,

Alain.
---
Alain Rogister
http://www.ubiquity.be

[Zach]

This appears to a be a problem with class loaders and/or RMI,
that is to say it is not a JMS Problem. Specifically, the assertion
is ensuring that the thread has a class loader - and your thread does
not. The same check was in place for 6.0 so I am not sure why it
fails now on 6.1

Please post this in the rmi-iiop newsgroup.
_sjz.

"Alain Rogister" <a...@ubiquity.be> wrote in message
news:3b72...@newsgroups.bea.com...