[jira] [Commented] (AMQ-5700) Invalid TLS Padding data Error

[Harikrishnan P (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14392118#comment-14392118
 ] 

Harikrishnan P commented on AMQ-5700:
-

No, am using an Mqtt paho C client to connect to ActiveMQ broker.The code for 
the same is pasted below.

#include "stdio.h"
#include "stdlib.h"
#include "string.h"
#include "MQTTClient.h"

#define ADDRESS "ssl://localhost:8883"
#define CLIENTID"ExampleClientPub"
#define TOPIC   "test"
#define PAYLOAD "Hello World!"
#define QOS 1
#define TIMEOUT 1L
#define CLIENT_CRT   "/home/harikrishnan/Certs/client.crt"
#define CA_CRT   "/home/harikrishnan/Certs/ca.crt"
#define CLIENT_PEM   "/home/harikrishnan/Certs/client.pem"

volatile MQTTClient_deliveryToken deliveredtoken;

void delivered(void *context, MQTTClient_deliveryToken dt)
{
printf("Message with token value %d delivery confirmed\n", dt);
deliveredtoken = dt;
}

int msgarrvd(void *context, char *topicName, int topicLen, MQTTClient_message 
*message)
{
int i;
char* payloadptr;

printf("Message arrived\n");
printf(" topic: %s\n", topicName);
printf("   message: ");

payloadptr = message->payload;
for(i=0; ipayloadlen; i++)
{
putchar(*payloadptr++);
}
putchar('\n');
MQTTClient_freeMessage(&message);
MQTTClient_free(topicName);
return 1;
}

void connlost(void *context, char *cause)
{
printf("\nConnection lost\n");
printf(" cause: %s\n", cause);
}

int main(int argc, char* argv[])
{
MQTTClient client;
MQTTClient_connectOptions conn_opts = MQTTClient_connectOptions_initializer;
MQTTClient_SSLOptions ssl_opts = MQTTClient_SSLOptions_initializer;
MQTTClient_message pubmsg = MQTTClient_message_initializer;
MQTTClient_deliveryToken token;
int rc;

MQTTClient_create(&client, ADDRESS, CLIENTID,
MQTTCLIENT_PERSISTENCE_NONE, NULL);

conn_opts.ssl = &ssl_opts;

conn_opts.ssl->keyStore = "/home/harikrishnan/Test_Certs/client-chain.pem";
conn_opts.ssl->privateKeyPassword = "password";

conn_opts.ssl->enabledCipherSuites = "DEFAULT";
conn_opts.ssl->enableServerCertAuth = 0;


MQTTClient_setCallbacks(client, NULL, connlost, msgarrvd, delivered);

if ((rc = MQTTClient_connect(client, &conn_opts)) != MQTTCLIENT_SUCCESS)
{
printf("Failed to connect, return code %d\n", rc);
exit(-1);
}
pubmsg.payload = PAYLOAD;
pubmsg.payloadlen = strlen(PAYLOAD);
pubmsg.qos = QOS;
pubmsg.retained = 0;
deliveredtoken = 0;
MQTTClient_publishMessage(client, TOPIC, &pubmsg, &token);
printf("Waiting for publication of %s\n"
"on topic %s for client with ClientID: %s\n",
PAYLOAD, TOPIC, CLIENTID);
while(deliveredtoken != token);
MQTTClient_disconnect(client, 1);
MQTTClient_destroy(&client);
return rc;
}


> Invalid TLS Padding data Error
> --
>
> Key: AMQ-5700
> URL: https://issues.apache.org/jira/browse/AMQ-5700
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 5.11.0
> Environment: Ubuntu 12.04 Kernel 3.13, java version 
> "1.7.0_72",OpenSSL 1.0.1 
>Reporter: Harikrishnan P
>
> 
> 
>  uri="tcp://0.0.0.0:1883?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/>
> 
> 
> Tried creating certificates as per the following link:
> https://github.com/rethab/php-stomp-cert-example/blob/master/README.md



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMQ-5701) Invalid TLS Padding data Error

[Harikrishnan P (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-5701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14392103#comment-14392103
 ] 

Harikrishnan P commented on AMQ-5701:
-

No, am using an Mqtt paho C client to connect to ActiveMQ broker.The code for 
the same is pasted below.

#include "stdio.h"
#include "stdlib.h"
#include "string.h"
#include "MQTTClient.h"

#define ADDRESS "ssl://localhost:8883"
#define CLIENTID"ExampleClientPub"
#define TOPIC   "test"
#define PAYLOAD "Hello World!"
#define QOS 1
#define TIMEOUT 1L
#define CLIENT_CRT   "/home/harikrishnan/Certs/client.crt"
#define CA_CRT   "/home/harikrishnan/Certs/ca.crt"
#define CLIENT_PEM   "/home/harikrishnan/Certs/client.pem"

volatile MQTTClient_deliveryToken deliveredtoken;

void delivered(void *context, MQTTClient_deliveryToken dt)
{
printf("Message with token value %d delivery confirmed\n", dt);
deliveredtoken = dt;
}

int msgarrvd(void *context, char *topicName, int topicLen, MQTTClient_message 
*message)
{
int i;
char* payloadptr;

printf("Message arrived\n");
printf(" topic: %s\n", topicName);
printf("   message: ");

payloadptr = message->payload;
for(i=0; ipayloadlen; i++)
{
putchar(*payloadptr++);
}
putchar('\n');
MQTTClient_freeMessage(&message);
MQTTClient_free(topicName);
return 1;
}

void connlost(void *context, char *cause)
{
printf("\nConnection lost\n");
printf(" cause: %s\n", cause);
}

int main(int argc, char* argv[])
{
MQTTClient client;
MQTTClient_connectOptions conn_opts = MQTTClient_connectOptions_initializer;
MQTTClient_SSLOptions ssl_opts = MQTTClient_SSLOptions_initializer;
MQTTClient_message pubmsg = MQTTClient_message_initializer;
MQTTClient_deliveryToken token;
int rc;

MQTTClient_create(&client, ADDRESS, CLIENTID,
MQTTCLIENT_PERSISTENCE_NONE, NULL);

conn_opts.ssl = &ssl_opts;

conn_opts.ssl->keyStore = "/home/harikrishnan/Test_Certs/client-chain.pem";
conn_opts.ssl->privateKeyPassword = "password";

conn_opts.ssl->enabledCipherSuites = "DEFAULT";
conn_opts.ssl->enableServerCertAuth = 0;


MQTTClient_setCallbacks(client, NULL, connlost, msgarrvd, delivered);

if ((rc = MQTTClient_connect(client, &conn_opts)) != MQTTCLIENT_SUCCESS)
{
printf("Failed to connect, return code %d\n", rc);
exit(-1);
}
pubmsg.payload = PAYLOAD;
pubmsg.payloadlen = strlen(PAYLOAD);
pubmsg.qos = QOS;
pubmsg.retained = 0;
deliveredtoken = 0;
MQTTClient_publishMessage(client, TOPIC, &pubmsg, &token);
printf("Waiting for publication of %s\n"
"on topic %s for client with ClientID: %s\n",
PAYLOAD, TOPIC, CLIENTID);
while(deliveredtoken != token);
MQTTClient_disconnect(client, 1);
MQTTClient_destroy(&client);
return rc;
}


> Invalid TLS Padding data Error
> --
>
> Key: AMQ-5701
> URL: https://issues.apache.org/jira/browse/AMQ-5701
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 5.11.0
> Environment: Ubuntu 12.04 Kernel 3.13, java version 
> "1.7.0_72",OpenSSL 1.0.1 
>Reporter: Harikrishnan P
>
> 
> 
>  uri="tcp://0.0.0.0:1883?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/>
> 
> 
> Tried creating certificates as per the following link:
> https://github.com/rethab/php-stomp-cert-example/blob/master/README.md



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] activemq pull request: Improved filename sanitization

