[jira] [Comment Edited] (AMQNET-387) no iconnectionfactory implementation found for connection uri
[ https://issues.apache.org/jira/browse/AMQNET-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13289942#comment-13289942 ] Tamilmaran edited comment on AMQNET-387 at 6/6/12 4:35 AM: --- Yes,I could see the Apache.NMS.ActiveMQ.dll in the output path on server side as i had referenced it previously. On the client side,it's gone as i cleaned the solution to rebuild it. It is working if i have Apache.NMS.ActiveMQ.dll in the output folder even if i didn't use it. May i know how it is being called internally...? can u get me understand the flow/architecture? was (Author: tamilmaran): Yes,I could see the Apache.NMS.ActiveMQ.dll in the output path on server side as i had referenced it previously. On the client side,it's gone as i cleaned the solution to rebuild it. It is working if i have Apache.NMS.ActiveMQ.dll in the output folder even if i didn't use it. May i know how it is being called internally...? can u get me understand the flow? > no iconnectionfactory implementation found for connection uri > - > > Key: AMQNET-387 > URL: https://issues.apache.org/jira/browse/AMQNET-387 > Project: ActiveMQ .Net > Issue Type: Bug >Reporter: Tamilmaran >Assignee: Jim Gomes > > I'm facing the "no iconnectionfactory implementation found for connection > uri" issue on the client system.The server side which has the broker into it, > is running perfectly for topic/queue pub/sub.But the client is not working. > I have used only NMS DLL. I am not supposed to use NMS.ActiveMQ DLL. In this > case, How to get rid of this issue? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQNET-387) no iconnectionfactory implementation found for connection uri
[ https://issues.apache.org/jira/browse/AMQNET-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13289942#comment-13289942 ] Tamilmaran commented on AMQNET-387: --- Yes,I could see the Apache.NMS.ActiveMQ.dll in the output path on server side as i had referenced it previously. On the client side,it's gone as i cleaned the solution to rebuild it. It is working if i have Apache.NMS.ActiveMQ.dll in the output folder even if i didn't use it. May i know how it is being called internally...? can u get me understand the flow? > no iconnectionfactory implementation found for connection uri > - > > Key: AMQNET-387 > URL: https://issues.apache.org/jira/browse/AMQNET-387 > Project: ActiveMQ .Net > Issue Type: Bug >Reporter: Tamilmaran >Assignee: Jim Gomes > > I'm facing the "no iconnectionfactory implementation found for connection > uri" issue on the client system.The server side which has the broker into it, > is running perfectly for topic/queue pub/sub.But the client is not working. > I have used only NMS DLL. I am not supposed to use NMS.ActiveMQ DLL. In this > case, How to get rid of this issue? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (AMQNET-387) no iconnectionfactory implementation found for connection uri
[ https://issues.apache.org/jira/browse/AMQNET-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13289873#comment-13289873 ] Jim Gomes edited comment on AMQNET-387 at 6/5/12 11:58 PM: --- Tamilmaran, as Tim mentioned, you should see the Apache.NMS.ActiveMQ.dll assembly on the server. If it's not there, but it is being loaded, it's possible that it may have been placed into the Global Assembly Cache (GAC). I haven't tested that, but it's a theory as to why you may not be seeing it, yet it is being loaded. To solve the client-side problem, all you have to do is copy the Apache.NMS.ActiveMQ.dll into the same folder as the Apache.NMS.dll. As you mention, you only need to develop against the Apache.NMS.dll, but you need to deploy both assemblies. was (Author: jgomes): Tamilmaran, as Tim mentioned, you should see the Apache.NMS.ActiveMQ.dll assembly on the server. If it's not there, but it is being loaded, it's possible that it may have been placed into the Global Assembly Cache (GAC). I haven't tested that, but it's a theory as to why you may not be seeing it, yet it is being loaded. To solve the client-side problem, all you have to do is copy the Apache.NMS.ActiveMQ.dll into the save folder as the Apache.NMS.dll. As you mention, you only need to develop against the Apache.NMS.dll, but you need to deploy both assemblies. > no iconnectionfactory implementation found for connection uri > - > > Key: AMQNET-387 > URL: https://issues.apache.org/jira/browse/AMQNET-387 > Project: ActiveMQ .Net > Issue Type: Bug >Reporter: Tamilmaran >Assignee: Jim Gomes > > I'm facing the "no iconnectionfactory implementation found for connection > uri" issue on the client system.The server side which has the broker into it, > is running perfectly for topic/queue pub/sub.But the client is not working. > I have used only NMS DLL. I am not supposed to use NMS.ActiveMQ DLL. In this > case, How to get rid of this issue? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQNET-387) no iconnectionfactory implementation found for connection uri
[ https://issues.apache.org/jira/browse/AMQNET-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13289873#comment-13289873 ] Jim Gomes commented on AMQNET-387: -- Tamilmaran, as Tim mentioned, you should see the Apache.NMS.ActiveMQ.dll assembly on the server. If it's not there, but it is being loaded, it's possible that it may have been placed into the Global Assembly Cache (GAC). I haven't tested that, but it's a theory as to why you may not be seeing it, yet it is being loaded. To solve the client-side problem, all you have to do is copy the Apache.NMS.ActiveMQ.dll into the save folder as the Apache.NMS.dll. As you mention, you only need to develop against the Apache.NMS.dll, but you need to deploy both assemblies. > no iconnectionfactory implementation found for connection uri > - > > Key: AMQNET-387 > URL: https://issues.apache.org/jira/browse/AMQNET-387 > Project: ActiveMQ .Net > Issue Type: Bug >Reporter: Tamilmaran >Assignee: Jim Gomes > > I'm facing the "no iconnectionfactory implementation found for connection > uri" issue on the client system.The server side which has the broker into it, > is running perfectly for topic/queue pub/sub.But the client is not working. > I have used only NMS DLL. I am not supposed to use NMS.ActiveMQ DLL. In this > case, How to get rid of this issue? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQCPP-407) Application crashes after stopping message broker
[ https://issues.apache.org/jira/browse/AMQCPP-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13289807#comment-13289807 ] Timothy Bish commented on AMQCPP-407: - The stack trace still doesn't reveal anything new, the CMSTemplate code calls connection.close() in the resource manager before destroying the connection object so its still a mystery how the transport can still be active and firing onException events at the time of destruction. You don't have any other ActiveMQConnectoin objects outside of your CMSTemplate usage do you? > Application crashes after stopping message broker > - > > Key: AMQCPP-407 > URL: https://issues.apache.org/jira/browse/AMQCPP-407 > Project: ActiveMQ C++ Client > Issue Type: Bug > Components: CMS Impl >Affects Versions: 3.4.1 > Environment: Windows xp service pack 3, ActiveMQ broker 5.3.1, apr > 1.4.2, apr-util 1.3.9, apr iconv 1.2.1 >Reporter: Helen Huang >Assignee: Timothy Bish >Priority: Blocker > Fix For: 3.4.1 > > Attachments: AttemptedFix1.7z > > > Stopping the message broker would crash our application. The following is the > call stack of the fault thread. > Thread 0 - System ID 672 > Entry point msvcr80!endthreadex+61 > Create time 5/24/2012 1:53:56 PM > Time spent in user mode 0 Days 0:0:0.46 > Time spent in kernel mode 0 Days 0:0:0.78 > Function Arg 1 Arg 2 Arg 3 Source > kernel32!InterlockedDecrement+9 00242110 > msvcrt!cexit+f 77c1 0001 > ntdll!LdrInitializeThunk+24 77c1f2a1 77c1 > ntdll!RtlDestroyEnvironment+178 0eec256d 0001 > kernel32!IsValidLocale+8eb 0003 77e8f3b0 > kernel32!ExitProcess+14 0003 0ec21a04 0003 > msvcr80!amsg_exit+5e 0003 0001 > msvcr80!exit+d 1795efe0 > user32!MessageBoxIndirectA+23a 0001 7c91005d 13946b5e > user32!MessageBoxIndirectA+254 13946b5e 00e30850 > ntdll!RtlFreeHeap+130 0468001b 0202 1795f110 > activemq_cppu!activemq::core::ActiveMQConnection::onException+fd 1795fe24 > 7f427d47 1795fe18 > activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 > 7f427d33 1795fe18 > activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 > 7f427cef 1795fe18 > activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 > 1795f60c 0ef4a264 > activemq_cppu!activemq::transport::inactivity::InactivityMonitor::onException+33 > 1795fe24 7f427cd7 1795fe18 > activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 > 7f427c83 1795fe18 > activemq_cppu!activemq::transport::IOTransport::fire+4b 1795fe24 > 0ec48ed7 1795fe18 > activemq_cppu!activemq::transport::IOTransport::run+15e 7f427107 > 7c809c65 12519500 > activemq_cppu!decaf::lang::ThreadProperties::runCallback+82 7c936d80 > 04682060 0ec229bb > activemq_cppu!`anonymous namespace'::threadWorker+20 04682060 > 0ec229bb 12519500 > ntdll!RtlRemoveVectoredExceptionHandler+2a2 04682060 7c80b729 > 1252f168 > msvcr80!endthreadex+c7 0ec229e1 1252f168 > KERNEL32!INTERLOCKEDDECREMENT+9WARNING - DebugDiag was not able to locate > debug symbols for kernel32.dll, so the information below may be incomplete. > In > ScotAppU__PID__1168__Date__05_24_2012__Time_02_18_41PM__916__Second_Chance_Exception_C005.dmp > the assembly instruction at kernel32!InterlockedDecrement+9 in > C:\WINDOWS\system32\kernel32.dll from Microsoft Corporation has caused an > access violation exception (0xC005) when trying to write to memory > location 0x014718e4 on thread 0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (AMQCPP-407) Application crashes after stopping message broker
[ https://issues.apache.org/jira/browse/AMQCPP-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13289764#comment-13289764 ] Helen Huang edited comment on AMQCPP-407 at 6/5/12 9:59 PM: With the changes in IOTransport, we still found crashes on the lab system, but we did not catch any in our development environment yet. I am not sure the crashes came from the same place or not. We will try some more tests tomorrow and let you know if we find anything. Thanks! was (Author: hhuang): With the changes in IOTransport, we still found crashes on the lab system, but we have not been able to catch any in our development environment yet. I am not sure the crashes came from the same place. Will try some more test tomorrow and let you know if we find anything. Thanks! > Application crashes after stopping message broker > - > > Key: AMQCPP-407 > URL: https://issues.apache.org/jira/browse/AMQCPP-407 > Project: ActiveMQ C++ Client > Issue Type: Bug > Components: CMS Impl >Affects Versions: 3.4.1 > Environment: Windows xp service pack 3, ActiveMQ broker 5.3.1, apr > 1.4.2, apr-util 1.3.9, apr iconv 1.2.1 >Reporter: Helen Huang >Assignee: Timothy Bish >Priority: Blocker > Fix For: 3.4.1 > > Attachments: AttemptedFix1.7z > > > Stopping the message broker would crash our application. The following is the > call stack of the fault thread. > Thread 0 - System ID 672 > Entry point msvcr80!endthreadex+61 > Create time 5/24/2012 1:53:56 PM > Time spent in user mode 0 Days 0:0:0.46 > Time spent in kernel mode 0 Days 0:0:0.78 > Function Arg 1 Arg 2 Arg 3 Source > kernel32!InterlockedDecrement+9 00242110 > msvcrt!cexit+f 77c1 0001 > ntdll!LdrInitializeThunk+24 77c1f2a1 77c1 > ntdll!RtlDestroyEnvironment+178 0eec256d 0001 > kernel32!IsValidLocale+8eb 0003 77e8f3b0 > kernel32!ExitProcess+14 0003 0ec21a04 0003 > msvcr80!amsg_exit+5e 0003 0001 > msvcr80!exit+d 1795efe0 > user32!MessageBoxIndirectA+23a 0001 7c91005d 13946b5e > user32!MessageBoxIndirectA+254 13946b5e 00e30850 > ntdll!RtlFreeHeap+130 0468001b 0202 1795f110 > activemq_cppu!activemq::core::ActiveMQConnection::onException+fd 1795fe24 > 7f427d47 1795fe18 > activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 > 7f427d33 1795fe18 > activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 > 7f427cef 1795fe18 > activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 > 1795f60c 0ef4a264 > activemq_cppu!activemq::transport::inactivity::InactivityMonitor::onException+33 > 1795fe24 7f427cd7 1795fe18 > activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 > 7f427c83 1795fe18 > activemq_cppu!activemq::transport::IOTransport::fire+4b 1795fe24 > 0ec48ed7 1795fe18 > activemq_cppu!activemq::transport::IOTransport::run+15e 7f427107 > 7c809c65 12519500 > activemq_cppu!decaf::lang::ThreadProperties::runCallback+82 7c936d80 > 04682060 0ec229bb > activemq_cppu!`anonymous namespace'::threadWorker+20 04682060 > 0ec229bb 12519500 > ntdll!RtlRemoveVectoredExceptionHandler+2a2 04682060 7c80b729 > 1252f168 > msvcr80!endthreadex+c7 0ec229e1 1252f168 > KERNEL32!INTERLOCKEDDECREMENT+9WARNING - DebugDiag was not able to locate > debug symbols for kernel32.dll, so the information below may be incomplete. > In > ScotAppU__PID__1168__Date__05_24_2012__Time_02_18_41PM__916__Second_Chance_Exception_C005.dmp > the assembly instruction at kernel32!InterlockedDecrement+9 in > C:\WINDOWS\system32\kernel32.dll from Microsoft Corporation has caused an > access violation exception (0xC005) when trying to write to memory > location 0x014718e4 on thread 0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQCPP-407) Application crashes after stopping message broker
[ https://issues.apache.org/jira/browse/AMQCPP-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13289764#comment-13289764 ] Helen Huang commented on AMQCPP-407: With the changes in IOTransport, we still found crashes on the lab system, but we have not been able to catch any in our development environment yet. I am not sure the crashes came from the same place. Will try some more test tomorrow and let you know if we find anything. Thanks! > Application crashes after stopping message broker > - > > Key: AMQCPP-407 > URL: https://issues.apache.org/jira/browse/AMQCPP-407 > Project: ActiveMQ C++ Client > Issue Type: Bug > Components: CMS Impl >Affects Versions: 3.4.1 > Environment: Windows xp service pack 3, ActiveMQ broker 5.3.1, apr > 1.4.2, apr-util 1.3.9, apr iconv 1.2.1 >Reporter: Helen Huang >Assignee: Timothy Bish >Priority: Blocker > Fix For: 3.4.1 > > Attachments: AttemptedFix1.7z > > > Stopping the message broker would crash our application. The following is the > call stack of the fault thread. > Thread 0 - System ID 672 > Entry point msvcr80!endthreadex+61 > Create time 5/24/2012 1:53:56 PM > Time spent in user mode 0 Days 0:0:0.46 > Time spent in kernel mode 0 Days 0:0:0.78 > Function Arg 1 Arg 2 Arg 3 Source > kernel32!InterlockedDecrement+9 00242110 > msvcrt!cexit+f 77c1 0001 > ntdll!LdrInitializeThunk+24 77c1f2a1 77c1 > ntdll!RtlDestroyEnvironment+178 0eec256d 0001 > kernel32!IsValidLocale+8eb 0003 77e8f3b0 > kernel32!ExitProcess+14 0003 0ec21a04 0003 > msvcr80!amsg_exit+5e 0003 0001 > msvcr80!exit+d 1795efe0 > user32!MessageBoxIndirectA+23a 0001 7c91005d 13946b5e > user32!MessageBoxIndirectA+254 13946b5e 00e30850 > ntdll!RtlFreeHeap+130 0468001b 0202 1795f110 > activemq_cppu!activemq::core::ActiveMQConnection::onException+fd 1795fe24 > 7f427d47 1795fe18 > activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 > 7f427d33 1795fe18 > activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 > 7f427cef 1795fe18 > activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 > 1795f60c 0ef4a264 > activemq_cppu!activemq::transport::inactivity::InactivityMonitor::onException+33 > 1795fe24 7f427cd7 1795fe18 > activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 > 7f427c83 1795fe18 > activemq_cppu!activemq::transport::IOTransport::fire+4b 1795fe24 > 0ec48ed7 1795fe18 > activemq_cppu!activemq::transport::IOTransport::run+15e 7f427107 > 7c809c65 12519500 > activemq_cppu!decaf::lang::ThreadProperties::runCallback+82 7c936d80 > 04682060 0ec229bb > activemq_cppu!`anonymous namespace'::threadWorker+20 04682060 > 0ec229bb 12519500 > ntdll!RtlRemoveVectoredExceptionHandler+2a2 04682060 7c80b729 > 1252f168 > msvcr80!endthreadex+c7 0ec229e1 1252f168 > KERNEL32!INTERLOCKEDDECREMENT+9WARNING - DebugDiag was not able to locate > debug symbols for kernel32.dll, so the information below may be incomplete. > In > ScotAppU__PID__1168__Date__05_24_2012__Time_02_18_41PM__916__Second_Chance_Exception_C005.dmp > the assembly instruction at kernel32!InterlockedDecrement+9 in > C:\WINDOWS\system32\kernel32.dll from Microsoft Corporation has caused an > access violation exception (0xC005) when trying to write to memory > location 0x014718e4 on thread 0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (AMQCPP-407) Application crashes after stopping message broker
[
https://issues.apache.org/jira/browse/AMQCPP-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13289709#comment-13289709
]
Helen Huang edited comment on AMQCPP-407 at 6/5/12 9:54 PM:
Hi Timothy,
I was able to set up a development environment where we can recreate the
problem (without using the change in IOTransport that you recently suggested).
It crashed on the following line in the function
ActiveMQConnection::onException():
Pointer< Iterator > iter(
this->config->transportListeners.iterator() );
Call stack:
msvcr80d.dll!_NMSG_WRITE(int rterrnum=25) Line 198 C
msvcr80d.dll!_purecall() Line 54 + 0x7 bytes C
>
> activemq-cppud.dll!activemq::core::ActiveMQConnection::onException(const
> decaf::lang::Exception & ex={...}) Line 782 + 0x49 bytes C++
activemq-cppud.dll!activemq::transport::TransportFilter::fire(const
decaf::lang::Exception & ex={...}) Line 54 + 0x17 bytesC++
activemq-cppud.dll!activemq::transport::TransportFilter::onException(const
decaf::lang::Exception & ex={...}) Line 47 C++
activemq-cppud.dll!activemq::transport::TransportFilter::fire(const
decaf::lang::Exception & ex={...}) Line 54 + 0x17 bytesC++
activemq-cppud.dll!activemq::transport::TransportFilter::onException(const
decaf::lang::Exception & ex={...}) Line 47 C++
activemq-cppud.dll!activemq::transport::TransportFilter::fire(const
decaf::lang::Exception & ex={...}) Line 54 + 0x17 bytesC++
activemq-cppud.dll!activemq::transport::TransportFilter::onException(const
decaf::lang::Exception & ex={...}) Line 47 C++
activemq-cppud.dll!activemq::transport::inactivity::InactivityMonitor::onException(const
decaf::lang::Exception & ex={...}) Line 314 C++
activemq-cppud.dll!activemq::transport::TransportFilter::fire(const
decaf::lang::Exception & ex={...}) Line 54 + 0x17 bytesC++
activemq-cppud.dll!activemq::transport::TransportFilter::onException(const
decaf::lang::Exception & ex={...}) Line 47 C++
activemq-cppud.dll!activemq::transport::IOTransport::fire(decaf::lang::Exception
& ex={...}) Line 72 + 0x17 bytes C++
activemq-cppud.dll!activemq::transport::IOTransport::run() Line 245
C++
activemq-cppud.dll!decaf::lang::ThreadProperties::runCallback(decaf::lang::ThreadProperties
* properties=0x0eccdde8) Line 137 + 0x13 bytes C++
activemq-cppud.dll!`anonymous namespace'::threadWorker(void *
arg=0x0eccdde8) Line 210 + 0x9 bytes C++
msvcr80d.dll!_callthreadstartex() Line 348 + 0xf bytes C
msvcr80d.dll!_threadstartex(void * ptd=0x0eccdb98) Line 331C
was (Author: hhuang):
Hi Timothy,
I was able to set up a development environment where we can recreate the
problem without using the change in IOTransport that you recently suggested).
It crashed on the following line in the function
ActiveMQConnection::onException():
Pointer< Iterator > iter(
this->config->transportListeners.iterator() );
Call stack:
msvcr80d.dll!_NMSG_WRITE(int rterrnum=25) Line 198 C
msvcr80d.dll!_purecall() Line 54 + 0x7 bytes C
>
> activemq-cppud.dll!activemq::core::ActiveMQConnection::onException(const
> decaf::lang::Exception & ex={...}) Line 782 + 0x49 bytes C++
activemq-cppud.dll!activemq::transport::TransportFilter::fire(const
decaf::lang::Exception & ex={...}) Line 54 + 0x17 bytesC++
activemq-cppud.dll!activemq::transport::TransportFilter::onException(const
decaf::lang::Exception & ex={...}) Line 47 C++
activemq-cppud.dll!activemq::transport::TransportFilter::fire(const
decaf::lang::Exception & ex={...}) Line 54 + 0x17 bytesC++
activemq-cppud.dll!activemq::transport::TransportFilter::onException(const
decaf::lang::Exception & ex={...}) Line 47 C++
activemq-cppud.dll!activemq::transport::TransportFilter::fire(const
decaf::lang::Exception & ex={...}) Line 54 + 0x17 bytesC++
activemq-cppud.dll!activemq::transport::TransportFilter::onException(const
decaf::lang::Exception & ex={...}) Line 47 C++
activemq-cppud.dll!activemq::transport::inactivity::InactivityMonitor::onException(const
decaf::lang::Exception & ex={...}) Line 314 C++
activemq-cppud.dll!activemq::transport::TransportFilter::fire(const
decaf::lang::Exception & ex={...}) Line 54 + 0x17 bytesC++
activemq-cppud.dll!activemq::transport::TransportFilter::onException(const
decaf::lang::Exception & ex={...}) Line 47 C++
activemq-cppud.dll!activemq::transport::IOTransport::fire(decaf::lang::Exception
& ex={...}) Line 72 + 0x17 bytes C++
activemq-cppud.dll!activemq::transport::IOTransport::run() Line 245
C++
activemq-cppud.dll!decaf::lang::ThreadProperties::run
[jira] [Comment Edited] (AMQCPP-407) Application crashes after stopping message broker
[
https://issues.apache.org/jira/browse/AMQCPP-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13289709#comment-13289709
]
Helen Huang edited comment on AMQCPP-407 at 6/5/12 9:54 PM:
Hi Timothy,
I was able to set up a development environment where we can recreate the
problem without using the change in IOTransport that you recently suggested).
It crashed on the following line in the function
ActiveMQConnection::onException():
Pointer< Iterator > iter(
this->config->transportListeners.iterator() );
Call stack:
msvcr80d.dll!_NMSG_WRITE(int rterrnum=25) Line 198 C
msvcr80d.dll!_purecall() Line 54 + 0x7 bytes C
>
> activemq-cppud.dll!activemq::core::ActiveMQConnection::onException(const
> decaf::lang::Exception & ex={...}) Line 782 + 0x49 bytes C++
activemq-cppud.dll!activemq::transport::TransportFilter::fire(const
decaf::lang::Exception & ex={...}) Line 54 + 0x17 bytesC++
activemq-cppud.dll!activemq::transport::TransportFilter::onException(const
decaf::lang::Exception & ex={...}) Line 47 C++
activemq-cppud.dll!activemq::transport::TransportFilter::fire(const
decaf::lang::Exception & ex={...}) Line 54 + 0x17 bytesC++
activemq-cppud.dll!activemq::transport::TransportFilter::onException(const
decaf::lang::Exception & ex={...}) Line 47 C++
activemq-cppud.dll!activemq::transport::TransportFilter::fire(const
decaf::lang::Exception & ex={...}) Line 54 + 0x17 bytesC++
activemq-cppud.dll!activemq::transport::TransportFilter::onException(const
decaf::lang::Exception & ex={...}) Line 47 C++
activemq-cppud.dll!activemq::transport::inactivity::InactivityMonitor::onException(const
decaf::lang::Exception & ex={...}) Line 314 C++
activemq-cppud.dll!activemq::transport::TransportFilter::fire(const
decaf::lang::Exception & ex={...}) Line 54 + 0x17 bytesC++
activemq-cppud.dll!activemq::transport::TransportFilter::onException(const
decaf::lang::Exception & ex={...}) Line 47 C++
activemq-cppud.dll!activemq::transport::IOTransport::fire(decaf::lang::Exception
& ex={...}) Line 72 + 0x17 bytes C++
activemq-cppud.dll!activemq::transport::IOTransport::run() Line 245
C++
activemq-cppud.dll!decaf::lang::ThreadProperties::runCallback(decaf::lang::ThreadProperties
* properties=0x0eccdde8) Line 137 + 0x13 bytes C++
activemq-cppud.dll!`anonymous namespace'::threadWorker(void *
arg=0x0eccdde8) Line 210 + 0x9 bytes C++
msvcr80d.dll!_callthreadstartex() Line 348 + 0xf bytes C
msvcr80d.dll!_threadstartex(void * ptd=0x0eccdb98) Line 331C
was (Author: hhuang):
Hi Timothy,
I was able to set up a development environment where we can recreate the
problem. It crashed on the following line in the function
ActiveMQConnection::onException():
Pointer< Iterator > iter(
this->config->transportListeners.iterator() );
Could you please come out a fix for it? Call stack:
msvcr80d.dll!_NMSG_WRITE(int rterrnum=25) Line 198 C
msvcr80d.dll!_purecall() Line 54 + 0x7 bytes C
>
> activemq-cppud.dll!activemq::core::ActiveMQConnection::onException(const
> decaf::lang::Exception & ex={...}) Line 782 + 0x49 bytes C++
activemq-cppud.dll!activemq::transport::TransportFilter::fire(const
decaf::lang::Exception & ex={...}) Line 54 + 0x17 bytesC++
activemq-cppud.dll!activemq::transport::TransportFilter::onException(const
decaf::lang::Exception & ex={...}) Line 47 C++
activemq-cppud.dll!activemq::transport::TransportFilter::fire(const
decaf::lang::Exception & ex={...}) Line 54 + 0x17 bytesC++
activemq-cppud.dll!activemq::transport::TransportFilter::onException(const
decaf::lang::Exception & ex={...}) Line 47 C++
activemq-cppud.dll!activemq::transport::TransportFilter::fire(const
decaf::lang::Exception & ex={...}) Line 54 + 0x17 bytesC++
activemq-cppud.dll!activemq::transport::TransportFilter::onException(const
decaf::lang::Exception & ex={...}) Line 47 C++
activemq-cppud.dll!activemq::transport::inactivity::InactivityMonitor::onException(const
decaf::lang::Exception & ex={...}) Line 314 C++
activemq-cppud.dll!activemq::transport::TransportFilter::fire(const
decaf::lang::Exception & ex={...}) Line 54 + 0x17 bytesC++
activemq-cppud.dll!activemq::transport::TransportFilter::onException(const
decaf::lang::Exception & ex={...}) Line 47 C++
activemq-cppud.dll!activemq::transport::IOTransport::fire(decaf::lang::Exception
& ex={...}) Line 72 + 0x17 bytes C++
activemq-cppud.dll!activemq::transport::IOTransport::run() Line 245
C++
activemq-cppud.dll!decaf::lang::ThreadProperties::runCallback(decaf::lang::ThreadPro
[jira] [Closed] (AMQ-3814) MessageConsumer.receive() throwing InterruptedException after Thread suspension resulting in an JMSException being thrown upon subsequent attempt to close MessageConsumer.
[ https://issues.apache.org/jira/browse/AMQ-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-3814. - Resolution: Incomplete No test case provided and can't reproduce, need the users usage scenario to look any further. > MessageConsumer.receive() throwing InterruptedException after Thread > suspension resulting in an JMSException being thrown upon subsequent attempt > to close MessageConsumer. > --- > > Key: AMQ-3814 > URL: https://issues.apache.org/jira/browse/AMQ-3814 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.5.1 >Reporter: Ingrid Olson > Labels: durable_subscription, interruptedexception, > interruptedioexception, jmsexception, message_consumer, threading > > When I suspend a thread that is calling receive() on a MessageConsumer, a > JMSException is thrown. The cause of this is an InterruptedException. In the > catch block of the thrown JMSException, I then try calling close() the > MessageConsumer. Attempting to close the MessageConsumer throws another > JMSException due to an InterruptedIOException that gets thrown inside of the > "this.transport.oneway(command)" line of the doAsyncSendPacket(Command > command) call inside of the doClose() method inside of the close() method of > the ActiveMQMessageConsumer class. > The result of this is that the MessageConsumer does not close, so that when I > try to resubscribe my MessageConsumer to a durable Topic, I get an error that > the MessageConsumer is already in use for that subscription name and client > ID. > #AMQ-3529 (https://issues.apache.org/jira/browse/AMQ-3529) looks like it > addresses a similar issue, which has supposedly been fixed. When I use the > most recent snapshot of 5.6, though, I still encounter the same problem. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQCPP-407) Application crashes after stopping message broker
[ https://issues.apache.org/jira/browse/AMQCPP-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Helen Huang updated AMQCPP-407: --- Comment: was deleted (was: By the way did you look at this following stack (you probably did, but just in case) This thread shows a connection can be destroyed by CmsTemplate. Is there any way to prevent IOTransport/TransportFilter from calling fire(), when a connection is being destroyed? activemq-cppud.dll!activemq::core::ActiveMQConnection::~ActiveMQConnection() Line 242 C++ activemq-cppud.dll!activemq::core::ActiveMQConnection::`vbase destructor'() + 0xf bytes C++ activemq-cppud.dll!activemq::core::ActiveMQConnection::`vector deleting destructor'() + 0x4d bytes C++ activemq-cppud.dll!activemq::cmsutil::ResourceLifecycleManager::destroy() Line 135 + 0x20 bytes C++ activemq-cppud.dll!activemq::cmsutil::CmsAccessor::destroy() Line 131 C++ activemq-cppud.dll!activemq::cmsutil::CmsDestinationAccessor::destroy() Line 58 C++ activemq-cppud.dll!activemq::cmsutil::CmsTemplate::destroy() Line 211 + 0xb bytes C++ activemq-cppud.dll!activemq::cmsutil::CmsTemplate::ProducerExecutor::doInCms(cms::Session * session=0x01231668) Line 527 + 0x1a bytes C++ activemq-cppud.dll!activemq::cmsutil::CmsTemplate::execute(activemq::cmsutil::SessionCallback * action=0x0012fb80) Line 446 C++ activemq-cppud.dll!activemq::cmsutil::CmsTemplate::execute(activemq::cmsutil::ProducerCallback * action=0x0012fc08) Line 465 C++ activemq-cppud.dll!activemq::cmsutil::CmsTemplate::send(activemq::cmsutil::MessageCreator * messageCreator=0x01210698) Line 546 C++ BrokerMonitor.exe!main(int argc=1, char * * argv=0x00b78fb8) Line 76 + 0x1f bytes C++ BrokerMonitor.exe!__tmainCRTStartup() Line 597 + 0x19 bytes C BrokerMonitor.exe!mainCRTStartup() Line 414 C ) > Application crashes after stopping message broker > - > > Key: AMQCPP-407 > URL: https://issues.apache.org/jira/browse/AMQCPP-407 > Project: ActiveMQ C++ Client > Issue Type: Bug > Components: CMS Impl >Affects Versions: 3.4.1 > Environment: Windows xp service pack 3, ActiveMQ broker 5.3.1, apr > 1.4.2, apr-util 1.3.9, apr iconv 1.2.1 >Reporter: Helen Huang >Assignee: Timothy Bish >Priority: Blocker > Fix For: 3.4.1 > > Attachments: AttemptedFix1.7z > > > Stopping the message broker would crash our application. The following is the > call stack of the fault thread. > Thread 0 - System ID 672 > Entry point msvcr80!endthreadex+61 > Create time 5/24/2012 1:53:56 PM > Time spent in user mode 0 Days 0:0:0.46 > Time spent in kernel mode 0 Days 0:0:0.78 > Function Arg 1 Arg 2 Arg 3 Source > kernel32!InterlockedDecrement+9 00242110 > msvcrt!cexit+f 77c1 0001 > ntdll!LdrInitializeThunk+24 77c1f2a1 77c1 > ntdll!RtlDestroyEnvironment+178 0eec256d 0001 > kernel32!IsValidLocale+8eb 0003 77e8f3b0 > kernel32!ExitProcess+14 0003 0ec21a04 0003 > msvcr80!amsg_exit+5e 0003 0001 > msvcr80!exit+d 1795efe0 > user32!MessageBoxIndirectA+23a 0001 7c91005d 13946b5e > user32!MessageBoxIndirectA+254 13946b5e 00e30850 > ntdll!RtlFreeHeap+130 0468001b 0202 1795f110 > activemq_cppu!activemq::core::ActiveMQConnection::onException+fd 1795fe24 > 7f427d47 1795fe18 > activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 > 7f427d33 1795fe18 > activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 > 7f427cef 1795fe18 > activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 > 1795f60c 0ef4a264 > activemq_cppu!activemq::transport::inactivity::InactivityMonitor::onException+33 > 1795fe24 7f427cd7 1795fe18 > activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 > 7f427c83 1795fe18 > activemq_cppu!activemq::transport::IOTransport::fire+4b 1795fe24 > 0ec48ed7 1795fe18 > activemq_cppu!activemq::transport::IOTransport::run+15e 7f427107 > 7c809c65 12519500 > activemq_cppu!decaf::lang::ThreadProperties::runCallback+82 7c936d80 > 04682060 0ec229bb > activemq_cppu!`anonymous namespace'::threadWorker+20 04682060 > 0ec229bb 12519500 > ntdll!RtlRemoveVectoredExceptionHandler+2a2 04682060 7c80b729 > 1252f168 > msvcr80!endthreadex+c7 0ec229e1 1252f168 > KERNEL32!INTERLOCKEDDECREMENT+9WARNING - DebugDiag was not able to locate > debug symbols for kernel32.dll,
[jira] [Closed] (AMQ-3869) Docs mention supporting both subcriptionName and subscriptName in stomp
[ https://issues.apache.org/jira/browse/AMQ-3869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-3869. - Resolution: Won't Fix Updated the docs to reflect the change as of v5.6.0. The Stomp php client was update to now use the correctly spelled version. > Docs mention supporting both subcriptionName and subscriptName in stomp > --- > > Key: AMQ-3869 > URL: https://issues.apache.org/jira/browse/AMQ-3869 > Project: ActiveMQ > Issue Type: Improvement > Components: stomp >Affects Versions: 5.6.0 >Reporter: Alan Hudson > Attachments: pc_diff.patch, st_diff.patch > > > This page mentions supporting both names http://activemq.apache.org/stomp.html > The stomp php client from here: http://stomp.fusesource.org uses the old > style. Likely others are as well. > Supporting both is likely best for awhile, or at least at minimum the docs > should be updated to indicate the old style is no longer supported. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (AMQCPP-407) Application crashes after stopping message broker
[
https://issues.apache.org/jira/browse/AMQCPP-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13289709#comment-13289709
]
Helen Huang edited comment on AMQCPP-407 at 6/5/12 8:51 PM:
Hi Timothy,
I was able to set up a development environment where we can recreate the
problem. It crashed on the following line in the function
ActiveMQConnection::onException():
Pointer< Iterator > iter(
this->config->transportListeners.iterator() );
Could you please come out a fix for it? Call stack:
msvcr80d.dll!_NMSG_WRITE(int rterrnum=25) Line 198 C
msvcr80d.dll!_purecall() Line 54 + 0x7 bytes C
>
> activemq-cppud.dll!activemq::core::ActiveMQConnection::onException(const
> decaf::lang::Exception & ex={...}) Line 782 + 0x49 bytes C++
activemq-cppud.dll!activemq::transport::TransportFilter::fire(const
decaf::lang::Exception & ex={...}) Line 54 + 0x17 bytesC++
activemq-cppud.dll!activemq::transport::TransportFilter::onException(const
decaf::lang::Exception & ex={...}) Line 47 C++
activemq-cppud.dll!activemq::transport::TransportFilter::fire(const
decaf::lang::Exception & ex={...}) Line 54 + 0x17 bytesC++
activemq-cppud.dll!activemq::transport::TransportFilter::onException(const
decaf::lang::Exception & ex={...}) Line 47 C++
activemq-cppud.dll!activemq::transport::TransportFilter::fire(const
decaf::lang::Exception & ex={...}) Line 54 + 0x17 bytesC++
activemq-cppud.dll!activemq::transport::TransportFilter::onException(const
decaf::lang::Exception & ex={...}) Line 47 C++
activemq-cppud.dll!activemq::transport::inactivity::InactivityMonitor::onException(const
decaf::lang::Exception & ex={...}) Line 314 C++
activemq-cppud.dll!activemq::transport::TransportFilter::fire(const
decaf::lang::Exception & ex={...}) Line 54 + 0x17 bytesC++
activemq-cppud.dll!activemq::transport::TransportFilter::onException(const
decaf::lang::Exception & ex={...}) Line 47 C++
activemq-cppud.dll!activemq::transport::IOTransport::fire(decaf::lang::Exception
& ex={...}) Line 72 + 0x17 bytes C++
activemq-cppud.dll!activemq::transport::IOTransport::run() Line 245
C++
activemq-cppud.dll!decaf::lang::ThreadProperties::runCallback(decaf::lang::ThreadProperties
* properties=0x0eccdde8) Line 137 + 0x13 bytes C++
activemq-cppud.dll!`anonymous namespace'::threadWorker(void *
arg=0x0eccdde8) Line 210 + 0x9 bytes C++
msvcr80d.dll!_callthreadstartex() Line 348 + 0xf bytes C
msvcr80d.dll!_threadstartex(void * ptd=0x0eccdb98) Line 331C
was (Author: hhuang):
Hi Timothy,
I was able to set up a development environment where we can recreate the
problem. It crashed the following line in function
ActiveMQConnection::onException()
Pointer< Iterator > iter(
this->config->transportListeners.iterator() );
Could you please come out a fix for it? Call stack:
msvcr80d.dll!_NMSG_WRITE(int rterrnum=25) Line 198 C
msvcr80d.dll!_purecall() Line 54 + 0x7 bytes C
>
> activemq-cppud.dll!activemq::core::ActiveMQConnection::onException(const
> decaf::lang::Exception & ex={...}) Line 782 + 0x49 bytes C++
activemq-cppud.dll!activemq::transport::TransportFilter::fire(const
decaf::lang::Exception & ex={...}) Line 54 + 0x17 bytesC++
activemq-cppud.dll!activemq::transport::TransportFilter::onException(const
decaf::lang::Exception & ex={...}) Line 47 C++
activemq-cppud.dll!activemq::transport::TransportFilter::fire(const
decaf::lang::Exception & ex={...}) Line 54 + 0x17 bytesC++
activemq-cppud.dll!activemq::transport::TransportFilter::onException(const
decaf::lang::Exception & ex={...}) Line 47 C++
activemq-cppud.dll!activemq::transport::TransportFilter::fire(const
decaf::lang::Exception & ex={...}) Line 54 + 0x17 bytesC++
activemq-cppud.dll!activemq::transport::TransportFilter::onException(const
decaf::lang::Exception & ex={...}) Line 47 C++
activemq-cppud.dll!activemq::transport::inactivity::InactivityMonitor::onException(const
decaf::lang::Exception & ex={...}) Line 314 C++
activemq-cppud.dll!activemq::transport::TransportFilter::fire(const
decaf::lang::Exception & ex={...}) Line 54 + 0x17 bytesC++
activemq-cppud.dll!activemq::transport::TransportFilter::onException(const
decaf::lang::Exception & ex={...}) Line 47 C++
activemq-cppud.dll!activemq::transport::IOTransport::fire(decaf::lang::Exception
& ex={...}) Line 72 + 0x17 bytes C++
activemq-cppud.dll!activemq::transport::IOTransport::run() Line 245
C++
activemq-cppud.dll!decaf::lang::ThreadProperties::runCallback(decaf::lang::ThreadProperties
* properties=0x0eccdde8) Lin
[jira] [Comment Edited] (AMQCPP-407) Application crashes after stopping message broker
[
https://issues.apache.org/jira/browse/AMQCPP-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13289709#comment-13289709
]
Helen Huang edited comment on AMQCPP-407 at 6/5/12 8:51 PM:
Hi Timothy,
I was able to set up a development environment where we can recreate the
problem. It crashed the following line in function
ActiveMQConnection::onException()
Pointer< Iterator > iter(
this->config->transportListeners.iterator() );
Could you please come out a fix for it? Call stack:
msvcr80d.dll!_NMSG_WRITE(int rterrnum=25) Line 198 C
msvcr80d.dll!_purecall() Line 54 + 0x7 bytes C
>
> activemq-cppud.dll!activemq::core::ActiveMQConnection::onException(const
> decaf::lang::Exception & ex={...}) Line 782 + 0x49 bytes C++
activemq-cppud.dll!activemq::transport::TransportFilter::fire(const
decaf::lang::Exception & ex={...}) Line 54 + 0x17 bytesC++
activemq-cppud.dll!activemq::transport::TransportFilter::onException(const
decaf::lang::Exception & ex={...}) Line 47 C++
activemq-cppud.dll!activemq::transport::TransportFilter::fire(const
decaf::lang::Exception & ex={...}) Line 54 + 0x17 bytesC++
activemq-cppud.dll!activemq::transport::TransportFilter::onException(const
decaf::lang::Exception & ex={...}) Line 47 C++
activemq-cppud.dll!activemq::transport::TransportFilter::fire(const
decaf::lang::Exception & ex={...}) Line 54 + 0x17 bytesC++
activemq-cppud.dll!activemq::transport::TransportFilter::onException(const
decaf::lang::Exception & ex={...}) Line 47 C++
activemq-cppud.dll!activemq::transport::inactivity::InactivityMonitor::onException(const
decaf::lang::Exception & ex={...}) Line 314 C++
activemq-cppud.dll!activemq::transport::TransportFilter::fire(const
decaf::lang::Exception & ex={...}) Line 54 + 0x17 bytesC++
activemq-cppud.dll!activemq::transport::TransportFilter::onException(const
decaf::lang::Exception & ex={...}) Line 47 C++
activemq-cppud.dll!activemq::transport::IOTransport::fire(decaf::lang::Exception
& ex={...}) Line 72 + 0x17 bytes C++
activemq-cppud.dll!activemq::transport::IOTransport::run() Line 245
C++
activemq-cppud.dll!decaf::lang::ThreadProperties::runCallback(decaf::lang::ThreadProperties
* properties=0x0eccdde8) Line 137 + 0x13 bytes C++
activemq-cppud.dll!`anonymous namespace'::threadWorker(void *
arg=0x0eccdde8) Line 210 + 0x9 bytes C++
msvcr80d.dll!_callthreadstartex() Line 348 + 0xf bytes C
msvcr80d.dll!_threadstartex(void * ptd=0x0eccdb98) Line 331C
was (Author: hhuang):
Hi Timothy,
I was able to set up a development environment where we can recreate the
problem. It crashed the following line in function
ActiveMQConnection::onException()
Pointer< Iterator > iter(
this->config->transportListeners.iterator() );
Could you please come out a fix for it. Call stack:
msvcr80d.dll!_NMSG_WRITE(int rterrnum=25) Line 198 C
msvcr80d.dll!_purecall() Line 54 + 0x7 bytes C
>
> activemq-cppud.dll!activemq::core::ActiveMQConnection::onException(const
> decaf::lang::Exception & ex={...}) Line 782 + 0x49 bytes C++
activemq-cppud.dll!activemq::transport::TransportFilter::fire(const
decaf::lang::Exception & ex={...}) Line 54 + 0x17 bytesC++
activemq-cppud.dll!activemq::transport::TransportFilter::onException(const
decaf::lang::Exception & ex={...}) Line 47 C++
activemq-cppud.dll!activemq::transport::TransportFilter::fire(const
decaf::lang::Exception & ex={...}) Line 54 + 0x17 bytesC++
activemq-cppud.dll!activemq::transport::TransportFilter::onException(const
decaf::lang::Exception & ex={...}) Line 47 C++
activemq-cppud.dll!activemq::transport::TransportFilter::fire(const
decaf::lang::Exception & ex={...}) Line 54 + 0x17 bytesC++
activemq-cppud.dll!activemq::transport::TransportFilter::onException(const
decaf::lang::Exception & ex={...}) Line 47 C++
activemq-cppud.dll!activemq::transport::inactivity::InactivityMonitor::onException(const
decaf::lang::Exception & ex={...}) Line 314 C++
activemq-cppud.dll!activemq::transport::TransportFilter::fire(const
decaf::lang::Exception & ex={...}) Line 54 + 0x17 bytesC++
activemq-cppud.dll!activemq::transport::TransportFilter::onException(const
decaf::lang::Exception & ex={...}) Line 47 C++
activemq-cppud.dll!activemq::transport::IOTransport::fire(decaf::lang::Exception
& ex={...}) Line 72 + 0x17 bytes C++
activemq-cppud.dll!activemq::transport::IOTransport::run() Line 245
C++
activemq-cppud.dll!decaf::lang::ThreadProperties::runCallback(decaf::lang::ThreadProperties
* properties=0x0eccdde8) Line 137 +
[jira] [Commented] (AMQCPP-407) Application crashes after stopping message broker
[
https://issues.apache.org/jira/browse/AMQCPP-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13289709#comment-13289709
]
Helen Huang commented on AMQCPP-407:
Hi Timothy,
I was able to set up a development environment where we can recreate the
problem. It crashed the following line in function
ActiveMQConnection::onException()
Pointer< Iterator > iter(
this->config->transportListeners.iterator() );
Could you please come out a fix for it. Call stack:
msvcr80d.dll!_NMSG_WRITE(int rterrnum=25) Line 198 C
msvcr80d.dll!_purecall() Line 54 + 0x7 bytes C
>
> activemq-cppud.dll!activemq::core::ActiveMQConnection::onException(const
> decaf::lang::Exception & ex={...}) Line 782 + 0x49 bytes C++
activemq-cppud.dll!activemq::transport::TransportFilter::fire(const
decaf::lang::Exception & ex={...}) Line 54 + 0x17 bytesC++
activemq-cppud.dll!activemq::transport::TransportFilter::onException(const
decaf::lang::Exception & ex={...}) Line 47 C++
activemq-cppud.dll!activemq::transport::TransportFilter::fire(const
decaf::lang::Exception & ex={...}) Line 54 + 0x17 bytesC++
activemq-cppud.dll!activemq::transport::TransportFilter::onException(const
decaf::lang::Exception & ex={...}) Line 47 C++
activemq-cppud.dll!activemq::transport::TransportFilter::fire(const
decaf::lang::Exception & ex={...}) Line 54 + 0x17 bytesC++
activemq-cppud.dll!activemq::transport::TransportFilter::onException(const
decaf::lang::Exception & ex={...}) Line 47 C++
activemq-cppud.dll!activemq::transport::inactivity::InactivityMonitor::onException(const
decaf::lang::Exception & ex={...}) Line 314 C++
activemq-cppud.dll!activemq::transport::TransportFilter::fire(const
decaf::lang::Exception & ex={...}) Line 54 + 0x17 bytesC++
activemq-cppud.dll!activemq::transport::TransportFilter::onException(const
decaf::lang::Exception & ex={...}) Line 47 C++
activemq-cppud.dll!activemq::transport::IOTransport::fire(decaf::lang::Exception
& ex={...}) Line 72 + 0x17 bytes C++
activemq-cppud.dll!activemq::transport::IOTransport::run() Line 245
C++
activemq-cppud.dll!decaf::lang::ThreadProperties::runCallback(decaf::lang::ThreadProperties
* properties=0x0eccdde8) Line 137 + 0x13 bytes C++
activemq-cppud.dll!`anonymous namespace'::threadWorker(void *
arg=0x0eccdde8) Line 210 + 0x9 bytes C++
msvcr80d.dll!_callthreadstartex() Line 348 + 0xf bytes C
msvcr80d.dll!_threadstartex(void * ptd=0x0eccdb98) Line 331C
> Application crashes after stopping message broker
> -
>
> Key: AMQCPP-407
> URL: https://issues.apache.org/jira/browse/AMQCPP-407
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: CMS Impl
>Affects Versions: 3.4.1
> Environment: Windows xp service pack 3, ActiveMQ broker 5.3.1, apr
> 1.4.2, apr-util 1.3.9, apr iconv 1.2.1
>Reporter: Helen Huang
>Assignee: Timothy Bish
>Priority: Blocker
> Fix For: 3.4.1
>
> Attachments: AttemptedFix1.7z
>
>
> Stopping the message broker would crash our application. The following is the
> call stack of the fault thread.
> Thread 0 - System ID 672
> Entry point msvcr80!endthreadex+61
> Create time 5/24/2012 1:53:56 PM
> Time spent in user mode 0 Days 0:0:0.46
> Time spent in kernel mode 0 Days 0:0:0.78
> Function Arg 1 Arg 2 Arg 3 Source
> kernel32!InterlockedDecrement+9 00242110
> msvcrt!cexit+f 77c1 0001
> ntdll!LdrInitializeThunk+24 77c1f2a1 77c1
> ntdll!RtlDestroyEnvironment+178 0eec256d 0001
> kernel32!IsValidLocale+8eb 0003 77e8f3b0
> kernel32!ExitProcess+14 0003 0ec21a04 0003
> msvcr80!amsg_exit+5e 0003 0001
> msvcr80!exit+d 1795efe0
> user32!MessageBoxIndirectA+23a 0001 7c91005d 13946b5e
> user32!MessageBoxIndirectA+254 13946b5e 00e30850
> ntdll!RtlFreeHeap+130 0468001b 0202 1795f110
> activemq_cppu!activemq::core::ActiveMQConnection::onException+fd 1795fe24
> 7f427d47 1795fe18
> activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24
> 7f427d33 1795fe18
> activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24
> 7f427cef 1795fe18
> activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24
> 1795f60c 0ef4a264
> activemq_cppu!activemq::transport::inactivity::Inact
[jira] [Resolved] (AMQNET-388) Add compression support to the ActiveMQ ObjectMessage command.
[ https://issues.apache.org/jira/browse/AMQNET-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQNET-388. - Resolution: Fixed Fix applied in trunk and the 1.5.x branch > Add compression support to the ActiveMQ ObjectMessage command. > -- > > Key: AMQNET-388 > URL: https://issues.apache.org/jira/browse/AMQNET-388 > Project: ActiveMQ .Net > Issue Type: Improvement > Components: ActiveMQ >Affects Versions: 1.5.5 >Reporter: Timothy Bish >Assignee: Timothy Bish >Priority: Minor > Fix For: 1.5.6, 1.6.0 > > > Currently the ObjectMessage type in NMS.ActiveMQ doesn't deal with message > compression. Need to add before and after marshal / unmarshal support to > deal with the binary payload being compressed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-3868) ActiveMQ 5.6 - RAR deployment is not working on JBoss6
[ https://issues.apache.org/jira/browse/AMQ-3868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colombo Marco updated AMQ-3868: --- Fix Version/s: 5.7.0 > ActiveMQ 5.6 - RAR deployment is not working on JBoss6 > -- > > Key: AMQ-3868 > URL: https://issues.apache.org/jira/browse/AMQ-3868 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.6.0 > Environment: Windows 7 / Centos 5 either 32 and 64 bit >Reporter: Colombo Marco >Priority: Blocker > Fix For: 5.7.0 > > Attachments: boot.log, exceptions.txt > > > Upgrading rar deployment on jboss 6 from 5.5 to 5.6 produce multiple errors > due to new introduced dependencies. Major problems are on guava libraries and > jaxson. > RAR file provided with release is producing the following errors, blocking > the AS startup (see attachments). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (AMQNET-388) Add compression support to the ActiveMQ ObjectMessage command.
Timothy Bish created AMQNET-388: --- Summary: Add compression support to the ActiveMQ ObjectMessage command. Key: AMQNET-388 URL: https://issues.apache.org/jira/browse/AMQNET-388 Project: ActiveMQ .Net Issue Type: Improvement Components: ActiveMQ Affects Versions: 1.5.5 Reporter: Timothy Bish Assignee: Timothy Bish Priority: Minor Fix For: 1.5.6, 1.6.0 Currently the ObjectMessage type in NMS.ActiveMQ doesn't deal with message compression. Need to add before and after marshal / unmarshal support to deal with the binary payload being compressed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQNET-387) no iconnectionfactory implementation found for connection uri
[ https://issues.apache.org/jira/browse/AMQNET-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13289326#comment-13289326 ] Timothy Bish commented on AMQNET-387: - You'll need to then explain your setup better then because I don't understand what it is you are doing. In any event, the NMS API dll has no client logic in it, its just an API. In order to communicate with a broker you need one of the client libs. > no iconnectionfactory implementation found for connection uri > - > > Key: AMQNET-387 > URL: https://issues.apache.org/jira/browse/AMQNET-387 > Project: ActiveMQ .Net > Issue Type: Bug >Reporter: Tamilmaran >Assignee: Jim Gomes > > I'm facing the "no iconnectionfactory implementation found for connection > uri" issue on the client system.The server side which has the broker into it, > is running perfectly for topic/queue pub/sub.But the client is not working. > I have used only NMS DLL. I am not supposed to use NMS.ActiveMQ DLL. In this > case, How to get rid of this issue? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQNET-387) no iconnectionfactory implementation found for connection uri
[ https://issues.apache.org/jira/browse/AMQNET-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13289323#comment-13289323 ] Tamilmaran commented on AMQNET-387: --- no, actually in sever side itself, i am using .NET only to connect with broker. There new NMSConnectionFactory(BrokerURI) doesn't throw error. but the same throws this error on client side. > no iconnectionfactory implementation found for connection uri > - > > Key: AMQNET-387 > URL: https://issues.apache.org/jira/browse/AMQNET-387 > Project: ActiveMQ .Net > Issue Type: Bug >Reporter: Tamilmaran >Assignee: Jim Gomes > > I'm facing the "no iconnectionfactory implementation found for connection > uri" issue on the client system.The server side which has the broker into it, > is running perfectly for topic/queue pub/sub.But the client is not working. > I have used only NMS DLL. I am not supposed to use NMS.ActiveMQ DLL. In this > case, How to get rid of this issue? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQNET-387) no iconnectionfactory implementation found for connection uri
[ https://issues.apache.org/jira/browse/AMQNET-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13289315#comment-13289315 ] Timothy Bish commented on AMQNET-387: - Because the broker is not using .NET, its a Java app. > no iconnectionfactory implementation found for connection uri > - > > Key: AMQNET-387 > URL: https://issues.apache.org/jira/browse/AMQNET-387 > Project: ActiveMQ .Net > Issue Type: Bug >Reporter: Tamilmaran >Assignee: Jim Gomes > > I'm facing the "no iconnectionfactory implementation found for connection > uri" issue on the client system.The server side which has the broker into it, > is running perfectly for topic/queue pub/sub.But the client is not working. > I have used only NMS DLL. I am not supposed to use NMS.ActiveMQ DLL. In this > case, How to get rid of this issue? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQNET-387) no iconnectionfactory implementation found for connection uri
[ https://issues.apache.org/jira/browse/AMQNET-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13289309#comment-13289309 ] Tamilmaran commented on AMQNET-387: --- But then how is it working on server side alone without those DLLs? > no iconnectionfactory implementation found for connection uri > - > > Key: AMQNET-387 > URL: https://issues.apache.org/jira/browse/AMQNET-387 > Project: ActiveMQ .Net > Issue Type: Bug >Reporter: Tamilmaran >Assignee: Jim Gomes > > I'm facing the "no iconnectionfactory implementation found for connection > uri" issue on the client system.The server side which has the broker into it, > is running perfectly for topic/queue pub/sub.But the client is not working. > I have used only NMS DLL. I am not supposed to use NMS.ActiveMQ DLL. In this > case, How to get rid of this issue? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQNET-387) no iconnectionfactory implementation found for connection uri
[ https://issues.apache.org/jira/browse/AMQNET-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13289306#comment-13289306 ] Timothy Bish commented on AMQNET-387: - You must use both the NMS API assembly and one of the provider assemblies such as NMS.ActiveMQ, or NMS.Stomp you can't use the NMS API assembly alone. > no iconnectionfactory implementation found for connection uri > - > > Key: AMQNET-387 > URL: https://issues.apache.org/jira/browse/AMQNET-387 > Project: ActiveMQ .Net > Issue Type: Bug >Reporter: Tamilmaran >Assignee: Jim Gomes > > I'm facing the "no iconnectionfactory implementation found for connection > uri" issue on the client system.The server side which has the broker into it, > is running perfectly for topic/queue pub/sub.But the client is not working. > I have used only NMS DLL. I am not supposed to use NMS.ActiveMQ DLL. In this > case, How to get rid of this issue? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (AMQNET-387) no iconnectionfactory implementation found for connection uri
Tamilmaran created AMQNET-387: - Summary: no iconnectionfactory implementation found for connection uri Key: AMQNET-387 URL: https://issues.apache.org/jira/browse/AMQNET-387 Project: ActiveMQ .Net Issue Type: Bug Reporter: Tamilmaran Assignee: Jim Gomes I'm facing the "no iconnectionfactory implementation found for connection uri" issue on the client system.The server side which has the broker into it, is running perfectly for topic/queue pub/sub.But the client is not working. I have used only NMS DLL. I am not supposed to use NMS.ActiveMQ DLL. In this case, How to get rid of this issue? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-3353) Durable subscribers on durable topics don't receive messages after network disconnect
[
https://issues.apache.org/jira/browse/AMQ-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Calvo updated AMQ-3353:
---
Attachment: DurableSubscriberWithNetworkDisconnectTest.java
TEST-org.apache.activemq.usecases.DurableSubscriberWithNetworkDisconnectTest.xml
New test with 3 combinations for the maxReconnectAttemps (0,1 and -1).
It fails 13 out of 24.
Using 5.7-SNAPSHOT.
Repository Root: https://svn.apache.org/repos/asf
Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68
Revision: 1346054
Node Kind: directory
Schedule: normal
Last Changed Author: gtully
Last Changed Rev: 1345202
Last Changed Date: 2012-06-01 16:32:50 +0200 (Fri, 01 Jun 2012)
> Durable subscribers on durable topics don't receive messages after network
> disconnect
> -
>
> Key: AMQ-3353
> URL: https://issues.apache.org/jira/browse/AMQ-3353
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
>Affects Versions: 5.3.1, 5.5.0
> Environment: Windows & Linux
> JDK 1.6
>Reporter: Syed Faraz Ali
>Assignee: Gary Tully
> Fix For: 5.6.0
>
> Attachments: DurableSubscriberWithNetworkDisconnectTest.java,
> DurableSubscriberWithNetworkDisconnectTest.java,
> DurableSubscriberWithNetworkDisconnectTest.java,
> TEST-org.apache.activemq.usecases.DurableSubscriberWithNetworkDisconnectTest.xml,
>
> TEST-org.apache.activemq.usecases.DurableSubscriberWithNetworkDisconnectTest.xml,
> test-results.ods
>
>
> I've set up a durable topic with the default (persistent) delivery mode on
> one machine that is publishing a simple text message every 5 seconds. I
> created a durable subscriber that consumes messages published to the above
> topic on another machine. I am using broker to broker communication between
> the two machines.
> I start up the two programs on either machine and see the messages coming
> through to the subscriber. If I then pull the network cable to disconnect the
> network between the two machines, wait for a minute and then plug it back in,
> my subscriber doesn't receive the messages any more. I can see from the
> output that the publisher is still publishing them (Temporary topics,
> non-durable queues all continue to sync up in our production environment, it
> is only the durable topics that don't work after network reconnect)
> If I were to tweak a setting on the publisher's broker (that was introduced
> only in 5.5.0), suppressDuplicateTopicSubscriptions=false, then the topics
> work correctly after network reconnect. But this may have other unintended
> consequences and I was hoping to get a better idea of:
> - is this a known issue ? if so, then are there any specific challenges that
> have caused it not to be fixed?
> - are other people out there using durable topics and subscribers without a
> failover option that have run into this problem? What have they done to work
> around?
> Here is how my subscriber and publisher are set up:
> Topic Publisher (Machine 1)
> publisherConnection = connFactory.createConnection();
> publisherConnection.setClientID( "ProducerCliID" );
> publisherConnection.start();
> session = publisherConnection.createSession( true, -1 );
> Destination producerTopic = session.createTopic( TEST_TOPIC_NAME );
> producer = session.createProducer( (Topic)producerTopic );
>
>
>
> // On a timer, keep sending this out every 5 seconds
> String text = "HELLO " + count++;
> TextMessage msg = session.createTextMessage( text );
> System.out.println( "Sending TextMessage = " + msg.getText()
> );
> producer.send( msg );
> session.commit();
> Subscriber ( Machine 2):
> Connection clientConnection = connFactory.createConnection();
> clientConnection.setClientID("cliID");
> clientConnection.start();
> Session session = clientConnection.createSession( false,
> Session.AUTO_ACKNOWLEDGE );
> Destination topic = session.createTopic( topicName );
> MessageConsumer subscriber = session.createDurableSubscriber(
> (Topic)topic, "subName" );
> TestMessageListener msgListener = new TestMessageListener( 1000 );
> subscriber.setMessageListener( msgListener );
> .
> .
> // TestMessageListener's onMessage method simply outputs the message:
> public void onMessage(Message message)
> {
> if ( message instanceof TextMessage )
> {
> System.out.println( "Message received = " +
> ((TextMessage)message) );
> }
> }
> I can provide the jars for you to run the program if need be.
--
This message is automatically generate
