You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Barbara Dawkins (JIRA)" <ji...@apache.org> on 2010/08/20 00:47:47 UTC

[jira] Created: (AMQCPP-314) Starting app with Com using cms destroys connection of other app. New problem with recent lib version

Starting app with Com using cms destroys connection of other app. New problem with recent lib version
-----------------------------------------------------------------------------------------------------

                 Key: AMQCPP-314
                 URL: https://issues.apache.org/activemq/browse/AMQCPP-314
             Project: ActiveMQ C++ Client
          Issue Type: Bug
    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


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 CMS.

Here are more details about our applications.

Both applications are using a COM component that we have created as a thin wrapper around CMS.
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.


[jira] Commented: (AMQCPP-314) Starting app with Com using cms destroys connection of other app. New problem with recent lib version

Posted by "Barbara Dawkins (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/AMQCPP-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61646#action_61646 ] 

Barbara Dawkins commented on AMQCPP-314:
----------------------------------------

We've tried the changes from the trunk,  it seems to be working fine.  Thanks! 



> Starting app with Com using cms destroys connection of other app. New problem with recent lib version
> -----------------------------------------------------------------------------------------------------
>
>                 Key: AMQCPP-314
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-314
>             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
>             Fix For: 3.2.3, 3.3.0
>
>         Attachments: ActiveMQLog_CatcherStart.txt, ActiveMQLog_PitcherStart.txt, ActiveMQLog_SimpleSenderStart.txt, CatcherPitcherTest2.zip
>
>
> 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 CMS.
> Here are more details about our applications.
> Both applications are using a COM component that we have created as a thin wrapper around CMS.
> 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.


[jira] Updated: (AMQCPP-314) Starting app with Com using cms destroys connection of other app. New problem with recent lib version

Posted by "Barbara Dawkins (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQCPP-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Barbara Dawkins updated AMQCPP-314:
-----------------------------------

    Attachment: ActiveMQLog_CatcherStart.txt
                ActiveMQLog_PitcherStart.txt
                ActiveMQLog_SimpleSenderStart.txt

Three snippets of the ActiveMQ log file.   Catcher and SimpleSender are using the same ID,  and SimpleSender log shows Catcher connection was deliberately closed.  The CMSWrapper here says there is no way to control the ID used.    Is there?

> Starting app with Com using cms destroys connection of other app. New problem with recent lib version
> -----------------------------------------------------------------------------------------------------
>
>                 Key: AMQCPP-314
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-314
>             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, CatcherPitcherTest2.zip
>
>
> 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 CMS.
> Here are more details about our applications.
> Both applications are using a COM component that we have created as a thin wrapper around CMS.
> 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.


[jira] Updated: (AMQCPP-314) Starting app with Com using cms destroys connection of other app. New problem with recent lib version

Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQCPP-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish updated AMQCPP-314:
--------------------------------

    Fix Version/s: 3.2.3
                   3.3.0

> Starting app with Com using cms destroys connection of other app. New problem with recent lib version
> -----------------------------------------------------------------------------------------------------
>
>                 Key: AMQCPP-314
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-314
>             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
>             Fix For: 3.2.3, 3.3.0
>
>         Attachments: ActiveMQLog_CatcherStart.txt, ActiveMQLog_PitcherStart.txt, ActiveMQLog_SimpleSenderStart.txt, CatcherPitcherTest2.zip
>
>
> 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 CMS.
> Here are more details about our applications.
> Both applications are using a COM component that we have created as a thin wrapper around CMS.
> 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.


[jira] Commented: (AMQCPP-314) Starting app with Com using cms destroys connection of other app. New problem with recent lib version

Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/AMQCPP-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61383#action_61383 ] 

Timothy Bish commented on AMQCPP-314:
-------------------------------------

Stepping through the InetAddress::getLocalHost() method with your debugger to ensure its the apr call the throws the exception would be good, then you might be able to inspect that stack to see where the exception comes from.  If the apr call is actually throwing an exception then its most likely there's a bug in the apr code as its not supposed to throw any exceptions according to their docs.  It should be returning APR_SUCCESS or an error code.



> Starting app with Com using cms destroys connection of other app. New problem with recent lib version
> -----------------------------------------------------------------------------------------------------
>
>                 Key: AMQCPP-314
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-314
>             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, CatcherPitcherTest2.zip
>
>
> 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 CMS.
> Here are more details about our applications.
> Both applications are using a COM component that we have created as a thin wrapper around CMS.
> 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.


[jira] Commented: (AMQCPP-314) Starting app with Com using cms destroys connection of other app. New problem with recent lib version

Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/AMQCPP-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61366#action_61366 ] 

Timothy Bish commented on AMQCPP-314:
-------------------------------------

Would need to know what the actual Winsock error is that we are getting from APR.  You could try a later version of APR to see if there's been a fix there for this.



