[jira] [Created] (AMQ-4290) if subscriber is stopped publisher also stopped in my app with activemq

[Tamilmaran (JIRA)]

Tamilmaran created AMQ-4290:
---

 Summary: if subscriber is stopped publisher also stopped in my app 
with activemq
 Key: AMQ-4290
 URL: https://issues.apache.org/jira/browse/AMQ-4290
 Project: ActiveMQ
  Issue Type: Bug
 Environment: c# code with Apache.NMS and Apache.NMS.ActiveMQ dll
ActiveMQ version is 5.6
Reporter: Tamilmaran


I studied that in ActiveMQ publisher publishes messages even if there is no 
subscriber to consume it. But in my application it is not. My server app has a 
durable subscriber, client app publishes msg to server. If i stopped the 
server, the client is not publishing any message. When i checked the log it's 
showing that connection is already closed. What could be the reason for it or 
any activemq configuration change?

I have used c# code with Apache.NMS and Apache.NMS.ActiveMQ dll
ActiveMQ version is 5.6

--
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-4287) REOPEN - javax.jms.JMSException: The resource is allready being used in transaction context.

[Marcin Cinik (JIRA)]

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

Marcin Cinik commented on AMQ-4287:
---

I will try to provide results of such a test.

> REOPEN - javax.jms.JMSException: The resource is allready being used in 
> transaction context. 
> -
>
> Key: AMQ-4287
> URL: https://issues.apache.org/jira/browse/AMQ-4287
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Connector
>Affects Versions: 5.5.0, 5.5.1, 5.7.0
> Environment: SLES11sp1 64bits, Glassfish 2.1.1, Glassfish 3.1.1 
> activemq-5.5.0, jdk6
> Linux (unknow), Glassfish 3.1, activemq-5.5.1, 
> activemq-rar-5.7.0.rar
>Reporter: Marcin Cinik
>Priority: Critical
>
> I had to reopen the previous issue as the problem is still existing.
> I am using activemq-5.5 with activemq-rar-5.7.0.rar and I am getting
> {quote}
> Caused by: javax.jms.JMSException: The resource is already being used in 
> transaction context.
> at 
> org.apache.activemq.ra.ManagedTransactionContext.setUseSharedTxContext(ManagedTransactionContext.java:47)
> at 
> org.apache.activemq.ra.ManagedSessionProxy.setUseSharedTxContext(ManagedSessionProxy.java:67)
> at 
> org.apache.activemq.ra.ManagedConnectionProxy.createSessionProxy(ManagedConnectionProxy.java:122)
> at 
> org.apache.activemq.ra.ManagedConnectionProxy.createSession(ManagedConnectionProxy.java:105)
> {quote}
> under high load. This is certainly critical issue as it prevents from using 
> rar adapter for any serious applications.

--
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: svn commit: r1441100 - /activemq/trunk/pom.xml

[Claus Ibsen]

Hi

Just a heads up that we had some issue with hamcrest 1.1 - 1.3 at Camel.
There were some 3rd party libraries that required 1.1 and would fail
with some weird issues with 1.3.
Just in case you see something weird at AMQ now.

So we spotted 1 or 2 and downgraded them specially to use hamcrest 1.1
for their module for testing.


On Thu, Jan 31, 2013 at 7:22 PM,   wrote:
> Author: tabish
> Date: Thu Jan 31 18:22:54 2013
> New Revision: 1441100
>
> URL: http://svn.apache.org/viewvc?rev=1441100&view=rev
> Log:
> bump versions of plugin and dependencies to latest patch releases prior to 
> v5.8 release.
>
> Modified:
> activemq/trunk/pom.xml
>
> Modified: activemq/trunk/pom.xml
> URL: 
> http://svn.apache.org/viewvc/activemq/trunk/pom.xml?rev=1441100&r1=1441099&r2=1441100&view=diff
> ==
> --- activemq/trunk/pom.xml (original)
> +++ activemq/trunk/pom.xml Thu Jan 31 18:22:54 2013
> @@ -51,7 +51,7 @@
>  2.0
>  1.8.3
>  3.2.1
> -1.0.10
> +1.0.12
>  1.4
>  1.4
>  2.6
> @@ -68,8 +68,8 @@
>  1.12
>  0.1.8
>  1.8.0.12
> -4.2.2
> -4.2.2
> +4.2.3
> +4.2.3
>  1.9.2
>  1.9.0
>  1.0
> @@ -80,8 +80,8 @@
>  1.3.3
>  2.5.1
>  1.5_5
> -4.10
> -1.1
> +4.11
> +1.3
>  2.0
>  2.3.0
>  0.5
> @@ -137,15 +137,15 @@
>  2.3.7
>  2.13
>  1.3
> -2.3
> -2.2.1
> +2.4
> +2.4
>  2.9
> -2.2
> +2.3
>  2.5.1
>  2.4
>  2.5
>  2.2
> -2.8.1
> +2.9
>  2.4
>  2.0
>  0.7.2
>
>



-- 
Claus Ibsen
-
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cib...@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen

Build failed in Jenkins: ActiveMQ-Java7 #125

[Apache Jenkins Server]

See 

Changes:

[ceposta] Fix for https://issues.apache.org/jira/browse/AMQ-4289 
activemq-perf-maven-plugin is unusable because of bug in ReflectionUtil helper 
class

previous commit actually had fix commented out. this has the fix.

[ceposta] Fix for https://issues.apache.org/jira/browse/AMQ-4289 
activemq-perf-maven-plugin is unusable because of bug in ReflectionUtil helper 
class
also added test to show error

[tabish] Add a fix for: https://issues.apache.org/jira/browse/AMQ-4147

[tabish] Apply fix and test for: https://issues.apache.org/jira/browse/AMQ-4116

[gtully] add some commamd assertions to broker feature test

[tabish] apply fix for: https://issues.apache.org/jira/browse/AMQ-4288

[tabish] bump versions of plugin and dependencies to latest patch releases 
prior to v5.8 release.

[tabish] apply fix for: https://issues.apache.org/jira/browse/AMQ-4288

[tabish] apply fix for: https://issues.apache.org/jira/browse/AMQ-4288

[dejanb] https://issues.apache.org/jira/browse/AMQ-4034 - osgi web console, 
laying down foundations for config admin configuration

[dejanb] https://issues.apache.org/jira/browse/AMQ-4034 - osgi web console, 
fixing classpath

[gtully] https://issues.apache.org/jira/browse/AMQ-4285 - tidied up test to be 
tolerant of pitfalls of request/reply with temps over a network

--
[...truncated 8482 lines...]
[INFO] --- maven-source-plugin:2.1.2:jar (default-cli) @ activemq-maven-plugin 
---
[INFO] META-INF already added, skipping
[INFO] META-INF/DEPENDENCIES already added, skipping
[INFO] META-INF/NOTICE already added, skipping
[INFO] META-INF/LICENSE already added, skipping
[INFO] Building jar: 

[INFO] META-INF already added, skipping
[INFO] META-INF/DEPENDENCIES already added, skipping
[INFO] META-INF/NOTICE already added, skipping
[INFO] META-INF/LICENSE already added, skipping
mojoSucceeded org.apache.maven.plugins:maven-source-plugin:2.1.2(default-cli)
projectSucceeded org.apache.activemq.tooling:activemq-maven-plugin:5.8-SNAPSHOT
projectSkipped org.apache.activemq:activemq-web:5.8-SNAPSHOT
[INFO] 
[INFO] 
[INFO] Skipping ActiveMQ :: Web
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
projectSkipped org.apache.activemq:activemq-web-demo:5.8-SNAPSHOT
[INFO] 
[INFO] 
[INFO] Skipping ActiveMQ :: Web Demo
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
projectSkipped org.apache.activemq:activemq-web-console:5.8-SNAPSHOT
[INFO] 
[INFO] 
[INFO] Skipping ActiveMQ :: Web Console
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
projectSkipped org.apache.activemq:activemq-itests-spring31:5.8-SNAPSHOT
[INFO] 
[INFO] 
[INFO] Skipping ActiveMQ :: Integration Test :: Spring 3.1
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
projectSkipped org.apache.activemq:apache-activemq:5.8-SNAPSHOT
[INFO] 
[INFO] 
[INFO] Skipping ActiveMQ :: Assembly
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
sessionEnded
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] ActiveMQ .. SUCCESS [5.453s]
[INFO] ActiveMQ :: Openwire Generator  SUCCESS [4.011s]
[INFO] ActiveMQ :: Client  SUCCESS [18.281s]
[INFO] ActiveMQ :: Openwire Legacy Support ... SUCCESS [2.438s]
[INFO] ActiveMQ :: JAAS .. SUCCESS [26.589s]
[INFO] ActiveMQ :: Broker  SUCCESS [56.682s]
[INFO] ActiveMQ :: KahaDB Store .

Jenkins build is back to stable : ActiveMQ-Java7 » ActiveMQ :: RA #125

[Apache Jenkins Server]

See 

Jenkins build is still unstable: ActiveMQ-Java7 » ActiveMQ :: STOMP Protocol #125

[Apache Jenkins Server]

See 

Build failed in Jenkins: ActiveMQ-Java7 » ActiveMQ :: MQTT Protocol #125

[Apache Jenkins Server]

See 


--
projectStarted org.apache.activemq:activemq-mqtt:5.8-SNAPSHOT
[INFO] 
[INFO] 
[INFO] Building ActiveMQ :: MQTT Protocol 5.8-SNAPSHOT
[INFO] 
Downloading: 
http://repo.maven.apache.org/maven2/org/eclipse/jetty/maven-jetty-plugin/7.6.7.v20120910/maven-jetty-plugin-7.6.7.v20120910.pom
[WARNING] The POM for org.eclipse.jetty:maven-jetty-plugin:jar:7.6.7.v20120910 
is missing, no dependency information available
[WARNING] Failed to retrieve plugin descriptor for 
org.eclipse.jetty:maven-jetty-plugin:7.6.7.v20120910: Plugin 
org.eclipse.jetty:maven-jetty-plugin:7.6.7.v20120910 or one of its dependencies 
could not be resolved: Failed to read artifact descriptor for 
org.eclipse.jetty:maven-jetty-plugin:jar:7.6.7.v20120910
mojoStarted org.apache.maven.plugins:maven-clean-plugin:2.5(default-clean)
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ activemq-mqtt ---
mojoSucceeded org.apache.maven.plugins:maven-clean-plugin:2.5(default-clean)
mojoStarted org.apache.maven.plugins:maven-enforcer-plugin:1.0.1(default)
[INFO] 
[INFO] --- maven-enforcer-plugin:1.0.1:enforce (default) @ activemq-mqtt ---
mojoSucceeded org.apache.maven.plugins:maven-enforcer-plugin:1.0.1(default)
mojoStarted org.apache.felix:maven-bundle-plugin:2.3.7(cleanVersions)
[INFO] 
[INFO] --- maven-bundle-plugin:2.3.7:cleanVersions (cleanVersions) @ 
activemq-mqtt ---
mojoSucceeded org.apache.felix:maven-bundle-plugin:2.3.7(cleanVersions)
mojoStarted 
org.apache.activemq.protobuf:activemq-protobuf:1.1(default)[WARNING] No proto 
files found in directory: 


