activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino (JIRA)" <>
Subject [jira] Resolved: (AMQ-647) Openwire client hangs after receiving some hundred messages
Date Mon, 12 Jun 2006 20:25:51 GMT
     [ ]
Hiram Chirino resolved AMQ-647:

    Resolution: Duplicate

This looks like a duplicate of issue AMQ-721

> Openwire client hangs after receiving some hundred messages
> -----------------------------------------------------------
>          Key: AMQ-647
>          URL:
>      Project: ActiveMQ
>         Type: Bug

>   Components: JMS client
>     Versions: 4.0
>  Environment: * Broker version activemq-4.0-SNAPSHOT dated 03-21-06
> * OS : Solaris SunOS 5.10 Generic 118822-30 (SunFire-V210) for the broker
> * WinXP SP1 for the Openwire client on .NET Framework 1.1 (openwire version 387473)
>     Reporter: Laurent Jeanneau
>     Priority: Critical

> I'm currently testing the openwire .NET JMS implementation to communicate with a activemq
java broker ; the aim of this test is to evaluate the possibilty to deploy the solution in
live environment.
> My test platform is quite simple :
> * A java JMS publisher publishes 100messages / 1s on a test topic
> * A java consumer is listening to this topic
> * A openwire consumer listens to the same topic
> After a few hundreds messages (about 10-20 seconds of publish), the openwire client hangs
and receives no more message. Using the Visual Studio debugger, it appears that the client
is waiting on a "read" from the socket. The side effect of this is that after a few more seconds,
the publisher itself stops to emit messages as if some internal queue becomes full or someting.
> I'm fully aware that Openwire is always in a development process but I want to point
out that this issue already existed in the previous versions I had tested. This problem prevents
using the openwire implementation in a live environment in the current state.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message