> Starting app with Com using cms destroys connection of other app. New problem with recent lib version
> -----------------------------------------------------------------------------------------------------
>
>                 Key: AMQCPP-314
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-314
>             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, CatcherPitcherTest2.zip
>
>
> 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 CMS.
> Here are more details about our applications.
> Both applications are using a COM component that we have created as a thin wrapper around CMS.
> 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.


[jira] Commented: (AMQCPP-314) Starting app with Com using cms destroys connection of other app. New problem with recent lib version

Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/AMQCPP-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61647#action_61647 ] 

Timothy Bish commented on AMQCPP-314:
-------------------------------------

There is also a fix in the 3.2.x fixes branch which will be the code used in the next release (3.2.3).  Trunk may have unstable code in it as development in trunk adds new features.

> Starting app with Com using cms destroys connection of other app. New problem with recent lib version
> -----------------------------------------------------------------------------------------------------
>
>                 Key: AMQCPP-314
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-314
>             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
>             Fix For: 3.2.3, 3.3.0
>
>         Attachments: ActiveMQLog_CatcherStart.txt, ActiveMQLog_PitcherStart.txt, ActiveMQLog_SimpleSenderStart.txt, CatcherPitcherTest2.zip
>
>
> 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 CMS.
> Here are more details about our applications.
> Both applications are using a COM component that we have created as a thin wrapper around CMS.
> 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.


[jira] Commented: (AMQCPP-314) Starting app with Com using cms destroys connection of other app. New problem with recent lib version

Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/AMQCPP-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61387#action_61387 ] 

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: https://issues.apache.org/activemq/browse/AMQCPP-314
>             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, CatcherPitcherTest2.zip
>
>
> 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 CMS.
> Here are more details about our applications.
> Both applications are using a COM component that we have created as a thin wrapper around CMS.
> 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.


[jira] Commented: (AMQCPP-314) Starting app with Com using cms destroys connection of other app. New problem with recent lib version

Posted by "Barbara Dawkins (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/AMQCPP-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61384#action_61384 ] 

Barbara Dawkins commented on AMQCPP-314:
----------------------------------------

Again,  from my notes in the incident.  This is the stack track immediately before the debug abruptly exits back to the ActiveMQ::ActiveMQConnection constructor.  I took the stack trace immediately before apr_gethostname called Winsock's gethostname.
(I've tried putting a try/catch around the statement,  I still go back to ActiveMQConnection's constructor.  This is very weird.)
One I hit F10 or F11 to try and step through the gethostname,  I'm back at ActiveMQConnnection. 



> Starting app with Com using cms destroys connection of other app. New problem with recent lib version
> -----------------------------------------------------------------------------------------------------
>
>                 Key: AMQCPP-314
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-314
>             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, CatcherPitcherTest2.zip
>
>
> 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 CMS.
> Here are more details about our applications.
> Both applications are using a COM component that we have created as a thin wrapper around CMS.
> 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.


[jira] Resolved: (AMQCPP-314) Starting app with Com using cms destroys connection of other app. New problem with recent lib version

Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQCPP-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish resolved AMQCPP-314.
---------------------------------

    Resolution: Fixed

Fixed in trunk and 3.2 fixes branch.

> Starting app with Com using cms destroys connection of other app. New problem with recent lib version
> -----------------------------------------------------------------------------------------------------
>
>                 Key: AMQCPP-314
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-314
>             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
>             Fix For: 3.2.3, 3.3.0
>
>         Attachments: ActiveMQLog_CatcherStart.txt, ActiveMQLog_PitcherStart.txt, ActiveMQLog_SimpleSenderStart.txt, CatcherPitcherTest2.zip
>
>
> 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 CMS.
> Here are more details about our applications.
> Both applications are using a COM component that we have created as a thin wrapper around CMS.
> 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.


[jira] Updated: (AMQCPP-314) Starting app with Com using cms destroys connection of other app. New problem with recent lib version

Posted by "Barbara Dawkins (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQCPP-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Barbara Dawkins updated AMQCPP-314:
-----------------------------------

    Attachment: CatcherPitcherTest2.zip

The zip file has a bin directory.  
The catcher app is PersonalizationMessageCatcherU.exe,  and should be started first.  
The PersonalizationPitcher.exe can be run to verify that Catcher can recieve messages,  just hit "Enter" in it's console window whenever you want to send a message.
The SimpleSender.exe file will kill PersonalizationMessageCatcher's connection when it is started.  After that,  you can verify the connection is gone when looking at the topic page or by hitting "Enter" on the Pitcher again.
There are two .reg files in bin directory also,  they will turn on logging for SimpleSender and the Catcher.

Also, CmsMessageHandlerCOMU.dll and NCRSimple.dll should be registered.  Thanks.

