[jira] [Commented] (AMQCPP-494) Commiting a session with a deleted consumer causes access violation

[Andrei Gheorghe (JIRA)]

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

Andrei Gheorghe commented on AMQCPP-494:


Apparently I've uploaded a different test file. This one works for me also. If 
I just call close() on the consumer there is no problem. But if I delete 
consumer then I get an access violation on session->commit(). Is this still a 
bug or it's something by design, maybe consumers aren't meant to be deleted 
like this?

> Commiting a session with a deleted consumer causes access violation
> ---
>
> Key: AMQCPP-494
> URL: https://issues.apache.org/jira/browse/AMQCPP-494
> Project: ActiveMQ C++ Client
>  Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Andrei Gheorghe
>Assignee: Timothy Bish
>Priority: Minor
> Attachments: test.cpp
>
>
> I'm not sure if this is a bug or if I'm using the library wrong.
> The attached test file will cause an access violation error when trying to 
> commit the session.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (AMQ-3694) Blocked/Slow advisory consumers in duplex network connector, eventually breaks request/reply with temps

[J CHEN (JIRA)]

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

J CHEN commented on AMQ-3694:
-

Does this problem affect 5.3.1 as well?  We are thinking about upgrading
08:55:25,314 - [ActiveMQ Transport: tcp:///10.2.50.44:61616] [WARN] 
[TransportConnection.java:290] : Async error occurred: javax.jms.JMSException: 
The destination temp-queue://ID:x-37275-1371171214828-0:2171:1 does not 
exist.

> Blocked/Slow advisory consumers in duplex network connector, eventually 
> breaks request/reply with temps
> ---
>
> Key: AMQ-3694
> URL: https://issues.apache.org/jira/browse/AMQ-3694
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, Connector
>Affects Versions: 5.5.0
>Reporter: Gary Tully
>Assignee: Gary Tully
>  Labels: activemq, blocking, networkconnector, requestreply, temp
> Fix For: 5.6.0
>
>
> In duplex network connectors, the destinations and temp advisories are not 
> acked. This leads to a buildup of advisory messages on the bridging broker 
> and missing advisories on the target.
> In the main, when the numbers of destinations is static and there are no temp 
> queues per roundtrip this goes unnoticed.
> If request/reply is used over a network with a temp queue per request (a bit 
> of an anti pattern, they are typically per connection), the problem is 
> quickly visible with the default prefetch. Very quickly advisories for temp 
> queue creation and producer consumers get blocked and communication comes to 
> a halt. 
> The root cause is that advisories are not acked in the duplex case so we can 
> only get 750 (.75*prefetch) of them before we block.
> symptom{code}javax.jms.JMSException: The destination 
> temp-queue://ID:xxx-xxx-0:7:17 does not exist.
> {code} or replies do not get propagated back because the consumer advisory is 
> blocked.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (AMQCPP-495) CPP clients support IPv6 and ssl transportation through http/socks(4or5) proxy

[Kimi Wu (JIRA)]

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

Kimi Wu updated AMQCPP-495:
---

Attachment: ipv6_proxy.patch

> CPP clients support IPv6 and ssl transportation through http/socks(4or5) proxy
> --
>
> Key: AMQCPP-495
> URL: https://issues.apache.org/jira/browse/AMQCPP-495
> Project: ActiveMQ C++ Client
>  Issue Type: New Feature
>  Components: Decaf, Transports
>Affects Versions: 3.4.5
>Reporter: Kimi Wu
>Assignee: Timothy Bish
>Priority: Minor
> Attachments: ipv6_proxy.patch
>
>
> 1. ActiveMQ broker supports IPv6 protocol. But current ActiveMQ-CPP clients 
> don't. My partner and I modified ActiveMQ-CPP 3.4.5 to support IPv6.
> 2. In some cases activemq-cpp clients have to connect to activemq through a 
> proxy. But current tcp/ssl transport does not provide this functionality.
> My partner and I modified ActiveMQ-CPP 3.4.5 to enable SSL transport to 
> support http/socks4/socks5 proxy.
> 3. In some cases the certification of ActiveMQ broker can't be regenerated. 
> However, ActiveMQ-CPP clients need the "commonName" field in the 
> certification matches the server host name. My partner and I modified 
> ActiveMQ-CPP 3.4.5 to overwrite the server host name.
> ***
> What is changed:
> A local patched ActiveMQ-CPP, based on 3.4.5, 
> which supports IPv6 and Http / Socks 4 / Socks 5 proxy for SSL transport.
> Proxy usgae:
> To enable proxy for SSL transport, use these system properties 
> property comments
> 
> decaf.net.ssl.proxyType values:http/socks4/socks5
> decaf.net.ssl.proxyHost proxy address
> decaf.net.ssl.proxyPort proxy port
> decaf.net.ssl.proxyUser proxy user name
> decaf.net.ssl.proxyPassword proxy password
> Overwriting server host name usage:
> To overwrite the field, use these system properties 
> property comments
> 
> decaf.net.ssl.serverNamethe name matched "CommonName" field
> source: ipv6_proxy.patch
> ***

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (AMQCPP-495) CPP clients support IPv6 and ssl transportation through http/socks(4or5) proxy

[Kimi Wu (JIRA)]

Kimi Wu created AMQCPP-495:
--

 Summary: CPP clients support IPv6 and ssl transportation through 
http/socks(4or5) proxy
 Key: AMQCPP-495
 URL: https://issues.apache.org/jira/browse/AMQCPP-495
 Project: ActiveMQ C++ Client
  Issue Type: New Feature
  Components: Decaf, Transports
Affects Versions: 3.4.5
Reporter: Kimi Wu
Assignee: Timothy Bish
Priority: Minor


1. ActiveMQ broker supports IPv6 protocol. But current ActiveMQ-CPP clients 
don't. My partner and I modified ActiveMQ-CPP 3.4.5 to support IPv6.

2. In some cases activemq-cpp clients have to connect to activemq through a 
proxy. But current tcp/ssl transport does not provide this functionality.
My partner and I modified ActiveMQ-CPP 3.4.5 to enable SSL transport to support 
http/socks4/socks5 proxy.

3. In some cases the certification of ActiveMQ broker can't be regenerated. 
However, ActiveMQ-CPP clients need the "commonName" field in the certification 
matches the server host name. My partner and I modified ActiveMQ-CPP 3.4.5 to 
overwrite the server host name.

***
What is changed:
A local patched ActiveMQ-CPP, based on 3.4.5, 
which supports IPv6 and Http / Socks 4 / Socks 5 proxy for SSL transport.

Proxy usgae:
To enable proxy for SSL transport, use these system properties 

property comments

decaf.net.ssl.proxyType values:http/socks4/socks5
decaf.net.ssl.proxyHost proxy address
decaf.net.ssl.proxyPort proxy port
decaf.net.ssl.proxyUser proxy user name
decaf.net.ssl.proxyPassword proxy password


Overwriting server host name usage:
To overwrite the field, use these system properties 

property comments

decaf.net.ssl.serverNamethe name matched "CommonName" field

source: ipv6_proxy.patch

***

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Build failed in Jenkins: ActiveMQ-Trunk-Deploy #804

[Apache Jenkins Server]

See 

Changes:

[tabish] https://issues.apache.org/jira/browse/AMQ-4589

Apply patch to work around known race condition.

[tabish] https://issues.apache.org/jira/browse/AMQ-3447

Apply workaround patch for this issue,

--
[...truncated 5847 lines...]
[INFO] ActiveMQ :: STOMP Protocol  SKIPPED
[INFO] ActiveMQ :: MQTT Protocol . SKIPPED
[INFO] ActiveMQ :: JDBC Store  SKIPPED
[INFO] ActiveMQ :: LevelDB Store . SKIPPED
[INFO] ActiveMQ :: RA  SKIPPED
[INFO] ActiveMQ :: Pool .. SKIPPED
[INFO] ActiveMQ :: Spring  SKIPPED
[INFO] ActiveMQ :: AMQP .. SKIPPED
[INFO] ActiveMQ :: Console ... SKIPPED
[INFO] ActiveMQ :: Unit Tests  SKIPPED
[INFO] ActiveMQ :: Camel . SKIPPED
[INFO] ActiveMQ :: HTTP Protocol Support . SKIPPED
[INFO] ActiveMQ :: All JAR bundle  SKIPPED
[INFO] ActiveMQ :: File Server ... SKIPPED
[INFO] ActiveMQ :: Log4j Appender  SKIPPED
[INFO] ActiveMQ :: Apache Karaf .. SKIPPED
[INFO] ActiveMQ :: RAR ... SKIPPED
[INFO] ActiveMQ :: Run Jar ... SKIPPED
[INFO] ActiveMQ :: Tooling ... SUCCESS [5.913s]
[INFO] ActiveMQ :: Memory Usage Test Plugin .. SKIPPED
[INFO] ActiveMQ :: Performance Test Plugin ... SKIPPED
[INFO] ActiveMQ :: StartUp Plugin  SKIPPED
[INFO] ActiveMQ :: Web ... SKIPPED
[INFO] ActiveMQ :: OSGi bundle ... SKIPPED
[INFO] ActiveMQ :: Blueprint . FAILURE [5.158s]
[INFO] ActiveMQ :: Web Demo .. SKIPPED
[INFO] ActiveMQ :: Web Console ... SKIPPED
[INFO] ActiveMQ :: Karaf Integration Tests ... SKIPPED
[INFO] ActiveMQ :: Integration Test :: Spring 3.1  SKIPPED
[INFO] ActiveMQ :: Assembly .. SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 1:15.359s
[INFO] Finished at: Thu Jun 20 03:08:19 UTC 2013
[INFO] Final Memory: 41M/981M
[INFO] 
[JENKINS] Archiving 
 to 
/home/hudson/hudson/jobs/ActiveMQ-Trunk-Deploy/modules/org.apache.activemq$activemq-parent/builds/2013-06-20_03-06-40/archive/org.apache.activemq/activemq-parent/5.9-SNAPSHOT/activemq-parent-5.9-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
/home/hudson/hudson/jobs/ActiveMQ-Trunk-Deploy/modules/org.apache.activemq$activemq-client/builds/2013-06-20_03-06-40/archive/org.apache.activemq/activemq-client/5.9-SNAPSHOT/activemq-client-5.9-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
/home/hudson/hudson/jobs/ActiveMQ-Trunk-Deploy/modules/org.apache.activemq$apache-activemq/builds/2013-06-20_03-06-44/archive/org.apache.activemq/apache-activemq/5.9-SNAPSHOT/apache-activemq-5.9-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
/home/hudson/hudson/jobs/ActiveMQ-Trunk-Deploy/modules/org.apache.activemq$activemq-camel/builds/2013-06-20_03-06-42/archive/org.apache.activemq/activemq-camel/5.9-SNAPSHOT/activemq-camel-5.9-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
/home/hudson/hudson/jobs/ActiveMQ-Trunk-Deploy/modules/org.apache.activemq.tooling$activemq-tooling/builds/2013-06-20_03-06-43/archive/org.apache.activemq.tooling/activemq-tooling/5.9-SNAPSHOT/activemq-tooling-5.9-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
/home/hudson/hudson/jobs/ActiveMQ-Trunk-Deploy/modules/org.apache.activemq$activemq-pool/builds/2013-06-20_03-06-42/archive/org.apache.activemq/activemq-pool/5.9-SNAPSHOT/activemq-pool-5.9-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
/home/hudson/hudson/jobs/ActiveMQ-Trunk-Deploy/modules/org.apache.activemq$activemq-karaf-itest/builds/2013-06-20_03-06-44/archive/org.apache.activemq/activemq-karaf-itest/5.9-SNAPSHOT/activemq-karaf-itest-5.9-

Build failed in Jenkins: ActiveMQ-Trunk-Deploy » ActiveMQ :: Blueprint #804

[Apache Jenkins Server]

See 


--
[INFO] 
[INFO] 
[INFO] Skipping ActiveMQ :: Memory Usage Test Plugin
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping ActiveMQ :: Performance Test Plugin
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping ActiveMQ :: StartUp Plugin
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping ActiveMQ :: Web
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping ActiveMQ :: OSGi bundle
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Building ActiveMQ :: Blueprint 5.9-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ activemq-blueprint ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.0.1:enforce (default) @ activemq-blueprint 
---
[INFO] 
[INFO] --- maven-bundle-plugin:2.3.7:cleanVersions (cleanVersions) @ 
activemq-blueprint ---
Jun 20, 2013 3:08:16 AM hudson.maven.ExecutedMojo 
WARNING: Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo
[INFO] [INFO] Building jar: 


[INFO] --- maven-source-plugin:2.2.1:jar (default-cli) @ activemq-blueprint ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.0.1:enforce (default) @ activemq-blueprint 
---
[INFO] 
[INFO] --- maven-bundle-plugin:2.3.7:cleanVersions (cleanVersions) @ 
activemq-blueprint ---
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ 
activemq-blueprint ---
[INFO] [debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] Copying 3 resources

[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
activemq-blueprint ---
[INFO] [INFO] No sources to compile

[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ 
activemq-blueprint ---
[debug] execute contextualize
[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources

[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
activemq-blueprint ---
[INFO] [INFO] No sources to compile

[INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ 
activemq-blueprint ---
[INFO] [INFO] Surefire report directory: 


---
 T E S T S
---

[INFO] --- maven-surefire-plugin:2.10:test (default-test) @ activemq-blueprint 
---

Results :

Tests run: 0, Failures: 0, Errors: 0, Skipped: 0

[JENKINS] Recording test results
[INFO] 
[INFO] --- maven-bundle-plugin:2.3.7:bundle (default-bundle) @ 
activemq-blueprint ---
[WARNING] Bundle org.apache.activemq:activemq-blueprint:bundle:5.9-SNAPSHOT : 
Instructions in Export-Package that are never used: org\.apache\.activemq.*.*
Classpath: 
Jar:.,Jar:org.apache.aries.blueprint,Jar:xbean-blueprint,Jar:commons-jexl,Jar:pax-logging-api

[WARNING] Bundle org.apache.activemq:activemq-blueprint:bundle:5.9-SNAPSHOT : 
Superf

Build failed in Jenkins: ActiveMQ-Trunk-Deploy » ActiveMQ :: Openwire Generator #804

[Apache Jenkins Server]

See 


--
[INFO] 
[INFO] 
[INFO] Building ActiveMQ :: Openwire Generator 5.9-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ 
activemq-openwire-generator ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.0.1:enforce (default) @ 
activemq-openwire-generator ---
[INFO] 
[INFO] --- maven-bundle-plugin:2.3.7:cleanVersions (cleanVersions) @ 
activemq-openwire-generator ---
Jun 20, 2013 3:07:45 AM hudson.maven.ExecutedMojo 
WARNING: Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo
[INFO] 
[INFO] --- maven-source-plugin:2.2.1:jar (default-cli) @ 
activemq-openwire-generator ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-enforcer-plugin:1.0.1:enforce (default) @ 
activemq-openwire-generator ---
[INFO] 
[INFO] --- maven-bundle-plugin:2.3.7:cleanVersions (cleanVersions) @ 
activemq-openwire-generator ---
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ 
activemq-openwire-generator ---
[INFO] [debug] execute contextualize

[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

--- maven-resources-plugin:2.5:resources (default-resources) @ 
activemq-openwire-generator ---
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ 
activemq-openwire-generator ---
[INFO] Compiling 18 source files to 

[INFO] [debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources

[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
activemq-openwire-generator ---
[INFO] [INFO] No sources to compile

[INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ 
activemq-openwire-generator ---
[INFO] 
[INFO] --- maven-surefire-plugin:2.10:test (default-test) @ 
activemq-openwire-generator ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ activemq-openwire-generator 
---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:3.1:attach-descriptor (attach-descriptor) @ 
activemq-openwire-generator ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.0.1:enforce (default) @ 
activemq-openwire-generator ---
[INFO] 
[INFO] --- maven-bundle-plugin:2.3.7:cleanVersions (cleanVersions) @ 
activemq-openwire-generator ---
Jun 20, 2013 3:07:50 AM hudson.maven.ExecutedMojo 
WARNING: Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo
[INFO] 
[INFO] --- maven-source-plugin:2.2.1:jar (attach-sources) @ 
activemq-openwire-generator ---
[WARNING] Artifact 
org.apache.activemq:activemq-openwire-generator:java-source:sources:5.9-SNAPSHOT
 already attached to project, ignoring duplicate
[INFO] 
[INFO] --- maven-javadoc-plugin:2.8.1:jar (attach-javadocs) @ 
activemq-openwire-generator ---
[INFO] 
Loading source files for package org.apache.activemq.openwire.tool...
Constructing Javadoc information...
Standard Doclet version 1.6.0_45
Building tree for all the packages and classes...
Generating 

Generating 

Generating 

Generating 

Generating 

[jira] [Commented] (AMQ-4585) MQTT BlockingConnection.receive fails when receiving pending messages after reconnect without cleaning session

[Timothy Bish (JIRA)]

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

Timothy Bish commented on AMQ-4585:
---

The problem is a tricky one, it looks like there might be an issue in the MQTT 
client.  The issue happens on subscribe when for some reason the client 
receives two SUBACK frames when there appears to only have been one sent.  You 
can see it in this trace log where the SUBSCRIBE followed by a PUBLISH results 
in two SUBACK frames and the second one causes the client to bail.  

{noformat}
2013-06-19 16:50:40,556 | DEBUG | MQTTProtocolConverter  | MQTT Client 
MQTT-Sub-Client connected.
2013-06-19 16:50:40,557 | INFO  | MQTTTest   | Client 
Received:
MQTTFrame { type: CONNACK, qos: AT_MOST_ONCE, dup:false }
2013-06-19 16:50:40,557 | INFO  | MQTTTest   | MQTT login 
accepted
2013-06-19 16:50:40,557 | INFO  | MQTTTest   | Client Sent:
MQTTFrame { type: SUBSCRIBE, qos: AT_LEAST_ONCE, dup:false }
2013-06-19 16:50:40,559 | TRACE | MQTTIO | Received: 
MQTTFrame { type: SUBSCRIBE, qos: AT_LEAST_ONCE, dup:false }
2013-06-19 16:50:40,562 | TRACE | MQTTIO | Sending: 
MQTTFrame { type: SUBACK, qos: AT_MOST_ONCE, dup:false }
2013-06-19 16:50:40,562 | TRACE | MQTTIO | Sending: 
MQTTFrame { type: PUBLISH, qos: AT_LEAST_ONCE, dup:false }
2013-06-19 16:50:40,562 | INFO  | MQTTTest   | Client 
Received:
MQTTFrame { type: SUBACK, qos: AT_MOST_ONCE, dup:false }
2013-06-19 16:50:40,562 | INFO  | MQTTTest   | Client 
Received:
MQTTFrame { type: SUBACK, qos: AT_MOST_ONCE, dup:false }
2013-06-19 16:50:40,562 | INFO  | MQTTTest   | Fatal 
connection failure: %s
java.net.ProtocolException: Command from server contained an invalid message 
id: 1
at 
org.fusesource.mqtt.client.CallbackConnection.completeRequest(CallbackConnection.java:723)
at 
org.fusesource.mqtt.client.CallbackConnection.processFrame(CallbackConnection.java:762)
at 
org.fusesource.mqtt.client.CallbackConnection.access$1500(CallbackConnection.java:51)
at 
org.fusesource.mqtt.client.CallbackConnection$6.onTransportCommand(CallbackConnection.java:392)
at 
org.fusesource.hawtdispatch.transport.TcpTransport.drainInbound(TcpTransport.java:659)
at 
org.fusesource.hawtdispatch.transport.TcpTransport$6.run(TcpTransport.java:538)
at 
org.fusesource.hawtdispatch.internal.NioDispatchSource$3.run(NioDispatchSource.java:209)
at 
org.fusesource.hawtdispatch.internal.SerialDispatchQueue.run(SerialDispatchQueue.java:100)
at 
org.fusesource.hawtdispatch.internal.pool.SimpleThread.run(SimpleThread.java:77)
2013-06-19 16:50:40,563 | INFO  | MQTTTest   | Client 
Received:
MQTTFrame { type: PUBLISH, qos: AT_LEAST_ONCE, dup:false }
2013-06-19 16:50:40,564 | INFO  | BrokerService  | Apache 
ActiveMQ 5.9-SNAPSHOT (localhost, ID:OfficePC-37216-1371675037999-0:1) is 
shutting down
{noformat}


> MQTT BlockingConnection.receive fails when receiving pending messages after 
> reconnect without cleaning session
> --
>
> Key: AMQ-4585
> URL: https://issues.apache.org/jira/browse/AMQ-4585
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.8.0
>Reporter: Pedro Marques
> Attachments: MQTTTest.java
>
>
> The system throws at least three different types of exceptions when a 
> subscriber receives the first pending message without cleaning the session. 
> The test case corresponds to receiving several messages from a publisher then 
> closing the subscriber connection and finally reconnecting with 
> setCleanSession(false) and attempt to read the messages published while the 
> subscriber was disconnected.
> The exceptions thrown:
> {code}
> java.net.ProtocolException: Command from server contained an invalid message 
> id: 1
>   at 
> org.fusesource.mqtt.client.CallbackConnection.completeRequest(CallbackConnection.java:723)
>   at 
> org.fusesource.mqtt.client.CallbackConnection.processFrame(CallbackConnection.java:762)
>   at 
> org.fusesource.mqtt.client.CallbackConnection.access$1500(CallbackConnection.java:51)
>   at 
> org.fusesource.mqtt.client.CallbackConnection$6.onTransportCommand(CallbackConnection.java:392)
>   at 
> org.fusesource.hawtdispatch.transport.TcpTransport.drainInbound(TcpTransport.java:659)
>   at 
> org.fusesource.hawtdispatch.transport.SslTransport.drainInbound(SslTransport.java:264)
>   at 
> org.fusesource.hawtdispatch.transport.TcpTransport$6.run(TcpTransport.java:538)
>   at 
> org.fusesource

[jira] [Commented] (AMQCPP-494) Commiting a session with a deleted consumer causes access violation

[Timothy Bish (JIRA)]

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

Timothy Bish commented on AMQCPP-494:
-

Using the latest code from trunk or the 3.7.x fixes branch I cannot reproduce 
this.  I'd recommend you pull from: 
https://svn.apache.org/repos/asf/activemq/activemq-cpp/branches/3.7.x and see 
if your issue is resolved.  This is the branch where the v3.7.1 patch release 
will be cut in early July. 

> Commiting a session with a deleted consumer causes access violation
> ---
>
> Key: AMQCPP-494
> URL: https://issues.apache.org/jira/browse/AMQCPP-494
> Project: ActiveMQ C++ Client
>  Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Andrei Gheorghe
>Assignee: Timothy Bish
>Priority: Minor
> Attachments: test.cpp
>
>
> I'm not sure if this is a bug or if I'm using the library wrong.
> The attached test file will cause an access violation error when trying to 
> commit the session.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Jenkins build became unstable: ActiveMQ » ActiveMQ :: MQTT Protocol #1316

[Apache Jenkins Server]

See 

Jenkins build is unstable: ActiveMQ » ActiveMQ :: Web #1316

[Apache Jenkins Server]

See 

[jira] [Closed] (AMQ-4352) Expired message on the dlq miss originalExpiration property

[Timothy Bish (JIRA)]

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

Timothy Bish closed AMQ-4352.
-

Resolution: Cannot Reproduce

The test is working against trunk.  Please reopen if you find that this is not 
resolved. 

> Expired message on the dlq miss originalExpiration property
> ---
>
> Key: AMQ-4352
> URL: https://issues.apache.org/jira/browse/AMQ-4352
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: JMS client
>Affects Versions: 5.x
>Reporter: SuoNayi
> Fix For: 5.9.0
>
> Attachments: AMQ4352.patch, AMQ4352Test.java
>
>
> When messages expire they are moved to the dead letter queue for 
> retrospection.
> Expired messages have one originalExpiration property to indicate when it's 
> expired, but we can not see the property via Web Console or using consumers 
> to fetch them from the dlq.
> The unit test reproduces the problem.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (AMQ-4589) Race condition in AjaxListener causes lost messages

[Timothy Bish (JIRA)]

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

Timothy Bish resolved AMQ-4589.
---

   Resolution: Fixed
Fix Version/s: 5.9.0

Patch applied on trunk for 5.9

> Race condition in AjaxListener causes lost messages
> ---
>
> Key: AMQ-4589
> URL: https://issues.apache.org/jira/browse/AMQ-4589
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.8.0
> Environment: Jetty 9.0.3, Java 7, Windows
>Reporter: Thomas Themel
> Fix For: 5.9.0
>
> Attachments: AjaxListener-race.diff
>
>
> Running activemq-web under a container that supports Servlet 3, there is a 
> race condition when resuming continuations that leads to lost messages 
> because the same continuation is resumed multiple times and the second time 
> around the undelivered_message attribute is overwritten. 
> Here's an example debug log of the issue under Jetty:
> {noformat}
> 2013-06-19 10:46:51,340 DEBUG o.a.a.web.MessageListenerServlet   - doMessage 
> timeout=25000
> 2013-06-19 10:46:51,350 DEBUG o.a.a.web.MessageListenerServlet   - received 
> null from ActiveMQMessageConsumer { 
> value=ID:deapp0313-52345-1371228095770-3:126:1:1, started=true }
> 2013-06-19 10:46:51,350 DEBUG o.a.a.web.MessageListenerServlet   - Suspending 
> continuation org.eclipse.jetty.continuation.Servlet3Continuation@73d4a75a
> 2013-06-19 10:46:53,053 DEBUG org.apache.activemq.web.AjaxListener   - 
> message is ActiveMQTextMessage {commandId = 4419, responseRequired = true, 
> messageId = ID:deapp0313-52345-1371228095770-1:1:1:1:4415, 
> originalDestination = null, originalTransactionId = null, producerId = 
> ID:deapp0313-52345-1371228095770-1:1:1:1, destination = topic://W2ETopic, 
> transactionId = null, expiration = 0, timestamp = 1371631612606, arrival = 0, 
> brokerInTime = 1371631612628, brokerOutTime = 1371631612629, correlationId = 
> null, replyTo = null, persistent = true, type = null, priority = 4, groupID = 
> null, groupSequence = 0, targetConsumerId = null, compressed = false, userID 
> = null, content = null, marshalledProperties = 
> org.apache.activemq.util.ByteSequence@1e5bc429, dataStructure = null, 
> redeliveryCounter = 0, size = 0, properties = {instance=1796}, 
> readOnlyProperties = true, readOnlyBody = true, droppable = false, text = 
> {"instance":{"instanceId":1796,"changeNo":217...nput":true}}}
> 2013-06-19 10:46:53,062 DEBUG org.apache.activemq.web.AjaxListener   - 
> Resuming suspended continuation 
> org.eclipse.jetty.continuation.Servlet3Continuation@73d4a75a
> 2013-06-19 10:46:53,063 DEBUG org.apache.activemq.web.AjaxListener   - 
> message for ActiveMQMessageConsumer { 
> value=ID:deapp0313-52345-1371228095770-3:126:1:1, started=true } 
> continuation=org.eclipse.jetty.continuation.Servlet3Continuation@73d4a75a
> 2013-06-19 10:46:53,064 DEBUG org.apache.activemq.web.AjaxListener   - 
> message is ActiveMQTextMessage {commandId = 4420, responseRequired = true, 
> messageId = ID:deapp0313-52345-1371228095770-1:1:1:1:4416, 
> originalDestination = null, originalTransactionId = null, producerId = 
> ID:deapp0313-52345-1371228095770-1:1:1:1, destination = topic://W2ETopic, 
> transactionId = null, expiration = 0, timestamp = 1371631612644, arrival = 0, 
> brokerInTime = 1371631612644, brokerOutTime = 1371631613022, correlationId = 
> null, replyTo = null, persistent = true, type = null, priority = 4, groupID = 
> null, groupSequence = 0, targetConsumerId = null, compressed = false, userID 
> = null, content = null, marshalledProperties = 
> org.apache.activemq.util.ByteSequence@1aab6f51, dataStructure = null, 
> redeliveryCounter = 0, size = 0, properties = {instance=1796}, 
> readOnlyProperties = true, readOnlyBody = true, droppable = false, text = 
> {"instance":{"instanceId":1796,"changeNo":217...nput":true}}}
> 2013-06-19 10:46:53,064 DEBUG org.apache.activemq.web.AjaxListener   - 
> Resuming suspended continuation 
> org.eclipse.jetty.continuation.Servlet3Continuation@73d4a75a
> 2013-06-19 10:46:53,065 DEBUG o.a.a.web.MessageListenerServlet   - GET 
> client=org.apache.activemq.web.AjaxWebClient@7c00281 
> session=c5qseeifcc9l1n49e7ivdx3at clientId=w2e-gui-0.18586184200830758 
> uri=/amq 
> query=timeout=12&d=1371631611528&r=0.4084213834721595&clientId=w2e-gui-0.18586184200830758
> 2013-06-19 10:46:53,065 DEBUG o.a.a.web.MessageListenerServlet   - doMessage 
> timeout=25000
> 2013-06-19 10:46:53,065 DEBUG o.a.a.web.MessageListenerServlet   - sending 
> pre-existing message
> 2013-06-19 10:46:53,066 DEBUG o.a.a.web.MessageListenerServlet   - Send 0 
> unconsumed messages
> 2013-06-19 10:46:53,065 ERROR org.apache.activemq.web.AjaxListener   - Error 
> receiving message java.lang.IllegalStateException: REDISPATCHED,resumed
> java.lang.IllegalStateException: REDISP

[jira] [Resolved] (AMQ-3447) When MessageListenerServlet is running under servlet3, the continuation is not timing out.

[Timothy Bish (JIRA)]

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

Timothy Bish resolved AMQ-3447.
---

   Resolution: Fixed
Fix Version/s: 5.9.0

Patch applied on trunk, for v5.9.0

> When MessageListenerServlet is running under servlet3, the continuation is 
> not timing out.
> --
>
> Key: AMQ-3447
> URL: https://issues.apache.org/jira/browse/AMQ-3447
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.5.0
> Environment: Ubuntu 11.04 using glassfish as web container running 
> servlet 3.0 webapp.
>Reporter: Rui Gu
>  Labels: Ajax
> Fix For: 5.9.0
>
>
> In MessageListenerServlet.java
>   if (message == null && 
> client.getListener().getUndeliveredMessages().size() == 0) {
> Continuation continuation = 
> ContinuationSupport.getContinuation(request);
> 
> if (continuation.isExpired()) {
> response.setStatus(HttpServletResponse.SC_OK);
> StringWriter swriter = new StringWriter();
> PrintWriter writer = new PrintWriter(swriter);
> writer.println("");
> writer.print("");
> writer.flush();
> String m = swriter.toString();
> response.getWriter().println(m); 
> 
> return;
> }
> continuation.setTimeout(timeout);
> continuation.suspend();
> LOG.debug( "Suspending continuation " + continuation );
> 
> // Fetch the listeners
> AjaxListener listener = client.getListener();
> listener.access();
> // register this continuation with our listener.
> listener.setContinuation(continuation);
> 
> return;
> }
> Based on above code, the continuation is expected to be expired after given 
> timeout when there is no message available for the ajax client and the ajax 
> client will then receive an "empty" message. However based on the servlet 3 
> Continuation implementation in jetty (Servlet3Continuation.java) the only 
> place where the continuation is set to expire is within the below method 
> (there is a bug in this method as well). 
> public void addContinuationListener(final ContinuationListener listener)
> {
> AsyncListener wrapped = new AsyncListener()
> {
> public void onComplete(final AsyncEvent event) throws IOException
> {
> listener.onComplete(Servlet3Continuation.this);
> }
> public void onError(AsyncEvent event) throws IOException
> {
> listener.onComplete(Servlet3Continuation.this);
> }
> public void onStartAsync(AsyncEvent event) throws IOException
> {
> event.getAsyncContext().addListener(this);
> }
> public void onTimeout(AsyncEvent event) throws IOException
> {
> _expired=true;
> listener.onTimeout(Servlet3Continuation.this);
> }
> };
> 
> if (_context==null)
> _context.addListener(wrapped);
> else
> _listeners.add(wrapped);
> }
> Without adding a listener the continuation will never be set to expire, 
> therefore the "empty" response is never sent back to the client, the 
> connection from the client is resumed and suspended over and over again until 
> the connection is aborted by client or there is a message available.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (AMQ-4588) org.apache.activemq.util.IdGenerator calls non-configurable new ServerSocket(0);

[Timothy Bish (JIRA)]

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

Timothy Bish commented on AMQ-4588:
---

We welcome patches so if you have some idea of what would be the best solution 
then patch away. 

> org.apache.activemq.util.IdGenerator calls non-configurable new 
> ServerSocket(0);
> 
>
> Key: AMQ-4588
> URL: https://issues.apache.org/jira/browse/AMQ-4588
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: JMS client
>Affects Versions: 5.8.0
>Reporter: Bill DeCoste
>Priority: Minor
>
> In order to have the AMQ client run on OpenShift the IdGenerator call 'new 
> ServerSocket(0);' needs to be configurable to be avoided. OpenShift only 
> allows binding to a specific, provided, unique loopback address and a limited 
> set of ports. Ideally there would be a configuration option that allows the 
> stub prefix to be set via a JVM param. The current logic doesn't break 
> OpenShift as the PermissionDenied exception is caught and swallowed but the 
> stack trace is ugly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (AMQCPP-494) Commiting a session with a deleted consumer causes access violation

[Timothy Bish (JIRA)]

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

Timothy Bish commented on AMQCPP-494:
-

Well you would hope that nothing you do would cause an access violation but 
instead throw an exception so probably a bug, will look into it. 

> Commiting a session with a deleted consumer causes access violation
> ---
>
> Key: AMQCPP-494
> URL: https://issues.apache.org/jira/browse/AMQCPP-494
> Project: ActiveMQ C++ Client
>  Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Andrei Gheorghe
>Assignee: Timothy Bish
>Priority: Minor
> Attachments: test.cpp
>
>
> I'm not sure if this is a bug or if I'm using the library wrong.
> The attached test file will cause an access violation error when trying to 
> commit the session.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (AMQCPP-494) Commiting a session with a deleted consumer causes access violation

[Andrei Gheorghe (JIRA)]

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

Andrei Gheorghe updated AMQCPP-494:
---

Description: 
I'm not sure if this is a bug or if I'm using the library wrong.
The attached test file will cause an access violation error when trying to 
commit the session.


  was:
I'm not sure if this is a bug or if I'm using the library wrong.
The following program will cause an access violation error when trying to 
commit the session.



> Commiting a session with a deleted consumer causes access violation
> ---
>
> Key: AMQCPP-494
> URL: https://issues.apache.org/jira/browse/AMQCPP-494
> Project: ActiveMQ C++ Client
>  Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Andrei Gheorghe
>Assignee: Timothy Bish
>Priority: Minor
> Attachments: test.cpp
>
>
> I'm not sure if this is a bug or if I'm using the library wrong.
> The attached test file will cause an access violation error when trying to 
> commit the session.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (AMQCPP-494) Commiting a session with a deleted consumer causes access violation

[Andrei Gheorghe (JIRA)]

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

Andrei Gheorghe updated AMQCPP-494:
---

Attachment: test.cpp

> Commiting a session with a deleted consumer causes access violation
> ---
>
> Key: AMQCPP-494
> URL: https://issues.apache.org/jira/browse/AMQCPP-494
> Project: ActiveMQ C++ Client
>  Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Andrei Gheorghe
>Assignee: Timothy Bish
>Priority: Minor
> Attachments: test.cpp
>
>
> I'm not sure if this is a bug or if I'm using the library wrong.
> The following program will cause an access violation error when trying to 
> commit the session.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (AMQCPP-494) Commiting a session with a deleted consumer causes access violation

[Andrei Gheorghe (JIRA)]

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

Andrei Gheorghe updated AMQCPP-494:
---

Description: 
I'm not sure if this is a bug or if I'm using the library wrong.
The following program will cause an access violation error when trying to 
commit the session.


  was:
I'm not sure if this is a bug or if I'm using the library wrong.
The following program will cause an access violation error when trying to 
commit the session.

#include 
#include 
#include 

int main()
{
activemq::library::ActiveMQCPP::initializeLibrary();

activemq::core::ActiveMQConnectionFactory 
factory("tcp://localhost:61616");
activemq::commands::ActiveMQQueue queue("testqueue");

cms::Connection* connection = factory.createConnection();
connection->start();
cms::Session* session = 
connection->createSession(cms::Session::SESSION_TRANSACTED);
cms::MessageConsumer* consumer = session->createConsumer(&queue);

consumer->receive();
delete consumer;
session->commit();

activemq::library::ActiveMQCPP::shutdownLibrary();
}


> Commiting a session with a deleted consumer causes access violation
> ---
>
> Key: AMQCPP-494
> URL: https://issues.apache.org/jira/browse/AMQCPP-494
> Project: ActiveMQ C++ Client
>  Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Andrei Gheorghe
>Assignee: Timothy Bish
>Priority: Minor
> Attachments: test.cpp
>
>
> I'm not sure if this is a bug or if I'm using the library wrong.
> The following program will cause an access violation error when trying to 
> commit the session.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (AMQCPP-494) Commiting a session with a deleted consumer causes access violation

[Andrei Gheorghe (JIRA)]

Andrei Gheorghe created AMQCPP-494:
--

 Summary: Commiting a session with a deleted consumer causes access 
violation
 Key: AMQCPP-494
 URL: https://issues.apache.org/jira/browse/AMQCPP-494
 Project: ActiveMQ C++ Client
  Issue Type: Bug
Affects Versions: 3.7.0
Reporter: Andrei Gheorghe
Assignee: Timothy Bish
Priority: Minor


I'm not sure if this is a bug or if I'm using the library wrong.
The following program will cause an access violation error when trying to 
commit the session.

#include 
#include 
#include 

int main()
{
activemq::library::ActiveMQCPP::initializeLibrary();

activemq::core::ActiveMQConnectionFactory 
factory("tcp://localhost:61616");
activemq::commands::ActiveMQQueue queue("testqueue");

cms::Connection* connection = factory.createConnection();
connection->start();
cms::Session* session = 
connection->createSession(cms::Session::SESSION_TRANSACTED);
cms::MessageConsumer* consumer = session->createConsumer(&queue);

consumer->receive();
delete consumer;
session->commit();

activemq::library::ActiveMQCPP::shutdownLibrary();
}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: How to disable KahaDB

[Christian Posta]

where is kahadb storing unnecessary files? can you post your config?


On Wed, Jun 19, 2013 at 5:51 AM, Dayakar  wrote:

> Hi,
> I am using jdbcPersistenceAdapter in my ActiveMQ.xml
>
> So I want to disable KahaDB . its unneceesary storing in to my file system
>
> how can i disable Kaha DB
>
> Thanks & Regards,
> Dayakar
>
>
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/How-to-disable-KahaDB-tp4668345.html
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>



-- 
*Christian Posta*
http://www.christianposta.com/blog
twitter: @christianposta

[jira] [Created] (AMQ-4590) AMQP: Only one connection from a given container is allowed

[Gordon Sim (JIRA)]

Gordon Sim created AMQ-4590:
---

 Summary: AMQP: Only one connection from a given container is 
allowed
 Key: AMQ-4590
 URL: https://issues.apache.org/jira/browse/AMQ-4590
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker
Affects Versions: 5.8.0
Reporter: Gordon Sim


This is because the container id in AMQP is mapped onto the JMS clientid. The 
limitation prevents another broker establishing more than AMQP connection to 
ActiveMQ (or else it would need to identify itself as a different container for 
each).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (AMQ-4533) Messages stuck in queue with redelivered=true

[Wieslaw Dudek (JIRA)]

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

Wieslaw Dudek commented on AMQ-4533:


Here is what I tried to put into spring2.xml & spring3.xml but we still have 
e.g. 400 messages stuck. I checked a few possible configurations for 
 and the test case is still failing.


  

   
  
 
  


  



> Messages stuck in queue with redelivered=true
> -
>
> Key: AMQ-4533
> URL: https://issues.apache.org/jira/browse/AMQ-4533
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: JMS client
>Affects Versions: 5.7.0
> Environment: Fuse Message Broker 5.7.0
>Reporter: Jason Shepherd
> Attachments: AMQ4533TestPatch.txt, AMQ4533TestPatch.txt, 
> AMQ4533TestPatch.txt, kahaPendingMessages.zip
>
>
> We're  getting message stuck in queues with the 
> redelivery flag set to true.
> We used the following test model: put every 1 second 50 messages 
> sequentially, and after that, the rest of 1000 msgs quickly to INPUT_QUEUE 
> and 
> while starting 25 listeners cosuming from INPUT_QUEUE, which takes about 30 
> seconds to move the message to RECEIPT_QUEUE, 10 other listeners on 
> RECEIPT_QUEUE consume and counts them.
> We tried making one of the consumer slow by setting the 
> processing time to 10 seconds (sleep) and putting a heavy load in 
> 500 threads every 1 ms to some other queues the same time.
> Our test case is attached, you might need to install some dependencies 
> to the local maven repository manually:
>  mvn install:install-file -DgroupId=org.apache.activemq 
> -DartifactId=activemq-core -Dversion=5.7.0-fuse-71-047 -Dpackaging=jar 
> -Dfile=activemq-core-5.7.0.fuse-71-047.jar
>  mvn install:install-file -DgroupId=org.apache.kahadb 
> -DartifactId=kahadb -Dversion=5.7.0-fuse-71-047 -Dpackaging=jar 
> -Dfile=kahadb-5.7.0.fuse-71-047.jar
>  mvn install:install-file 
> -DgroupId=org.apache.geronimo.management.specs 
> -DartifactId=geronimo-j2ee-management_1.1_spec -Dversion=1.0.1 
> -Dpackaging=jar -Dfile=geronimo-j2ee-management_1.1_spec-1.0.1.jar
>  mvn install:install-file -DgroupId=org.apache.activemq.pool 
> -DartifactId=activemq-pool -Dversion=5.7.0-fuse-71-047 -Dpackaging=jar 
> -Dfile=activemq-pool-5.7.0.fuse-71-047.jar
> To run the test, simply use the Maven test target:
> mvn clean test
> If the problem occurs the you'll get a message like this in the test 
> results, (target/surefire-reports):
> java.lang.AssertionError: Still messages in InputQueue expected:<0> 
> but was:<365>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

How to disable KahaDB

[Dayakar]

Hi,
I am using jdbcPersistenceAdapter in my ActiveMQ.xml

So I want to disable KahaDB . its unneceesary storing in to my file system

how can i disable Kaha DB

Thanks & Regards,
Dayakar





--
View this message in context: 
http://activemq.2283324.n4.nabble.com/How-to-disable-KahaDB-tp4668345.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

[jira] [Commented] (AMQ-4585) MQTT BlockingConnection.receive fails when receiving pending messages after reconnect without cleaning session

[Pedro Marques (JIRA)]

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

Pedro Marques commented on AMQ-4585:


Forget about the locking problem when setCleanSession(true)... It was just a 
distraction on my part, obviously, if I clean the session there are no messages 
pending and the receive blocks...

> MQTT BlockingConnection.receive fails when receiving pending messages after 
> reconnect without cleaning session
> --
>
> Key: AMQ-4585
> URL: https://issues.apache.org/jira/browse/AMQ-4585
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.8.0
>Reporter: Pedro Marques
> Attachments: MQTTTest.java
>
>
> The system throws at least three different types of exceptions when a 
> subscriber receives the first pending message without cleaning the session. 
> The test case corresponds to receiving several messages from a publisher then 
> closing the subscriber connection and finally reconnecting with 
> setCleanSession(false) and attempt to read the messages published while the 
> subscriber was disconnected.
> The exceptions thrown:
> {code}
> java.net.ProtocolException: Command from server contained an invalid message 
> id: 1
>   at 
> org.fusesource.mqtt.client.CallbackConnection.completeRequest(CallbackConnection.java:723)
>   at 
> org.fusesource.mqtt.client.CallbackConnection.processFrame(CallbackConnection.java:762)
>   at 
> org.fusesource.mqtt.client.CallbackConnection.access$1500(CallbackConnection.java:51)
>   at 
> org.fusesource.mqtt.client.CallbackConnection$6.onTransportCommand(CallbackConnection.java:392)
>   at 
> org.fusesource.hawtdispatch.transport.TcpTransport.drainInbound(TcpTransport.java:659)
>   at 
> org.fusesource.hawtdispatch.transport.SslTransport.drainInbound(SslTransport.java:264)
>   at 
> org.fusesource.hawtdispatch.transport.TcpTransport$6.run(TcpTransport.java:538)
>   at 
> org.fusesource.hawtdispatch.internal.NioDispatchSource$3.run(NioDispatchSource.java:209)
>   at 
> org.fusesource.hawtdispatch.internal.SerialDispatchQueue.run(SerialDispatchQueue.java:100)
>   at 
> org.fusesource.hawtdispatch.internal.pool.SimpleThread.run(SimpleThread.java:77)
> {code}
> {code}
> java.lang.ArrayIndexOutOfBoundsException: 0
>   at 
> org.fusesource.mqtt.codec.MessageSupport$AckBase.decode(MessageSupport.java:81)
>   at org.fusesource.mqtt.codec.PUBREC.decode(PUBREC.java:40)
>   at 
> org.fusesource.mqtt.client.CallbackConnection.processFrame(CallbackConnection.java:749)
>   at 
> org.fusesource.mqtt.client.CallbackConnection.access$1500(CallbackConnection.java:51)
>   at 
> org.fusesource.mqtt.client.CallbackConnection$6.onTransportCommand(CallbackConnection.java:392)
>   at 
> org.fusesource.hawtdispatch.transport.TcpTransport.drainInbound(TcpTransport.java:659)
>   at 
> org.fusesource.hawtdispatch.transport.SslTransport.drainInbound(SslTransport.java:264)
>   at 
> org.fusesource.hawtdispatch.transport.TcpTransport$6.run(TcpTransport.java:538)
>   at 
> org.fusesource.hawtdispatch.internal.NioDispatchSource$3.run(NioDispatchSource.java:209)
>   at 
> org.fusesource.hawtdispatch.internal.SerialDispatchQueue.run(SerialDispatchQueue.java:100)
>   at 
> org.fusesource.hawtdispatch.internal.pool.SimpleThread.run(SimpleThread.java:77)
> {code}
> {code}
> java.net.ProtocolException: Unexpected MQTT command type: 0
>   at 
> org.fusesource.mqtt.client.CallbackConnection.processFrame(CallbackConnection.java:775)
>   at 
> org.fusesource.mqtt.client.CallbackConnection.access$1500(CallbackConnection.java:51)
>   at 
> org.fusesource.mqtt.client.CallbackConnection$6.onTransportCommand(CallbackConnection.java:392)
>   at 
> org.fusesource.hawtdispatch.transport.TcpTransport.drainInbound(TcpTransport.java:659)
>   at 
> org.fusesource.hawtdispatch.transport.SslTransport.drainInbound(SslTransport.java:264)
>   at 
> org.fusesource.hawtdispatch.transport.TcpTransport$6.run(TcpTransport.java:538)
>   at 
> org.fusesource.hawtdispatch.internal.NioDispatchSource$3.run(NioDispatchSource.java:209)
>   at 
> org.fusesource.hawtdispatch.internal.SerialDispatchQueue.run(SerialDispatchQueue.java:100)
>   at 
> org.fusesource.hawtdispatch.internal.pool.SimpleThread.run(SimpleThread.java:77)
> {code}
> No message is shown in the server. The problem doesn't occur always but most 
> of the times the first reconnection attempt is made. With 
> setCleanSession(true) the system works fine.
> Code sample (publisher, permanently running):
> {code}
> MQTT mqtt = new MQTT();
> mqtt.setHost(url);
> mqtt.setUserName(user);
> mqtt.setPassword(password);
> mqtt.set

[jira] [Updated] (AMQ-4589) Race condition in AjaxListener causes lost messages

[Thomas Themel (JIRA)]

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

Thomas Themel updated AMQ-4589:
---

Attachment: AjaxListener-race.diff

Patch against activemq-parent 5.8.0

> Race condition in AjaxListener causes lost messages
> ---
>
> Key: AMQ-4589
> URL: https://issues.apache.org/jira/browse/AMQ-4589
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.8.0
> Environment: Jetty 9.0.3, Java 7, Windows
>Reporter: Thomas Themel
> Attachments: AjaxListener-race.diff
>
>
> Running activemq-web under a container that supports Servlet 3, there is a 
> race condition when resuming continuations that leads to lost messages 
> because the same continuation is resumed multiple times and the second time 
> around the undelivered_message attribute is overwritten. 
> Here's an example debug log of the issue under Jetty:
> {noformat}
> 2013-06-19 10:46:51,340 DEBUG o.a.a.web.MessageListenerServlet   - doMessage 
> timeout=25000
> 2013-06-19 10:46:51,350 DEBUG o.a.a.web.MessageListenerServlet   - received 
> null from ActiveMQMessageConsumer { 
> value=ID:deapp0313-52345-1371228095770-3:126:1:1, started=true }
> 2013-06-19 10:46:51,350 DEBUG o.a.a.web.MessageListenerServlet   - Suspending 
> continuation org.eclipse.jetty.continuation.Servlet3Continuation@73d4a75a
> 2013-06-19 10:46:53,053 DEBUG org.apache.activemq.web.AjaxListener   - 
> message is ActiveMQTextMessage {commandId = 4419, responseRequired = true, 
> messageId = ID:deapp0313-52345-1371228095770-1:1:1:1:4415, 
> originalDestination = null, originalTransactionId = null, producerId = 
> ID:deapp0313-52345-1371228095770-1:1:1:1, destination = topic://W2ETopic, 
> transactionId = null, expiration = 0, timestamp = 1371631612606, arrival = 0, 
> brokerInTime = 1371631612628, brokerOutTime = 1371631612629, correlationId = 
> null, replyTo = null, persistent = true, type = null, priority = 4, groupID = 
> null, groupSequence = 0, targetConsumerId = null, compressed = false, userID 
> = null, content = null, marshalledProperties = 
> org.apache.activemq.util.ByteSequence@1e5bc429, dataStructure = null, 
> redeliveryCounter = 0, size = 0, properties = {instance=1796}, 
> readOnlyProperties = true, readOnlyBody = true, droppable = false, text = 
> {"instance":{"instanceId":1796,"changeNo":217...nput":true}}}
> 2013-06-19 10:46:53,062 DEBUG org.apache.activemq.web.AjaxListener   - 
> Resuming suspended continuation 
> org.eclipse.jetty.continuation.Servlet3Continuation@73d4a75a
> 2013-06-19 10:46:53,063 DEBUG org.apache.activemq.web.AjaxListener   - 
> message for ActiveMQMessageConsumer { 
> value=ID:deapp0313-52345-1371228095770-3:126:1:1, started=true } 
> continuation=org.eclipse.jetty.continuation.Servlet3Continuation@73d4a75a
> 2013-06-19 10:46:53,064 DEBUG org.apache.activemq.web.AjaxListener   - 
> message is ActiveMQTextMessage {commandId = 4420, responseRequired = true, 
> messageId = ID:deapp0313-52345-1371228095770-1:1:1:1:4416, 
> originalDestination = null, originalTransactionId = null, producerId = 
> ID:deapp0313-52345-1371228095770-1:1:1:1, destination = topic://W2ETopic, 
> transactionId = null, expiration = 0, timestamp = 1371631612644, arrival = 0, 
> brokerInTime = 1371631612644, brokerOutTime = 1371631613022, correlationId = 
> null, replyTo = null, persistent = true, type = null, priority = 4, groupID = 
> null, groupSequence = 0, targetConsumerId = null, compressed = false, userID 
> = null, content = null, marshalledProperties = 
> org.apache.activemq.util.ByteSequence@1aab6f51, dataStructure = null, 
> redeliveryCounter = 0, size = 0, properties = {instance=1796}, 
> readOnlyProperties = true, readOnlyBody = true, droppable = false, text = 
> {"instance":{"instanceId":1796,"changeNo":217...nput":true}}}
> 2013-06-19 10:46:53,064 DEBUG org.apache.activemq.web.AjaxListener   - 
> Resuming suspended continuation 
> org.eclipse.jetty.continuation.Servlet3Continuation@73d4a75a
> 2013-06-19 10:46:53,065 DEBUG o.a.a.web.MessageListenerServlet   - GET 
> client=org.apache.activemq.web.AjaxWebClient@7c00281 
> session=c5qseeifcc9l1n49e7ivdx3at clientId=w2e-gui-0.18586184200830758 
> uri=/amq 
> query=timeout=12&d=1371631611528&r=0.4084213834721595&clientId=w2e-gui-0.18586184200830758
> 2013-06-19 10:46:53,065 DEBUG o.a.a.web.MessageListenerServlet   - doMessage 
> timeout=25000
> 2013-06-19 10:46:53,065 DEBUG o.a.a.web.MessageListenerServlet   - sending 
> pre-existing message
> 2013-06-19 10:46:53,066 DEBUG o.a.a.web.MessageListenerServlet   - Send 0 
> unconsumed messages
> 2013-06-19 10:46:53,065 ERROR org.apache.activemq.web.AjaxListener   - Error 
> receiving message java.lang.IllegalStateException: REDISPATCHED,resumed
> java.lang.IllegalStateException: REDISPATCHED,resumed
>   at 
> org.ecli

[jira] [Created] (AMQ-4589) Race condition in AjaxListener causes lost messages

[Thomas Themel (JIRA)]

Thomas Themel created AMQ-4589:
--

 Summary: Race condition in AjaxListener causes lost messages
 Key: AMQ-4589
 URL: https://issues.apache.org/jira/browse/AMQ-4589
 Project: ActiveMQ
  Issue Type: Bug
Affects Versions: 5.8.0
 Environment: Jetty 9.0.3, Java 7, Windows
Reporter: Thomas Themel


Running activemq-web under a container that supports Servlet 3, there is a race 
condition when resuming continuations that leads to lost messages because the 
same continuation is resumed multiple times and the second time around the 
undelivered_message attribute is overwritten. 

Here's an example debug log of the issue under Jetty:

{noformat}
2013-06-19 10:46:51,340 DEBUG o.a.a.web.MessageListenerServlet   - doMessage 
timeout=25000
2013-06-19 10:46:51,350 DEBUG o.a.a.web.MessageListenerServlet   - received 
null from ActiveMQMessageConsumer { 
value=ID:deapp0313-52345-1371228095770-3:126:1:1, started=true }
2013-06-19 10:46:51,350 DEBUG o.a.a.web.MessageListenerServlet   - Suspending 
continuation org.eclipse.jetty.continuation.Servlet3Continuation@73d4a75a
2013-06-19 10:46:53,053 DEBUG org.apache.activemq.web.AjaxListener   - message 
is ActiveMQTextMessage {commandId = 4419, responseRequired = true, messageId = 
ID:deapp0313-52345-1371228095770-1:1:1:1:4415, originalDestination = null, 
originalTransactionId = null, producerId = 
ID:deapp0313-52345-1371228095770-1:1:1:1, destination = topic://W2ETopic, 
transactionId = null, expiration = 0, timestamp = 1371631612606, arrival = 0, 
brokerInTime = 1371631612628, brokerOutTime = 1371631612629, correlationId = 
null, replyTo = null, persistent = true, type = null, priority = 4, groupID = 
null, groupSequence = 0, targetConsumerId = null, compressed = false, userID = 
null, content = null, marshalledProperties = 
org.apache.activemq.util.ByteSequence@1e5bc429, dataStructure = null, 
redeliveryCounter = 0, size = 0, properties = {instance=1796}, 
readOnlyProperties = true, readOnlyBody = true, droppable = false, text = 
{"instance":{"instanceId":1796,"changeNo":217...nput":true}}}
2013-06-19 10:46:53,062 DEBUG org.apache.activemq.web.AjaxListener   - Resuming 
suspended continuation 
org.eclipse.jetty.continuation.Servlet3Continuation@73d4a75a
2013-06-19 10:46:53,063 DEBUG org.apache.activemq.web.AjaxListener   - message 
for ActiveMQMessageConsumer { value=ID:deapp0313-52345-1371228095770-3:126:1:1, 
started=true } 
continuation=org.eclipse.jetty.continuation.Servlet3Continuation@73d4a75a
2013-06-19 10:46:53,064 DEBUG org.apache.activemq.web.AjaxListener   - message 
is ActiveMQTextMessage {commandId = 4420, responseRequired = true, messageId = 
ID:deapp0313-52345-1371228095770-1:1:1:1:4416, originalDestination = null, 
originalTransactionId = null, producerId = 
ID:deapp0313-52345-1371228095770-1:1:1:1, destination = topic://W2ETopic, 
transactionId = null, expiration = 0, timestamp = 1371631612644, arrival = 0, 
brokerInTime = 1371631612644, brokerOutTime = 1371631613022, correlationId = 
null, replyTo = null, persistent = true, type = null, priority = 4, groupID = 
null, groupSequence = 0, targetConsumerId = null, compressed = false, userID = 
null, content = null, marshalledProperties = 
org.apache.activemq.util.ByteSequence@1aab6f51, dataStructure = null, 
redeliveryCounter = 0, size = 0, properties = {instance=1796}, 
readOnlyProperties = true, readOnlyBody = true, droppable = false, text = 
{"instance":{"instanceId":1796,"changeNo":217...nput":true}}}
2013-06-19 10:46:53,064 DEBUG org.apache.activemq.web.AjaxListener   - Resuming 
suspended continuation 
org.eclipse.jetty.continuation.Servlet3Continuation@73d4a75a
2013-06-19 10:46:53,065 DEBUG o.a.a.web.MessageListenerServlet   - GET 
client=org.apache.activemq.web.AjaxWebClient@7c00281 
session=c5qseeifcc9l1n49e7ivdx3at clientId=w2e-gui-0.18586184200830758 uri=/amq 
query=timeout=12&d=1371631611528&r=0.4084213834721595&clientId=w2e-gui-0.18586184200830758
2013-06-19 10:46:53,065 DEBUG o.a.a.web.MessageListenerServlet   - doMessage 
timeout=25000
2013-06-19 10:46:53,065 DEBUG o.a.a.web.MessageListenerServlet   - sending 
pre-existing message
2013-06-19 10:46:53,066 DEBUG o.a.a.web.MessageListenerServlet   - Send 0 
unconsumed messages
2013-06-19 10:46:53,065 ERROR org.apache.activemq.web.AjaxListener   - Error 
receiving message java.lang.IllegalStateException: REDISPATCHED,resumed
java.lang.IllegalStateException: REDISPATCHED,resumed
at 
org.eclipse.jetty.server.HttpChannelState.dispatch(HttpChannelState.java:335) 
~[jetty-server-9.0.3.v20130506.jar:9.0.3.v20130506]
at 
org.eclipse.jetty.server.AsyncContextState.dispatch(AsyncContextState.java:109) 
~[jetty-server-9.0.3.v20130506.jar:9.0.3.v20130506]
at 
org.eclipse.jetty.continuation.Servlet3Continuation.resume(Servlet3Continuation.java:186)
 ~[jetty-continuation-9.0.3.v20130506.jar:9.0.3.v20130506]
a

[jira] [Commented] (AMQ-3447) When MessageListenerServlet is running under servlet3, the continuation is not timing out.

[Thomas Themel (JIRA)]

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

Thomas Themel commented on AMQ-3447:


Acknowledged as a Jetty bug, fixed in HEAD: 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=410911

> When MessageListenerServlet is running under servlet3, the continuation is 
> not timing out.
> --
>
> Key: AMQ-3447
> URL: https://issues.apache.org/jira/browse/AMQ-3447
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.5.0
> Environment: Ubuntu 11.04 using glassfish as web container running 
> servlet 3.0 webapp.
>Reporter: Rui Gu
>  Labels: Ajax
>
> In MessageListenerServlet.java
>   if (message == null && 
> client.getListener().getUndeliveredMessages().size() == 0) {
> Continuation continuation = 
> ContinuationSupport.getContinuation(request);
> 
> if (continuation.isExpired()) {
> response.setStatus(HttpServletResponse.SC_OK);
> StringWriter swriter = new StringWriter();
> PrintWriter writer = new PrintWriter(swriter);
> writer.println("");
> writer.print("");
> writer.flush();
> String m = swriter.toString();
> response.getWriter().println(m); 
> 
> return;
> }
> continuation.setTimeout(timeout);
> continuation.suspend();
> LOG.debug( "Suspending continuation " + continuation );
> 
> // Fetch the listeners
> AjaxListener listener = client.getListener();
> listener.access();
> // register this continuation with our listener.
> listener.setContinuation(continuation);
> 
> return;
> }
> Based on above code, the continuation is expected to be expired after given 
> timeout when there is no message available for the ajax client and the ajax 
> client will then receive an "empty" message. However based on the servlet 3 
> Continuation implementation in jetty (Servlet3Continuation.java) the only 
> place where the continuation is set to expire is within the below method 
> (there is a bug in this method as well). 
> public void addContinuationListener(final ContinuationListener listener)
> {
> AsyncListener wrapped = new AsyncListener()
> {
> public void onComplete(final AsyncEvent event) throws IOException
> {
> listener.onComplete(Servlet3Continuation.this);
> }
> public void onError(AsyncEvent event) throws IOException
> {
> listener.onComplete(Servlet3Continuation.this);
> }
> public void onStartAsync(AsyncEvent event) throws IOException
> {
> event.getAsyncContext().addListener(this);
> }
> public void onTimeout(AsyncEvent event) throws IOException
> {
> _expired=true;
> listener.onTimeout(Servlet3Continuation.this);
> }
> };
> 
> if (_context==null)
> _context.addListener(wrapped);
> else
> _listeners.add(wrapped);
> }
> Without adding a listener the continuation will never be set to expire, 
> therefore the "empty" response is never sent back to the client, the 
> connection from the client is resumed and suspended over and over again until 
> the connection is aborted by client or there is a message available.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira