StackTrace of JMSException -
weblogic.jms.common.JMSException: Error sending message
at weblogic.jms.client.JMSProducer.sendMessage(JMSProducer.java:279)
at weblogic.jms.client.JMSProducer.send(JMSProducer.java:164)
at testproject.AdapterBeanUnitTest.testAsString(AdapterBeanUnitTest.java:140)
at testproject.AdapterBeanUnitTest.main(AdapterBeanUnitTest.java:66)-----------
Linked Exception -----------
weblogic.rjvm.PeerGoneException: ; nested exception is:
java.io.EOFException
java.io.EOFException
at weblogic.rjvm.t3.T3JVMConnection.endOfStream(T3JVMConnection.java:599)
at weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:303)
at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:225)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.rmi.extensions.RemoteRuntimeException - with nested exception:
[weblogic.rjvm.PeerGoneException: ; nested exception is:
java.io.EOFException]
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:60)
at $Proxy2.dispatchSyncNoTranFuture(Unknown Source)
at weblogic.jms.dispatcher.DispatcherWrapperState.dispatchSyncNoTran(DispatcherWrapperState.java:341)
at weblogic.jms.client.JMSProducer.sendMessage(JMSProducer.java:269)
at weblogic.jms.client.JMSProducer.send(JMSProducer.java:164)
FYI, there is a MaxT3MessageSize and MaxHTTPMessageSize
setting on the server. This defaults to 10000000 which seems to be close
to the boundary you're hitting. If you can't find it on the console, drop the line:
MaxT3MessageSize="20000000"
into your server's section in your config.xml and see what happens.
Tom