[dfj]

GitHub user dfj opened a pull request:

https://github.com/apache/activemq/pull/79

Improved filename sanitization



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/dfj/activemq activemq-5.10.x

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/activemq/pull/79.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #79


commit d48f950cb1734d5bf50736681efe5b9d187bdc2c
Author: David Jorm 
Date:   2015-04-02T01:05:04Z

Improved filename sanitization




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] activemq pull request: Improved filename sanitization

[dfj]

GitHub user dfj opened a pull request:

https://github.com/apache/activemq/pull/78

Improved filename sanitization



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/dfj/activemq activemq-5.11.x

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/activemq/pull/78.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #78


commit 35b3f0524bd3cf4dc0aca4e4b2c92cfe178e2b2a
Author: David Jorm 
Date:   2015-04-02T01:04:24Z

Improved filename sanitization




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] activemq pull request: Improved filename sanitization

[dfj]

GitHub user dfj opened a pull request:

https://github.com/apache/activemq/pull/77

Improved filename sanitization



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/dfj/activemq master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/activemq/pull/77.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #77


commit a1cc5501c4b998223df1b2bc4b349f24e86c07ff
Author: David Jorm 
Date:   2015-04-02T01:03:02Z

Improved filename sanitization




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [DISCUSS} HornetQ & ActiveMQ's next generation

[Jim Jagielski]

> 
> The board will not, and does not, tolerate outside
> influences impacting our internal decision making
> and development methods.

PUH-LEASE do not read ANYTHING into the above. It is a simple
catch-all reminder.

Jenkins build is back to normal : ActiveMQ-Trunk-Deploy #1290

[Apache Jenkins Server]

See 

[jira] [Resolved] (AMQ-5684) AMQP: messages get stuck

[Timothy Bish (JIRA)]

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

Timothy Bish resolved AMQ-5684.
---
   Resolution: Fixed
Fix Version/s: 5.12.0

Fix confirmed by Chuck, thanks!

> AMQP: messages get stuck
> 
>
> Key: AMQ-5684
> URL: https://issues.apache.org/jira/browse/AMQ-5684
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: AMQP
>Affects Versions: 5.12.0
> Environment: 5.12-SNAPSHOT 20150322 running on Fedora linux
>Reporter: Chuck Rolke
>Assignee: Timothy Bish
> Fix For: 5.12.0
>
> Attachments: AMQ5684-reproducer.cs, second-receiver-hang-20150323.html
>
>
> While investigating AMQ-5646 the same test failed in a different way.
> It did not progress as far. The test:
> * Client opens a connection and a session.
> * Client opens a sender and sends 20 messages
> * Client opens a receiver with a credit of two
> The receiver receives one message and that's all. The expectation is to 
> receive two messages.
> A trace to be attached.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMQ-5684) AMQP: messages get stuck

[Chuck Rolke (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-5684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14391551#comment-14391551
 ] 

Chuck Rolke commented on AMQ-5684:
--

Snapshot 5.12-20150331 looks good. The test case passes.

> AMQP: messages get stuck
> 
>
> Key: AMQ-5684
> URL: https://issues.apache.org/jira/browse/AMQ-5684
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: AMQP
>Affects Versions: 5.12.0
> Environment: 5.12-SNAPSHOT 20150322 running on Fedora linux
>Reporter: Chuck Rolke
>Assignee: Timothy Bish
> Attachments: AMQ5684-reproducer.cs, second-receiver-hang-20150323.html
>
>
> While investigating AMQ-5646 the same test failed in a different way.
> It did not progress as far. The test:
> * Client opens a connection and a session.
> * Client opens a sender and sends 20 messages
> * Client opens a receiver with a credit of two
> The receiver receives one message and that's all. The expectation is to 
> receive two messages.
> A trace to be attached.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [DISCUSS} HornetQ & ActiveMQ's next generation

[Jim Jagielski]

I have decided to not draft any email. There really is
no need.

The PMC is on task to provide a board report. It is
expected that the report will be open and honest
and present the board with the current projected
roadmap for AMQ5 and AMQ6 going forward. It is
expected that this report will be based on facts
and consensus-based discussions within the PMC
and the community. It is also expected that the
report itself will note any and all points of view
within the PMC; I encourage all PMC members to ensure
that your individual PoV is represented at some level
in that report.

The board will not, and does not, tolerate outside
influences impacting our internal decision making
and development methods.

[GitHub] activemq-6 pull request: Docs and settings updates

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/activemq-6/pull/200


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] activemq-6 pull request: Docs and settings updates

