[jira] [Commented] (AMQ-6147) AMQP: Update Proton-J to 0.12.0
[ https://issues.apache.org/jira/browse/AMQ-6147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15165675#comment-15165675 ] Timothy Bish commented on AMQ-6147: --- Having reviewed the code the problem with the failing test is due to the order of events and how we handle the prefetch value reduction. The current implementation is actually a bit simpler than what we would need if the use the option to not emit flows on send so it's probably better to just leave it as it is currently implemented so that we don't introduce new breakages. > AMQP: Update Proton-J to 0.12.0 > --- > > Key: AMQ-6147 > URL: https://issues.apache.org/jira/browse/AMQ-6147 > Project: ActiveMQ > Issue Type: Improvement > Components: AMQP >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Minor > Fix For: 5.14.0, 5.13.2 > > Attachments: AMQ-6147.patch > > > Update proton to latest version -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMQ-6183) Provide the DispatchAsync value on Subscriptions to the SubscriptionViewMBean
[ https://issues.apache.org/jira/browse/AMQ-6183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-6183. --- Resolution: Fixed > Provide the DispatchAsync value on Subscriptions to the SubscriptionViewMBean > - > > Key: AMQ-6183 > URL: https://issues.apache.org/jira/browse/AMQ-6183 > Project: ActiveMQ > Issue Type: Bug > Components: JMX >Affects Versions: 5.13.0, 5.13.1, 5.12.3 >Reporter: Timothy Bish >Assignee: Timothy Bish >Priority: Trivial > Fix For: 5.14.0 > > > The SubscriptionVewMBean does not expose the dispatchAsync property from a > consumer. > The ProducerViewMBean does expose a dispatchAsync value from a producer which > is never used and leads to some confusion. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMQ-6183) Provide the DispatchAsync value on Subscriptions to the SubscriptionViewMBean
[ https://issues.apache.org/jira/browse/AMQ-6183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163927#comment-15163927 ] ASF subversion and git services commented on AMQ-6183: -- Commit c2ad0c32512e5265fa5482a0e49aa13f359acb8f in activemq's branch refs/heads/master from [~tabish121] [ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=c2ad0c3 ] AMQ-6183 Add isDispatchSync to the subscription view and deprecate the meaningless one in the producer view > Provide the DispatchAsync value on Subscriptions to the SubscriptionViewMBean > - > > Key: AMQ-6183 > URL: https://issues.apache.org/jira/browse/AMQ-6183 > Project: ActiveMQ > Issue Type: Bug > Components: JMX >Affects Versions: 5.13.0, 5.13.1, 5.12.3 >Reporter: Timothy Bish >Assignee: Timothy Bish >Priority: Trivial > Fix For: 5.14.0 > > > The SubscriptionVewMBean does not expose the dispatchAsync property from a > consumer. > The ProducerViewMBean does expose a dispatchAsync value from a producer which > is never used and leads to some confusion. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMQ-6183) Provide the DispatchAsync value on Subscriptions to the SubscriptionViewMBean
Timothy Bish created AMQ-6183: - Summary: Provide the DispatchAsync value on Subscriptions to the SubscriptionViewMBean Key: AMQ-6183 URL: https://issues.apache.org/jira/browse/AMQ-6183 Project: ActiveMQ Issue Type: Bug Components: JMX Affects Versions: 5.12.3, 5.13.1, 5.13.0 Reporter: Timothy Bish Assignee: Timothy Bish Priority: Trivial Fix For: 5.14.0 The SubscriptionVewMBean does not expose the dispatchAsync property from a consumer. The ProducerViewMBean does expose a dispatchAsync value from a producer which is never used and leads to some confusion. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMQ-6163) ActiveMQ creates a new empty KahaDB
[ https://issues.apache.org/jira/browse/AMQ-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163756#comment-15163756 ] Björn Paulsen commented on AMQ-6163: Yes, there are entries for 127.0.0.1 in /etc/hosts But this is wrong, the folder name should be the broker name, or the folder which is configured: this should create activemq-data/SOMENAME/KahaDB/ Or a persistenceAdapter say the directory In both cases it never should be activemq-data/127.0.0.1/KahaDB > ActiveMQ creates a new empty KahaDB > --- > > Key: AMQ-6163 > URL: https://issues.apache.org/jira/browse/AMQ-6163 > Project: ActiveMQ > Issue Type: Bug > Components: activemq-camel >Affects Versions: 5.13.0 > Environment: Windows 10, Eclipse >Reporter: Björn Paulsen > Attachments: AllInOneBoilerBug.zip > > > Hello Together, > I want create a JVM with Camel and ActiveMQ inside. > I create in Eclipse a new Spring configuration. It works, but when I open the > ActiveMQ Managment Website and look on the Queue Detail Page, where should > list all Messages, ActiveMQ creates a new empty KahaDB in the Directory > activemq-data and read from there, so no Messages are show. When I go back on > Queue List i see the right count of messages. > I ask on Nabble about the Problem, but there couldn't help me anybody. So I > think this is not a configuration error, this should be a bug. > http://activemq.2283324.n4.nabble.com/ActiveMQ-KahaDB-Directory-td4706593.html > I have a example Eclipse Project where you can see the error, but I couldn't > upload this here, so I do it on file-upload.net > http://www.file-upload.net/download-11292082/AllInOneBoilerBug.zip.html > I hope this could help. > Thank you very much -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ARTEMIS-359) [TestSuite] IBM JDK does not allow to instrument classes
[
https://issues.apache.org/jira/browse/ARTEMIS-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163527#comment-15163527
]
ASF GitHub Bot commented on ARTEMIS-359:
Github user asfgit closed the pull request at:
https://github.com/apache/activemq-artemis/pull/404
> [TestSuite] IBM JDK does not allow to instrument classes
>
>
> Key: ARTEMIS-359
> URL: https://issues.apache.org/jira/browse/ARTEMIS-359
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Miroslav Novak
> Fix For: 1.3.0
>
>
> IBM JDK 6/7/8 does not allow byteman agent to modify classes. For example
> "extra-tests" will fail with following exception:
> {code}
> Running
> org.apache.activemq.artemis.tests.extras.byteman.ActiveMQMessageHandlerTest
> byteman jar is
> /home/mnovak/.m2/repository/org/jboss/byteman/byteman/2.2.0/byteman-2.2.0.jar
> com.ibm.tools.attach.AttachNotSupportedException: acknowledgement timeout
> from 21654 on port 42521
> at
> com.ibm.tools.attach.javaSE.VirtualMachineImpl.tryAttachTarget(VirtualMachineImpl.java:401)
> at
> com.ibm.tools.attach.javaSE.VirtualMachineImpl.attachTarget(VirtualMachineImpl.java:94)
> at
> com.ibm.tools.attach.javaSE.AttachProviderImpl.attachVirtualMachine(AttachProviderImpl.java:37)
> at
> ibm.tools.attach.J9AttachProvider.attachVirtualMachine(J9AttachProvider.java:55)
> at com.sun.tools.attach.VirtualMachine.attach(VirtualMachine.java:231)
> at org.jboss.byteman.agent.install.Install.attach(Install.java:374)
> at org.jboss.byteman.agent.install.Install.install(Install.java:113)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitConfigState.loadAgent(BMUnitConfigState.java:340)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitConfigState.pushConfigurationState(BMUnitConfigState.java:472)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitRunner$1.evaluate(BMUnitRunner.java:98)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
> at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
> Caused by: java.net.SocketTimeoutException: Accept timed out
> at
> java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:445)
> at java.net.ServerSocket.implAccept(ServerSocket.java:620)
> at java.net.ServerSocket.accept(ServerSocket.java:579)
> at
> com.ibm.tools.attach.javaSE.VirtualMachineImpl.tryAttachTarget(VirtualMachineImpl.java:396)
> ... 17 more
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 291.094 sec
> <<< FAILURE! - in
> org.apache.activemq.artemis.tests.extras.byteman.ActiveMQMessageHandlerTest
> org.apache.activemq.artemis.tests.extras.byteman.ActiveMQMessageHandlerTest(org.apache.activemq.artemis.tests.extras.byteman.ActiveMQMessageHandlerTest)
> Time elapsed: 291.094 sec <<< ERROR!
> com.sun.tools.attach.AttachNotSupportedException: acknowledgement timeout
> from 21654 on port 42521
> at
> ibm.tools.attach.J9AttachProvider.attachVirtualMachine(J9AttachProvider.java:60)
> at com.sun.tools.attach.VirtualMachine.attach(VirtualMachine.java:231)
> at org.jboss.byteman.agent.install.Install.attach(Install.java:374)
> at org.jboss.byteman.agent.install.Install.install(Install.java:113)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitConfigState.loadAgent(BMUnitConfigState.java:340)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitConfigState.pushConfigurationState(BMUnitConfigState.java:472)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitRunner$1.evaluate(BMUnitRunner.java:98)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
> at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(For
[jira] [Commented] (ARTEMIS-359) [TestSuite] IBM JDK does not allow to instrument classes
[
https://issues.apache.org/jira/browse/ARTEMIS-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163526#comment-15163526
]
ASF subversion and git services commented on ARTEMIS-359:
-
Commit 45aeeb3ba75d3705fb6c465dcd1781c4f07a28de in activemq-artemis's branch
refs/heads/master from Clebert Suconic
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=45aeeb3 ]
Revert "ARTEMIS-359 - test suite fix - IBM JDK 6/7/8 does not allow byteman
agent to modify classes."
This is causing issues with running tests on the IDEs
This reverts commit fe9b95ed64821c6ed63564a0c0ba9792123823b3.
> [TestSuite] IBM JDK does not allow to instrument classes
>
>
> Key: ARTEMIS-359
> URL: https://issues.apache.org/jira/browse/ARTEMIS-359
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Miroslav Novak
> Fix For: 1.3.0
>
>
> IBM JDK 6/7/8 does not allow byteman agent to modify classes. For example
> "extra-tests" will fail with following exception:
> {code}
> Running
> org.apache.activemq.artemis.tests.extras.byteman.ActiveMQMessageHandlerTest
> byteman jar is
> /home/mnovak/.m2/repository/org/jboss/byteman/byteman/2.2.0/byteman-2.2.0.jar
> com.ibm.tools.attach.AttachNotSupportedException: acknowledgement timeout
> from 21654 on port 42521
> at
> com.ibm.tools.attach.javaSE.VirtualMachineImpl.tryAttachTarget(VirtualMachineImpl.java:401)
> at
> com.ibm.tools.attach.javaSE.VirtualMachineImpl.attachTarget(VirtualMachineImpl.java:94)
> at
> com.ibm.tools.attach.javaSE.AttachProviderImpl.attachVirtualMachine(AttachProviderImpl.java:37)
> at
> ibm.tools.attach.J9AttachProvider.attachVirtualMachine(J9AttachProvider.java:55)
> at com.sun.tools.attach.VirtualMachine.attach(VirtualMachine.java:231)
> at org.jboss.byteman.agent.install.Install.attach(Install.java:374)
> at org.jboss.byteman.agent.install.Install.install(Install.java:113)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitConfigState.loadAgent(BMUnitConfigState.java:340)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitConfigState.pushConfigurationState(BMUnitConfigState.java:472)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitRunner$1.evaluate(BMUnitRunner.java:98)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
> at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
> Caused by: java.net.SocketTimeoutException: Accept timed out
> at
> java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:445)
> at java.net.ServerSocket.implAccept(ServerSocket.java:620)
> at java.net.ServerSocket.accept(ServerSocket.java:579)
> at
> com.ibm.tools.attach.javaSE.VirtualMachineImpl.tryAttachTarget(VirtualMachineImpl.java:396)
> ... 17 more
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 291.094 sec
> <<< FAILURE! - in
> org.apache.activemq.artemis.tests.extras.byteman.ActiveMQMessageHandlerTest
> org.apache.activemq.artemis.tests.extras.byteman.ActiveMQMessageHandlerTest(org.apache.activemq.artemis.tests.extras.byteman.ActiveMQMessageHandlerTest)
> Time elapsed: 291.094 sec <<< ERROR!
> com.sun.tools.attach.AttachNotSupportedException: acknowledgement timeout
> from 21654 on port 42521
> at
> ibm.tools.attach.J9AttachProvider.attachVirtualMachine(J9AttachProvider.java:60)
> at com.sun.tools.attach.VirtualMachine.attach(VirtualMachine.java:231)
> at org.jboss.byteman.agent.install.Install.attach(Install.java:374)
> at org.jboss.byteman.agent.install.Install.install(Install.java:113)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitConfigState.loadAgent(BMUnitConfigState.java:340)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitConfigState.pushConfigurationState(BMUnitConfigState.java:472)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitRunner$1.evaluate(BMUnitRunner.java:98)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)
> at
> org.apache.maven.surefire.junit4.JU
[jira] [Commented] (ARTEMIS-359) [TestSuite] IBM JDK does not allow to instrument classes
[
https://issues.apache.org/jira/browse/ARTEMIS-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163322#comment-15163322
]
ASF GitHub Bot commented on ARTEMIS-359:
GitHub user clebertsuconic opened a pull request:
https://github.com/apache/activemq-artemis/pull/404
Revert "ARTEMIS-359 - test suite fix - IBM JDK 6/7/8 does not allow b…
…yteman agent to modify classes."
This is causing issues with running tests on the IDEs
This reverts commit fe9b95ed64821c6ed63564a0c0ba9792123823b3.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/clebertsuconic/activemq-artemis revert
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/404.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #404
commit d12ccbf63a2795455b3a0db85a6eb0463bbc6c7d
Author: Clebert Suconic
Date: 2016-02-24T17:00:30Z
Revert "ARTEMIS-359 - test suite fix - IBM JDK 6/7/8 does not allow byteman
agent to modify classes."
This is causing issues with running tests on the IDEs
This reverts commit fe9b95ed64821c6ed63564a0c0ba9792123823b3.
> [TestSuite] IBM JDK does not allow to instrument classes
>
>
> Key: ARTEMIS-359
> URL: https://issues.apache.org/jira/browse/ARTEMIS-359
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Miroslav Novak
> Fix For: 1.3.0
>
>
> IBM JDK 6/7/8 does not allow byteman agent to modify classes. For example
> "extra-tests" will fail with following exception:
> {code}
> Running
> org.apache.activemq.artemis.tests.extras.byteman.ActiveMQMessageHandlerTest
> byteman jar is
> /home/mnovak/.m2/repository/org/jboss/byteman/byteman/2.2.0/byteman-2.2.0.jar
> com.ibm.tools.attach.AttachNotSupportedException: acknowledgement timeout
> from 21654 on port 42521
> at
> com.ibm.tools.attach.javaSE.VirtualMachineImpl.tryAttachTarget(VirtualMachineImpl.java:401)
> at
> com.ibm.tools.attach.javaSE.VirtualMachineImpl.attachTarget(VirtualMachineImpl.java:94)
> at
> com.ibm.tools.attach.javaSE.AttachProviderImpl.attachVirtualMachine(AttachProviderImpl.java:37)
> at
> ibm.tools.attach.J9AttachProvider.attachVirtualMachine(J9AttachProvider.java:55)
> at com.sun.tools.attach.VirtualMachine.attach(VirtualMachine.java:231)
> at org.jboss.byteman.agent.install.Install.attach(Install.java:374)
> at org.jboss.byteman.agent.install.Install.install(Install.java:113)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitConfigState.loadAgent(BMUnitConfigState.java:340)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitConfigState.pushConfigurationState(BMUnitConfigState.java:472)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitRunner$1.evaluate(BMUnitRunner.java:98)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
> at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
> Caused by: java.net.SocketTimeoutException: Accept timed out
> at
> java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:445)
> at java.net.ServerSocket.implAccept(ServerSocket.java:620)
> at java.net.ServerSocket.accept(ServerSocket.java:579)
> at
> com.ibm.tools.attach.javaSE.VirtualMachineImpl.tryAttachTarget(VirtualMachineImpl.java:396)
> ... 17 more
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 291.094 sec
> <<< FAILURE! - in
> org.apache.activemq.artemis.tests.extras.byteman.ActiveMQMessageHandlerTest
> org.apache.activemq.artemis.tests.extras.byteman.ActiveMQMessageHandlerTest(org.apache.activemq.artemis.tests.extras.byteman.ActiveMQMessageHandlerTest)
> Time elapsed: 291.094 sec <<< ERROR!
> com.sun.tools.attach.AttachNotSupportedException: acknowledgement timeout
> from 21654 on port 42521
> at
> ibm.tools.attach.J9AttachProvider.attachVirtualMachine(J9AttachProvider.java:60)
> at com.sun.tools.attach.VirtualMachine.attach(VirtualMachine.j
[jira] [Closed] (ARTEMIS-359) [TestSuite] IBM JDK does not allow to instrument classes
[
https://issues.apache.org/jira/browse/ARTEMIS-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clebert suconic closed ARTEMIS-359.
---
Resolution: Won't Fix
> [TestSuite] IBM JDK does not allow to instrument classes
>
>
> Key: ARTEMIS-359
> URL: https://issues.apache.org/jira/browse/ARTEMIS-359
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Miroslav Novak
> Fix For: 1.3.0
>
>
> IBM JDK 6/7/8 does not allow byteman agent to modify classes. For example
> "extra-tests" will fail with following exception:
> {code}
> Running
> org.apache.activemq.artemis.tests.extras.byteman.ActiveMQMessageHandlerTest
> byteman jar is
> /home/mnovak/.m2/repository/org/jboss/byteman/byteman/2.2.0/byteman-2.2.0.jar
> com.ibm.tools.attach.AttachNotSupportedException: acknowledgement timeout
> from 21654 on port 42521
> at
> com.ibm.tools.attach.javaSE.VirtualMachineImpl.tryAttachTarget(VirtualMachineImpl.java:401)
> at
> com.ibm.tools.attach.javaSE.VirtualMachineImpl.attachTarget(VirtualMachineImpl.java:94)
> at
> com.ibm.tools.attach.javaSE.AttachProviderImpl.attachVirtualMachine(AttachProviderImpl.java:37)
> at
> ibm.tools.attach.J9AttachProvider.attachVirtualMachine(J9AttachProvider.java:55)
> at com.sun.tools.attach.VirtualMachine.attach(VirtualMachine.java:231)
> at org.jboss.byteman.agent.install.Install.attach(Install.java:374)
> at org.jboss.byteman.agent.install.Install.install(Install.java:113)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitConfigState.loadAgent(BMUnitConfigState.java:340)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitConfigState.pushConfigurationState(BMUnitConfigState.java:472)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitRunner$1.evaluate(BMUnitRunner.java:98)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
> at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
> Caused by: java.net.SocketTimeoutException: Accept timed out
> at
> java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:445)
> at java.net.ServerSocket.implAccept(ServerSocket.java:620)
> at java.net.ServerSocket.accept(ServerSocket.java:579)
> at
> com.ibm.tools.attach.javaSE.VirtualMachineImpl.tryAttachTarget(VirtualMachineImpl.java:396)
> ... 17 more
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 291.094 sec
> <<< FAILURE! - in
> org.apache.activemq.artemis.tests.extras.byteman.ActiveMQMessageHandlerTest
> org.apache.activemq.artemis.tests.extras.byteman.ActiveMQMessageHandlerTest(org.apache.activemq.artemis.tests.extras.byteman.ActiveMQMessageHandlerTest)
> Time elapsed: 291.094 sec <<< ERROR!
> com.sun.tools.attach.AttachNotSupportedException: acknowledgement timeout
> from 21654 on port 42521
> at
> ibm.tools.attach.J9AttachProvider.attachVirtualMachine(J9AttachProvider.java:60)
> at com.sun.tools.attach.VirtualMachine.attach(VirtualMachine.java:231)
> at org.jboss.byteman.agent.install.Install.attach(Install.java:374)
> at org.jboss.byteman.agent.install.Install.install(Install.java:113)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitConfigState.loadAgent(BMUnitConfigState.java:340)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitConfigState.pushConfigurationState(BMUnitConfigState.java:472)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitRunner$1.evaluate(BMUnitRunner.java:98)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
> at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
> at
> o
[jira] [Commented] (ARTEMIS-359) [TestSuite] IBM JDK does not allow to instrument classes
[
https://issues.apache.org/jira/browse/ARTEMIS-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163319#comment-15163319
]
clebert suconic commented on ARTEMIS-359:
-
I am reverting this commit:
this is breaking integration with IDEs.. it's not possible to run Byteman tests
under Idea because of these properties. Idea just get the maven properties to
run the tests.
I would say don't run these tests on IBM?
> [TestSuite] IBM JDK does not allow to instrument classes
>
>
> Key: ARTEMIS-359
> URL: https://issues.apache.org/jira/browse/ARTEMIS-359
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Miroslav Novak
> Fix For: 1.3.0
>
>
> IBM JDK 6/7/8 does not allow byteman agent to modify classes. For example
> "extra-tests" will fail with following exception:
> {code}
> Running
> org.apache.activemq.artemis.tests.extras.byteman.ActiveMQMessageHandlerTest
> byteman jar is
> /home/mnovak/.m2/repository/org/jboss/byteman/byteman/2.2.0/byteman-2.2.0.jar
> com.ibm.tools.attach.AttachNotSupportedException: acknowledgement timeout
> from 21654 on port 42521
> at
> com.ibm.tools.attach.javaSE.VirtualMachineImpl.tryAttachTarget(VirtualMachineImpl.java:401)
> at
> com.ibm.tools.attach.javaSE.VirtualMachineImpl.attachTarget(VirtualMachineImpl.java:94)
> at
> com.ibm.tools.attach.javaSE.AttachProviderImpl.attachVirtualMachine(AttachProviderImpl.java:37)
> at
> ibm.tools.attach.J9AttachProvider.attachVirtualMachine(J9AttachProvider.java:55)
> at com.sun.tools.attach.VirtualMachine.attach(VirtualMachine.java:231)
> at org.jboss.byteman.agent.install.Install.attach(Install.java:374)
> at org.jboss.byteman.agent.install.Install.install(Install.java:113)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitConfigState.loadAgent(BMUnitConfigState.java:340)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitConfigState.pushConfigurationState(BMUnitConfigState.java:472)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitRunner$1.evaluate(BMUnitRunner.java:98)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
> at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
> Caused by: java.net.SocketTimeoutException: Accept timed out
> at
> java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:445)
> at java.net.ServerSocket.implAccept(ServerSocket.java:620)
> at java.net.ServerSocket.accept(ServerSocket.java:579)
> at
> com.ibm.tools.attach.javaSE.VirtualMachineImpl.tryAttachTarget(VirtualMachineImpl.java:396)
> ... 17 more
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 291.094 sec
> <<< FAILURE! - in
> org.apache.activemq.artemis.tests.extras.byteman.ActiveMQMessageHandlerTest
> org.apache.activemq.artemis.tests.extras.byteman.ActiveMQMessageHandlerTest(org.apache.activemq.artemis.tests.extras.byteman.ActiveMQMessageHandlerTest)
> Time elapsed: 291.094 sec <<< ERROR!
> com.sun.tools.attach.AttachNotSupportedException: acknowledgement timeout
> from 21654 on port 42521
> at
> ibm.tools.attach.J9AttachProvider.attachVirtualMachine(J9AttachProvider.java:60)
> at com.sun.tools.attach.VirtualMachine.attach(VirtualMachine.java:231)
> at org.jboss.byteman.agent.install.Install.attach(Install.java:374)
> at org.jboss.byteman.agent.install.Install.install(Install.java:113)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitConfigState.loadAgent(BMUnitConfigState.java:340)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitConfigState.pushConfigurationState(BMUnitConfigState.java:472)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitRunner$1.evaluate(BMUnitRunner.java:98)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
> at
> org.apache.maven.surefire.juni
[jira] [Reopened] (ARTEMIS-359) [TestSuite] IBM JDK does not allow to instrument classes
[
https://issues.apache.org/jira/browse/ARTEMIS-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clebert suconic reopened ARTEMIS-359:
-
> [TestSuite] IBM JDK does not allow to instrument classes
>
>
> Key: ARTEMIS-359
> URL: https://issues.apache.org/jira/browse/ARTEMIS-359
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Miroslav Novak
> Fix For: 1.3.0
>
>
> IBM JDK 6/7/8 does not allow byteman agent to modify classes. For example
> "extra-tests" will fail with following exception:
> {code}
> Running
> org.apache.activemq.artemis.tests.extras.byteman.ActiveMQMessageHandlerTest
> byteman jar is
> /home/mnovak/.m2/repository/org/jboss/byteman/byteman/2.2.0/byteman-2.2.0.jar
> com.ibm.tools.attach.AttachNotSupportedException: acknowledgement timeout
> from 21654 on port 42521
> at
> com.ibm.tools.attach.javaSE.VirtualMachineImpl.tryAttachTarget(VirtualMachineImpl.java:401)
> at
> com.ibm.tools.attach.javaSE.VirtualMachineImpl.attachTarget(VirtualMachineImpl.java:94)
> at
> com.ibm.tools.attach.javaSE.AttachProviderImpl.attachVirtualMachine(AttachProviderImpl.java:37)
> at
> ibm.tools.attach.J9AttachProvider.attachVirtualMachine(J9AttachProvider.java:55)
> at com.sun.tools.attach.VirtualMachine.attach(VirtualMachine.java:231)
> at org.jboss.byteman.agent.install.Install.attach(Install.java:374)
> at org.jboss.byteman.agent.install.Install.install(Install.java:113)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitConfigState.loadAgent(BMUnitConfigState.java:340)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitConfigState.pushConfigurationState(BMUnitConfigState.java:472)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitRunner$1.evaluate(BMUnitRunner.java:98)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
> at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
> Caused by: java.net.SocketTimeoutException: Accept timed out
> at
> java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:445)
> at java.net.ServerSocket.implAccept(ServerSocket.java:620)
> at java.net.ServerSocket.accept(ServerSocket.java:579)
> at
> com.ibm.tools.attach.javaSE.VirtualMachineImpl.tryAttachTarget(VirtualMachineImpl.java:396)
> ... 17 more
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 291.094 sec
> <<< FAILURE! - in
> org.apache.activemq.artemis.tests.extras.byteman.ActiveMQMessageHandlerTest
> org.apache.activemq.artemis.tests.extras.byteman.ActiveMQMessageHandlerTest(org.apache.activemq.artemis.tests.extras.byteman.ActiveMQMessageHandlerTest)
> Time elapsed: 291.094 sec <<< ERROR!
> com.sun.tools.attach.AttachNotSupportedException: acknowledgement timeout
> from 21654 on port 42521
> at
> ibm.tools.attach.J9AttachProvider.attachVirtualMachine(J9AttachProvider.java:60)
> at com.sun.tools.attach.VirtualMachine.attach(VirtualMachine.java:231)
> at org.jboss.byteman.agent.install.Install.attach(Install.java:374)
> at org.jboss.byteman.agent.install.Install.install(Install.java:113)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitConfigState.loadAgent(BMUnitConfigState.java:340)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitConfigState.pushConfigurationState(BMUnitConfigState.java:472)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitRunner$1.evaluate(BMUnitRunner.java:98)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
> at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
> at
> org.apache.maven.surefi
[jira] [Updated] (ARTEMIS-359) [TestSuite] IBM JDK does not allow to instrument classes
[
https://issues.apache.org/jira/browse/ARTEMIS-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clebert suconic updated ARTEMIS-359:
Fix Version/s: 1.3.0
> [TestSuite] IBM JDK does not allow to instrument classes
>
>
> Key: ARTEMIS-359
> URL: https://issues.apache.org/jira/browse/ARTEMIS-359
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Miroslav Novak
> Fix For: 1.3.0
>
>
> IBM JDK 6/7/8 does not allow byteman agent to modify classes. For example
> "extra-tests" will fail with following exception:
> {code}
> Running
> org.apache.activemq.artemis.tests.extras.byteman.ActiveMQMessageHandlerTest
> byteman jar is
> /home/mnovak/.m2/repository/org/jboss/byteman/byteman/2.2.0/byteman-2.2.0.jar
> com.ibm.tools.attach.AttachNotSupportedException: acknowledgement timeout
> from 21654 on port 42521
> at
> com.ibm.tools.attach.javaSE.VirtualMachineImpl.tryAttachTarget(VirtualMachineImpl.java:401)
> at
> com.ibm.tools.attach.javaSE.VirtualMachineImpl.attachTarget(VirtualMachineImpl.java:94)
> at
> com.ibm.tools.attach.javaSE.AttachProviderImpl.attachVirtualMachine(AttachProviderImpl.java:37)
> at
> ibm.tools.attach.J9AttachProvider.attachVirtualMachine(J9AttachProvider.java:55)
> at com.sun.tools.attach.VirtualMachine.attach(VirtualMachine.java:231)
> at org.jboss.byteman.agent.install.Install.attach(Install.java:374)
> at org.jboss.byteman.agent.install.Install.install(Install.java:113)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitConfigState.loadAgent(BMUnitConfigState.java:340)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitConfigState.pushConfigurationState(BMUnitConfigState.java:472)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitRunner$1.evaluate(BMUnitRunner.java:98)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
> at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
> Caused by: java.net.SocketTimeoutException: Accept timed out
> at
> java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:445)
> at java.net.ServerSocket.implAccept(ServerSocket.java:620)
> at java.net.ServerSocket.accept(ServerSocket.java:579)
> at
> com.ibm.tools.attach.javaSE.VirtualMachineImpl.tryAttachTarget(VirtualMachineImpl.java:396)
> ... 17 more
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 291.094 sec
> <<< FAILURE! - in
> org.apache.activemq.artemis.tests.extras.byteman.ActiveMQMessageHandlerTest
> org.apache.activemq.artemis.tests.extras.byteman.ActiveMQMessageHandlerTest(org.apache.activemq.artemis.tests.extras.byteman.ActiveMQMessageHandlerTest)
> Time elapsed: 291.094 sec <<< ERROR!
> com.sun.tools.attach.AttachNotSupportedException: acknowledgement timeout
> from 21654 on port 42521
> at
> ibm.tools.attach.J9AttachProvider.attachVirtualMachine(J9AttachProvider.java:60)
> at com.sun.tools.attach.VirtualMachine.attach(VirtualMachine.java:231)
> at org.jboss.byteman.agent.install.Install.attach(Install.java:374)
> at org.jboss.byteman.agent.install.Install.install(Install.java:113)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitConfigState.loadAgent(BMUnitConfigState.java:340)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitConfigState.pushConfigurationState(BMUnitConfigState.java:472)
> at
> org.jboss.byteman.contrib.bmunit.BMUnitRunner$1.evaluate(BMUnitRunner.java:98)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
> at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
> at
>
[jira] [Commented] (ARTEMIS-421) wrong XA_RETRY XAException error code returned on crash for 1PC
[ https://issues.apache.org/jira/browse/ARTEMIS-421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163317#comment-15163317 ] ASF GitHub Bot commented on ARTEMIS-421: Github user asfgit closed the pull request at: https://github.com/apache/activemq-artemis/pull/403 > wrong XA_RETRY XAException error code returned on crash for 1PC > --- > > Key: ARTEMIS-421 > URL: https://issues.apache.org/jira/browse/ARTEMIS-421 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 1.1.0 >Reporter: Howard Gao >Assignee: Howard Gao >Priority: Critical > Fix For: 1.2.0 > > > According to XA spec you can't return XA_RETRY from xa_commit(TMONEPHASE) and > that RMFAIL should be returned. > Currently artemis always return XA_RETRY regardless of one_phase flag. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ARTEMIS-421) wrong XA_RETRY XAException error code returned on crash for 1PC
[ https://issues.apache.org/jira/browse/ARTEMIS-421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163316#comment-15163316 ] ASF subversion and git services commented on ARTEMIS-421: - Commit ddf8d8f96e33f5f80e1c7a1590de9579aa8ead50 in activemq-artemis's branch refs/heads/master from [~gaohoward] [ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=ddf8d8f ] ARTEMIS-421 wrong XA_RETRY XAException error code returned on crash for 1PC > wrong XA_RETRY XAException error code returned on crash for 1PC > --- > > Key: ARTEMIS-421 > URL: https://issues.apache.org/jira/browse/ARTEMIS-421 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 1.1.0 >Reporter: Howard Gao >Assignee: Howard Gao >Priority: Critical > Fix For: 1.2.0 > > > According to XA spec you can't return XA_RETRY from xa_commit(TMONEPHASE) and > that RMFAIL should be returned. > Currently artemis always return XA_RETRY regardless of one_phase flag. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMQ-6182) disable TRACE method in apache activeMQ Server
[ https://issues.apache.org/jira/browse/AMQ-6182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163171#comment-15163171 ] Vidya Sagar D commented on AMQ-6182: The security dept ask me to disable "TRACE method" on this port 61614. I saw that it's disable for default on port 8161 where are the webapps admin, hawtio, etc. ( at org/eclipse/jetty/webapp/webdefault.xml for jetty webserver there is a ) Is possible disable it on port 61614 too ? Please could someone tell me how to do that ... > disable TRACE method in apache activeMQ Server > -- > > Key: AMQ-6182 > URL: https://issues.apache.org/jira/browse/AMQ-6182 > Project: ActiveMQ > Issue Type: Task >Affects Versions: 5.11.1, 5.13.0 > Environment: linux operating system >Reporter: Vidya Sagar D >Priority: Critical > Labels: activemq, activemq-web-console,, jetty > Original Estimate: 12h > Remaining Estimate: 12h > > For security reasons, have to disable TRACE method in Apache ActiveMQ Server, > unable to do it. > Could you please help me to disable TRACE method in Apache ActiveMQ server ( > Jetty 7.x - Internal Server) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (AMQ-6172) Broker Health check status never updates
[
https://issues.apache.org/jira/browse/AMQ-6172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-6172.
-
Resolution: Not A Problem
Closing this out as it is working as designed and there doesn't seem to be any
issues with call the health methods exposed via Jolokia
> Broker Health check status never updates
>
>
> Key: AMQ-6172
> URL: https://issues.apache.org/jira/browse/AMQ-6172
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
>Affects Versions: 5.13.1
>Reporter: Yevhenii Pazii
>
> Method getCurrentStatus of HealthViewMBean class never changes status even if
> broker have critical conditions. No matter how this methods calls through JMX
> or jolokia.
> Method returns instance field without any calculations.
> {quote}
> public String getCurrentStatus() \{
> return this.currentState;
> }
> {quote}
> The method which actually updates this field is "List
> healthList() throws Exception;". As far as I know no one else call this
> method, so status field never updates. This method works fine by JMX, but it
> doesn't exposed to jolokia for Rest calls.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ARTEMIS-421) wrong XA_RETRY XAException error code returned on crash for 1PC
[ https://issues.apache.org/jira/browse/ARTEMIS-421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163034#comment-15163034 ] ASF GitHub Bot commented on ARTEMIS-421: Github user gaohoward commented on the pull request: https://github.com/apache/activemq-artemis/pull/403#issuecomment-188268825 It's checkstyle error. I'll fix it. > wrong XA_RETRY XAException error code returned on crash for 1PC > --- > > Key: ARTEMIS-421 > URL: https://issues.apache.org/jira/browse/ARTEMIS-421 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 1.1.0 >Reporter: Howard Gao >Assignee: Howard Gao >Priority: Critical > Fix For: 1.2.0 > > > According to XA spec you can't return XA_RETRY from xa_commit(TMONEPHASE) and > that RMFAIL should be returned. > Currently artemis always return XA_RETRY regardless of one_phase flag. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMQ-6163) ActiveMQ creates a new empty KahaDB
[ https://issues.apache.org/jira/browse/AMQ-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15162994#comment-15162994 ] Christopher L. Shannon commented on AMQ-6163: - I didn't look at the test project yet but I looked a little bit at the logic for getting the broker name for that directory. One thing I noticed is that there's some logic in the BrokerService to grab the local host name and to use that for the broker name if a certain flag is set, although normally it just uses what was set in the xml. It's possible that the method call InetAddress.getLocalHost() is returning 127.0.0.1 for you instead of localhost and that's causing this problem. Is there an entry in your /etc/hosts file for localhost 127.0.0.1? > ActiveMQ creates a new empty KahaDB > --- > > Key: AMQ-6163 > URL: https://issues.apache.org/jira/browse/AMQ-6163 > Project: ActiveMQ > Issue Type: Bug > Components: activemq-camel >Affects Versions: 5.13.0 > Environment: Windows 10, Eclipse >Reporter: Björn Paulsen > Attachments: AllInOneBoilerBug.zip > > > Hello Together, > I want create a JVM with Camel and ActiveMQ inside. > I create in Eclipse a new Spring configuration. It works, but when I open the > ActiveMQ Managment Website and look on the Queue Detail Page, where should > list all Messages, ActiveMQ creates a new empty KahaDB in the Directory > activemq-data and read from there, so no Messages are show. When I go back on > Queue List i see the right count of messages. > I ask on Nabble about the Problem, but there couldn't help me anybody. So I > think this is not a configuration error, this should be a bug. > http://activemq.2283324.n4.nabble.com/ActiveMQ-KahaDB-Directory-td4706593.html > I have a example Eclipse Project where you can see the error, but I couldn't > upload this here, so I do it on file-upload.net > http://www.file-upload.net/download-11292082/AllInOneBoilerBug.zip.html > I hope this could help. > Thank you very much -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMQ-6118) ActiveMQ SSL CRL Checking via OCSP
[ https://issues.apache.org/jira/browse/AMQ-6118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15162946#comment-15162946 ] Christopher L. Shannon commented on AMQ-6118: - I updated this issue to be a new feature and to possibly go into a 5.14.0 release if someone gets time to work on it. Also, contributions are always welcome so if you have time and want to try and tackle adding this feature then that would be great as well. > ActiveMQ SSL CRL Checking via OCSP > -- > > Key: AMQ-6118 > URL: https://issues.apache.org/jira/browse/AMQ-6118 > Project: ActiveMQ > Issue Type: New Feature > Components: Broker >Affects Versions: 5.12.1 > Environment: Windows Server 2012R2 with ActiveMQ Windows Distribution >Reporter: Marko Jovanovic > Fix For: 5.14.0 > > Attachments: jvm_args.png > > > For some unknown reason, the CRL Check via OCSP isn't working in Windows > ActiveMQ 5.12.1 > After reviewing the Linux distribution of Activemq there was a configuration > line found in the file bin/env. > The Config in Linux Distribution looked like: > # Set additional JSE arguments > #ACTIVEMQ_SSL_OPTS="-Dcom.sun.security.enableCRLDP=true -Docsp.enable=true > -Docsp.responderURL=http://ocsp.example.net:80"; > Where to set it in Windows file distribution? > Tried to set it in activemq file but no success. I couldn't see any request > going to the responder URL which I configured. > Think there is a general Problem with the code concerning OCSP functionality. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMQ-6118) ActiveMQ SSL CRL Checking via OCSP
[ https://issues.apache.org/jira/browse/AMQ-6118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon updated AMQ-6118: Fix Version/s: 5.14.0 Issue Type: New Feature (was: Bug) > ActiveMQ SSL CRL Checking via OCSP > -- > > Key: AMQ-6118 > URL: https://issues.apache.org/jira/browse/AMQ-6118 > Project: ActiveMQ > Issue Type: New Feature > Components: Broker >Affects Versions: 5.12.1 > Environment: Windows Server 2012R2 with ActiveMQ Windows Distribution >Reporter: Marko Jovanovic > Fix For: 5.14.0 > > Attachments: jvm_args.png > > > For some unknown reason, the CRL Check via OCSP isn't working in Windows > ActiveMQ 5.12.1 > After reviewing the Linux distribution of Activemq there was a configuration > line found in the file bin/env. > The Config in Linux Distribution looked like: > # Set additional JSE arguments > #ACTIVEMQ_SSL_OPTS="-Dcom.sun.security.enableCRLDP=true -Docsp.enable=true > -Docsp.responderURL=http://ocsp.example.net:80"; > Where to set it in Windows file distribution? > Tried to set it in activemq file but no success. I couldn't see any request > going to the responder URL which I configured. > Think there is a general Problem with the code concerning OCSP functionality. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMQ-6182) disable TRACE method in apache activeMQ Server
[ https://issues.apache.org/jira/browse/AMQ-6182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15162936#comment-15162936 ] Christopher L. Shannon commented on AMQ-6182: - I'm not sure I entirely understand what you mean but have you looked at http://activemq.apache.org/how-do-i-change-the-logging.html ? You can configure the logging levels for ActiveMQ easily. Also, for help with configuration, those questions are better sent to the user's mailing list. http://activemq.apache.org/mailing-lists.html > disable TRACE method in apache activeMQ Server > -- > > Key: AMQ-6182 > URL: https://issues.apache.org/jira/browse/AMQ-6182 > Project: ActiveMQ > Issue Type: Task >Affects Versions: 5.11.1, 5.13.0 > Environment: linux operating system >Reporter: Vidya Sagar D >Priority: Critical > Labels: activemq, activemq-web-console,, jetty > Original Estimate: 12h > Remaining Estimate: 12h > > For security reasons, have to disable TRACE method in Apache ActiveMQ Server, > unable to do it. > Could you please help me to disable TRACE method in Apache ActiveMQ server ( > Jetty 7.x - Internal Server) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ARTEMIS-421) wrong XA_RETRY XAException error code returned on crash for 1PC
[ https://issues.apache.org/jira/browse/ARTEMIS-421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15162814#comment-15162814 ] ASF GitHub Bot commented on ARTEMIS-421: GitHub user gaohoward opened a pull request: https://github.com/apache/activemq-artemis/pull/403 ARTEMIS-421 wrong XA_RETRY XAException error code returned on crash for 1PC ARTEMIS-421 wrong XA_RETRY XAException error code returned on crash for 1PC You can merge this pull request into a Git repository by running: $ git pull https://github.com/gaohoward/activemq-artemis artemis421 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-artemis/pull/403.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #403 commit 19fe7fd595566236788929afe26e9cebedce9ce7 Author: Howard Gao Date: 2016-02-24T10:54:45Z ARTEMIS-421 wrong XA_RETRY XAException error code returned on crash for 1PC > wrong XA_RETRY XAException error code returned on crash for 1PC > --- > > Key: ARTEMIS-421 > URL: https://issues.apache.org/jira/browse/ARTEMIS-421 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 1.1.0 >Reporter: Howard Gao >Assignee: Howard Gao >Priority: Critical > Fix For: 1.2.0 > > > According to XA spec you can't return XA_RETRY from xa_commit(TMONEPHASE) and > that RMFAIL should be returned. > Currently artemis always return XA_RETRY regardless of one_phase flag. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMQ-6182) disable TRACE method in apache activeMQ Server
Vidya Sagar D created AMQ-6182: -- Summary: disable TRACE method in apache activeMQ Server Key: AMQ-6182 URL: https://issues.apache.org/jira/browse/AMQ-6182 Project: ActiveMQ Issue Type: Task Affects Versions: 5.13.0, 5.11.1 Environment: linux operating system Reporter: Vidya Sagar D Priority: Critical For security reasons, have to disable TRACE method in Apache ActiveMQ Server, unable to do it. Could you please help me to disable TRACE method in Apache ActiveMQ server ( Jetty 7.x - Internal Server) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ARTEMIS-421) wrong XA_RETRY XAException error code returned on crash for 1PC
Howard Gao created ARTEMIS-421: -- Summary: wrong XA_RETRY XAException error code returned on crash for 1PC Key: ARTEMIS-421 URL: https://issues.apache.org/jira/browse/ARTEMIS-421 Project: ActiveMQ Artemis Issue Type: Bug Components: Broker Affects Versions: 1.1.0 Reporter: Howard Gao Assignee: Howard Gao Priority: Critical Fix For: 1.2.0 According to XA spec you can't return XA_RETRY from xa_commit(TMONEPHASE) and that RMFAIL should be returned. Currently artemis always return XA_RETRY regardless of one_phase flag. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ARTEMIS-420) The service script should support running the broker as a different user
Lionel Cons created ARTEMIS-420:
---
Summary: The service script should support running the broker as a
different user
Key: ARTEMIS-420
URL: https://issues.apache.org/jira/browse/ARTEMIS-420
Project: ActiveMQ Artemis
Issue Type: Improvement
Reporter: Lionel Cons
There is no support for changing user in {{artemis-service}}. It simply
executes:
{code}
nohup ${ARTEMIS_INSTANCE}/bin/artemis run > /dev/null 2> /dev/null &
{code}
In contrast, one can set {{APOLLO_USER}} to change the user running the Apollo
broker. This is implemented in {{apollo-broker-service}} as:
{code}
if [ -z "$APOLLO_USER" -o `id -un` = "$APOLLO_USER" ] ; then
nohup ${APOLLO_BASE}/bin/apollo-broker run > /dev/null 2> /dev/null &
else
sudo -n -u ${APOLLO_USER} nohup ${APOLLO_BASE}/bin/apollo-broker run >
/dev/null 2> /dev/null &
fi
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
