Mailing-List: contact activemq-dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: activemq-dev@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
From: "Naveen Rawat" <naveen@in.effectsoft.com>
To: activemq-dev@geronimo.apache.org, user@activemq.codehaus.org
Subject: SIGSEGV in openwire synchronous Q test 
Date: Thu, 06 Jul 2006 12:35:28 +0200
Mime-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <courier.44ACE770.0000102A@effectsoft.com>


Hi all 


I tried out the openwire test for synchronous queues availabe in
[source_060515.zip (339 kb)] and [patch_060518.zip (29 kb)] 

from http://issues.apache.org/activemq//browse/AMQ-656 


I segregated the test into two : sender and receiver client, sender 
messaging to receiver. 

The clients are capably maintaining the persistency with the pending 
queue-hold messages --- to the exception that the receiver receives a 
SIGSEGV signal if the queue have nothing to offer for the receiver client. 
The receiver also terminates with this signal when all the pending messags 
are through with the receiver. The GDB output when queue has nothing for 
receiver says - 

 --------------------------------------------------------------------------- 

Program received signal SIGSEGV, Segmentation fault.
apache::activemq::MessageConsumer::autoAcknowledge (this=0x80ff058, 
message=@0xbf96f2d4)
    at /home/nrawat/openwire/src/main/cpp/activemq/MessageConsumer.cpp:225
225             activeMessage->setAcknowledger( smartify(this) ) ; 

 --------------------------------------------------------------------------- 


Is everything fine with autoAcknowledge? 

 
Hearty Regards,
Naveen Rawat 


XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 

My AMQ is running as - 

 -------------------
ACTIVEMQ_HOME: /home/nrawat/incubator-activemq-4.0
Loading message broker from: xbean:activemq.xml
Created MBeanServer with ID: da6bf4:10c44471e46:-8000:kuwix:1
INFO  BrokerService                  - ActiveMQ 4.0 JMS Message Broker 
(localhost) is starting
INFO  BrokerService                  - For help or more information please 
see: http://incubator.apache.org/activemq/
RMIConnectorServer started at: 
service:jmx:rmi://kuwix/jndi/rmi://localhost:1099/jmxrmi
INFO  ManagementContext              - JMX consoles can connect to 
service:jmx:rmi://kuwix/jndi/rmi://localhost:1099/jmxrmi
INFO  JDBCPersistenceAdapter         - Database driver recognized: 
[apache_derby_embedded_jdbc_driver]
INFO  JournalPersistenceAdapter      - Journal Recovery Started from: Active 
Journal: using 5 x 20.0 Megs at: 
/home/nrawat/incubator-activemq-4.0/activemq-data/journal
INFO  JournalPersistenceAdapter      - Journal Recovered: 0 message(s) in 
transactions recovered.
INFO  TransportServerThreadSupport   - Listening for connections at: 
tcp://kuwix:61666
WARN  MulticastDiscoveryAgent        - brokerName not set
INFO  TransportConnector             - Connector default Started
INFO  TransportServerThreadSupport   - Listening for connections at: 
tcp://kuwix:61633?wireFormat=stomp
INFO  TransportConnector             - Connector stomp Started
INFO  NetworkConnector               - Network Connector default Started
INFO  BrokerService                  - ActiveMQ JMS Message Broker 
(localhost, ID:kuwix-1335-1152196745226-1:0) started
 ------------------