Re: "Invalid TLS Padding data Error" while trying to connect ActiveMQ via SSL

2015-03-31 Thread Hadrian Zbarcea
Also what kind of keys and algorithms you use may be relevant, jce not installed, could be many things. At this point there is no clear indication that the bug is actually in activemq. More details would help. Best, Hadrian On 03/31/2015 09:13 AM, Hadrian Zbarcea wrote: Can you please add a f

Re: Creating a Network of Replicated LevelDB broker clusters

2015-03-31 Thread James A. Robinson
On Tue, Mar 31, 2015 at 1:32 PM, wonderkind wrote: > What version of ActiveMQ are you running with? I am working with 5.11.1.. I'm running 5.11.1 plus the patch in ticket AMQ-5082. Jim

Re: Creating a Network of Replicated LevelDB broker clusters

2015-03-31 Thread wonderkind
I am running the broker using the activemq script, and in console mode, not sure if that produces more verbose information than how you are running it. What version of ActiveMQ are you running with? I am working with 5.11.1.. Thanks. Kevin From: "James A. Robinson-2 [via ActiveMQ]" mailto:m

Re: Creating a Network of Replicated LevelDB broker clusters

2015-03-31 Thread James A. Robinson
On Tue, Mar 31, 2015 at 12:08 PM, wonderkind wrote: > > Is your broker running pretty clean when you send messages through the fabric of network of replicated master/slaves? Yes, though I'm only running the examples/openwire/swissarmy producer/consumer example using the defaults. On the 2nd cl

ActiveMQ issue connecting to ZooKeeper 3.4.6

2015-03-31 Thread barry.barnett
I have an ActiveMQ Broker (v5.10) running within the ServiceMix (v5.1.1) Karaf container using the ZooKeeper 3.4.5 libraries I believe. These appear to be hardcoded in the ActiveMQ v5.10 manifest. We are utilizing the replicatedLevelDB for the ActiveMQ brokers. When I try to connect to ZooKee

Re: Creating a Network of Replicated LevelDB broker clusters

2015-03-31 Thread wonderkind
Thanks. Mine is working now. It looks like the one major difference is the zk session timeout. I was using the default, and you had it set to 5 seconds. However, I am still seeing exceptions such as this one: "java.lang.RuntimeException: An IOException was thrown (should never happen in thi

Re: Messages are lost in a ActiveMQ network message broker

2015-03-31 Thread artnaseef
First off, 5.4.3 is an old version that had many issues; I highly recommend upgrading. With that said, Topic flow across a network of brokers is prone to message loss. For example, if the network connection between two brokers is lost, then non-durable Topic subscriptions between the two brokers

Re: "Invalid TLS Padding data Error" while trying to connect ActiveMQ via SSL

2015-03-31 Thread artnaseef
Hmm, the unknown data type is a concern. Can you try without client certificates? Also, please provide the details of the java version in use. -- View this message in context: http://activemq.2283324.n4.nabble.com/Invalid-TLS-Padding-data-Error-while-trying-to-connect-ActiveMQ-via-SSL-tp46940

Re: ActiveMQ conenction problem in Amazon AWS

2015-03-31 Thread artnaseef
Could there be a network issue? Failure on sysread() sounds like a dropped connection. One thing you can try to diagnose this under Linux is to use strace on the stomp client and look for the exact reason sysread() fails. Note that I have seen others having intermittent network issues in AWS, bu

Re: "Invalid TLS Padding data Error" while trying to connect ActiveMQ via SSL

2015-03-31 Thread Hadrian Zbarcea
Can you please add a few details about the environment (like the OS type and version). Thanks, Hadrian On 03/31/2015 08:48 AM, Tim Bain wrote: Based on a few minutes of Googling, the most common cause of that exception seems to be code that doesn't read enough bytes before trying to unwrap (d

Re: "Invalid TLS Padding data Error" while trying to connect ActiveMQ via SSL

2015-03-31 Thread Tim Bain
Based on a few minutes of Googling, the most common cause of that exception seems to be code that doesn't read enough bytes before trying to unwrap (decrypt) the content. If that's what's going on, the log lines you posted clearly indicate that the bug is in ActiveMQ code rather than code you wrot