Jdom's Document object creating problem while being send accross using ObjectMessage..

Akhil Nagpal

unread,

Mar 24, 2003, 9:54:52 PM3/24/03

to

HI,
Actually i have created my own class which implements serializable. I set the
object of this class in the ObjectMessage and send it across. Sometime i have
to send some vector,sometimes string and sometime a XML document. So i can set
these type of objects in my custom serializable object and send it. For sending
XML , either i can send it as a string or as u said as Document object. But i
want to do send it as a Document object. So i have created a an object of "org.jdom.Document"
which implement serializable and setting this object into my custom object and
sending this custom object in the objectmessage. But then weblogic throws some
exceptions which has nothing to do with serialization.I am printing the exception
below. (without the object of org.jdom.Document this custom object reaches safely
and happily:))...this exception is something related to transactions.....can anybody
tell me what could be the reason..
I am not able to think why this kind of exception comes only when i try to send
the jdom's Document object and never in other cases..

java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured
in the transaction branch start() failed o
n resource 'oraclePool': XAER_RMERR : A resource manager error has occured in
the transaction branch
oracle.jdbc.xa.OracleXAException
at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:483)
at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:190)
at weblogic.jdbc.jta.VendorXAResource.start(VendorXAResource.java:41)
at weblogic.jdbc.jta.DataSource.start(DataSource.java:569)
at weblogic.transaction.internal.ServerResourceInfo.start(ServerResourceInfo.java:1165)
at weblogic.transaction.internal.ServerResourceInfo.xaStart(ServerResourceInfo.java:1108)
at weblogic.transaction.internal.ServerResourceInfo.enlist(ServerResourceInfo.java:287)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:391)
at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1146)
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1101)
at weblogic.jdbc.jta.Connection.getXAConn(Connection.java:145)
at weblogic.jdbc.jta.Connection.createStatement(Connection.java:204)
at weblogic.jdbc.rmi.internal.ConnectionImpl.createStatement(ConnectionImpl.java:130)
at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:71)
at com.sds.kb.cm.CMMDBReceiver.onMessage(CMMDBReceiver.java:134)
at weblogic.ejb20.internal.MDListener.execute(MDListener.java:356)
at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:290)
at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:271)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2303)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:2226)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)

at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1151)

any help will be appriciated..
Akhil

Akhil Nagpal

unread,

Mar 24, 2003, 10:05:17 PM3/24/03

to

HI All,
Sorry the excepiotn is of deserialization...this is the stack trace...mistake...

weblogic.jms.common.JMSException: Error deserializing object
at weblogic.jms.common.ObjectMessageImpl.getObject(ObjectMessageImpl.java:140)
at com.sds.kb.cm.CMMDBReceiver.onMessage(CMMDBReceiver.java:143)

at weblogic.ejb20.internal.MDListener.execute(MDListener.java:356)
at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:290)
at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:271)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2303)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:2226)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)

----------- Linked Exception -----------
weblogic.jms.common.JMSException: Error deserializing object
at weblogic.jms.common.ObjectMessageImpl.getObject(ObjectMessageImpl.java:140)
at com.sds.kb.cm.CMMDBReceiver.onMessage(CMMDBReceiver.java:143)

at weblogic.ejb20.internal.MDListener.execute(MDListener.java:356)
at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:290)
at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:271)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2303)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:2226)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)

Akhil

Tom Barnes

unread,

Mar 25, 2003, 12:10:08 PM3/25/03

to Akhil Nagpal

Is this the full stack trace?

Zach

unread,

Mar 25, 2003, 3:32:28 PM3/25/03

to

Class loader issue. What version is this?
_sjz.

"Tom Barnes" <ple...@replyinnewsgroup.com> wrote in message
news:3E808D70...@replyinnewsgroup.com...

Akhil Nagpal

unread,

Mar 25, 2003, 10:09:39 PM3/25/03

to

HI Tom and Zach,
Thanks for your replies and u r right it was not a full stack trace..but later
i used the xerces2 implmentation of DOM and could accomplish it.i think i was
not giving the right class of jdom to weblogic ..

Thanks
Akhil Nagpal