[INFO] 
[INFO] --- activemq-protobuf:1.1:compile (default) @ activemq-mqtt ---
mojoSucceeded org.apache.activemq.protobuf:activemq-protobuf:1.1(default)
mojoStarted org.apache.maven.plugins:maven-remote-resources-plugin:1.3(default)
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ activemq-mqtt 
---
mojoSucceeded 
org.apache.maven.plugins:maven-remote-resources-plugin:1.3(default)
mojoStarted 
org.apache.maven.plugins:maven-resources-plugin:2.5(default-resources)[debug] 
execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.

[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
activemq-mqtt ---
[INFO] Copying 5 resources
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
mojoSucceeded 
org.apache.maven.plugins:maven-resources-plugin:2.5(default-resources)
mojoStarted 
org.apache.maven.plugins:maven-compiler-plugin:2.5.1(default-compile)
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ 
activemq-mqtt ---
[INFO] Compiling 16 source files to 

mojoSucceeded 
org.apache.maven.plugins:maven-compiler-plugin:2.5.1(default-compile)
mojoStarted 
org.apache.maven.plugins:maven-resources-plugin:2.5(default-testResources)[debug]
 execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
activemq-mqtt ---
[INFO] Copying 3 resources
mojoSucceeded 
org.apache.maven.plugins:maven-resources-plugin:2.5(default-testResources)
mojoStarted 
org.apache.maven.plugins:maven-compiler-plugin:2.5.1(default-testCompile)
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ 
activemq-mqtt ---
[INFO] Compiling 6 source files to 

mojoSucceeded 
org.apache.maven.plugins:maven-compiler-plugin:2.5.1(default-testCompile)
mojoStarted org.apache.maven.plugins:maven-surefire-plugin:2.13(default-test)
[INFO] 
[INFO] --- maven-surefire-plugin:2.13:test (default-test) @ activemq-mqtt 
---[INFO] Surefire report directory: 



---
 T E S T S
---

---
 T E S T S
---
Running org.apache.activemq.transport.mqtt.MQTTSSLTest
Running org.apache.activemq.transport.mqtt.MQTTTest
Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 380.98 sec
Running org.apache.activemq.transport.m

Build failed in Jenkins: ActiveMQ #1210

[Apache Jenkins Server]

See 

Changes:

[ceposta] Fix for https://issues.apache.org/jira/browse/AMQ-4289 
activemq-perf-maven-plugin is unusable because of bug in ReflectionUtil helper 
class

previous commit actually had fix commented out. this has the fix.

[ceposta] Fix for https://issues.apache.org/jira/browse/AMQ-4289 
activemq-perf-maven-plugin is unusable because of bug in ReflectionUtil helper 
class
also added test to show error

[tabish] Add a fix for: https://issues.apache.org/jira/browse/AMQ-4147

[tabish] Apply fix and test for: https://issues.apache.org/jira/browse/AMQ-4116

[gtully] add some commamd assertions to broker feature test

[tabish] apply fix for: https://issues.apache.org/jira/browse/AMQ-4288

[tabish] bump versions of plugin and dependencies to latest patch releases 
prior to v5.8 release.

[tabish] apply fix for: https://issues.apache.org/jira/browse/AMQ-4288

[tabish] apply fix for: https://issues.apache.org/jira/browse/AMQ-4288

[dejanb] https://issues.apache.org/jira/browse/AMQ-4034 - osgi web console, 
laying down foundations for config admin configuration

[dejanb] https://issues.apache.org/jira/browse/AMQ-4034 - osgi web console, 
fixing classpath

[gtully] https://issues.apache.org/jira/browse/AMQ-4285 - tidied up test to be 
tolerant of pitfalls of request/reply with temps over a network

--
[...truncated 8309 lines...]
WARNING: Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo
forkedProjectSucceeded 
org.apache.activemq.tooling:activemq-maven-plugin:5.8-SNAPSHOT
mojoStarted org.apache.maven.plugins:maven-source-plugin:2.1.2(default-cli)
[INFO] 
[INFO] --- maven-source-plugin:2.1.2:jar (default-cli) @ activemq-maven-plugin 
---
[INFO] META-INF already added, skipping
[INFO] META-INF/DEPENDENCIES already added, skipping
[INFO] META-INF/NOTICE already added, skipping
[INFO] META-INF/LICENSE already added, skipping
[INFO] Building jar: 

[INFO] META-INF already added, skipping
[INFO] META-INF/DEPENDENCIES already added, skipping
[INFO] META-INF/NOTICE already added, skipping
[INFO] META-INF/LICENSE already added, skipping
mojoSucceeded org.apache.maven.plugins:maven-source-plugin:2.1.2(default-cli)
projectSucceeded org.apache.activemq.tooling:activemq-maven-plugin:5.8-SNAPSHOT
projectSkipped org.apache.activemq:activemq-web:5.8-SNAPSHOT
[INFO] 
[INFO] 
[INFO] Skipping ActiveMQ :: Web
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
projectSkipped org.apache.activemq:activemq-web-demo:5.8-SNAPSHOT
[INFO] 
[INFO] 
[INFO] Skipping ActiveMQ :: Web Demo
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
projectSkipped org.apache.activemq:activemq-web-console:5.8-SNAPSHOT
[INFO] 
[INFO] 
[INFO] Skipping ActiveMQ :: Web Console
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
projectSkipped org.apache.activemq:activemq-itests-spring31:5.8-SNAPSHOT
[INFO] 
[INFO] 
[INFO] Skipping ActiveMQ :: Integration Test :: Spring 3.1
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
projectSkipped org.apache.activemq:apache-activemq:5.8-SNAPSHOT
[INFO] 
[INFO] 
[INFO] Skipping ActiveMQ :: Assembly
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
sessionEnded
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] ActiveMQ .. SUCCESS [5.562s]
[INFO] ActiveMQ :: Openwire Generator  SUCCESS [5.044s]
[INFO] ActiveMQ :: Client  SUCCESS [23.588s]
[INFO] ActiveMQ :: Openwire Legacy Support ...

Build failed in Jenkins: ActiveMQ » ActiveMQ :: MQTT Protocol #1210

[Apache Jenkins Server]

See 


--
projectStarted org.apache.activemq:activemq-mqtt:5.8-SNAPSHOT
[INFO] 
[INFO] 
[INFO] Building ActiveMQ :: MQTT Protocol 5.8-SNAPSHOT
[INFO] 
Downloading: 
http://repo.maven.apache.org/maven2/org/eclipse/jetty/maven-jetty-plugin/7.6.7.v20120910/maven-jetty-plugin-7.6.7.v20120910.pom
[WARNING] The POM for org.eclipse.jetty:maven-jetty-plugin:jar:7.6.7.v20120910 
is missing, no dependency information available
[WARNING] Failed to retrieve plugin descriptor for 
org.eclipse.jetty:maven-jetty-plugin:7.6.7.v20120910: Plugin 
org.eclipse.jetty:maven-jetty-plugin:7.6.7.v20120910 or one of its dependencies 
could not be resolved: Failed to read artifact descriptor for 
org.eclipse.jetty:maven-jetty-plugin:jar:7.6.7.v20120910
mojoStarted org.apache.maven.plugins:maven-clean-plugin:2.5(default-clean)
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ activemq-mqtt ---
mojoSucceeded org.apache.maven.plugins:maven-clean-plugin:2.5(default-clean)
mojoStarted org.apache.maven.plugins:maven-enforcer-plugin:1.0.1(default)
[INFO] 
[INFO] --- maven-enforcer-plugin:1.0.1:enforce (default) @ activemq-mqtt ---
mojoSucceeded org.apache.maven.plugins:maven-enforcer-plugin:1.0.1(default)
mojoStarted org.apache.felix:maven-bundle-plugin:2.3.7(cleanVersions)
[INFO] 
[INFO] --- maven-bundle-plugin:2.3.7:cleanVersions (cleanVersions) @ 
activemq-mqtt ---
mojoSucceeded org.apache.felix:maven-bundle-plugin:2.3.7(cleanVersions)
mojoStarted org.apache.activemq.protobuf:activemq-protobuf:1.1(default)
[INFO] 
[INFO] --- activemq-protobuf:1.1:compile (default) @ activemq-mqtt ---
[WARNING] No proto files found in directory: 

mojoSucceeded org.apache.activemq.protobuf:activemq-protobuf:1.1(default)
mojoStarted org.apache.maven.plugins:maven-remote-resources-plugin:1.3(default)
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ activemq-mqtt 
---
mojoSucceeded 
org.apache.maven.plugins:maven-remote-resources-plugin:1.3(default)
mojoStarted 
org.apache.maven.plugins:maven-resources-plugin:2.5(default-resources)[debug] 
execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.

