JMSException: Error sending message

[Uri]

Hi,

I'm facing a strage problem with WebLogic JMS: When my application starts, it
sends some messages. After a while, one of the messages fails to be sent, and
my exception listener is called. When the application restarts the connection,
it continues to work properly, and the exception does'nt happen again.

When I'm sending the message I get this:
eblogic.jms.common.JMSException: Error sending message
at weblogic.jms.client.JMSProducer.sendMessage(JMSProducer.java:279)
at weblogic.jms.client.JMSProducer.publish(JMSProducer.java:125)
at com.niragongo.infra.notifier.NotifierConnection.sendEvent(NotifierConnection.java:250)
...
----------- Linked Exception -----------
java.io.InterruptedIOException
at weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:85)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:135)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy68.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.publish(JMSProducer.java:125)
at com.niragongo.infra.notifier.NotifierConnection.sendEvent(NotifierConnection.java:250)
...
--------------- nested within: ------------------
weblogic.rmi.extensions.RemoteRuntimeException - with nested exception:
[java.io.InterruptedIOException]
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:60)
at $Proxy68.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.publish(JMSProducer.java:125)
at com.niragongo.infra.notifier.NotifierConnection.sendEvent(NotifierConnection.java:250)
...

Immedialtly later, my Exception listener is called with this Exception:

weblogic.jms.common.LostServerException: weblogic.rjvm.PeerGoneEvent[source=weblogic.rjvm.RJVMImpl@2b1778
- id: '5068253506240389762S:10.99.10.101:[5500,5500,5501,5501,5500,5501,-1]:niragongo:adminServer'
connect time: 'Wed Aug 14 18:37:41 IDT 2002'] - id: '5068253506240389762S:10.99.10.101:[5500,5500,5501,5501,5500,5501,-1]:niragongo:adminServer',
reason: 'java.io.InterruptedIOException'
at weblogic.jms.client.JMSConnection.jmsPeerGone(JMSConnection.java:654)
at weblogic.jms.dispatcher.DispatcherWrapperState.peerGone(DispatcherWrapperState.java:435)
at weblogic.rjvm.RJVMImpl$PeerGoneDeliverer.execute(RJVMImpl.java:1049)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)


I'm Using WebLogic 6.1sp2 on Solaris 8, and it seems to be happening on WebLogic
7 as well.

Any ideas?

Thanks,
Uri

[Zach]

RMI is telling JMS that it could not complete a request and JMS reports that
back. The code beneath RMI is then telling JMS that the connection is lost.
JMS has no recourse. It propagates the exception up the stack.

_sjz.

"Uri" <ey...@iname.com> wrote in message news:3d5a...@newsgroups.bea.com...

[Uri]

Zach,

That sounds reasonable. What can I do to stop it from happening? It happens
every time I start a server, after 3 or 4 messages have been sent successfuly.
The network connection between the servers stays up the whole time.

Uri

"Zach" <nos...@bea.com> wrote:
>RMI is telling JMS that it could not complete a request and JMS reports
>that
>back. The code beneath RMI is then telling JMS that the connection is
>lost.
>JMS has no recourse. It propagates the exception up the stack.
>
>_sjz.
>
>"Uri" <ey...@iname.com> wrote in message news:3d5a...@newsgroups.bea.com...
>>
>> Hi,
>>
>> I'm facing a strage problem with WebLogic JMS: When my application
>starts, it
>> sends some messages. After a while, one of the messages fails to be
>sent,
>and
>> my exception listener is called. When the application restarts the
>connection,
>> it continues to work properly, and the exception does'nt happen again.
>>
>> When I'm sending the message I get this:
>> eblogic.jms.common.JMSException: Error sending message
>> at weblogic.jms.client.JMSProducer.sendMessage(JMSProducer.java:279)
>> at weblogic.jms.client.JMSProducer.publish(JMSProducer.java:125)
>> at
>com.niragongo.infra.notifier.NotifierConnection.sendEvent(NotifierConnection

>..java:250)

>> ...
>> ----------- Linked Exception -----------
>> java.io.InterruptedIOException
>> at
>weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.
>java:85)
>> at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:135)
>> at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
>> at $Proxy68.dispatchSyncNoTranFuture(Unknown Source)
>> at
>weblogic.jms.dispatcher.DispatcherWrapperState.dispatchSyncNoTran(Dispatcher
>WrapperState.java:341)
>> at weblogic.jms.client.JMSProducer.sendMessage(JMSProducer.java:269)
>> at weblogic.jms.client.JMSProducer.publish(JMSProducer.java:125)
>> at
>com.niragongo.infra.notifier.NotifierConnection.sendEvent(NotifierConnection

>..java:250)

>> ...
>> --------------- nested within: ------------------
>> weblogic.rmi.extensions.RemoteRuntimeException - with nested exception:
>> [java.io.InterruptedIOException]
>> at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:60)
>> at $Proxy68.dispatchSyncNoTranFuture(Unknown Source)
>> at
>weblogic.jms.dispatcher.DispatcherWrapperState.dispatchSyncNoTran(Dispatcher
>WrapperState.java:341)
>> at weblogic.jms.client.JMSProducer.sendMessage(JMSProducer.java:269)
>> at weblogic.jms.client.JMSProducer.publish(JMSProducer.java:125)
>> at
>com.niragongo.infra.notifier.NotifierConnection.sendEvent(NotifierConnection

>..java:250)

[Zach]

I would post this in another newsgroup. Possibly the cluster newsgroup.
The short of it is that the underlying layers of WebLogic are lying to JMS
about the viability of the connection.

_sjz.

"Uri" <nos...@niragongo.com> wrote in message
news:3d5b5094$1...@newsgroups.bea.com...