activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nathan Mittler (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AMQCPP-137) Exception in ResponseCorrelator::onCommand()
Date Sun, 30 Sep 2007 10:26:23 GMT

     [ https://issues.apache.org/activemq/browse/AMQCPP-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Nathan Mittler updated AMQCPP-137:
----------------------------------

    Fix Version/s:     (was: 2.2)
                   2.1.1

> Exception in ResponseCorrelator::onCommand() 
> ---------------------------------------------
>
>                 Key: AMQCPP-137
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-137
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>          Components: CMS Impl
>    Affects Versions: 2.0.1
>         Environment: Win XP
>            Reporter: Greg Griffin
>            Assignee: Timothy Bish
>            Priority: Minor
>             Fix For: 2.1.1
>
>
> EXCEPTION:
> ResponseCorrelator::onCommand() - received unknown response for request: 179414
> Exception: writing msg
> response from futureResponse was invalid
> response from futureResponse was invalid
>         FILE: ..\src\main\activemq\transport\ResponseCorrelator.cpp, LINE: 145
>         FILE: ..\src\main\activemq\transport\ResponseCorrelator.cpp, LINE: 152
>         FILE: ..\src\main\activemq\connector\openwire\OpenWireFormatNegotiator.cpp, LINE:
105
>         FILE: ..\src\main\activemq\connector\openwire\OpenWireConnector.cpp, LINE: 1468
>         FILE: ..\src\main\activemq\connector\openwire\OpenWireConnector.cpp, LINE: 928
>         FILE: ..\src\main\activemq\core\ActiveMQSession.cpp, LINE: 703
>         FILE: ..\src\main\activemq\core\ActiveMQProducer.cpp, LINE: 194
>         FILE: ..\src\main\activemq\core\ActiveMQProducer.cpp, LINE: 149
> CODE SNIPPET:
> 	try {
> 		msgBytes = session->createBytesMessage();
> 		msgBytes->writeInt(time);
> 		msgBytes->writeByte(type);
> 		msgBytes->writeDouble(price);
> 		msgBytes->writeLong(size);
> 		key.insert(0,topicBase);
> 		tmpTopic = getTopic( key );
> 		publisher->send(tmpTopic, msgBytes);
> 		delete msgBytes;
> 	} 
> 	catch (CMSException& e) {
>         std::cerr << "Exception: writing msg" << endl;
>         messenger->onException(e);
> 		exit(-1);
>         return;
>     }
> Exception happened in code that has been processing hundreds of msgs per second for 5
hours a day, no problem. But occurred during time when had a runaway java process taking all
of one CPU and lot's of memory.
> No msgs in broker (4.1.1) logs

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


Mime
View raw message