[
https://issues.apache.org/activemq/browse/AMQCPP-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41397#action_41397
]
Ismail Mehdi commented on AMQCPP-170:
-------------------------------------
Here's the stack for 2.1:
#5 0x078e8ae4 in
activemq::connector::openwire::OpenWireConnector::createProducer
(this=0xa04a158, destination=0x9fd0568, session=0xccbb428) at
activemq/connector/openwire/OpenWireConnector.cpp:752
#6 0x078adb06 in activemq::core::ActiveMQSession::createProducer
(this=0x844f890, destination=0x9fd0568) at activemq/core/ActiveMQSession.cpp:348
> SEGV in activemq::connector::openwire::OpenWireConnector::createProducer
> ------------------------------------------------------------------------
>
> Key: AMQCPP-170
> URL: https://issues.apache.org/activemq/browse/AMQCPP-170
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: Openwire
> Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3
> Environment: Linux 2.6.9-42.ELsmp #1 SMP Sat Aug 12 09:39:11 CDT 2006
> i686 i686 i386 GNU/Linux
> Reporter: Ismail Mehdi
> Assignee: Nathan Mittler
>
> Client setup is a JMS client sending messages to a C++ process with a
> timeout. Under heavy load the C++ process does not reply fast enough and the
> java client gives-up.
> If the connection is dropped while the C++ is inside of
> OpenWireConnector::createProducer, an exception is thrown and the cleanup
> code causes a segv in:
> activemq/connector/openwire/OpenWireConnector.cpp:752
> (this is for CMS 2.1)
> reproduced for 2.1.3 as well. line 679 for 2.1.3
> Fix is pretty straightforward, do not delete the producerInfo twice. The
> first time it is done in producer should be sufficient.
> Alternatively, I imagine setting producerInfo to 0 once it is deleted would
> avoid the crash as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