[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
activemq-mqtt ---
[INFO] Copying 5 resources
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
mojoSucceeded 
org.apache.maven.plugins:maven-resources-plugin:2.5(default-resources)
mojoStarted 
org.apache.maven.plugins:maven-compiler-plugin:2.5.1(default-compile)
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ 
activemq-mqtt ---
[INFO] Compiling 16 source files to 

mojoSucceeded 
org.apache.maven.plugins:maven-compiler-plugin:2.5.1(default-compile)
mojoStarted 
org.apache.maven.plugins:maven-resources-plugin:2.5(default-testResources)[debug]
 execute contextualize

[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
activemq-mqtt ---
[INFO] Copying 3 resources
[INFO] Copying 3 resources
mojoSucceeded 
org.apache.maven.plugins:maven-resources-plugin:2.5(default-testResources)
mojoStarted 
org.apache.maven.plugins:maven-compiler-plugin:2.5.1(default-testCompile)
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ 
activemq-mqtt ---
[INFO] Compiling 6 source files to 

mojoSucceeded 
org.apache.maven.plugins:maven-compiler-plugin:2.5.1(default-testCompile)
mojoStarted org.apache.maven.plugins:maven-surefire-plugin:2.13(default-test)
[INFO] 
[INFO] [INFO] Surefire report directory: 


---
 T E S T S
---
--- maven-surefire-plugin:2.13:test (default-test) @ activemq-mqtt ---

---
 T E S T S
---
Running org.apache.activemq.transport.mqtt.MQTTSSLTest
Running org.apache.activemq.transport.mqtt.MQTTTest
Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 380.924 sec
Running org.apache.activemq.transport.mqtt.MTQQNioTest
Tests run: 14, Failur

[jira] [Resolved] (AMQ-4289) activemq-perf-maven-plugin is unusable because of bug in ReflectionUtil helper class

[Christian Posta (JIRA)]

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

Christian Posta resolved AMQ-4289.
--

Resolution: Fixed

Yep! Nice catch!

Fix with r1441277

> activemq-perf-maven-plugin is unusable because of bug in ReflectionUtil 
> helper class
> 
>
> Key: AMQ-4289
> URL: https://issues.apache.org/jira/browse/AMQ-4289
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Performance Test
>Affects Versions: 5.8.0
>Reporter: Christian Posta
>Assignee: Christian Posta
>  Labels: maven-activemq-perf-plugin
>
> End up getting stack overflow for recursive call in 
> ReflectionUtil.retrieveClassProperties()... if there is a getter that returns 
> itself, it will not check that the "targetObject" which it's inspecting is 
> the same as what an identity getter would return. For example, 
> RedeliveryPolicy has a method:
> getValue() {
> return this;
> }
> which causes this stack trace:
> java.lang.StackOverflowError
>   at java.io.FileOutputStream.writeBytes(Native Method)
>   at java.io.FileOutputStream.write(FileOutputStream.java:282)
>   at 
> java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
>   at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
>   at java.io.PrintStream.flush(PrintStream.java:288)
>   at 
> com.intellij.rt.execution.junit.segments.SegmentedOutputStream.flush(SegmentedOutputStream.java:48)
>   at 
> com.intellij.rt.execution.junit.segments.SegmentedOutputStream.write(SegmentedOutputStream.java:44)
>   at java.io.OutputStream.write(OutputStream.java:99)
>   at java.io.PrintStream.write(PrintStream.java:430)
>   at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:202)
>   at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:272)
>   at sun.nio.cs.StreamEncoder.flushBuffer(StreamEncoder.java:85)
>   at java.io.OutputStreamWriter.flushBuffer(OutputStreamWriter.java:168)
>   at java.io.PrintStream.write(PrintStream.java:477)
>   at java.io.PrintStream.print(PrintStream.java:619)
>   at java.io.PrintStream.println(PrintStream.java:773)
>   at java.lang.Throwable.printStackTrace(Throwable.java:461)
>   at java.lang.Throwable.printStackTrace(Throwable.java:451)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:229)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieve

[jira] [Reopened] (AMQ-4289) activemq-perf-maven-plugin is unusable because of bug in ReflectionUtil helper class

[Timothy Bish (JIRA)]

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

Timothy Bish reopened AMQ-4289:
---


Double check your commit, looks like you might have commented out the fix ;)

> activemq-perf-maven-plugin is unusable because of bug in ReflectionUtil 
> helper class
> 
>
> Key: AMQ-4289
> URL: https://issues.apache.org/jira/browse/AMQ-4289
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Performance Test
>Affects Versions: 5.8.0
>Reporter: Christian Posta
>Assignee: Christian Posta
>  Labels: maven-activemq-perf-plugin
>
> End up getting stack overflow for recursive call in 
> ReflectionUtil.retrieveClassProperties()... if there is a getter that returns 
> itself, it will not check that the "targetObject" which it's inspecting is 
> the same as what an identity getter would return. For example, 
> RedeliveryPolicy has a method:
> getValue() {
> return this;
> }
> which causes this stack trace:
> java.lang.StackOverflowError
>   at java.io.FileOutputStream.writeBytes(Native Method)
>   at java.io.FileOutputStream.write(FileOutputStream.java:282)
>   at 
> java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
>   at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
>   at java.io.PrintStream.flush(PrintStream.java:288)
>   at 
> com.intellij.rt.execution.junit.segments.SegmentedOutputStream.flush(SegmentedOutputStream.java:48)
>   at 
> com.intellij.rt.execution.junit.segments.SegmentedOutputStream.write(SegmentedOutputStream.java:44)
>   at java.io.OutputStream.write(OutputStream.java:99)
>   at java.io.PrintStream.write(PrintStream.java:430)
>   at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:202)
>   at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:272)
>   at sun.nio.cs.StreamEncoder.flushBuffer(StreamEncoder.java:85)
>   at java.io.OutputStreamWriter.flushBuffer(OutputStreamWriter.java:168)
>   at java.io.PrintStream.write(PrintStream.java:477)
>   at java.io.PrintStream.print(PrintStream.java:619)
>   at java.io.PrintStream.println(PrintStream.java:773)
>   at java.lang.Throwable.printStackTrace(Throwable.java:461)
>   at java.lang.Throwable.printStackTrace(Throwable.java:451)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:229)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.Reflection

[jira] [Resolved] (AMQ-4289) activemq-perf-maven-plugin is unusable because of bug in ReflectionUtil helper class

[Christian Posta (JIRA)]

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

Christian Posta resolved AMQ-4289.
--

Resolution: Fixed

Fix on trunk with r1441270

> activemq-perf-maven-plugin is unusable because of bug in ReflectionUtil 
> helper class
> 
>
> Key: AMQ-4289
> URL: https://issues.apache.org/jira/browse/AMQ-4289
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Performance Test
>Affects Versions: 5.8.0
>Reporter: Christian Posta
>Assignee: Christian Posta
>  Labels: maven-activemq-perf-plugin
>
> End up getting stack overflow for recursive call in 
> ReflectionUtil.retrieveClassProperties()... if there is a getter that returns 
> itself, it will not check that the "targetObject" which it's inspecting is 
> the same as what an identity getter would return. For example, 
> RedeliveryPolicy has a method:
> getValue() {
> return this;
> }
> which causes this stack trace:
> java.lang.StackOverflowError
>   at java.io.FileOutputStream.writeBytes(Native Method)
>   at java.io.FileOutputStream.write(FileOutputStream.java:282)
>   at 
> java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
>   at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
>   at java.io.PrintStream.flush(PrintStream.java:288)
>   at 
> com.intellij.rt.execution.junit.segments.SegmentedOutputStream.flush(SegmentedOutputStream.java:48)
>   at 
> com.intellij.rt.execution.junit.segments.SegmentedOutputStream.write(SegmentedOutputStream.java:44)
>   at java.io.OutputStream.write(OutputStream.java:99)
>   at java.io.PrintStream.write(PrintStream.java:430)
>   at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:202)
>   at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:272)
>   at sun.nio.cs.StreamEncoder.flushBuffer(StreamEncoder.java:85)
>   at java.io.OutputStreamWriter.flushBuffer(OutputStreamWriter.java:168)
>   at java.io.PrintStream.write(PrintStream.java:477)
>   at java.io.PrintStream.print(PrintStream.java:619)
>   at java.io.PrintStream.println(PrintStream.java:773)
>   at java.lang.Throwable.printStackTrace(Throwable.java:461)
>   at java.lang.Throwable.printStackTrace(Throwable.java:451)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:229)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
>   at 
> org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProp

[jira] [Created] (AMQ-4289) activemq-perf-maven-plugin is unusable because of bug in ReflectionUtil helper class

[Christian Posta (JIRA)]

Christian Posta created AMQ-4289:


 Summary: activemq-perf-maven-plugin is unusable because of bug in 
ReflectionUtil helper class
 Key: AMQ-4289
 URL: https://issues.apache.org/jira/browse/AMQ-4289
 Project: ActiveMQ
  Issue Type: Bug
  Components: Performance Test
Affects Versions: 5.8.0
Reporter: Christian Posta
Assignee: Christian Posta


End up getting stack overflow for recursive call in 
ReflectionUtil.retrieveClassProperties()... if there is a getter that returns 
itself, it will not check that the "targetObject" which it's inspecting is the 
same as what an identity getter would return. For example, RedeliveryPolicy has 
a method:

getValue() {
return this;
}

which causes this stack trace:

java.lang.StackOverflowError
at java.io.FileOutputStream.writeBytes(Native Method)
at java.io.FileOutputStream.write(FileOutputStream.java:282)
at 
java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
at java.io.PrintStream.flush(PrintStream.java:288)
at 
com.intellij.rt.execution.junit.segments.SegmentedOutputStream.flush(SegmentedOutputStream.java:48)
at 
com.intellij.rt.execution.junit.segments.SegmentedOutputStream.write(SegmentedOutputStream.java:44)
at java.io.OutputStream.write(OutputStream.java:99)
at java.io.PrintStream.write(PrintStream.java:430)
at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:202)
at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:272)
at sun.nio.cs.StreamEncoder.flushBuffer(StreamEncoder.java:85)
at java.io.OutputStreamWriter.flushBuffer(OutputStreamWriter.java:168)
at java.io.PrintStream.write(PrintStream.java:477)
at java.io.PrintStream.print(PrintStream.java:619)
at java.io.PrintStream.println(PrintStream.java:773)
at java.lang.Throwable.printStackTrace(Throwable.java:461)
at java.lang.Throwable.printStackTrace(Throwable.java:451)
at 
org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:229)
at 
org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
at 
org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
at 
org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
at 
org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
at 
org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
at 
org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
at 
org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
at 
org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
at 
org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
at 
org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
at 
org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
at 
org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
at 
org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
at 
org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
at 
org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
at 
org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
at 
org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
at 
org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
at 
org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
at 
org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
at 
org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
at 
org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
at 
org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
at 
org.apache.activemq.tool.properties.ReflectionUtil.retrieveClassProperties(ReflectionUtil.java:218)
at 
org.apac

[jira] [Updated] (AMQ-1243) Multiple WebClient instances

[Timothy Bish (JIRA)]

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

Timothy Bish updated AMQ-1243:
--

Fix Version/s: (was: NEEDS_REVIEWED)
   AGING_TO_DIE

