[jira] [Resolved] (ARTEMIS-1736) management role access methods not ordered

[Justin Bertram (JIRA)]

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

Justin Bertram resolved ARTEMIS-1736.
-
   Resolution: Fixed
Fix Version/s: 2.5.0

> management role access methods not ordered
> --
>
> Key: ARTEMIS-1736
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1736
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: Andy Taylor
>Priority: Major
> Fix For: 2.5.0
>
>
> in the management.xml the access elements are not us3d in order meaning * can 
> be selected every time



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ARTEMIS-1752) Avoid null pointer in bridge

[Justin Bertram (JIRA)]

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

Justin Bertram resolved ARTEMIS-1752.
-
   Resolution: Fixed
Fix Version/s: 2.5.1

> Avoid null pointer in bridge
> 
>
> Key: ARTEMIS-1752
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1752
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: Andy Taylor
>Assignee: Andy Taylor
>Priority: Major
> Fix For: 2.5.1
>
>
> serverLocator.notifyNodeDown(System.currentTimeMillis(), targetNodeID);
>  
> shpould have a null guard in BridgeImpl.java



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ARTEMIS-1764) Broker does not start properly if prepared tx exists with ack to non existent queue

[Justin Bertram (JIRA)]

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

Justin Bertram resolved ARTEMIS-1764.
-
   Resolution: Fixed
Fix Version/s: 2.5.1

> Broker does not start properly if prepared tx exists with ack to non existent 
> queue
> ---
>
> Key: ARTEMIS-1764
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1764
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: Martyn Taylor
>Priority: Major
> Fix For: 2.5.1
>
>
> A Tx exists with an ack or messagequeue X in prepared state.  If X is deleted 
> and the broker stopped and started.  The journal loader throws an exception 
> and the broker does not start properly.  Acceptors are not started etc...
>  
> 2018-03-22 13:35:07,149 WARN [org.apache.activemq.artemis.core.server] 
> AMQ222043: Message for queue 6,107,672 which does not exist. This message 
> will be ignored.
> 2018-03-22 13:35:07,152 ERROR [org.apache.activemq.artemis.core.server] 
> AMQ224000: Failure in initialisation: java.lang.IllegalStateException: Cannot 
> find queue with id 6107672
>  at 
> org.apache.activemq.artemis.core.server.impl.PostOfficeJournalLoader.handlePreparedAcknowledge(PostOfficeJournalLoader.java:306)
>  [artemis-server-2.6.0-SNAPSHOT.jar:2.6.0-SNAPSHOT]
>  at 
> org.apache.activemq.artemis.core.persistence.impl.journal.AbstractJournalStorageManager.loadPreparedTransactions(AbstractJournalStorageManager.java:1721)
>  [artemis-server-2.6.0-SNAPSHOT.jar:2.6.0-SNAPSHOT]
>  at 
> org.apache.activemq.artemis.core.persistence.impl.journal.AbstractJournalStorageManager.loadMessageJournal(AbstractJournalStorageManager.java:1169)
>  [artemis-server-2.6.0-SNAPSHOT.jar:2.6.0-SNAPSHOT]
>  at 
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.loadJournals(ActiveMQServerImpl.java:2588)
>  [artemis-server-2.6.0-SNAPSHOT.jar:2.6.0-SNAPSHOT]
>  at 
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.initialisePart2(ActiveMQServerImpl.java:2346)
>  [artemis-server-2.6.0-SNAPSHOT.jar:2.6.0-SNAPSHOT]
>  at 
> org.apache.activemq.artemis.core.server.impl.LiveOnlyActivation.run(LiveOnlyActivation.java:71)
>  [artemis-server-2.6.0-SNAPSHOT.jar:2.6.0-SNAPSHOT]
>  at 
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.internalStart(ActiveMQServerImpl.java:522)
>  [artemis-server-2.6.0-SNAPSHOT.jar:2.6.0-SNAPSHOT]
>  at 
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:461)
>  [artemis-server-2.6.0-SNAPSHOT.jar:2.6.0-SNAPSHOT]
>  at 
> org.apache.activemq.artemis.integration.FileBroker.start(FileBroker.java:111) 
> [artemis-cli-2.6.0-SNAPSHOT.jar:2.6.0-SNAPSHOT]
>  at org.apache.activemq.artemis.cli.commands.Run.execute(Run.java:82) 
> [artemis-cli-2.6.0-SNAPSHOT.jar:2.6.0-SNAPSHOT]
>  at org.apache.activemq.artemis.cli.Artemis.internalExecute(Artemis.java:149) 
> [artemis-cli-2.6.0-SNAPSHOT.jar:2.6.0-SNAPSHOT]
>  at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:97) 
> [artemis-cli-2.6.0-SNAPSHOT.jar:2.6.0-SNAPSHOT]
>  at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:124) 
> [artemis-cli-2.6.0-SNAPSHOT.jar:2.6.0-SNAPSHOT]
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> [rt.jar:1.8.0_151]
>  at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> [rt.jar:1.8.0_151]
>  at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  [rt.jar:1.8.0_151]
>  at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_151]
>  at org.apache.activemq.artemis.boot.Artemis.execute(Artemis.java:129) 
> [artemis-boot.jar:2.6.0-SNAPSHOT]
>  at org.apache.activemq.artemis.boot.Artemis.main(Artemis.java:49) 
> [artemis-boot.jar:2.6.0-SNAPSHOT]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ARTEMIS-370) Make JDBC Journal Sync period configurable

[Justin Bertram (JIRA)]

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

Justin Bertram resolved ARTEMIS-370.

Resolution: Fixed

> Make JDBC Journal Sync period configurable
> --
>
> Key: ARTEMIS-370
> URL: https://issues.apache.org/jira/browse/ARTEMIS-370
> Project: ActiveMQ Artemis
>  Issue Type: Improvement
>Affects Versions: 2.5.0
>Reporter: Martyn Taylor
>Priority: Major
> Fix For: 2.5.1
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ARTEMIS-1653) Allow database tables to be created externally

[Justin Bertram (JIRA)]

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

Justin Bertram resolved ARTEMIS-1653.
-
   Resolution: Fixed
Fix Version/s: 2.5.1

> Allow database tables to be created externally
> --
>
> Key: ARTEMIS-1653
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1653
> Project: ActiveMQ Artemis
>  Issue Type: Improvement
>  Components: Broker
>Affects Versions: 2.4.0
>Reporter: Niels Lippke
>Assignee: Francesco Nigro
>Priority: Major
> Fix For: 2.5.1
>
>
> In some environments (e.g. production) it is not allowed that applications 
> create their own schema. It's common practice to pass DDL-Statetements to 
> DBAs instead prior to rollout.
> Currently the broker does not support this scenario. If the required tables 
> already exist the broker fails to start.
> A better approach is that if the broker detects empy tables and initializes 
> them in the very same way it does if the tables dont't exist.
> See also discussion in 
> [forum|http://activemq.2283324.n4.nabble.com/ARTEMIS-Server-doesn-t-start-if-JDBC-store-is-used-and-table-NODE-MANAGER-STORE-is-empty-td4735779.html].



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ARTEMIS-1776) Implement asynchronous flow control on bridge and clustered bridge

[Justin Bertram (JIRA)]

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

Justin Bertram resolved ARTEMIS-1776.
-
Resolution: Fixed

> Implement asynchronous flow control on bridge and clustered bridge
> --
>
> Key: ARTEMIS-1776
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1776
> Project: ActiveMQ Artemis
>  Issue Type: Improvement
>Affects Versions: 2.5.0
>Reporter: clebert suconic
>Assignee: clebert suconic
>Priority: Major
> Fix For: 2.5.1
>
>
> Currently the flow control on the Bridge is based on back pressure only, 
> through Netty writeable interfaces.
>  
> If the user selected a positive producerWindowSize the Queue may block while 
> the Processing is happening. What could lead to distributed deadlocks on the 
> Bridge.
>  
> This will avoid that possibility.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ARTEMIS-375) When use ./artemis data exp, the xml printed to stdout mixed with logging information

[Justin Bertram (JIRA)]

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

Justin Bertram resolved ARTEMIS-375.

   Resolution: Fixed
Fix Version/s: 2.5.1

> When use ./artemis data exp, the xml printed to stdout mixed with logging 
> information
> -
>
> Key: ARTEMIS-375
> URL: https://issues.apache.org/jira/browse/ARTEMIS-375
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Affects Versions: 1.2.0
>Reporter: Howard Nguyen
>Priority: Major
> Fix For: 2.5.1
>
> Attachments: XmlDataExport-improvement.patch
>
>
> When use ./artemis data exp, the xml printed to stdout mixed with logging 
> information.
> Attached patch.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ARTEMIS-1652) XmlDataImporter forgets to delete tmp files

[Justin Bertram (JIRA)]

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

Justin Bertram updated ARTEMIS-1652:

Summary: XmlDataImporter forgets to delete tmp files  (was: XmlDataImporter 
forgets delete tmp files)