> Starting app with Com using cms destroys connection of other app. New problem with recent lib version
> -----------------------------------------------------------------------------------------------------
>
>                 Key: AMQCPP-314
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-314
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>    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: CatcherPitcherTest2.zip
>
>
> 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 CMS.
> Here are more details about our applications.
> Both applications are using a COM component that we have created as a thin wrapper around CMS.
> 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.


[jira] Updated: (AMQCPP-314) Starting app with Com using cms destroys connection of other app. New problem with recent lib version

Posted by "Barbara Dawkins (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQCPP-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Barbara Dawkins updated AMQCPP-314:
-----------------------------------

    Component/s: CMS Impl

In the Attached file,  CmsMessageHandlerCOMU.dll, NCRSimple.dll,  and tbControlsU.dll need to be registered.  Their configuration files are in the config and the config\LocalTestFiles directory.  The URL of the broker on my system is 127.0.0.1 (localhost),  port 61616.  The config files will need to changed if you are using a different address.  

Thanks.

> Starting app with Com using cms destroys connection of other app. New problem with recent lib version
> -----------------------------------------------------------------------------------------------------
>
>                 Key: AMQCPP-314
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-314
>             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: CatcherPitcherTest2.zip
>
>
> 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 CMS.
> Here are more details about our applications.
> Both applications are using a COM component that we have created as a thin wrapper around CMS.
> 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.


[jira] Commented: (AMQCPP-314) Starting app with Com using cms destroys connection of other app. New problem with recent lib version

Posted by "Barbara Dawkins (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/AMQCPP-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61382#action_61382 ] 

Barbara Dawkins commented on AMQCPP-314:
----------------------------------------

>From my notes:

"I traced through the creation of the ConnectionID. When apr_gethostname calls gethostname, some sort of exception occurs that
throws the trace back to ActiveMQConnection::ActiveMQConnection. I attempted to do generic catches, but was unable to stop the
exit back to the "Pointer<ConnectionConfig> configuration( new ConnectionConfig );" line. "