[clebertsuconic]

GitHub user clebertsuconic opened a pull request:

https://github.com/apache/activemq-6/pull/200

Docs and settings updates



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/clebertsuconic/activemq-6 master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/activemq-6/pull/200.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #200


commit a7a362b1d71819b6ed2eb3f5cfb241a8a1bc1376
Author: Clebert Suconic 
Date:   2015-04-01T20:10:17Z

Improving Print-data on DuplicateIDs (showing some information to help 
Bridge Duplicate IDs)

commit 48d002e19a19de9664ccc548b36afd697434da31
Author: Clebert Suconic 
Date:   2015-04-01T20:10:39Z

adding a word about compact-min-files on the docs

commit 6239ff6291348ae31fe776de1bcef9d73f24c3f5
Author: Clebert Suconic 
Date:   2015-04-01T20:13:56Z

settings updates

commit c38acee50996420c451f68dafe9e5371ded3
Author: Clebert Suconic 
Date:   2015-04-01T20:16:13Z

fixing extra-tests dependency




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (AMQ-5705) originBrokerURL incorrectly set in advisory messages

[Vu Le (JIRA)]

Vu Le created AMQ-5705:
--

 Summary: originBrokerURL incorrectly set in advisory messages
 Key: AMQ-5705
 URL: https://issues.apache.org/jira/browse/AMQ-5705
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker
Affects Versions: 5.11.1
Reporter: Vu Le
Priority: Minor


With a broker configured with multiple transports, the "originBrokerURL" 
property of advisory messages is incorrectly set. 

Assuming a broker that has two transports configured, an advisory message for a 
connection made to transport-A may have the "originBrokerURL" property set to 
transport-B.

Looks like the "originBrokerURL" value is set from the 
getDefaultSocketURIString() method in the BrokerService class. Is there a good 
reason why the "originBrokerURL" value does not correlate with the transport 
where the advisory event is actually being triggered?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: How is ActiveMQ 6.0 for continual integration / testing?

[Clebert Suconic]

For every Pull Request sent (e.g: https://github.com/apache/activemq-6/pull/197)

There will be a build with a considerable sized testsuite running..
which we call fast-test
https://builds.apache.org/job/ActiveMQ6-PR-Build/223/


This will validate tests, CheckStyle and Licensing.



This will run the entire JMS tests, unit-tests and some other tests.
It's worth looking at:
https://builds.apache.org/job/ActiveMQ6-PR-Build/223/testReport/



We then run the entire testsuite daily:
https://builds.apache.org/view/All/job/ActiveMQ6-Nightly-Regression-Test/


There are some failures on this environment now but that's something
we are working to solve with Infra. They run ok on my personal dev
enrionment and some other servers I have access to.

We are in hold now based on the discussions on dev-list this week, but
we should fix that soon.


Anyway, I hope you get the picture.. PRs are rejected if they fail the
basic testsuite, and we will monitor the entire testsuite daily.

On Wed, Apr 1, 2015 at 3:48 PM, Kevin Burton  wrote:
> This was one of the things that bothered/bothers me about ActiveMQ 5.x… the
> test takes 24 hours to run.  I’ve never actually had any success getting it
> to run because it’s crashed on me every time.  (even for release builds).
>
> Our internal tests take 20 minutes to build… and that is too long IMO.
> Certainly our tests could be more comprehensive but I think they’re pretty
> damn good right now.
>
> Would be good if ActiveMQ 6.0 could resolve this and we could get builds
> integrated quickly after a commit. :)
>
> Kevin
>
> --
>
> Founder/CEO Spinn3r.com
> Location: *San Francisco, CA*
> blog: http://burtonator.wordpress.com
> … or check out my Google+ profile
> 
> 



-- 
Clebert Suconic
http://community.jboss.org/people/clebert.suco...@jboss.com
http://clebertsuconic.blogspot.com

How is ActiveMQ 6.0 for continual integration / testing?

[Kevin Burton]

This was one of the things that bothered/bothers me about ActiveMQ 5.x… the
test takes 24 hours to run.  I’ve never actually had any success getting it
to run because it’s crashed on me every time.  (even for release builds).

Our internal tests take 20 minutes to build… and that is too long IMO.
Certainly our tests could be more comprehensive but I think they’re pretty
damn good right now.

Would be good if ActiveMQ 6.0 could resolve this and we could get builds
integrated quickly after a commit. :)

Kevin

-- 

Founder/CEO Spinn3r.com
Location: *San Francisco, CA*
blog: http://burtonator.wordpress.com
… or check out my Google+ profile

[jira] [Resolved] (AMQ-5703) kahadb - index recovery - corrupt journal records cannot be skipped

[Gary Tully (JIRA)]

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

Gary Tully resolved AMQ-5703.
-
Resolution: Fixed

fix and test in http://git-wip-us.apache.org/repos/asf/activemq/commit/a7178a46

