activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] Commented: (AMQCPP-314) Starting app with Com using cms destroys connection of other app. New problem with recent lib version
Date Tue, 24 Aug 2010 23:02:48 GMT


Timothy Bish commented on AMQCPP-314:

I updated the code in trunk and in 3.2.x fixes with some additional try/catch blocks in InetAddress,
that's about all I can do without knowing more about what the error is and why its happening.

If it persists then I'd recommend attempting to create a short but complete sample app that
demonstrates the issue and does not require COM knowledge.  

> Starting app with Com using cms destroys connection of other app. New problem with recent
lib version
> -----------------------------------------------------------------------------------------------------
>                 Key: AMQCPP-314
>                 URL:
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>          Components: CMS Impl
>    Affects Versions: 3.2.2
>         Environment: Windows XP, SP 3, ActiveMQ apache-activemq-5.3.1 and/or apache-activemq-5.4.0.
CMS library 3.2.2
>            Reporter: Barbara Dawkins
>            Assignee: Timothy Bish
>            Priority: Critical
>         Attachments: ActiveMQLog_CatcherStart.txt, ActiveMQLog_PitcherStart.txt, ActiveMQLog_SimpleSenderStart.txt,
> We ran into a problem after we upgraded the CMS library from revison 3.1.3 to revision
3.2.2.  We have two applications. When we start up the second application, and try to send
a message to the activemq broker, it seems to wipe out the existing connection that the first
application has. This is a new problem. We have not seen this with the earlier version of
> Here are more details about our applications.
> Both applications are using a COM component that we have created as a thin wrapper around
> Application 1: 
>  The "Catcher" application creates listeners and waits for messages to arrive on two
"request" topics.  When it receives messages, it sends out responses on the appropriate "response"
topic.  This app is intended as a local, dumbed-down similator of a remote server.  The Catcher
app uses only the COM wrapper of CMS.  When the catcher is started, you can see it's listeners
on the "Topics" page.
> Application 2:
> The "SimpleSender" app uses an Additional COM object that loads the CMS wrapper.  SimpleSender
creates listers on the "response" topics and sends messages on the "request" topics.    When
SimpleSender starts,  it loads it's configuration, creates a listener on the response topic,
and sends 1 message.  If you look at the topics page (http://localhost:8161/admin/topics.jsp)
before the message is sent,  the Catcher listeners are undisturbed.  After it sends a message,
 the listeners are destroyed.
> Application 3:
> A simple message sender that only uses the COM wrapper.  It does not destroy Catcher's
connections,  and can be used to test whether Catcher can receive messages.
> I will send an attachment containing the test programs.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message