Jenkins build became unstable: ActiveMQ » ActiveMQ :: MQTT Protocol #1510
See https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-mqtt/1510/changes
Build failed in Jenkins: ActiveMQ » ActiveMQ :: Unit Tests #1510
See https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-unit-tests/1510/changes Changes: [tabish121] Fix test, remote broker only dequeues the message if it is ack'd -- [...truncated 1142 lines...] [06:02:33] Running org.apache.activemq.bugs.AMQ4893Test [06:02:33] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.335 sec - in org.apache.activemq.bugs.AMQ4893Test [06:02:34] Running org.apache.activemq.bugs.AMQ4899Test [06:02:40] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.36 sec - in org.apache.activemq.bugs.AMQ4899Test [06:02:41] Running org.apache.activemq.bugs.AMQ4930Test [06:02:52] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.782 sec - in org.apache.activemq.bugs.AMQ4930Test [06:02:53] Running org.apache.activemq.bugs.AMQ4950Test [06:02:54] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.399 sec - in org.apache.activemq.bugs.AMQ4950Test [06:02:54] Running org.apache.activemq.bugs.AMQ4952Test [06:03:13] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 18.409 sec - in org.apache.activemq.bugs.AMQ4952Test [06:03:13] Running org.apache.activemq.bugs.AMQ5035Test [06:03:16] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.131 sec - in org.apache.activemq.bugs.AMQ5035Test [06:03:17] Running org.apache.activemq.bugs.AMQ5136Test [06:03:18] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.376 sec - in org.apache.activemq.bugs.AMQ5136Test [06:03:19] Running org.apache.activemq.bugs.AMQ5212Test [06:03:27] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.473 sec - in org.apache.activemq.bugs.AMQ5212Test [06:03:28] Running org.apache.activemq.bugs.AMQ5266Test [06:03:50] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 21.724 sec - in org.apache.activemq.bugs.AMQ5266Test [06:03:50] Running org.apache.activemq.bugs.ActiveMQSlowConsumerManualTest [06:03:58] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.907 sec - in org.apache.activemq.bugs.ActiveMQSlowConsumerManualTest [06:03:59] Running org.apache.activemq.bugs.ConnectionPerMessageTest [06:05:13] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 74.279 sec - in org.apache.activemq.bugs.ConnectionPerMessageTest [06:05:14] Running org.apache.activemq.bugs.CraigsBugTest [06:05:18] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.254 sec - in org.apache.activemq.bugs.CraigsBugTest [06:05:19] Running org.apache.activemq.bugs.DoubleExpireTest [06:06:20] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 61.366 sec - in org.apache.activemq.bugs.DoubleExpireTest [06:06:21] Running org.apache.activemq.bugs.DurableConsumerTest [06:06:55] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 34.074 sec - in org.apache.activemq.bugs.DurableConsumerTest [06:06:55] Running org.apache.activemq.bugs.JMSDurableTopicNoLocalTest [06:07:02] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.746 sec - in org.apache.activemq.bugs.JMSDurableTopicNoLocalTest [06:07:03] Running org.apache.activemq.bugs.JmsDurableTopicSlowReceiveTest [06:08:48] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 105.156 sec - in org.apache.activemq.bugs.JmsDurableTopicSlowReceiveTest [06:08:48] Running org.apache.activemq.bugs.JmsTimeoutTest [06:09:05] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 16.711 sec - in org.apache.activemq.bugs.JmsTimeoutTest [06:09:06] Running org.apache.activemq.bugs.MemoryUsageBlockResumeTest [06:09:09] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.232 sec - in org.apache.activemq.bugs.MemoryUsageBlockResumeTest [06:09:09] Running org.apache.activemq.bugs.MemoryUsageBrokerTest [06:09:26] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 16.08 sec - in org.apache.activemq.bugs.MemoryUsageBrokerTest [06:09:26] Running org.apache.activemq.bugs.MemoryUsageCleanupTest [06:12:57] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 211.204 sec - in org.apache.activemq.bugs.MemoryUsageCleanupTest [06:12:58] Running org.apache.activemq.bugs.MessageExpirationReaperTest [06:13:07] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.023 sec - in org.apache.activemq.bugs.MessageExpirationReaperTest [06:13:08] Running org.apache.activemq.bugs.MissingDataFileTest [06:13:37] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 29.532 sec - in org.apache.activemq.bugs.MissingDataFileTest [06:13:38] Running org.apache.activemq.bugs.OptimizeAcknowledgeWithExpiredMsgsTest [06:13:38] Killed [06:13:39] Running org.apache.activemq.bugs.QueueWorkerPrefetchTest [06:13:40] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.291 sec - in org.apache.activemq.bugs.QueueWorkerPrefetchTest [06:13:41] Running org.apache.activemq.bugs.RedeliveryPluginHeaderTest [06:13:47]
Jenkins build is back to stable : ActiveMQ » ActiveMQ :: LevelDB Store #1510
See https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-leveldb-store/1510/
Jenkins build is back to stable : ActiveMQ » ActiveMQ :: STOMP Protocol #1510
See https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-stomp/1510/
Build failed in Jenkins: ActiveMQ #1510
See https://builds.apache.org/job/ActiveMQ/1510/changes Changes: [dkulp] Remove some unneeded repos, move one to just the module that needs it, add a defaultGoal [dkulp] Minor cleanup to use a c:out to output the data [tabish121] Fix test, remote broker only dequeues the message if it is ack'd -- [...truncated 3750 lines...] [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ/ws/activemq-tooling/activemq-perf-maven-plugin/pom.xml to org.apache.activemq.tooling/activemq-perf-maven-plugin/5.11-SNAPSHOT/activemq-perf-maven-plugin-5.11-SNAPSHOT.pom [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ/ws/activemq-tooling/activemq-perf-maven-plugin/target/activemq-perf-maven-plugin-5.11-SNAPSHOT.jar to org.apache.activemq.tooling/activemq-perf-maven-plugin/5.11-SNAPSHOT/activemq-perf-maven-plugin-5.11-SNAPSHOT.jar Sending artifact delta relative to ActiveMQ ? ActiveMQ :: Performance Test Plugin #1509 Archived 2 artifacts Archive block size is 32768 Received 0 blocks and 95470 bytes Compression is 0.0% Took 0.11 sec [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ/ws/activemq-amqp/pom.xml to org.apache.activemq/activemq-amqp/5.11-SNAPSHOT/activemq-amqp-5.11-SNAPSHOT.pom [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ/ws/activemq-amqp/target/activemq-amqp-5.11-SNAPSHOT.jar to org.apache.activemq/activemq-amqp/5.11-SNAPSHOT/activemq-amqp-5.11-SNAPSHOT.jar Sending artifact delta relative to ActiveMQ ? ActiveMQ :: AMQP #1509 Archived 2 artifacts Archive block size is 32768 Received 0 blocks and 89326 bytes Compression is 0.0% Took 96 ms [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ/ws/activemq-itests-spring31/pom.xml to org.apache.activemq/activemq-itests-spring31/5.11-SNAPSHOT/activemq-itests-spring31-5.11-SNAPSHOT.pom Sending artifact delta relative to ActiveMQ ? ActiveMQ :: Integration Test :: Spring 3.1 #1506 Archived 1 artifacts Archive block size is 32768 Received 0 blocks and 3005 bytes Compression is 0.0% Took 0.17 sec [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ/ws/assembly/pom.xml to org.apache.activemq/apache-activemq/5.11-SNAPSHOT/apache-activemq-5.11-SNAPSHOT.pom Sending artifact delta relative to ActiveMQ ? ActiveMQ :: Assembly #1506 Archived 1 artifacts Archive block size is 32768 Received 0 blocks and 18450 bytes Compression is 0.0% Took 2.9 sec [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ/ws/activemq-jms-pool/pom.xml to org.apache.activemq/activemq-jms-pool/5.11-SNAPSHOT/activemq-jms-pool-5.11-SNAPSHOT.pom [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ/ws/activemq-jms-pool/target/activemq-jms-pool-5.11-SNAPSHOT.jar to org.apache.activemq/activemq-jms-pool/5.11-SNAPSHOT/activemq-jms-pool-5.11-SNAPSHOT.jar Sending artifact delta relative to ActiveMQ ? ActiveMQ :: Generic JMS Pool #1509 Archived 2 artifacts Archive block size is 32768 Received 0 blocks and 54241 bytes Compression is 0.0% Took 0.17 sec [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ/ws/activemq-log4j-appender/pom.xml to org.apache.activemq/activemq-log4j-appender/5.11-SNAPSHOT/activemq-log4j-appender-5.11-SNAPSHOT.pom [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ/ws/activemq-log4j-appender/target/activemq-log4j-appender-5.11-SNAPSHOT.jar to org.apache.activemq/activemq-log4j-appender/5.11-SNAPSHOT/activemq-log4j-appender-5.11-SNAPSHOT.jar Sending artifact delta relative to ActiveMQ ? ActiveMQ :: Log4j Appender #1509 Archived 2 artifacts Archive block size is 32768 Received 0 blocks and 17926 bytes Compression is 0.0% Took 0.14 sec [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ/ws/activemq-runtime-config/pom.xml to org.apache.activemq/activemq-runtime-config/5.11-SNAPSHOT/activemq-runtime-config-5.11-SNAPSHOT.pom [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ/ws/activemq-runtime-config/target/activemq-runtime-config-5.11-SNAPSHOT.jar to org.apache.activemq/activemq-runtime-config/5.11-SNAPSHOT/activemq-runtime-config-5.11-SNAPSHOT.jar Sending artifact delta relative to ActiveMQ ? ActiveMQ :: Runtime Configuration #1509 Archived 2 artifacts Archive block size is 32768 Received 0 blocks and 1584308 bytes Compression is 0.0% Took 0.63 sec [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ/ws/activemq-pool/pom.xml to org.apache.activemq/activemq-pool/5.11-SNAPSHOT/activemq-pool-5.11-SNAPSHOT.pom [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ/ws/activemq-pool/target/activemq-pool-5.11-SNAPSHOT.jar to org.apache.activemq/activemq-pool/5.11-SNAPSHOT/activemq-pool-5.11-SNAPSHOT.jar Sending artifact delta relative to ActiveMQ ? ActiveMQ :: Pool #1509 Archived 2 artifacts Archive block size is 32768 Received 0 blocks and 23919 bytes Compression is 0.0% Took 0.13 sec [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ/ws/activemq-stomp/pom.xml to
[jira] [Commented] (AMQ-5153) LevelDB does not store subscribedDestination for durable subscriptions
[ https://issues.apache.org/jira/browse/AMQ-5153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14103856#comment-14103856 ] Brian Davis commented on AMQ-5153: -- Here is how to reproduce the issue: create a topic testing.durable. create a topic testing.durable.test create a durable on testing.durable. create a different durable on testing.durable.test send message to testing.durable. restart broker when you look at the subscribers all durables are tied to testing.durable.test this happens because the consumers get added to all matching subscribers creating them in the LevelDB store, but because the store does not store the subscribedDestination on a restart levelDB loses the durable's real topic. LevelDB does not store subscribedDestination for durable subscriptions -- Key: AMQ-5153 URL: https://issues.apache.org/jira/browse/AMQ-5153 Project: ActiveMQ Issue Type: Bug Components: activemq-leveldb-store Affects Versions: 5.9.1 Reporter: Brian Davis LevelDB store does not save the subscribedDestination of the SubscriptionInfo for a durable subscription. This is important because when a restart happens you have no clue if this durable subscription goes with the topic or to a different topic (because of wildcarding). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (AMQ-5153) LevelDB does not store subscribedDestination for durable subscriptions
[ https://issues.apache.org/jira/browse/AMQ-5153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14103862#comment-14103862 ] Timothy Bish commented on AMQ-5153: --- Recommend you create a unit test and try it against the latest release. LevelDB does not store subscribedDestination for durable subscriptions -- Key: AMQ-5153 URL: https://issues.apache.org/jira/browse/AMQ-5153 Project: ActiveMQ Issue Type: Bug Components: activemq-leveldb-store Affects Versions: 5.9.1 Reporter: Brian Davis LevelDB store does not save the subscribedDestination of the SubscriptionInfo for a durable subscription. This is important because when a restart happens you have no clue if this durable subscription goes with the topic or to a different topic (because of wildcarding). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (AMQ-4693) Add kerberos [SASL] authentication for TCP connectors
[ https://issues.apache.org/jira/browse/AMQ-4693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14103887#comment-14103887 ] Deepak commented on AMQ-4693: - Hi ActiveMQ team, Did you get a chance to look at this? Could you please provide a rough timeline for this based on current priorities and project pipeline? Can this be taken up sometime soon given that this will be useful for a lot of use cases in general and will take ActiveMQ usage to the next level? Thanks, Deepak Add kerberos [SASL] authentication for TCP connectors - Key: AMQ-4693 URL: https://issues.apache.org/jira/browse/AMQ-4693 Project: ActiveMQ Issue Type: New Feature Components: Broker Affects Versions: 5.8.0 Environment: linux, solaris Reporter: Bhanu Priority: Minor Fix For: Unscheduled Hi, Can kerberos based authentication be added to ActiveMQ's TCP connectors. Thanks, Bhanu -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (AMQNET-489) Port fixes from AMQ-5146 to NMS.ActiveMQ
Timothy Bish created AMQNET-489:
---
Summary: Port fixes from AMQ-5146 to NMS.ActiveMQ
Key: AMQNET-489
URL: https://issues.apache.org/jira/browse/AMQNET-489
Project: ActiveMQ .Net
Issue Type: Bug
Components: ActiveMQ
Affects Versions: 1.6.3, 1.6.2, 1.6.0, 1.6.1
Reporter: Timothy Bish
Assignee: Timothy Bish
Fix For: 1.6.4, 1.7.0
From the AMQ-5146 issue:
{quote}
A consumer with a transacted session that dies after receive or in onMessage
(due to some of the message content for example), but before the a transaction
can complete will continue to receive the message.
The connection will die, the transaction will rollback, the broker will
increment the redeliveryCounter and redispatch the message.
However the redeliveryPolicy, which is only checked on rollback (client side)
will never kick in.
the result is infinite redelivery with an ever incrementing redeliveryCounter.
It is a reasonable expectation that this message would eventually find its way
into the dlq.
The broker redelivery plugin does not help because it is triggered by the
client side poison ack.
Either the broker redelivery plugin can get involved before dispatch, or a
client can do a predispatch check.
{quote}
We should look at porting the fixes done there over to NMS.ActiveMQ
--
This message was sent by Atlassian JIRA
(v6.2#6252)
Re: Possible HornetQ donation to ActiveMQ
We are still on track for this. we are having some delays due to the paperwork that needs to be filled up. We will have an update soon. On Sat, Aug 16, 2014 at 4:38 AM, Richard Kettelerij richardkettele...@gmail.com wrote: Any progress on this? Just curious. On Thu, Jul 31, 2014 at 11:18 AM, sirinath sirinath19...@gmail.com wrote: Maybe you can consider consolidating Qpid also as both are Apache projects. Also may be Kafka though this might need more through. One fautre to retain should be embedded use in HornetQ -- View this message in context: http://activemq.2283324.n4.nabble.com/Possible-HornetQ-donation-to-ActiveMQ-tp4682971p4683916.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. -- Clebert Suconic http://community.jboss.org/people/clebert.suco...@jboss.com http://clebertsuconic.blogspot.com
Re: Possible HornetQ donation to ActiveMQ
Meanwhile we are making our technical work. OpenWire is already part of our master (one of the tasks we would need to have accomplished before we could make any releases out of the new codebase). And making a lot of progress on AMQP. It's just paperwork now.. we will give an update here soon as I said. On Wed, Aug 20, 2014 at 11:42 AM, Clebert Suconic clebert.suco...@gmail.com wrote: We are still on track for this. we are having some delays due to the paperwork that needs to be filled up. We will have an update soon. On Sat, Aug 16, 2014 at 4:38 AM, Richard Kettelerij richardkettele...@gmail.com wrote: Any progress on this? Just curious. On Thu, Jul 31, 2014 at 11:18 AM, sirinath sirinath19...@gmail.com wrote: Maybe you can consider consolidating Qpid also as both are Apache projects. Also may be Kafka though this might need more through. One fautre to retain should be embedded use in HornetQ -- View this message in context: http://activemq.2283324.n4.nabble.com/Possible-HornetQ-donation-to-ActiveMQ-tp4682971p4683916.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. -- Clebert Suconic http://community.jboss.org/people/clebert.suco...@jboss.com http://clebertsuconic.blogspot.com -- Clebert Suconic http://community.jboss.org/people/clebert.suco...@jboss.com http://clebertsuconic.blogspot.com
Re: Possible HornetQ donation to ActiveMQ
It might be better to hold off doing to much work a head of time, you want to be build a community of developers around this :) Clebert Suconic mailto:clebert.suco...@gmail.com 20 August 2014 16:43 Meanwhile we are making our technical work. OpenWire is already part of our master (one of the tasks we would need to have accomplished before we could make any releases out of the new codebase). And making a lot of progress on AMQP. It's just paperwork now.. we will give an update here soon as I said. On Wed, Aug 20, 2014 at 11:42 AM, Clebert Suconicclebert.suco...@gmail.com wrote: We are still on track for this. we are having some delays due to the paperwork that needs to be filled up. We will have an update soon. On Sat, Aug 16, 2014 at 4:38 AM, Richard Kettelerij richardkettele...@gmail.com wrote: Any progress on this? Just curious. On Thu, Jul 31, 2014 at 11:18 AM, sirinathsirinath19...@gmail.com wrote: Maybe you can consider consolidating Qpid also as both are Apache projects. Also may be Kafka though this might need more through. One fautre to retain should be embedded use in HornetQ -- View this message in context: http://activemq.2283324.n4.nabble.com/Possible-HornetQ-donation-to-ActiveMQ-tp4682971p4683916.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. -- Clebert Suconic http://community.jboss.org/people/clebert.suco...@jboss.com http://clebertsuconic.blogspot.com Clebert Suconic mailto:clebert.suco...@gmail.com 20 August 2014 16:42 We are still on track for this. we are having some delays due to the paperwork that needs to be filled up. We will have an update soon. On Sat, Aug 16, 2014 at 4:38 AM, Richard Kettelerij Richard Kettelerij mailto:richardkettele...@gmail.com 16 August 2014 09:38 Any progress on this? Just curious. sirinath mailto:sirinath19...@gmail.com 31 July 2014 10:18 Maybe you can consider consolidating Qpid also as both are Apache projects. Also may be Kafka though this might need more through. One fautre to retain should be embedded use in HornetQ -- View this message in context: http://activemq.2283324.n4.nabble.com/Possible-HornetQ-donation-to-ActiveMQ-tp4682971p4683916.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. Clebert Suconic mailto:clebert.suco...@gmail.com 8 July 2014 15:31 Hi all, My name is Clebert Suconic, I'm the project lead for the HornetQ JMS broker (http://hornetq.jboss.org/). The HornetQ team is currently in the planning phase for the next release of the broker and we've been thinking about whether it would make sense for us to collaborate more closely with the ActiveMQ community. There is a lot of overlap in the capabilities of the two brokers today and it strikes us that it would be beneficial to both communities for us to join forces to build one truly great JMS broker rather than spend our time duplicating efforts on both brokers. ActiveMQ has a great community of developers and users and it'd be great to be able to consolidate our work there. My understanding is that the Apollo sub-project aimed to provide a basis for the next generation of ActiveMQ, addressing some of the current limitations. Perhaps HornetQ could be an alternative. HornetQ has some good performance and scalability numbers as well as support for JMS 2.0. It already supports STOMP today and adding support for OpenWire would be straight-forward and would provide continuity for existing clients. Essentially, the goal could be to combine the existing flexibility of ActiveMQ with the performance of HornetQ. Anyway, these are just some initial ideas, for now I'm really just interested to know how the ActiveMQ community would feel about a donation of the HornetQ codebase. Thanks and best regards, Clebert.
[jira] [Created] (AMQ-5325) CMS (C++ client) crashed if getLocalHost failed
Huan Bui created AMQ-5325: - Summary: CMS (C++ client) crashed if getLocalHost failed Key: AMQ-5325 URL: https://issues.apache.org/jira/browse/AMQ-5325 Project: ActiveMQ Issue Type: Bug Components: CMS (C++ client) Affects Versions: 5.10.0 Environment: Suse Linux 12.3 Reporter: Huan Bui Priority: Minor CMS (C++ client) crashed when calling ActiveMQ::initializeLibrary(). Here is the backtrace from gdb #0 decaf::net::InetAddress::getLocalHost () at decaf/net/InetAddress.cpp:174 #1 0x7f071766247b in IdGeneratorKernel (this=0x31de9d0) at activemq/util/IdGenerator.cpp:60 #2 activemq::util::IdGenerator::initialize () at activemq/util/IdGenerator.cpp:169 #3 0x0043fe30 in main () apr_sockaddr_info_get returned APR_SUCCESS but address is NULL causing the segfault at InetAddress.cpp line 174. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (AMQ-5325) CMS (C++ client) crashed if getLocalHost failed
[
https://issues.apache.org/jira/browse/AMQ-5325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Huan Bui updated AMQ-5325:
--
Attachment: InetAddress.cpp
if (result != APR_SUCCESS || address == NULL) {
throw UnknownHostException(__FILE__, __LINE__, Could not resolve
the IP Address of this host.);
}
Add address == NULL condition to prevent the crash.
CMS (C++ client) crashed if getLocalHost failed
---
Key: AMQ-5325
URL: https://issues.apache.org/jira/browse/AMQ-5325
Project: ActiveMQ
Issue Type: Bug
Components: CMS (C++ client)
Affects Versions: 5.10.0
Environment: Suse Linux 12.3
Reporter: Huan Bui
Priority: Minor
Attachments: InetAddress.cpp
CMS (C++ client) crashed when calling ActiveMQ::initializeLibrary(). Here is
the backtrace from gdb
#0 decaf::net::InetAddress::getLocalHost () at decaf/net/InetAddress.cpp:174
#1 0x7f071766247b in IdGeneratorKernel (this=0x31de9d0) at
activemq/util/IdGenerator.cpp:60
#2 activemq::util::IdGenerator::initialize () at
activemq/util/IdGenerator.cpp:169
#3 0x0043fe30 in main ()
apr_sockaddr_info_get returned APR_SUCCESS but address is NULL causing the
segfault at InetAddress.cpp line 174.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Moved] (AMQCPP-550) CMS (C++ client) crashed if getLocalHost failed
[ https://issues.apache.org/jira/browse/AMQCPP-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish moved AMQ-5325 to AMQCPP-550: -- Component/s: (was: CMS (C++ client)) Decaf Affects Version/s: (was: 5.10.0) 3.8.3 Key: AMQCPP-550 (was: AMQ-5325) Project: ActiveMQ C++ Client (was: ActiveMQ) CMS (C++ client) crashed if getLocalHost failed --- Key: AMQCPP-550 URL: https://issues.apache.org/jira/browse/AMQCPP-550 Project: ActiveMQ C++ Client Issue Type: Bug Components: Decaf Affects Versions: 3.8.3 Environment: Suse Linux 12.3 Reporter: Huan Bui Priority: Minor Attachments: InetAddress.cpp CMS (C++ client) crashed when calling ActiveMQ::initializeLibrary(). Here is the backtrace from gdb #0 decaf::net::InetAddress::getLocalHost () at decaf/net/InetAddress.cpp:174 #1 0x7f071766247b in IdGeneratorKernel (this=0x31de9d0) at activemq/util/IdGenerator.cpp:60 #2 activemq::util::IdGenerator::initialize () at activemq/util/IdGenerator.cpp:169 #3 0x0043fe30 in main () apr_sockaddr_info_get returned APR_SUCCESS but address is NULL causing the segfault at InetAddress.cpp line 174. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (AMQCPP-550) CMS (C++ client) crashed if getLocalHost failed
[ https://issues.apache.org/jira/browse/AMQCPP-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQCPP-550. - Resolution: Fixed Fix Version/s: 3.9.0 3.8.4 Assignee: Timothy Bish Fixed, thanks. CMS (C++ client) crashed if getLocalHost failed --- Key: AMQCPP-550 URL: https://issues.apache.org/jira/browse/AMQCPP-550 Project: ActiveMQ C++ Client Issue Type: Bug Components: Decaf Affects Versions: 3.8.3 Environment: Suse Linux 12.3 Reporter: Huan Bui Assignee: Timothy Bish Priority: Minor Fix For: 3.8.4, 3.9.0 Attachments: InetAddress.cpp CMS (C++ client) crashed when calling ActiveMQ::initializeLibrary(). Here is the backtrace from gdb #0 decaf::net::InetAddress::getLocalHost () at decaf/net/InetAddress.cpp:174 #1 0x7f071766247b in IdGeneratorKernel (this=0x31de9d0) at activemq/util/IdGenerator.cpp:60 #2 activemq::util::IdGenerator::initialize () at activemq/util/IdGenerator.cpp:169 #3 0x0043fe30 in main () apr_sockaddr_info_get returned APR_SUCCESS but address is NULL causing the segfault at InetAddress.cpp line 174. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (AMQNET-454) Add Apache Qpid provider to NMS
[
https://issues.apache.org/jira/browse/AMQNET-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14104549#comment-14104549
]
Chuck Rolke commented on AMQNET-454:
Hi Jim,
Thanks for your help. This version works better than any before it. In fact I
think it is ready for a general release.
I tested it on a Windows 7 box with fresh checkouts and having never built
Apache.NMS before. Everything worked as expected. The test system has both
Visual Studio 2008, 2010, and 2012. Here is what I did:
* Execute *nant install-all* for vendors
org.apache.qpid\Apache.Qpid\0.28.0.16239 and org.nunit\NUnit\2.5.8.
* Execute *nant install-all* in Apache.NMS. This installed net-2.0, net-3.5,
and net-4.0.
* Execute *nant* in Apache.NMS.AMQP\trunk. This builds net-2.0 and net-4.0
Apache.NMS.AMQP.dll mission code.
* Open the VS2008-amqp.sln.
** Build Debug and Release vs2008-HelloWorld
** Build Debug vs2008-amqp-test
* Open the VS2010-amqp.sln.
** Build Debug and Release vs2010-HelloWorld
** Build Debug vs2010-amqp-test
* Start Qpidd broker (qpidd --auth no --no-data-dir --load-module amqpd.dll) on
port 5672. An ActiveMQ broker with amqp support works as well. Tests and
HelloWorld require AMQP 1.0 broker support.
* Execute NUnit tests (84 tests pass, 0 fail, 0 skipped in both runs)
** cd .\build\net-2.0\debug
** c:\program files (x86)\NUnit 2.5.8\bin\net-2.0\nunit-x86.exe
.\Apache.NMS.AMQP.Test.dll
** cd ..\..\net-4.0\debug
** c:\program files (x86)\NUnit 2.5.8\bin\net-2.0\nunit-x86.exe
.\Apache.NMS.AMQP.Test.dll
* CD into the four build directories and execute the four vs20xx-HelloWorld.exe
programs.
I'm eager to see this project move out of the incubation phase and become a
supported provider. Maybe that one last patch in NMSConnectionFactory:
{noformat}
+ schemaProviderFactoryMap[amqp] = new
ProviderFactoryInfo(Apache.NMS.AMQP, Apache.NMS.AMQP.ConnectionFactory);
{noformat}
Let me know if there's anything else to clean up before this can move forward.
Thanks,
-Chuck
Add Apache Qpid provider to NMS
---
Key: AMQNET-454
URL: https://issues.apache.org/jira/browse/AMQNET-454
Project: ActiveMQ .Net
Issue Type: New Feature
Components: NMS
Affects Versions: 1.6.0
Reporter: Chuck Rolke
Assignee: Jim Gomes
Attachments: Apache.NMS.AMQP-21-Add-Map-Text-Message-tests.patch,
Apache.NMS.AMQP-22-add-more-tests.patch,
Apache.NMS.AMQP-23a-MessageDeliveryTest.cs.patch,
Apache.NMS.AMQP-23b-MSConnectionFactoryTest.cs.patch,
Apache.NMS.AMQP-23c-NmsConsoleTracer.cs.patch,
Apache.NMS.AMQP-23d-addTraceStatements.patch,
Apache.NMS.AMQP-23e-addFilesToTestProject.patch,
Apache.NMS.AMQP-24-tidy-up.patch, Apache.NMS.AMQP-25-use-qpid-0.28.patch,
Apache.NMS.AMQP-26-hook-in-session-ack.patch,
Apache.NMS.AMQP-27-nant-unmanaged-copy.patch,
Apache.NMS.AMQP-28-close-qpid-sender-receiver.patch,
Apache.NMS.AMQP-29-stop-sessions-before-connection.patch,
Apache.NMS.AMQP-30-lock-x86-only.patch,
Apache.NMS.AMQP-Add-message-cloning-19.patch,
Apache.NMS.AMQP-add-connection-property-table-17.patch,
Apache.NMS.AMQP-add-hello-world-example-11.patch,
Apache.NMS.AMQP-add-hello-world-example-retry-12.patch,
Apache.NMS.AMQP-add-hello-world-to-vs2008-18.patch,
Apache.NMS.AMQP-add-message-conversions-06.patch,
Apache.NMS.AMQP-add-message-test-20.patch,
Apache.NMS.AMQP-add-topic-05.patch,
Apache.NMS.AMQP-connectionProperties-07.patch,
Apache.NMS.AMQP-copyrights-conn-str-fix-09.patch,
Apache.NMS.AMQP-fix-destination-to-use-qpid-address-10.patch,
Apache.NMS.AMQP-fix-helloworld-13.patch,
Apache.NMS.AMQP-fix-list-message-body-15.patch,
Apache.NMS.AMQP-fix-map-message-body-14.patch,
Apache.NMS.AMQP-fix-replyTo-and-receive-timeouts-16.patch,
Apache.NMS.AMQP-object-lifecycle-04.patch,
Apache.NMS.AMQP-provider-configs-03.patch,
Apache.NMS.AMQP-qpid-object-lifecycle-02.patch,
Apache.NMS.AMQP-set-connection-credentials-08.patch, RELEASE.txt,
vendor-Apache.QPID-00-replace-debug-with-release.patch,
vendor-QPid-nant-01.patch
NMS includes various providers ActiveMQ, STOMP, MSMQ, EMS, and WCF. This
issue proposes to add [Apache Qpid|http://qpid.apache.org/index.html] as
another provider.
Qpid has a [Messaging .NET
Binding|http://qpid.apache.org/releases/qpid-0.24/programming/book/ch05.html]
that is layered on top of the native C++ Qpid Messaging client. The Qpid .NET
binding is attractive as the hook for tying in Qpid as an NMS provider.
The proposed NMS provider supports [AMQP
1.0|http://qpid.apache.org/amqp.html] by including [Qpid
Proton|http://qpid.apache.org/proton/index.html] libraries.
From a high level this addition to Active.NMS would consist of two parts
* Add Qpid as a vendor kit. This includes both the Qpid .NET Binding and Qpid
Proton in a single kit.
[jira] [Commented] (AMQNET-454) Add Apache Qpid provider to NMS
[ https://issues.apache.org/jira/browse/AMQNET-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14104564#comment-14104564 ] Jim Gomes commented on AMQNET-454: -- Hi Chuck, That's fantastic! I added the default provider mapping to the NMSConnectionFactory. I'm excited to see this new provider implementation become part of the product. Add Apache Qpid provider to NMS --- Key: AMQNET-454 URL: https://issues.apache.org/jira/browse/AMQNET-454 Project: ActiveMQ .Net Issue Type: New Feature Components: NMS Affects Versions: 1.6.0 Reporter: Chuck Rolke Assignee: Jim Gomes Attachments: Apache.NMS.AMQP-21-Add-Map-Text-Message-tests.patch, Apache.NMS.AMQP-22-add-more-tests.patch, Apache.NMS.AMQP-23a-MessageDeliveryTest.cs.patch, Apache.NMS.AMQP-23b-MSConnectionFactoryTest.cs.patch, Apache.NMS.AMQP-23c-NmsConsoleTracer.cs.patch, Apache.NMS.AMQP-23d-addTraceStatements.patch, Apache.NMS.AMQP-23e-addFilesToTestProject.patch, Apache.NMS.AMQP-24-tidy-up.patch, Apache.NMS.AMQP-25-use-qpid-0.28.patch, Apache.NMS.AMQP-26-hook-in-session-ack.patch, Apache.NMS.AMQP-27-nant-unmanaged-copy.patch, Apache.NMS.AMQP-28-close-qpid-sender-receiver.patch, Apache.NMS.AMQP-29-stop-sessions-before-connection.patch, Apache.NMS.AMQP-30-lock-x86-only.patch, Apache.NMS.AMQP-Add-message-cloning-19.patch, Apache.NMS.AMQP-add-connection-property-table-17.patch, Apache.NMS.AMQP-add-hello-world-example-11.patch, Apache.NMS.AMQP-add-hello-world-example-retry-12.patch, Apache.NMS.AMQP-add-hello-world-to-vs2008-18.patch, Apache.NMS.AMQP-add-message-conversions-06.patch, Apache.NMS.AMQP-add-message-test-20.patch, Apache.NMS.AMQP-add-topic-05.patch, Apache.NMS.AMQP-connectionProperties-07.patch, Apache.NMS.AMQP-copyrights-conn-str-fix-09.patch, Apache.NMS.AMQP-fix-destination-to-use-qpid-address-10.patch, Apache.NMS.AMQP-fix-helloworld-13.patch, Apache.NMS.AMQP-fix-list-message-body-15.patch, Apache.NMS.AMQP-fix-map-message-body-14.patch, Apache.NMS.AMQP-fix-replyTo-and-receive-timeouts-16.patch, Apache.NMS.AMQP-object-lifecycle-04.patch, Apache.NMS.AMQP-provider-configs-03.patch, Apache.NMS.AMQP-qpid-object-lifecycle-02.patch, Apache.NMS.AMQP-set-connection-credentials-08.patch, RELEASE.txt, vendor-Apache.QPID-00-replace-debug-with-release.patch, vendor-QPid-nant-01.patch NMS includes various providers ActiveMQ, STOMP, MSMQ, EMS, and WCF. This issue proposes to add [Apache Qpid|http://qpid.apache.org/index.html] as another provider. Qpid has a [Messaging .NET Binding|http://qpid.apache.org/releases/qpid-0.24/programming/book/ch05.html] that is layered on top of the native C++ Qpid Messaging client. The Qpid .NET binding is attractive as the hook for tying in Qpid as an NMS provider. The proposed NMS provider supports [AMQP 1.0|http://qpid.apache.org/amqp.html] by including [Qpid Proton|http://qpid.apache.org/proton/index.html] libraries. From a high level this addition to Active.NMS would consist of two parts * Add Qpid as a vendor kit. This includes both the Qpid .NET Binding and Qpid Proton in a single kit. * Add the new provider with code linking NMS to Qpid -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (AMQNET-454) Add Apache Qpid provider to NMS
[ https://issues.apache.org/jira/browse/AMQNET-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14104577#comment-14104577 ] Timothy Bish commented on AMQNET-454: - @Chuck. Before there could be a release for the AMQP client it needs to have a space on the NMS Wiki with documentation covering things like building, getting started, release pages, etc. You need to follow the Apache process by having an ICLA on file (http://activemq.apache.org/contributing.html) and then asking on the mailing list for access to the Wiki so you can start building the space in Confluence. Add Apache Qpid provider to NMS --- Key: AMQNET-454 URL: https://issues.apache.org/jira/browse/AMQNET-454 Project: ActiveMQ .Net Issue Type: New Feature Components: NMS Affects Versions: 1.6.0 Reporter: Chuck Rolke Assignee: Jim Gomes Attachments: Apache.NMS.AMQP-21-Add-Map-Text-Message-tests.patch, Apache.NMS.AMQP-22-add-more-tests.patch, Apache.NMS.AMQP-23a-MessageDeliveryTest.cs.patch, Apache.NMS.AMQP-23b-MSConnectionFactoryTest.cs.patch, Apache.NMS.AMQP-23c-NmsConsoleTracer.cs.patch, Apache.NMS.AMQP-23d-addTraceStatements.patch, Apache.NMS.AMQP-23e-addFilesToTestProject.patch, Apache.NMS.AMQP-24-tidy-up.patch, Apache.NMS.AMQP-25-use-qpid-0.28.patch, Apache.NMS.AMQP-26-hook-in-session-ack.patch, Apache.NMS.AMQP-27-nant-unmanaged-copy.patch, Apache.NMS.AMQP-28-close-qpid-sender-receiver.patch, Apache.NMS.AMQP-29-stop-sessions-before-connection.patch, Apache.NMS.AMQP-30-lock-x86-only.patch, Apache.NMS.AMQP-Add-message-cloning-19.patch, Apache.NMS.AMQP-add-connection-property-table-17.patch, Apache.NMS.AMQP-add-hello-world-example-11.patch, Apache.NMS.AMQP-add-hello-world-example-retry-12.patch, Apache.NMS.AMQP-add-hello-world-to-vs2008-18.patch, Apache.NMS.AMQP-add-message-conversions-06.patch, Apache.NMS.AMQP-add-message-test-20.patch, Apache.NMS.AMQP-add-topic-05.patch, Apache.NMS.AMQP-connectionProperties-07.patch, Apache.NMS.AMQP-copyrights-conn-str-fix-09.patch, Apache.NMS.AMQP-fix-destination-to-use-qpid-address-10.patch, Apache.NMS.AMQP-fix-helloworld-13.patch, Apache.NMS.AMQP-fix-list-message-body-15.patch, Apache.NMS.AMQP-fix-map-message-body-14.patch, Apache.NMS.AMQP-fix-replyTo-and-receive-timeouts-16.patch, Apache.NMS.AMQP-object-lifecycle-04.patch, Apache.NMS.AMQP-provider-configs-03.patch, Apache.NMS.AMQP-qpid-object-lifecycle-02.patch, Apache.NMS.AMQP-set-connection-credentials-08.patch, RELEASE.txt, vendor-Apache.QPID-00-replace-debug-with-release.patch, vendor-QPid-nant-01.patch NMS includes various providers ActiveMQ, STOMP, MSMQ, EMS, and WCF. This issue proposes to add [Apache Qpid|http://qpid.apache.org/index.html] as another provider. Qpid has a [Messaging .NET Binding|http://qpid.apache.org/releases/qpid-0.24/programming/book/ch05.html] that is layered on top of the native C++ Qpid Messaging client. The Qpid .NET binding is attractive as the hook for tying in Qpid as an NMS provider. The proposed NMS provider supports [AMQP 1.0|http://qpid.apache.org/amqp.html] by including [Qpid Proton|http://qpid.apache.org/proton/index.html] libraries. From a high level this addition to Active.NMS would consist of two parts * Add Qpid as a vendor kit. This includes both the Qpid .NET Binding and Qpid Proton in a single kit. * Add the new provider with code linking NMS to Qpid -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (AMQNET-454) Add Apache Qpid provider to NMS
[ https://issues.apache.org/jira/browse/AMQNET-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14104639#comment-14104639 ] Chuck Rolke commented on AMQNET-454: I have an ICLA on file and I've been a committer and PMC member of the qpid project for about four years. See https://qpid.apache.org/contributors.html I'll send mail to the list shortly. -Chuck Add Apache Qpid provider to NMS --- Key: AMQNET-454 URL: https://issues.apache.org/jira/browse/AMQNET-454 Project: ActiveMQ .Net Issue Type: New Feature Components: NMS Affects Versions: 1.6.0 Reporter: Chuck Rolke Assignee: Jim Gomes Attachments: Apache.NMS.AMQP-21-Add-Map-Text-Message-tests.patch, Apache.NMS.AMQP-22-add-more-tests.patch, Apache.NMS.AMQP-23a-MessageDeliveryTest.cs.patch, Apache.NMS.AMQP-23b-MSConnectionFactoryTest.cs.patch, Apache.NMS.AMQP-23c-NmsConsoleTracer.cs.patch, Apache.NMS.AMQP-23d-addTraceStatements.patch, Apache.NMS.AMQP-23e-addFilesToTestProject.patch, Apache.NMS.AMQP-24-tidy-up.patch, Apache.NMS.AMQP-25-use-qpid-0.28.patch, Apache.NMS.AMQP-26-hook-in-session-ack.patch, Apache.NMS.AMQP-27-nant-unmanaged-copy.patch, Apache.NMS.AMQP-28-close-qpid-sender-receiver.patch, Apache.NMS.AMQP-29-stop-sessions-before-connection.patch, Apache.NMS.AMQP-30-lock-x86-only.patch, Apache.NMS.AMQP-Add-message-cloning-19.patch, Apache.NMS.AMQP-add-connection-property-table-17.patch, Apache.NMS.AMQP-add-hello-world-example-11.patch, Apache.NMS.AMQP-add-hello-world-example-retry-12.patch, Apache.NMS.AMQP-add-hello-world-to-vs2008-18.patch, Apache.NMS.AMQP-add-message-conversions-06.patch, Apache.NMS.AMQP-add-message-test-20.patch, Apache.NMS.AMQP-add-topic-05.patch, Apache.NMS.AMQP-connectionProperties-07.patch, Apache.NMS.AMQP-copyrights-conn-str-fix-09.patch, Apache.NMS.AMQP-fix-destination-to-use-qpid-address-10.patch, Apache.NMS.AMQP-fix-helloworld-13.patch, Apache.NMS.AMQP-fix-list-message-body-15.patch, Apache.NMS.AMQP-fix-map-message-body-14.patch, Apache.NMS.AMQP-fix-replyTo-and-receive-timeouts-16.patch, Apache.NMS.AMQP-object-lifecycle-04.patch, Apache.NMS.AMQP-provider-configs-03.patch, Apache.NMS.AMQP-qpid-object-lifecycle-02.patch, Apache.NMS.AMQP-set-connection-credentials-08.patch, RELEASE.txt, vendor-Apache.QPID-00-replace-debug-with-release.patch, vendor-QPid-nant-01.patch NMS includes various providers ActiveMQ, STOMP, MSMQ, EMS, and WCF. This issue proposes to add [Apache Qpid|http://qpid.apache.org/index.html] as another provider. Qpid has a [Messaging .NET Binding|http://qpid.apache.org/releases/qpid-0.24/programming/book/ch05.html] that is layered on top of the native C++ Qpid Messaging client. The Qpid .NET binding is attractive as the hook for tying in Qpid as an NMS provider. The proposed NMS provider supports [AMQP 1.0|http://qpid.apache.org/amqp.html] by including [Qpid Proton|http://qpid.apache.org/proton/index.html] libraries. From a high level this addition to Active.NMS would consist of two parts * Add Qpid as a vendor kit. This includes both the Qpid .NET Binding and Qpid Proton in a single kit. * Add the new provider with code linking NMS to Qpid -- This message was sent by Atlassian JIRA (v6.2#6252)
Re: ActiveMQ/OpenWire on linux - error Remote wire format magic not valid
I have the same problem, any one knows how to handle it? thanks -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-OpenWire-on-linux-error-Remote-wire-format-magic-not-valid-tp3453117p4684796.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
[jira] [Created] (AMQ-5326) SslTransport doesn't support soWriteTimeout
Lei Huang created AMQ-5326: -- Summary: SslTransport doesn't support soWriteTimeout Key: AMQ-5326 URL: https://issues.apache.org/jira/browse/AMQ-5326 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.5.1 Environment: Linux Reporter: Lei Huang ActimveMQ 5.5.1 doesn't support soWriteTimeout for SslTransport. ssl://0.0.0.0:61616?transport.soWriteTimeout=2000 will throw IllegalArgumentException. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (AMQ-5326) SslTransport doesn't support soWriteTimeout
[
https://issues.apache.org/jira/browse/AMQ-5326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14105011#comment-14105011
]
Lei Huang commented on AMQ-5326:
Fixed.
--- a/src/main/java/org/apache/activemq/transport/tcp/TcpTransportFactory.java
+++ b/src/main/java/org/apache/activemq/transport/tcp/TcpTransportFactory.java
@@ -111,6 +111,10 @@ public class TcpTransportFactory extends TransportFactory {
return super.compositeConfigure(transport, format, options);
}
+protected Transport swtCompositeConfigure(Transport transport, WireFormat
format, Map options) {
+return super.compositeConfigure(transport, format, options);
+}
+
/**
* Returns true if the inactivity monitor should be used on the transport
*/
~
--- a/src/main/java/org/apache/activemq/transport/tcp/SslTransportFactory.java
+++ b/src/main/java/org/apache/activemq/transport/tcp/SslTransportFactory.java
@@ -114,8 +114,8 @@ public class SslTransportFactory extends
TcpTransportFactory {
if (format instanceof OpenWireFormat) {
transport = new WireFormatNegotiator(transport,
(OpenWireFormat)format, sslTransport.getMinmumWireFormatVersion());
}
-
-return transport;
+
+return super.swtCompositeConfigure(transport, format, options);
}
/**
SslTransport doesn't support soWriteTimeout
---
Key: AMQ-5326
URL: https://issues.apache.org/jira/browse/AMQ-5326
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.5.1
Environment: Linux
Reporter: Lei Huang
ActimveMQ 5.5.1 doesn't support soWriteTimeout for SslTransport.
ssl://0.0.0.0:61616?transport.soWriteTimeout=2000
will throw IllegalArgumentException.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
Build failed in Jenkins: ActiveMQ-Trunk-Deploy #1035
See https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/1035/ -- [...truncated 14694 lines...] [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/ws/activemq-runtime-config/target/activemq-runtime-config-5.11-SNAPSHOT-sources.jar to org.apache.activemq/activemq-runtime-config/5.11-20140821.045404-70/activemq-runtime-config-5.11-20140821.045404-70-sources.jar [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/ws/activemq-runtime-config/target/activemq-runtime-config-5.11-SNAPSHOT-javadoc.jar to org.apache.activemq/activemq-runtime-config/5.11-20140821.045404-70/activemq-runtime-config-5.11-20140821.045404-70-javadoc.jar Sending artifact delta relative to ActiveMQ-Trunk-Deploy ? ActiveMQ :: Runtime Configuration #1034 Archived 4 artifacts Archive block size is 32768 Received 0 blocks and 24283240 bytes Compression is 0.0% Took 7 sec [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/ws/activemq-pool/pom.xml to org.apache.activemq/activemq-pool/5.11-SNAPSHOT/activemq-pool-5.11-SNAPSHOT.pom [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/ws/activemq-pool/target/activemq-pool-5.11-SNAPSHOT.jar to org.apache.activemq/activemq-pool/5.11-20140821.044831-71/activemq-pool-5.11-20140821.044831-71.jar [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/ws/activemq-pool/target/activemq-pool-5.11-SNAPSHOT-sources.jar to org.apache.activemq/activemq-pool/5.11-20140821.044831-71/activemq-pool-5.11-20140821.044831-71-sources.jar [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/ws/activemq-pool/target/activemq-pool-5.11-SNAPSHOT-javadoc.jar to org.apache.activemq/activemq-pool/5.11-20140821.044831-71/activemq-pool-5.11-20140821.044831-71-javadoc.jar Sending artifact delta relative to ActiveMQ-Trunk-Deploy ? ActiveMQ :: Pool #1034 Archived 4 artifacts Archive block size is 32768 Received 0 blocks and 114683 bytes Compression is 0.0% Took 75 ms [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/ws/activemq-stomp/pom.xml to org.apache.activemq/activemq-stomp/5.11-SNAPSHOT/activemq-stomp-5.11-SNAPSHOT.pom [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/ws/activemq-stomp/target/activemq-stomp-5.11-SNAPSHOT.jar to org.apache.activemq/activemq-stomp/5.11-20140821.044545-71/activemq-stomp-5.11-20140821.044545-71.jar [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/ws/activemq-stomp/target/activemq-stomp-5.11-SNAPSHOT-sources.jar to org.apache.activemq/activemq-stomp/5.11-20140821.044545-71/activemq-stomp-5.11-20140821.044545-71-sources.jar [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/ws/activemq-stomp/target/activemq-stomp-5.11-SNAPSHOT-javadoc.jar to org.apache.activemq/activemq-stomp/5.11-20140821.044545-71/activemq-stomp-5.11-20140821.044545-71-javadoc.jar Sending artifact delta relative to ActiveMQ-Trunk-Deploy ? ActiveMQ :: STOMP Protocol #1034 Archived 4 artifacts Archive block size is 32768 Received 0 blocks and 549804 bytes Compression is 0.0% Took 0.14 sec [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/ws/activemq-run/dependency-reduced-pom.xml to org.apache.activemq/activemq-run/5.11-SNAPSHOT/activemq-run-5.11-SNAPSHOT.pom [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/ws/activemq-run/target/activemq-run-5.11-SNAPSHOT.jar to org.apache.activemq/activemq-run/5.11-20140821.045235-71/activemq-run-5.11-20140821.045235-71.jar Sending artifact delta relative to ActiveMQ-Trunk-Deploy ? ActiveMQ :: Run Jar #1034 Archived 2 artifacts Archive block size is 32768 Received 0 blocks and 19043 bytes Compression is 0.0% Took 37 ms [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/ws/activemq-mqtt/pom.xml to org.apache.activemq/activemq-mqtt/5.11-SNAPSHOT/activemq-mqtt-5.11-SNAPSHOT.pom [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/ws/activemq-mqtt/target/activemq-mqtt-5.11-SNAPSHOT.jar to org.apache.activemq/activemq-mqtt/5.11-20140821.044605-70/activemq-mqtt-5.11-20140821.044605-70.jar [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/ws/activemq-mqtt/target/activemq-mqtt-5.11-SNAPSHOT-sources.jar to org.apache.activemq/activemq-mqtt/5.11-20140821.044605-70/activemq-mqtt-5.11-20140821.044605-70-sources.jar [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/ws/activemq-mqtt/target/activemq-mqtt-5.11-SNAPSHOT-javadoc.jar to org.apache.activemq/activemq-mqtt/5.11-20140821.044605-70/activemq-mqtt-5.11-20140821.044605-70-javadoc.jar Sending artifact delta relative to ActiveMQ-Trunk-Deploy ? ActiveMQ :: MQTT Protocol #1034 Archived 4 artifacts Archive block size is 32768 Received 0 blocks and 424658 bytes Compression is 0.0% Took 1.3 sec [JENKINS] Archiving
Build failed in Jenkins: ActiveMQ-Trunk-Deploy » ActiveMQ :: Performance Test Plugin #1035
See https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq.tooling$activemq-perf-maven-plugin/1035/ -- [INFO] [INFO] [INFO] Building ActiveMQ :: Performance Test Plugin 5.11-SNAPSHOT [INFO] [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ activemq-perf-maven-plugin --- [INFO] Deleting https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq.tooling$activemq-perf-maven-plugin/ws/target [INFO] [INFO] --- maven-enforcer-plugin:1.0.1:enforce (default) @ activemq-perf-maven-plugin --- [INFO] [INFO] --- maven-bundle-plugin:2.3.7:cleanVersions (cleanVersions) @ activemq-perf-maven-plugin --- [INFO] [INFO] --- maven-plugin-plugin:3.1:descriptor (default-descriptor) @ activemq-perf-maven-plugin --- [INFO] Using 'UTF-8' encoding to read mojo metadata. [INFO] Applying mojo extractor for language: java-annotations [INFO] Mojo extractor for language: java-annotations found 0 mojo descriptors. [INFO] Applying mojo extractor for language: java [INFO] Mojo extractor for language: java found 3 mojo descriptors. [INFO] Applying mojo extractor for language: bsh [INFO] Mojo extractor for language: bsh found 0 mojo descriptors. [INFO] [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ activemq-perf-maven-plugin --- [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ activemq-perf-maven-plugin --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 1 resource [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ activemq-perf-maven-plugin --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 43 source files to https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq.tooling$activemq-perf-maven-plugin/ws/target/classes [WARNING] https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq.tooling$activemq-perf-maven-plugin/ws/src/main/java/org/apache/activemq/tool/spi/ClassLoaderSPIConnectionFactory.java:[60,35] toURL() in java.io.File has been deprecated [WARNING] https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq.tooling$activemq-perf-maven-plugin/ws/src/main/java/org/apache/activemq/tool/spi/ClassLoaderSPIConnectionFactory.java:[67,54] toURL() in java.io.File has been deprecated [WARNING] https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq.tooling$activemq-perf-maven-plugin/ws/src/main/java/org/apache/activemq/tool/properties/ReflectionUtil.java:[74,48] non-varargs call of varargs method with inexact argument type for last parameter; cast to java.lang.Object for a varargs call cast to java.lang.Object[] for a non-varargs call and to suppress this warning [WARNING] https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq.tooling$activemq-perf-maven-plugin/ws/src/main/java/org/apache/activemq/tool/properties/ReflectionUtil.java:[205,77] non-varargs call of varargs method with inexact argument type for last parameter; cast to java.lang.Object for a varargs call cast to java.lang.Object[] for a non-varargs call and to suppress this warning [WARNING] https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq.tooling$activemq-perf-maven-plugin/ws/src/main/java/org/apache/activemq/tool/properties/ReflectionUtil.java:[215,80] non-varargs call of varargs method with inexact argument type for last parameter; cast to java.lang.Object for a varargs call cast to java.lang.Object[] for a non-varargs call and to suppress this warning [WARNING] https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq.tooling$activemq-perf-maven-plugin/ws/src/main/java/org/apache/activemq/maven/ProducerMojo.java: Some input files use unchecked or unsafe operations. [WARNING] https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq.tooling$activemq-perf-maven-plugin/ws/src/main/java/org/apache/activemq/maven/ProducerMojo.java: Recompile with -Xlint:unchecked for details. [INFO] [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ activemq-perf-maven-plugin --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq.tooling$activemq-perf-maven-plugin/ws/src/test/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ activemq-perf-maven-plugin --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 4 source files to