> Multiple WebClient instances
> 
>
> Key: AMQ-1243
> URL: https://issues.apache.org/jira/browse/AMQ-1243
> Project: ActiveMQ
>  Issue Type: Improvement
> Environment: Using activemq-web-demo as a test for changes in 
> activemq-web while using the 'chat demo'. Patch created from eclipse on mactel
>Reporter: James Alan Shepherd
>Assignee: Dejan Bosanac
>Priority: Minor
> Fix For: AGING_TO_DIE
>
> Attachments: ASF.LICENSE.NOT.GRANTED--patch-trunk-2007-05-04.txt, 
> patch-trunk-2007-05-09.txt
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> Just learning about ActiveMQ and noticed, like many before I imagine, that 
> the chat demo doesn't let you use it in different tabs/windows of a browser 
> at once. Well, it runs, but you share the consumers in the WebClient stored 
> in the HttpSession.
> So, why not have multiple WebClients in the Session, one for each 'rendering' 
> of the window, meaning for each instance of amq(.js)?
> So you need a UID in HttpSession for each amq instance.
> You also need to set the amq._pollDelay to something sensible, as polling is 
> done by GET and connections to the server are throttled by the browser.
> Hopefully the attached patch will seem resonable.
> Changes in _amq.js are set to test the new functionality;
> minimal changes to MessageListenerServlet;
> few changes to WebClient;
> added WebClientDirector to direct getting of correct WebClient instance and 
> creating new ones.

--
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-4147) Memory usage incorrectly updated across network of brokers when VMTransport is used.

[Timothy Bish (JIRA)]

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

Timothy Bish commented on AMQ-4147:
---

Added a fix to prevent the Bridge from propagating MemoryUsage values when 
copying.  Will look further at why we would ever want to copy MemoryUsage in 
Message.copy().  

