[jira] [Updated] (ARTEMIS-392) Artemis NettyConnetor doesn't set Allocators after HTTP socket upgrade
[ https://issues.apache.org/jira/browse/ARTEMIS-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-392: Summary: Artemis NettyConnetor doesn't set Allocators after HTTP socket upgrade (was: Netty doesn't set Allocators after HTTP socket upgrade) > Artemis NettyConnetor doesn't set Allocators after HTTP socket upgrade > -- > > Key: ARTEMIS-392 > URL: https://issues.apache.org/jira/browse/ARTEMIS-392 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 1.1.0 >Reporter: clebert suconic >Assignee: clebert suconic > Fix For: 1.3.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ARTEMIS-392) Netty doesn't set Allocators after HTTP socket upgrade
[ https://issues.apache.org/jira/browse/ARTEMIS-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15135067#comment-15135067 ] ASF GitHub Bot commented on ARTEMIS-392: GitHub user clebertsuconic opened a pull request: https://github.com/apache/activemq-artemis/pull/374 ARTEMIS-392 Fixing Allocator after socket upgrade You can merge this pull request into a Git repository by running: $ git pull https://github.com/clebertsuconic/activemq-artemis ARTEMIS-392 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-artemis/pull/374.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 #374 commit 6408e3f8eec64efb070ab61d5535d86544101263 Author: Clebert Suconic Date: 2016-02-05T21:42:34Z ARTEMIS-392 Fixing Allocator after socket upgrade https://issues.apache.org/jira/browse/ARTEMIS-392 > Netty doesn't set Allocators after HTTP socket upgrade > -- > > Key: ARTEMIS-392 > URL: https://issues.apache.org/jira/browse/ARTEMIS-392 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 1.1.0 >Reporter: clebert suconic >Assignee: clebert suconic > Fix For: 1.3.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ARTEMIS-392) Netty doesn't set Allocators after HTTP socket upgrade
clebert suconic created ARTEMIS-392: --- Summary: Netty doesn't set Allocators after HTTP socket upgrade Key: ARTEMIS-392 URL: https://issues.apache.org/jira/browse/ARTEMIS-392 Project: ActiveMQ Artemis Issue Type: Bug Affects Versions: 1.1.0 Reporter: clebert suconic Assignee: clebert suconic Fix For: 1.3.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ARTEMIS-391) Connection Limit doesn't log when over the limit
[
https://issues.apache.org/jira/browse/ARTEMIS-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134950#comment-15134950
]
clebert suconic commented on ARTEMIS-391:
-
[~jbertram] I am assigining this to you just as I know you wrote this. If you
can't do now assign it to null.
> Connection Limit doesn't log when over the limit
>
>
> Key: ARTEMIS-391
> URL: https://issues.apache.org/jira/browse/ARTEMIS-391
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 1.2.0
>Reporter: clebert suconic
>Assignee: Justin Bertram
> Fix For: 1.3.0
>
>
> The current security limit doesn't log anything when going beyond the limit:
> there is a Log.DEBUG, and an empty exception that is not shown anywhere.
>else {
> if (ActiveMQServerLogger.LOGGER.isDebugEnabled()) {
>ActiveMQServerLogger.LOGGER.debug(new
> StringBuilder().append("Connection limit of
> ").append(connectionsAllowed).append(" reached. Refusing connection from
> ").append(ctx.channel().remoteAddress()));
> }
> throw new Exception();
> }
> The conneciton should be closed, and proper log should be printed. I think
> this is a situation for log.warn as the admins will need to be aware of it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ARTEMIS-391) Connection Limit doesn't log when over the limit
[
https://issues.apache.org/jira/browse/ARTEMIS-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clebert suconic updated ARTEMIS-391:
Assignee: Justin Bertram
Affects Version/s: 1.2.0
Fix Version/s: 1.3.0
> Connection Limit doesn't log when over the limit
>
>
> Key: ARTEMIS-391
> URL: https://issues.apache.org/jira/browse/ARTEMIS-391
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 1.2.0
>Reporter: clebert suconic
>Assignee: Justin Bertram
> Fix For: 1.3.0
>
>
> The current security limit doesn't log anything when going beyond the limit:
> there is a Log.DEBUG, and an empty exception that is not shown anywhere.
>else {
> if (ActiveMQServerLogger.LOGGER.isDebugEnabled()) {
>ActiveMQServerLogger.LOGGER.debug(new
> StringBuilder().append("Connection limit of
> ").append(connectionsAllowed).append(" reached. Refusing connection from
> ").append(ctx.channel().remoteAddress()));
> }
> throw new Exception();
> }
> The conneciton should be closed, and proper log should be printed. I think
> this is a situation for log.warn as the admins will need to be aware of it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ARTEMIS-391) Connection Limit doesn't log when over the limit
clebert suconic created ARTEMIS-391:
---
Summary: Connection Limit doesn't log when over the limit
Key: ARTEMIS-391
URL: https://issues.apache.org/jira/browse/ARTEMIS-391
Project: ActiveMQ Artemis
Issue Type: Bug
Reporter: clebert suconic
The current security limit doesn't log anything when going beyond the limit:
there is a Log.DEBUG, and an empty exception that is not shown anywhere.
else {
if (ActiveMQServerLogger.LOGGER.isDebugEnabled()) {
ActiveMQServerLogger.LOGGER.debug(new
StringBuilder().append("Connection limit of
").append(connectionsAllowed).append(" reached. Refusing connection from
").append(ctx.channel().remoteAddress()));
}
throw new Exception();
}
The conneciton should be closed, and proper log should be printed. I think this
is a situation for log.warn as the admins will need to be aware of it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (OPENWIRE-12) Remove dependency on Hawtbuf
[ https://issues.apache.org/jira/browse/OPENWIRE-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved OPENWIRE-12. -- Resolution: Fixed > Remove dependency on Hawtbuf > > > Key: OPENWIRE-12 > URL: https://issues.apache.org/jira/browse/OPENWIRE-12 > Project: ActiveMQ OpenWire > Issue Type: Improvement >Reporter: Timothy Bish >Assignee: Timothy Bish > > Replace Hawtbuf dependency with internal Buffer implementation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OPENWIRE-12) Remove dependency on Hawtbuf
[ https://issues.apache.org/jira/browse/OPENWIRE-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated OPENWIRE-12: - Fix Version/s: 1.0 > Remove dependency on Hawtbuf > > > Key: OPENWIRE-12 > URL: https://issues.apache.org/jira/browse/OPENWIRE-12 > Project: ActiveMQ OpenWire > Issue Type: Improvement >Reporter: Timothy Bish >Assignee: Timothy Bish > Fix For: 1.0 > > > Replace Hawtbuf dependency with internal Buffer implementation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OPENWIRE-12) Remove dependency on Hawtbuf
[ https://issues.apache.org/jira/browse/OPENWIRE-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134877#comment-15134877 ] ASF subversion and git services commented on OPENWIRE-12: - Commit 12291ecbbbf5f8e4775d6fe98f03f4b89ff1bd6d in activemq-openwire's branch refs/heads/master from [~tabish121] [ https://git-wip-us.apache.org/repos/asf?p=activemq-openwire.git;h=12291ec ] OPENWIRE-12 Remove dependency on HawtBuf and replace with internal Buffer implementation. > Remove dependency on Hawtbuf > > > Key: OPENWIRE-12 > URL: https://issues.apache.org/jira/browse/OPENWIRE-12 > Project: ActiveMQ OpenWire > Issue Type: Improvement >Reporter: Timothy Bish >Assignee: Timothy Bish > > Replace Hawtbuf dependency with internal Buffer implementation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OPENWIRE-12) Remove dependency on Hawtbuf
Timothy Bish created OPENWIRE-12: Summary: Remove dependency on Hawtbuf Key: OPENWIRE-12 URL: https://issues.apache.org/jira/browse/OPENWIRE-12 Project: ActiveMQ OpenWire Issue Type: Improvement Reporter: Timothy Bish Assignee: Timothy Bish Replace Hawtbuf dependency with internal Buffer implementation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMQ-6161) Not able start active mq 5.13.0
[ https://issues.apache.org/jira/browse/AMQ-6161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134799#comment-15134799 ] Christopher L. Shannon commented on AMQ-6161: - It looks like you are using SunOS on sparc hardware (your original description says linux). Unfortunately, not too many developers have access to a workstation running in that environment so it will be hard to try and debug your problem. Contributions are welcome however, so I would suggest taking a look at the startup script and seeing if you can determine the problem and maybe propose a fix. You can also try mailing the users forum to see if anyone else is running with SunOS who might be able to help. > Not able start active mq 5.13.0 > --- > > Key: AMQ-6161 > URL: https://issues.apache.org/jira/browse/AMQ-6161 > Project: ActiveMQ > Issue Type: Bug >Reporter: Vijaya Ragavan >Priority: Blocker > Original Estimate: 4h > Remaining Estimate: 4h > > I am trying to install active mq 5.13.0 in linux machine and bit is 32. > When i try to execute it failed to start > -bash-4.1$ ./activemq start > Starting ActiveMQ Broker... > ./activemq[414]: exec: wrapper: cannot execute [Invalid argument] > In earlier version able to start with out any configuration change. > Here how to start newer version(5013.0) active mq -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ARTEMIS-390) ReplicationAddMessage java.lang.IllegalStateException: Cannot find add info
[
https://issues.apache.org/jira/browse/ARTEMIS-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134751#comment-15134751
]
Justin Bertram commented on ARTEMIS-390:
Can you provide details on the use-case here or (ideally) a reproducible
test-case? The IllegalStateException is thrown intentionally here when the
data can't be found. The real question is why the data isn't there at this
point. Please provide additional details or we'll just have to close this
JIRA. Thanks!
> ReplicationAddMessage java.lang.IllegalStateException: Cannot find add info
> ---
>
> Key: ARTEMIS-390
> URL: https://issues.apache.org/jira/browse/ARTEMIS-390
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 1.2.0
> Environment: production
>Reporter: Howard Nguyen
>
> {code}
> 00:05:12,746 WARN [org.apache.activemq.artemis.core.server] AMQ222086: error
> handling packet PACKET(ReplicationAddMessage)[type=91, channelID=2,
> packetObject=ReplicationAddMessage] for replication:
> java.lang.IllegalStateException: Cannot find add info 226853
> at
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.appendUpdateRecord(JournalImpl.java:756)
> [artemis-journal-1.2.0.jar:1.2.0]
> at
> org.apache.activemq.artemis.core.journal.impl.JournalBase.appendUpdateRecord(JournalBase.java:183)
> [artemis-journal-1.2.0.jar:1.2.0]
> at
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.appendUpdateRecord(JournalImpl.java:78)
> [artemis-journal-1.2.0.jar:1.2.0]
> at
> org.apache.activemq.artemis.core.journal.impl.JournalBase.appendUpdateRecord(JournalBase.java:129)
> [artemis-journal-1.2.0.jar:1.2.0]
> at
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.appendUpdateRecord(JournalImpl.java:78)
> [artemis-journal-1.2.0.jar:1.2.0]
> at
> org.apache.activemq.artemis.core.replication.ReplicationEndpoint.handleAppendAddRecord(ReplicationEndpoint.java:668)
> [artemis-server-1.2.0.jar:1.2.0]
> at
> org.apache.activemq.artemis.core.replication.ReplicationEndpoint.handlePacket(ReplicationEndpoint.java:167)
> [artemis-server-1.2.0.jar:1.2.0]
> at
> org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:594)
> [artemis-core-client-1.2.0.jar:1.2.0]
> at
> org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:368)
> [artemis-core-client-1.2.0.jar:1.2.0]
> at
> org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:350)
> [artemis-core-client-1.2.0.jar:1.2.0]
> at
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl$DelegatingBufferHandler.bufferReceived(ClientSessionFactoryImpl.java:1140)
> [artemis-core-client-1.2.0.jar:1.2.0]
> at
> org.apache.activemq.artemis.core.remoting.impl.netty.ActiveMQChannelHandler.channelRead(ActiveMQChannelHandler.java:68)
> [artemis-core-client-1.2.0.jar:1.2.0]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:308)
> [netty-all-4.0.32.Final.jar:4.0.32.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:294)
> [netty-all-4.0.32.Final.jar:4.0.32.Final]
> at
> io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:265)
> [netty-all-4.0.32.Final.jar:4.0.32.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:308)
> [netty-all-4.0.32.Final.jar:4.0.32.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:294)
> [netty-all-4.0.32.Final.jar:4.0.32.Final]
> at
> io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:846)
> [netty-all-4.0.32.Final.jar:4.0.32.Final]
> at
> io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:131)
> [netty-all-4.0.32.Final.jar:4.0.32.Final]
> at
> io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:511)
> [netty-all-4.0.32.Final.jar:4.0.32.Final]
> at
> io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468)
> [netty-all-4.0.32.Final.jar:4.0.32.Final]
> at
> io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382)
> [netty-all-4.0.32.Final.jar:4.0.32.Final]
> at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354)
> [netty-all-4.0.32.Final.jar:4.0.32.Final]
> at
> io.netty.util.concurrent.SingleThreadEventExecuto
[jira] [Commented] (ARTEMIS-389) See NPE on artemis backup log (ReplicationAddTXMessage)
[
https://issues.apache.org/jira/browse/ARTEMIS-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134745#comment-15134745
]
Justin Bertram commented on ARTEMIS-389:
Can you provide details on the use-case here or (ideally) a reproducible
test-case? The NPE is thrown intentionally here when the file is null or
unopened. The real question is why it's null/unopened at this point. Please
provide additional details or we'll just have to close this JIRA. Thanks!
> See NPE on artemis backup log (ReplicationAddTXMessage)
> ---
>
> Key: ARTEMIS-389
> URL: https://issues.apache.org/jira/browse/ARTEMIS-389
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 1.2.0
> Environment: production
>Reporter: Howard Nguyen
>
> {code}
> 00:02:11,891 WARN [org.apache.activemq.artemis.core.server] AMQ222086: error
> handling packet PACKET(ReplicationAddTXMessage)[type=92, channelID=2,
> packetObject=ReplicationAddTXMessage] for replication:
> java.lang.NullPointerException: File not opened, file=null
> at
> org.apache.activemq.artemis.core.io.aio.AIOSequentialFile.checkOpened(AIOSequentialFile.java:293)
> [artemis-journal-1.2.0.jar:1.2.0]
> at
> org.apache.activemq.artemis.core.io.aio.AIOSequentialFile.writeDirect(AIOSequentialFile.java:205)
> [artemis-journal-1.2.0.jar:1.2.0]
> at
> org.apache.activemq.artemis.core.io.AbstractSequentialFile.write(AbstractSequentialFile.java:256)
> [artemis-journal-1.2.0.jar:1.2.0]
> at
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.appendRecord(JournalImpl.java:2461)
> [artemis-journal-1.2.0.jar:1.2.0]
> at
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.appendAddRecordTransactional(JournalImpl.java:858)
> [artemis-journal-1.2.0.jar:1.2.0]
> at
> org.apache.activemq.artemis.core.journal.impl.JournalBase.appendAddRecordTransactional(JournalBase.java:145)
> [artemis-journal-1.2.0.jar:1.2.0]
> at
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.appendAddRecordTransactional(JournalImpl.java:78)
> [artemis-journal-1.2.0.jar:1.2.0]
> at
> org.apache.activemq.artemis.core.replication.ReplicationEndpoint.handleAppendAddTXRecord(ReplicationEndpoint.java:654)
> [artemis-server-1.2.0.jar:1.2.0]
> at
> org.apache.activemq.artemis.core.replication.ReplicationEndpoint.handlePacket(ReplicationEndpoint.java:170)
> [artemis-server-1.2.0.jar:1.2.0]
> at
> org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:594)
> [artemis-core-client-1.2.0.jar:1.2.0]
> at
> org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:368)
> [artemis-core-client-1.2.0.jar:1.2.0]
> at
> org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:350)
> [artemis-core-client-1.2.0.jar:1.2.0]
> at
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl$DelegatingBufferHandler.bufferReceived(ClientSessionFactoryImpl.java:1140)
> [artemis-core-client-1.2.0.jar:1.2.0]
> at
> org.apache.activemq.artemis.core.remoting.impl.netty.ActiveMQChannelHandler.channelRead(ActiveMQChannelHandler.java:68)
> [artemis-core-client-1.2.0.jar:1.2.0]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:308)
> [netty-all-4.0.32.Final.jar:4.0.32.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:294)
> [netty-all-4.0.32.Final.jar:4.0.32.Final]
> at
> io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:265)
> [netty-all-4.0.32.Final.jar:4.0.32.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:308)
> [netty-all-4.0.32.Final.jar:4.0.32.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:294)
> [netty-all-4.0.32.Final.jar:4.0.32.Final]
> at
> io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:846)
> [netty-all-4.0.32.Final.jar:4.0.32.Final]
> at
> io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:131)
> [netty-all-4.0.32.Final.jar:4.0.32.Final]
> at
> io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:511)
> [netty-all-4.0.32.Final.jar:4.0.32.Final]
> at
> io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468)
> [netty-all-4.0.32.Final.jar:4.0.32.Final]
> at
> io.netty.channel.nio.NioEventLo
[jira] [Closed] (ARTEMIS-387) Typos in error message
[ https://issues.apache.org/jira/browse/ARTEMIS-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-387. --- Resolution: Fixed Fix Version/s: 1.3.0 > Typos in error message > -- > > Key: ARTEMIS-387 > URL: https://issues.apache.org/jira/browse/ARTEMIS-387 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 1.2.0 >Reporter: Mike Hearn >Assignee: Justin Bertram >Priority: Trivial > Fix For: 1.3.0 > > > 15:04:46 57 BridgeImpl.connect: AMQ221026: Bridge XXX connected to > fowardingAddress=XXX. XXX does not have any bindings what means messages will > be ignored until a binding is created. > forwardingAddress not fowarding > "does not have any bindings, WHICH means" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMQ-6161) Not able start active mq 5.13.0
[ https://issues.apache.org/jira/browse/AMQ-6161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134729#comment-15134729 ] Vijaya Ragavan commented on AMQ-6161: -- I am using tar.gz(apache-activemq-5.13.0-bin.tar.gz) Please find my system configurations. -bash-4.1$ uname -a SunOS waivwebmq03 5.11 11.2 sun4v sparc sun4v -bash-4.1$ getconf LONG_BIT 32 -bash-4.1$ > Not able start active mq 5.13.0 > --- > > Key: AMQ-6161 > URL: https://issues.apache.org/jira/browse/AMQ-6161 > Project: ActiveMQ > Issue Type: Bug >Reporter: Vijaya Ragavan >Priority: Blocker > Original Estimate: 4h > Remaining Estimate: 4h > > I am trying to install active mq 5.13.0 in linux machine and bit is 32. > When i try to execute it failed to start > -bash-4.1$ ./activemq start > Starting ActiveMQ Broker... > ./activemq[414]: exec: wrapper: cannot execute [Invalid argument] > In earlier version able to start with out any configuration change. > Here how to start newer version(5013.0) active mq -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ARTEMIS-387) Typos in error message
[ https://issues.apache.org/jira/browse/ARTEMIS-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134717#comment-15134717 ] ASF GitHub Bot commented on ARTEMIS-387: Github user asfgit closed the pull request at: https://github.com/apache/activemq-artemis/pull/373 > Typos in error message > -- > > Key: ARTEMIS-387 > URL: https://issues.apache.org/jira/browse/ARTEMIS-387 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 1.2.0 >Reporter: Mike Hearn >Assignee: Justin Bertram >Priority: Trivial > > 15:04:46 57 BridgeImpl.connect: AMQ221026: Bridge XXX connected to > fowardingAddress=XXX. XXX does not have any bindings what means messages will > be ignored until a binding is created. > forwardingAddress not fowarding > "does not have any bindings, WHICH means" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ARTEMIS-387) Typos in error message
[ https://issues.apache.org/jira/browse/ARTEMIS-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134716#comment-15134716 ] ASF subversion and git services commented on ARTEMIS-387: - Commit 8dcea17f1101e705a124737ccea938eadc904368 in activemq-artemis's branch refs/heads/master from [~jbertram] [ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=8dcea17 ] ARTEMIS-387 grammar fix > Typos in error message > -- > > Key: ARTEMIS-387 > URL: https://issues.apache.org/jira/browse/ARTEMIS-387 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 1.2.0 >Reporter: Mike Hearn >Assignee: Justin Bertram >Priority: Trivial > > 15:04:46 57 BridgeImpl.connect: AMQ221026: Bridge XXX connected to > fowardingAddress=XXX. XXX does not have any bindings what means messages will > be ignored until a binding is created. > forwardingAddress not fowarding > "does not have any bindings, WHICH means" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ARTEMIS-390) ReplicationAddMessage java.lang.IllegalStateException: Cannot find add info
Howard Nguyen created ARTEMIS-390:
-
Summary: ReplicationAddMessage java.lang.IllegalStateException:
Cannot find add info
Key: ARTEMIS-390
URL: https://issues.apache.org/jira/browse/ARTEMIS-390
Project: ActiveMQ Artemis
Issue Type: Bug
Affects Versions: 1.2.0
Environment: production
Reporter: Howard Nguyen
{code}
00:05:12,746 WARN [org.apache.activemq.artemis.core.server] AMQ222086: error
handling packet PACKET(ReplicationAddMessage)[type=91, channelID=2,
packetObject=ReplicationAddMessage] for replication:
java.lang.IllegalStateException: Cannot find add info 226853
at
org.apache.activemq.artemis.core.journal.impl.JournalImpl.appendUpdateRecord(JournalImpl.java:756)
[artemis-journal-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis.core.journal.impl.JournalBase.appendUpdateRecord(JournalBase.java:183)
[artemis-journal-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis.core.journal.impl.JournalImpl.appendUpdateRecord(JournalImpl.java:78)
[artemis-journal-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis.core.journal.impl.JournalBase.appendUpdateRecord(JournalBase.java:129)
[artemis-journal-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis.core.journal.impl.JournalImpl.appendUpdateRecord(JournalImpl.java:78)
[artemis-journal-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis.core.replication.ReplicationEndpoint.handleAppendAddRecord(ReplicationEndpoint.java:668)
[artemis-server-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis.core.replication.ReplicationEndpoint.handlePacket(ReplicationEndpoint.java:167)
[artemis-server-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:594)
[artemis-core-client-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:368)
[artemis-core-client-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:350)
[artemis-core-client-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl$DelegatingBufferHandler.bufferReceived(ClientSessionFactoryImpl.java:1140)
[artemis-core-client-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis.core.remoting.impl.netty.ActiveMQChannelHandler.channelRead(ActiveMQChannelHandler.java:68)
[artemis-core-client-1.2.0.jar:1.2.0]
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:308)
[netty-all-4.0.32.Final.jar:4.0.32.Final]
at
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:294)
[netty-all-4.0.32.Final.jar:4.0.32.Final]
at
io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:265)
[netty-all-4.0.32.Final.jar:4.0.32.Final]
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:308)
[netty-all-4.0.32.Final.jar:4.0.32.Final]
at
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:294)
[netty-all-4.0.32.Final.jar:4.0.32.Final]
at
io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:846)
[netty-all-4.0.32.Final.jar:4.0.32.Final]
at
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:131)
[netty-all-4.0.32.Final.jar:4.0.32.Final]
at
io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:511)
[netty-all-4.0.32.Final.jar:4.0.32.Final]
at
io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468)
[netty-all-4.0.32.Final.jar:4.0.32.Final]
at
io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382)
[netty-all-4.0.32.Final.jar:4.0.32.Final]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354)
[netty-all-4.0.32.Final.jar:4.0.32.Final]
at
io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
[netty-all-4.0.32.Final.jar:4.0.32.Final]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_60]
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ARTEMIS-389) See NPE on artemis backup log (ReplicationAddTXMessage)
[
https://issues.apache.org/jira/browse/ARTEMIS-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard Nguyen updated ARTEMIS-389:
--
Description:
{code}
00:02:11,891 WARN [org.apache.activemq.artemis.core.server] AMQ222086: error
handling packet PACKET(ReplicationAddTXMessage)[type=92, channelID=2,
packetObject=ReplicationAddTXMessage] for replication:
java.lang.NullPointerException: File not opened, file=null
at
org.apache.activemq.artemis.core.io.aio.AIOSequentialFile.checkOpened(AIOSequentialFile.java:293)
[artemis-journal-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis.core.io.aio.AIOSequentialFile.writeDirect(AIOSequentialFile.java:205)
[artemis-journal-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis.core.io.AbstractSequentialFile.write(AbstractSequentialFile.java:256)
[artemis-journal-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis.core.journal.impl.JournalImpl.appendRecord(JournalImpl.java:2461)
[artemis-journal-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis.core.journal.impl.JournalImpl.appendAddRecordTransactional(JournalImpl.java:858)
[artemis-journal-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis.core.journal.impl.JournalBase.appendAddRecordTransactional(JournalBase.java:145)
[artemis-journal-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis.core.journal.impl.JournalImpl.appendAddRecordTransactional(JournalImpl.java:78)
[artemis-journal-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis.core.replication.ReplicationEndpoint.handleAppendAddTXRecord(ReplicationEndpoint.java:654)
[artemis-server-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis.core.replication.ReplicationEndpoint.handlePacket(ReplicationEndpoint.java:170)
[artemis-server-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:594)
[artemis-core-client-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:368)
[artemis-core-client-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:350)
[artemis-core-client-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl$DelegatingBufferHandler.bufferReceived(ClientSessionFactoryImpl.java:1140)
[artemis-core-client-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis.core.remoting.impl.netty.ActiveMQChannelHandler.channelRead(ActiveMQChannelHandler.java:68)
[artemis-core-client-1.2.0.jar:1.2.0]
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:308)
[netty-all-4.0.32.Final.jar:4.0.32.Final]
at
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:294)
[netty-all-4.0.32.Final.jar:4.0.32.Final]
at
io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:265)
[netty-all-4.0.32.Final.jar:4.0.32.Final]
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:308)
[netty-all-4.0.32.Final.jar:4.0.32.Final]
at
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:294)
[netty-all-4.0.32.Final.jar:4.0.32.Final]
at
io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:846)
[netty-all-4.0.32.Final.jar:4.0.32.Final]
at
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:131)
[netty-all-4.0.32.Final.jar:4.0.32.Final]
at
io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:511)
[netty-all-4.0.32.Final.jar:4.0.32.Final]
at
io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468)
[netty-all-4.0.32.Final.jar:4.0.32.Final]
at
io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382)
[netty-all-4.0.32.Final.jar:4.0.32.Final]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354)
[netty-all-4.0.32.Final.jar:4.0.32.Final]
at
io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
[netty-all-4.0.32.Final.jar:4.0.32.Final]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_60]
{code}
was:
{code}
00:02:11,891 WARN [org.apache.activemq.artemis.core.server] AMQ222086: error
handling packet PACKET(ReplicationAddTXMessage)[type=92, channelID=2,
packetObject=ReplicationAddTXMessage] for replication:
java.lang.NullPointerException: File not opened, file=null
at
org.apache.activemq.artemis.core.io.aio.AIOSequentialFile.checkOpened(AIOSequentialFile.java:293)
[artemis-journal-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis
[jira] [Created] (ARTEMIS-389) See NPE on artemis backup log (ReplicationAddTXMessage)
Howard Nguyen created ARTEMIS-389:
-
Summary: See NPE on artemis backup log (ReplicationAddTXMessage)
Key: ARTEMIS-389
URL: https://issues.apache.org/jira/browse/ARTEMIS-389
Project: ActiveMQ Artemis
Issue Type: Bug
Affects Versions: 1.2.0
Environment: production
Reporter: Howard Nguyen
{code}
00:02:11,891 WARN [org.apache.activemq.artemis.core.server] AMQ222086: error
handling packet PACKET(ReplicationAddTXMessage)[type=92, channelID=2,
packetObject=ReplicationAddTXMessage] for replication:
java.lang.NullPointerException: File not opened, file=null
at
org.apache.activemq.artemis.core.io.aio.AIOSequentialFile.checkOpened(AIOSequentialFile.java:293)
[artemis-journal-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis.core.io.aio.AIOSequentialFile.writeDirect(AIOSequentialFile.java:205)
[artemis-journal-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis.core.io.AbstractSequentialFile.write(AbstractSequentialFile.java:256)
[artemis-journal-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis.core.journal.impl.JournalImpl.appendRecord(JournalImpl.java:2461)
[artemis-journal-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis.core.journal.impl.JournalImpl.appendAddRecordTransactional(JournalImpl.java:858)
[artemis-journal-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis.core.journal.impl.JournalBase.appendAddRecordTransactional(JournalBase.java:145)
[artemis-journal-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis.core.journal.impl.JournalImpl.appendAddRecordTransactional(JournalImpl.java:78)
[artemis-journal-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis.core.replication.ReplicationEndpoint.handleAppendAddTXRecord(ReplicationEndpoint.java:654)
[artemis-server-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis.core.replication.ReplicationEndpoint.handlePacket(ReplicationEndpoint.java:170)
[artemis-server-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:594)
[artemis-core-client-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:368)
[artemis-core-client-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:350)
[artemis-core-client-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl$DelegatingBufferHandler.bufferReceived(ClientSessionFactoryImpl.java:1140)
[artemis-core-client-1.2.0.jar:1.2.0]
at
org.apache.activemq.artemis.core.remoting.impl.netty.ActiveMQChannelHandler.channelRead(ActiveMQChannelHandler.java:68)
[artemis-core-client-1.2.0.jar:1.2.0]
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:308)
[netty-all-4.0.32.Final.jar:4.0.32.Final]
at
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:294)
[netty-all-4.0.32.Final.jar:4.0.32.Final]
at
io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:265)
[netty-all-4.0.32.Final.jar:4.0.32.Final]
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:308)
[netty-all-4.0.32.Final.jar:4.0.32.Final]
at
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:294)
[netty-all-4.0.32.Final.jar:4.0.32.Final]
at
io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:846)
[netty-all-4.0.32.Final.jar:4.0.32.Final]
at
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:131)
[netty-all-4.0.32.Final.jar:4.0.32.Final]
at
io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:511)
[netty-all-4.0.32.Final.jar:4.0.32.Final]
at
io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468)
[netty-all-4.0.32.Final.jar:4.0.32.Final]
at
io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382)
[netty-all-4.0.32.Final.jar:4.0.32.Final]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354)
[netty-all-4.0.32.Final.jar:4.0.32.Final]
at
io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
[netty-all-4.0.32.Final.jar:4.0.32.Final]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_60]
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ARTEMIS-387) Typos in error message
[ https://issues.apache.org/jira/browse/ARTEMIS-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134604#comment-15134604 ] ASF GitHub Bot commented on ARTEMIS-387: GitHub user jbertram opened a pull request: https://github.com/apache/activemq-artemis/pull/373 ARTEMIS-387 grammar fix You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-387 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-artemis/pull/373.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 #373 commit 8dcea17f1101e705a124737ccea938eadc904368 Author: jbertram Date: 2016-02-05T18:13:11Z ARTEMIS-387 grammar fix > Typos in error message > -- > > Key: ARTEMIS-387 > URL: https://issues.apache.org/jira/browse/ARTEMIS-387 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 1.2.0 >Reporter: Mike Hearn >Assignee: Justin Bertram >Priority: Trivial > > 15:04:46 57 BridgeImpl.connect: AMQ221026: Bridge XXX connected to > fowardingAddress=XXX. XXX does not have any bindings what means messages will > be ignored until a binding is created. > forwardingAddress not fowarding > "does not have any bindings, WHICH means" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ARTEMIS-387) Typos in error message
[ https://issues.apache.org/jira/browse/ARTEMIS-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram reassigned ARTEMIS-387: -- Assignee: Justin Bertram > Typos in error message > -- > > Key: ARTEMIS-387 > URL: https://issues.apache.org/jira/browse/ARTEMIS-387 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 1.2.0 >Reporter: Mike Hearn >Assignee: Justin Bertram >Priority: Trivial > > 15:04:46 57 BridgeImpl.connect: AMQ221026: Bridge XXX connected to > fowardingAddress=XXX. XXX does not have any bindings what means messages will > be ignored until a binding is created. > forwardingAddress not fowarding > "does not have any bindings, WHICH means" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ARTEMIS-387) Typos in error message
[ https://issues.apache.org/jira/browse/ARTEMIS-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134589#comment-15134589 ] clebert suconic commented on ARTEMIS-387: - This is usually a 2 minutes thing. But if you are versed yet with github/pull-requests.. that's fine.. I will do it. > Typos in error message > -- > > Key: ARTEMIS-387 > URL: https://issues.apache.org/jira/browse/ARTEMIS-387 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 1.2.0 >Reporter: Mike Hearn >Priority: Trivial > > 15:04:46 57 BridgeImpl.connect: AMQ221026: Bridge XXX connected to > fowardingAddress=XXX. XXX does not have any bindings what means messages will > be ignored until a binding is created. > forwardingAddress not fowarding > "does not have any bindings, WHICH means" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMQ-6161) Not able start active mq 5.13.0
[ https://issues.apache.org/jira/browse/AMQ-6161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134521#comment-15134521 ] Christopher L. Shannon commented on AMQ-6161: - Are you using the tar.gz distribution? On my 64 bit Linux box I have no problems running with the tar.gz distribution which is meant for unix. > Not able start active mq 5.13.0 > --- > > Key: AMQ-6161 > URL: https://issues.apache.org/jira/browse/AMQ-6161 > Project: ActiveMQ > Issue Type: Bug >Reporter: Vijaya Ragavan >Priority: Blocker > Original Estimate: 4h > Remaining Estimate: 4h > > I am trying to install active mq 5.13.0 in linux machine and bit is 32. > When i try to execute it failed to start > -bash-4.1$ ./activemq start > Starting ActiveMQ Broker... > ./activemq[414]: exec: wrapper: cannot execute [Invalid argument] > In earlier version able to start with out any configuration change. > Here how to start newer version(5013.0) active mq -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ARTEMIS-387) Typos in error message
[ https://issues.apache.org/jira/browse/ARTEMIS-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134419#comment-15134419 ] Mike Hearn commented on ARTEMIS-387: Eventually, sure. Right now I'm under some time/delivery pressure on my existing project. If I end up needing to do a more substantial patch to Artemis I'll look at doing this at the same time, but I hope I can avoid that. > Typos in error message > -- > > Key: ARTEMIS-387 > URL: https://issues.apache.org/jira/browse/ARTEMIS-387 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 1.2.0 >Reporter: Mike Hearn >Priority: Trivial > > 15:04:46 57 BridgeImpl.connect: AMQ221026: Bridge XXX connected to > fowardingAddress=XXX. XXX does not have any bindings what means messages will > be ignored until a binding is created. > forwardingAddress not fowarding > "does not have any bindings, WHICH means" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMQ-6162) DLQ'd message does not get DLQ'd again until broker restart
[ https://issues.apache.org/jira/browse/AMQ-6162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jo Vandermeeren updated AMQ-6162: - Attachment: AMQ6162Test.java Unit test added > DLQ'd message does not get DLQ'd again until broker restart > --- > > Key: AMQ-6162 > URL: https://issues.apache.org/jira/browse/AMQ-6162 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.13.0 >Reporter: Jo Vandermeeren > Attachments: AMQ6162Test.java > > > Given the following setup: Q1 -> DLQ1 (dead letter for Q1) -> DLQ2 (dead > letter for Q2). > Sessions are transacted. > 1. Send message to Q1 > 2. Consume Q1 and rollback > 3. Message is DLQ'd to DLQ1 > 4. Consume DLQ1 and rollback > 5. Message is DLQ'd to DLQ2 > 6. Move message via JMX from DLQ2 to Q1 (QueueViewMBean.moveMessageTo()) > 7. Consume Q1 and rollback > 8. DLQ1 stays empty, message seems lost > If you restart the broker between step 5 and step 6, the message does get > DLQ'd to DLQ1 again. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMQ-6162) DLQ'd message does not get DLQ'd again until broker restart
Jo Vandermeeren created AMQ-6162: Summary: DLQ'd message does not get DLQ'd again until broker restart Key: AMQ-6162 URL: https://issues.apache.org/jira/browse/AMQ-6162 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.13.0 Reporter: Jo Vandermeeren Given the following setup: Q1 -> DLQ1 (dead letter for Q1) -> DLQ2 (dead letter for Q2). Sessions are transacted. 1. Send message to Q1 2. Consume Q1 and rollback 3. Message is DLQ'd to DLQ1 4. Consume DLQ1 and rollback 5. Message is DLQ'd to DLQ2 6. Move message via JMX from DLQ2 to Q1 (QueueViewMBean.moveMessageTo()) 7. Consume Q1 and rollback 8. DLQ1 stays empty, message seems lost If you restart the broker between step 5 and step 6, the message does get DLQ'd to DLQ1 again. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMQ-6156) ActiveMQConnection threads in parked state during startup
[
https://issues.apache.org/jira/browse/AMQ-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134434#comment-15134434
]
Timothy Bish commented on AMQ-6156:
---
Would need to check your tests, I just did this and it works as expected.
{code}
@Test
public void test() throws JMSException {
ActiveMQConnectionFactory cf = new ActiveMQConnectionFactory(
"failover:(tcp://localhost:61616)?" +
"maxReconnectAttempts=5&" +
"maxReconnectDelay=3&" +
"startupMaxReconnectAttempts=3&" +
"timeout=1000&randomize=false");
cf.createConnection().start();
}
{code}
{noformat}
2016-02-05 11:42:21,719 [ActiveMQ Task-1] - ERROR FailoverTransport
- Failed to connect to [tcp://localhost:61616] after: 3 attempt(s)
{noformat}
> ActiveMQConnection threads in parked state during startup
> -
>
> Key: AMQ-6156
> URL: https://issues.apache.org/jira/browse/AMQ-6156
> Project: ActiveMQ
> Issue Type: Bug
> Components: Connector
>Affects Versions: 5.11.1
> Environment: Linux
>Reporter: Ger Lawlor
>
> I've implemented a JMS producer using
> org.apache.activemq.ActiveMQConnectionFactory API. In the deployment they are
> 10 threads launched and each thread invokes the following sequence of methods
> which wrap around the ActiveMQConnection API.
> connector = new ActiveMQConnect();
> connector.setEndPointURL(primaryURL, secondaryURL, connectorQueryString);
> connector.setCredentials(userName, password);
> connector.initializeConnection();
> connector.setDestinationQueue(queueName);
> connector.addMessageToQueue(message);
> connector.sendMessageToQueue();
> The call to initializeConnection in turn invokes the following code which
> returns the connection
> 1) ActiveMQConnectionFactory connectionFactory = new
> ActiveMQConnectionFactory(m_userName, m_password, m_endPointUrl);
> 2) m_queueConnection = connectionFactory.createConnection();
> 3) m_queueConnection.start();
> However, (and potentially under load), a large % of the threads enter the
> parked state and stay there. The stack trace for these threads is as follows:
> java.lang.Thread.State: WAITING
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1841)
>
> at
> java.util.concurrent.ArrayBlockingQueue.take(ArrayBlockingQueue.java:341)
> at
> org.apache.activemq.transport.FutureResponse.getResult(FutureResponse.java:40)
>
> at
> org.apache.activemq.transport.ResponseCorrelator.request(ResponseCorrelator.java:80)
>
> at
> org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1195)
>
> at
> org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1289)
>
> at
> org.apache.activemq.ActiveMQConnection.start(ActiveMQConnection.java:456)
> at ActiveMQConnect.initializeConnection(ActiveMQConnect.java:63)
> The JMS producer connects using failover transport to an active/passive or
> primary/failover configuration.
> Is the problem being caused by the failover URL? The documentation seemed to
> indicate that the failover URL can be sent with format:
> failover:(tcp://amq01:61616,tcp://amq02:61616)?queryString
> Would appreciate any advice so I can resolve this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMQ-6156) ActiveMQConnection threads in parked state during startup
[ https://issues.apache.org/jira/browse/AMQ-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134423#comment-15134423 ] Ger Lawlor commented on AMQ-6156: - I've upgraded from 5.11.1 to 5.13.0 on suspicion that the error may have been because the failover transport parameter documentation only related to latest version. I also linked to the activemq-all.jar file from the 5.13.0 installation so as to ensure I was working with latest. I see the same outcome with invalid connect parameters as per URL above. > ActiveMQConnection threads in parked state during startup > - > > Key: AMQ-6156 > URL: https://issues.apache.org/jira/browse/AMQ-6156 > Project: ActiveMQ > Issue Type: Bug > Components: Connector >Affects Versions: 5.11.1 > Environment: Linux >Reporter: Ger Lawlor > > I've implemented a JMS producer using > org.apache.activemq.ActiveMQConnectionFactory API. In the deployment they are > 10 threads launched and each thread invokes the following sequence of methods > which wrap around the ActiveMQConnection API. > connector = new ActiveMQConnect(); > connector.setEndPointURL(primaryURL, secondaryURL, connectorQueryString); > connector.setCredentials(userName, password); > connector.initializeConnection(); > connector.setDestinationQueue(queueName); > connector.addMessageToQueue(message); > connector.sendMessageToQueue(); > The call to initializeConnection in turn invokes the following code which > returns the connection > 1) ActiveMQConnectionFactory connectionFactory = new > ActiveMQConnectionFactory(m_userName, m_password, m_endPointUrl); > 2) m_queueConnection = connectionFactory.createConnection(); > 3) m_queueConnection.start(); > However, (and potentially under load), a large % of the threads enter the > parked state and stay there. The stack trace for these threads is as follows: > java.lang.Thread.State: WAITING > at sun.misc.Unsafe.park(Native Method) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1841) > > at > java.util.concurrent.ArrayBlockingQueue.take(ArrayBlockingQueue.java:341) > at > org.apache.activemq.transport.FutureResponse.getResult(FutureResponse.java:40) > > at > org.apache.activemq.transport.ResponseCorrelator.request(ResponseCorrelator.java:80) > > at > org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1195) > > at > org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1289) > > at > org.apache.activemq.ActiveMQConnection.start(ActiveMQConnection.java:456) > at ActiveMQConnect.initializeConnection(ActiveMQConnect.java:63) > The JMS producer connects using failover transport to an active/passive or > primary/failover configuration. > Is the problem being caused by the failover URL? The documentation seemed to > indicate that the failover URL can be sent with format: > failover:(tcp://amq01:61616,tcp://amq02:61616)?queryString > Would appreciate any advice so I can resolve this issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMQ-6161) Not able start active mq 5.13.0
Vijaya Ragavan created AMQ-6161: Summary: Not able start active mq 5.13.0 Key: AMQ-6161 URL: https://issues.apache.org/jira/browse/AMQ-6161 Project: ActiveMQ Issue Type: Bug Reporter: Vijaya Ragavan Priority: Blocker I am trying to install active mq 5.13.0 in linux machine and bit is 32. When i try to execute it failed to start -bash-4.1$ ./activemq start Starting ActiveMQ Broker... ./activemq[414]: exec: wrapper: cannot execute [Invalid argument] In earlier version able to start with out any configuration change. Here how to start newer version(5013.0) active mq -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMQ-6156) ActiveMQConnection threads in parked state during startup
[
https://issues.apache.org/jira/browse/AMQ-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134369#comment-15134369
]
Ger Lawlor commented on AMQ-6156:
-
Hi,
I also tried the format you suggest e.g.
failover:(tcp://localhost:61616)?maxReconnectAttempts=5&maxReconnectDelay=3&startupMaxReconnectAttempts=3&timeout=1000&randomize=false
This is the error I get:
Invalid connect parameters: {startupMaxReconnectAttempts=3, timeout=1000}
Thus the reason for me moving them onto the tcp transport URL. I had the double
tcp localhost urls in their for primary/failover testing previously, so that
can be ignored. According to the docs, the above should work.
Thoughts?
Ger.
> ActiveMQConnection threads in parked state during startup
> -
>
> Key: AMQ-6156
> URL: https://issues.apache.org/jira/browse/AMQ-6156
> Project: ActiveMQ
> Issue Type: Bug
> Components: Connector
>Affects Versions: 5.11.1
> Environment: Linux
>Reporter: Ger Lawlor
>
> I've implemented a JMS producer using
> org.apache.activemq.ActiveMQConnectionFactory API. In the deployment they are
> 10 threads launched and each thread invokes the following sequence of methods
> which wrap around the ActiveMQConnection API.
> connector = new ActiveMQConnect();
> connector.setEndPointURL(primaryURL, secondaryURL, connectorQueryString);
> connector.setCredentials(userName, password);
> connector.initializeConnection();
> connector.setDestinationQueue(queueName);
> connector.addMessageToQueue(message);
> connector.sendMessageToQueue();
> The call to initializeConnection in turn invokes the following code which
> returns the connection
> 1) ActiveMQConnectionFactory connectionFactory = new
> ActiveMQConnectionFactory(m_userName, m_password, m_endPointUrl);
> 2) m_queueConnection = connectionFactory.createConnection();
> 3) m_queueConnection.start();
> However, (and potentially under load), a large % of the threads enter the
> parked state and stay there. The stack trace for these threads is as follows:
> java.lang.Thread.State: WAITING
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1841)
>
> at
> java.util.concurrent.ArrayBlockingQueue.take(ArrayBlockingQueue.java:341)
> at
> org.apache.activemq.transport.FutureResponse.getResult(FutureResponse.java:40)
>
> at
> org.apache.activemq.transport.ResponseCorrelator.request(ResponseCorrelator.java:80)
>
> at
> org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1195)
>
> at
> org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1289)
>
> at
> org.apache.activemq.ActiveMQConnection.start(ActiveMQConnection.java:456)
> at ActiveMQConnect.initializeConnection(ActiveMQConnect.java:63)
> The JMS producer connects using failover transport to an active/passive or
> primary/failover configuration.
> Is the problem being caused by the failover URL? The documentation seemed to
> indicate that the failover URL can be sent with format:
> failover:(tcp://amq01:61616,tcp://amq02:61616)?queryString
> Would appreciate any advice so I can resolve this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMQ-6156) ActiveMQConnection threads in parked state during startup
[
https://issues.apache.org/jira/browse/AMQ-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134321#comment-15134321
]
Timothy Bish commented on AMQ-6156:
---
Your URI is incorrect, the failover options don't get applied to each TCP
transport instance in the URI, try this:
{noformat}
failover:(tcp://localhost:61616)?maxReconnectAttempts=5&maxReconnectDelay=3&randomize=false&startupMaxReconnectAttempts=10&timeout=1000
{noformat}
I don't really know why you have the same address in there twice, no need for
two {{tcp://localhost:61616}} addresses in there.
> ActiveMQConnection threads in parked state during startup
> -
>
> Key: AMQ-6156
> URL: https://issues.apache.org/jira/browse/AMQ-6156
> Project: ActiveMQ
> Issue Type: Bug
> Components: Connector
>Affects Versions: 5.11.1
> Environment: Linux
>Reporter: Ger Lawlor
>
> I've implemented a JMS producer using
> org.apache.activemq.ActiveMQConnectionFactory API. In the deployment they are
> 10 threads launched and each thread invokes the following sequence of methods
> which wrap around the ActiveMQConnection API.
> connector = new ActiveMQConnect();
> connector.setEndPointURL(primaryURL, secondaryURL, connectorQueryString);
> connector.setCredentials(userName, password);
> connector.initializeConnection();
> connector.setDestinationQueue(queueName);
> connector.addMessageToQueue(message);
> connector.sendMessageToQueue();
> The call to initializeConnection in turn invokes the following code which
> returns the connection
> 1) ActiveMQConnectionFactory connectionFactory = new
> ActiveMQConnectionFactory(m_userName, m_password, m_endPointUrl);
> 2) m_queueConnection = connectionFactory.createConnection();
> 3) m_queueConnection.start();
> However, (and potentially under load), a large % of the threads enter the
> parked state and stay there. The stack trace for these threads is as follows:
> java.lang.Thread.State: WAITING
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1841)
>
> at
> java.util.concurrent.ArrayBlockingQueue.take(ArrayBlockingQueue.java:341)
> at
> org.apache.activemq.transport.FutureResponse.getResult(FutureResponse.java:40)
>
> at
> org.apache.activemq.transport.ResponseCorrelator.request(ResponseCorrelator.java:80)
>
> at
> org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1195)
>
> at
> org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1289)
>
> at
> org.apache.activemq.ActiveMQConnection.start(ActiveMQConnection.java:456)
> at ActiveMQConnect.initializeConnection(ActiveMQConnect.java:63)
> The JMS producer connects using failover transport to an active/passive or
> primary/failover configuration.
> Is the problem being caused by the failover URL? The documentation seemed to
> indicate that the failover URL can be sent with format:
> failover:(tcp://amq01:61616,tcp://amq02:61616)?queryString
> Would appreciate any advice so I can resolve this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (ARTEMIS-388) No obvious way to discover whether an embedded server actually started OK or not
[ https://issues.apache.org/jira/browse/ARTEMIS-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram reassigned ARTEMIS-388: -- Assignee: Justin Bertram > No obvious way to discover whether an embedded server actually started OK or > not > > > Key: ARTEMIS-388 > URL: https://issues.apache.org/jira/browse/ARTEMIS-388 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Mike Hearn >Assignee: Justin Bertram > > If I use the embedded Artemis API, then if the port it's listening on is > taken the server still "starts" correctly, but with the most important > component in a failed state! I would like to abort the startup of my app in > case something like this happens but I wasn't able to figure out from the > documentation how to actually check if all the requested > connectors/bridges/etc are all functioning correctly or if an exception was > thrown (I can see the exception in the logs, of course). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMQ-6156) ActiveMQConnection threads in parked state during startup
[
https://issues.apache.org/jira/browse/AMQ-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134306#comment-15134306
]
Ger Lawlor commented on AMQ-6156:
-
Hi Timothy,
I've started making changes in respect of your comments above to my AMQ
producer client to improve the failover transport handling.
In doing so I have added the following query parameters onto the failover URL
failover:(tcp://localhost:61616?startupMaxReconnectAttempts=10&timeout=1000,tcp://localhost:61616?startupMaxReconnectAttempts=10&timeout=1000)?maxReconnectAttempts=5&maxReconnectDelay=3&randomize=false
I am now getting an error where the connection fails due to incorrect connect
parameters {startupMaxReconnectAttempts=10, timeout=1000}
If you would prefer I open a new case for this issue then let me know, but I am
wondering if you've seen this before and have any ideas as to what is wrong -
all parameters being passed are listed as transport parameters on the failover
transport page: http://activemq.apache.org/failover-transport-reference.html
Thanks,
Ger.
> ActiveMQConnection threads in parked state during startup
> -
>
> Key: AMQ-6156
> URL: https://issues.apache.org/jira/browse/AMQ-6156
> Project: ActiveMQ
> Issue Type: Bug
> Components: Connector
>Affects Versions: 5.11.1
> Environment: Linux
>Reporter: Ger Lawlor
>
> I've implemented a JMS producer using
> org.apache.activemq.ActiveMQConnectionFactory API. In the deployment they are
> 10 threads launched and each thread invokes the following sequence of methods
> which wrap around the ActiveMQConnection API.
> connector = new ActiveMQConnect();
> connector.setEndPointURL(primaryURL, secondaryURL, connectorQueryString);
> connector.setCredentials(userName, password);
> connector.initializeConnection();
> connector.setDestinationQueue(queueName);
> connector.addMessageToQueue(message);
> connector.sendMessageToQueue();
> The call to initializeConnection in turn invokes the following code which
> returns the connection
> 1) ActiveMQConnectionFactory connectionFactory = new
> ActiveMQConnectionFactory(m_userName, m_password, m_endPointUrl);
> 2) m_queueConnection = connectionFactory.createConnection();
> 3) m_queueConnection.start();
> However, (and potentially under load), a large % of the threads enter the
> parked state and stay there. The stack trace for these threads is as follows:
> java.lang.Thread.State: WAITING
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1841)
>
> at
> java.util.concurrent.ArrayBlockingQueue.take(ArrayBlockingQueue.java:341)
> at
> org.apache.activemq.transport.FutureResponse.getResult(FutureResponse.java:40)
>
> at
> org.apache.activemq.transport.ResponseCorrelator.request(ResponseCorrelator.java:80)
>
> at
> org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1195)
>
> at
> org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1289)
>
> at
> org.apache.activemq.ActiveMQConnection.start(ActiveMQConnection.java:456)
> at ActiveMQConnect.initializeConnection(ActiveMQConnect.java:63)
> The JMS producer connects using failover transport to an active/passive or
> primary/failover configuration.
> Is the problem being caused by the failover URL? The documentation seemed to
> indicate that the failover URL can be sent with format:
> failover:(tcp://amq01:61616,tcp://amq02:61616)?queryString
> Would appreciate any advice so I can resolve this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ARTEMIS-355) Duplex bridges
[ https://issues.apache.org/jira/browse/ARTEMIS-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-355: Fix Version/s: 1.3.0 > Duplex bridges > -- > > Key: ARTEMIS-355 > URL: https://issues.apache.org/jira/browse/ARTEMIS-355 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: Broker >Affects Versions: 1.2.0 >Reporter: Mike Hearn >Assignee: Martyn Taylor > Fix For: 1.3.0 > > > I can't find any way to make an embedded artemis A connect to an embedded > artemis B such that B can send messages to A without connectivity at the TCP > level, e.g. due to firewall traversal. It'd be convenient if there was no > need for me to implement firewall punching myself. Apparently ActiveMQ can do > this using some sort of "duplex" attribute, but it's not in Artemis. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ARTEMIS-388) No obvious way to discover whether an embedded server actually started OK or not
Mike Hearn created ARTEMIS-388: -- Summary: No obvious way to discover whether an embedded server actually started OK or not Key: ARTEMIS-388 URL: https://issues.apache.org/jira/browse/ARTEMIS-388 Project: ActiveMQ Artemis Issue Type: Bug Reporter: Mike Hearn If I use the embedded Artemis API, then if the port it's listening on is taken the server still "starts" correctly, but with the most important component in a failed state! I would like to abort the startup of my app in case something like this happens but I wasn't able to figure out from the documentation how to actually check if all the requested connectors/bridges/etc are all functioning correctly or if an exception was thrown (I can see the exception in the logs, of course). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ARTEMIS-355) Duplex bridges
[ https://issues.apache.org/jira/browse/ARTEMIS-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134254#comment-15134254 ] Mike Hearn commented on ARTEMIS-355: Yes, my use case is to have separate servers some of which may be on different sides of a corporate firewall. Being able to connect out of the firewall and then exchange messages bidirectionally is something a raw socket can do - it's a shame that this feature is lost when using Artemis. I honestly had not even considered that it may work this way, and now I'm wondering what the best fix or workaround may be until this issue is implemented (if it ever is? seems to be low priority?) > Duplex bridges > -- > > Key: ARTEMIS-355 > URL: https://issues.apache.org/jira/browse/ARTEMIS-355 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: Broker >Affects Versions: 1.2.0 >Reporter: Mike Hearn >Assignee: Martyn Taylor > > I can't find any way to make an embedded artemis A connect to an embedded > artemis B such that B can send messages to A without connectivity at the TCP > level, e.g. due to firewall traversal. It'd be convenient if there was no > need for me to implement firewall punching myself. Apparently ActiveMQ can do > this using some sort of "duplex" attribute, but it's not in Artemis. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ARTEMIS-387) Typos in error message
[ https://issues.apache.org/jira/browse/ARTEMIS-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134235#comment-15134235 ] clebert suconic commented on ARTEMIS-387: - Nice candidate for a Pull Request. Can you do it? > Typos in error message > -- > > Key: ARTEMIS-387 > URL: https://issues.apache.org/jira/browse/ARTEMIS-387 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 1.2.0 >Reporter: Mike Hearn >Priority: Trivial > > 15:04:46 57 BridgeImpl.connect: AMQ221026: Bridge XXX connected to > fowardingAddress=XXX. XXX does not have any bindings what means messages will > be ignored until a binding is created. > forwardingAddress not fowarding > "does not have any bindings, WHICH means" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ARTEMIS-387) Typos in error message
Mike Hearn created ARTEMIS-387: -- Summary: Typos in error message Key: ARTEMIS-387 URL: https://issues.apache.org/jira/browse/ARTEMIS-387 Project: ActiveMQ Artemis Issue Type: Bug Affects Versions: 1.2.0 Reporter: Mike Hearn Priority: Trivial 15:04:46 57 BridgeImpl.connect: AMQ221026: Bridge XXX connected to fowardingAddress=XXX. XXX does not have any bindings what means messages will be ignored until a binding is created. forwardingAddress not fowarding "does not have any bindings, WHICH means" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMQ-6160) JDBC XA: NullPointerException on rollback in PREPARED_STATE when trying to unset the XID
[
https://issues.apache.org/jira/browse/AMQ-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens Hadlich updated AMQ-6160:
--
Description:
The messageId.getEntryLocator() gives null which leads to the NPE.
The NPE seems to lead to a db connection leak in conjunction with Apache
Commons DBCP. A workaround we applied is to configure the pool to remove this
"abandoned" connections (see
https://commons.apache.org/proper/commons-dbcp/configuration.html):
{noformat}
...
{noformat}
Example stacktrace for the NPE:
{noformat}
11:12:32.965 [messageListenerContainer-7] WARN c.a.d.xa.XAResourceTransaction
- XA resource 'atomikosFactorIn': rollback for XID
'3137322E31362E3231352E34312E746D30303030363030303435:3137322E31362E3231352E34312E746D313136'
raised -7: the XA resource has become unavailable
javax.transaction.xa.XAException: java.lang.NullPointerException
at
org.apache.activemq.TransactionContext.toXAException(TransactionContext.java:735)
~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.apache.activemq.TransactionContext.rollback(TransactionContext.java:497)
~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.datasource.xa.XAResourceTransaction.rollback(XAResourceTransaction.java:677)
~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.RollbackMessage.send(RollbackMessage.java:70)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.PropagationMessage.submit(PropagationMessage.java:83)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.Propagator$PropagatorThread.run(Propagator.java:79)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.Propagator.submitPropagationMessage(Propagator.java:58)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.CoordinatorStateHandler.rollbackFromWithinCallback(CoordinatorStateHandler.java:709)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.ActiveStateHandler$4.doRollback(ActiveStateHandler.java:213)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.CoordinatorStateHandler.rollbackWithAfterCompletionNotification(CoordinatorStateHandler.java:837)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.ActiveStateHandler.rollbackWithAfterCompletionNotification(ActiveStateHandler.java:49)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.ActiveStateHandler.prepare(ActiveStateHandler.java:208)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.CoordinatorImp.prepare(CoordinatorImp.java:681)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.CoordinatorImp.terminate(CoordinatorImp.java:975)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.CompositeTerminatorImp.commit(CompositeTerminatorImp.java:82)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.CompositeTransactionImp.commit(CompositeTransactionImp.java:336)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.jta.TransactionImp.commit(TransactionImp.java:190)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.jta.TransactionManagerImp.commit(TransactionManagerImp.java:436)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.jta.UserTransactionImp.commit(UserTransactionImp.java:107)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.transaction.jta.JtaTransactionManager.doCommit(JtaTransactionManager.java:1021)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:761)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:730)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:247)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1150)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1142)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:1039)
[
[jira] [Resolved] (AMQ-6157) Thread leak when failover fails to connect at startup
[
https://issues.apache.org/jira/browse/AMQ-6157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik resolved AMQ-6157.
---
Resolution: Not A Problem
You are right, the problem is not in the failover but in the JMS bridge, or the
use of both in combination. Since failover is not needed here it does not seem
like a real problem.
Thanks for your help
> Thread leak when failover fails to connect at startup
> -
>
> Key: AMQ-6157
> URL: https://issues.apache.org/jira/browse/AMQ-6157
> Project: ActiveMQ
> Issue Type: Bug
> Environment: Tomee plus 1.7.2 which includes ActiveMQ 5.10.0
> Linux tomee 3.13.0-49-generic #83-Ubuntu SMP Fri Apr 10 20:11:33 UTC 2015
> x86_64 x86_64 x86_64 GNU/Linux
> java version "1.8.0_66"
> Java(TM) SE Runtime Environment (build 1.8.0_66-b17)
> Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode)
>Reporter: Erik
> Attachments: broker-config.xml, jstack.txt, tomee.xml
>
>
> I have configured several brokers and sometimes one of them is not available
> when the application server is started.
> When left running the amount of threads slowly builds up, depending how often
> reconnect fails, and consumes more and more memory
> To reproduce I have deliberately configured failover with a host that is not
> reachable
> {code}
> failover:(tcp://host.not.found:1234?keepAlive=true&wireFormat.maxInactivityDuration=0&daemon=true)?maxReconnectAttempts=2&startupMaxReconnectAttempts=1)
> {code}
> When I start Tomee, AMQ is not able to connect as expected
> {code}
> Feb 04, 2016 1:13:27 PM
> org.apache.activemq.transport.failover.FailoverTransport doReconnect
> SEVERE: Failed to connect to
> [tcp://host.not.found:6523?keepAlive=true&wireFormat.maxInactivityDuration=0&daemon=true]
> after: 1 attempt(s)
> {code}
> For each reconnect attempt a new thread is created and left waiting for a
> lock. These threads seem to wait indefinately
> {code}
> "ActiveMQ Connection Executor: unconnected" #75 daemon prio=5 os_prio=0
> tid=0x7f083c04 nid=0xfaa waiting on condition [0x7f0824fc1000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0xc080aa78> (a
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
> at
> java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
> at
> java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (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:all-tabpanel ] Robbie Gemmell updated AMQ-6147: Description: Update proton to latest version (was: Update proton to latest version which includes some fixes for credit handling issues.) > 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 >Affects Versions: 5.13.0 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Minor > Fix For: 5.14.0 > > Attachments: AMQ-6147.patch > > > Update proton to latest version -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[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=15133965#comment-15133965 ] Robbie Gemmell commented on AMQ-6147: - Yep, planned to eventually, don't think I had added that yet when I originally made the patch. Also figured it could warrant changes in that area but haven't looked into it yet. > 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 >Affects Versions: 5.13.0 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Minor > Fix For: 5.14.0 > > Attachments: AMQ-6147.patch > > > Update proton to latest version which includes some fixes for credit handling > issues. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMQ-6160) JDBC XA: NullPointerException on rollback in PREPARED_STATE when trying to unset the XID
[
https://issues.apache.org/jira/browse/AMQ-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens Hadlich updated AMQ-6160:
--
Affects Version/s: 5.13.0
> JDBC XA: NullPointerException on rollback in PREPARED_STATE when trying to
> unset the XID
>
>
> Key: AMQ-6160
> URL: https://issues.apache.org/jira/browse/AMQ-6160
> Project: ActiveMQ
> Issue Type: Bug
> Components: JDBC
>Affects Versions: 5.12.1, 5.13.0
>Reporter: Jens Hadlich
>
> The messageId.getEntryLocator() gives null which leads to the NPE.
> The NPE seems to lead to a db connection leak in conjuction with dbcp. A
> workaround we applied is to configure the pool to remove this "abandoned"
> connections:
> {noformat}
>
> ...
>
>
>
>
>
> {noformat}
> Example stacktrace for the NPE:
> {noformat}
> 11:12:32.965 [messageListenerContainer-7] WARN
> c.a.d.xa.XAResourceTransaction - XA resource 'atomikosFactorIn': rollback for
> XID
> '3137322E31362E3231352E34312E746D30303030363030303435:3137322E31362E3231352E34312E746D313136'
> raised -7: the XA resource has become unavailable
> javax.transaction.xa.XAException: java.lang.NullPointerException
> at
> org.apache.activemq.TransactionContext.toXAException(TransactionContext.java:735)
> ~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> org.apache.activemq.TransactionContext.rollback(TransactionContext.java:497)
> ~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.datasource.xa.XAResourceTransaction.rollback(XAResourceTransaction.java:677)
> ~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.RollbackMessage.send(RollbackMessage.java:70)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.PropagationMessage.submit(PropagationMessage.java:83)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.Propagator$PropagatorThread.run(Propagator.java:79)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.Propagator.submitPropagationMessage(Propagator.java:58)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CoordinatorStateHandler.rollbackFromWithinCallback(CoordinatorStateHandler.java:709)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.ActiveStateHandler$4.doRollback(ActiveStateHandler.java:213)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CoordinatorStateHandler.rollbackWithAfterCompletionNotification(CoordinatorStateHandler.java:837)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.ActiveStateHandler.rollbackWithAfterCompletionNotification(ActiveStateHandler.java:49)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.ActiveStateHandler.prepare(ActiveStateHandler.java:208)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CoordinatorImp.prepare(CoordinatorImp.java:681)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CoordinatorImp.terminate(CoordinatorImp.java:975)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CompositeTerminatorImp.commit(CompositeTerminatorImp.java:82)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CompositeTransactionImp.commit(CompositeTransactionImp.java:336)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.jta.TransactionImp.commit(TransactionImp.java:190)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.jta.TransactionManagerImp.commit(TransactionManagerImp.java:436)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.jta.UserTransactionImp.commit(UserTransactionImp.java:107)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> org.springframework.transaction.jta.JtaTransactionManager.doCommit(JtaTransactionManager.java:1021)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:761)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:730)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:247)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> org.s
[jira] [Updated] (AMQ-6160) JDBC XA: NullPointerException on rollback in PREPARED_STATE when trying to unset the XID
[
https://issues.apache.org/jira/browse/AMQ-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens Hadlich updated AMQ-6160:
--
Description:
The messageId.getEntryLocator() gives null which leads to the NPE.
The NPE seems to lead to a db connection leak in conjuction with dbcp. A
workaround we applied is to configure the pool to remove this "abandoned"
connections:
{noformat}
...
{noformat}
Example stacktrace for the NPE:
{noformat}
11:12:32.965 [messageListenerContainer-7] WARN c.a.d.xa.XAResourceTransaction
- XA resource 'atomikosFactorIn': rollback for XID
'3137322E31362E3231352E34312E746D30303030363030303435:3137322E31362E3231352E34312E746D313136'
raised -7: the XA resource has become unavailable
javax.transaction.xa.XAException: java.lang.NullPointerException
at
org.apache.activemq.TransactionContext.toXAException(TransactionContext.java:735)
~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.apache.activemq.TransactionContext.rollback(TransactionContext.java:497)
~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.datasource.xa.XAResourceTransaction.rollback(XAResourceTransaction.java:677)
~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.RollbackMessage.send(RollbackMessage.java:70)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.PropagationMessage.submit(PropagationMessage.java:83)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.Propagator$PropagatorThread.run(Propagator.java:79)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.Propagator.submitPropagationMessage(Propagator.java:58)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.CoordinatorStateHandler.rollbackFromWithinCallback(CoordinatorStateHandler.java:709)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.ActiveStateHandler$4.doRollback(ActiveStateHandler.java:213)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.CoordinatorStateHandler.rollbackWithAfterCompletionNotification(CoordinatorStateHandler.java:837)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.ActiveStateHandler.rollbackWithAfterCompletionNotification(ActiveStateHandler.java:49)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.ActiveStateHandler.prepare(ActiveStateHandler.java:208)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.CoordinatorImp.prepare(CoordinatorImp.java:681)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.CoordinatorImp.terminate(CoordinatorImp.java:975)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.CompositeTerminatorImp.commit(CompositeTerminatorImp.java:82)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.CompositeTransactionImp.commit(CompositeTransactionImp.java:336)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.jta.TransactionImp.commit(TransactionImp.java:190)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.jta.TransactionManagerImp.commit(TransactionManagerImp.java:436)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.jta.UserTransactionImp.commit(UserTransactionImp.java:107)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.transaction.jta.JtaTransactionManager.doCommit(JtaTransactionManager.java:1021)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:761)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:730)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:247)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1150)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1142)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:1039)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at java.lang.Thread.run(Thread.java:74
[jira] [Updated] (AMQ-6160) JDBC XA: NullPointerException on rollback in PREPARED_STATE when trying to unset the XID
[
https://issues.apache.org/jira/browse/AMQ-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens Hadlich updated AMQ-6160:
--
Description:
The messageId.getEntryLocator() gives null which leads to the NPE.
The NPE seems to lead to a db connection leak in conjuction with dbcp. A
workaround we applied is to configure the pool to remove this "abandoned"
connections:
{noformat}
...
{normat}
Example stacktrace for the NPA:
{noformat}
11:12:32.965 [messageListenerContainer-7] WARN c.a.d.xa.XAResourceTransaction
- XA resource 'atomikosFactorIn': rollback for XID
'3137322E31362E3231352E34312E746D30303030363030303435:3137322E31362E3231352E34312E746D313136'
raised -7: the XA resource has become unavailable
javax.transaction.xa.XAException: java.lang.NullPointerException
at
org.apache.activemq.TransactionContext.toXAException(TransactionContext.java:735)
~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.apache.activemq.TransactionContext.rollback(TransactionContext.java:497)
~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.datasource.xa.XAResourceTransaction.rollback(XAResourceTransaction.java:677)
~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.RollbackMessage.send(RollbackMessage.java:70)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.PropagationMessage.submit(PropagationMessage.java:83)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.Propagator$PropagatorThread.run(Propagator.java:79)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.Propagator.submitPropagationMessage(Propagator.java:58)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.CoordinatorStateHandler.rollbackFromWithinCallback(CoordinatorStateHandler.java:709)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.ActiveStateHandler$4.doRollback(ActiveStateHandler.java:213)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.CoordinatorStateHandler.rollbackWithAfterCompletionNotification(CoordinatorStateHandler.java:837)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.ActiveStateHandler.rollbackWithAfterCompletionNotification(ActiveStateHandler.java:49)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.ActiveStateHandler.prepare(ActiveStateHandler.java:208)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.CoordinatorImp.prepare(CoordinatorImp.java:681)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.CoordinatorImp.terminate(CoordinatorImp.java:975)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.CompositeTerminatorImp.commit(CompositeTerminatorImp.java:82)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.CompositeTransactionImp.commit(CompositeTransactionImp.java:336)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.jta.TransactionImp.commit(TransactionImp.java:190)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.jta.TransactionManagerImp.commit(TransactionManagerImp.java:436)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.jta.UserTransactionImp.commit(UserTransactionImp.java:107)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.transaction.jta.JtaTransactionManager.doCommit(JtaTransactionManager.java:1021)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:761)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:730)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:247)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1150)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1142)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:1039)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at java.lang.Thread.run(Thread.java:745)
[jira] [Updated] (AMQ-6160) JDBC XA: NullPointerException on rollback in PREPARED_STATE when trying to unset the XID
[
https://issues.apache.org/jira/browse/AMQ-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens Hadlich updated AMQ-6160:
--
Description:
The messageId.getEntryLocator() gives null which leads to the NPE.
The NPE seems to lead to a db connection leak in conjuction with dbcp. A
workaround we applied is to configure the pool to remove this "abandoned"
connections:
{noformat}
...
{normat}
Example stacktrace:
{noformat}
11:12:32.965 [messageListenerContainer-7] WARN c.a.d.xa.XAResourceTransaction
- XA resource 'atomikosFactorIn': rollback for XID
'3137322E31362E3231352E34312E746D30303030363030303435:3137322E31362E3231352E34312E746D313136'
raised -7: the XA resource has become unavailable
javax.transaction.xa.XAException: java.lang.NullPointerException
at
org.apache.activemq.TransactionContext.toXAException(TransactionContext.java:735)
~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.apache.activemq.TransactionContext.rollback(TransactionContext.java:497)
~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.datasource.xa.XAResourceTransaction.rollback(XAResourceTransaction.java:677)
~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.RollbackMessage.send(RollbackMessage.java:70)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.PropagationMessage.submit(PropagationMessage.java:83)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.Propagator$PropagatorThread.run(Propagator.java:79)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.Propagator.submitPropagationMessage(Propagator.java:58)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.CoordinatorStateHandler.rollbackFromWithinCallback(CoordinatorStateHandler.java:709)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.ActiveStateHandler$4.doRollback(ActiveStateHandler.java:213)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.CoordinatorStateHandler.rollbackWithAfterCompletionNotification(CoordinatorStateHandler.java:837)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.ActiveStateHandler.rollbackWithAfterCompletionNotification(ActiveStateHandler.java:49)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.ActiveStateHandler.prepare(ActiveStateHandler.java:208)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.CoordinatorImp.prepare(CoordinatorImp.java:681)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.CoordinatorImp.terminate(CoordinatorImp.java:975)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.CompositeTerminatorImp.commit(CompositeTerminatorImp.java:82)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.CompositeTransactionImp.commit(CompositeTransactionImp.java:336)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.jta.TransactionImp.commit(TransactionImp.java:190)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.jta.TransactionManagerImp.commit(TransactionManagerImp.java:436)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.jta.UserTransactionImp.commit(UserTransactionImp.java:107)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.transaction.jta.JtaTransactionManager.doCommit(JtaTransactionManager.java:1021)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:761)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:730)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:247)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1150)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1142)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:1039)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at java.lang.Thread.run(Thread.java:745) [na:1.7.0_76
[jira] [Comment Edited] (AMQ-6160) JDBC XA: NullPointerException on rollback in PREPARED_STATE when trying to unset the XID
[
https://issues.apache.org/jira/browse/AMQ-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15133904#comment-15133904
]
Jens Hadlich edited comment on AMQ-6160 at 2/5/16 9:48 AM:
---
Actually, I'm not quite sure why the entryLocator becomes NULL. Could you
please give me a hint on that?
*Proposed solution*: Use {{messageId.getFutureOrSequenceLong()}} to get the
sequence id in case the entryLocator is NULL.
See: https://github.com/apache/activemq/pull/167
was (Author: jenshadlich):
Actually, I'm not quite sure why the entryLocator becomes NULL. Could you
please give me a hint on that?
Proposed solution: Use {{messageId.getFutureOrSequenceLong()}} to get the
sequence id in case the entryLocator is NULL.
See: https://github.com/apache/activemq/pull/167
> JDBC XA: NullPointerException on rollback in PREPARED_STATE when trying to
> unset the XID
>
>
> Key: AMQ-6160
> URL: https://issues.apache.org/jira/browse/AMQ-6160
> Project: ActiveMQ
> Issue Type: Bug
> Components: JDBC
>Affects Versions: 5.12.1
>Reporter: Jens Hadlich
>
> The messageId.getEntryLocator() gives null which leads to the NPE.
> Example stacktrace:
> {noformat}
> 11:12:32.965 [messageListenerContainer-7] WARN
> c.a.d.xa.XAResourceTransaction - XA resource 'atomikosFactorIn': rollback for
> XID
> '3137322E31362E3231352E34312E746D30303030363030303435:3137322E31362E3231352E34312E746D313136'
> raised -7: the XA resource has become unavailable
> javax.transaction.xa.XAException: java.lang.NullPointerException
> at
> org.apache.activemq.TransactionContext.toXAException(TransactionContext.java:735)
> ~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> org.apache.activemq.TransactionContext.rollback(TransactionContext.java:497)
> ~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.datasource.xa.XAResourceTransaction.rollback(XAResourceTransaction.java:677)
> ~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.RollbackMessage.send(RollbackMessage.java:70)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.PropagationMessage.submit(PropagationMessage.java:83)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.Propagator$PropagatorThread.run(Propagator.java:79)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.Propagator.submitPropagationMessage(Propagator.java:58)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CoordinatorStateHandler.rollbackFromWithinCallback(CoordinatorStateHandler.java:709)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.ActiveStateHandler$4.doRollback(ActiveStateHandler.java:213)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CoordinatorStateHandler.rollbackWithAfterCompletionNotification(CoordinatorStateHandler.java:837)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.ActiveStateHandler.rollbackWithAfterCompletionNotification(ActiveStateHandler.java:49)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.ActiveStateHandler.prepare(ActiveStateHandler.java:208)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CoordinatorImp.prepare(CoordinatorImp.java:681)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CoordinatorImp.terminate(CoordinatorImp.java:975)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CompositeTerminatorImp.commit(CompositeTerminatorImp.java:82)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CompositeTransactionImp.commit(CompositeTransactionImp.java:336)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.jta.TransactionImp.commit(TransactionImp.java:190)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.jta.TransactionManagerImp.commit(TransactionManagerImp.java:436)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.jta.UserTransactionImp.commit(UserTransactionImp.java:107)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> org.springframework.transaction.jta.JtaTransactionManager.doCommit(JtaTransactionManager.java:1021)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:761)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> org.springframework.tra
[jira] [Comment Edited] (AMQ-6160) JDBC XA: NullPointerException on rollback in PREPARED_STATE when trying to unset the XID
[
https://issues.apache.org/jira/browse/AMQ-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15133904#comment-15133904
]
Jens Hadlich edited comment on AMQ-6160 at 2/5/16 9:48 AM:
---
Actually, I'm not quite sure why the entryLocator becomes NULL. Could you
please give me a hint on that?
Proposed solution: Use {{messageId.getFutureOrSequenceLong()}} to get the
sequence id in case the entryLocator is NULL.
See: https://github.com/apache/activemq/pull/167
was (Author: jenshadlich):
Actually, I'm not quite sure why the entryLocator becomes NULL. Could you
please give me a hint on that?
Proposed solution: Use messageId.getFutureOrSequenceLong() to get the sequence
id.
See: https://github.com/apache/activemq/pull/167
> JDBC XA: NullPointerException on rollback in PREPARED_STATE when trying to
> unset the XID
>
>
> Key: AMQ-6160
> URL: https://issues.apache.org/jira/browse/AMQ-6160
> Project: ActiveMQ
> Issue Type: Bug
> Components: JDBC
>Affects Versions: 5.12.1
>Reporter: Jens Hadlich
>
> The messageId.getEntryLocator() gives null which leads to the NPE.
> Example stacktrace:
> {noformat}
> 11:12:32.965 [messageListenerContainer-7] WARN
> c.a.d.xa.XAResourceTransaction - XA resource 'atomikosFactorIn': rollback for
> XID
> '3137322E31362E3231352E34312E746D30303030363030303435:3137322E31362E3231352E34312E746D313136'
> raised -7: the XA resource has become unavailable
> javax.transaction.xa.XAException: java.lang.NullPointerException
> at
> org.apache.activemq.TransactionContext.toXAException(TransactionContext.java:735)
> ~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> org.apache.activemq.TransactionContext.rollback(TransactionContext.java:497)
> ~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.datasource.xa.XAResourceTransaction.rollback(XAResourceTransaction.java:677)
> ~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.RollbackMessage.send(RollbackMessage.java:70)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.PropagationMessage.submit(PropagationMessage.java:83)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.Propagator$PropagatorThread.run(Propagator.java:79)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.Propagator.submitPropagationMessage(Propagator.java:58)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CoordinatorStateHandler.rollbackFromWithinCallback(CoordinatorStateHandler.java:709)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.ActiveStateHandler$4.doRollback(ActiveStateHandler.java:213)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CoordinatorStateHandler.rollbackWithAfterCompletionNotification(CoordinatorStateHandler.java:837)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.ActiveStateHandler.rollbackWithAfterCompletionNotification(ActiveStateHandler.java:49)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.ActiveStateHandler.prepare(ActiveStateHandler.java:208)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CoordinatorImp.prepare(CoordinatorImp.java:681)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CoordinatorImp.terminate(CoordinatorImp.java:975)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CompositeTerminatorImp.commit(CompositeTerminatorImp.java:82)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CompositeTransactionImp.commit(CompositeTransactionImp.java:336)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.jta.TransactionImp.commit(TransactionImp.java:190)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.jta.TransactionManagerImp.commit(TransactionManagerImp.java:436)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.jta.UserTransactionImp.commit(UserTransactionImp.java:107)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> org.springframework.transaction.jta.JtaTransactionManager.doCommit(JtaTransactionManager.java:1021)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:761)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> org.springframework.transaction.support.AbstractPlatformTransa
[jira] [Comment Edited] (AMQ-6160) JDBC XA: NullPointerException on rollback in PREPARED_STATE when trying to unset the XID
[
https://issues.apache.org/jira/browse/AMQ-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15133904#comment-15133904
]
Jens Hadlich edited comment on AMQ-6160 at 2/5/16 9:47 AM:
---
Actually, I'm not quite sure why the entryLocator becomes NULL. Could you
please give me a hint on that?
Proposed solution: Use messageId.getFutureOrSequenceLong() to get the sequence
id.
See: https://github.com/apache/activemq/pull/167
was (Author: jenshadlich):
Actually I'm not quite sure why the entryLocator becomes NULL.
Proposed solution: Use messageId.getFutureOrSequenceLong() to get the sequence
id.
See: https://github.com/apache/activemq/pull/167
> JDBC XA: NullPointerException on rollback in PREPARED_STATE when trying to
> unset the XID
>
>
> Key: AMQ-6160
> URL: https://issues.apache.org/jira/browse/AMQ-6160
> Project: ActiveMQ
> Issue Type: Bug
> Components: JDBC
>Affects Versions: 5.12.1
>Reporter: Jens Hadlich
>
> The messageId.getEntryLocator() gives null which leads to the NPE.
> Example stacktrace:
> {noformat}
> 11:12:32.965 [messageListenerContainer-7] WARN
> c.a.d.xa.XAResourceTransaction - XA resource 'atomikosFactorIn': rollback for
> XID
> '3137322E31362E3231352E34312E746D30303030363030303435:3137322E31362E3231352E34312E746D313136'
> raised -7: the XA resource has become unavailable
> javax.transaction.xa.XAException: java.lang.NullPointerException
> at
> org.apache.activemq.TransactionContext.toXAException(TransactionContext.java:735)
> ~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> org.apache.activemq.TransactionContext.rollback(TransactionContext.java:497)
> ~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.datasource.xa.XAResourceTransaction.rollback(XAResourceTransaction.java:677)
> ~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.RollbackMessage.send(RollbackMessage.java:70)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.PropagationMessage.submit(PropagationMessage.java:83)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.Propagator$PropagatorThread.run(Propagator.java:79)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.Propagator.submitPropagationMessage(Propagator.java:58)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CoordinatorStateHandler.rollbackFromWithinCallback(CoordinatorStateHandler.java:709)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.ActiveStateHandler$4.doRollback(ActiveStateHandler.java:213)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CoordinatorStateHandler.rollbackWithAfterCompletionNotification(CoordinatorStateHandler.java:837)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.ActiveStateHandler.rollbackWithAfterCompletionNotification(ActiveStateHandler.java:49)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.ActiveStateHandler.prepare(ActiveStateHandler.java:208)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CoordinatorImp.prepare(CoordinatorImp.java:681)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CoordinatorImp.terminate(CoordinatorImp.java:975)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CompositeTerminatorImp.commit(CompositeTerminatorImp.java:82)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CompositeTransactionImp.commit(CompositeTransactionImp.java:336)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.jta.TransactionImp.commit(TransactionImp.java:190)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.jta.TransactionManagerImp.commit(TransactionManagerImp.java:436)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.jta.UserTransactionImp.commit(UserTransactionImp.java:107)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> org.springframework.transaction.jta.JtaTransactionManager.doCommit(JtaTransactionManager.java:1021)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:761)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:730)
> [messaging-t
[jira] [Comment Edited] (AMQ-6160) JDBC XA: NullPointerException on rollback in PREPARED_STATE when trying to unset the XID
[
https://issues.apache.org/jira/browse/AMQ-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15133904#comment-15133904
]
Jens Hadlich edited comment on AMQ-6160 at 2/5/16 9:46 AM:
---
Actually I'm not quite sure why the entryLocator becomes NULL.
Proposed solution: Use messageId.getFutureOrSequenceLong() to get the sequence
id.
See: https://github.com/apache/activemq/pull/167
was (Author: jenshadlich):
Proposed solution: Use messageId.getFutureOrSequenceLong() to get the sequence
id.
See: https://github.com/apache/activemq/pull/167
> JDBC XA: NullPointerException on rollback in PREPARED_STATE when trying to
> unset the XID
>
>
> Key: AMQ-6160
> URL: https://issues.apache.org/jira/browse/AMQ-6160
> Project: ActiveMQ
> Issue Type: Bug
> Components: JDBC
>Affects Versions: 5.12.1
>Reporter: Jens Hadlich
>
> The messageId.getEntryLocator() gives null which leads to the NPE.
> Example stacktrace:
> {noformat}
> 11:12:32.965 [messageListenerContainer-7] WARN
> c.a.d.xa.XAResourceTransaction - XA resource 'atomikosFactorIn': rollback for
> XID
> '3137322E31362E3231352E34312E746D30303030363030303435:3137322E31362E3231352E34312E746D313136'
> raised -7: the XA resource has become unavailable
> javax.transaction.xa.XAException: java.lang.NullPointerException
> at
> org.apache.activemq.TransactionContext.toXAException(TransactionContext.java:735)
> ~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> org.apache.activemq.TransactionContext.rollback(TransactionContext.java:497)
> ~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.datasource.xa.XAResourceTransaction.rollback(XAResourceTransaction.java:677)
> ~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.RollbackMessage.send(RollbackMessage.java:70)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.PropagationMessage.submit(PropagationMessage.java:83)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.Propagator$PropagatorThread.run(Propagator.java:79)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.Propagator.submitPropagationMessage(Propagator.java:58)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CoordinatorStateHandler.rollbackFromWithinCallback(CoordinatorStateHandler.java:709)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.ActiveStateHandler$4.doRollback(ActiveStateHandler.java:213)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CoordinatorStateHandler.rollbackWithAfterCompletionNotification(CoordinatorStateHandler.java:837)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.ActiveStateHandler.rollbackWithAfterCompletionNotification(ActiveStateHandler.java:49)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.ActiveStateHandler.prepare(ActiveStateHandler.java:208)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CoordinatorImp.prepare(CoordinatorImp.java:681)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CoordinatorImp.terminate(CoordinatorImp.java:975)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CompositeTerminatorImp.commit(CompositeTerminatorImp.java:82)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CompositeTransactionImp.commit(CompositeTransactionImp.java:336)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.jta.TransactionImp.commit(TransactionImp.java:190)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.jta.TransactionManagerImp.commit(TransactionManagerImp.java:436)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.jta.UserTransactionImp.commit(UserTransactionImp.java:107)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> org.springframework.transaction.jta.JtaTransactionManager.doCommit(JtaTransactionManager.java:1021)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:761)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:730)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> org.springframework.jms.listener.AbstractPollingMessageList
[jira] [Comment Edited] (AMQ-6160) JDBC XA: NullPointerException on rollback in PREPARED_STATE when trying to unset the XID
[
https://issues.apache.org/jira/browse/AMQ-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15133904#comment-15133904
]
Jens Hadlich edited comment on AMQ-6160 at 2/5/16 9:45 AM:
---
Proposed solution: Use messageId.getFutureOrSequenceLong() to get the sequence
id.
See: https://github.com/apache/activemq/pull/167
was (Author: jenshadlich):
Proposed solution: Use messageId.getFutureOrSequenceLong() to get the sequence
id.
> JDBC XA: NullPointerException on rollback in PREPARED_STATE when trying to
> unset the XID
>
>
> Key: AMQ-6160
> URL: https://issues.apache.org/jira/browse/AMQ-6160
> Project: ActiveMQ
> Issue Type: Bug
> Components: JDBC
>Affects Versions: 5.12.1
>Reporter: Jens Hadlich
>
> The messageId.getEntryLocator() gives null which leads to the NPE.
> Example stacktrace:
> {noformat}
> 11:12:32.965 [messageListenerContainer-7] WARN
> c.a.d.xa.XAResourceTransaction - XA resource 'atomikosFactorIn': rollback for
> XID
> '3137322E31362E3231352E34312E746D30303030363030303435:3137322E31362E3231352E34312E746D313136'
> raised -7: the XA resource has become unavailable
> javax.transaction.xa.XAException: java.lang.NullPointerException
> at
> org.apache.activemq.TransactionContext.toXAException(TransactionContext.java:735)
> ~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> org.apache.activemq.TransactionContext.rollback(TransactionContext.java:497)
> ~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.datasource.xa.XAResourceTransaction.rollback(XAResourceTransaction.java:677)
> ~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.RollbackMessage.send(RollbackMessage.java:70)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.PropagationMessage.submit(PropagationMessage.java:83)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.Propagator$PropagatorThread.run(Propagator.java:79)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.Propagator.submitPropagationMessage(Propagator.java:58)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CoordinatorStateHandler.rollbackFromWithinCallback(CoordinatorStateHandler.java:709)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.ActiveStateHandler$4.doRollback(ActiveStateHandler.java:213)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CoordinatorStateHandler.rollbackWithAfterCompletionNotification(CoordinatorStateHandler.java:837)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.ActiveStateHandler.rollbackWithAfterCompletionNotification(ActiveStateHandler.java:49)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.ActiveStateHandler.prepare(ActiveStateHandler.java:208)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CoordinatorImp.prepare(CoordinatorImp.java:681)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CoordinatorImp.terminate(CoordinatorImp.java:975)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CompositeTerminatorImp.commit(CompositeTerminatorImp.java:82)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CompositeTransactionImp.commit(CompositeTransactionImp.java:336)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.jta.TransactionImp.commit(TransactionImp.java:190)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.jta.TransactionManagerImp.commit(TransactionManagerImp.java:436)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.jta.UserTransactionImp.commit(UserTransactionImp.java:107)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> org.springframework.transaction.jta.JtaTransactionManager.doCommit(JtaTransactionManager.java:1021)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:761)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:730)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:247)
> [messaging-test-tool-1.0-SNA
[jira] [Commented] (AMQ-6160) JDBC XA: NullPointerException on rollback in PREPARED_STATE when trying to unset the XID
[
https://issues.apache.org/jira/browse/AMQ-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15133907#comment-15133907
]
ASF GitHub Bot commented on AMQ-6160:
-
GitHub user jenshadlich opened a pull request:
https://github.com/apache/activemq/pull/167
[AMQ-6160] fix NPE; use messageId.getFutureOrSequenceLong() as sequen…
…ceId if entryLocator is NULL
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jenshadlich/activemq master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq/pull/167.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 #167
commit 569ab7e4d01913b646f024f097662da5ed7c8797
Author: Jens Hadlich
Date: 2016-02-05T09:43:12Z
[AMQ-6160] fix NPE; use messageId.getFutureOrSequenceLong() as sequenceId
if entryLocator is NULL
> JDBC XA: NullPointerException on rollback in PREPARED_STATE when trying to
> unset the XID
>
>
> Key: AMQ-6160
> URL: https://issues.apache.org/jira/browse/AMQ-6160
> Project: ActiveMQ
> Issue Type: Bug
> Components: JDBC
>Affects Versions: 5.12.1
>Reporter: Jens Hadlich
>
> The messageId.getEntryLocator() gives null which leads to the NPE.
> Example stacktrace:
> {noformat}
> 11:12:32.965 [messageListenerContainer-7] WARN
> c.a.d.xa.XAResourceTransaction - XA resource 'atomikosFactorIn': rollback for
> XID
> '3137322E31362E3231352E34312E746D30303030363030303435:3137322E31362E3231352E34312E746D313136'
> raised -7: the XA resource has become unavailable
> javax.transaction.xa.XAException: java.lang.NullPointerException
> at
> org.apache.activemq.TransactionContext.toXAException(TransactionContext.java:735)
> ~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> org.apache.activemq.TransactionContext.rollback(TransactionContext.java:497)
> ~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.datasource.xa.XAResourceTransaction.rollback(XAResourceTransaction.java:677)
> ~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.RollbackMessage.send(RollbackMessage.java:70)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.PropagationMessage.submit(PropagationMessage.java:83)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.Propagator$PropagatorThread.run(Propagator.java:79)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.Propagator.submitPropagationMessage(Propagator.java:58)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CoordinatorStateHandler.rollbackFromWithinCallback(CoordinatorStateHandler.java:709)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.ActiveStateHandler$4.doRollback(ActiveStateHandler.java:213)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CoordinatorStateHandler.rollbackWithAfterCompletionNotification(CoordinatorStateHandler.java:837)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.ActiveStateHandler.rollbackWithAfterCompletionNotification(ActiveStateHandler.java:49)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.ActiveStateHandler.prepare(ActiveStateHandler.java:208)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CoordinatorImp.prepare(CoordinatorImp.java:681)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CoordinatorImp.terminate(CoordinatorImp.java:975)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CompositeTerminatorImp.commit(CompositeTerminatorImp.java:82)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CompositeTransactionImp.commit(CompositeTransactionImp.java:336)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.jta.TransactionImp.commit(TransactionImp.java:190)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.jta.TransactionManagerImp.commit(TransactionManagerImp.java:436)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.jta.UserTransactionImp.commit(UserTransactionImp.java:107)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> org.springframework.transaction.jta.JtaTransactionManager.doCommit(JtaTransactionManager.java:1021)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> org.springframework.t
[jira] [Commented] (AMQ-6160) JDBC XA: NullPointerException on rollback in PREPARED_STATE when trying to unset the XID
[
https://issues.apache.org/jira/browse/AMQ-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15133904#comment-15133904
]
Jens Hadlich commented on AMQ-6160:
---
Proposed solution: Use messageId.getFutureOrSequenceLong() to get the sequence
id.
> JDBC XA: NullPointerException on rollback in PREPARED_STATE when trying to
> unset the XID
>
>
> Key: AMQ-6160
> URL: https://issues.apache.org/jira/browse/AMQ-6160
> Project: ActiveMQ
> Issue Type: Bug
> Components: JDBC
>Affects Versions: 5.12.1
>Reporter: Jens Hadlich
>
> The messageId.getEntryLocator() gives null which leads to the NPE.
> Example stacktrace:
> {noformat}
> 11:12:32.965 [messageListenerContainer-7] WARN
> c.a.d.xa.XAResourceTransaction - XA resource 'atomikosFactorIn': rollback for
> XID
> '3137322E31362E3231352E34312E746D30303030363030303435:3137322E31362E3231352E34312E746D313136'
> raised -7: the XA resource has become unavailable
> javax.transaction.xa.XAException: java.lang.NullPointerException
> at
> org.apache.activemq.TransactionContext.toXAException(TransactionContext.java:735)
> ~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> org.apache.activemq.TransactionContext.rollback(TransactionContext.java:497)
> ~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.datasource.xa.XAResourceTransaction.rollback(XAResourceTransaction.java:677)
> ~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.RollbackMessage.send(RollbackMessage.java:70)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.PropagationMessage.submit(PropagationMessage.java:83)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.Propagator$PropagatorThread.run(Propagator.java:79)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.Propagator.submitPropagationMessage(Propagator.java:58)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CoordinatorStateHandler.rollbackFromWithinCallback(CoordinatorStateHandler.java:709)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.ActiveStateHandler$4.doRollback(ActiveStateHandler.java:213)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CoordinatorStateHandler.rollbackWithAfterCompletionNotification(CoordinatorStateHandler.java:837)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.ActiveStateHandler.rollbackWithAfterCompletionNotification(ActiveStateHandler.java:49)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.ActiveStateHandler.prepare(ActiveStateHandler.java:208)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CoordinatorImp.prepare(CoordinatorImp.java:681)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CoordinatorImp.terminate(CoordinatorImp.java:975)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CompositeTerminatorImp.commit(CompositeTerminatorImp.java:82)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.imp.CompositeTransactionImp.commit(CompositeTransactionImp.java:336)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.jta.TransactionImp.commit(TransactionImp.java:190)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.jta.TransactionManagerImp.commit(TransactionManagerImp.java:436)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> com.atomikos.icatch.jta.UserTransactionImp.commit(UserTransactionImp.java:107)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> org.springframework.transaction.jta.JtaTransactionManager.doCommit(JtaTransactionManager.java:1021)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:761)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:730)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:247)
> [messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
> at
> org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1150)
> [messaging-test-tool-1.0
[jira] [Updated] (AMQ-6160) JDBC XA: NullPointerException on rollback in PREPARED_STATE when trying to unset the XID
[
https://issues.apache.org/jira/browse/AMQ-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens Hadlich updated AMQ-6160:
--
Description:
The messageId.getEntryLocator() gives null which leads to the NPE.
Example stacktrace:
{noformat}
11:12:32.965 [messageListenerContainer-7] WARN c.a.d.xa.XAResourceTransaction
- XA resource 'atomikosFactorIn': rollback for XID
'3137322E31362E3231352E34312E746D30303030363030303435:3137322E31362E3231352E34312E746D313136'
raised -7: the XA resource has become unavailable
javax.transaction.xa.XAException: java.lang.NullPointerException
at
org.apache.activemq.TransactionContext.toXAException(TransactionContext.java:735)
~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.apache.activemq.TransactionContext.rollback(TransactionContext.java:497)
~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.datasource.xa.XAResourceTransaction.rollback(XAResourceTransaction.java:677)
~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.RollbackMessage.send(RollbackMessage.java:70)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.PropagationMessage.submit(PropagationMessage.java:83)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.Propagator$PropagatorThread.run(Propagator.java:79)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.Propagator.submitPropagationMessage(Propagator.java:58)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.CoordinatorStateHandler.rollbackFromWithinCallback(CoordinatorStateHandler.java:709)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.ActiveStateHandler$4.doRollback(ActiveStateHandler.java:213)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.CoordinatorStateHandler.rollbackWithAfterCompletionNotification(CoordinatorStateHandler.java:837)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.ActiveStateHandler.rollbackWithAfterCompletionNotification(ActiveStateHandler.java:49)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.ActiveStateHandler.prepare(ActiveStateHandler.java:208)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.CoordinatorImp.prepare(CoordinatorImp.java:681)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.CoordinatorImp.terminate(CoordinatorImp.java:975)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.CompositeTerminatorImp.commit(CompositeTerminatorImp.java:82)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.CompositeTransactionImp.commit(CompositeTransactionImp.java:336)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.jta.TransactionImp.commit(TransactionImp.java:190)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.jta.TransactionManagerImp.commit(TransactionManagerImp.java:436)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.jta.UserTransactionImp.commit(UserTransactionImp.java:107)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.transaction.jta.JtaTransactionManager.doCommit(JtaTransactionManager.java:1021)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:761)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:730)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:247)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1150)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1142)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:1039)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at java.lang.Thread.run(Thread.java:745) [na:1.7.0_76]
Caused by: javax.jms.JMSException: java.lang.NullPointerException
at
org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:49)
~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.apache.activemq.Act
[jira] [Created] (AMQ-6160) JDBC XA: NullPointerException on rollback in PREPARED_STATE when trying to unset the XID
Jens Hadlich created AMQ-6160:
-
Summary: JDBC XA: NullPointerException on rollback in
PREPARED_STATE when trying to unset the XID
Key: AMQ-6160
URL: https://issues.apache.org/jira/browse/AMQ-6160
Project: ActiveMQ
Issue Type: Bug
Components: JDBC
Affects Versions: 5.12.1
Reporter: Jens Hadlich
The messageId.getEntryLocator() gives null which leads to the NPE.
Example stacktrace:
{noformat}
11:12:32.965 [messageListenerContainer-7] WARN c.a.d.xa.XAResourceTransaction
- XA resource 'atomikosFactorIn': rollback for XID
'3137322E31362E3231352E34312E746D30303030363030303435:3137322E31362E3231352E34312E746D313136'
raised -7: the XA resource has become unavailable
javax.transaction.xa.XAException: java.lang.NullPointerException
at
org.apache.activemq.TransactionContext.toXAException(TransactionContext.java:735)
~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.apache.activemq.TransactionContext.rollback(TransactionContext.java:497)
~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.datasource.xa.XAResourceTransaction.rollback(XAResourceTransaction.java:677)
~[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.RollbackMessage.send(RollbackMessage.java:70)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.PropagationMessage.submit(PropagationMessage.java:83)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.Propagator$PropagatorThread.run(Propagator.java:79)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.Propagator.submitPropagationMessage(Propagator.java:58)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.CoordinatorStateHandler.rollbackFromWithinCallback(CoordinatorStateHandler.java:709)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.ActiveStateHandler$4.doRollback(ActiveStateHandler.java:213)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.CoordinatorStateHandler.rollbackWithAfterCompletionNotification(CoordinatorStateHandler.java:837)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.ActiveStateHandler.rollbackWithAfterCompletionNotification(ActiveStateHandler.java:49)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.ActiveStateHandler.prepare(ActiveStateHandler.java:208)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.CoordinatorImp.prepare(CoordinatorImp.java:681)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.CoordinatorImp.terminate(CoordinatorImp.java:975)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.CompositeTerminatorImp.commit(CompositeTerminatorImp.java:82)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.imp.CompositeTransactionImp.commit(CompositeTransactionImp.java:336)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.jta.TransactionImp.commit(TransactionImp.java:190)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.jta.TransactionManagerImp.commit(TransactionManagerImp.java:436)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
com.atomikos.icatch.jta.UserTransactionImp.commit(UserTransactionImp.java:107)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.transaction.jta.JtaTransactionManager.doCommit(JtaTransactionManager.java:1021)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:761)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:730)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:247)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1150)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1142)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:1039)
[messaging-test-tool-1.0-SNAPSHOT.2.jar:na]
at java.lang.Thread.run(Thread.java:745) [na:1.7.0_76]
Caused by: javax.j