> kahadb - index recovery - corrupt journal records cannot be skipped
> ---
>
> Key: AMQ-5703
> URL: https://issues.apache.org/jira/browse/AMQ-5703
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: KahaDB, Message Store
>Affects Versions: 5.11.0
>Reporter: Gary Tully
>Assignee: Gary Tully
>  Labels: kahadb, recovery
> Fix For: 5.12.0
>
>
> Working with some corrupt data stores - if corruption occurs in the middle of 
> a journal and the index needs to be rebuilt we get:{code}java.io.EOFException
>   at java.io.RandomAccessFile.readFully(RandomAccessFile.java:446)
>   at java.io.RandomAccessFile.readFully(RandomAccessFile.java:424)
>   at 
> org.apache.activemq.util.RecoverableRandomAccessFile.readFully(RecoverableRandomAccessFile.java:75)
>   at 
> org.apache.activemq.store.kahadb.disk.journal.DataFileAccessor.readRecord(DataFileAccessor.java:87)
>   at 
> org.apache.activemq.store.kahadb.disk.journal.Journal.read(Journal.java:641)
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:1014)
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:606)
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:400)
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:418)
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:262)
>   at 
> org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:206)
>   at org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)
>   at 
> org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:223)
>   at org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)
>   at 
> org.apache.activemq.broker.BrokerService.doStartPersistenceAdapter(BrokerService.java:652)
>   at 
> org.apache.activemq.broker.BrokerService.startPersistenceAdapter(BrokerService.java:641)
>   at 
> org.apache.activemq.broker.BrokerService.start(BrokerService.java:606){code}
> attempting to read an invalid location. This stops further recovery and the 
> entire journal needs to be removed to progress.
> We have already identified the corrupt record, we just need to skip it when 
> we replay.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMQ-5082) ActiveMQ replicatedLevelDB cluster breaks, all nodes stop listening

[Christian Posta (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14390759#comment-14390759
 ] 

Christian Posta commented on AMQ-5082:
--

Will be in 5.12 when released. Do you needed it back ported to a 5.11.x?
Or can test with the nightly builds here:

https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/apache-activemq/5.12-SNAPSHOT/

> ActiveMQ replicatedLevelDB cluster breaks, all nodes stop listening
> ---
>
> Key: AMQ-5082
> URL: https://issues.apache.org/jira/browse/AMQ-5082
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: activemq-leveldb-store
>Affects Versions: 5.9.0, 5.10.0
>Reporter: Scott Feldstein
>Assignee: Christian Posta
>Priority: Critical
> Fix For: 5.12.0
>
> Attachments: 03-07.tgz, amq_5082_threads.tar.gz, 
> mq-node1-cluster.failure, mq-node2-cluster.failure, mq-node3-cluster.failure, 
> zookeeper.out-cluster.failure
>
>
> I have a 3 node amq cluster and one zookeeper node using a replicatedLevelDB 
> persistence adapter.
> {code}
> 
>directory="${activemq.data}/leveldb"
>   replicas="3"
>   bind="tcp://0.0.0.0:0"
>   zkAddress="zookeep0:2181"
>   zkPath="/activemq/leveldb-stores"/>
> 
> {code}
> After about a day or so of sitting idle there are cascading failures and the 
> cluster completely stops listening all together.
> I can reproduce this consistently on 5.9 and the latest 5.10 (commit 
> 2360fb859694bacac1e48092e53a56b388e1d2f0).  I am going to attach logs from 
> the three mq nodes and the zookeeper logs that reflect the time where the 
> cluster starts having issues.
> The cluster stops listening Mar 4, 2014 4:56:50 AM (within 5 seconds).
> The OSs are all centos 5.9 on one esx server, so I doubt networking is an 
> issue.
> If you need more data it should be pretty easy to get whatever is needed 
> since it is consistently reproducible.
> This bug may be related to AMQ-5026, but looks different enough to file a 
> separate issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMQ-5082) ActiveMQ replicatedLevelDB cluster breaks, all nodes stop listening

[anselme dewavrin (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14390730#comment-14390730
 ] 

anselme dewavrin commented on AMQ-5082:
---

A big Thank you Jim, we were truly annoyed by this !

Christian, will this be included in the main branch of the downloadable 
binaries ? In which version ?

Thanks in advance,

Anselme

> ActiveMQ replicatedLevelDB cluster breaks, all nodes stop listening
> ---
>
> Key: AMQ-5082
> URL: https://issues.apache.org/jira/browse/AMQ-5082
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: activemq-leveldb-store
>Affects Versions: 5.9.0, 5.10.0
>Reporter: Scott Feldstein
>Assignee: Christian Posta
>Priority: Critical
> Fix For: 5.12.0
>
> Attachments: 03-07.tgz, amq_5082_threads.tar.gz, 
> mq-node1-cluster.failure, mq-node2-cluster.failure, mq-node3-cluster.failure, 
> zookeeper.out-cluster.failure
>
>
> I have a 3 node amq cluster and one zookeeper node using a replicatedLevelDB 
> persistence adapter.
> {code}
> 
>directory="${activemq.data}/leveldb"
>   replicas="3"
>   bind="tcp://0.0.0.0:0"
>   zkAddress="zookeep0:2181"
>   zkPath="/activemq/leveldb-stores"/>
> 
> {code}
> After about a day or so of sitting idle there are cascading failures and the 
> cluster completely stops listening all together.
> I can reproduce this consistently on 5.9 and the latest 5.10 (commit 
> 2360fb859694bacac1e48092e53a56b388e1d2f0).  I am going to attach logs from 
> the three mq nodes and the zookeeper logs that reflect the time where the 
> cluster starts having issues.
> The cluster stops listening Mar 4, 2014 4:56:50 AM (within 5 seconds).
> The OSs are all centos 5.9 on one esx server, so I doubt networking is an 
> issue.
> If you need more data it should be pretty easy to get whatever is needed 
> since it is consistently reproducible.
> This bug may be related to AMQ-5026, but looks different enough to file a 
> separate issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMQ-5702) REST production of message bodies can result in IllegalStateException: STREAMED (same as AMQ-5579)

[J G (JIRA)]

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

J G updated AMQ-5702:
-
Description: 
I am working on a project to use Apache ActiveMQ with a RESTful interface. It's 
a cross platform error logging project, so code written in C++, Java, VBA, Perl 
or indeed anything that can access an URL can then report issues. The point is, 
we DO NOT deploy any libraries - we simply use the native implementations 
within the language to access an URL. The HTTP message body then contains the 
details of the error - who, what, when, what line of code and so on.

