Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <1875898593.1207926103602.JavaMail.jira@brutus>
Date: Fri, 11 Apr 2008 08:01:43 -0700 (PDT)
From: "Nathan Mittler (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Updated: (AMQCPP-165) Core Dump on reconnect/open queue
In-Reply-To: <136979.1202110775567.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/activemq/browse/AMQCPP-165?page=3Dcom.atla=
ssian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nathan Mittler updated AMQCPP-165:
----------------------------------

    Fix Version/s: 2.2

> Core Dump on reconnect/open queue
> ---------------------------------
>
>                 Key: AMQCPP-165
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-165
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>    Affects Versions: 2.1.1
>         Environment: Red Hat Linux 2.4.x
>            Reporter: pfid
>            Assignee: Nathan Mittler
>             Fix For: 2.2
>
>         Attachments: sample.tar.gz
>
>
> our activemq application core dumped several times during the last days w=
hen the connection to the broker was lost. each time it was either caused b=
y the broker beeing restartet or write attempts failing (see exception belo=
w).
> in both cases the application catches a CMS exception, closes all queues =
and tries to re-open them after 60s. all activemq objects are destroyed aft=
er closing (see cleanup() from web example).
> the core dumps seemed to happen when the application trys to re-open the =
connection, but fails because the broker is still unreachable. here is the =
backtrace:
> <quote>
> #0  activemq::connector::openwire::OpenWireConnector::closeResource (this=
=3D0x8b4a268, resource=3D0x8b4dde0) at activemq/connector/openwire/OpenWire=
Connector.cpp:1200
> #1  0x080da6fc in activemq::connector::BaseConnectorResource::close (this=
=3D0x8b4dde0) at activemq/connector/BaseConnectorResource.cpp:59
> #2  0x0812ff50 in ~OpenWireSessionInfo (this=3D0x8b4dde0) at OpenWireSess=
ionInfo.h:56
> #3  0x0812d0c4 in activemq::connector::openwire::OpenWireConnector::creat=
eSession (this=3D0x8b4dde0, ackMode=3Dcms::Session::AUTO_ACKNOWLEDGE)
>     at activemq/connector/openwire/OpenWireConnector.cpp:281
> #4  0x080e86c1 in activemq::core::ActiveMQConnection::createSession (this=
=3D0x8b4ded0, ackMode=3D137247624) at activemq/core/ActiveMQConnection.cpp:=
98
> #5  0x08059c19 in ActiveMqQueue::open (this=3D0x8b1d6b0, aQueueName=3D0x8=
ab925c "outqueue", aMode=3DActiveMqQueue::modeWrite, aListenMode=3D0) at ac=
tivemqqueue.cc:335
> </quote>
> Debuggin shows that at activemq/connector/openwire/OpenWireConnector.cpp:=
1200
> 1200:  dataStructure =3D session->getSessionInfo()->getSessionId();
> the session object is null, the previously dyn-casted resource object how=
ever is not null:
> <quote>
> (gdb) p session
> $1 =3D (activemq::connector::openwire::OpenWireSessionInfo *) 0x0
> (gdb) p resource
> $2 =3D (class activemq::connector::ConnectorResource *) 0x8b4dde0</quote>
> (corrupt memory?)
> Exception when write attempts fail:
> <quote>No valid response received for command: Begin Class =3D ActiveMQTe=
xtMessage Begin Class =3D ActiveMQMessageBase  Value of ackHandler =3D 0  V=
alue of redeliveryCount =3D 0  Value of properties =3D Begin Class Primitiv=
eMap: Begin Class PrimitiveMap:  Begin Class =3D Message  Value of Message:=
:ID_MESSAGE =3D 0  Value of ProducerId is Below: Begin Class =3D ProducerId=
  Value of ProducerId::ID_PRODUCERID =3D 123  Value of ConnectionId =3D 0c0=
0f32b-2269-4e0f-ace1-13fd0414b4b5  Value of Value =3D 0  Value of SessionId=
 =3D 0 No Data for Class BaseDataStructure End Class =3D ProducerId   Value=
 of Destination is Below: Begin Class =3D ActiveMQQueue Begin Class =3D Act=
iveMQDestination  Value of exclusive =3D false  Value of ordered =3D false =
 Value of advisory =3D false  Value of orderedTarget =3D coordinator  Value=
 of physicalName =3D ffs_out  Value of options =3D Begin Class activemq::ut=
il::Properties: End Class activemq::util::Properties:  No Data for Class Ba=
seDataStructure End Class =3D ActiveMQDestination End Class =3D ActiveMQQue=
ue   Value of TransactionId is Below:    Object is NULL  Value of OriginalD=
estination is Below:    Object is NULL  Value of MessageId is Below: Begin =
Class =3D MessageId  Value of MessageId::ID_MESSAGEID =3D 110  Value of Pro=
ducerId is Below: Begin Class =3D ProducerId  Value of ProducerId::ID_PRODU=
CERID =3D 123  Value of ConnectionId =3D 0c00f32b-2269-4e0f-ace1-13fd0414b4=
b5  Value of Value =3D 0  Value of SessionId =3D 0 No Data for Class BaseDa=
taStructure End Class =3D ProducerId   Value of ProducerSequenceId =3D 4  V=
alue of BrokerSequenceId =3D 0 No Data for Class BaseDataStructure End Clas=
s =3D MessageId   Value of OriginalTransactionId is Below:    Object is NUL=
L  Value of GroupID =3D   Value of GroupSequence =3D 0  Value of Correlatio=
nId =3D   Value of Persistent =3D 1  Value of Expiration =3D 1201683817204 =
 Value of Priority =3D 4  Value of ReplyTo is Below:    Object is NULL  Val=
ue of Timestamp =3D 1201676617204  Value of Type =3D   Value of Content[0] =
=3D , check broker.</quote>
> Versions:
> Activemq-cpp-2.1.1
> ActiveMq Broker 4.1.1
> the application handles 17 write-mode queues, with a rather low messages/=
second rate.
> Using 5.0.0 broker instead of 4.1.1 would most likely solve this problem,=
 since the failed write attempts problem only occurs with 4.1.1 broker (i r=
eported this bug before, but it seemed like no one was interested in taking=
 care of it). however, the broker 5.0.0 won't start with preconfigured JAAS=
 queues, so its not an option and we have to stick with 4.1.1. i will try t=
he latest snapshot these days, however i dont feel good when using a snapsh=
ot server in production environment.

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