> Memory usage incorrectly updated across network of brokers when VMTransport 
> is used.
> 
>
> Key: AMQ-4147
> URL: https://issues.apache.org/jira/browse/AMQ-4147
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.8.0
>Reporter: Stirling Chow
> Attachments: AMQ4147Test.java
>
>
> Symptom
> ===
> I was writing some unit tests based on 
> {{org.apache.activemq.JmsMultipleBrokersTestSupport}}, and noticed the 
> following issue:
> When brokers are connected in a network using VMTransport (i.e., VMTransport 
> on both the local and remote ends of a bridge), and a message moves from 
> broker1 to broker2, the memory usage of the message continues to be accounted 
> for on broker1 until the message is actually consumed on broker2.  
> If the brokers are bridged using a non-VM transport (e.g., TCP), memory usage 
> on broker1 is reduced as soon as the message is bridged to broker2, and 
> broker2's memory usage increases until the message is consumed.
> Cause
> =
> The cause is the same as in AMQ-4116: {{Message.copy()}} copies the 
> {{memoryUsage}} object.  As a result, when the message moves from broker1 to 
> broker2, the original {{memoryUsage}} object, which refers to broker1 is 
> copied through to broker2 and never updated to broker2's {{memoryUsage}} 
> object.
> Specifically, the message is copied from the local transport before being 
> sent to the remote transport by this code:
> {code:title=DemandForwardingBridgeSupport.java}
> protected void serviceLocalCommand(Command command) {
> if (!disposed.get()) {
> try {
> if (command.isMessageDispatch()) {
> enqueueCounter.incrementAndGet();
> final MessageDispatch md = (MessageDispatch) command;
> final DemandSubscription sub = 
> subscriptionMapByLocalId.get(md.getConsumerId());
> if (sub != null && md.getMessage() != null && 
> sub.incrementOutstandingResponses()) {
> if (suppressMessageDispatch(md, sub)) {
> if (LOG.isDebugEnabled()) {
> LOG.debug(configuration.getBrokerName() + " 
> message not forwarded to " + remoteBrokerName + " because message came from 
> there or fails networkTTL, brokerPath: " + 
> Arrays.toString(md.getMessage().getBrokerPath()) + ", message: " + 
> md.getMessage());
> }
> // still ack as it may be durable
> try {
> localBroker.oneway(new MessageAck(md, 
> MessageAck.INDIVIDUAL_ACK_TYPE, 1));
> } finally {
> sub.decrementOutstandingResponses();
> }
> return;
> }
> Message message = configureMessage(md);
> ...
> protected Message configureMessage(MessageDispatch md) {
> Message message = md.getMessage().copy();
> ...
> {code}
> This bug is not present when a non-VM transport is used for the bridge 
> because {{Message.memoryUsage}} is marked transient *not* copied during 
> serialization/deserialization over the transport.
> Solution
> 
> Since this is at least the second bug to result from the current 
> {{Message.copy()}} behaviour, I think "Solution 1" proposed from AMQ-4116 is 
> starting to look attractive as both a solution to AMQ-4116 and this bug:
> Modify {{Message.copy()}} so that it sets the resulting message's 
> {{memoryUsage}} object to {{null}}.  This would make {{Message.copy()}} 
> behave more similarly to serialization/deserialization.

--
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] (AMQ-4147) Memory usage incorrectly updated across network of brokers when VMTransport is used.

[Timothy Bish (JIRA)]

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

Timothy Bish updated AMQ-4147:
--

Fix Version/s: 5.8.0

> Memory usage incorrectly updated across network of brokers when VMTransport 
> is used.
> 
>
> Key: AMQ-4147
> URL: https://issues.apache.org/jira/browse/AMQ-4147
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.7.0
>Reporter: Stirling Chow
> Fix For: 5.8.0
>
> Attachments: AMQ4147Test.java
>
>
> Symptom
> ===
> I was writing some unit tests based on 
> {{org.apache.activemq.JmsMultipleBrokersTestSupport}}, and noticed the 
> following issue:
> When brokers are connected in a network using VMTransport (i.e., VMTransport 
> on both the local and remote ends of a bridge), and a message moves from 
> broker1 to broker2, the memory usage of the message continues to be accounted 
> for on broker1 until the message is actually consumed on broker2.  
> If the brokers are bridged using a non-VM transport (e.g., TCP), memory usage 
> on broker1 is reduced as soon as the message is bridged to broker2, and 
> broker2's memory usage increases until the message is consumed.
> Cause
> =
> The cause is the same as in AMQ-4116: {{Message.copy()}} copies the 
> {{memoryUsage}} object.  As a result, when the message moves from broker1 to 
> broker2, the original {{memoryUsage}} object, which refers to broker1 is 
> copied through to broker2 and never updated to broker2's {{memoryUsage}} 
> object.
> Specifically, the message is copied from the local transport before being 
> sent to the remote transport by this code:
> {code:title=DemandForwardingBridgeSupport.java}
> protected void serviceLocalCommand(Command command) {
> if (!disposed.get()) {
> try {
> if (command.isMessageDispatch()) {
> enqueueCounter.incrementAndGet();
> final MessageDispatch md = (MessageDispatch) command;
> final DemandSubscription sub = 
> subscriptionMapByLocalId.get(md.getConsumerId());
> if (sub != null && md.getMessage() != null && 
> sub.incrementOutstandingResponses()) {
> if (suppressMessageDispatch(md, sub)) {
> if (LOG.isDebugEnabled()) {
> LOG.debug(configuration.getBrokerName() + " 
> message not forwarded to " + remoteBrokerName + " because message came from 
> there or fails networkTTL, brokerPath: " + 
> Arrays.toString(md.getMessage().getBrokerPath()) + ", message: " + 
> md.getMessage());
> }
> // still ack as it may be durable
> try {
> localBroker.oneway(new MessageAck(md, 
> MessageAck.INDIVIDUAL_ACK_TYPE, 1));
> } finally {
> sub.decrementOutstandingResponses();
> }
> return;
> }
> Message message = configureMessage(md);
> ...
> protected Message configureMessage(MessageDispatch md) {
> Message message = md.getMessage().copy();
> ...
> {code}
> This bug is not present when a non-VM transport is used for the bridge 
> because {{Message.memoryUsage}} is marked transient *not* copied during 
> serialization/deserialization over the transport.
> Solution
> 
> Since this is at least the second bug to result from the current 
> {{Message.copy()}} behaviour, I think "Solution 1" proposed from AMQ-4116 is 
> starting to look attractive as both a solution to AMQ-4116 and this bug:
> Modify {{Message.copy()}} so that it sets the resulting message's 
> {{memoryUsage}} object to {{null}}.  This would make {{Message.copy()}} 
> behave more similarly to serialization/deserialization.

--
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] (AMQ-4147) Memory usage incorrectly updated across network of brokers when VMTransport is used.

[Timothy Bish (JIRA)]

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

Timothy Bish updated AMQ-4147:
--

Affects Version/s: (was: 5.8.0)
   5.7.0

> Memory usage incorrectly updated across network of brokers when VMTransport 
> is used.
> 
>
> Key: AMQ-4147
> URL: https://issues.apache.org/jira/browse/AMQ-4147
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.7.0
>Reporter: Stirling Chow
> Attachments: AMQ4147Test.java
>
>
> Symptom
> ===
> I was writing some unit tests based on 
> {{org.apache.activemq.JmsMultipleBrokersTestSupport}}, and noticed the 
> following issue:
> When brokers are connected in a network using VMTransport (i.e., VMTransport 
> on both the local and remote ends of a bridge), and a message moves from 
> broker1 to broker2, the memory usage of the message continues to be accounted 
> for on broker1 until the message is actually consumed on broker2.  
> If the brokers are bridged using a non-VM transport (e.g., TCP), memory usage 
> on broker1 is reduced as soon as the message is bridged to broker2, and 
> broker2's memory usage increases until the message is consumed.
> Cause
> =
> The cause is the same as in AMQ-4116: {{Message.copy()}} copies the 
> {{memoryUsage}} object.  As a result, when the message moves from broker1 to 
> broker2, the original {{memoryUsage}} object, which refers to broker1 is 
> copied through to broker2 and never updated to broker2's {{memoryUsage}} 
> object.
> Specifically, the message is copied from the local transport before being 
> sent to the remote transport by this code:
> {code:title=DemandForwardingBridgeSupport.java}
> protected void serviceLocalCommand(Command command) {
> if (!disposed.get()) {
> try {
> if (command.isMessageDispatch()) {
> enqueueCounter.incrementAndGet();
> final MessageDispatch md = (MessageDispatch) command;
> final DemandSubscription sub = 
> subscriptionMapByLocalId.get(md.getConsumerId());
> if (sub != null && md.getMessage() != null && 
> sub.incrementOutstandingResponses()) {
> if (suppressMessageDispatch(md, sub)) {
> if (LOG.isDebugEnabled()) {
> LOG.debug(configuration.getBrokerName() + " 
> message not forwarded to " + remoteBrokerName + " because message came from 
> there or fails networkTTL, brokerPath: " + 
> Arrays.toString(md.getMessage().getBrokerPath()) + ", message: " + 
> md.getMessage());
> }
> // still ack as it may be durable
> try {
> localBroker.oneway(new MessageAck(md, 
> MessageAck.INDIVIDUAL_ACK_TYPE, 1));
> } finally {
> sub.decrementOutstandingResponses();
> }
> return;
> }
> Message message = configureMessage(md);
> ...
> protected Message configureMessage(MessageDispatch md) {
> Message message = md.getMessage().copy();
> ...
> {code}
> This bug is not present when a non-VM transport is used for the bridge 
> because {{Message.memoryUsage}} is marked transient *not* copied during 
> serialization/deserialization over the transport.
> Solution
> 
> Since this is at least the second bug to result from the current 
> {{Message.copy()}} behaviour, I think "Solution 1" proposed from AMQ-4116 is 
> starting to look attractive as both a solution to AMQ-4116 and this bug:
> Modify {{Message.copy()}} so that it sets the resulting message's 
> {{memoryUsage}} object to {{null}}.  This would make {{Message.copy()}} 
> behave more similarly to serialization/deserialization.

--
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-4116) Memory usage is not cleared from the source queue when a message is moved to another queue over the VMTransport

[Timothy Bish (JIRA)]

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

Timothy Bish resolved AMQ-4116.
---

   Resolution: Fixed
Fix Version/s: 5.8.0
 Assignee: Timothy Bish

Fix applied, thanks for the test and patch.  

> Memory usage is not cleared from the source queue when a message is moved to 
> another queue over the VMTransport
> ---
>
> Key: AMQ-4116
> URL: https://issues.apache.org/jira/browse/AMQ-4116
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Transport
>Affects Versions: 5.7.0
>Reporter: Stirling Chow
>Assignee: Timothy Bish
> Fix For: 5.8.0
>
> Attachments: AMQ4116.patch, AMQ4116Test.java
>
>
> Reproduction
> 
> Using VMTransport:
> 1. Produce a message on queue A and verify that queue A's memory usage 
> increases
> 2. Consume the message from queue A and verify that queue A's memory usage 
> decreases.
> 3. Resend the message to queue B.
> Expected: Queue A's memory usage is not increased by the enqueue to queue B.
> Actual: Queue A's memory usage increases and no memory usage increase occurs 
> on queue B.
> Symptom
> ===
> When messages are moved between queues using the VMTransport, they continue 
> to contribute to the memory usage of the source queue rather than the 
> destination queue.
> The correct behaviour (memory usage decreases from queue A and increases in 
> queue B) is exhibited by non-VMTransport (e.g., TCP).
> Cause
> =
> When the message is first sent to queue A, it's memoryUsage field is set to 
> match queue A's:
> {code:title=org.apache.activemq.broker.region.Queue}
> public void send(final ProducerBrokerExchange producerExchange, final Message 
> message) throws Exception {
> final ConnectionContext context = producerExchange.getConnectionContext();
> // There is delay between the client sending it and it arriving at the
> // destination.. it may have expired.
> message.setRegionDestination(this);
> ...
> {code}
> {code:title=org.apache.activemq.command.Message}
> public void 
> setRegionDestination(org.apache.activemq.broker.region.Destination 
> destination) {
> this.regionDestination = destination;
> if(this.memoryUsage==null) {
> this.memoryUsage=regionDestination.getMemoryUsage();
> }
> }
> {code}
> As the message moves across the transport, it is copied along with the 
> memoryUsage field:
> {code:title=org.apache.activemq.command.Message}
> protected void copy(Message copy) {
> super.copy(copy);
> ...
> copy.memoryUsage=this.memoryUsage;
> ...
> {code}
> When the message is sent to the second queue, memoryUsage is non-null, so 
> setRegionDestination(...) does not update memoryUsage to reflect the new 
> destination queue.
> When the destination queue accepts the message, the memoryUsage of the source 
> queue is (incorrectly) increased:
> {code:title=org.apache.activemq.command.Message}
> public int incrementReferenceCount() {
> int rc;
> int size;
> synchronized (this) {
> rc = ++referenceCount;
> size = getSize();
> }
> if (rc == 1 && getMemoryUsage() != null) {
> getMemoryUsage().increaseUsage(size);
> {code}
> This mal-behaviour is not exhibited by other transports since they serialize 
> Message and memoryUsage is transient.  As a result, the call to 
> setRegionDestination(...) will properly update memoryUsage when the message 
> arrives at the destination queue.
> Solution
> 
> There are a number of possible solutions, any of which would correct the 
> behaviour (although I am unsure what side-effects they may have on other 
> behaviour):
> 1. It seems odd that memoryUsage is copied when Message is copied.  If 
> Message.copy(...) is used as a shortcut to avoid 
> serialization/deserialization on VMTransport, then it should have the same 
> semantics and avoid copying transient fields.
> 2. It seems odd that setRegionDestination(...) would not always set the 
> memoryUsage to match the destination's memoryUsage.
> 3. ActiveMQConnection has a comment regarding concessions made for messages 
> transmitted by the VM transport:
> {code:title=org.apache.activemq.ActiveMQConnection}
> public void onCommand(final Object o) {
> final Command command = (Command)o;
> if (!closed.get() && command != null) {
> try {
> command.visit(new CommandVisitorAdapter() {
> @Override
> public Response processMessageDispatch(MessageDispatch md) 
> throws Exception {
> waitForTransportInterruptionProcessingToComplete();
> ActiveMQDispatcher dispatcher = 
> dispatchers.get(md.getConsumerId());
> if (dispatcher !=

[jira] [Commented] (AMQ-4116) Memory usage is not cleared from the source queue when a message is moved to another queue over the VMTransport

[Timothy Bish (JIRA)]

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

Timothy Bish commented on AMQ-4116:
---

Agreed that when copied in ActiveMQConnection there's definitely no need for 
the copy to retain a reference to the MemoryUsage.  Will look at AMQ-4147 also 
but applying this patch won't hurt anything even if we take action on 4147.  

> Memory usage is not cleared from the source queue when a message is moved to 
> another queue over the VMTransport
> ---
>
> Key: AMQ-4116
> URL: https://issues.apache.org/jira/browse/AMQ-4116
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Transport
>Affects Versions: 5.7.0
>Reporter: Stirling Chow
> Attachments: AMQ4116.patch, AMQ4116Test.java
>
>
> Reproduction
> 
> Using VMTransport:
> 1. Produce a message on queue A and verify that queue A's memory usage 
> increases
> 2. Consume the message from queue A and verify that queue A's memory usage 
> decreases.
> 3. Resend the message to queue B.
> Expected: Queue A's memory usage is not increased by the enqueue to queue B.
> Actual: Queue A's memory usage increases and no memory usage increase occurs 
> on queue B.
> Symptom
> ===
> When messages are moved between queues using the VMTransport, they continue 
> to contribute to the memory usage of the source queue rather than the 
> destination queue.
> The correct behaviour (memory usage decreases from queue A and increases in 
> queue B) is exhibited by non-VMTransport (e.g., TCP).
> Cause
> =
> When the message is first sent to queue A, it's memoryUsage field is set to 
> match queue A's:
> {code:title=org.apache.activemq.broker.region.Queue}
> public void send(final ProducerBrokerExchange producerExchange, final Message 
> message) throws Exception {
> final ConnectionContext context = producerExchange.getConnectionContext();
> // There is delay between the client sending it and it arriving at the
> // destination.. it may have expired.
> message.setRegionDestination(this);
> ...
> {code}
> {code:title=org.apache.activemq.command.Message}
> public void 
> setRegionDestination(org.apache.activemq.broker.region.Destination 
> destination) {
> this.regionDestination = destination;
> if(this.memoryUsage==null) {
> this.memoryUsage=regionDestination.getMemoryUsage();
> }
> }
> {code}
> As the message moves across the transport, it is copied along with the 
> memoryUsage field:
> {code:title=org.apache.activemq.command.Message}
> protected void copy(Message copy) {
> super.copy(copy);
> ...
> copy.memoryUsage=this.memoryUsage;
> ...
> {code}
> When the message is sent to the second queue, memoryUsage is non-null, so 
> setRegionDestination(...) does not update memoryUsage to reflect the new 
> destination queue.
> When the destination queue accepts the message, the memoryUsage of the source 
> queue is (incorrectly) increased:
> {code:title=org.apache.activemq.command.Message}
> public int incrementReferenceCount() {
> int rc;
> int size;
> synchronized (this) {
> rc = ++referenceCount;
> size = getSize();
> }
> if (rc == 1 && getMemoryUsage() != null) {
> getMemoryUsage().increaseUsage(size);
> {code}
> This mal-behaviour is not exhibited by other transports since they serialize 
> Message and memoryUsage is transient.  As a result, the call to 
> setRegionDestination(...) will properly update memoryUsage when the message 
> arrives at the destination queue.
> Solution
> 
> There are a number of possible solutions, any of which would correct the 
> behaviour (although I am unsure what side-effects they may have on other 
> behaviour):
> 1. It seems odd that memoryUsage is copied when Message is copied.  If 
> Message.copy(...) is used as a shortcut to avoid 
> serialization/deserialization on VMTransport, then it should have the same 
> semantics and avoid copying transient fields.
> 2. It seems odd that setRegionDestination(...) would not always set the 
> memoryUsage to match the destination's memoryUsage.
> 3. ActiveMQConnection has a comment regarding concessions made for messages 
> transmitted by the VM transport:
> {code:title=org.apache.activemq.ActiveMQConnection}
> public void onCommand(final Object o) {
> final Command command = (Command)o;
> if (!closed.get() && command != null) {
> try {
> command.visit(new CommandVisitorAdapter() {
> @Override
> public Response processMessageDispatch(MessageDispatch md) 
> throws Exception {
> waitForTransportInterruptionProcessingToComplete();
> ActiveMQDispatch

[jira] [Closed] (AMQ-4164) In network of master slave brokers, if both masters down, slaves incorrectly create treat each other as slaves

[Timothy Bish (JIRA)]

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

Timothy Bish closed AMQ-4164.
-

Resolution: Won't Fix

This is no longer an issue as we don't support pure master / slave any longer.  

> In network of master slave brokers, if both masters down, slaves incorrectly 
> create treat each other as slaves
> --
>
> Key: AMQ-4164
> URL: https://issues.apache.org/jira/browse/AMQ-4164
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Transport
>Affects Versions: 5.7.0
>Reporter: Martin Serrano
> Attachments: amq-4164.patch
>
>
> When running a test with a network of master/slave brokers, I have both 
> masters go down.  In this case, the slaves are started and their respective 
> network connections are started.  The logic in 
> {{TransportConnection.processBrokerInfo(BrokerInfo info)}}, checks if the 
> info represents a slave broker and starts a MasterBroker filter if so.  
> However this logic is faulty if the info for the slave broker is arriving via 
> a network connection.
> As a result a slave tries to connect a networked broker as a slave.  This 
> results in incorrect behavior, errors, and can cause the system to lockup 
> during shutdown (due to hanging ResponseCorrelation).

--
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: Increase the temp queue timeout from 30 seconds

[Christian Posta]

Temp queues are cleared out when the connection goes away or explicitly
deleted, there is no automatic timeout that removes them. Might be a
wso2esb configuration?



On Thu, Jan 31, 2013 at 9:57 AM, pmbsa  wrote:

> Is there a simple way to increase the timeout on the replyto temp queues
> from
> 3 ms? (Request/response type implementation using wso2esb and wso2as
> axis2 services)
>
> I have some potentially long running services that are failing because the
> temp queues are being cleaned up before its done, it would really simplify
> things if I could just increase that timeout.
>
> the error is something like this
> "JMSSender Did not receive a JMS response within 3 ms to destination :
> temp-queue://.."
>
> Any assistance would be much appreciated.
>
> thanks
> Paul
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Increase-the-temp-queue-timeout-from-30-seconds-tp4662534.html
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>



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

[jira] [Closed] (AMQ-3644) Derby Persistence Adapter does not work with large queue

[Timothy Bish (JIRA)]

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

Timothy Bish closed AMQ-3644.
-

Resolution: Incomplete

No test cases provided.  And latest releases uses newest Derby version so 
should retest your code against that.

> Derby Persistence Adapter does not work with large queue
> 
>
> Key: AMQ-3644
> URL: https://issues.apache.org/jira/browse/AMQ-3644
> Project: ActiveMQ
>  Issue Type: Improvement
>  Components: Message Store
>Affects Versions: 5.4.2, 5.4.3, 5.5.1
>Reporter: Steffen Kuche
>Priority: Minor
>  Labels: broker, derby, messages, persistence
> Fix For: AGING_TO_DIE
>
> Attachments: patch.txt, test.zip
>
>
> Our application was blocked by activemq when a consumer reconnects to the 
> broker after a longer time.
> It pointed out, that the method DefaultJDBCAdapter.recoverNextMessages took 
> about *three minutes* to recover the next 20 Messages for the Store Based 
> Cursor. Here is the corresponding stacktrace:
> {noFormat}
> "BrokerService[embedded] Task" daemon prio=10 tid=0x42bcf000 
> nid=0x17fd runnable [0x7f2b342a1000]
>java.lang.Thread.State: RUNNABLE
>   at java.io.FileOutputStream.open(Native Method)
>   at java.io.FileOutputStream.(FileOutputStream.java:194)
>   at java.io.FileOutputStream.(FileOutputStream.java:145)
>   at org.apache.derby.impl.io.DirFile.getOutputStream(Unknown Source)
>   at org.apache.derby.impl.store.raw.data.StreamFileContainer.run(Unknown 
> Source)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at 
> org.apache.derby.impl.store.raw.data.StreamFileContainer.privGetOutputStream(Unknown
>  Source)
>   - locked <0xf23e6640> (a 
> org.apache.derby.impl.store.raw.data.StreamFileContainer)
>   at 
> org.apache.derby.impl.store.raw.data.StreamFileContainer.load(Unknown Source)
>   at 
> org.apache.derby.impl.store.raw.data.BaseDataFileFactory.addAndLoadStreamContainer(Unknown
>  Source)
>   at 
> org.apache.derby.impl.store.raw.xact.Xact.addAndLoadStreamContainer(Unknown 
> Source)
>   at 
> org.apache.derby.impl.store.access.sort.MergeSort.createMergeRun(Unknown 
> Source)
>   at org.apache.derby.impl.store.access.sort.MergeInserter.insert(Unknown 
> Source)
>   at org.apache.derby.impl.sql.execute.SortResultSet.loadSorter(Unknown 
> Source)
>   at org.apache.derby.impl.sql.execute.SortResultSet.openCore(Unknown 
> Source)
>   at 
> org.apache.derby.impl.sql.execute.BasicNoPutResultSetImpl.open(Unknown Source)
>   at 
> org.apache.derby.impl.sql.GenericPreparedStatement.executeStmt(Unknown Source)
>   at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown 
> Source)
>   at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown 
> Source)
>   - locked <0xa4981ec8> (a 
> org.apache.derby.impl.jdbc.EmbedConnection40)
>   at 
> org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown 
> Source)
>   at 
> org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeQuery(Unknown Source)
>   at 
> org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
>   at 
> org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
>   at 
> org.apache.activemq.store.jdbc.adapter.DefaultJDBCAdapter.doRecoverNextMessages(DefaultJDBCAdapter.java:929)
>   at 
> org.apache.activemq.store.jdbc.JDBCMessageStore.recoverNextMessages(JDBCMessageStore.java:229)
>   at 
> org.apache.activemq.store.ProxyMessageStore.recoverNextMessages(ProxyMessageStore.java:88)
>   at 
> org.apache.activemq.broker.region.cursors.QueueStorePrefetch.doFillBatch(QueueStorePrefetch.java:97)
>   at 
> org.apache.activemq.broker.region.cursors.AbstractStoreCursor.fillBatch(AbstractStoreCursor.java:262)
>   - locked <0xad06ca48> (a 
> org.apache.activemq.broker.region.cursors.QueueStorePrefetch)
>   at 
> org.apache.activemq.broker.region.cursors.AbstractStoreCursor.reset(AbstractStoreCursor.java:110)
>   at 
> org.apache.activemq.broker.region.cursors.StoreQueueCursor.reset(StoreQueueCursor.java:157)
>   - locked <0xad06ca00> (a 
> org.apache.activemq.broker.region.cursors.StoreQueueCursor)
>   at org.apache.activemq.broker.region.Queue.doPageIn(Queue.java:1678)
>   at 
> org.apache.activemq.broker.region.Queue.pageInMessages(Queue.java:1898)
>   at org.apache.activemq.broker.region.Queue.iterate(Queue.java:1425)
>   - locked <0xad06d010> (a 
> org.apache.activemq.broker.region.Queue$3)
>   at 
> org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:1

Re: http://activemq.apache.org/schema/core is missing

[Hiram Chirino]

Sorry about that.  Should be fixed now.


On Thu, Jan 31, 2013 at 2:15 PM, Kotliarsky, Oleg (Contractor) <
oleg.kotliar...@dexone.com> wrote:

> Hi
> We are looking for the urgent solution to repair our production
> environment.
>
> http://activemq.apache.org/schema/core is missing.
>
> Could you help ASAP please?
>
> Oleg Kotliarsky
> Amdocs @ Dex One Account
> 303-784-1830
>



-- 

**

*Hiram Chirino*

*Engineering | Red Hat, Inc.*

*hchir...@redhat.com  | fusesource.com | redhat.com*

*skype: hiramchirino | twitter: @hiramchirino
*

*blog: Hiram Chirino's Bit Mojo *

http://activemq.apache.org/schema/core is missing

[Kotliarsky, Oleg (Contractor)]

Hi
We are looking for the urgent solution to repair our production environment.

http://activemq.apache.org/schema/core is missing.

Could you help ASAP please?

Oleg Kotliarsky
Amdocs @ Dex One Account
303-784-1830

[jira] [Resolved] (AMQ-4288) OptimizedAckTest fails intermittently

[Timothy Bish (JIRA)]

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

Timothy Bish resolved AMQ-4288.
---

   Resolution: Fixed
Fix Version/s: 5.8.0

Thanks, passing now repeatedly on my old mac. 

> OptimizedAckTest fails intermittently
> -
>
> Key: AMQ-4288
> URL: https://issues.apache.org/jira/browse/AMQ-4288
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Test Cases
>Reporter: Kevin Earls
>Priority: Minor
> Fix For: 5.8.0
>
> Attachments: AMQ4288A.patch, AMQ4288B.patch, AMQ4288.patch
>
>
> Both the testVerySlowReceivedMessageStillInflight and 
> testReceivedMessageNotInFlightAfterScheduledAckFires tests fail.

--
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] (AMQ-4288) OptimizedAckTest fails intermittently

[Kevin Earls (JIRA)]

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

Kevin Earls updated AMQ-4288:
-

Attachment: AMQ4288B.patch

Updated the test to wait for acks to finish after receiving the 7th message.  
This should eliminate the race condition the tests were hitting before.

> OptimizedAckTest fails intermittently
> -
>
> Key: AMQ-4288
> URL: https://issues.apache.org/jira/browse/AMQ-4288
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Test Cases
>Reporter: Kevin Earls
>Priority: Minor
> Attachments: AMQ4288A.patch, AMQ4288B.patch, AMQ4288.patch
>
>
> Both the testVerySlowReceivedMessageStillInflight and 
> testReceivedMessageNotInFlightAfterScheduledAckFires tests fail.

--
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-450) Win32 Thread Handle Leak

[Timothy Bish (JIRA)]

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

Timothy Bish commented on AMQCPP-450:
-

Would happen regardless of the Windows Arch in use.  Will leak on every 
reconnect if you are using the failover transport.  Would recommend you grab 
the v3.5.1-SNAPSHOT I just pushed to here:  
http://people.apache.org/~tabish/cms-3.5.x/

> Win32 Thread Handle Leak
> 
>
> Key: AMQCPP-450
> URL: https://issues.apache.org/jira/browse/AMQCPP-450
> Project: ActiveMQ C++ Client
>  Issue Type: Bug
>  Components: Decaf
>Affects Versions: 3.5.0
> Environment: Windows client/AMQ 5.7 broker
>Reporter: Scott Weaver
>Assignee: Timothy Bish
>Priority: Minor
> Fix For: 3.5.1, 3.6.0
>
>
> PlatformThread::detachOSThread(thread->handle) missing from threading 
> library's dereferenceThread() method right before deleting thread. Adding 
> this in prevents large thread handle leak in win32 environment. Recreate by 
> cycling the broker with an active subscription and watch the handle count 
> grow each time it is cycled.

--
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-450) Win32 Thread Handle Leak

[Tom Liebl (JIRA)]

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

Tom Liebl commented on AMQCPP-450:
--

Could you clarify the severity of this issue? Does this only happen when the 
broker is restarted with active subscriptions? And only when using win32? 64bit 
is unaffected? 

> Win32 Thread Handle Leak
> 
>
> Key: AMQCPP-450
> URL: https://issues.apache.org/jira/browse/AMQCPP-450
> Project: ActiveMQ C++ Client
>  Issue Type: Bug
>  Components: Decaf
>Affects Versions: 3.5.0
> Environment: Windows client/AMQ 5.7 broker
>Reporter: Scott Weaver
>Assignee: Timothy Bish
>Priority: Minor
> Fix For: 3.5.1, 3.6.0
>
>
> PlatformThread::detachOSThread(thread->handle) missing from threading 
> library's dereferenceThread() method right before deleting thread. Adding 
> this in prevents large thread handle leak in win32 environment. Recreate by 
> cycling the broker with an active subscription and watch the handle count 
> grow each time it is cycled.

--
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-4288) OptimizedAckTest fails intermittently

[Timothy Bish (JIRA)]

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

Timothy Bish commented on AMQ-4288:
---

Still seeing failures on my old Mac

> OptimizedAckTest fails intermittently
> -
>
> Key: AMQ-4288
> URL: https://issues.apache.org/jira/browse/AMQ-4288
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Test Cases
>Reporter: Kevin Earls
>Priority: Minor
> Attachments: AMQ4288A.patch, AMQ4288.patch
>
>
> Both the testVerySlowReceivedMessageStillInflight and 
> testReceivedMessageNotInFlightAfterScheduledAckFires tests fail.

--
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] (AMQ-4288) OptimizedAckTest fails intermittently

[Kevin Earls (JIRA)]

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

Kevin Earls updated AMQ-4288:
-

Attachment: AMQ4288A.patch

Updated to include the save fix for the testReceivedMessageStillInflight test.


> OptimizedAckTest fails intermittently
> -
>
> Key: AMQ-4288
> URL: https://issues.apache.org/jira/browse/AMQ-4288
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Test Cases
>Reporter: Kevin Earls
>Priority: Minor
> Attachments: AMQ4288A.patch, AMQ4288.patch
>
>
> Both the testVerySlowReceivedMessageStillInflight and 
> testReceivedMessageNotInFlightAfterScheduledAckFires tests fail.

--
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] (AMQ-4288) OptimizedAckTest fails intermittently

[Kevin Earls (JIRA)]

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

Kevin Earls updated AMQ-4288:
-

Attachment: AMQ4288.patch

Fixed (? or at least improved) a race condition in both test cases which 
occurred intermittently on slower machines.
  

> OptimizedAckTest fails intermittently
> -
>
> Key: AMQ-4288
> URL: https://issues.apache.org/jira/browse/AMQ-4288
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Test Cases
>Reporter: Kevin Earls
>Priority: Minor
> Attachments: AMQ4288.patch
>
>
> Both the testVerySlowReceivedMessageStillInflight and 
> testReceivedMessageNotInFlightAfterScheduledAckFires tests fail.

--
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] (AMQ-4288) OptimizedAckTest fails intermittently

[Kevin Earls (JIRA)]

Kevin Earls created AMQ-4288:


 Summary: OptimizedAckTest fails intermittently
 Key: AMQ-4288
 URL: https://issues.apache.org/jira/browse/AMQ-4288
 Project: ActiveMQ
  Issue Type: Bug
  Components: Test Cases
Reporter: Kevin Earls
Priority: Minor


Both the testVerySlowReceivedMessageStillInflight and 
testReceivedMessageNotInFlightAfterScheduledAckFires tests fail.

--
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

Increase the temp queue timeout from 30 seconds

[pmbsa]

Is there a simple way to increase the timeout on the replyto temp queues from
3 ms? (Request/response type implementation using wso2esb and wso2as
axis2 services)
 
I have some potentially long running services that are failing because the
temp queues are being cleaned up before its done, it would really simplify
things if I could just increase that timeout.

the error is something like this
"JMSSender Did not receive a JMS response within 3 ms to destination :
temp-queue://.."

Any assistance would be much appreciated.

thanks
Paul



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Increase-the-temp-queue-timeout-from-30-seconds-tp4662534.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

[jira] [Commented] (AMQ-4287) REOPEN - javax.jms.JMSException: The resource is allready being used in transaction context.

[Gary Tully (JIRA)]

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

Gary Tully commented on AMQ-4287:
-

would it be possible to modify one of the existing test cases to try and build 
a reproducible test case?
http://svn.apache.org/viewvc/activemq/trunk/activemq-ra/src/test/java/org/apache/activemq/ra/?pathrev=1440531

> REOPEN - javax.jms.JMSException: The resource is allready being used in 
> transaction context. 
> -
>
> Key: AMQ-4287
> URL: https://issues.apache.org/jira/browse/AMQ-4287
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Connector
>Affects Versions: 5.5.0, 5.5.1, 5.7.0
> Environment: SLES11sp1 64bits, Glassfish 2.1.1, Glassfish 3.1.1 
> activemq-5.5.0, jdk6
> Linux (unknow), Glassfish 3.1, activemq-5.5.1, 
> activemq-rar-5.7.0.rar
>Reporter: Marcin Cinik
>Priority: Critical
>
> I had to reopen the previous issue as the problem is still existing.
> I am using activemq-5.5 with activemq-rar-5.7.0.rar and I am getting
> {quote}
> Caused by: javax.jms.JMSException: The resource is already being used in 
> transaction context.
> at 
> org.apache.activemq.ra.ManagedTransactionContext.setUseSharedTxContext(ManagedTransactionContext.java:47)
> at 
> org.apache.activemq.ra.ManagedSessionProxy.setUseSharedTxContext(ManagedSessionProxy.java:67)
> at 
> org.apache.activemq.ra.ManagedConnectionProxy.createSessionProxy(ManagedConnectionProxy.java:122)
> at 
> org.apache.activemq.ra.ManagedConnectionProxy.createSession(ManagedConnectionProxy.java:105)
> {quote}
> under high load. This is certainly critical issue as it prevents from using 
> rar adapter for any serious applications.

--
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-4285) NetworkFailoverTest failing

[Gary Tully (JIRA)]

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

Gary Tully resolved AMQ-4285.
-

Resolution: Fixed
  Assignee: Gary Tully

it looks better now.

there are a bunch of pitfalls of request/reply with temps over a network.

temps are not persistent and are tied to the connection that creates them so  
failures can occur when a connection fails.

some appropriate mods to the test

- backup=false in failover - otherwise there is a race between failover restore 
and broker teardown of the old connection.
 -- we can loose a replayed temp dest, if it arrives before the remove is 
complete.

- Broker.setCacheTempDestinations - this helps with reply that occur before the 
destination is removed during failover. the cache keeps the message (a form of 
temp persistence)

- tracking DestinationDoesNotExistException - a reply may fail if it occurs 
during failover recovery

- tracking dlq due to failed forwards that result from 
DestinationDoesNotExistException

> NetworkFailoverTest failing 
> 
>
> Key: AMQ-4285
> URL: https://issues.apache.org/jira/browse/AMQ-4285
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Test Cases
>Affects Versions: 5.7.0
>Reporter: Timothy Bish
>Assignee: Gary Tully
>Priority: Minor
> Fix For: 5.8.0
>
>
> The test case NetworkFailoverTest is failing most times on my machine, will 
> fail more often if the message count value is increased. 

--
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: Double Checking the svn pubsub website

[Hiram Chirino]

Thanks for the heads up.  I've checked them in now.


On Thu, Jan 31, 2013 at 4:33 AM, Massimo Paladin wrote:

> Hiram,
>
> there is a problem with the website, if you try to browse it (
> http://activemq.apache.org/)
> the css and js in styles subdir are broken.
>
> I don't see any styles folder in
> https://svn.apache.org/repos/infra/websites/production/activemq/content
>
> Cheers,
>
> ---
> Massimo Paladin
>
> email: massimo.pala...@gmail.com
> website: http://www.mpaladin.com
>
>
> On Wed, Jan 30, 2013 at 2:16 PM, Hiram Chirino  >wrote:
>
> > Well it looks good to me.  Going to have them switch it live.
> >
> >
> > On Mon, Jan 28, 2013 at 6:02 PM, Hiram Chirino  > >wrote:
> >
> > > Hi guys so we need to switch over the website to the svn pubsub system.
> > >  see: https://issues.apache.org/jira/browse/INFRA-5381
> > >
> > > So the website is now checked into:
> > >
> https://svn.apache.org/repos/infra/websites/production/activemq/content<
> >
> https://svn.apache.org/repos/infra/websites/production/activemq/content/index.html
> > >
> > >
> > > Could you guys check it out, browse it and double check it looks ok
> > before
> > > we switch the live site to it?  Thanks!
> > >
> > > --
> > >
> > > **
> > >
> > > *Hiram Chirino*
> > >
> > > *Engineering | Red Hat, Inc.*
> > >
> > > *hchir...@redhat.com  | fusesource.com |
> redhat.com
> > *
> > >
> > > *skype: hiramchirino | twitter: @hiramchirino<
> > http://twitter.com/hiramchirino>
> > > *
> > >
> > > *blog: Hiram Chirino's Bit Mojo *
> > >
> > >
> >
> >
> > --
> >
> > **
> >
> > *Hiram Chirino*
> >
> > *Engineering | Red Hat, Inc.*
> >
> > *hchir...@redhat.com  | fusesource.com | redhat.com
> *
> >
> > *skype: hiramchirino | twitter: @hiramchirino<
> > http://twitter.com/hiramchirino>
> > *
> >
> > *blog: Hiram Chirino's Bit Mojo *
> >
>



-- 

**

*Hiram Chirino*

*Engineering | Red Hat, Inc.*

*hchir...@redhat.com  | fusesource.com | redhat.com*

*skype: hiramchirino | twitter: @hiramchirino
*

*blog: Hiram Chirino's Bit Mojo *

activemq-apollo pull request: Update apollo-website/src/documentation/getti...

[xorbyte]

GitHub user xorbyte opened a pull request:

https://github.com/apache/activemq-apollo/pull/2

Update apollo-website/src/documentation/getting-started.md

Fixed a few typos and grammar errors.

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

$ git pull https://github.com/xorbyte/activemq-apollo patch-1

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

https://github.com/apache/activemq-apollo/pull/2.patch


commit fde540f4f7310954deab78985f5159bcc79a8862
Author: alexandru totolici 
Date:   2013-01-31T06:05:33Z

Update apollo-website/src/documentation/getting-started.md

Fixed a few typos and grammar errors.

[jira] [Updated] (AMQ-4287) REOPEN - javax.jms.JMSException: The resource is allready being used in transaction context.

[Marcin Cinik (JIRA)]

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

Marcin Cinik updated AMQ-4287:
--

  Component/s: Connector
 Priority: Critical  (was: Major)
  Description: 
I had to reopen the previous issue as the problem is still existing.
I am using activemq-5.5 with activemq-rar-5.7.0.rar and I am getting

{quote}
Caused by: javax.jms.JMSException: The resource is already being used in 
transaction context.
at 
org.apache.activemq.ra.ManagedTransactionContext.setUseSharedTxContext(ManagedTransactionContext.java:47)
at 
org.apache.activemq.ra.ManagedSessionProxy.setUseSharedTxContext(ManagedSessionProxy.java:67)
at 
org.apache.activemq.ra.ManagedConnectionProxy.createSessionProxy(ManagedConnectionProxy.java:122)
at 
org.apache.activemq.ra.ManagedConnectionProxy.createSession(ManagedConnectionProxy.java:105)
{quote}
under high load. This is certainly critical issue as it prevents from using rar 
adapter for any serious applications.

  was:
My error code:
{quote}javax.ejb.EJBException: nested exception is: javax.jms.JMSException: The 
resource is allready being used in transaction context.
javax.jms.JMSException: The resource is allready being used in transaction 
context.
at 
org.apache.activemq.ra.ManagedTransactionContext.setUseSharedTxContext(ManagedTransactionContext.java:47)
at 
org.apache.activemq.ra.ManagedSessionProxy.setUseSharedTxContext(ManagedSessionProxy.java:67)
at 
org.apache.activemq.ra.ManagedConnectionProxy.createSessionProxy(ManagedConnectionProxy.java:122)
at 
org.apache.activemq.ra.ManagedConnectionProxy.createSession(ManagedConnectionProxy.java:105)
at ch.no.prod.mdb.ToProdMDB.publish(ToProdMDB.java:163)
at ch.no.prod.mdb.ToProdMDB.onMessage(ToProdMDB.java:107)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
com.sun.enterprise.security.application.EJBSecurityManager.runMethod(EJBSecurityManager.java:1011)
at 
com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:175)
at 
com.sun.ejb.containers.BaseContainer.invokeTargetBeanMethod(BaseContainer.java:2929)
at 
com.sun.ejb.containers.BaseContainer.intercept(BaseContainer.java:4020)
at 
com.sun.ejb.containers.MessageBeanContainer.deliverMessage(MessageBeanContainer.java:)
at 
com.sun.ejb.containers.MessageBeanListenerImpl.deliverMessage(MessageBeanListenerImpl.java:74)
at 
com.sun.enterprise.connectors.inflow.MessageEndpointInvocationHandler.invoke(MessageEndpointInvocationHandler.java:179)
at $Proxy62.onMessage(Unknown Source)
at 
org.apache.activemq.ra.MessageEndpointProxy$MessageEndpointAlive.onMessage(MessageEndpointProxy.java:123)
at 
org.apache.activemq.ra.MessageEndpointProxy.onMessage(MessageEndpointProxy.java:64)
at org.apache.activemq.ActiveMQSession.run(ActiveMQSession.java:833)
at 
org.apache.activemq.ra.ServerSessionImpl.run(ServerSessionImpl.java:169)
at com.sun.enterprise.connectors.work.OneWork.doWork(OneWork.java:77)
at 
com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:555)
javax.ejb.EJBException: nested exception is: javax.jms.JMSException: The 
resource is allready being used in transaction context.
at ch.no.prod.mdb.ToProdMDB.publish(ToProdMDB.java:279)
at ch.no.prod.mdb.ToProdMDB.onMessage(ToProdMDB.java:107)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
com.sun.enterprise.security.application.EJBSecurityManager.runMethod(EJBSecurityManager.java:1011)
at 
com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:175)
at 
com.sun.ejb.containers.BaseContainer.invokeTargetBeanMethod(BaseContainer.java:2929)
at 
com.sun.ejb.containers.BaseContainer.intercept(BaseContainer.java:4020)
at 
com.sun.ejb.containers.MessageBeanContainer.deliverMessage(MessageBeanContainer.java:)
at 
com.sun.ejb.containers.MessageBeanListenerImpl.deliverMessage(MessageBeanListenerImpl.java:74)
at 
com.sun.enterprise.connectors.inflow.MessageEndpointInvocationHandler.invoke(MessageEndpointInvocationHandler.java:179)
at $Proxy62.onMessage(Unknown Source)
at 
org.apache.activemq.ra.MessageEndpointProxy$MessageEndpointAlive.onMessage(MessageEnd

[jira] [Created] (AMQ-4287) REOPEN - javax.jms.JMSException: The resource is allready being used in transaction context.

[Marcin Cinik (JIRA)]

Marcin Cinik created AMQ-4287:
-

 Summary: REOPEN - javax.jms.JMSException: The resource is allready 
being used in transaction context. 
 Key: AMQ-4287
 URL: https://issues.apache.org/jira/browse/AMQ-4287
 Project: ActiveMQ
  Issue Type: Bug
Affects Versions: 5.5.0, 5.5.1
 Environment: SLES11sp1 64bits, Glassfish 2.1.1, activemq-5.5.0, jdk6
Linux (unknow), Glassfish 3.1, activemq-5.5.1
Reporter: Marcin Cinik


My error code:
{quote}javax.ejb.EJBException: nested exception is: javax.jms.JMSException: The 
resource is allready being used in transaction context.
javax.jms.JMSException: The resource is allready being used in transaction 
context.
at 
org.apache.activemq.ra.ManagedTransactionContext.setUseSharedTxContext(ManagedTransactionContext.java:47)
at 
org.apache.activemq.ra.ManagedSessionProxy.setUseSharedTxContext(ManagedSessionProxy.java:67)
at 
org.apache.activemq.ra.ManagedConnectionProxy.createSessionProxy(ManagedConnectionProxy.java:122)
at 
org.apache.activemq.ra.ManagedConnectionProxy.createSession(ManagedConnectionProxy.java:105)
at ch.no.prod.mdb.ToProdMDB.publish(ToProdMDB.java:163)
at ch.no.prod.mdb.ToProdMDB.onMessage(ToProdMDB.java:107)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
com.sun.enterprise.security.application.EJBSecurityManager.runMethod(EJBSecurityManager.java:1011)
at 
com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:175)
at 
com.sun.ejb.containers.BaseContainer.invokeTargetBeanMethod(BaseContainer.java:2929)
at 
com.sun.ejb.containers.BaseContainer.intercept(BaseContainer.java:4020)
at 
com.sun.ejb.containers.MessageBeanContainer.deliverMessage(MessageBeanContainer.java:)
at 
com.sun.ejb.containers.MessageBeanListenerImpl.deliverMessage(MessageBeanListenerImpl.java:74)
at 
com.sun.enterprise.connectors.inflow.MessageEndpointInvocationHandler.invoke(MessageEndpointInvocationHandler.java:179)
at $Proxy62.onMessage(Unknown Source)
at 
org.apache.activemq.ra.MessageEndpointProxy$MessageEndpointAlive.onMessage(MessageEndpointProxy.java:123)
at 
org.apache.activemq.ra.MessageEndpointProxy.onMessage(MessageEndpointProxy.java:64)
at org.apache.activemq.ActiveMQSession.run(ActiveMQSession.java:833)
at 
org.apache.activemq.ra.ServerSessionImpl.run(ServerSessionImpl.java:169)
at com.sun.enterprise.connectors.work.OneWork.doWork(OneWork.java:77)
at 
com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:555)
javax.ejb.EJBException: nested exception is: javax.jms.JMSException: The 
resource is allready being used in transaction context.
at ch.no.prod.mdb.ToProdMDB.publish(ToProdMDB.java:279)
at ch.no.prod.mdb.ToProdMDB.onMessage(ToProdMDB.java:107)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
com.sun.enterprise.security.application.EJBSecurityManager.runMethod(EJBSecurityManager.java:1011)
at 
com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:175)
at 
com.sun.ejb.containers.BaseContainer.invokeTargetBeanMethod(BaseContainer.java:2929)
at 
com.sun.ejb.containers.BaseContainer.intercept(BaseContainer.java:4020)
at 
com.sun.ejb.containers.MessageBeanContainer.deliverMessage(MessageBeanContainer.java:)
at 
com.sun.ejb.containers.MessageBeanListenerImpl.deliverMessage(MessageBeanListenerImpl.java:74)
at 
com.sun.enterprise.connectors.inflow.MessageEndpointInvocationHandler.invoke(MessageEndpointInvocationHandler.java:179)
at $Proxy62.onMessage(Unknown Source)
at 
org.apache.activemq.ra.MessageEndpointProxy$MessageEndpointAlive.onMessage(MessageEndpointProxy.java:123)
at 
org.apache.activemq.ra.MessageEndpointProxy.onMessage(MessageEndpointProxy.java:64)
at org.apache.activemq.ActiveMQSession.run(ActiveMQSession.java:833)
at 
org.apache.activemq.ra.ServerSessionImpl.run(ServerSessionImpl.java:169)
at com.sun.enterprise.connectors.work.OneWork.doWork(OneWork.java:77)
at 
com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:555){quote}
 
And more informations found on web : 
http://osdir.com/ml/general/2011-11/msg2.html and 
htt

Re: Double Checking the svn pubsub website

[Massimo Paladin]

Hiram,

there is a problem with the website, if you try to browse it (
http://activemq.apache.org/)
the css and js in styles subdir are broken.

I don't see any styles folder in
https://svn.apache.org/repos/infra/websites/production/activemq/content

Cheers,

---
Massimo Paladin

email: massimo.pala...@gmail.com
website: http://www.mpaladin.com


On Wed, Jan 30, 2013 at 2:16 PM, Hiram Chirino wrote:

> Well it looks good to me.  Going to have them switch it live.
>
>
> On Mon, Jan 28, 2013 at 6:02 PM, Hiram Chirino  >wrote:
>
> > Hi guys so we need to switch over the website to the svn pubsub system.
> >  see: https://issues.apache.org/jira/browse/INFRA-5381
> >
> > So the website is now checked into:
> > https://svn.apache.org/repos/infra/websites/production/activemq/content<
> https://svn.apache.org/repos/infra/websites/production/activemq/content/index.html
> >
> >
> > Could you guys check it out, browse it and double check it looks ok
> before
> > we switch the live site to it?  Thanks!
> >
> > --
> >
> > **
> >
> > *Hiram Chirino*
> >
> > *Engineering | Red Hat, Inc.*
> >
> > *hchir...@redhat.com  | fusesource.com | redhat.com
> *
> >
> > *skype: hiramchirino | twitter: @hiramchirino<
> http://twitter.com/hiramchirino>
> > *
> >
> > *blog: Hiram Chirino's Bit Mojo *
> >
> >
>
>
> --
>
> **
>
> *Hiram Chirino*
>
> *Engineering | Red Hat, Inc.*
>
> *hchir...@redhat.com  | fusesource.com | redhat.com*
>
> *skype: hiramchirino | twitter: @hiramchirino<
> http://twitter.com/hiramchirino>
> *
>
> *blog: Hiram Chirino's Bit Mojo *
>