The piece I am working on is a port of an MSMQ implementation (you can a 
simpllified implementation of the MSMQ version on this 
http://blog.alignment-systems.com/2015/03/excel-vba-industrialisationpart-seven.html
 and on github at https://github.com/JohnGreenan/7_ExcelVBE) 

So, I can access Apache Active MQ from a Windows PC using the 
WinHttp.WinHttpRequest class 
(https://msdn.microsoft.com/en-us/library/windows/desktop/aa384106%28v=vs.85%29.aspx)

The issue is that when I try and send a body of the request, I get the same 
error as shown in this JIRA.

Within cURL it's possible to workaround as described by Mark Frazier, but I 
have tried a few approaches on this WITHIN VBA and failed to get it to work.

What I propose to do is to create a github repository with the VBA code and 
instructions on how to replicate, but I am not sure if that's how you guys 
work? Do you actually work with implementations in languages, or is it just the 
case that it it works with cURL then the other language implementation is 
viewed as being at fault?

Can you please give me some guidance on how I can work with you to get this 
resolved?

Replication code at: https://github.com/JohnGreenan/ApacheActiveMQ.REST.winhttp

  was:
I am working on a project to use Apache ActiveMQ with a RESTful interface. It's 
a cross platform error logging project, so code written in C++, Java, VBA, Perl 
or indeed anything that can access an URL can then report issues. The point is, 
we DO NOT deploy any libraries - we simply use the native implementations 
within the language to access an URL. The HTTP message body then contains the 
details of the error - who, what, when, what line of code and so on.

The piece I am working on is a port of an MSMQ implementation (you can a 
simpllified implementation of the MSMQ version on this 
http://blog.alignment-systems.com/2015/03/excel-vba-industrialisationpart-seven.html
 and on github at https://github.com/JohnGreenan/7_ExcelVBE)

So, I can access Apache Active MQ from a Windows PC using the 
WinHttp.WinHttpRequest class 
(https://msdn.microsoft.com/en-us/library/windows/desktop/aa384106%28v=vs.85%29.aspx)

The issue is that when I try and send a body of the request, I get the same 
error as shown in this JIRA.

Within cURL it's possible to workaround as described by Mark Frazier, but I 
have tried a few approaches on this WITHIN VBA and failed to get it to work.

What I propose to do is to create a github repository with the VBA code and 
instructions on how to replicate, but I am not sure if that's how you guys 
work? Do you actually work with implementations in languages, or is it just the 
case that it it works with cURL then the other language implementation is 
viewed as being at fault?

Can you please give me some guidance on how I can work with you to get this 
resolved?


> REST production of message bodies can result in IllegalStateException: 
> STREAMED (same as AMQ-5579)
> --
>
> Key: AMQ-5702
> URL: https://issues.apache.org/jira/browse/AMQ-5702
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Transport
>Affects Versions: 5.10.0
> Environment: Windows 8.1 64bit
>Reporter: J G
>
> I am working on a project to use Apache ActiveMQ with a RESTful interface. 
> It's a cross platform error logging project, so code written in C++, Java, 
> VBA, Perl or indeed anything that can access an URL can then report issues. 
> The point is, we DO NOT deploy any libraries - we simply use the native 
> implementations within the language to access an URL. The HTTP message body 
> then contains the details of the error - who, what, when, what line of code 
> and so on.
> The piece I am working on is a port of an MSMQ implementation (you can a 
> simpllified implementation of the MSMQ version on this 
> http://blog.alignment-systems.com/2015/03/excel-vba-industrialisationpart-seven.html
>  and on github at https://github.com/JohnGreenan/7_ExcelVBE) 
> So, I can access Apache Active MQ from a Windows PC using the 
> WinHttp.WinHttpRequest class 
> (https://msdn.microsoft.com/en-us/library/windows/desktop/aa384106%28v=vs.85%29.aspx)
> The issue is that when I try and send a body of

[jira] [Commented] (AMQ-5082) ActiveMQ replicatedLevelDB cluster breaks, all nodes stop listening

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14390671#comment-14390671
 ] 

ASF GitHub Bot commented on AMQ-5082:
-

Github user jimrobinson closed the pull request at:

https://github.com/apache/activemq/pull/76


> ActiveMQ replicatedLevelDB cluster breaks, all nodes stop listening
> ---
>
> Key: AMQ-5082
> URL: https://issues.apache.org/jira/browse/AMQ-5082
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: activemq-leveldb-store
>Affects Versions: 5.9.0, 5.10.0
>Reporter: Scott Feldstein
>Assignee: Christian Posta
>Priority: Critical
> Fix For: 5.12.0
>
> Attachments: 03-07.tgz, amq_5082_threads.tar.gz, 
> mq-node1-cluster.failure, mq-node2-cluster.failure, mq-node3-cluster.failure, 
> zookeeper.out-cluster.failure
>
>
> I have a 3 node amq cluster and one zookeeper node using a replicatedLevelDB 
> persistence adapter.
> {code}
> 
>directory="${activemq.data}/leveldb"
>   replicas="3"
>   bind="tcp://0.0.0.0:0"
>   zkAddress="zookeep0:2181"
>   zkPath="/activemq/leveldb-stores"/>
> 
> {code}
> After about a day or so of sitting idle there are cascading failures and the 
> cluster completely stops listening all together.
> I can reproduce this consistently on 5.9 and the latest 5.10 (commit 
> 2360fb859694bacac1e48092e53a56b388e1d2f0).  I am going to attach logs from 
> the three mq nodes and the zookeeper logs that reflect the time where the 
> cluster starts having issues.
> The cluster stops listening Mar 4, 2014 4:56:50 AM (within 5 seconds).
> The OSs are all centos 5.9 on one esx server, so I doubt networking is an 
> issue.
> If you need more data it should be pretty easy to get whatever is needed 
> since it is consistently reproducible.
> This bug may be related to AMQ-5026, but looks different enough to file a 
> separate issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] activemq pull request: fix the inconsistency with ElectingLevelDBS...

[jimrobinson]

Github user jimrobinson closed the pull request at:

https://github.com/apache/activemq/pull/76


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (AMQ-5082) ActiveMQ replicatedLevelDB cluster breaks, all nodes stop listening

[Christian Posta (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14390648#comment-14390648
 ] 

Christian Posta commented on AMQ-5082:
--

Thanks Jim for digging into this. I've committed your PR. Running tests on my 
side I've not gotten it to fail. Hopefully jenkins thinks the same thing :)

Thanks again for your contributions!! Look forward to others :)

> ActiveMQ replicatedLevelDB cluster breaks, all nodes stop listening
> ---
>
> Key: AMQ-5082
> URL: https://issues.apache.org/jira/browse/AMQ-5082
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: activemq-leveldb-store
>Affects Versions: 5.9.0, 5.10.0
>Reporter: Scott Feldstein
>Assignee: Christian Posta
>Priority: Critical
> Fix For: 5.12.0
>
> Attachments: 03-07.tgz, amq_5082_threads.tar.gz, 
> mq-node1-cluster.failure, mq-node2-cluster.failure, mq-node3-cluster.failure, 
> zookeeper.out-cluster.failure
>
>
> I have a 3 node amq cluster and one zookeeper node using a replicatedLevelDB 
> persistence adapter.
> {code}
> 
>directory="${activemq.data}/leveldb"
>   replicas="3"
>   bind="tcp://0.0.0.0:0"
>   zkAddress="zookeep0:2181"
>   zkPath="/activemq/leveldb-stores"/>
> 
> {code}
> After about a day or so of sitting idle there are cascading failures and the 
> cluster completely stops listening all together.
> I can reproduce this consistently on 5.9 and the latest 5.10 (commit 
> 2360fb859694bacac1e48092e53a56b388e1d2f0).  I am going to attach logs from 
> the three mq nodes and the zookeeper logs that reflect the time where the 
> cluster starts having issues.
> The cluster stops listening Mar 4, 2014 4:56:50 AM (within 5 seconds).
> The OSs are all centos 5.9 on one esx server, so I doubt networking is an 
> issue.
> If you need more data it should be pretty easy to get whatever is needed 
> since it is consistently reproducible.
> This bug may be related to AMQ-5026, but looks different enough to file a 
> separate issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [DISCUSS} HornetQ & ActiveMQ's next generation

[Jim Jagielski]

Just a quick FYI:

I have reached out to Red Hat (w/ my ASF hat one) via Mark Little
and Dave Ingham. Both have been *extremely* open, eager and honest
w/ me. I plan on writing up a quick summary of my thoughts and
our conversations and maybe suggest some ways of moving forward.

Sometimes our biases, and past history, can color our interpretations
of events and actions and, to be short, I firmly believe that that
has been a factor here.

As I draft my email, I encourage a short reprieve :)

[jira] [Resolved] (AMQ-5704) AMQP: SASL Mechanisms sent in the wrong order.

[Timothy Bish (JIRA)]

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

Timothy Bish resolved AMQ-5704.
---
Resolution: Fixed

now sending in correct order of preference. 

> AMQP: SASL Mechanisms sent in the wrong order.
> --
>
> Key: AMQ-5704
> URL: https://issues.apache.org/jira/browse/AMQ-5704
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: AMQP
>Affects Versions: 5.10.0, 5.10.1, 5.10.2, 5.11.0, 5.11.1
>Reporter: Timothy Bish
>Assignee: Timothy Bish
> Fix For: 5.12.0
>
>
> During the SASL handshake the broker advertises the supported mechanisms as  
> "ANONYMOUS", "PLAIN" however the AMQP v1.0 specification requires the 
> mechanisms be sent in decreasing order of preference.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMQ-5704) AMQP: SASL Mechanisms sent in the wrong order.

[Timothy Bish (JIRA)]

Timothy Bish created AMQ-5704:
-

 Summary: AMQP: SASL Mechanisms sent in the wrong order.
 Key: AMQ-5704
 URL: https://issues.apache.org/jira/browse/AMQ-5704
 Project: ActiveMQ
  Issue Type: Bug
  Components: AMQP
Affects Versions: 5.11.1, 5.11.0, 5.10.2, 5.10.1, 5.10.0
Reporter: Timothy Bish
Assignee: Timothy Bish
 Fix For: 5.12.0


During the SASL handshake the broker advertises the supported mechanisms as  
"ANONYMOUS", "PLAIN" however the AMQP v1.0 specification requires the 
mechanisms be sent in decreasing order of preference.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (AMQ-5680) MessageBrokerView.getTempQueues() have test for destination.isTopic() instead of destination.isQueue()

[Timothy Bish (JIRA)]

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

Timothy Bish resolved AMQ-5680.
---
   Resolution: Fixed
Fix Version/s: 5.12.0

Fixed, thanks for pointing that out. 

> MessageBrokerView.getTempQueues() have test for destination.isTopic() instead 
> of destination.isQueue()
> --
>
> Key: AMQ-5680
> URL: https://issues.apache.org/jira/browse/AMQ-5680
> Project: ActiveMQ
>  Issue Type: Bug
>Reporter: Endre Stølsvik
>Priority: Minor
> Fix For: 5.12.0
>
>
> The following code is a near-copy of the .getTempTopics() right above - 
> without the change of the "if (destination.isTopic()..." to "if 
> (destination.isQueue()..."
> {code}
> /**
>  * Retrieve a set of all TemporaryQueues be used by the Broker
>  * @return  all TemporaryQueues
>  */
> public Set getTempQueues(){
> Set result = new HashSet();
> for (ActiveMQDestination destination:getDestinations()){
> if (destination.isTopic() && destination.isTemporary()){
> result.add((ActiveMQTempQueue) destination);
> }
> }
> return result;
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMQ-5703) kahadb - index recovery - corrupt journal records cannot be skipped

[Gary Tully (JIRA)]

Gary Tully created AMQ-5703:
---

 Summary: kahadb - index recovery - corrupt journal records cannot 
be skipped
 Key: AMQ-5703
 URL: https://issues.apache.org/jira/browse/AMQ-5703
 Project: ActiveMQ
  Issue Type: Bug
  Components: KahaDB, Message Store
Affects Versions: 5.11.0
Reporter: Gary Tully
Assignee: Gary Tully
 Fix For: 5.12.0


Working with some corrupt data stores - if corruption occurs in the middle of a 
journal and the index needs to be rebuilt we get:{code}java.io.EOFException
at java.io.RandomAccessFile.readFully(RandomAccessFile.java:446)
at java.io.RandomAccessFile.readFully(RandomAccessFile.java:424)
at 
org.apache.activemq.util.RecoverableRandomAccessFile.readFully(RecoverableRandomAccessFile.java:75)
at 
org.apache.activemq.store.kahadb.disk.journal.DataFileAccessor.readRecord(DataFileAccessor.java:87)
at 
org.apache.activemq.store.kahadb.disk.journal.Journal.read(Journal.java:641)
at 
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:1014)
at 
org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:606)
at 
org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:400)
at 
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:418)
at 
org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:262)
at 
org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:206)
at org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)
at 
org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:223)
at org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)
at 
org.apache.activemq.broker.BrokerService.doStartPersistenceAdapter(BrokerService.java:652)
at 
org.apache.activemq.broker.BrokerService.startPersistenceAdapter(BrokerService.java:641)
at 
org.apache.activemq.broker.BrokerService.start(BrokerService.java:606){code}
attempting to read an invalid location. This stops further recovery and the 
entire journal needs to be removed to progress.
We have already identified the corrupt record, we just need to skip it when we 
replay.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMQ-5701) Invalid TLS Padding data Error

