Build failed in Jenkins: ActiveMQ-Trunk-Deploy » ActiveMQ :: LevelDB Store #722
See https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq$activemq-leveldb-store/722/ -- [INFO] [INFO] [INFO] Building ActiveMQ :: LevelDB Store 5.9-SNAPSHOT [INFO] [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ activemq-leveldb-store --- [INFO] [INFO] --- maven-enforcer-plugin:1.0.1:enforce (default) @ activemq-leveldb-store --- [INFO] [INFO] --- maven-bundle-plugin:2.3.7:cleanVersions (cleanVersions) @ activemq-leveldb-store --- [INFO] [INFO] Compiling: https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq$activemq-leveldb-store/ws/src/main/proto/records.proto [INFO] --- hawtbuf-protoc:1.9:compile (default) @ activemq-leveldb-store --- [INFO] [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ activemq-leveldb-store --- [debug] execute contextualize [INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq$activemq-leveldb-store/ws/src/main/resources [INFO] Copying 3 resources [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ activemq-leveldb-store --- [INFO] [INFO] --- scala-maven-plugin:3.1.0:compile (default) @ activemq-leveldb-store --- [INFO] https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq$activemq-leveldb-store/ws/src/main/java:-1: info: compiling [INFO] https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq$activemq-leveldb-store/ws/target/generated-sources/proto:-1: info: compiling [INFO] https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq$activemq-leveldb-store/ws/src/main/scala:-1: info: compiling [INFO] Compiling 21 source files to https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq$activemq-leveldb-store/ws/target/classes at 1361268499963 [INFO] compiler plugin: BasicArtifact(org.fusesource.jvmassert,jvmassert,1.4,null) [WARNING] https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq$activemq-leveldb-store/ws/src/main/scala/org/apache/activemq/leveldb/DBManager.scala:255: warning: non-variable type argument Long in type pattern (Long, Int) is unchecked since it is eliminated by erasure [WARNING] case x:(Long, Int) = [WARNING] ^ [WARNING] https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq$activemq-leveldb-store/ws/src/main/scala/org/apache/activemq/leveldb/LevelDBClient.scala:1103: warning: non-variable type argument Long in type pattern (Long, Int) is unchecked since it is eliminated by erasure [WARNING] case x:(Long, Int) = x [WARNING]^ [WARNING] https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq$activemq-leveldb-store/ws/src/main/scala/org/apache/activemq/leveldb/LevelDBClient.scala:1124: warning: non-variable type argument Long in type pattern (Long, Int) is unchecked since it is eliminated by erasure [WARNING] case x:(Long, Int) = x [WARNING]^ [WARNING] https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq$activemq-leveldb-store/ws/src/main/scala/org/apache/activemq/leveldb/LevelDBClient.scala:1167: warning: non-variable type argument Long in type pattern (Long, Int) is unchecked since it is eliminated by erasure [WARNING] case x:(Long, Int) = x [WARNING]^ [WARNING] warning: there were 6 feature warnings; re-run with -feature for details [WARNING] 5 warnings found [INFO] prepare-compile in 0 s [INFO] compile in 34 s [INFO] [INFO] Compiling 8 source files to https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq$activemq-leveldb-store/ws/target/classes [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ activemq-leveldb-store --- [INFO] [INFO] Nothing to compile - all classes are up to date [INFO] --- scala-maven-plugin:3.1.0:compile (compile) @ activemq-leveldb-store --- [debug] execute contextualize [INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 1 resource [INFO] Copying 3 resources [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ activemq-leveldb-store --- [INFO] [INFO] No sources to compile [INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ activemq-leveldb-store --- [INFO] [INFO] https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq$activemq-leveldb-store/ws/src/test/scala:-1: info: compiling [INFO] Compiling 10 source files to
Build failed in Jenkins: ActiveMQ-Trunk-Deploy #722
See https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/722/changes Changes: [tabish] fix for: https://issues.apache.org/jira/browse/AMQ-4331 -- [...truncated 12342 lines...] Uploaded: https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/tooling/maven-metadata.xml (606 B at 1.7 KB/sec) Uploading: https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/tooling/activemq-maven-plugin/5.9-SNAPSHOT/activemq-maven-plugin-5.9-20130219.101129-12-sources.jar Uploaded: https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/tooling/activemq-maven-plugin/5.9-SNAPSHOT/activemq-maven-plugin-5.9-20130219.101129-12-sources.jar (11 KB at 27.1 KB/sec) Uploading: https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/tooling/activemq-maven-plugin/5.9-SNAPSHOT/maven-metadata.xml Uploaded: https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/tooling/activemq-maven-plugin/5.9-SNAPSHOT/maven-metadata.xml (2 KB at 3.4 KB/sec) Uploading: https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/tooling/activemq-maven-plugin/5.9-SNAPSHOT/activemq-maven-plugin-5.9-20130219.101129-12-javadoc.jar Uploaded: https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/tooling/activemq-maven-plugin/5.9-SNAPSHOT/activemq-maven-plugin-5.9-20130219.101129-12-javadoc.jar (33 KB at 84.3 KB/sec) Uploading: https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/tooling/activemq-maven-plugin/5.9-SNAPSHOT/maven-metadata.xml Uploaded: https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/tooling/activemq-maven-plugin/5.9-SNAPSHOT/maven-metadata.xml (2 KB at 3.6 KB/sec) [INFO] [INFO] [INFO] Skipping ActiveMQ :: Web [INFO] This project has been banned from the build due to previous failures. [INFO] [INFO] [INFO] [INFO] Skipping ActiveMQ :: Web Demo [INFO] This project has been banned from the build due to previous failures. [INFO] [INFO] [INFO] [INFO] Skipping ActiveMQ :: Web Console [INFO] This project has been banned from the build due to previous failures. [INFO] [INFO] [INFO] [INFO] Skipping ActiveMQ :: Integration Test :: Spring 3.1 [INFO] This project has been banned from the build due to previous failures. [INFO] [INFO] [INFO] [INFO] Skipping ActiveMQ :: Assembly [INFO] This project has been banned from the build due to previous failures. [INFO] [INFO] [INFO] Reactor Summary: [INFO] [INFO] ActiveMQ .. SUCCESS [44.243s] [INFO] ActiveMQ :: Openwire Generator SUCCESS [13.996s] [INFO] ActiveMQ :: Client SUCCESS [34.339s] [INFO] ActiveMQ :: Openwire Legacy Support ... SUCCESS [20.992s] [INFO] ActiveMQ :: JAAS .. SUCCESS [14.879s] [INFO] ActiveMQ :: Broker SUCCESS [23.178s] [INFO] ActiveMQ :: KahaDB Store .. SUCCESS [15.920s] [INFO] ActiveMQ :: STOMP Protocol SUCCESS [11.911s] [INFO] ActiveMQ :: MQTT Protocol . SUCCESS [15.529s] [INFO] ActiveMQ :: JDBC Store SUCCESS [10.804s] [INFO] ActiveMQ :: LevelDB Store . FAILURE [1:16.277s] [INFO] ActiveMQ :: RA SUCCESS [15.291s] [INFO] ActiveMQ :: Pool .. SUCCESS [10.273s] [INFO] ActiveMQ :: Spring SKIPPED [INFO] ActiveMQ :: AMQP .. SKIPPED [INFO] ActiveMQ :: Console ... SUCCESS [17.381s] [INFO] ActiveMQ :: Unit Tests
Build failed in Jenkins: ActiveMQ #1227
See https://builds.apache.org/job/ActiveMQ/1227/changes Changes: [tabish] fix for: https://issues.apache.org/jira/browse/AMQ-4331 [gtully] https://issues.apache.org/jira/browse/AMQ-4328 - fix and test. With a large backlog the flow can block when the vm transport is sync b/c the async requests can overlap with acks -- [...truncated 5628 lines...] Results : Failed tests: testRepeatStressWithCache(org.apache.activemq.store.kahadb.plist.PListImplTest): test did not timeout Tests run: 58, Failures: 1, Errors: 0, Skipped: 1 [ERROR] There are test failures. Please refer to https://builds.apache.org/job/ActiveMQ/ws/activemq-kahadb-store/target/surefire-reports for the individual test results. [JENKINS] Recording test results [INFO] [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ activemq-kahadb-store --- [INFO] Building jar: https://builds.apache.org/job/ActiveMQ/ws/activemq-kahadb-store/target/activemq-kahadb-store-5.9-SNAPSHOT.jar [INFO] [INFO] --- maven-site-plugin:3.1:attach-descriptor (attach-descriptor) @ activemq-kahadb-store --- [INFO] Checking legal files in: activemq-kahadb-store-5.9-SNAPSHOT.jar [INFO] [INFO] --- ianal-maven-plugin:1.0-alpha-1:verify-legal-files (default) @ activemq-kahadb-store --- [INFO] [INFO] Installing https://builds.apache.org/job/ActiveMQ/ws/activemq-kahadb-store/target/activemq-kahadb-store-5.9-SNAPSHOT.jar to /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/activemq/activemq-kahadb-store/5.9-SNAPSHOT/activemq-kahadb-store-5.9-SNAPSHOT.jar [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ activemq-kahadb-store --- [INFO] Installing https://builds.apache.org/job/ActiveMQ/ws/activemq-kahadb-store/pom.xml to /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/activemq/activemq-kahadb-store/5.9-SNAPSHOT/activemq-kahadb-store-5.9-SNAPSHOT.pom [INFO] [INFO] --- maven-enforcer-plugin:1.0.1:enforce (default) @ activemq-kahadb-store --- [INFO] [INFO] --- maven-bundle-plugin:2.3.7:cleanVersions (cleanVersions) @ activemq-kahadb-store --- Feb 19, 2013 10:30:51 AM hudson.maven.ExecutedMojo init WARNING: Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo [INFO] [INFO] --- maven-source-plugin:2.1.2:jar (default-cli) @ activemq-kahadb-store --- [INFO] org already added, skipping [INFO] org/apache already added, skipping [INFO] org/apache/activemq already added, skipping [INFO] org/apache/activemq/store already added, skipping [INFO] org/apache/activemq/store/kahadb already added, skipping [INFO] META-INF already added, skipping [INFO] META-INF/NOTICE already added, skipping [INFO] META-INF/DEPENDENCIES already added, skipping [INFO] META-INF/LICENSE already added, skipping [INFO] Building jar: https://builds.apache.org/job/ActiveMQ/ws/activemq-kahadb-store/target/activemq-kahadb-store-5.9-SNAPSHOT-sources.jar [INFO] org already added, skipping [INFO] org/apache already added, skipping [INFO] org/apache/activemq already added, skipping [INFO] org/apache/activemq/store already added, skipping [INFO] org/apache/activemq/store/kahadb already added, skipping [INFO] META-INF already added, skipping [INFO] META-INF/NOTICE already added, skipping [INFO] META-INF/DEPENDENCIES already added, skipping [INFO] META-INF/LICENSE already added, skipping [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 [INFO] [INFO] Building ActiveMQ :: STOMP Protocol 5.9-SNAPSHOT [INFO] [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 [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ activemq-stomp --- [INFO] [INFO] --- maven-enforcer-plugin:1.0.1:enforce (default) @ activemq-stomp --- [INFO] [INFO] --- maven-bundle-plugin:2.3.7:cleanVersions (cleanVersions) @ activemq-stomp --- [INFO] [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ activemq-stomp --- [INFO] [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 14 resources [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ activemq-stomp --- [INFO] skip non existing resourceDirectory https://builds.apache.org/job/ActiveMQ/ws/activemq-stomp/src/main/filtered-resources [INFO] Copying 3 resources [INFO] [INFO] Compiling 24 source files to
[jira] [Commented] (AMQ-4296) Unit tests fail intermittently when using LevelDB adapter
[ https://issues.apache.org/jira/browse/AMQ-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13581241#comment-13581241 ] Gary Tully commented on AMQ-4296: - adding failing org.apache.activemq.broker.region.cursors.StoreQueueCursorJournalNoDuplicateTest, but scenario where journal is used over a journaled pa is dubious. Unit tests fail intermittently when using LevelDB adapter - Key: AMQ-4296 URL: https://issues.apache.org/jira/browse/AMQ-4296 Project: ActiveMQ Issue Type: Bug Components: Test Cases Affects Versions: 5.8.0 Reporter: Timothy Bish Priority: Minor Fix For: 5.9.0 A couple of the unit tests that have be modified to run with LevelDB as the persistence adapter fail intermittently. AMQ2584Test#testSize DuranleSubscriptionOfflineTest#testConsumeOnlyMatchedMessages LevelDBXARecoveryBrokerTest#testTopicPersistentPreparedAcksAvailableAfterRestartAndRollback -- 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-4296) Unit tests fail intermittently when using LevelDB adapter
[ https://issues.apache.org/jira/browse/AMQ-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13581249#comment-13581249 ] Gary Tully commented on AMQ-4296: - org.apache.activemq.bugs.AMQ2149Test needs a leveldb variant, and will fail atm Unit tests fail intermittently when using LevelDB adapter - Key: AMQ-4296 URL: https://issues.apache.org/jira/browse/AMQ-4296 Project: ActiveMQ Issue Type: Bug Components: Test Cases Affects Versions: 5.8.0 Reporter: Timothy Bish Priority: Minor Fix For: 5.9.0 A couple of the unit tests that have be modified to run with LevelDB as the persistence adapter fail intermittently. AMQ2584Test#testSize DuranleSubscriptionOfflineTest#testConsumeOnlyMatchedMessages LevelDBXARecoveryBrokerTest#testTopicPersistentPreparedAcksAvailableAfterRestartAndRollback -- 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-4332) LargeQueueSparseDeleteTest gets timeouts on testMoveMessages and testRemoveMessages
Kevin Earls created AMQ-4332: Summary: LargeQueueSparseDeleteTest gets timeouts on testMoveMessages and testRemoveMessages Key: AMQ-4332 URL: https://issues.apache.org/jira/browse/AMQ-4332 Project: ActiveMQ Issue Type: Bug Components: Test Cases Reporter: Kevin Earls Priority: Minor Attachments: AMQ4332.patch Both of these test have 10 second timeouts, but while occasionally completing in 6-7 seconds, generally are averaging 10-12. I'll attach a patch which bumps up the timeouts, but if you want I can add a bug to look into a possible performance issue here. I ran these tests against the 5.7 fuse branch and they averaged 4-5 seconds. -- 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-4332) LargeQueueSparseDeleteTest gets timeouts on testMoveMessages and testRemoveMessages
[ https://issues.apache.org/jira/browse/AMQ-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Earls updated AMQ-4332: - Attachment: AMQ4332.patch LargeQueueSparseDeleteTest gets timeouts on testMoveMessages and testRemoveMessages --- Key: AMQ-4332 URL: https://issues.apache.org/jira/browse/AMQ-4332 Project: ActiveMQ Issue Type: Bug Components: Test Cases Reporter: Kevin Earls Priority: Minor Attachments: AMQ4332.patch Both of these test have 10 second timeouts, but while occasionally completing in 6-7 seconds, generally are averaging 10-12. I'll attach a patch which bumps up the timeouts, but if you want I can add a bug to look into a possible performance issue here. I ran these tests against the 5.7 fuse branch and they averaged 4-5 seconds. -- 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-4333) ActiveMQ 5.8: Failed to execute purge task
Ana Cortés created AMQ-4333: --- Summary: ActiveMQ 5.8: Failed to execute purge task Key: AMQ-4333 URL: https://issues.apache.org/jira/browse/AMQ-4333 Project: ActiveMQ Issue Type: Bug Reporter: Ana Cortés Fix For: 5.8.0 With a clean ActiveMQ 5.8 (without any queues), i can purge without any problem (./bin/activemq purge). But when i deploy my Camel application in the normal way (then ActiveMQ has now the queues of my application), i cannot purge anymore. I receive the next problem: ERROR: java.lang.RuntimeException: Failed to execute purge task. Reason: javax.management.ReflectionException: No such operation: purge java.lang.RuntimeException: Failed to execute purge task. Reason: javax.management.ReflectionException: No such operation: purge at org.apache.activemq.console.command.PurgeCommand.runTask(PurgeCommand.java:140) at org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:57) at org.apache.activemq.console.command.AbstractJmxCommand.execute(AbstractJmxCommand.java:387) at org.apache.activemq.console.command.ShellCommand.runTask(ShellCommand.java:150) at org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:57) at org.apache.activemq.console.command.ShellCommand.main(ShellCommand.java:104) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) Caused by: java.lang.NoSuchMethodException: purge() at com.sun.jmx.mbeanserver.PerInterface.noSuchMethod(PerInterface.java:150) at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:94) . See: http://activemq.2283324.n4.nabble.com/ActiveMQ-5-8-Failed-to-execute-purge-task-td4663610.html -- 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-4284) KahaDBSTore reset batching
[
https://issues.apache.org/jira/browse/AMQ-4284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13581258#comment-13581258
]
mauro rappa commented on AMQ-4284:
--
I didn't see the error anymore...no additional info to claim it's solved.
KahaDBSTore reset batching
--
Key: AMQ-4284
URL: https://issues.apache.org/jira/browse/AMQ-4284
Project: ActiveMQ
Issue Type: Bug
Components: Message Store
Affects Versions: 5.6.0
Reporter: mauro rappa
Labels: performance
I'm using apache-activemq-5.6.0 on Centos 6.3 with persistence configured as:
kahaDB directory=${activemq.data}/kahadb checksumJournalFiles=true
checkForCorruptJournalFiles=true cleanupInterval=1
journalMaxFileLength=64mb checkpointInterval=3000 maxAsyncJobs=1000
archiveDataLogs=false directoryArchive=${activemq.data}/kahadb/consumed/
all MQ instance is running on a SAN partition ( type ext4 option
rw,journal_ioprio=0,max_batch_time=5000,data=journal )
but during some load tests is saw few times this error:
2013-01-29 13:25:56,511 | ERROR | Failed to reset batching |
org.apache.activemq.store.kahadb.KahaDBStore | ActiveMQ ShutdownHook
java.lang.IllegalStateException: PageFile is not loaded
at org.apache.kahadb.page.PageFile.assertLoaded(PageFile.java:800)
at org.apache.kahadb.page.PageFile.tx(PageFile.java:294)
at
org.apache.activemq.store.kahadb.KahaDBStore$KahaDBMessageStore.resetBatching(KahaDBStore.java:575)
at
org.apache.activemq.store.ProxyMessageStore.resetBatching(ProxyMessageStore.java:111)
at
org.apache.activemq.broker.region.cursors.QueueStorePrefetch.resetBatch(QueueStorePrefetch.java:85)
at
org.apache.activemq.broker.region.cursors.AbstractStoreCursor.stop(AbstractStoreCursor.java:72)
at
org.apache.activemq.broker.region.cursors.StoreQueueCursor.stop(StoreQueueCursor.java:84)
at org.apache.activemq.broker.region.Queue.stop(Queue.java:909)
at
org.apache.activemq.broker.region.AbstractRegion.stop(AbstractRegion.java:118)
at
org.apache.activemq.util.ServiceStopper.stop(ServiceStopper.java:41)
at
org.apache.activemq.broker.region.RegionBroker.doStop(RegionBroker.java:713)
at
org.apache.activemq.broker.jmx.ManagedRegionBroker.doStop(ManagedRegionBroker.java:122)
at
org.apache.activemq.broker.region.RegionBroker.stop(RegionBroker.java:201)
at org.apache.activemq.broker.BrokerFilter.stop(BrokerFilter.java:161)
at org.apache.activemq.broker.BrokerFilter.stop(BrokerFilter.java:161)
at
org.apache.activemq.broker.TransactionBroker.stop(TransactionBroker.java:193)
at
org.apache.activemq.broker.BrokerService$3.stop(BrokerService.java:1961)
at
org.apache.activemq.util.ServiceStopper.stop(ServiceStopper.java:41)
at
org.apache.activemq.broker.BrokerService.stop(BrokerService.java:624)
at
org.apache.activemq.broker.BrokerService.containerShutdown(BrokerService.java:2162)
at
org.apache.activemq.broker.BrokerService$4.run(BrokerService.java:2129)
is it something known? any wrong tuning on my side?
--
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
what is the alternate for KahaPersistenceAdapter in 5.8
Hi, As KahaPersistenceAdapter class in Deprecated in 5.8, so what is the alternate for that one. Which class i have to use. Thanks, Ravi -- View this message in context: http://activemq.2283324.n4.nabble.com/what-is-the-alternate-for-KahaPersistenceAdapter-in-5-8-tp4663685.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
[jira] [Commented] (AMQ-4296) Unit tests fail intermittently when using LevelDB adapter
[ https://issues.apache.org/jira/browse/AMQ-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13581279#comment-13581279 ] Gary Tully commented on AMQ-4296: - also - org.apache.activemq.usecases.ThreeBrokerVirtualTopicNetworkAMQPATest Unit tests fail intermittently when using LevelDB adapter - Key: AMQ-4296 URL: https://issues.apache.org/jira/browse/AMQ-4296 Project: ActiveMQ Issue Type: Bug Components: Test Cases Affects Versions: 5.8.0 Reporter: Timothy Bish Priority: Minor Fix For: 5.9.0 A couple of the unit tests that have be modified to run with LevelDB as the persistence adapter fail intermittently. AMQ2584Test#testSize DuranleSubscriptionOfflineTest#testConsumeOnlyMatchedMessages LevelDBXARecoveryBrokerTest#testTopicPersistentPreparedAcksAvailableAfterRestartAndRollback -- 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] [Assigned] (AMQ-4000) Durable subscription not getting unregistered on networked broker
[ https://issues.apache.org/jira/browse/AMQ-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Posta reassigned AMQ-4000: Assignee: Christian Posta Durable subscription not getting unregistered on networked broker - Key: AMQ-4000 URL: https://issues.apache.org/jira/browse/AMQ-4000 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.6.0 Environment: network of brokers, durable topic subscriptions. Reporter: Torsten Mielke Assignee: Christian Posta Labels: durable_subscription, networks Attachments: JUnitTest.patch In a network of two brokers, a durable subscription is correctly propagated across to the remote broker. However when the consumer unsubscribes from the durable subscription again, it is only removed on the local broker but not on the remote broker. The remote broker keeps its durable subscription alive. As a consequence messages sent to the topic destination on the remote broker for which the durable subscriptions existed, are passed on to the local broker, although there is no active subscription on the local broker. The local broker will discard these msgs but unnecessary traffic has already occurred on the network bridge. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQCPP-464) Deadlock during normal task termination
[ https://issues.apache.org/jira/browse/AMQCPP-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Weaver updated AMQCPP-464: Attachment: CrashHang_Report__CMStressD.exe__02192013112259191.mht Made suggested change and can see thread 5 is AQS head which is waited on by thread 2 being joined by thread 0 in this new dump. Debugger is stopped on all threads in this state if you need further information. Deadlock during normal task termination --- Key: AMQCPP-464 URL: https://issues.apache.org/jira/browse/AMQCPP-464 Project: ActiveMQ C++ Client Issue Type: Bug Components: Decaf Affects Versions: 3.6.0 Environment: Windows XP VS2005 Reporter: Scott Weaver Assignee: Timothy Bish Priority: Critical Attachments: CrashHang_Report__CMStressD.exe__02182013132527878.mht, CrashHang_Report__CMStressD.exe__02192013112259191.mht Normal task termination hangs occasionally. -- 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-464) Deadlock during normal task termination
[ https://issues.apache.org/jira/browse/AMQCPP-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13581432#comment-13581432 ] Timothy Bish commented on AMQCPP-464: - Great thanks, will take a look when I have a chance. If you reproduce it again do the stack traces always look about the same? Deadlock during normal task termination --- Key: AMQCPP-464 URL: https://issues.apache.org/jira/browse/AMQCPP-464 Project: ActiveMQ C++ Client Issue Type: Bug Components: Decaf Affects Versions: 3.6.0 Environment: Windows XP VS2005 Reporter: Scott Weaver Assignee: Timothy Bish Priority: Critical Attachments: CrashHang_Report__CMStressD.exe__02182013132527878.mht, CrashHang_Report__CMStressD.exe__02192013112259191.mht Normal task termination hangs occasionally. -- 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-464) Deadlock during normal task termination
[ https://issues.apache.org/jira/browse/AMQCPP-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13581435#comment-13581435 ] Scott Weaver commented on AMQCPP-464: - Yes, stack traces appear to look the same so it appears to be a single issue. Good news is that this is created by attempting to recreate the termination access violation which appears to be fixed now. I will follow up with Helen to see if she is comfortable closing 459 now. Deadlock during normal task termination --- Key: AMQCPP-464 URL: https://issues.apache.org/jira/browse/AMQCPP-464 Project: ActiveMQ C++ Client Issue Type: Bug Components: Decaf Affects Versions: 3.6.0 Environment: Windows XP VS2005 Reporter: Scott Weaver Assignee: Timothy Bish Priority: Critical Attachments: CrashHang_Report__CMStressD.exe__02182013132527878.mht, CrashHang_Report__CMStressD.exe__02192013112259191.mht Normal task termination hangs occasionally. -- 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-464) Deadlock during normal task termination
[ https://issues.apache.org/jira/browse/AMQCPP-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13581438#comment-13581438 ] Scott Weaver commented on AMQCPP-464: - Furthermore, based upon the similarity of the dumps, my guess is that thread 6 in the first dump has the main lock. (Appears to consistently be the thread calling destroyThread.) Deadlock during normal task termination --- Key: AMQCPP-464 URL: https://issues.apache.org/jira/browse/AMQCPP-464 Project: ActiveMQ C++ Client Issue Type: Bug Components: Decaf Affects Versions: 3.6.0 Environment: Windows XP VS2005 Reporter: Scott Weaver Assignee: Timothy Bish Priority: Critical Attachments: CrashHang_Report__CMStressD.exe__02182013132527878.mht, CrashHang_Report__CMStressD.exe__02192013112259191.mht Normal task termination hangs occasionally. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Jenkins build is back to normal : ActiveMQ-Java7 » ActiveMQ :: MQTT Protocol #143
See https://builds.apache.org/job/ActiveMQ-Java7/org.apache.activemq$activemq-mqtt/143/
Jenkins build is unstable: ActiveMQ-Java7 #143
See https://builds.apache.org/job/ActiveMQ-Java7/143/changes
Re: what is the alternate for KahaPersistenceAdapter in 5.8
On 02/19/2013 06:07 AM, Ravindra wrote: Hi, As KahaPersistenceAdapter class in Deprecated in 5.8, so what is the alternate for that one. Which class i have to use. KahaDBPersistenceAdapter in activemq-kahadb-store is the default now. Thanks, Ravi -- View this message in context: http://activemq.2283324.n4.nabble.com/what-is-the-alternate-for-KahaPersistenceAdapter-in-5-8-tp4663685.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. -- Tim Bish Sr Software Engineer | RedHat Inc. tim.b...@redhat.com | www.fusesource.com | www.redhat.com skype: tabish121 | twitter: @tabish121 blog: http://timbish.blogspot.com/
[jira] [Commented] (AMQCPP-464) Deadlock during normal task termination
[ https://issues.apache.org/jira/browse/AMQCPP-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13581455#comment-13581455 ] Scott Weaver commented on AMQCPP-464: - Further information on second dump, thread 0 is attempting to join thread thread 2. Thread 2 is parked waiting on lock by thread 5. Thread 5 is attempting to join thread 7. Thread 7 is parked waiting on the same lock as thread 2 (held by thread 5). Therefore, it appears the issue is with threads 5 and 7. 5 is attempting a join with the lock that target thread 7 is waiting on. Deadlock during normal task termination --- Key: AMQCPP-464 URL: https://issues.apache.org/jira/browse/AMQCPP-464 Project: ActiveMQ C++ Client Issue Type: Bug Components: Decaf Affects Versions: 3.6.0 Environment: Windows XP VS2005 Reporter: Scott Weaver Assignee: Timothy Bish Priority: Critical Attachments: CrashHang_Report__CMStressD.exe__02182013132527878.mht, CrashHang_Report__CMStressD.exe__02192013112259191.mht Normal task termination hangs occasionally. -- 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-4334) Create SubqueueSelectorCacheBroker based on Infinispan for Network of brokers
Zacarias created AMQ-4334: - Summary: Create SubqueueSelectorCacheBroker based on Infinispan for Network of brokers Key: AMQ-4334 URL: https://issues.apache.org/jira/browse/AMQ-4334 Project: ActiveMQ Issue Type: Improvement Components: Broker Affects Versions: 5.8.0 Environment: Allow the SubqueueSelectorCacheBroker to persist selector information in a ISPN cache for concurrent nodes utilization. Extends issue https://issues.apache.org/jira/browse/AMQ-4271 Reporter: Zacarias Priority: Minor Fix For: NEEDS_REVIEWED -- 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-4334) Create SubqueueSelectorCacheBroker based on Infinispan for Network of brokers
[ https://issues.apache.org/jira/browse/AMQ-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zacarias updated AMQ-4334: -- Description: Allow the SubqueueSelectorCacheBroker to persist selector information in a ISPN cache for concurrent nodes utilization. Extends issue https://issues.apache.org/jira/browse/AMQ-4271 Create SubqueueSelectorCacheBroker based on Infinispan for Network of brokers - Key: AMQ-4334 URL: https://issues.apache.org/jira/browse/AMQ-4334 Project: ActiveMQ Issue Type: Improvement Components: Broker Affects Versions: 5.8.0 Environment: Allow the SubqueueSelectorCacheBroker to persist selector information in a ISPN cache for concurrent nodes utilization. Extends issue https://issues.apache.org/jira/browse/AMQ-4271 Reporter: Zacarias Priority: Minor Fix For: NEEDS_REVIEWED Allow the SubqueueSelectorCacheBroker to persist selector information in a ISPN cache for concurrent nodes utilization. Extends issue https://issues.apache.org/jira/browse/AMQ-4271 -- 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-4334) Create SubqueueSelectorCacheBroker based on Infinispan for Network of brokers
[ https://issues.apache.org/jira/browse/AMQ-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zacarias updated AMQ-4334: -- Environment: (was: Allow the SubqueueSelectorCacheBroker to persist selector information in a ISPN cache for concurrent nodes utilization. Extends issue https://issues.apache.org/jira/browse/AMQ-4271) Create SubqueueSelectorCacheBroker based on Infinispan for Network of brokers - Key: AMQ-4334 URL: https://issues.apache.org/jira/browse/AMQ-4334 Project: ActiveMQ Issue Type: Improvement Components: Broker Affects Versions: 5.8.0 Reporter: Zacarias Priority: Minor Fix For: NEEDS_REVIEWED Allow the SubqueueSelectorCacheBroker to persist selector information in a ISPN cache for concurrent nodes utilization. Extends issue https://issues.apache.org/jira/browse/AMQ-4271 -- 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-4334) Create SubqueueSelectorCacheBroker based on Infinispan for Network of brokers
[ https://issues.apache.org/jira/browse/AMQ-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zacarias updated AMQ-4334: -- Description: Allow the SubqueueSelectorCacheBroker to persist selector information in a ISPN cache for concurrent nodes utilization. Extends issue https://issues.apache.org/jira/browse/AMQ-4271 Current version just allow a file serialization of the information. was: Allow the SubqueueSelectorCacheBroker to persist selector information in a ISPN cache for concurrent nodes utilization. Extends issue https://issues.apache.org/jira/browse/AMQ-4271 Create SubqueueSelectorCacheBroker based on Infinispan for Network of brokers - Key: AMQ-4334 URL: https://issues.apache.org/jira/browse/AMQ-4334 Project: ActiveMQ Issue Type: Improvement Components: Broker Affects Versions: 5.8.0 Reporter: Zacarias Priority: Minor Fix For: NEEDS_REVIEWED Allow the SubqueueSelectorCacheBroker to persist selector information in a ISPN cache for concurrent nodes utilization. Extends issue https://issues.apache.org/jira/browse/AMQ-4271 Current version just allow a file serialization of the information. -- 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-464) Deadlock during normal task termination
[ https://issues.apache.org/jira/browse/AMQCPP-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13581586#comment-13581586 ] Timothy Bish commented on AMQCPP-464: - New SNAPSHOT posted which hopefully resolves this. Thanks for the analysis help. Deadlock during normal task termination --- Key: AMQCPP-464 URL: https://issues.apache.org/jira/browse/AMQCPP-464 Project: ActiveMQ C++ Client Issue Type: Bug Components: Decaf Affects Versions: 3.6.0 Environment: Windows XP VS2005 Reporter: Scott Weaver Assignee: Timothy Bish Priority: Critical Attachments: CrashHang_Report__CMStressD.exe__02182013132527878.mht, CrashHang_Report__CMStressD.exe__02192013112259191.mht Normal task termination hangs occasionally. -- 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-464) Deadlock during normal task termination
[ https://issues.apache.org/jira/browse/AMQCPP-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13581650#comment-13581650 ] Scott Weaver commented on AMQCPP-464: - Testing now and looks good so far. Assuming our overnight tests run successfully, how long before you submit this as 3.6.0? I see you are still doing failover work. Will this be completed shortly? We will still have to test whatever you release one more time assuming there are more changes. Thanks for all your efforts in quickly resolving these issues. Deadlock during normal task termination --- Key: AMQCPP-464 URL: https://issues.apache.org/jira/browse/AMQCPP-464 Project: ActiveMQ C++ Client Issue Type: Bug Components: Decaf Affects Versions: 3.6.0 Environment: Windows XP VS2005 Reporter: Scott Weaver Assignee: Timothy Bish Priority: Critical Attachments: CrashHang_Report__CMStressD.exe__02182013132527878.mht, CrashHang_Report__CMStressD.exe__02192013112259191.mht Normal task termination hangs occasionally. -- 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-459) Found an access violation in NodePool::ReturNode(Node* node)
[ https://issues.apache.org/jira/browse/AMQCPP-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13581659#comment-13581659 ] Helen Huang commented on AMQCPP-459: Thanks a lot for the fix! I can no longer recreate the issue after getting the latest 3.6 snapshot (uploaded on 15/Feb/13). Found an access violation in NodePool::ReturNode(Node* node) Key: AMQCPP-459 URL: https://issues.apache.org/jira/browse/AMQCPP-459 Project: ActiveMQ C++ Client Issue Type: Bug Components: CMS Impl Affects Versions: 3.5.0 Environment: Windows xp service pack 3, ActiveMQ broker 5.3.1, apr 1.4.2, apr-util 1.3.9, apr iconv 1.2.1 Reporter: Helen Huang Assignee: Timothy Bish Priority: Critical Fix For: 3.6.0 Attachments: CMStress.zip, CrashHang_Report__CMStressUD.exe__02142013143459322.mht Caught an access violation in NodePool::ReturNode(Node* node) The following is the call stack: activemq-cppud.dll!`anonymous namespace'::NodePool::returnNode(`anonymous-namespace'::Node * node=0x05237488) Line 311 + 0x6 bytes activemq-cppud.dll!decaf::util::concurrent::locks::DefaultConditionObject::unlinkCancelledWaiters() Line 1450 activemq-cppud.dll!decaf::util::concurrent::locks::DefaultConditionObject::await() Line 1145 CmsMessageHandlerCOMUD.dll!decaf::util::concurrent::LinkedBlockingQueuedecaf::lang::Runnable *::take() Line 435 + 0x32 bytes activemq-cppud.dll!decaf::util::concurrent::ExecutorKernel::getTask() Line 1288 + 0x24 bytes activemq-cppud.dll!decaf::util::concurrent::ExecutorKernel::runWorker(decaf::util::concurrent::ExecutorKernel::Worker * w=0x052359b8) Line 720 + 0xe bytes activemq-cppud.dll!decaf::util::concurrent::ExecutorKernel::Worker::run() Line 184 activemq-cppud.dll!decaf::lang::Thread::run() Line 143 activemq-cppud.dll!`anonymous namespace'::runCallback(void * arg=0x0523a690) Line 262 + 0x11 bytes activemq-cppud.dll!`anonymous namespace'::threadEntryMethod(void * arg=0x0523a690) Line 250 + 0x15 bytes msvcr80d.dll!_callthreadstartex() Line 348 + 0xf bytes msvcr80d.dll!_threadstartex(void * ptd=0x0523ab30) Line 331 kernel32.dll!7c80b729() -- 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-464) Deadlock during normal task termination
[ https://issues.apache.org/jira/browse/AMQCPP-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13581660#comment-13581660 ] Timothy Bish commented on AMQCPP-464: - Failover work is basically done aside from some additional unit tests that I'd like to add. Some other small cleanup work and tests. If we can get the current code base stable then I'd try and get that out as v3.6.0 without many more changes as it should represent a fairly robust release thanks to your groups hard work in testing and reporting problems. Deadlock during normal task termination --- Key: AMQCPP-464 URL: https://issues.apache.org/jira/browse/AMQCPP-464 Project: ActiveMQ C++ Client Issue Type: Bug Components: Decaf Affects Versions: 3.6.0 Environment: Windows XP VS2005 Reporter: Scott Weaver Assignee: Timothy Bish Priority: Critical Attachments: CrashHang_Report__CMStressD.exe__02182013132527878.mht, CrashHang_Report__CMStressD.exe__02192013112259191.mht Normal task termination hangs occasionally. -- 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] [Closed] (AMQCPP-459) Found an access violation in NodePool::ReturNode(Node* node)
[ https://issues.apache.org/jira/browse/AMQCPP-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Helen Huang closed AMQCPP-459. -- Resolution: Fixed Found an access violation in NodePool::ReturNode(Node* node) Key: AMQCPP-459 URL: https://issues.apache.org/jira/browse/AMQCPP-459 Project: ActiveMQ C++ Client Issue Type: Bug Components: CMS Impl Affects Versions: 3.5.0 Environment: Windows xp service pack 3, ActiveMQ broker 5.3.1, apr 1.4.2, apr-util 1.3.9, apr iconv 1.2.1 Reporter: Helen Huang Assignee: Timothy Bish Priority: Critical Fix For: 3.6.0 Attachments: CMStress.zip, CrashHang_Report__CMStressUD.exe__02142013143459322.mht Caught an access violation in NodePool::ReturNode(Node* node) The following is the call stack: activemq-cppud.dll!`anonymous namespace'::NodePool::returnNode(`anonymous-namespace'::Node * node=0x05237488) Line 311 + 0x6 bytes activemq-cppud.dll!decaf::util::concurrent::locks::DefaultConditionObject::unlinkCancelledWaiters() Line 1450 activemq-cppud.dll!decaf::util::concurrent::locks::DefaultConditionObject::await() Line 1145 CmsMessageHandlerCOMUD.dll!decaf::util::concurrent::LinkedBlockingQueuedecaf::lang::Runnable *::take() Line 435 + 0x32 bytes activemq-cppud.dll!decaf::util::concurrent::ExecutorKernel::getTask() Line 1288 + 0x24 bytes activemq-cppud.dll!decaf::util::concurrent::ExecutorKernel::runWorker(decaf::util::concurrent::ExecutorKernel::Worker * w=0x052359b8) Line 720 + 0xe bytes activemq-cppud.dll!decaf::util::concurrent::ExecutorKernel::Worker::run() Line 184 activemq-cppud.dll!decaf::lang::Thread::run() Line 143 activemq-cppud.dll!`anonymous namespace'::runCallback(void * arg=0x0523a690) Line 262 + 0x11 bytes activemq-cppud.dll!`anonymous namespace'::threadEntryMethod(void * arg=0x0523a690) Line 250 + 0x15 bytes msvcr80d.dll!_callthreadstartex() Line 348 + 0xf bytes msvcr80d.dll!_threadstartex(void * ptd=0x0523ab30) Line 331 kernel32.dll!7c80b729() -- 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-4334) Create SubqueueSelectorCacheBroker based on Infinispan for Network of brokers
[ https://issues.apache.org/jira/browse/AMQ-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13581672#comment-13581672 ] Zacarias commented on AMQ-4334: --- I would like to have an schema like this plugins virtualSelectorCacheBrokerPlugin cacheProvider fileCacheProvider persistFile = selectorcache.data/ /cacheProvider /virtualSelectorCacheBrokerPlugin /plugins plugins virtualSelectorCacheBrokerPlugin cacheProvider ispnCacheProvider configFile=/ /cacheProvider /virtualSelectorCacheBrokerPlugin /plugins Create SubqueueSelectorCacheBroker based on Infinispan for Network of brokers - Key: AMQ-4334 URL: https://issues.apache.org/jira/browse/AMQ-4334 Project: ActiveMQ Issue Type: Improvement Components: Broker Affects Versions: 5.8.0 Reporter: Zacarias Priority: Minor Fix For: NEEDS_REVIEWED Allow the SubqueueSelectorCacheBroker to persist selector information in a ISPN cache for concurrent nodes utilization. Extends issue https://issues.apache.org/jira/browse/AMQ-4271 Current version just allow a file serialization of the information. -- 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-4335) Cannot set maxFrameSize greater than 100MB
Pat Flaherty created AMQ-4335: - Summary: Cannot set maxFrameSize greater than 100MB Key: AMQ-4335 URL: https://issues.apache.org/jira/browse/AMQ-4335 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.8.0 Environment: Windows 2008 R2 Reporter: Pat Flaherty Trying to send JSON messages greater then 100MB and I receive the error: Transport Connection to: tcp://192.168.10.1:55823 failed: java.io.IOException: Frame size of 140 MB larger than max allowed 100 MB I tried increasing the frame size in 5.8.0 as follows: transportConnectors !-- DOS protection, limit concurrent connections to 1000 and frame size to 100MB -- transportConnector name=openwire uri=tcp://192.168.10.1:61616?maximumConnections=1000amp;wireformat.maxFrameSize=157286400/ transportConnector name=amqp uri=amqp://0.0.0.0:5672?maximumConnections=1000amp;wireformat.maxFrameSize=157286400/ /transportConnectors -- 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] (AMQNET-414) Exception thrown when using DTC in multiple processes connected to the same broker
Remo Gloor created AMQNET-414: - Summary: Exception thrown when using DTC in multiple processes connected to the same broker Key: AMQNET-414 URL: https://issues.apache.org/jira/browse/AMQNET-414 Project: ActiveMQ .Net Issue Type: Bug Reporter: Remo Gloor Assignee: Jim Gomes Priority: Critical When using DTC in multiple processes that access the same broker instance all but the first instance can't enlist to the transaction. All other throw an exception that there is already a resource manager with the same id. This only happens in case another resource manager like a db server is enlisted on the transaction. This happens because they all processes connected to one broker instance use the same resource manager ID. It is a Guid generated from the broker id. I doubt that there is any good ID that is unique to the process instance but still the same on restart (e.g. connection/client id change on reboot). Is there any other? If not the resource manager id has be configurable somehow by the application. An other option (the one that should be prefered) is to enlist as promotable single phase enlistment. But this would require that the ActiveMQ server is responsible for the transaction as soon as it gets promoted. This would require changes in the server itsself though but make the system much more robust. http://msdn.microsoft.com/en-us/library/ms229980(v=vs.80).aspx -- 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] (AMQNET-414) Exception thrown when using DTC in multiple processes connected to the same broker
[ https://issues.apache.org/jira/browse/AMQNET-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13581758#comment-13581758 ] Timothy Bish commented on AMQNET-414: - I doubt anyone is going to want to change the JMS broker to make it more .NET / Microsoft friendly. Exception thrown when using DTC in multiple processes connected to the same broker -- Key: AMQNET-414 URL: https://issues.apache.org/jira/browse/AMQNET-414 Project: ActiveMQ .Net Issue Type: Bug Reporter: Remo Gloor Assignee: Jim Gomes When using DTC in multiple processes that access the same broker instance all but the first instance can't enlist to the transaction. All other throw an exception that there is already a resource manager with the same id. This only happens in case another resource manager like a db server is enlisted on the transaction. This happens because they all processes connected to one broker instance use the same resource manager ID. It is a Guid generated from the broker id. I doubt that there is any good ID that is unique to the process instance but still the same on restart (e.g. connection/client id change on reboot). Is there any other? If not the resource manager id has be configurable somehow by the application. An other option (the one that should be prefered) is to enlist as promotable single phase enlistment. But this would require that the ActiveMQ server is responsible for the transaction as soon as it gets promoted. This would require changes in the server itsself though but make the system much more robust. http://msdn.microsoft.com/en-us/library/ms229980(v=vs.80).aspx -- 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] (AMQNET-414) Exception thrown when using DTC in multiple processes connected to the same broker
[ https://issues.apache.org/jira/browse/AMQNET-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQNET-414: Priority: Major (was: Critical) Exception thrown when using DTC in multiple processes connected to the same broker -- Key: AMQNET-414 URL: https://issues.apache.org/jira/browse/AMQNET-414 Project: ActiveMQ .Net Issue Type: Bug Reporter: Remo Gloor Assignee: Jim Gomes When using DTC in multiple processes that access the same broker instance all but the first instance can't enlist to the transaction. All other throw an exception that there is already a resource manager with the same id. This only happens in case another resource manager like a db server is enlisted on the transaction. This happens because they all processes connected to one broker instance use the same resource manager ID. It is a Guid generated from the broker id. I doubt that there is any good ID that is unique to the process instance but still the same on restart (e.g. connection/client id change on reboot). Is there any other? If not the resource manager id has be configurable somehow by the application. An other option (the one that should be prefered) is to enlist as promotable single phase enlistment. But this would require that the ActiveMQ server is responsible for the transaction as soon as it gets promoted. This would require changes in the server itsself though but make the system much more robust. http://msdn.microsoft.com/en-us/library/ms229980(v=vs.80).aspx -- 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
ConnectionFailedException with ActiveMQ 5.6, Camel2.10, JBoss5.1
Hello All, Since last week we have been facing issue while consuming messages from Active MQs. Here is the snapshot of the environment.JBoss 5.1 Camel 2.10.0 Spring 3.1.2.Release activemq-all 5.6.0 (Run time Active MQ Broker version apache-activemq-5.7.0)Below is the server stacktrace :org.apache.activemq.ConnectionFailedException: The JMS connection has failed: java.io.EOFException at org.springframework.jms.support.JmsUtils.convertJmsAccessException(JmsUtils.java:316) at org.springframework.jms.support.JmsAccessor.convertJmsAccessException(JmsAccessor.java:168) at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:469) at org.springframework.jms.core.JmsTemplate.send(JmsTemplate.java:543) at org.springframework.jms.core.JmsTemplate.convertAndSend(JmsTemplate.java:620) at org.common.JmsTemplateComponent$JmsTemplateProcessor.process(JmsTemplateComponent.java:140) at org.apache.camel.impl.ProcessorEndpoint.onExchange(ProcessorEndpoint.java:101) at org.apache.camel.impl.ProcessorEndpoint$1.process(ProcessorEndpoint.java:71) at org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.SendProcessor$2.doInAsyncProducer(SendProcessor.java:120) at org.apache.camel.impl.ProducerCache.doInAsyncProducer(ProducerCache.java:292) at org.apache.camel.processor.SendProcessor.process(SendProcessor.java:115) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:73) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:91) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.RedeliveryErrorHandler.processErrorHandler(RedeliveryErrorHandler.java:330) at org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:220) at org.apache.camel.processor.RouteContextProcessor.processNext(RouteContextProcessor.java:45) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.processor.interceptor.DefaultChannel.process(DefaultChannel.java:303) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.Pipeline.process(Pipeline.java:117) at org.apache.camel.processor.Pipeline.process(Pipeline.java:80) at org.apache.camel.processor.RouteContextProcessor.processNext(RouteContextProcessor.java:45) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.processor.UnitOfWorkProcessor.processAsync(UnitOfWorkProcessor.java:150) at org.apache.camel.processor.UnitOfWorkProcessor.process(UnitOfWorkProcessor.java:117) at org.apache.camel.processor.RouteInflightRepositoryProcessor.processNext(RouteInflightRepositoryProcessor.java:48) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:73) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:99) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:86) at org.apache.camel.component.timer.TimerConsumer.sendTimerExchange(TimerConsumer.java:134) at org.apache.camel.component.timer.TimerConsumer$1.run(TimerConsumer.java:63) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) Caused by: org.apache.activemq.ConnectionFailedException: The JMS connection has failed: java.io.EOFException at org.apache.activemq.ActiveMQConnection.checkClosedOrFailed(ActiveMQConnection.java:1436) at org.apache.activemq.ActiveMQConnection.createSession(ActiveMQConnection.java:307) at sun.reflect.GeneratedMethodAccessor1545.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at
Jenkins build is back to stable : ActiveMQ » ActiveMQ :: KahaDB Store #1228
See https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-kahadb-store/1228/
Build failed in Jenkins: ActiveMQ #1228
See https://builds.apache.org/job/ActiveMQ/1228/changes Changes: [gtully] more exclusions - https://issues.apache.org/jira/browse/AMQ-4296 [gtully] https://issues.apache.org/jira/browse/AMQ-4328 - regression in AMQ3274Test, need to sync demand sub creation on async vm transport [gtully] another leveldb scenario needing work - https://issues.apache.org/jira/browse/AMQ-4296 [gtully] another leveldb scenario that needs some investigation, but use case seems dubious - https://issues.apache.org/jira/browse/AMQ-4296 -- [...truncated 5543 lines...] [INFO] --- ianal-maven-plugin:1.0-alpha-1:verify-legal-files (default) @ activemq-broker --- [INFO] [INFO] Installing https://builds.apache.org/job/ActiveMQ/ws/activemq-broker/target/activemq-broker-5.9-SNAPSHOT.jar to /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/activemq/activemq-broker/5.9-SNAPSHOT/activemq-broker-5.9-SNAPSHOT.jar [INFO] Installing https://builds.apache.org/job/ActiveMQ/ws/activemq-broker/pom.xml to /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/activemq/activemq-broker/5.9-SNAPSHOT/activemq-broker-5.9-SNAPSHOT.pom [INFO] Installing https://builds.apache.org/job/ActiveMQ/ws/activemq-broker/target/activemq-broker-5.9-SNAPSHOT-tests.jar to /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/activemq/activemq-broker/5.9-SNAPSHOT/activemq-broker-5.9-SNAPSHOT-tests.jar [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ activemq-broker --- [INFO] [INFO] --- maven-enforcer-plugin:1.0.1:enforce (default) @ activemq-broker --- [INFO] [INFO] --- maven-bundle-plugin:2.3.7:cleanVersions (cleanVersions) @ activemq-broker --- Feb 20, 2013 3:57:27 AM hudson.maven.ExecutedMojo init WARNING: Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo [INFO] [INFO] --- maven-source-plugin:2.1.2:jar (default-cli) @ activemq-broker --- [INFO] META-INF already added, skipping [INFO] META-INF already added, skipping [INFO] META-INF/NOTICE already added, skipping [INFO] META-INF/DEPENDENCIES already added, skipping [INFO] META-INF/LICENSE already added, skipping [INFO] Building jar: https://builds.apache.org/job/ActiveMQ/ws/activemq-broker/target/activemq-broker-5.9-SNAPSHOT-sources.jar [INFO] META-INF already added, skipping [INFO] META-INF already added, skipping [INFO] META-INF/NOTICE already added, skipping [INFO] META-INF/DEPENDENCIES already added, skipping [INFO] META-INF/LICENSE already added, skipping [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 [INFO] [INFO] Building ActiveMQ :: KahaDB Store 5.9-SNAPSHOT [INFO] Downloading: http://repo.fusesource.com/nexus/content/groups/public/com/thoughtworks/xstream/xstream/1.4.4/xstream-1.4.4.pom Downloading: http://repo.maven.apache.org/maven2/com/thoughtworks/xstream/xstream/1.4.4/xstream-1.4.4.pom Downloaded: http://repo.maven.apache.org/maven2/com/thoughtworks/xstream/xstream/1.4.4/xstream-1.4.4.pom (9 KB at 107.5 KB/sec) Downloading: http://repo.fusesource.com/nexus/content/groups/public/com/thoughtworks/xstream/xstream-parent/1.4.4/xstream-parent-1.4.4.pom Downloading: http://repo.maven.apache.org/maven2/com/thoughtworks/xstream/xstream-parent/1.4.4/xstream-parent-1.4.4.pom Downloaded: http://repo.maven.apache.org/maven2/com/thoughtworks/xstream/xstream-parent/1.4.4/xstream-parent-1.4.4.pom (19 KB at 89.6 KB/sec) Downloading: http://repo.fusesource.com/nexus/content/groups/public/com/thoughtworks/xstream/xstream/1.4.4/xstream-1.4.4.jar Downloading: http://repo.maven.apache.org/maven2/com/thoughtworks/xstream/xstream/1.4.4/xstream-1.4.4.jar Downloaded: http://repo.maven.apache.org/maven2/com/thoughtworks/xstream/xstream/1.4.4/xstream-1.4.4.jar (473 KB at 2314.3 KB/sec) [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ activemq-kahadb-store --- [INFO] [INFO] --- maven-enforcer-plugin:1.0.1:enforce (default) @ activemq-kahadb-store --- [INFO] [INFO] --- maven-bundle-plugin:2.3.7:cleanVersions (cleanVersions) @ activemq-kahadb-store --- [INFO] [INFO] Compiling: https://builds.apache.org/job/ActiveMQ/ws/activemq-kahadb-store/src/main/proto/journal-data.proto [INFO] --- activemq-protobuf:1.1:compile (default) @
Re:ConnectionFailedException with ActiveMQ 5.6, Camel2.10, JBoss5.1
Seems the connection is closed by broker and you still use the broken connection. You can use FailoverTransport[1] to handle this situation. [1]http://activemq.apache.org/failover-transport-reference.html At 2013-02-20 11:53:51,nakshathri manjunath...@happiestminds.com wrote: Hello All, Since last week we have been facing issue while consuming messages from Active MQs. Here is the snapshot of the environment.JBoss 5.1 Camel 2.10.0 Spring 3.1.2.Release activemq-all 5.6.0 (Run time Active MQ Broker version apache-activemq-5.7.0)Below is the server stacktrace :org.apache.activemq.ConnectionFailedException: The JMS connection has failed: java.io.EOFException at org.springframework.jms.support.JmsUtils.convertJmsAccessException(JmsUtils.java:316) at org.springframework.jms.support.JmsAccessor.convertJmsAccessException(JmsAccessor.java:168) at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:469) at org.springframework.jms.core.JmsTemplate.send(JmsTemplate.java:543) at org.springframework.jms.core.JmsTemplate.convertAndSend(JmsTemplate.java:620) at org.common.JmsTemplateComponent$JmsTemplateProcessor.process(JmsTemplateComponent.java:140) at org.apache.camel.impl.ProcessorEndpoint.onExchange(ProcessorEndpoint.java:101) at org.apache.camel.impl.ProcessorEndpoint$1.process(ProcessorEndpoint.java:71) at org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.SendProcessor$2.doInAsyncProducer(SendProcessor.java:120) at org.apache.camel.impl.ProducerCache.doInAsyncProducer(ProducerCache.java:292) at org.apache.camel.processor.SendProcessor.process(SendProcessor.java:115) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:73) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:91) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.RedeliveryErrorHandler.processErrorHandler(RedeliveryErrorHandler.java:330) at org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:220) at org.apache.camel.processor.RouteContextProcessor.processNext(RouteContextProcessor.java:45) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.processor.interceptor.DefaultChannel.process(DefaultChannel.java:303) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.Pipeline.process(Pipeline.java:117) at org.apache.camel.processor.Pipeline.process(Pipeline.java:80) at org.apache.camel.processor.RouteContextProcessor.processNext(RouteContextProcessor.java:45) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.processor.UnitOfWorkProcessor.processAsync(UnitOfWorkProcessor.java:150) at org.apache.camel.processor.UnitOfWorkProcessor.process(UnitOfWorkProcessor.java:117) at org.apache.camel.processor.RouteInflightRepositoryProcessor.processNext(RouteInflightRepositoryProcessor.java:48) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:73) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:99) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:86) at org.apache.camel.component.timer.TimerConsumer.sendTimerExchange(TimerConsumer.java:134) at org.apache.camel.component.timer.TimerConsumer$1.run(TimerConsumer.java:63) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) Caused by: org.apache.activemq.ConnectionFailedException: The JMS connection has failed: java.io.EOFException at org.apache.activemq.ActiveMQConnection.checkClosedOrFailed(ActiveMQConnection.java:1436) at org.apache.activemq.ActiveMQConnection.createSession(ActiveMQConnection.java:307) at
Re: ConnectionFailedException with ActiveMQ 5.6, Camel2.10, JBoss5.1
You have a single connection factory and no failover I guess? Try a failover URL and look at the RA adapters I think they are pooling. On Feb 19, 2013, at 20:53, nakshathri manjunath...@happiestminds.com wrote: Hello All, Since last week we have been facing issue while consuming messages from Active MQs. Here is the snapshot of the environment.JBoss 5.1 Camel 2.10.0 Spring 3.1.2.Release activemq-all 5.6.0 (Run time Active MQ Broker version apache-activemq-5.7.0)Below is the server stacktrace :org.apache.activemq.ConnectionFailedException: The JMS connection has failed: java.io.EOFException at org.springframework.jms.support.JmsUtils.convertJmsAccessException(JmsUtils.java:316) at org.springframework.jms.support.JmsAccessor.convertJmsAccessException(JmsAccessor.java:168) at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:469) at org.springframework.jms.core.JmsTemplate.send(JmsTemplate.java:543) at org.springframework.jms.core.JmsTemplate.convertAndSend(JmsTemplate.java:620) at org.common.JmsTemplateComponent$JmsTemplateProcessor.process(JmsTemplateComponent.java:140) at org.apache.camel.impl.ProcessorEndpoint.onExchange(ProcessorEndpoint.java:101) at org.apache.camel.impl.ProcessorEndpoint$1.process(ProcessorEndpoint.java:71) at org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.SendProcessor$2.doInAsyncProducer(SendProcessor.java:120) at org.apache.camel.impl.ProducerCache.doInAsyncProducer(ProducerCache.java:292) at org.apache.camel.processor.SendProcessor.process(SendProcessor.java:115) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:73) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:91) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.RedeliveryErrorHandler.processErrorHandler(RedeliveryErrorHandler.java:330) at org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:220) at org.apache.camel.processor.RouteContextProcessor.processNext(RouteContextProcessor.java:45) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.processor.interceptor.DefaultChannel.process(DefaultChannel.java:303) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.Pipeline.process(Pipeline.java:117) at org.apache.camel.processor.Pipeline.process(Pipeline.java:80) at org.apache.camel.processor.RouteContextProcessor.processNext(RouteContextProcessor.java:45) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.processor.UnitOfWorkProcessor.processAsync(UnitOfWorkProcessor.java:150) at org.apache.camel.processor.UnitOfWorkProcessor.process(UnitOfWorkProcessor.java:117) at org.apache.camel.processor.RouteInflightRepositoryProcessor.processNext(RouteInflightRepositoryProcessor.java:48) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:73) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:99) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:86) at org.apache.camel.component.timer.TimerConsumer.sendTimerExchange(TimerConsumer.java:134) at org.apache.camel.component.timer.TimerConsumer$1.run(TimerConsumer.java:63) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) Caused by: org.apache.activemq.ConnectionFailedException: The JMS connection has failed: java.io.EOFException at org.apache.activemq.ActiveMQConnection.checkClosedOrFailed(ActiveMQConnection.java:1436) at
Jenkins build is back to normal : ActiveMQ-Trunk-Deploy » ActiveMQ :: LevelDB Store #723
See https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq$activemq-leveldb-store/723/
Jenkins build is back to normal : ActiveMQ-Trunk-Deploy #723
See https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/723/changes
Re: what is the alternate for KahaPersistenceAdapter in 5.8
Hi,
Thanks for Given response.
My next question is that how we can change class name in Master.xml from
KahaPersistenceAdapter to KahaDBPersistenceAdapter. it not allowing to
change value to KahaDBPersistenceAdapter.
example
amq:persistenceAdapter
amq:kahaPersistenceAdapter
directory=${activemq.broker.datadir}
/
/amq:persistenceAdapter
XSD is not supporting KahaDBPersistenceAdapter.
so XSD in not changed according to new KahaDBPersistenceAdapter value in
5.8?
Or we have any other way to change this value.
Thanks,
Ravindra
--
View this message in context:
http://activemq.2283324.n4.nabble.com/what-is-the-alternate-for-KahaPersistenceAdapter-in-5-8-tp4663685p4663764.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