> XmlDataImporter forgets to delete tmp files
> ---
>
> Key: ARTEMIS-1652
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1652
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 2.4.0
>Reporter: Howard Gao
>Assignee: Howard Gao
>Priority: Major
> Fix For: 2.5.0
>
>
> When using the tool to import more than one large messages from xml exported 
> file, this utility class will create some tmp files, each for one large 
> message. However it only delete one of the tmp files. All the rest of tmp 
> files won't get cleaned up.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ARTEMIS-1629) Set clientID on STOMP connections before authentication

[Justin Bertram (JIRA)]

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

Justin Bertram updated ARTEMIS-1629:

Summary: Set clientID on STOMP connections before authentication  (was: In 
ActiveMQSecurityManager3#validateUser calling remoteConnection.getClientID() 
returns null)

> Set clientID on STOMP connections before authentication
> ---
>
> Key: ARTEMIS-1629
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1629
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>  Components: STOMP
>Affects Versions: 2.4.0
> Environment: Artemis 2.5.0-SNAPSHOT
>Reporter: Johan Stenberg
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.5.0
>
> Attachments: Artemis1629Test.java
>
>
> We are using a custom security manager in our setup. Opposite to other 
> protocols (e.g. AMQP), executing *remotingConnection.getClientID()* returns 
> null for StompConnections when accessed from within 
> ActiveMQSecurityManager3#validateUser(String, String, RemotingConnection).
> We however already need to know the client at this time as we perform certain 
> validations/on-the-fly configurations based on the value.
> The issue would be solved if the statement 
> *connection.setClientID(clientID);* from 
> [https://github.com/apache/activemq-artemis/blob/master/artemis-protocols/artemis-stomp-protocol/src/main/java/org/apache/activemq/artemis/core/protocol/stomp/v10/StompFrameHandlerV10.java#L56]
>  would be moved two lines up before *if (connection.validateUser(login, 
> passcode, connection)) {*
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARTEMIS-618) Fails to initialize journal if hard drive block size is over 512 bytes

[clebert suconic (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427499#comment-16427499
 ] 

clebert suconic commented on ARTEMIS-618:
-

you know you helped me to find a pesky failure that was happening from time to 
time on our Travis? thanks for the help.

> Fails to initialize journal if hard drive block size is over 512 bytes
> --
>
> Key: ARTEMIS-618
> URL: https://issues.apache.org/jira/browse/ARTEMIS-618
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Affects Versions: 2.5.0
> Environment: CentOS 7 on hard drive with 4 KB blocks
>Reporter: Rostyslav Smirnov
>Assignee: clebert suconic
>Priority: Major
> Fix For: 2.5.1
>
>
> AIO journal fails to initialize with the following error:
> AMQ224000: Failure in initialisation: java.io.IOException: Cannot initialize 
> file
>   at org.apache.activemq.artemis.jlibaio.LibaioContext.fill(Native 
> Method) [artemis-native-1.3.0.jar:]
>   at 
> org.apache.activemq.artemis.jlibaio.LibaioFile.fill(LibaioFile.java:122) 
> [artemis-native-1.3.0.jar:]
>   at 
> org.apache.activemq.artemis.core.io.aio.AIOSequentialFile.fill(AIOSequentialFile.java:126)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalFilesRepository.createFile0(JournalFilesRepository.java:587)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalFilesRepository.createFile(JournalFilesRepository.java:537)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalFilesRepository.ensureMinFiles(JournalFilesRepository.java:201)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.setUpCurrentFile(JournalImpl.java:2709)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.load(JournalImpl.java:1755)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.load(JournalImpl.java:1135)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.load(JournalImpl.java:1119)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.persistence.impl.journal.AbstractJournalStorageManager.loadMessageJournal(AbstractJournalStorageManager.java:864)
>  [artemis-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.loadJournals(ActiveMQServerImpl.java:2054)
>  [artemis-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.initialisePart2(ActiveMQServerImpl.java:1927)
>  [artemis-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.server.impl.LiveOnlyActivation.run(LiveOnlyActivation.java:63)
>  [artemis-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:427)
>  [artemis-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:394)
>  [artemis-jms-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.integration.FileBroker.start(FileBroker.java:65) 
> [artemis-cli-1.3.0.jar:1.3.0]
>   at org.apache.activemq.artemis.cli.commands.Run.execute(Run.java:83) 
> [artemis-cli-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.cli.Artemis.internalExecute(Artemis.java:110) 
> [artemis-cli-1.3.0.jar:1.3.0]
>   at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:72) 
> [artemis-cli-1.3.0.jar:1.3.0]
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> [rt.jar:1.8.0_65]
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> [rt.jar:1.8.0_65]
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  [rt.jar:1.8.0_65]
>   at java.lang.reflect.Method.invoke(Method.java:497) [rt.jar:1.8.0_65]
>   at org.apache.activemq.artemis.boot.Artemis.execute(Artemis.java:122) 
> [artemis-boot.jar:1.3.0]
>   at org.apache.activemq.artemis.boot.Artemis.main(Artemis.java:45) 
> [artemis-boot.jar:1.3.0]
> This is due to buffers not being aligned for writing to file open with 
> O_DIRECT flag.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARTEMIS-618) Fails to initialize journal if hard drive block size is over 512 bytes

[Rostyslav Smirnov (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427497#comment-16427497
 ] 

Rostyslav Smirnov commented on ARTEMIS-618:
---

Yes, indeed.

> Fails to initialize journal if hard drive block size is over 512 bytes
> --
>
> Key: ARTEMIS-618
> URL: https://issues.apache.org/jira/browse/ARTEMIS-618
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Affects Versions: 2.5.0
> Environment: CentOS 7 on hard drive with 4 KB blocks
>Reporter: Rostyslav Smirnov
>Assignee: clebert suconic
>Priority: Major
> Fix For: 2.5.1
>
>
> AIO journal fails to initialize with the following error:
> AMQ224000: Failure in initialisation: java.io.IOException: Cannot initialize 
> file
>   at org.apache.activemq.artemis.jlibaio.LibaioContext.fill(Native 
> Method) [artemis-native-1.3.0.jar:]
>   at 
> org.apache.activemq.artemis.jlibaio.LibaioFile.fill(LibaioFile.java:122) 
> [artemis-native-1.3.0.jar:]
>   at 
> org.apache.activemq.artemis.core.io.aio.AIOSequentialFile.fill(AIOSequentialFile.java:126)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalFilesRepository.createFile0(JournalFilesRepository.java:587)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalFilesRepository.createFile(JournalFilesRepository.java:537)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalFilesRepository.ensureMinFiles(JournalFilesRepository.java:201)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.setUpCurrentFile(JournalImpl.java:2709)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.load(JournalImpl.java:1755)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.load(JournalImpl.java:1135)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.load(JournalImpl.java:1119)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.persistence.impl.journal.AbstractJournalStorageManager.loadMessageJournal(AbstractJournalStorageManager.java:864)
>  [artemis-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.loadJournals(ActiveMQServerImpl.java:2054)
>  [artemis-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.initialisePart2(ActiveMQServerImpl.java:1927)
>  [artemis-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.server.impl.LiveOnlyActivation.run(LiveOnlyActivation.java:63)
>  [artemis-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:427)
>  [artemis-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:394)
>  [artemis-jms-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.integration.FileBroker.start(FileBroker.java:65) 
> [artemis-cli-1.3.0.jar:1.3.0]
>   at org.apache.activemq.artemis.cli.commands.Run.execute(Run.java:83) 
> [artemis-cli-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.cli.Artemis.internalExecute(Artemis.java:110) 
> [artemis-cli-1.3.0.jar:1.3.0]
>   at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:72) 
> [artemis-cli-1.3.0.jar:1.3.0]
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> [rt.jar:1.8.0_65]
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> [rt.jar:1.8.0_65]
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  [rt.jar:1.8.0_65]
>   at java.lang.reflect.Method.invoke(Method.java:497) [rt.jar:1.8.0_65]
>   at org.apache.activemq.artemis.boot.Artemis.execute(Artemis.java:122) 
> [artemis-boot.jar:1.3.0]
>   at org.apache.activemq.artemis.boot.Artemis.main(Artemis.java:45) 
> [artemis-boot.jar:1.3.0]
> This is due to buffers not being aligned for writing to file open with 
> O_DIRECT flag.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARTEMIS-618) Fails to initialize journal if hard drive block size is over 512 bytes

[clebert suconic (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427490#comment-16427490
 ] 

clebert suconic commented on ARTEMIS-618:
-

ok, so I assumed it worked then.. ???

> Fails to initialize journal if hard drive block size is over 512 bytes
> --
>
> Key: ARTEMIS-618
> URL: https://issues.apache.org/jira/browse/ARTEMIS-618
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Affects Versions: 2.5.0
> Environment: CentOS 7 on hard drive with 4 KB blocks
>Reporter: Rostyslav Smirnov
>Assignee: clebert suconic
>Priority: Major
> Fix For: 2.5.1
>
>
> AIO journal fails to initialize with the following error:
> AMQ224000: Failure in initialisation: java.io.IOException: Cannot initialize 
> file
>   at org.apache.activemq.artemis.jlibaio.LibaioContext.fill(Native 
> Method) [artemis-native-1.3.0.jar:]
>   at 
> org.apache.activemq.artemis.jlibaio.LibaioFile.fill(LibaioFile.java:122) 
> [artemis-native-1.3.0.jar:]
>   at 
> org.apache.activemq.artemis.core.io.aio.AIOSequentialFile.fill(AIOSequentialFile.java:126)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalFilesRepository.createFile0(JournalFilesRepository.java:587)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalFilesRepository.createFile(JournalFilesRepository.java:537)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalFilesRepository.ensureMinFiles(JournalFilesRepository.java:201)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.setUpCurrentFile(JournalImpl.java:2709)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.load(JournalImpl.java:1755)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.load(JournalImpl.java:1135)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.load(JournalImpl.java:1119)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.persistence.impl.journal.AbstractJournalStorageManager.loadMessageJournal(AbstractJournalStorageManager.java:864)
>  [artemis-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.loadJournals(ActiveMQServerImpl.java:2054)
>  [artemis-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.initialisePart2(ActiveMQServerImpl.java:1927)
>  [artemis-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.server.impl.LiveOnlyActivation.run(LiveOnlyActivation.java:63)
>  [artemis-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:427)
>  [artemis-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:394)
>  [artemis-jms-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.integration.FileBroker.start(FileBroker.java:65) 
> [artemis-cli-1.3.0.jar:1.3.0]
>   at org.apache.activemq.artemis.cli.commands.Run.execute(Run.java:83) 
> [artemis-cli-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.cli.Artemis.internalExecute(Artemis.java:110) 
> [artemis-cli-1.3.0.jar:1.3.0]
>   at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:72) 
> [artemis-cli-1.3.0.jar:1.3.0]
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> [rt.jar:1.8.0_65]
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> [rt.jar:1.8.0_65]
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  [rt.jar:1.8.0_65]
>   at java.lang.reflect.Method.invoke(Method.java:497) [rt.jar:1.8.0_65]
>   at org.apache.activemq.artemis.boot.Artemis.execute(Artemis.java:122) 
> [artemis-boot.jar:1.3.0]
>   at org.apache.activemq.artemis.boot.Artemis.main(Artemis.java:45) 
> [artemis-boot.jar:1.3.0]
> This is due to buffers not being aligned for writing to file open with 
> O_DIRECT flag.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (ARTEMIS-618) Fails to initialize journal if hard drive block size is over 512 bytes

[clebert suconic (JIRA)]

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

clebert suconic closed ARTEMIS-618.
---
Resolution: Fixed

> Fails to initialize journal if hard drive block size is over 512 bytes
> --
>
> Key: ARTEMIS-618
> URL: https://issues.apache.org/jira/browse/ARTEMIS-618
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Affects Versions: 2.5.0
> Environment: CentOS 7 on hard drive with 4 KB blocks
>Reporter: Rostyslav Smirnov
>Assignee: clebert suconic
>Priority: Major
> Fix For: 2.5.1
>
>
> AIO journal fails to initialize with the following error:
> AMQ224000: Failure in initialisation: java.io.IOException: Cannot initialize 
> file
>   at org.apache.activemq.artemis.jlibaio.LibaioContext.fill(Native 
> Method) [artemis-native-1.3.0.jar:]
>   at 
> org.apache.activemq.artemis.jlibaio.LibaioFile.fill(LibaioFile.java:122) 
> [artemis-native-1.3.0.jar:]
>   at 
> org.apache.activemq.artemis.core.io.aio.AIOSequentialFile.fill(AIOSequentialFile.java:126)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalFilesRepository.createFile0(JournalFilesRepository.java:587)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalFilesRepository.createFile(JournalFilesRepository.java:537)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalFilesRepository.ensureMinFiles(JournalFilesRepository.java:201)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.setUpCurrentFile(JournalImpl.java:2709)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.load(JournalImpl.java:1755)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.load(JournalImpl.java:1135)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.load(JournalImpl.java:1119)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.persistence.impl.journal.AbstractJournalStorageManager.loadMessageJournal(AbstractJournalStorageManager.java:864)
>  [artemis-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.loadJournals(ActiveMQServerImpl.java:2054)
>  [artemis-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.initialisePart2(ActiveMQServerImpl.java:1927)
>  [artemis-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.server.impl.LiveOnlyActivation.run(LiveOnlyActivation.java:63)
>  [artemis-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:427)
>  [artemis-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:394)
>  [artemis-jms-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.integration.FileBroker.start(FileBroker.java:65) 
> [artemis-cli-1.3.0.jar:1.3.0]
>   at org.apache.activemq.artemis.cli.commands.Run.execute(Run.java:83) 
> [artemis-cli-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.cli.Artemis.internalExecute(Artemis.java:110) 
> [artemis-cli-1.3.0.jar:1.3.0]
>   at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:72) 
> [artemis-cli-1.3.0.jar:1.3.0]
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> [rt.jar:1.8.0_65]
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> [rt.jar:1.8.0_65]
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  [rt.jar:1.8.0_65]
>   at java.lang.reflect.Method.invoke(Method.java:497) [rt.jar:1.8.0_65]
>   at org.apache.activemq.artemis.boot.Artemis.execute(Artemis.java:122) 
> [artemis-boot.jar:1.3.0]
>   at org.apache.activemq.artemis.boot.Artemis.main(Artemis.java:45) 
> [artemis-boot.jar:1.3.0]
> This is due to buffers not being aligned for writing to file open with 
> O_DIRECT flag.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARTEMIS-618) Fails to initialize journal if hard drive block size is over 512 bytes

[Rostyslav Smirnov (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427489#comment-16427489
 ] 

Rostyslav Smirnov commented on ARTEMIS-618:
---

Tested the fix. Thanks, [~clebertsuconic]!

> Fails to initialize journal if hard drive block size is over 512 bytes
> --
>
> Key: ARTEMIS-618
> URL: https://issues.apache.org/jira/browse/ARTEMIS-618
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Affects Versions: 2.5.0
> Environment: CentOS 7 on hard drive with 4 KB blocks
>Reporter: Rostyslav Smirnov
>Assignee: clebert suconic
>Priority: Major
> Fix For: 2.5.1
>
>
> AIO journal fails to initialize with the following error:
> AMQ224000: Failure in initialisation: java.io.IOException: Cannot initialize 
> file
>   at org.apache.activemq.artemis.jlibaio.LibaioContext.fill(Native 
> Method) [artemis-native-1.3.0.jar:]
>   at 
> org.apache.activemq.artemis.jlibaio.LibaioFile.fill(LibaioFile.java:122) 
> [artemis-native-1.3.0.jar:]
>   at 
> org.apache.activemq.artemis.core.io.aio.AIOSequentialFile.fill(AIOSequentialFile.java:126)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalFilesRepository.createFile0(JournalFilesRepository.java:587)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalFilesRepository.createFile(JournalFilesRepository.java:537)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalFilesRepository.ensureMinFiles(JournalFilesRepository.java:201)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.setUpCurrentFile(JournalImpl.java:2709)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.load(JournalImpl.java:1755)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.load(JournalImpl.java:1135)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.load(JournalImpl.java:1119)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.persistence.impl.journal.AbstractJournalStorageManager.loadMessageJournal(AbstractJournalStorageManager.java:864)
>  [artemis-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.loadJournals(ActiveMQServerImpl.java:2054)
>  [artemis-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.initialisePart2(ActiveMQServerImpl.java:1927)
>  [artemis-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.server.impl.LiveOnlyActivation.run(LiveOnlyActivation.java:63)
>  [artemis-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:427)
>  [artemis-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:394)
>  [artemis-jms-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.integration.FileBroker.start(FileBroker.java:65) 
> [artemis-cli-1.3.0.jar:1.3.0]
>   at org.apache.activemq.artemis.cli.commands.Run.execute(Run.java:83) 
> [artemis-cli-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.cli.Artemis.internalExecute(Artemis.java:110) 
> [artemis-cli-1.3.0.jar:1.3.0]
>   at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:72) 
> [artemis-cli-1.3.0.jar:1.3.0]
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> [rt.jar:1.8.0_65]
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> [rt.jar:1.8.0_65]
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  [rt.jar:1.8.0_65]
>   at java.lang.reflect.Method.invoke(Method.java:497) [rt.jar:1.8.0_65]
>   at org.apache.activemq.artemis.boot.Artemis.execute(Artemis.java:122) 
> [artemis-boot.jar:1.3.0]
>   at org.apache.activemq.artemis.boot.Artemis.main(Artemis.java:45) 
> [artemis-boot.jar:1.3.0]
> This is due to buffers not being aligned for writing to file open with 
> O_DIRECT flag.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ARTEMIS-1329) JMS test NoLocalSubscriberTest#testNoLocalReconnect fails with OpenWire protocol (activemq-client JMS library)

[Justin Bertram (JIRA)]

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

Justin Bertram resolved ARTEMIS-1329.
-
   Resolution: Fixed
Fix Version/s: 2.5.0

> JMS test NoLocalSubscriberTest#testNoLocalReconnect fails with OpenWire 
> protocol (activemq-client JMS library)
> --
>
> Key: ARTEMIS-1329
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1329
> Project: ActiveMQ Artemis
>  Issue Type: Test
>  Components: Broker, OpenWire
>Affects Versions: 2.3.0
>Reporter: Jiri Daněk
>Assignee: Stanislav Knot
>Priority: Major
> Fix For: 2.5.0
>
>
> Consider test 
> org.apache.activemq.artemis.tests.integration.jms.client.NoLocalSubscriberTest#testNoLocalReconnect.
> When it is adapted to run with multiple JMS clients, or when run from the 
> standalone reproducer at 
> https://github.com/jdanekrh/jms-reproducers/blob/NoLocalSubscriberTest/src/test/java/org/apache/activemq/artemis/tests/integration/jms/client/NoLocalSubscriberTest.java
> (the standalone reproducer requires a running broker to connect to), the test 
> passes with Core and AMQP protocols,
> and fails with OpenWire at assertion
> {noformat}
>  // now drain the subscription
>  // we should not receive message M3, but we should receive message M4
>  // However for some reason Artemis doesn't receive either
>  TextMessage textMessage = (TextMessage) 
> topicSubscriber.receive(1000);
>  assertNotNull(textMessage);
> {noformat}
> With exception
> {noformat}
> java.lang.AssertionError
>   at org.junit.Assert.fail(Assert.java:86)
>   at org.junit.Assert.assertTrue(Assert.java:41)
>   at org.junit.Assert.assertNotNull(Assert.java:621)
>   at org.junit.Assert.assertNotNull(Assert.java:631)
>   at 
> org.apache.activemq.artemis.tests.integration.jms.client.NoLocalSubscriberTest.testNoLocalReconnect(NoLocalSubscriberTest.java:178)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>   at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
>   at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>   at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
>   at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
>   at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
>   at org.junit.runners.Suite.runChild(Suite.java:127)
>   at org.junit.runners.Suite.runChild(Suite.java:26)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
>   at org.junit.runner.JUnitCore.run(JUnitCore.java:160)
>   at 
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
>   at 
> 

[jira] [Updated] (ARTEMIS-1547) Support referrals in the LDAP login module

[Justin Bertram (JIRA)]

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

Justin Bertram updated ARTEMIS-1547:

Issue Type: New Feature  (was: Improvement)

> Support referrals in the LDAP login module
> --
>
> Key: ARTEMIS-1547
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1547
> Project: ActiveMQ Artemis
>  Issue Type: New Feature
>  Components: Broker
>Affects Versions: 2.4.0
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.5.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARTEMIS-1770) Warnings/Errors during clean shutdown of server with JMS Bridge

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427313#comment-16427313
 ] 

ASF GitHub Bot commented on ARTEMIS-1770:
-

Github user asfgit closed the pull request at:

https://github.com/apache/activemq-artemis/pull/1995


> Warnings/Errors during clean shutdown of server with JMS Bridge
> ---
>
> Key: ARTEMIS-1770
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1770
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Affects Versions: 1.5.6, 2.5.0
>Reporter: Radovan Stancel
>Priority: Major
>
> If server with JMS bridge is cleanly shutdown then following errors appears 
> in the server log:
> {code}
> 16:03:06,458 ERROR [org.apache.activemq.artemis.core.client] (ServerService 
> Thread Pool -- 76) AMQ214004: XA end operation failed : 
> ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119010: 
> Connection is destroyed]
>  at 
> org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:338)
>  [artemis-core-client-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1]
>  at 
> org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:318)
>  [artemis-core-client-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1]
>  at 
> org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQSessionContext.xaEnd(ActiveMQSessionContext.java:383)
>  [artemis-core-client-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1]
>  at 
> org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.end(ClientSessionImpl.java:1173)
>  [artemis-core-client-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1]
>  at 
> com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.doEnd(TransactionImple.java:1069)
>  [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.endAssociation(TransactionImple.java:1040)
>  [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.endAssociation(XAResourceRecord.java:1287)
>  [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelAbort(XAResourceRecord.java:313)
>  [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:3023) 
> [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:3002) 
> [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.arjuna.coordinator.BasicAction.Abort(BasicAction.java:1674) 
> [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.cancel(TwoPhaseCoordinator.java:124)
>  [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at com.arjuna.ats.arjuna.AtomicAction.cancel(AtomicAction.java:215) 
> [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.rollback(TransactionImple.java:284)
>  [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider$Entry.rollbackLocal(JBossLocalTransactionProvider.java:317)
>  at 
> org.wildfly.transaction.client.provider.jboss.JBossJTALocalTransactionProvider.rollbackLocal(JBossJTALocalTransactionProvider.java:116)
>  at 
> org.wildfly.transaction.client.LocalTransaction.rollback(LocalTransaction.java:87)
>  at 
> org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.stop(JMSBridgeImpl.java:501)
>  [artemis-jms-server-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1]
>  at 
> org.wildfly.extension.messaging.activemq.jms.bridge.JMSBridgeService$2.run(JMSBridgeService.java:127)
>  
> [wildfly-messaging-activemq-7.1.0.Alpha1-redhat-15.jar:7.1.0.Alpha1-redhat-15]
>  at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [rt.jar:1.8.0_71]
>  at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [rt.jar:1.8.0_71]
>  at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_71]
>  at org.jboss.threads.JBossThread.run(JBossThread.java:320) 
> [jboss-threads-2.2.1.Final-redhat-1.jar:2.2.1.Final-redhat-1]
> 16:03:06,464 WARN [com.arjuna.ats.jta] (ServerService Thread Pool -- 76) 
> ARJUNA016129: Could not end XA 

[jira] [Commented] (ARTEMIS-1770) Warnings/Errors during clean shutdown of server with JMS Bridge

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427311#comment-16427311
 ] 

ASF subversion and git services commented on ARTEMIS-1770:
--

Commit 20aed7f864ad1f2a549a155f2b8e689b8850e7c4 in activemq-artemis's branch 
refs/heads/1.x from [~rstancel]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=20aed7f ]

[ARTEMIS-1770] Log warning when connection is closed


> Warnings/Errors during clean shutdown of server with JMS Bridge
> ---
>
> Key: ARTEMIS-1770
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1770
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Affects Versions: 1.5.6, 2.5.0
>Reporter: Radovan Stancel
>Priority: Major
>
> If server with JMS bridge is cleanly shutdown then following errors appears 
> in the server log:
> {code}
> 16:03:06,458 ERROR [org.apache.activemq.artemis.core.client] (ServerService 
> Thread Pool -- 76) AMQ214004: XA end operation failed : 
> ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119010: 
> Connection is destroyed]
>  at 
> org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:338)
>  [artemis-core-client-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1]
>  at 
> org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:318)
>  [artemis-core-client-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1]
>  at 
> org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQSessionContext.xaEnd(ActiveMQSessionContext.java:383)
>  [artemis-core-client-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1]
>  at 
> org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.end(ClientSessionImpl.java:1173)
>  [artemis-core-client-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1]
>  at 
> com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.doEnd(TransactionImple.java:1069)
>  [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.endAssociation(TransactionImple.java:1040)
>  [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.endAssociation(XAResourceRecord.java:1287)
>  [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelAbort(XAResourceRecord.java:313)
>  [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:3023) 
> [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:3002) 
> [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.arjuna.coordinator.BasicAction.Abort(BasicAction.java:1674) 
> [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.cancel(TwoPhaseCoordinator.java:124)
>  [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at com.arjuna.ats.arjuna.AtomicAction.cancel(AtomicAction.java:215) 
> [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.rollback(TransactionImple.java:284)
>  [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider$Entry.rollbackLocal(JBossLocalTransactionProvider.java:317)
>  at 
> org.wildfly.transaction.client.provider.jboss.JBossJTALocalTransactionProvider.rollbackLocal(JBossJTALocalTransactionProvider.java:116)
>  at 
> org.wildfly.transaction.client.LocalTransaction.rollback(LocalTransaction.java:87)
>  at 
> org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.stop(JMSBridgeImpl.java:501)
>  [artemis-jms-server-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1]
>  at 
> org.wildfly.extension.messaging.activemq.jms.bridge.JMSBridgeService$2.run(JMSBridgeService.java:127)
>  
> [wildfly-messaging-activemq-7.1.0.Alpha1-redhat-15.jar:7.1.0.Alpha1-redhat-15]
>  at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [rt.jar:1.8.0_71]
>  at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [rt.jar:1.8.0_71]
>  at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_71]
>  at org.jboss.threads.JBossThread.run(JBossThread.java:320) 
> 

[jira] [Commented] (ARTEMIS-1770) Warnings/Errors during clean shutdown of server with JMS Bridge

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427245#comment-16427245
 ] 

ASF GitHub Bot commented on ARTEMIS-1770:
-

GitHub user rstancel opened a pull request:

https://github.com/apache/activemq-artemis/pull/1995

[ARTEMIS-1770] Log warning when connection is closed

Jira: https://issues.apache.org/jira/browse/ARTEMIS-1770

Master PR: https://github.com/apache/activemq-artemis/pull/1990

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

$ git pull https://github.com/rstancel/jboss-activemq-artemis 
ARTEMIS-1770_1.x

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

https://github.com/apache/activemq-artemis/pull/1995.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 #1995






> Warnings/Errors during clean shutdown of server with JMS Bridge
> ---
>
> Key: ARTEMIS-1770
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1770
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Affects Versions: 1.5.6, 2.5.0
>Reporter: Radovan Stancel
>Priority: Major
>
> If server with JMS bridge is cleanly shutdown then following errors appears 
> in the server log:
> {code}
> 16:03:06,458 ERROR [org.apache.activemq.artemis.core.client] (ServerService 
> Thread Pool -- 76) AMQ214004: XA end operation failed : 
> ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119010: 
> Connection is destroyed]
>  at 
> org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:338)
>  [artemis-core-client-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1]
>  at 
> org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:318)
>  [artemis-core-client-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1]
>  at 
> org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQSessionContext.xaEnd(ActiveMQSessionContext.java:383)
>  [artemis-core-client-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1]
>  at 
> org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.end(ClientSessionImpl.java:1173)
>  [artemis-core-client-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1]
>  at 
> com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.doEnd(TransactionImple.java:1069)
>  [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.endAssociation(TransactionImple.java:1040)
>  [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.endAssociation(XAResourceRecord.java:1287)
>  [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelAbort(XAResourceRecord.java:313)
>  [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:3023) 
> [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:3002) 
> [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.arjuna.coordinator.BasicAction.Abort(BasicAction.java:1674) 
> [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.cancel(TwoPhaseCoordinator.java:124)
>  [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at com.arjuna.ats.arjuna.AtomicAction.cancel(AtomicAction.java:215) 
> [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.rollback(TransactionImple.java:284)
>  [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider$Entry.rollbackLocal(JBossLocalTransactionProvider.java:317)
>  at 
> org.wildfly.transaction.client.provider.jboss.JBossJTALocalTransactionProvider.rollbackLocal(JBossJTALocalTransactionProvider.java:116)
>  at 
> org.wildfly.transaction.client.LocalTransaction.rollback(LocalTransaction.java:87)
>  at 
> org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.stop(JMSBridgeImpl.java:501)
>  [artemis-jms-server-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1]
>  at 
> 

[jira] [Commented] (ARTEMIS-1787) Openwire message should not contain internal property

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427160#comment-16427160
 ] 

ASF GitHub Bot commented on ARTEMIS-1787:
-

GitHub user stanlyDoge opened a pull request:

https://github.com/apache/activemq-artemis/pull/1994

ARTEMIS-1787 Openwire message should not contain internal property



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

$ git pull https://github.com/stanlyDoge/activemq-artemis ARTEMIS-1787

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

https://github.com/apache/activemq-artemis/pull/1994.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 #1994


commit 0210fee3bc3731e3173f012987bfd9d9f2965958
Author: Stanislav Knot 
Date:   2018-04-05T16:01:41Z

ARTEMIS-1787 Openwire message should not contain internal property




> Openwire message should not contain internal property
> -
>
> Key: ARTEMIS-1787
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1787
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: Stanislav Knot
>Assignee: Stanislav Knot
>Priority: Major
>
> Openwire message contains __AMQ_CID property.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ARTEMIS-1787) Openwire message should not contain internal property

[Stanislav Knot (JIRA)]

Stanislav Knot created ARTEMIS-1787:
---

 Summary: Openwire message should not contain internal property
 Key: ARTEMIS-1787
 URL: https://issues.apache.org/jira/browse/ARTEMIS-1787
 Project: ActiveMQ Artemis
  Issue Type: Bug
Reporter: Stanislav Knot
Assignee: Stanislav Knot


Openwire message contains __AMQ_CID property.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARTEMIS-618) Fails to initialize journal if hard drive block size is over 512 bytes

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427148#comment-16427148
 ] 

ASF subversion and git services commented on ARTEMIS-618:
-

Commit 4dd594f38b30306ae613295127f88d6f043e1300 in activemq-artemis's branch 
refs/heads/master from Clebert Suconic
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=4dd594f ]

ARTEMIS-618 Using proper block size on Native One Mega Buffer

This buffer is used on fill


> Fails to initialize journal if hard drive block size is over 512 bytes
> --
>
> Key: ARTEMIS-618
> URL: https://issues.apache.org/jira/browse/ARTEMIS-618
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Affects Versions: 2.5.0
> Environment: CentOS 7 on hard drive with 4 KB blocks
>Reporter: Rostyslav Smirnov
>Assignee: clebert suconic
>Priority: Major
> Fix For: 2.5.1
>
>
> AIO journal fails to initialize with the following error:
> AMQ224000: Failure in initialisation: java.io.IOException: Cannot initialize 
> file
>   at org.apache.activemq.artemis.jlibaio.LibaioContext.fill(Native 
> Method) [artemis-native-1.3.0.jar:]
>   at 
> org.apache.activemq.artemis.jlibaio.LibaioFile.fill(LibaioFile.java:122) 
> [artemis-native-1.3.0.jar:]
>   at 
> org.apache.activemq.artemis.core.io.aio.AIOSequentialFile.fill(AIOSequentialFile.java:126)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalFilesRepository.createFile0(JournalFilesRepository.java:587)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalFilesRepository.createFile(JournalFilesRepository.java:537)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalFilesRepository.ensureMinFiles(JournalFilesRepository.java:201)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.setUpCurrentFile(JournalImpl.java:2709)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.load(JournalImpl.java:1755)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.load(JournalImpl.java:1135)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.load(JournalImpl.java:1119)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.persistence.impl.journal.AbstractJournalStorageManager.loadMessageJournal(AbstractJournalStorageManager.java:864)
>  [artemis-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.loadJournals(ActiveMQServerImpl.java:2054)
>  [artemis-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.initialisePart2(ActiveMQServerImpl.java:1927)
>  [artemis-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.server.impl.LiveOnlyActivation.run(LiveOnlyActivation.java:63)
>  [artemis-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:427)
>  [artemis-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:394)
>  [artemis-jms-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.integration.FileBroker.start(FileBroker.java:65) 
> [artemis-cli-1.3.0.jar:1.3.0]
>   at org.apache.activemq.artemis.cli.commands.Run.execute(Run.java:83) 
> [artemis-cli-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.cli.Artemis.internalExecute(Artemis.java:110) 
> [artemis-cli-1.3.0.jar:1.3.0]
>   at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:72) 
> [artemis-cli-1.3.0.jar:1.3.0]
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> [rt.jar:1.8.0_65]
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> [rt.jar:1.8.0_65]
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  [rt.jar:1.8.0_65]
>   at java.lang.reflect.Method.invoke(Method.java:497) [rt.jar:1.8.0_65]
>   at org.apache.activemq.artemis.boot.Artemis.execute(Artemis.java:122) 
> [artemis-boot.jar:1.3.0]
>   at org.apache.activemq.artemis.boot.Artemis.main(Artemis.java:45) 
> [artemis-boot.jar:1.3.0]
> This is due to buffers not being aligned for writing to file open with 
> O_DIRECT flag.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARTEMIS-618) Fails to initialize journal if hard drive block size is over 512 bytes

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427149#comment-16427149
 ] 

ASF GitHub Bot commented on ARTEMIS-618:


Github user asfgit closed the pull request at:

https://github.com/apache/activemq-artemis/pull/1993


> Fails to initialize journal if hard drive block size is over 512 bytes
> --
>
> Key: ARTEMIS-618
> URL: https://issues.apache.org/jira/browse/ARTEMIS-618
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Affects Versions: 2.5.0
> Environment: CentOS 7 on hard drive with 4 KB blocks
>Reporter: Rostyslav Smirnov
>Assignee: clebert suconic
>Priority: Major
> Fix For: 2.5.1
>
>
> AIO journal fails to initialize with the following error:
> AMQ224000: Failure in initialisation: java.io.IOException: Cannot initialize 
> file
>   at org.apache.activemq.artemis.jlibaio.LibaioContext.fill(Native 
> Method) [artemis-native-1.3.0.jar:]
>   at 
> org.apache.activemq.artemis.jlibaio.LibaioFile.fill(LibaioFile.java:122) 
> [artemis-native-1.3.0.jar:]
>   at 
> org.apache.activemq.artemis.core.io.aio.AIOSequentialFile.fill(AIOSequentialFile.java:126)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalFilesRepository.createFile0(JournalFilesRepository.java:587)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalFilesRepository.createFile(JournalFilesRepository.java:537)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalFilesRepository.ensureMinFiles(JournalFilesRepository.java:201)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.setUpCurrentFile(JournalImpl.java:2709)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.load(JournalImpl.java:1755)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.load(JournalImpl.java:1135)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.load(JournalImpl.java:1119)
>  [artemis-journal-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.persistence.impl.journal.AbstractJournalStorageManager.loadMessageJournal(AbstractJournalStorageManager.java:864)
>  [artemis-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.loadJournals(ActiveMQServerImpl.java:2054)
>  [artemis-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.initialisePart2(ActiveMQServerImpl.java:1927)
>  [artemis-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.server.impl.LiveOnlyActivation.run(LiveOnlyActivation.java:63)
>  [artemis-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:427)
>  [artemis-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:394)
>  [artemis-jms-server-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.integration.FileBroker.start(FileBroker.java:65) 
> [artemis-cli-1.3.0.jar:1.3.0]
>   at org.apache.activemq.artemis.cli.commands.Run.execute(Run.java:83) 
> [artemis-cli-1.3.0.jar:1.3.0]
>   at 
> org.apache.activemq.artemis.cli.Artemis.internalExecute(Artemis.java:110) 
> [artemis-cli-1.3.0.jar:1.3.0]
>   at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:72) 
> [artemis-cli-1.3.0.jar:1.3.0]
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> [rt.jar:1.8.0_65]
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> [rt.jar:1.8.0_65]
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  [rt.jar:1.8.0_65]
>   at java.lang.reflect.Method.invoke(Method.java:497) [rt.jar:1.8.0_65]
>   at org.apache.activemq.artemis.boot.Artemis.execute(Artemis.java:122) 
> [artemis-boot.jar:1.3.0]
>   at org.apache.activemq.artemis.boot.Artemis.main(Artemis.java:45) 
> [artemis-boot.jar:1.3.0]
> This is due to buffers not being aligned for writing to file open with 
> O_DIRECT flag.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (ARTEMIS-1786) DatabaseStorageConfiguration cannot be configured via system properties

[clebert suconic (JIRA)]

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

clebert suconic closed ARTEMIS-1786.

Resolution: Not A Problem

BeanUtils is being used on Configuration. simply use 
prefix.databaseConfiguration.anythingYouLike=YourValue

> DatabaseStorageConfiguration cannot be configured via system properties
> ---
>
> Key: ARTEMIS-1786
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1786
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 2.5.0
>Reporter: Erich Duda
>Priority: Major
>
> {{ConfigurationImpl}} class has method \[1\] which parses system properties. 
> This enables to define the parameters using the system properties. However 
> {{DatabaseStorageConfiguration}} class doesn't have such feature and thus 
> these parameters cannot be defined by system properties.
> To be consistent, parameters defined in DatabaseStorageConfiguration should 
> be configurable via system properties as well.
> \[1\] 
> https://github.com/apache/activemq-artemis/blob/eec10994720abca9b9b19d09604924083a35d3ea/artemis-server/src/main/java/org/apache/activemq/artemis/core/config/impl/ConfigurationImpl.java#L332



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMQ-6943) ActiveMQ.Advisory.Producer.Queue listener receives RemoveInfo instead of ProducerInfo

[Christopher L. Shannon (JIRA)]

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

Christopher L. Shannon commented on AMQ-6943:
-

This is correct behavior and not an issue (the documentation probably just 
needs updating).  The remove info will contain the producer Id so you can use 
that to figure out when a producer was removed. 

If you want to know when a destination has no more producers you could figure 
this out by listening for the producer creation advisories and then tracking 
all the producers on a destination somehow (map or some other data structure, 
etc). Then when the RemoveInfo is received you can get the producer Id and 
remove that producer from your tracking.

> ActiveMQ.Advisory.Producer.Queue listener receives RemoveInfo instead of 
> ProducerInfo
> -
>
> Key: AMQ-6943
> URL: https://issues.apache.org/jira/browse/AMQ-6943
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.15.3
> Environment: Windows and Red Hat.
>Reporter: Reid Sommerville
>Priority: Major
>
> According to the page [http://activemq.apache.org/advisory-message.html] when 
> listening to the advisory ActiveMQ.Advisory.Producer.Queue a ProducerInfo 
> should be sent when a producer starts/stops. The ProducerInfo message is sent 
> with the expected value in the "producerCount" attribute when the producer is 
> created, however on calling producer.close() I receive in my listener a 
> RemoveInfo message.
> My intention is to detect when a queue has 0 producers so I can terminate the 
> consumer so the Queue can be deleted by the gcInactiveDestinations support 
> however the RemoveInfo has no getDestination() member to provide information 
> on what queue the closed producer was attached to.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (AMQ-6943) ActiveMQ.Advisory.Producer.Queue listener receives RemoveInfo instead of ProducerInfo

[Christopher L. Shannon (JIRA)]

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

Christopher L. Shannon closed AMQ-6943.
---
Resolution: Not A Problem

> ActiveMQ.Advisory.Producer.Queue listener receives RemoveInfo instead of 
> ProducerInfo
> -
>
> Key: AMQ-6943
> URL: https://issues.apache.org/jira/browse/AMQ-6943
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.15.3
> Environment: Windows and Red Hat.
>Reporter: Reid Sommerville
>Priority: Major
>
> According to the page [http://activemq.apache.org/advisory-message.html] when 
> listening to the advisory ActiveMQ.Advisory.Producer.Queue a ProducerInfo 
> should be sent when a producer starts/stops. The ProducerInfo message is sent 
> with the expected value in the "producerCount" attribute when the producer is 
> created, however on calling producer.close() I receive in my listener a 
> RemoveInfo message.
> My intention is to detect when a queue has 0 producers so I can terminate the 
> consumer so the Queue can be deleted by the gcInactiveDestinations support 
> however the RemoveInfo has no getDestination() member to provide information 
> on what queue the closed producer was attached to.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARTEMIS-1770) Warnings/Errors during clean shutdown of server with JMS Bridge

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426918#comment-16426918
 ] 

ASF GitHub Bot commented on ARTEMIS-1770:
-

Github user asfgit closed the pull request at:

https://github.com/apache/activemq-artemis/pull/1990


> Warnings/Errors during clean shutdown of server with JMS Bridge
> ---
>
> Key: ARTEMIS-1770
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1770
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Affects Versions: 1.5.6, 2.5.0
>Reporter: Radovan Stancel
>Priority: Major
>
> If server with JMS bridge is cleanly shutdown then following errors appears 
> in the server log:
> {code}
> 16:03:06,458 ERROR [org.apache.activemq.artemis.core.client] (ServerService 
> Thread Pool -- 76) AMQ214004: XA end operation failed : 
> ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119010: 
> Connection is destroyed]
>  at 
> org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:338)
>  [artemis-core-client-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1]
>  at 
> org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:318)
>  [artemis-core-client-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1]
>  at 
> org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQSessionContext.xaEnd(ActiveMQSessionContext.java:383)
>  [artemis-core-client-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1]
>  at 
> org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.end(ClientSessionImpl.java:1173)
>  [artemis-core-client-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1]
>  at 
> com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.doEnd(TransactionImple.java:1069)
>  [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.endAssociation(TransactionImple.java:1040)
>  [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.endAssociation(XAResourceRecord.java:1287)
>  [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelAbort(XAResourceRecord.java:313)
>  [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:3023) 
> [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:3002) 
> [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.arjuna.coordinator.BasicAction.Abort(BasicAction.java:1674) 
> [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.cancel(TwoPhaseCoordinator.java:124)
>  [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at com.arjuna.ats.arjuna.AtomicAction.cancel(AtomicAction.java:215) 
> [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.rollback(TransactionImple.java:284)
>  [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider$Entry.rollbackLocal(JBossLocalTransactionProvider.java:317)
>  at 
> org.wildfly.transaction.client.provider.jboss.JBossJTALocalTransactionProvider.rollbackLocal(JBossJTALocalTransactionProvider.java:116)
>  at 
> org.wildfly.transaction.client.LocalTransaction.rollback(LocalTransaction.java:87)
>  at 
> org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.stop(JMSBridgeImpl.java:501)
>  [artemis-jms-server-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1]
>  at 
> org.wildfly.extension.messaging.activemq.jms.bridge.JMSBridgeService$2.run(JMSBridgeService.java:127)
>  
> [wildfly-messaging-activemq-7.1.0.Alpha1-redhat-15.jar:7.1.0.Alpha1-redhat-15]
>  at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [rt.jar:1.8.0_71]
>  at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [rt.jar:1.8.0_71]
>  at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_71]
>  at org.jboss.threads.JBossThread.run(JBossThread.java:320) 
> [jboss-threads-2.2.1.Final-redhat-1.jar:2.2.1.Final-redhat-1]
> 16:03:06,464 WARN [com.arjuna.ats.jta] (ServerService Thread Pool -- 76) 
> ARJUNA016129: Could not end XA 

[jira] [Commented] (ARTEMIS-1770) Warnings/Errors during clean shutdown of server with JMS Bridge

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426917#comment-16426917
 ] 

ASF subversion and git services commented on ARTEMIS-1770:
--

Commit 10849eb8abc01b8ae66c9ddeb350625efbc66384 in activemq-artemis's branch 
refs/heads/master from [~rstancel]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=10849eb ]

[ARTEMIS-1770] Log warning when connection is closed


> Warnings/Errors during clean shutdown of server with JMS Bridge
> ---
>
> Key: ARTEMIS-1770
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1770
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Affects Versions: 1.5.6, 2.5.0
>Reporter: Radovan Stancel
>Priority: Major
>
> If server with JMS bridge is cleanly shutdown then following errors appears 
> in the server log:
> {code}
> 16:03:06,458 ERROR [org.apache.activemq.artemis.core.client] (ServerService 
> Thread Pool -- 76) AMQ214004: XA end operation failed : 
> ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119010: 
> Connection is destroyed]
>  at 
> org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:338)
>  [artemis-core-client-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1]
>  at 
> org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:318)
>  [artemis-core-client-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1]
>  at 
> org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQSessionContext.xaEnd(ActiveMQSessionContext.java:383)
>  [artemis-core-client-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1]
>  at 
> org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.end(ClientSessionImpl.java:1173)
>  [artemis-core-client-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1]
>  at 
> com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.doEnd(TransactionImple.java:1069)
>  [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.endAssociation(TransactionImple.java:1040)
>  [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.endAssociation(XAResourceRecord.java:1287)
>  [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelAbort(XAResourceRecord.java:313)
>  [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:3023) 
> [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:3002) 
> [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.arjuna.coordinator.BasicAction.Abort(BasicAction.java:1674) 
> [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.cancel(TwoPhaseCoordinator.java:124)
>  [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at com.arjuna.ats.arjuna.AtomicAction.cancel(AtomicAction.java:215) 
> [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.rollback(TransactionImple.java:284)
>  [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider$Entry.rollbackLocal(JBossLocalTransactionProvider.java:317)
>  at 
> org.wildfly.transaction.client.provider.jboss.JBossJTALocalTransactionProvider.rollbackLocal(JBossJTALocalTransactionProvider.java:116)
>  at 
> org.wildfly.transaction.client.LocalTransaction.rollback(LocalTransaction.java:87)
>  at 
> org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.stop(JMSBridgeImpl.java:501)
>  [artemis-jms-server-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1]
>  at 
> org.wildfly.extension.messaging.activemq.jms.bridge.JMSBridgeService$2.run(JMSBridgeService.java:127)
>  
> [wildfly-messaging-activemq-7.1.0.Alpha1-redhat-15.jar:7.1.0.Alpha1-redhat-15]
>  at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [rt.jar:1.8.0_71]
>  at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [rt.jar:1.8.0_71]
>  at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_71]
>  at org.jboss.threads.JBossThread.run(JBossThread.java:320) 
> 

[jira] [Updated] (AMQ-6943) ActiveMQ.Advisory.Producer.Queue listener receives RemoveInfo instead of ProducerInfo

[Reid Sommerville (JIRA)]

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

Reid Sommerville updated AMQ-6943:
--
Description: 
According to the page [http://activemq.apache.org/advisory-message.html] when 
listening to the advisory ActiveMQ.Advisory.Producer.Queue a ProducerInfo 
should be sent when a producer starts/stops. The ProducerInfo message is sent 
with the expected value in the "producerCount" attribute when the producer is 
created, however on calling producer.close() I receive in my listener a 
RemoveInfo message.

My intention is to detect when a queue has 0 producers so I can terminate the 
consumer so the Queue can be deleted by the gcInactiveDestinations support 
however the RemoveInfo has no getDestination() member to provide information on 
what queue the closed producer was attached to.

  was:
According to the page [http://activemq.apache.org/advisory-message.html] when 
listening to the advisory ActiveMQ.Advisory.Producer.Queue a ProducerInfo 
should be sent when a producer starts/stops. The ProducerInfo message is sent 
with the expected value in the "producerCount" attribute however on calling 
producer.close() I receive in my listener a RemoveInfo message.

My intention is to detect when a queue has 0 producers so I can terminate the 
consumer so the Queue can be delered by the gcInactiveDestinations support 
however then RemoveInfo has no getDestination() member to provide information 
on what queue the closed producer was attached to.


> ActiveMQ.Advisory.Producer.Queue listener receives RemoveInfo instead of 
> ProducerInfo
> -
>
> Key: AMQ-6943
> URL: https://issues.apache.org/jira/browse/AMQ-6943
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.15.3
> Environment: Windows and Red Hat.
>Reporter: Reid Sommerville
>Priority: Major
>
> According to the page [http://activemq.apache.org/advisory-message.html] when 
> listening to the advisory ActiveMQ.Advisory.Producer.Queue a ProducerInfo 
> should be sent when a producer starts/stops. The ProducerInfo message is sent 
> with the expected value in the "producerCount" attribute when the producer is 
> created, however on calling producer.close() I receive in my listener a 
> RemoveInfo message.
> My intention is to detect when a queue has 0 producers so I can terminate the 
> consumer so the Queue can be deleted by the gcInactiveDestinations support 
> however the RemoveInfo has no getDestination() member to provide information 
> on what queue the closed producer was attached to.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMQ-6943) ActiveMQ.Advisory.Producer.Queue listener receives RemoveInfo instead of ProducerInfo

[Reid Sommerville (JIRA)]

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

Reid Sommerville updated AMQ-6943:
--
Summary: ActiveMQ.Advisory.Producer.Queue listener receives RemoveInfo 
instead of ProducerInfo  (was: ActiveMQ.Advisory.Producer.Queue listener 
recieves RemoveInfo instead of ProducerInfo)

> ActiveMQ.Advisory.Producer.Queue listener receives RemoveInfo instead of 
> ProducerInfo
> -
>
> Key: AMQ-6943
> URL: https://issues.apache.org/jira/browse/AMQ-6943
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.15.3
> Environment: Windows and Red Hat.
>Reporter: Reid Sommerville
>Priority: Major
>
> According to the page [http://activemq.apache.org/advisory-message.html] when 
> listening to the advisory ActiveMQ.Advisory.Producer.Queue a ProducerInfo 
> should be sent when a producer starts/stops. The ProducerInfo message is sent 
> with the expected value in the "producerCount" attribute however on calling 
> producer.close() I receive in my listener a RemoveInfo message.
> My intention is to detect when a queue has 0 producers so I can terminate the 
> consumer so the Queue can be delered by the gcInactiveDestinations support 
> however then RemoveInfo has no getDestination() member to provide information 
> on what queue the closed producer was attached to.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (AMQ-6943) ActiveMQ.Advisory.Producer.Queue listener recieves RemoveInfo instead of ProducerInfo

[Reid Sommerville (JIRA)]

Reid Sommerville created AMQ-6943:
-

 Summary: ActiveMQ.Advisory.Producer.Queue listener recieves 
RemoveInfo instead of ProducerInfo
 Key: AMQ-6943
 URL: https://issues.apache.org/jira/browse/AMQ-6943
 Project: ActiveMQ
  Issue Type: Bug
Affects Versions: 5.15.3
 Environment: Windows and Red Hat.
Reporter: Reid Sommerville


According to the page [http://activemq.apache.org/advisory-message.html] when 
listening to the advisory ActiveMQ.Advisory.Producer.Queue a ProducerInfo 
should be sent when a producer starts/stops. The ProducerInfo message is sent 
with the expected value in the "producerCount" attribute however on calling 
producer.close() I receive in my listener a RemoveInfo message.

My intention is to detect when a queue has 0 producers so I can terminate the 
consumer so the Queue can be delered by the gcInactiveDestinations support 
however then RemoveInfo has no getDestination() member to provide information 
on what queue the closed producer was attached to.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARTEMIS-1653) Allow database tables to be created externally

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426839#comment-16426839
 ] 

ASF GitHub Bot commented on ARTEMIS-1653:
-

Github user franz1981 closed the pull request at:

https://github.com/apache/activemq-artemis/pull/1986


> Allow database tables to be created externally
> --
>
> Key: ARTEMIS-1653
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1653
> Project: ActiveMQ Artemis
>  Issue Type: Improvement
>  Components: Broker
>Affects Versions: 2.4.0
>Reporter: Niels Lippke
>Assignee: Francesco Nigro
>Priority: Major
>
> In some environments (e.g. production) it is not allowed that applications 
> create their own schema. It's common practice to pass DDL-Statetements to 
> DBAs instead prior to rollout.
> Currently the broker does not support this scenario. If the required tables 
> already exist the broker fails to start.
> A better approach is that if the broker detects empy tables and initializes 
> them in the very same way it does if the tables dont't exist.
> See also discussion in 
> [forum|http://activemq.2283324.n4.nabble.com/ARTEMIS-Server-doesn-t-start-if-JDBC-store-is-used-and-table-NODE-MANAGER-STORE-is-empty-td4735779.html].



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARTEMIS-1653) Allow database tables to be created externally

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426811#comment-16426811
 ] 

ASF GitHub Bot commented on ARTEMIS-1653:
-

Github user franz1981 commented on a diff in the pull request:

https://github.com/apache/activemq-artemis/pull/1986#discussion_r179441774
  
--- Diff: 
artemis-jdbc-store/src/main/java/org/apache/activemq/artemis/jdbc/store/drivers/AbstractJDBCDriver.java
 ---
@@ -191,9 +191,18 @@ private void createTableIfNotExists(String tableName, 
String... sqls) throws SQL
 } else {
try (Statement statement = connection.createStatement();
  ResultSet cntRs = 
statement.executeQuery(sqlProvider.getCountJournalRecordsSQL())) {
-  if (rs.next() && rs.getInt(1) > 0) {
+  int rows;
+  if (cntRs.next() && (rows = cntRs.getInt(1)) > 0) {
  logger.tracef("Table %s did exist but is not empty. 
Skipping initialization.", tableName);
+ if (logger.isDebugEnabled()) {
+final long expectedRows = 
Stream.of(sqls).map(String::toUpperCase).filter(sql -> sql.contains("INSERT 
INTO")).count();
--- End diff --

@clebertsuconic PLease do not merge it yet...because on DB2 it is creating 
some problems


> Allow database tables to be created externally
> --
>
> Key: ARTEMIS-1653
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1653
> Project: ActiveMQ Artemis
>  Issue Type: Improvement
>  Components: Broker
>Affects Versions: 2.4.0
>Reporter: Niels Lippke
>Assignee: Francesco Nigro
>Priority: Major
>
> In some environments (e.g. production) it is not allowed that applications 
> create their own schema. It's common practice to pass DDL-Statetements to 
> DBAs instead prior to rollout.
> Currently the broker does not support this scenario. If the required tables 
> already exist the broker fails to start.
> A better approach is that if the broker detects empy tables and initializes 
> them in the very same way it does if the tables dont't exist.
> See also discussion in 
> [forum|http://activemq.2283324.n4.nabble.com/ARTEMIS-Server-doesn-t-start-if-JDBC-store-is-used-and-table-NODE-MANAGER-STORE-is-empty-td4735779.html].



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ARTEMIS-1786) DatabaseStorageConfiguration cannot be configured via system properties

[Erich Duda (JIRA)]

Erich Duda created ARTEMIS-1786:
---

 Summary: DatabaseStorageConfiguration cannot be configured via 
system properties
 Key: ARTEMIS-1786
 URL: https://issues.apache.org/jira/browse/ARTEMIS-1786
 Project: ActiveMQ Artemis
  Issue Type: Bug
  Components: Broker
Affects Versions: 2.5.0
Reporter: Erich Duda


{{ConfigurationImpl}} class has method \[1\] which parses system properties. 
This enables to define the parameters using the system properties. However 
{{DatabaseStorageConfiguration}} class doesn't have such feature and thus these 
parameters cannot be defined by system properties.

To be consistent, parameters defined in DatabaseStorageConfiguration should be 
configurable via system properties as well.

\[1\] 
https://github.com/apache/activemq-artemis/blob/eec10994720abca9b9b19d09604924083a35d3ea/artemis-server/src/main/java/org/apache/activemq/artemis/core/config/impl/ConfigurationImpl.java#L332



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARTEMIS-1781) Broken backward compatibility with HornetQ

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426662#comment-16426662
 ] 

ASF GitHub Bot commented on ARTEMIS-1781:
-

Github user TomasHofman commented on the issue:

https://github.com/apache/activemq-artemis/pull/1987
  
@clebertsuconic I added my attempt at compatibility test.


> Broken backward compatibility with HornetQ
> --
>
> Key: ARTEMIS-1781
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1781
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Affects Versions: 1.5.5, 2.5.0
>Reporter: Tomas Hofman
>Priority: Major
>
> When connector is configured to use SSL encryption, HornetQ client receives 
> invalid parameter keys - camelCase instead of dash-separated.
> {code:java}
> 2018-01-23 17:39:32,769 logLev=WARN class=org.hornetq.jms.server 
> thread="Periodic Recovery" HQ122015: Can not connect to XARecoveryConfig 
> [transportConfiguration = [TransportConfiguration(name=hornetq-ssl-connector, 
> factory=org-hornetq-core-remoting-impl-netty-NettyConnectorFactory) 
> ?trustStorePassword=123456=123456=5500=true=ld9c02ad-umobi-mobicorp-test=/data/jboss/server/mobi/configuration/keys/jspStore_dev-jks=/data/jboss/server/mobi/configuration/keys/mobiJspDynWesTrust_dev-jks],
>  discoveryConfiguration = null, username=Z100283, password=] on 
> auto-generated resource recovery: java.lang.IllegalStateException: The 
> following keys are invalid for configuring a connector: trustStorePassword, 
> keyStorePassword, sslEnabled, trustStorePath, keyStorePath
>     at 
> org.hornetq.core.client.impl.ClientSessionFactoryImpl.checkTransportKeys(ClientSessionFactoryImpl.java:1542)
>     at 
> org.hornetq.core.client.impl.ClientSessionFactoryImpl.(ClientSessionFactoryImpl.java:212)
>     at 
> org.hornetq.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:872)
>     at 
> org.hornetq.jms.server.recovery.HornetQXAResourceWrapper.connect(HornetQXAResourceWrapper.java:377)
>     at 
> org.hornetq.jms.server.recovery.HornetQXAResourceWrapper.getDelegate(HornetQXAResourceWrapper.java:286)
>     at 
> org.hornetq.jms.server.recovery.HornetQXAResourceWrapper.recover(HornetQXAResourceWrapper.java:74)
>     at 
> com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoveryFirstPass(XARecoveryModule.java:541)
>     at 
> com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkFirstPass(XARecoveryModule.java:181)
>     at 
> com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:747)
>     at 
> com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:375)
> {code}
> Original issue: https://issues.jboss.org/browse/ENTMQBR-1034



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARTEMIS-1770) Warnings/Errors during clean shutdown of server with JMS Bridge

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426526#comment-16426526
 ] 

ASF GitHub Bot commented on ARTEMIS-1770:
-

Github user rstancel commented on a diff in the pull request:

https://github.com/apache/activemq-artemis/pull/1990#discussion_r179361706
  
--- Diff: 
artemis-core-client/src/main/java/org/apache/activemq/artemis/core/client/impl/ClientSessionImpl.java
 ---
@@ -1539,6 +1540,8 @@ public void end(final Xid xid, final int flags) 
throws XAException {
 startCall();
 try {
sessionContext.xaEnd(xid, flags);
+} catch (ActiveMQNotConnectedException ex) {
+   
ActiveMQClientLogger.LOGGER.connectionClosedWarn(ex.getType(), ex.getMessage());
--- End diff --

@clebertsuconic Done.


> Warnings/Errors during clean shutdown of server with JMS Bridge
> ---
>
> Key: ARTEMIS-1770
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1770
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Affects Versions: 1.5.6, 2.5.0
>Reporter: Radovan Stancel
>Priority: Major
>
> If server with JMS bridge is cleanly shutdown then following errors appears 
> in the server log:
> {code}
> 16:03:06,458 ERROR [org.apache.activemq.artemis.core.client] (ServerService 
> Thread Pool -- 76) AMQ214004: XA end operation failed : 
> ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119010: 
> Connection is destroyed]
>  at 
> org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:338)
>  [artemis-core-client-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1]
>  at 
> org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:318)
>  [artemis-core-client-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1]
>  at 
> org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQSessionContext.xaEnd(ActiveMQSessionContext.java:383)
>  [artemis-core-client-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1]
>  at 
> org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.end(ClientSessionImpl.java:1173)
>  [artemis-core-client-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1]
>  at 
> com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.doEnd(TransactionImple.java:1069)
>  [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.endAssociation(TransactionImple.java:1040)
>  [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.endAssociation(XAResourceRecord.java:1287)
>  [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelAbort(XAResourceRecord.java:313)
>  [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:3023) 
> [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:3002) 
> [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.arjuna.coordinator.BasicAction.Abort(BasicAction.java:1674) 
> [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.cancel(TwoPhaseCoordinator.java:124)
>  [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at com.arjuna.ats.arjuna.AtomicAction.cancel(AtomicAction.java:215) 
> [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.rollback(TransactionImple.java:284)
>  [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision: 
> c79e6)]
>  at 
> org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider$Entry.rollbackLocal(JBossLocalTransactionProvider.java:317)
>  at 
> org.wildfly.transaction.client.provider.jboss.JBossJTALocalTransactionProvider.rollbackLocal(JBossJTALocalTransactionProvider.java:116)
>  at 
> org.wildfly.transaction.client.LocalTransaction.rollback(LocalTransaction.java:87)
>  at 
> org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.stop(JMSBridgeImpl.java:501)
>  [artemis-jms-server-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1]
>  at 
> org.wildfly.extension.messaging.activemq.jms.bridge.JMSBridgeService$2.run(JMSBridgeService.java:127)
>  
>