[Timothy Bish (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-5701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14390513#comment-14390513
 ] 

Timothy Bish commented on AMQ-5701:
---

Are you trying to connect from a client of the than the ActiveMQ 5.11 JMS 
client ?  We need more details on your setup and what you have tried etc.  

> Invalid TLS Padding data Error
> --
>
> Key: AMQ-5701
> URL: https://issues.apache.org/jira/browse/AMQ-5701
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 5.11.0
> Environment: Ubuntu 12.04 Kernel 3.13, java version 
> "1.7.0_72",OpenSSL 1.0.1 
>Reporter: Harikrishnan P
>
> 
> 
>  uri="tcp://0.0.0.0:1883?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/>
> 
> 
> Tried creating certificates as per the following link:
> https://github.com/rethab/php-stomp-cert-example/blob/master/README.md



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMQ-5700) Invalid TLS Padding data Error

[Timothy Bish (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14390515#comment-14390515
 ] 

Timothy Bish commented on AMQ-5700:
---

Are you trying to connect from a client of the than the ActiveMQ 5.11 JMS 
client ? We need more details on your setup and what you have tried etc.

> Invalid TLS Padding data Error
> --
>
> Key: AMQ-5700
> URL: https://issues.apache.org/jira/browse/AMQ-5700
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 5.11.0
> Environment: Ubuntu 12.04 Kernel 3.13, java version 
> "1.7.0_72",OpenSSL 1.0.1 
>Reporter: Harikrishnan P
>
> 
> 
>  uri="tcp://0.0.0.0:1883?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/>
> 
> 
> Tried creating certificates as per the following link:
> https://github.com/rethab/php-stomp-cert-example/blob/master/README.md



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (AMQ-5701) Invalid TLS Padding data Error

[Timothy Bish (JIRA)]

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

Timothy Bish closed AMQ-5701.
-
Resolution: Duplicate

> Invalid TLS Padding data Error
> --
>
> Key: AMQ-5701
> URL: https://issues.apache.org/jira/browse/AMQ-5701
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 5.11.0
> Environment: Ubuntu 12.04 Kernel 3.13, java version 
> "1.7.0_72",OpenSSL 1.0.1 
>Reporter: Harikrishnan P
>
> 
> 
>  uri="tcp://0.0.0.0:1883?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/>
> 
> 
> Tried creating certificates as per the following link:
> https://github.com/rethab/php-stomp-cert-example/blob/master/README.md



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMQ-5702) REST production of message bodies can result in IllegalStateException: STREAMED (same as AMQ-5579)

