Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Failed in ack message weblogic.jms.common.JMSException: System error: weblogic.

1 view
Skip to first unread message

Bernard

unread,
Feb 4, 2003, 10:45:28 PM2/4/03
to
Hi,

I'm using JNI to allow my C++ client subscribe to messages on a JMS Topic in
WebLogic Server 6.1.
I can subscribe(Session.CLIENT_ACKNOWLEDGE) and receive messages, but when I
try to acknowledge the message, I get the stack trace below. Help?

Thanks,
Bernard

weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Assertion
violated
]
at weblogic.utils.Debug.assert(Debug.java:74)
at
weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:10
7)
at
weblogic.rjvm.MsgAbbrevInputStream.readClassDescriptor(MsgAbbrevInput
Stream.java:211)
at
weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedO
bjectInputStream.java:83)
at
weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedO
bjectInputStream.java:115)
at weblogic.rmi.internal.ObjectIO.readObject(ObjectIO.java:56)
at
weblogic.rmi.internal.BasicRemoteRef.unmarshalReturn(BasicRemoteRef.j
ava: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(Dis
patcherWrapperState.java:341)
at weblogic.jms.client.JMSSession.acknowledge(JMSSession.java:767)
at weblogic.jms.client.JMSSession.acknowledge(JMSSession.java:741)
at weblogic.jms.common.MessageImpl.acknowledge(MessageImpl.java:691)
at JMSConsumer.acknowledgeMessage(JMSConsumer.java:236)
Failed in ack message weblogic.jms.common.JMSException: System error:
weblogic.
rmi.extensions.RemoteRuntimeException - with nested exception:
[weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Assertion
violated
]]


Tom Barnes

unread,
Feb 5, 2003, 10:34:05 AM2/5/03
to Bernard
I suggest filing a case with customer support to trace down the problem.

You may want to upgrade to 7.0, which supports a BEA built JNI C++ JMS
client. This C client is available on dev2dev.bea.com, is supported
via this newsgroup, and is scheduled to be fully integrated into the
WebLogic in the "next next" release (eg the release after 8.1).

Furthermore, you may wish to investigate using a non-JNI proxy pattern -
use an IIOP client to invoke an EJB which in turn encapsulates a JMS
request. Post to the rmi-iiop newsgroup for more info on this
approach.

Tom, BEA

0 new messages