Given the above behavior,  I don't see where to put reading the returned error.  The return I can't catch happens where I would want to retreive the error code. :-(.
  



> Starting app with Com using cms destroys connection of other app. New problem with recent lib version
> -----------------------------------------------------------------------------------------------------
>
>                 Key: AMQCPP-314
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-314
>             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, CatcherPitcherTest2.zip
>
>
> 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 CMS.
> Here are more details about our applications.
> Both applications are using a COM component that we have created as a thin wrapper around CMS.
> 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.


[jira] Updated: (AMQCPP-314) Starting app with Com using cms destroys connection of other app. New problem with recent lib version

Posted by "Barbara Dawkins (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQCPP-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Barbara Dawkins updated AMQCPP-314:
-----------------------------------


I traced through the creation of the ConnectionID.  When apr_gethostname calls gethostname,  some sort of exception occurs that
throws the trace back to ActiveMQConnection::ActiveMQConnection.  I attempted to do generic catches,  but was unable to stop the
exit back to the "Pointer<ConnectionConfig> configuration( new ConnectionConfig );" line.  


>	libapr-1D.dll!apr_gethostname(char * buf=0x0214e650, int len=0x00000101, apr_pool_t * cont=0x01aa2328)  Line 262	C
 	activemq-cppud.dll!decaf::net::InetAddress::getLocalHost()  Line 154 + 0x2a bytes	C++
 	activemq-cppud.dll!activemq::util::IdGenerator::StaticData::StaticData()  Line 42 + 0xc bytes	C++
 	activemq-cppud.dll!activemq::util::IdGenerator::getClassStaticData()  Line 163 + 0x2a bytes	C++
 	activemq-cppud.dll!activemq::util::IdGenerator::generateId()  Line 89 + 0x5 bytes	C++
 	activemq-cppud.dll!activemq::core::ConnectionConfig::ConnectionConfig()  Line 145 + 0x1c bytes	C++
 	activemq-cppud.dll!activemq::core::ActiveMQConnection::ActiveMQConnection(const 

Since I don't know what error winsock2's gethostname is generating, 
I was able to get things working here by making this change to IdGenerator::StaticData::StaticData():

////////////////////////////////////////////////////////////////////////////////
IdGenerator::StaticData::StaticData() : UNIQUE_STUB(), instanceCount(0), hostname() {

  TCHAR chrComputerName[MAX_COMPUTERNAME_LENGTH + 1];
  DWORD dwBufferSize = MAX_COMPUTERNAME_LENGTH + 1;  
  std::string stub = "";
  
#ifdef _WINDOWS_
  if(GetComputerName(chrComputerName,&dwBufferSize)) 
  {  
	  // We got the name, set the return value.  
	  hostname = chrComputerName;  
  } else 
  {  
	  hostname = UUID::randomUUID().toString(); 
  }  
    stub = "-1-" + Long::toString( System::currentTimeMillis() ) + "-";
#else

    try {
        hostname = InetAddress::getLocalHost().getHostName();
        ServerSocket ss( 0 );
        stub = "-" + Long::toString( ss.getLocalPort() ) + "-" +
                     Long::toString( System::currentTimeMillis() ) + "-";
        Thread::sleep( 100 );
        ss.close();
    } catch( Exception& ioe ) {
        hostname = "localhost";
        stub = "-1-" + Long::toString( System::currentTimeMillis() ) + "-";
    }
#endif

    UNIQUE_STUB = stub;
}

P. S.  Looking forward to your suggestions for permanent fix :-).



> Starting app with Com using cms destroys connection of other app. New problem with recent lib version
> -----------------------------------------------------------------------------------------------------
>
>                 Key: AMQCPP-314
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-314
>             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, CatcherPitcherTest2.zip
>
>
> 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 CMS.
> Here are more details about our applications.
> Both applications are using a COM component that we have created as a thin wrapper around CMS.
> 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.


[jira] Commented: (AMQCPP-314) Starting app with Com using cms destroys connection of other app. New problem with recent lib version

Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/AMQCPP-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61591#action_61591 ] 

Timothy Bish commented on AMQCPP-314:
-------------------------------------

Added what should be a fix in trunk, however this fix cannot go back into 3.2.x as it breaks ABI.  Will attempt to create a workaround in the 3.2.x code.  If you could test with trunk and let me know if your issue is resolved that would be helpful.

> Starting app with Com using cms destroys connection of other app. New problem with recent lib version
> -----------------------------------------------------------------------------------------------------
>
>                 Key: AMQCPP-314
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-314
>             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
>             Fix For: 3.2.3, 3.3.0
>
>         Attachments: ActiveMQLog_CatcherStart.txt, ActiveMQLog_PitcherStart.txt, ActiveMQLog_SimpleSenderStart.txt, CatcherPitcherTest2.zip
>
>
> 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 CMS.
> Here are more details about our applications.
> Both applications are using a COM component that we have created as a thin wrapper around CMS.
> 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.


[jira] Commented: (AMQCPP-314) Starting app with Com using cms destroys connection of other app. New problem with recent lib version

Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/AMQCPP-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61372#action_61372 ] 

Timothy Bish commented on AMQCPP-314:
-------------------------------------

The apr functions don't generally throw an exception but instead return a status code.  If the return value is not APR_SUCCESS then you can usually get more info using the following

{noformat}
    std::string returnValue;

    // Get the error code.
    apr_status_t errorCode = apr_get_netos_error();

    // Create a buffer and get the error
    char buffer[256];
    return apr_strerror( errorCode, buffer, sizeof( buffer ) );
{noformat}

> Starting app with Com using cms destroys connection of other app. New problem with recent lib version
> -----------------------------------------------------------------------------------------------------
>
>                 Key: AMQCPP-314
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-314
>             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, CatcherPitcherTest2.zip
>
>
> 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 CMS.
> Here are more details about our applications.
> Both applications are using a COM component that we have created as a thin wrapper around CMS.
> 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.


[jira] Commented: (AMQCPP-314) Starting app with Com using cms destroys connection of other app. New problem with recent lib version

Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/AMQCPP-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61594#action_61594 ] 

Timothy Bish commented on AMQCPP-314:
-------------------------------------

Work-around not applied to 3.2.x fixes branch.

> Starting app with Com using cms destroys connection of other app. New problem with recent lib version
> -----------------------------------------------------------------------------------------------------
>
>                 Key: AMQCPP-314
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-314
>             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
>             Fix For: 3.2.3, 3.3.0
>
>         Attachments: ActiveMQLog_CatcherStart.txt, ActiveMQLog_PitcherStart.txt, ActiveMQLog_SimpleSenderStart.txt, CatcherPitcherTest2.zip
>
>
> 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 CMS.
> Here are more details about our applications.
> Both applications are using a COM component that we have created as a thin wrapper around CMS.
> 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.


[jira] Commented: (AMQCPP-314) Starting app with Com using cms destroys connection of other app. New problem with recent lib version

Posted by "Barbara Dawkins (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/AMQCPP-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61369#action_61369 ] 

Barbara Dawkins commented on AMQCPP-314:
----------------------------------------

I am using 
   apr-1.4.2
   apr-iconv-0.9.7
   apr-util-1.3.9

Do you have any suggestions for how to catch the winsock error?  All the try/catches I put in place did not help. 



> Starting app with Com using cms destroys connection of other app. New problem with recent lib version
> -----------------------------------------------------------------------------------------------------
>
>                 Key: AMQCPP-314
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-314
>             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, CatcherPitcherTest2.zip
>
>
> 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 CMS.
> Here are more details about our applications.
> Both applications are using a COM component that we have created as a thin wrapper around CMS.
> 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.