[J G (JIRA)]

J G created AMQ-5702:


 Summary: REST production of message bodies can result in 
IllegalStateException: STREAMED (same as AMQ-5579)
 Key: AMQ-5702
 URL: https://issues.apache.org/jira/browse/AMQ-5702
 Project: ActiveMQ
  Issue Type: Bug
  Components: Transport
Affects Versions: 5.10.0
 Environment: Windows 8.1 64bit
Reporter: J G


I am working on a project to use Apache ActiveMQ with a RESTful interface. It's 
a cross platform error logging project, so code written in C++, Java, VBA, Perl 
or indeed anything that can access an URL can then report issues. The point is, 
we DO NOT deploy any libraries - we simply use the native implementations 
within the language to access an URL. The HTTP message body then contains the 
details of the error - who, what, when, what line of code and so on.

The piece I am working on is a port of an MSMQ implementation (you can a 
simpllified implementation of the MSMQ version on this 
http://blog.alignment-systems.com/2015/03/excel-vba-industrialisationpart-seven.html
 and on github at https://github.com/JohnGreenan/7_ExcelVBE)

So, I can access Apache Active MQ from a Windows PC using the 
WinHttp.WinHttpRequest class 
(https://msdn.microsoft.com/en-us/library/windows/desktop/aa384106%28v=vs.85%29.aspx)

The issue is that when I try and send a body of the request, I get the same 
error as shown in this JIRA.

Within cURL it's possible to workaround as described by Mark Frazier, but I 
have tried a few approaches on this WITHIN VBA and failed to get it to work.

What I propose to do is to create a github repository with the VBA code and 
instructions on how to replicate, but I am not sure if that's how you guys 
work? Do you actually work with implementations in languages, or is it just the 
case that it it works with cURL then the other language implementation is 
viewed as being at fault?

Can you please give me some guidance on how I can work with you to get this 
resolved?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [VOTE] Apache ActiveMQ 6.0.0 (RC3)

[James Carman]

On Wed, Apr 1, 2015 at 7:23 AM, Gary Tully  wrote:
> Would version 10 allow you to pause and be happy with 5.x for the next
> few years, till 10.x gets a chance to bed in?
>

A higher number isn't the answer.  HQ needs to go to the incubator.

Re: [VOTE] Apache ActiveMQ 6.0.0 (RC3)

[Gary Tully]

On 28 March 2015 at 19:02, artnaseef  wrote:
> Hey Gary - in all the discussion, I missed this response, so forgive my slow
> response.
ditto :-)

>
> First, let me apologize for my use of the word "take" - it sounds it was
> read as an attack or accusation, and that was not my intent.
Accepted.

>I simply meant, "why is it important that HornetQ be called AMQ-6?"
>
> On the point that AMQ needs a v6, can you tell me why that itself is
> important?  Please be specific - I have seen many comments made that really
> are just restatements of the line that ActiveMQ needs a new broker, but no
> real detail to discuss behind that.
>
I can cite a few examples but the full story is in jira:
1) durable subs should be modelled as queues. They are not in 5.x. Dealing
with slow durable consumers and large backlogs has had loads of issues in
the past[1] and still has issues like across networks.

