[jira] [Commented] (AMQ-6075) javax.jms.InvalidClientIDException: Broker:… already connected
[ https://issues.apache.org/jira/browse/AMQ-6075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16374284#comment-16374284 ] Rajesh Malla commented on AMQ-6075: --- Can anybody suggest whether there is fix available for this InvalidClientIDException ? We are using activemq 5.12.3 version and facing same exception. Can we apply above solution provided by E[~kudi]. Thank you > javax.jms.InvalidClientIDException: Broker:… already connected > -- > > Key: AMQ-6075 > URL: https://issues.apache.org/jira/browse/AMQ-6075 > Project: ActiveMQ > Issue Type: Bug > Components: activemq-pool >Affects Versions: 5.12.1 > Environment: OS：Windows Server 2012 >Reporter: mq >Priority: Critical > > We have a two node network brokers set up. it can work fine two or three > days. Suddenly, every broker will try to create connection to each other, but > because > There are already has connected to each other, so it will throw a > “javax.jms.InvalidClientIDException”.The brokers will retry after 6 second, > and the same exception will happened. > activemq.log > 1:02:54,925 | INFO | Establishing network connection from > vm://MQServer1?async=false to tcp://MQServer-2:61618 | > org.apache.activemq.network.DiscoveryNetworkConnector | > Notifier-MulticastDiscoveryAgent-listener:DiscoveryNetworkConnector:NC:BrokerService[MQServer1] > 1:02:55,097 | WARN | Failed to add Connection > MQServer1->MQServer2-123456-123456788990-123:1 due to > javax.jms.InvalidClientIDException: Broker: MQServer1 - Client: > NC_MQServer2_inbound_MQServer1 already connected from vm://MQServer1#2 | > org.apache.activemq.broker.TransportConnection | > triggerStartAsyncNetworkBridgeCreation: > remoteBroker=tcp://MQServer-2/190.100.100.11:61618@56430, localBroker= > vm://MQServer1#4 > 1:02:55,097 | INFO | Network connection between vm://MQServer1#4 and > tcp://MQServer-2/190.100.100.11:61618@56430 shutdown due to a local error: > javax.jms.InvalidClientIDException: Broker: MQServer1 - Client: > NC_MQServer2_inbound_MQServer1 already connected from vm://MQServer1#2 | > org.apache.activemq.network.DemandForwardingBridgeSupport | > triggerStartAsyncNetworkBridgeCreation: > remoteBroker=tcp://MQServer-2/190.100.100.11:61618@56430, localBroker= > vm://MQServer1#4 > 1:02:55,144 | INFO | MQServer1 bridge to MQServer2 stopped | > org.apache.activemq.network.DemandForwardingBridgeSupport | ActiveMQ > BrokerService[MQServer1] Task-2043 > wrapper.log > INFO | jvm 1| 1:02:55 | INFO | Establishing network connection from > vm://MQServer1?async=false to tcp://MQServer-2:61618 > INFO | jvm 1| 1:02:55 | WARN | Failed to add Connection > MQServer1->MQServer2-123456-123456788990-123:1 due to > javax.jms.InvalidClientIDException: Broker: MQServer1 - Client: > NC_MQServer2_inbound_MQServer1 already connected from vm://MQServer1#2 > INFO | jvm 1| 1:02:55 | INFO | Network connection between > vm://MQServer1#4 and tcp://MQServer-2/190.100.100.11:61618@56430 shutdown due > to a local error: javax.jms.InvalidClientIDException: Broker: MQServer1 - > Client: NC_MQServer2_inbound_MQServer1 already connected from vm://MQServer1#2 > INFO | jvm 1| 1:02:55 | INFO | MQServer1 bridge to MQServer2 stopped -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMQ-6897) synchronous request and reply not working when specifying dynamic include queue
[
https://issues.apache.org/jira/browse/AMQ-6897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajesh Malla updated AMQ-6897:
--
Description:
We are using activemq with camel for request and reply pattern. reply will come
to temperary queue.
whenever we are including specific queues to networkconnector, messages are not
coming to temp queue, where as when removing dynamica included queue in
networkconnector it is working.
how to proceed with this ? . how to give pattern to TEMP queue.
we tried with below pattern still it does not work. please help us
even : bridgeTempDestinations as true
networkConnector.addDynamicallyIncludedDestination(new ActiveMQTempQueue("ID:
*")) ;
was:
We are using activemq with camel for request and reply pattern. reply will come
to temperary queue.
whenever we are including specific queues to networkconnector, messages are not
coming to temp queue, where as when removing dynamica included queue in
networkconnector it is working.
how to proceed with this ? . how to give pattern to TEMP queue.
we tried with below pattern still it does not work. please help us
networkConnector.addDynamicallyIncludedDestination(new
ActiveMQTempQueue("ID:\\*")) ;
> synchronous request and reply not working when specifying dynamic include
> queue
> ---
>
> Key: AMQ-6897
> URL: https://issues.apache.org/jira/browse/AMQ-6897
> Project: ActiveMQ
> Issue Type: Bug
> Components: activemq-camel, activemq-pool
>Affects Versions: 5.10.2, 5.12.3
>Reporter: Rajesh Malla
>Priority: Major
>
> We are using activemq with camel for request and reply pattern. reply will
> come to temperary queue.
> whenever we are including specific queues to networkconnector, messages are
> not coming to temp queue, where as when removing dynamica included queue in
> networkconnector it is working.
> how to proceed with this ? . how to give pattern to TEMP queue.
> we tried with below pattern still it does not work. please help us
> even : bridgeTempDestinations as true
> networkConnector.addDynamicallyIncludedDestination(new ActiveMQTempQueue("ID:
> *")) ;
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMQ-6897) synchronous request and reply not working when specifying dynamic include queue
Rajesh Malla created AMQ-6897:
-
Summary: synchronous request and reply not working when specifying
dynamic include queue
Key: AMQ-6897
URL: https://issues.apache.org/jira/browse/AMQ-6897
Project: ActiveMQ
Issue Type: Bug
Components: activemq-camel, activemq-pool
Affects Versions: 5.12.3, 5.10.2
Reporter: Rajesh Malla
We are using activemq with camel for request and reply pattern. reply will come
to temperary queue.
whenever we are including specific queues to networkconnector, messages are not
coming to temp queue, where as when removing dynamica included queue in
networkconnector it is working.
how to proceed with this ? . how to give pattern to TEMP queue.
we tried with below pattern still it does not work. please help us
networkConnector.addDynamicallyIncludedDestination(new
ActiveMQTempQueue("ID:\\*")) ;
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMQ-6885) NetworkConnector working only in forward [ not working in reverse ]
Rajesh Malla created AMQ-6885:
-
Summary: NetworkConnector working only in forward [ not working in
reverse ]
Key: AMQ-6885
URL: https://issues.apache.org/jira/browse/AMQ-6885
Project: ActiveMQ
Issue Type: Bug
Components: activemq-camel, activemq-pool
Affects Versions: 5.12.3
Reporter: Rajesh Malla
We are using request/reply message pattern : *Broker1 <- -> Broker2
-> Consumer*
producer sending request message to Broker1, using n/w connector
[DiscoveryNetworkConnector] message forward to Broker2. Consumer who is
receiving message from Broker2 and responding to Broker2. Till this part is
working, which should further forward to Broker1 which is not happening.
Broker1 creating temp-queue and listening on that, same temp-queue name created
in broker2 and sends to Consumer.
When consumer is responding to that broker2 - temp-queue, here messages are not
moving to Broker1.
1) we are using http transport connectors
2) broker1 -> broker2 [prefetch=1000 default], DiscoveryNetworkConnector
3) broker -> consumer [queuePrefetch = 0 working by applying patch of
MessagePull from AMQ-6877]
4) components : servicemix 5.6.0 [ AMQ 5.12.3, CAMEL-JMS 2.16.2], *jdk 1.8*
5) we are using n/w connectors
broker1 -> broker2 [httpconnector]
broker2 -> broker1 [httpconnector]
Code adding networkconnector :
URI uri = new URI("static://" + server.getUrl());
NetworkConnector networkConnector = new DiscoveryNetworkConnector(uri);
networkConnector.setBrokerURL(server.getUrl());
for (String queueName : listOfQueues)
networkConnector.addDynamicallyIncludedDestination(new
ActiveMQQueue(queueName));
for (String queueName : excludedQueues)
networkConnector.addExcludedDestination(new ActiveMQQueue(queueName));
networkConnector.setName(uniqueName);
networkConnector.setPassword(pwd);
networkConnector.setUserName(username);
broker.addNetworkConnector(networkConnector);
activemq.xml :
http://activemq.apache.org/schema/core;
sslContext="mainsslConxt"
persistent="false"
populateJMSXUserID="true">
http://0.0.0.0:port1; />
https://0.0.0.0:port2; />
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMQ-6877) http connector - queuePrefetch=0 not working
[ https://issues.apache.org/jira/browse/AMQ-6877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16307371#comment-16307371 ] Rajesh Malla commented on AMQ-6877: --- Thank you for suggestion, we found change-set for : https://issues.apache.org/jira/browse/AMQ-6823 this is https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=blobdiff;f=activemq-client/src/main/java/org/apache/activemq/command/MessagePull.java;h=aa5a279e071c66c53ed83d966915df6d877600e5;hp=57a25f987a1f7d7551cc705e7cf1d471271ce199;hb=eccbd75;hpb=e2eabeb1c2a8234d2763238eae8a2a143e1860a6 which is only on MessagePull.java - [ *implements TransientInitializer & override of initTransients method* ] so we just want to confirm whether this is the only changeset or any other ? If there are other changes can you please share us that commit set. > http connector - queuePrefetch=0 not working > > > Key: AMQ-6877 > URL: https://issues.apache.org/jira/browse/AMQ-6877 > Project: ActiveMQ > Issue Type: Bug > Components: activemq-camel, JMS client >Affects Versions: 5.12.1, 5.13.1, 5.12.3, 5.13.2 >Reporter: Rajesh Malla > Fix For: 5.15.1 > > Attachments: SimpleJMS.java, pom.xml > > > We have activemq-broker running with 5.12.1 version, attached SimpleJMS.java > & pom.xml [ uses 5.12.3 version of activemq-http, activemq-client]. > In the broker activemq.xml - we have enabled http transport connector > http://0.0.0.0:22001; /> > Now > 1) in our SimpleJMS.java - if we are removing > ((ActiveMQConnection) > connection).getPrefetchPolicy().setQueuePrefetch(0); > then we are able to send & receive message successfully. > If we are setting QueuePrefetch to 0 then Producer is sending message > where as Consumer not receiving message :( > same SimpleJMS with & without QueuePrefetch=0 is working properly with 5.8.0 > version & 5.15.2 latest release. > all our activemq-http,activemq-client, broker all are in same version. > with 5.8.0 - we used jdk 1.6 > with 5.15.2 - we used jdk 1.8 > with 5.12.3[client] -> 5.12.1[broker] we tried jdk 1.8 & jdk 1.7 but no luck. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMQ-6878) backward compatibility issues consumer [ 5.8.0 ] -> AMQ broker [5.12.3 ]
Rajesh Malla created AMQ-6878: - Summary: backward compatibility issues consumer [ 5.8.0 ] -> AMQ broker [5.12.3 ] Key: AMQ-6878 URL: https://issues.apache.org/jira/browse/AMQ-6878 Project: ActiveMQ Issue Type: Bug Components: AMQP, JMS client Affects Versions: 5.8.0 Reporter: Rajesh Malla Attachments: SimpleJMS.java, pom.xml Our client is in 5.8.0 version of ACtiveMQ, where as broker is moved to 5.12.3 version. Now consumer is not receiving messages. We found similar AMQ defect, however solution is not provided : https://issues.apache.org/jira/browse/AMQ-5023 We found that org.apache.activemq.command.Message.java - introduced new field jmsXGroupFirstForConsumer. There are some other reasons also. So can you please provide us any patch on 5.8.0 or lower versions of AMQ to consume message of AMQ 5.9 <= versions. If we are using 5.15.2 broker, then on consumer [ 5.8.0 with jdk 1.6] side we are getting below : Exception in thread "ActiveMQ Transport: HTTP Reader http://localhost:22001; com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter$UnknownFieldException: No such field org.apache.activemq.command.ActiveMQObjectMessage.jmsXGroupFirstForConsumer Debugging information field : jmsXGroupFirstForConsumer class : org.apache.activemq.command.ActiveMQObjectMessage required-type : org.apache.activemq.command.ActiveMQObjectMessage converter-type : com.thoughtworks.xstream.converters.reflection.ReflectionConverter path: /org.apache.activemq.command.MessageDispatch/message/jmsXGroupFirstForConsumer line number : 49 class[1]: org.apache.activemq.command.MessageDispatch version : null --- at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.determineType(AbstractReflectionConverter.java:453) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.doUnmarshal(AbstractReflectionConverter.java:294) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.unmarshal(AbstractReflectionConverter.java:234) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.unmarshallField(AbstractReflectionConverter.java:355) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.doUnmarshal(AbstractReflectionConverter.java:306) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.unmarshal(AbstractReflectionConverter.java:234) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1058) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1042) at com.thoughtworks.xstream.XStream.fromXML(XStream.java:913) at com.thoughtworks.xstream.XStream.fromXML(XStream.java:904) at org.apache.activemq.transport.xstream.XStreamWireFormat.unmarshalText(XStreamWireFormat.java:53) at org.apache.activemq.transport.util.TextWireFormat.unmarshal(TextWireFormat.java:56) at org.apache.activemq.transport.http.HttpClientTransport.run(HttpClientTransport.java:190) at java.lang.Thread.run(Thread.java:682) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMQ-6877) http connector - queuePrefetch=0 not working
[ https://issues.apache.org/jira/browse/AMQ-6877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16305960#comment-16305960 ] Rajesh Malla commented on AMQ-6877: --- Thank you Timothy Bish, we are using service mix which is tightly coupled with 5.12.3 version of AMQ. Can you please provide us any patch / work around [ any customizations/extending classes ] for this so that it is very helpful for us. > http connector - queuePrefetch=0 not working > > > Key: AMQ-6877 > URL: https://issues.apache.org/jira/browse/AMQ-6877 > Project: ActiveMQ > Issue Type: Bug > Components: activemq-camel, JMS client >Affects Versions: 5.12.1, 5.13.1, 5.12.3, 5.13.2 >Reporter: Rajesh Malla > Fix For: 5.15.1 > > Attachments: SimpleJMS.java, pom.xml > > > We have activemq-broker running with 5.12.1 version, attached SimpleJMS.java > & pom.xml [ uses 5.12.3 version of activemq-http, activemq-client]. > In the broker activemq.xml - we have enabled http transport connector > http://0.0.0.0:22001; /> > Now > 1) in our SimpleJMS.java - if we are removing > ((ActiveMQConnection) > connection).getPrefetchPolicy().setQueuePrefetch(0); > then we are able to send & receive message successfully. > If we are setting QueuePrefetch to 0 then Producer is sending message > where as Consumer not receiving message :( > same SimpleJMS with & without QueuePrefetch=0 is working properly with 5.8.0 > version & 5.15.2 latest release. > all our activemq-http,activemq-client, broker all are in same version. > with 5.8.0 - we used jdk 1.6 > with 5.15.2 - we used jdk 1.8 > with 5.12.3[client] -> 5.12.1[broker] we tried jdk 1.8 & jdk 1.7 but no luck. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMQ-6877) http connector - queuePrefetch=0 not working
[ https://issues.apache.org/jira/browse/AMQ-6877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajesh Malla updated AMQ-6877: -- Description: We have activemq-broker running with 5.12.1 version, attached SimpleJMS.java & pom.xml [ uses 5.12.3 version of activemq-http, activemq-client]. In the broker activemq.xml - we have enabled http transport connector http://0.0.0.0:22001; /> Now 1) in our SimpleJMS.java - if we are removing ((ActiveMQConnection) connection).getPrefetchPolicy().setQueuePrefetch(0); then we are able to send & receive message successfully. If we are setting QueuePrefetch to 0 then Producer is sending message where as Consumer not receiving message :( same SimpleJMS with & without QueuePrefetch=0 is working properly with 5.8.0 version & 5.15.2 latest release. all our activemq-http,activemq-client, broker all are in same version. with 5.8.0 - we used jdk 1.6 with 5.15.2 - we used jdk 1.8 with 5.12.3[client] -> 5.12.1[broker] we tried jdk 1.8 & jdk 1.7 but no luck. was: We have activemq-broker running with 5.12.1 version, attached SimpleJMS.java & pom.xml [ uses 5.12.3 version of activemq-http, activemq-client]. In the broker activemq.xml - we have enabled http transport connector http://0.0.0.0:22001; /> Now 1) in our SimpleJMS.java - if we are removing ((ActiveMQConnection) connection).getPrefetchPolicy().setQueuePrefetch(0); then we are able to send & receive message successfully. If we are setting QueuePrefetch to 0 then Producer is sending message where as Consumer not receiving message :( same SimpleJMS is working properly with 5.8.0 version & 5.15.2 latest release. all our activemq-http,activemq-client, broker all are in same version. with 5.8.0 - we used jdk 1.6 with 5.15.2 - we used jdk 1.8 with 5.12.3[client] -> 5.12.1[broker] we tried jdk 1.8 & jdk 1.7 but no luck. > http connector - queuePrefetch=0 not working > > > Key: AMQ-6877 > URL: https://issues.apache.org/jira/browse/AMQ-6877 > Project: ActiveMQ > Issue Type: Bug > Components: activemq-camel, JMS client >Affects Versions: 5.12.1, 5.13.1, 5.12.3, 5.13.2 >Reporter: Rajesh Malla > Attachments: SimpleJMS.java, pom.xml > > > We have activemq-broker running with 5.12.1 version, attached SimpleJMS.java > & pom.xml [ uses 5.12.3 version of activemq-http, activemq-client]. > In the broker activemq.xml - we have enabled http transport connector > http://0.0.0.0:22001; /> > Now > 1) in our SimpleJMS.java - if we are removing > ((ActiveMQConnection) > connection).getPrefetchPolicy().setQueuePrefetch(0); > then we are able to send & receive message successfully. > If we are setting QueuePrefetch to 0 then Producer is sending message > where as Consumer not receiving message :( > same SimpleJMS with & without QueuePrefetch=0 is working properly with 5.8.0 > version & 5.15.2 latest release. > all our activemq-http,activemq-client, broker all are in same version. > with 5.8.0 - we used jdk 1.6 > with 5.15.2 - we used jdk 1.8 > with 5.12.3[client] -> 5.12.1[broker] we tried jdk 1.8 & jdk 1.7 but no luck. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMQ-6877) http connector - queuePrefetch=0 not working
[ https://issues.apache.org/jira/browse/AMQ-6877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajesh Malla updated AMQ-6877: -- Component/s: JMS client > http connector - queuePrefetch=0 not working > > > Key: AMQ-6877 > URL: https://issues.apache.org/jira/browse/AMQ-6877 > Project: ActiveMQ > Issue Type: Bug > Components: activemq-camel, JMS client >Affects Versions: 5.12.1, 5.13.1, 5.12.3, 5.13.2 >Reporter: Rajesh Malla > Attachments: SimpleJMS.java, pom.xml > > > We have activemq-broker running with 5.12.1 version, attached SimpleJMS.java > & pom.xml [ uses 5.12.3 version of activemq-http, activemq-client]. > In the broker activemq.xml - we have enabled http transport connector > http://0.0.0.0:22001; /> > Now > 1) in our SimpleJMS.java - if we are removing > ((ActiveMQConnection) > connection).getPrefetchPolicy().setQueuePrefetch(0); > then we are able to send & receive message successfully. > If we are setting QueuePrefetch to 0 then Producer is sending message > where as Consumer not receiving message :( > same SimpleJMS is working properly with 5.8.0 version & 5.15.2 latest release. > all our activemq-http,activemq-client, broker all are in same version. > with 5.8.0 - we used jdk 1.6 > with 5.15.2 - we used jdk 1.8 > with 5.12.3[client] -> 5.12.1[broker] we tried jdk 1.8 & jdk 1.7 but no luck. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMQ-6877) http connector - queuePrefetch=0 not working
Rajesh Malla created AMQ-6877: - Summary: http connector - queuePrefetch=0 not working Key: AMQ-6877 URL: https://issues.apache.org/jira/browse/AMQ-6877 Project: ActiveMQ Issue Type: Bug Components: activemq-camel Affects Versions: 5.13.2, 5.12.3, 5.13.1, 5.12.1 Reporter: Rajesh Malla Attachments: SimpleJMS.java, pom.xml We have activemq-broker running with 5.12.1 version, attached SimpleJMS.java & pom.xml [ uses 5.12.3 version of activemq-http, activemq-client]. In the broker activemq.xml - we have enabled http transport connector http://0.0.0.0:22001; /> Now 1) in our SimpleJMS.java - if we are removing ((ActiveMQConnection) connection).getPrefetchPolicy().setQueuePrefetch(0); then we are able to send & receive message successfully. If we are setting QueuePrefetch to 0 then Producer is sending message where as Consumer not receiving message :( same SimpleJMS is working properly with 5.8.0 version & 5.15.2 latest release. all our activemq-http,activemq-client, broker all are in same version. with 5.8.0 - we used jdk 1.6 with 5.15.2 - we used jdk 1.8 with 5.12.3[client] -> 5.12.1[broker] we tried jdk 1.8 & jdk 1.7 but no luck. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMQ-5023) Upgrade from activeMq 5.7 to 5.9
[
https://issues.apache.org/jira/browse/AMQ-5023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16282888#comment-16282888
]
Rajesh Malla commented on AMQ-5023:
---
Timothy Bish,
by looking at this error, I have one question, If our active mq server is in
one version and client is with different version. Can we test http connection
between these two ?
Lets suppose my active mq broker is with 5.12.3 version, where as my active mq
client is in 5.8.0 version. Can I test ?
because my client is failed with above error message.
Please help me answer to the above question.
> Upgrade from activeMq 5.7 to 5.9
>
>
> Key: AMQ-5023
> URL: https://issues.apache.org/jira/browse/AMQ-5023
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
>Affects Versions: 5.9.0
>Reporter: Pankaj
>Priority: Blocker
>
> Hi,
> I am trying to upgrade my broker from 5.7 to 5.9 and my existing consumers
> using
> activemq-all-5.7.0.jar(http://mvnrepository.com/artifact/org.apache.activemq/activemq-all)
> started failing with following error:
> 2014-02-04 15:22:31,063 WARN
> org.springframework.jms.connection.CachingConnectionFactory:301 - Encountered
> a JMSException - resetting the underlying JMS Connection
> javax.jms.JMSException: Channel was inactive for too (>3) long:
> http://localhost/
> at
> org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:49)
> at
> org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1949)
> at
> org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:1966)
> at
> org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101)
> at
> org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:126)
> at
> org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101)
> at
> org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:295)
> at
> org.apache.activemq.transport.AbstractInactivityMonitor$4.run(AbstractInactivityMonitor.java:209)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> Caused by: org.apache.activemq.transport.InactivityIOException: Channel was
> inactive for too (>3) long: http://localhost/
> ... 4 more
> 2014-02-04 15:22:31,064 INFO
> org.springframework.jms.listener.DefaultMessageListenerContainer:893 -
> Successfully refreshed JMS Connection
> javax.jms.JMSException: Channel was inactive for too (>3) long:
> http://localhost/
> at
> org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:49)
> at
> org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1949)
> at
> org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:1966)
> at
> org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101)
> at
> org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:126)
> at
> org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101)
> at
> org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:295)
> at
> org.apache.activemq.transport.AbstractInactivityMonitor$4.run(AbstractInactivityMonitor.java:209)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> Caused by: org.apache.activemq.transport.InactivityIOException: Channel was
> inactive for too (>3) long: http://localhost/
> ... 4 more
> 2014-02-04 15:22:31,203 INFO
> org.apache.activemq.transport.http.HttpClientTransport:260 - Broker Servlet
> supports GZip compression.
> 2014-02-04 15:22:31,206 INFO
> org.springframework.jms.connection.CachingConnectionFactory:291 - Established
> shared JMS Connection: ActiveMQConnection
> {id=ID:pankajarora-PC-65176-1391555324715-2:10,clientId=null,started=false}
> Exception in thread "ActiveMQ Transport: HTTP Reader http://localhost/;
> com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter$UnknownFieldException:
> No such field
> org.apache.activemq.command.ActiveMQTextMessage.jmsXGroupFirstForConsumer
> Debugging information
> field : jmsXGroupFirstForConsumer
> class : org.apache.activemq.command.ActiveMQTextMessage
> required-type : org.apache.activemq.command.ActiveMQTextMessage
> converter-type :
>
