Was that error happening when you first saw the behavior you first asked
about? Are you saying that these are related, or that they're two unrelated
issues? I can't see anything obvious about this exception that I would
expect to result in the behavior you saw in your first post, so my starting
ass
following error messages we are seeing on client side :
2018-03-08 18:38:24,248 41319597 [Camel (jcsCoreCamelContext) thread #12 -
JmsConsumer[uniquequename]]
(org.apache.activemq.activemq-osgi:org.apache.activemq.jms.pool.PooledSession:126)
WARN - Caught exception trying close() when putting ses
I'll start with the bad news. From what you've written, it could be either
product (Camel or ActiveMQ) that's causing the problem, and the people that
support the two products are both likely to initially assume it's the other
product's doing. So one of the best things you can do is to figure out
w
we are using activemq : 5.12.3
apache camel : 2.16.2
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Based on the error message in your original email, you appear to be using
Unicode pretty-print quote characters:
Lexical error at line
1, column 2. Encountered: "\u201c" (8220), after : ""
On Mar 8, 2018 7:00 PM, "dhanasekar" wrote:
> Hi,
>
> Yes, I tried removed ID: string in the message id a
Thanks for reply.
I haven't investgate JVM yet.
I'm using AMQ as follows conditions, is there a factor that is likely to
take time?
Conditions:
* Using MQTT (QoS=2)
* MQTT Client is Eclipse Paho 1.0.0
* Subscriber's CleanSession is false.
* Number of Subscribers is 1 over.
* Number of To
Hi,
Yes, I tried removed ID: string in the message id as well.
I found the 'root cause', still didn't find the solution.
*Root cause:*
ID:Dhanasekars-iMac.local-54880-1520061026486-1:1:1:1:1
JMSMessageID is not accepting : and -, if I remove these 2 special character
, Not getting error any mo
Hi
we are using mesh n/w connectors A,B,C. and we have two consumers. upto some
hours system is working fine, after that when we are checking messages those
are generated by camel with correlationId as null
ActiveMQObjectMessage {commandId = 4, responseRequired = true, messageId =
ID:asdf-55403-1
Hello all,
I have just downloaded activemq-activemq-5.15.3 version of activemq and
trying to build the source code by running mvn clean install.
Problem is that there is a failing test:
testRecoveryOnArchiveFailure(org.apache.activemq.store.kahadb.JournalArchiveTest)
Time elapsed: 2.934 sec <
If this was fixed in 2.5 it will be closed as a non issue. We can’t go
back in time and fix 2.4 ;)
Saying the obvious. But I am now confused if this is an issue in 2.5 or
not.
On Thu, Mar 8, 2018 at 12:06 AM dharmendra wrote:
> hi Clebert,
> Thanks for response . I am using Artemis 2.4.0 as
An update: the errors were caused by a peculiarity in our environment. Anyway,
looking at the nature of the changes between builds it is somewhat obvious this
issue couldn't have been caused by the related commits. So far I've been unable
to replicate the original issue, being the cluster connec
Trying out master results in weird issues:
Broker A logs a very large amount of this:
10:06:37,292 ERROR [org.apache.activemq.artemis.core.client] AMQ214031: Failed
to decode buffer, disconnect immediately.: java.lang.IllegalStateException:
java.lang.IllegalArgumentException: AMQ119032: Invalid
12 matches
Mail list logo