2) Cursors introduce a cache synchronisation problem.
I think that is mostly resolved but it permeates most of the core
dispatch logic and store interface.
It is more complex and error prone than necessary imho [2]. Cursors
model consumers but I think there is a better way. HQ models producers
in paging. Apollo collapses the index, both benefit from a single core
queue abstraction.

3) Priority support - should be modeled as multiple queues.
the cursors and stores and dispatch logic collude to do priority
support in 5.x - it has been error prone [3]

4) scalability; threading model, zero copy dispatch, locking and
contention. I won't site specjms again, but I burned a lot of cycles
to try and get the best numbers for the folks that ran those tests.
The results are good, but we were blown out of the water by a better
architecture. It is not a mickey-mouse test btw.

> When I look at those statements, I have
> to balance them with my belief of ActiveMQ's popularity, market penetration,
> and ongoing efforts to add ActiveMQ into companies.
>
Exactly. What a existing user wants most from a messaging solution is
stability. While each of the points above are fixable, they are all
high risk and taken together they are a huge body of work. As a result
of evolution there is much complexity; it always surprises me the
degree to which one or two of the 4k tests fail with some seemingly
unrelated change. The 4k tests are one of the most valuable parts of
activemq. They embody hundred of use cases. Keeping them all working
and doing major surgery is getting more difficult all the time.

> Also, have you considered the possibility that naming Apollo "AMQ-6" has
> contributed apparent lack of innovation?
>
I agree. I think the 6.x moniker is a problem. I am in favour of using
a 10.0.0.M1 name for the code donation.

It puts clear daylight between it and 5.x, leaving 5.x room to evolve.
But more importantly imho, it gives activemq clear direction. I think
the user community will eventually tell us if v10 can take over the
5.x mantle.

> In other words, isn't it a concern that it will be hard to encourage 
> innovation on the current product,
> ActiveMQ 5.x, as long as there's a promise of a very different ActiveMQ 6.x?
>
I think the innovation that is possible in 5.x is limited by
 a) its architecture and evolution.
 b) the need for stability, the large user base and numerous use cases.

There is plenty of room to improve however. I expect that to continue.

> I know that even causes me to pause.
>
Would version 10 allow you to pause and be happy with 5.x for the next
few years, till 10.x gets a chance to bed in?


[1] 
https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMQ%20AND%20status%20%3D%20Open%20AND%20text%20~%20%22Durable%22
[2] 
https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMQ%20AND%20text%20~%20%22cursor%22
[3] 
https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMQ%20AND%20text%20~%20%22priority%22

Re: [DISCUSS} HornetQ & ActiveMQ's next generation

[Niclas Hedhman]

I agree with Jim. If there is not (near) 100% consensus among committers,
then HQ should become its own project, and there is nothing wrong with
that. ASF are ridden with competing implementations and that is fully
embraced here.

¢2 from peanut gallery

On Sat, Mar 28, 2015 at 9:28 PM, Jim Jagielski  wrote:

> What I don't like, from what I read, is almost virus-like
> attempt to make HQ into AMQ. Virus works by invading a cell
> and then using the cell itself to reproduce; the original cell
> is gone, all that remains is the virus (this is incredibly
> simplified, btw). It almost seems that the idea is, well, we
> can't control the development of AMQ, so let's stack the
> deck and make HQ the next version of AMQ and, shazam!, we now
> control the direction of an Apache TLP.
>
> Someone on the thread called it a hostile takeover; I fail
> to see how that interpretation is far from the mark.
>



-- 
Niclas Hedhman, Software Developer
http://www.qi4j.org - New Energy for Java

[jira] [Created] (AMQ-5701) Invalid TLS Padding data Error

[Harikrishnan P (JIRA)]

Harikrishnan P created AMQ-5701:
---

 Summary: Invalid TLS Padding data Error
 Key: AMQ-5701
 URL: https://issues.apache.org/jira/browse/AMQ-5701
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker
Affects Versions: 5.11.0
 Environment: Ubuntu 12.04 Kernel 3.13, java version "1.7.0_72",OpenSSL 
1.0.1 
Reporter: Harikrishnan P









Tried creating certificates as per the following link:

https://github.com/rethab/php-stomp-cert-example/blob/master/README.md



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMQ-5700) Invalid TLS Padding data Error

[Harikrishnan P (JIRA)]

Harikrishnan P created AMQ-5700:
---

 Summary: Invalid TLS Padding data Error
 Key: AMQ-5700
 URL: https://issues.apache.org/jira/browse/AMQ-5700
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker
Affects Versions: 5.11.0
 Environment: Ubuntu 12.04 Kernel 3.13, java version "1.7.0_72",OpenSSL 
1.0.1 
Reporter: Harikrishnan P









Tried creating certificates as per the following link:

https://github.com/rethab/php-stomp-cert-example/blob/master/README.md



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)