[jira] [Commented] (ARTEMIS-1227) Internal properties not removed from messages

2017-10-09 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on ARTEMIS-1227:
-

GitHub user gaohoward opened a pull request:

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

ARTEMIS-1227 Internal properties not removed from messages

In a cluster if a node is shut down (or crashed) when a
message is being routed to a remote binding, a internal
property may be added to the message and persisted. The
name of the property is like _AMQ_ROUTE_TOsf.my-cluster*.
if the node starts back, it will load and reroute this message
and if it goes to a local consumer, this property won't
get removed and goes to the client.

The fix is to remove this internal property before it
is sent to any client.

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

$ git pull https://github.com/gaohoward/activemq-artemis k_a1227

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

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


commit 312d53d5abe7949f554a00bcf6e7f0dc2c44507e
Author: Howard Gao 
Date:   2017-10-10T01:14:32Z

ARTEMIS-1227 Internal properties not removed from messages

In a cluster if a node is shut down (or crashed) when a
message is being routed to a remote binding, a internal
property may be added to the message and persisted. The
name of the property is like _AMQ_ROUTE_TOsf.my-cluster*.
if the node starts back, it will load and reroute this message
and if it goes to a local consumer, this property won't
get removed and goes to the client.

The fix is to remove this internal property before it
is sent to any client.




> Internal properties not removed from messages
> -
>
> Key: ARTEMIS-1227
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1227
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 1.5.5, 2.1.0
>Reporter: Howard Gao
>Assignee: Howard Gao
> Fix For: unscheduled
>
>
> In a cluster if a node is shut down (or crashed) when a
> message is being routed to a remote binding, a internal
> property may be added to the message and persisted. The
> name of the property is like _AMQ_ROUTE_TOsf.my-cluster*.
> if the node starts back, it will load and reroute this message
> and if it goes to a local consumer, this property won't
> get removed and goes to the client.
> The fix is to remove this internal property before it
> is sent to any client.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1446) Support passing in properties to Transformers for configuration

2017-10-09 Thread ASF subversion and git services (JIRA) 

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

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

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

ARTEMIS-1446 fixing test


> Support passing in properties to Transformers for configuration
> ---
>
> Key: ARTEMIS-1446
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1446
> Project: ActiveMQ Artemis
>  Issue Type: Improvement
>Reporter: Michael Andre Pearce
>Assignee: Michael Andre Pearce
>
> Currently Bridge and Divert Transformers do not allow any configuration, as 
> such if you need the same transformer but just slightly different 
> configuration that could be managed by classical properties you need to make 
> concrete classes for each one.
> This is to allow passing in configuration properties into the transformers so 
> transformer implementations can be made more generic and re-usable and simply 
> configurable.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1446) Support passing in properties to Transformers for configuration

2017-10-09 Thread ASF subversion and git services (JIRA) 

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

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

Commit 4db8cd54ca2174357e36e4f0c231ad66f128d8b8 in activemq-artemis's branch 
refs/heads/master from [~michael.andre.pearce]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=4db8cd5 ]

ARTEMIS-1446 - Support Transformer configuration by properties

Update Tranformer to be able to handle initiation via propertiers (map)
Update Configuration to have more specific transfromer configuration type, and 
to take properties.
Support back compatibility.
Add AddHeadersTransformer which is a main use case, and can act as example also.
Update Control's to expose new property configuration
Add test cases
Update examples for new transformer config style


> Support passing in properties to Transformers for configuration
> ---
>
> Key: ARTEMIS-1446
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1446
> Project: ActiveMQ Artemis
>  Issue Type: Improvement
>Reporter: Michael Andre Pearce
>Assignee: Michael Andre Pearce
>
> Currently Bridge and Divert Transformers do not allow any configuration, as 
> such if you need the same transformer but just slightly different 
> configuration that could be managed by classical properties you need to make 
> concrete classes for each one.
> This is to allow passing in configuration properties into the transformers so 
> transformer implementations can be made more generic and re-usable and simply 
> configurable.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1446) Support passing in properties to Transformers for configuration

2017-10-09 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on ARTEMIS-1446:
-

Github user asfgit closed the pull request at:

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


> Support passing in properties to Transformers for configuration
> ---
>
> Key: ARTEMIS-1446
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1446
> Project: ActiveMQ Artemis
>  Issue Type: Improvement
>Reporter: Michael Andre Pearce
>Assignee: Michael Andre Pearce
>
> Currently Bridge and Divert Transformers do not allow any configuration, as 
> such if you need the same transformer but just slightly different 
> configuration that could be managed by classical properties you need to make 
> concrete classes for each one.
> This is to allow passing in configuration properties into the transformers so 
> transformer implementations can be made more generic and re-usable and simply 
> configurable.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMQ-6831) Broker fails to start complaining about missing/corrupt journal files after upgrading to 5.15.1

2017-10-09 Thread masc (JIRA) 

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

masc commented on AMQ-6831:
---

yes sorry, checked again and replaced the archive with the full kahadb folder

> Broker fails to start complaining about missing/corrupt journal files after 
> upgrading to 5.15.1
> ---
>
> Key: AMQ-6831
> URL: https://issues.apache.org/jira/browse/AMQ-6831
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.15.1
>Reporter: masc
> Attachments: kahadb.zip
>
>
> {code}
> 2017-10-09 12:29:36.802 ERROR 4197 --- [pool-3-thread-1] 
> org.deku.leoz.node.Application   : java.io.IOException: Detected 
> missing/corrupt journal files referenced by:[0:ActiveMQ.DLQ] 3 messages 
> affected.
> java.lang.Error: java.io.IOException: Detected missing/corrupt journal files 
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1148)
>  ~[na:1.8.0_131]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  ~[na:1.8.0_131]
>   at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_131]
> Caused by: java.io.IOException: Detected missing/corrupt journal files 
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.recoverIndex(MessageDatabase.java:965)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase$5.execute(MessageDatabase.java:717)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.disk.page.Transaction.execute(Transaction.java:779)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:714)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219) 
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55) 
> ~[activemq-client-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:232)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> {code}
> Downgrading to 5.15.0 resolves the problem.
> This is an embedded broker setup, using
> {code:none}
> val pa = brokerService.persistenceAdapter as KahaDBPersistenceAdapter
> pa.isCheckForCorruptJournalFiles = true
> pa.isIgnoreMissingJournalfiles = false
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMQ-6831) Broker fails to start complaining about missing/corrupt journal files after upgrading to 5.15.1

2017-10-09 Thread masc (JIRA) 

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

masc updated AMQ-6831:
--
Attachment: kahadb.zip

> Broker fails to start complaining about missing/corrupt journal files after 
> upgrading to 5.15.1
> ---
>
> Key: AMQ-6831
> URL: https://issues.apache.org/jira/browse/AMQ-6831
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.15.1
>Reporter: masc
> Attachments: kahadb.zip
>
>
> {code}
> 2017-10-09 12:29:36.802 ERROR 4197 --- [pool-3-thread-1] 
> org.deku.leoz.node.Application   : java.io.IOException: Detected 
> missing/corrupt journal files referenced by:[0:ActiveMQ.DLQ] 3 messages 
> affected.
> java.lang.Error: java.io.IOException: Detected missing/corrupt journal files 
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1148)
>  ~[na:1.8.0_131]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  ~[na:1.8.0_131]
>   at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_131]
> Caused by: java.io.IOException: Detected missing/corrupt journal files 
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.recoverIndex(MessageDatabase.java:965)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase$5.execute(MessageDatabase.java:717)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.disk.page.Transaction.execute(Transaction.java:779)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:714)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219) 
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55) 
> ~[activemq-client-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:232)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> {code}
> Downgrading to 5.15.0 resolves the problem.
> This is an embedded broker setup, using
> {code:none}
> val pa = brokerService.persistenceAdapter as KahaDBPersistenceAdapter
> pa.isCheckForCorruptJournalFiles = true
> pa.isIgnoreMissingJournalfiles = false
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMQ-6831) Broker fails to start complaining about missing/corrupt journal files after upgrading to 5.15.1

2017-10-09 Thread masc (JIRA) 

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

masc updated AMQ-6831:
--
Attachment: (was: kahadb.zip)

> Broker fails to start complaining about missing/corrupt journal files after 
> upgrading to 5.15.1
> ---
>
> Key: AMQ-6831
> URL: https://issues.apache.org/jira/browse/AMQ-6831
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.15.1
>Reporter: masc
>
> {code}
> 2017-10-09 12:29:36.802 ERROR 4197 --- [pool-3-thread-1] 
> org.deku.leoz.node.Application   : java.io.IOException: Detected 
> missing/corrupt journal files referenced by:[0:ActiveMQ.DLQ] 3 messages 
> affected.
> java.lang.Error: java.io.IOException: Detected missing/corrupt journal files 
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1148)
>  ~[na:1.8.0_131]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  ~[na:1.8.0_131]
>   at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_131]
> Caused by: java.io.IOException: Detected missing/corrupt journal files 
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.recoverIndex(MessageDatabase.java:965)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase$5.execute(MessageDatabase.java:717)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.disk.page.Transaction.execute(Transaction.java:779)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:714)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219) 
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55) 
> ~[activemq-client-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:232)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> {code}
> Downgrading to 5.15.0 resolves the problem.
> This is an embedded broker setup, using
> {code:none}
> val pa = brokerService.persistenceAdapter as KahaDBPersistenceAdapter
> pa.isCheckForCorruptJournalFiles = true
> pa.isIgnoreMissingJournalfiles = false
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1447) JDBC NodeManager to support JDBC HA Shared Store

2017-10-09 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on ARTEMIS-1447:
-

Github user clebertsuconic commented on the issue:

https://github.com/apache/activemq-artemis/pull/1576
  
```
  insertStateOnNodeManagerStoreTableSQL = "INSERT INTO " + tableName + 
" (ID) VALUES (0)";
  insertNodeIdOnNodeManagerStoreTableSQL = "INSERT INTO " + tableName + 
" (ID) VALUES (3)";
  insertLiveLockOnNodeManagerStoreTableSQL = "INSERT INTO " + tableName 
+ " (ID) VALUES (1)";
  insertBackupLockOnNodeManagerStoreTableSQL = "INSERT INTO " + 
tableName + " (ID) VALUES (2)";
```

Wouldn't be better to have a single statement (Using a separate table as I 
had already asked).. using prepared statements?

I'm a bit concerned also that the semantic of 1, 2 and 3.. is inside the 
literal string.. and I see no references on the LeaseLock implementation. I 
wouldn't understand how to debug this.. it makes it harder to maintain IMO.


> JDBC NodeManager to support JDBC HA Shared Store
> 
>
> Key: ARTEMIS-1447
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1447
> Project: ActiveMQ Artemis
>  Issue Type: New Feature
>  Components: Broker
>Reporter: Francesco Nigro
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1447) JDBC NodeManager to support JDBC HA Shared Store

2017-10-09 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on ARTEMIS-1447:
-

Github user clebertsuconic commented on the issue:

https://github.com/apache/activemq-artemis/pull/1576
  
for the JdbcNodeManager:

The package server.impl is already bloated.. I tried once to refactor it 
into smaller packages...

This is a nice abstract model you have, but instead of the big class, cal 
you create a packet jdbcNodeManager, and add your classes there?



Also, instead of creating your own scheduledExecutor.. Please extend 
ActiveMQScheduledComponent... if you can reuse the same executors that we 
already have created, just pass in the scheduledService as a parameter... and 
if you must create a new ScheduledService, you can still use the same class for 
that.


> JDBC NodeManager to support JDBC HA Shared Store
> 
>
> Key: ARTEMIS-1447
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1447
> Project: ActiveMQ Artemis
>  Issue Type: New Feature
>  Components: Broker
>Reporter: Francesco Nigro
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1447) JDBC NodeManager to support JDBC HA Shared Store

2017-10-09 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on ARTEMIS-1447:
-

Github user clebertsuconic commented on the issue:

https://github.com/apache/activemq-artemis/pull/1576
  
Instead of using the Journal Table for the locks... please create another 
Table for that.

To be honest... I don't understand what's going on with the data.. and this 
will be pretty hard to be maintained by someone else if you just use a single 
table for things like this.


> JDBC NodeManager to support JDBC HA Shared Store
> 
>
> Key: ARTEMIS-1447
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1447
> Project: ActiveMQ Artemis
>  Issue Type: New Feature
>  Components: Broker
>Reporter: Francesco Nigro
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ARTEMIS-1318) Uses unbuffered MAPPED Journal if no data-sync is required

2017-10-09 Thread clebert suconic (JIRA) 

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

clebert suconic updated ARTEMIS-1318:
-
Description: 
It is now possible to disable the Buffer timing by setting the timer to 0.

The CLI create will set the journal type to MAPPED if no-fsync is selected 
(with a question through input), and it will disable timing on that case.

  was:
Disable the TimedBuffer on MAPPED journal if no data-sync in required:
* reduced footprint (no TimedBuffer)
* reduced CPU usage (less buffer copy and no TimedBuffer background timer 
thread)
* reduced latencies (not timeout can influence when the write will happen)


> Uses unbuffered MAPPED Journal if no data-sync is required
> --
>
> Key: ARTEMIS-1318
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1318
> Project: ActiveMQ Artemis
>  Issue Type: Improvement
>Reporter: Francesco Nigro
>Assignee: Francesco Nigro
> Fix For: 2.4.0
>
>
> It is now possible to disable the Buffer timing by setting the timer to 0.
> The CLI create will set the journal type to MAPPED if no-fsync is selected 
> (with a question through input), and it will disable timing on that case.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (ARTEMIS-1318) Uses unbuffered MAPPED Journal if no data-sync is required

2017-10-09 Thread clebert suconic (JIRA) 

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

clebert suconic closed ARTEMIS-1318.

Resolution: Fixed

> Uses unbuffered MAPPED Journal if no data-sync is required
> --
>
> Key: ARTEMIS-1318
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1318
> Project: ActiveMQ Artemis
>  Issue Type: Improvement
>Reporter: Francesco Nigro
>Assignee: Francesco Nigro
> Fix For: 2.4.0
>
>
> It is now possible to disable the Buffer timing by setting the timer to 0.
> The CLI create will set the journal type to MAPPED if no-fsync is selected 
> (with a question through input), and it will disable timing on that case.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ARTEMIS-1318) Uses unbuffered MAPPED Journal if no data-sync is required

2017-10-09 Thread clebert suconic (JIRA) 

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

clebert suconic updated ARTEMIS-1318:
-
Fix Version/s: 2.4.0

> Uses unbuffered MAPPED Journal if no data-sync is required
> --
>
> Key: ARTEMIS-1318
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1318
> Project: ActiveMQ Artemis
>  Issue Type: Improvement
>Reporter: Francesco Nigro
>Assignee: Francesco Nigro
> Fix For: 2.4.0
>
>
> Disable the TimedBuffer on MAPPED journal if no data-sync in required:
> * reduced footprint (no TimedBuffer)
> * reduced CPU usage (less buffer copy and no TimedBuffer background timer 
> thread)
> * reduced latencies (not timeout can influence when the write will happen)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMQ-6831) Broker fails to start complaining about missing/corrupt journal files after upgrading to 5.15.1

2017-10-09 Thread Gary Tully (JIRA) 

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

Gary Tully commented on AMQ-6831:
-

[~masc3d] I had a quick peek at the kahadb.zip but there are no journal files 
in there. Can you check. Also, if possible describe simple steps to reproduce. 
I flipped the bits to enable PreallocationStrategy.ZEROS on a few of the 
recovery unit tests and did not reproduce.

> Broker fails to start complaining about missing/corrupt journal files after 
> upgrading to 5.15.1
> ---
>
> Key: AMQ-6831
> URL: https://issues.apache.org/jira/browse/AMQ-6831
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.15.1
>Reporter: masc
> Attachments: kahadb.zip
>
>
> {code}
> 2017-10-09 12:29:36.802 ERROR 4197 --- [pool-3-thread-1] 
> org.deku.leoz.node.Application   : java.io.IOException: Detected 
> missing/corrupt journal files referenced by:[0:ActiveMQ.DLQ] 3 messages 
> affected.
> java.lang.Error: java.io.IOException: Detected missing/corrupt journal files 
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1148)
>  ~[na:1.8.0_131]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  ~[na:1.8.0_131]
>   at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_131]
> Caused by: java.io.IOException: Detected missing/corrupt journal files 
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.recoverIndex(MessageDatabase.java:965)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase$5.execute(MessageDatabase.java:717)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.disk.page.Transaction.execute(Transaction.java:779)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:714)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219) 
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55) 
> ~[activemq-client-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:232)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> {code}
> Downgrading to 5.15.0 resolves the problem.
> This is an embedded broker setup, using
> {code:none}
> val pa = brokerService.persistenceAdapter as KahaDBPersistenceAdapter
> pa.isCheckForCorruptJournalFiles = true
> pa.isIgnoreMissingJournalfiles = false
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ARTEMIS-1456) createQueue(null, ...) is failing, even though documentation says this is valid call

2017-10-09 Thread JIRA 

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

Jiri Daněk updated ARTEMIS-1456:

External issue URL: 
https://stackoverflow.com/questions/44781032/how-to-create-durable-queue-using-artemis-jms-management-api/46649727

> createQueue(null, ...) is failing, even though documentation says this is 
> valid call
> 
>
> Key: ARTEMIS-1456
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1456
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 2.4.0
>Reporter: Jiri Daněk
>
> Documentation at 
> https://activemq.apache.org/artemis/docs/javadocs/javadoc-latest/org/apache/activemq/artemis/api/core/management/ActiveMQServerControl.html#createQueue-java.lang.String-java.lang.String-java.lang.String-
>  states
> bq. If address is null it will be defaulted to name. 
> I have the following program
> {code}
> public class ManagementServiceImplTest extends ActiveMQTestBase {
>@Test
>public void testCreateDurableQueue() throws Exception {
>   String address = RandomUtil.randomString();
>   Configuration config = 
> createBasicConfig().setJMXManagementEnabled(false);
>   ActiveMQServer server = 
> addServer(ActiveMQServers.newActiveMQServer(config, false));
>   server.start();
>   // invoke attribute and operation on the server
>   CoreMessage message = new CoreMessage(1, 100);
>   ManagementHelper.putOperationInvocation(message, ResourceNames.BROKER, 
> "createQueue", null, address, null, true);
>   Message reply = server.getManagementService().handleMessage(message);
>   System.out.println(reply.toString());
>   Assert.assertTrue(ManagementHelper.hasOperationSucceeded(reply));
>   System.out.println("REZULTZ HERE:");
>   for (Binding binding : 
> server.getPostOffice().getBindingsForAddress(SimpleString.toSimpleString(address)).getBindings())
>  {
>  System.out.println(binding);
>  System.out.println(((LocalQueueBinding) 
> binding).getQueue().isDurable());
>   }
>}
> {code}
> If I run it, I get {{AssertionError}} from 
> {{ManagementHelper.hasOperationSucceeded}}. The cause is the following 
> exception
> {noformat}
> java.lang.reflect.InvocationTargetException
>   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.apache.activemq.artemis.core.server.management.impl.ManagementServiceImpl.invokeOperation(ManagementServiceImpl.java:748)
>   at 
> org.apache.activemq.artemis.core.server.management.impl.ManagementServiceImpl.handleMessage(ManagementServiceImpl.java:391)
>   at 
> org.apache.activemq.artemis.tests.integration.management.ManagementServiceImplTest.testCreateDurableQueue(ManagementServiceImplTest.java:66)
>   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)
>

[jira] [Commented] (ARTEMIS-1452) Journal Configuration Improvements

2017-10-09 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on ARTEMIS-1452:
-

Github user asfgit closed the pull request at:

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


> Journal Configuration Improvements
> --
>
> Key: ARTEMIS-1452
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1452
> Project: ActiveMQ Artemis
>  Issue Type: Improvement
>Affects Versions: 2.3.0
>Reporter: clebert suconic
>Assignee: clebert suconic
> Fix For: 2.4.0
>
>
> When using more advanced systems, that are capable of doing a lot more queued 
> IO, the self optimization of the journal is not really being optimal.
> Besides It would be nice to have some of the configurations more explicit on 
> broker.xml
> And also, we should allow users to disable the TimedBuffering. By simply 
> using 0 at the journal-buffer-timeout.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1452) Journal Configuration Improvements

2017-10-09 Thread ASF subversion and git services (JIRA) 

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

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

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

ARTEMIS-1452 Improvements to IO parameters and options

- it is now possible to disable the TimedBuffer
- this is increasing the default on libaio maxAIO to 4k
- The Auto Tuning on the journal will use asynchronous writes to simulate what 
would happen on faster disks
- If you set datasync=false on the CLI, the system will suggest mapped and 
disable the buffer timeout

This closes #1436

This commit superseeds #1436 since it's now disabling the timed buffer through 
the CLI


> Journal Configuration Improvements
> --
>
> Key: ARTEMIS-1452
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1452
> Project: ActiveMQ Artemis
>  Issue Type: Improvement
>Affects Versions: 2.3.0
>Reporter: clebert suconic
>Assignee: clebert suconic
> Fix For: 2.4.0
>
>
> When using more advanced systems, that are capable of doing a lot more queued 
> IO, the self optimization of the journal is not really being optimal.
> Besides It would be nice to have some of the configurations more explicit on 
> broker.xml
> And also, we should allow users to disable the TimedBuffering. By simply 
> using 0 at the journal-buffer-timeout.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1318) Uses unbuffered MAPPED Journal if no data-sync is required

2017-10-09 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on ARTEMIS-1318:
-

Github user asfgit closed the pull request at:

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


> Uses unbuffered MAPPED Journal if no data-sync is required
> --
>
> Key: ARTEMIS-1318
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1318
> Project: ActiveMQ Artemis
>  Issue Type: Improvement
>Reporter: Francesco Nigro
>Assignee: Francesco Nigro
>
> Disable the TimedBuffer on MAPPED journal if no data-sync in required:
> * reduced footprint (no TimedBuffer)
> * reduced CPU usage (less buffer copy and no TimedBuffer background timer 
> thread)
> * reduced latencies (not timeout can influence when the write will happen)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1455) HQ222142: Error on resetting large message deliver - null: java.lang.NullPointerException

2017-10-09 Thread ASF subversion and git services (JIRA) 

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

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

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

ARTEMIS-1455 Fixing issues on Large Message conversion


> HQ222142: Error on resetting large message deliver - null: 
> java.lang.NullPointerException
> -
>
> Key: ARTEMIS-1455
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1455
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>  Components: AMQP
>Affects Versions: 2.3.0
>Reporter: Dmitrii Tikhomirov
>
> The message
> 
> HQ222142: Error on resetting large message deliver - null: 
> java.lang.NullPointerException
> 
> can be seen in the server log file.
> This issue is a clone of https://issues.jboss.org/browse/HORNETQ-1557



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (AMQ-6826) PostgresqlJDBCAdapter with table prefix errors when executing createSchemaStatements for creating Indexes.

2017-10-09 Thread Timothy Bish (JIRA) 

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

Timothy Bish closed AMQ-6826.
-
Resolution: Not A Problem

Configurable as indicated in comments, no fix needed

> PostgresqlJDBCAdapter with table prefix errors when executing 
> createSchemaStatements for creating Indexes.
> --
>
> Key: AMQ-6826
> URL: https://issues.apache.org/jira/browse/AMQ-6826
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker
> Environment: ALL
>Reporter: chandra shekhar pandey
>Priority: Minor
>
> - When using PostgresqlJDBCAdapter to auto create the tables and a table 
> prefix statement is also used the create schema statements fail because 
> PostgresqlJDBCAdapter doesn't add   the table prefix to Index:
> {code}
> activemq.xml snippet:
>  class="org.apache.activemq.store.jdbc.adapter.PostgresqlJDBCAdapter" />
>   
>   
>  adapter="#postgresPersistenceAdapter" dataSource="#postgres-ds" 
> lockKeepAlivePeriod="5000" >
> 
> 
> 
> 
> 
> 
> 
> 
> {code}
> - amq log error
> {code}
> 2017-09-28 10:06:40,199 | WARN  | AMQ-1-thread-1   | DefaultJDBCAdapter   
> | .jdbc.adapter.DefaultJDBCAdapter  117 | 137 - 
> org.apache.activemq.activemq-osgi - 5.11.0.redhat-621169 | Could not create 
> JDBC tables; they could already exist. Failure was: ALTER TABLE 
> LOCAL_ACTIVEMQ_ACKS DROP CONSTRAINT "activemq_acks_pkey" Message: ERROR: 
> constraint "activemq_acks_pkey" of relation "local_activemq_acks" does not 
> exist SQLState: 42704 Vendor code: 0
> 2017-09-28 10:06:40,200 | WARN  | AMQ-1-thread-1   | JDBCPersistenceAdapter   
> | tore.jdbc.JDBCPersistenceAdapter  601 | 137 - 
> org.apache.activemq.activemq-osgi - 5.11.0.redhat-621169 | Failure details: 
> ERROR: constraint "activemq_acks_pkey" of relation "local_activemq_acks" does 
> not exist
> org.postgresql.util.PSQLException: ERROR: constraint "activemq_acks_pkey" of 
> relation "local_activemq_acks" does not exist
> at 
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2477)[172:org.postgresql.jdbc42:42.1.4]
> at 
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2190)[172:org.postgresql.jdbc42:42.1.4]
> at 
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:300)[172:org.postgresql.jdbc42:42.1.4]
> at 
> org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:428)[172:org.postgresql.jdbc42:42.1.4]
> at 
> org.postgresql.jdbc.PgStatement.execute(PgStatement.java:354)[172:org.postgresql.jdbc42:42.1.4]
> at 
> org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:301)[172:org.postgresql.jdbc42:42.1.4]
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1455) HQ222142: Error on resetting large message deliver - null: java.lang.NullPointerException

2017-10-09 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on ARTEMIS-1455:
-

Github user asfgit closed the pull request at:

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


> HQ222142: Error on resetting large message deliver - null: 
> java.lang.NullPointerException
> -
>
> Key: ARTEMIS-1455
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1455
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>  Components: AMQP
>Affects Versions: 2.3.0
>Reporter: Dmitrii Tikhomirov
>
> The message
> 
> HQ222142: Error on resetting large message deliver - null: 
> java.lang.NullPointerException
> 
> can be seen in the server log file.
> This issue is a clone of https://issues.jboss.org/browse/HORNETQ-1557



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1444) Large messages are not working with OpenWire protocol

2017-10-09 Thread ASF subversion and git services (JIRA) 

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

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

Commit 988c91557da7124fed1a30fcd4c1c708aac6b8d2 in activemq-artemis's branch 
refs/heads/master from [~martyntaylor]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=988c915 ]

ARTEMIS-1444 Support Messages > JournalBufferSize in all Protocols


> Large messages are not working with OpenWire protocol
> -
>
> Key: ARTEMIS-1444
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1444
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Affects Versions: 2.3.0
>Reporter: Martyn Taylor
>
> Sending a message of 4mb causes the broker to throw an exception: 
> 11:32:39,593 ERROR 
> [org.apache.activemq.artemis.core.journal.impl.JournalImpl] 
> appendAddRecord::java.lang.IllegalArgumentException: Record is too large to 
> store 11360234: java.lang.IllegalArgumentException: Record is too large to 
> store 11360234
> at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.switchFileIfNecessary(JournalImpl.java:2872)
>  [artemis-journal-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.appendRecord(JournalImpl.java:2597)
>  [artemis-journal-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.access$200(JournalImpl.java:88)
>  [artemis-journal-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl$1.run(JournalImpl.java:744)
>  [artemis-journal-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:42)
>  [artemis-commons-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:31)
>  [artemis-commons-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.utils.actors.ProcessorBase$ExecutorTask.run(ProcessorBase.java:53)
>  [artemis-commons-2.2.0.jar:2.2.0]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>  [rt.jar:1.8.0_141]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>  [rt.jar:1.8.0_141]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_141]
>  
> 11:32:39,594 WARN  [org.apache.activemq.artemis.core.server] AMQ222057: It 
> was not possible to add references due to an IO error code 6 message = null
> 11:32:39,595 ERROR 
> [org.apache.activemq.artemis.core.journal.impl.JournalImpl] 
> appendUpdateRecord:java.lang.NullPointerException: 
> java.lang.NullPointerException
> at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl$2.run(JournalImpl.java:809)
>  [artemis-journal-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:42)
>  [artemis-commons-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:31)
>  [artemis-commons-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.utils.actors.ProcessorBase$ExecutorTask.run(ProcessorBase.java:53)
>  [artemis-commons-2.2.0.jar:2.2.0]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>  [rt.jar:1.8.0_141]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>  [rt.jar:1.8.0_141]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_141]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1455) HQ222142: Error on resetting large message deliver - null: java.lang.NullPointerException

2017-10-09 Thread ASF subversion and git services (JIRA) 

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

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

Commit 53efdbab49eea8755571b2e76ae3f8bf62d364be in activemq-artemis's branch 
refs/heads/master from [~ch...@me.com]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=53efdba ]

ARTEMIS-1455 HQ222142: Error on resetting large message deliver - null: 
java.lang.NullPointerException


> HQ222142: Error on resetting large message deliver - null: 
> java.lang.NullPointerException
> -
>
> Key: ARTEMIS-1455
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1455
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>  Components: AMQP
>Affects Versions: 2.3.0
>Reporter: Dmitrii Tikhomirov
>
> The message
> 
> HQ222142: Error on resetting large message deliver - null: 
> java.lang.NullPointerException
> 
> can be seen in the server log file.
> This issue is a clone of https://issues.jboss.org/browse/HORNETQ-1557



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1444) Large messages are not working with OpenWire protocol

2017-10-09 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on ARTEMIS-1444:
-

Github user asfgit closed the pull request at:

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


> Large messages are not working with OpenWire protocol
> -
>
> Key: ARTEMIS-1444
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1444
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Affects Versions: 2.3.0
>Reporter: Martyn Taylor
>
> Sending a message of 4mb causes the broker to throw an exception: 
> 11:32:39,593 ERROR 
> [org.apache.activemq.artemis.core.journal.impl.JournalImpl] 
> appendAddRecord::java.lang.IllegalArgumentException: Record is too large to 
> store 11360234: java.lang.IllegalArgumentException: Record is too large to 
> store 11360234
> at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.switchFileIfNecessary(JournalImpl.java:2872)
>  [artemis-journal-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.appendRecord(JournalImpl.java:2597)
>  [artemis-journal-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.access$200(JournalImpl.java:88)
>  [artemis-journal-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl$1.run(JournalImpl.java:744)
>  [artemis-journal-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:42)
>  [artemis-commons-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:31)
>  [artemis-commons-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.utils.actors.ProcessorBase$ExecutorTask.run(ProcessorBase.java:53)
>  [artemis-commons-2.2.0.jar:2.2.0]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>  [rt.jar:1.8.0_141]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>  [rt.jar:1.8.0_141]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_141]
>  
> 11:32:39,594 WARN  [org.apache.activemq.artemis.core.server] AMQ222057: It 
> was not possible to add references due to an IO error code 6 message = null
> 11:32:39,595 ERROR 
> [org.apache.activemq.artemis.core.journal.impl.JournalImpl] 
> appendUpdateRecord:java.lang.NullPointerException: 
> java.lang.NullPointerException
> at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl$2.run(JournalImpl.java:809)
>  [artemis-journal-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:42)
>  [artemis-commons-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:31)
>  [artemis-commons-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.utils.actors.ProcessorBase$ExecutorTask.run(ProcessorBase.java:53)
>  [artemis-commons-2.2.0.jar:2.2.0]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>  [rt.jar:1.8.0_141]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>  [rt.jar:1.8.0_141]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_141]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1444) Large messages are not working with OpenWire protocol

2017-10-09 Thread ASF subversion and git services (JIRA) 

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

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

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

ARTEMIS-1444 Fixing byte buffer conversion

I'm also using a lower size on message, to speed up the new test.

(100M may be a lot on some CIs)


> Large messages are not working with OpenWire protocol
> -
>
> Key: ARTEMIS-1444
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1444
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Affects Versions: 2.3.0
>Reporter: Martyn Taylor
>
> Sending a message of 4mb causes the broker to throw an exception: 
> 11:32:39,593 ERROR 
> [org.apache.activemq.artemis.core.journal.impl.JournalImpl] 
> appendAddRecord::java.lang.IllegalArgumentException: Record is too large to 
> store 11360234: java.lang.IllegalArgumentException: Record is too large to 
> store 11360234
> at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.switchFileIfNecessary(JournalImpl.java:2872)
>  [artemis-journal-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.appendRecord(JournalImpl.java:2597)
>  [artemis-journal-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.access$200(JournalImpl.java:88)
>  [artemis-journal-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl$1.run(JournalImpl.java:744)
>  [artemis-journal-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:42)
>  [artemis-commons-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:31)
>  [artemis-commons-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.utils.actors.ProcessorBase$ExecutorTask.run(ProcessorBase.java:53)
>  [artemis-commons-2.2.0.jar:2.2.0]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>  [rt.jar:1.8.0_141]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>  [rt.jar:1.8.0_141]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_141]
>  
> 11:32:39,594 WARN  [org.apache.activemq.artemis.core.server] AMQ222057: It 
> was not possible to add references due to an IO error code 6 message = null
> 11:32:39,595 ERROR 
> [org.apache.activemq.artemis.core.journal.impl.JournalImpl] 
> appendUpdateRecord:java.lang.NullPointerException: 
> java.lang.NullPointerException
> at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl$2.run(JournalImpl.java:809)
>  [artemis-journal-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:42)
>  [artemis-commons-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:31)
>  [artemis-commons-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.utils.actors.ProcessorBase$ExecutorTask.run(ProcessorBase.java:53)
>  [artemis-commons-2.2.0.jar:2.2.0]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>  [rt.jar:1.8.0_141]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>  [rt.jar:1.8.0_141]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_141]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1444) Large messages are not working with OpenWire protocol

2017-10-09 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on ARTEMIS-1444:
-

Github user clebertsuconic commented on the issue:

https://github.com/apache/activemq-artemis/pull/1574
  
@mtaylor I am merging with my commit in top of yours.. feel free to add a 
new commit if you find a better way.


> Large messages are not working with OpenWire protocol
> -
>
> Key: ARTEMIS-1444
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1444
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Affects Versions: 2.3.0
>Reporter: Martyn Taylor
>
> Sending a message of 4mb causes the broker to throw an exception: 
> 11:32:39,593 ERROR 
> [org.apache.activemq.artemis.core.journal.impl.JournalImpl] 
> appendAddRecord::java.lang.IllegalArgumentException: Record is too large to 
> store 11360234: java.lang.IllegalArgumentException: Record is too large to 
> store 11360234
> at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.switchFileIfNecessary(JournalImpl.java:2872)
>  [artemis-journal-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.appendRecord(JournalImpl.java:2597)
>  [artemis-journal-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.access$200(JournalImpl.java:88)
>  [artemis-journal-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl$1.run(JournalImpl.java:744)
>  [artemis-journal-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:42)
>  [artemis-commons-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:31)
>  [artemis-commons-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.utils.actors.ProcessorBase$ExecutorTask.run(ProcessorBase.java:53)
>  [artemis-commons-2.2.0.jar:2.2.0]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>  [rt.jar:1.8.0_141]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>  [rt.jar:1.8.0_141]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_141]
>  
> 11:32:39,594 WARN  [org.apache.activemq.artemis.core.server] AMQ222057: It 
> was not possible to add references due to an IO error code 6 message = null
> 11:32:39,595 ERROR 
> [org.apache.activemq.artemis.core.journal.impl.JournalImpl] 
> appendUpdateRecord:java.lang.NullPointerException: 
> java.lang.NullPointerException
> at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl$2.run(JournalImpl.java:809)
>  [artemis-journal-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:42)
>  [artemis-commons-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:31)
>  [artemis-commons-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.utils.actors.ProcessorBase$ExecutorTask.run(ProcessorBase.java:53)
>  [artemis-commons-2.2.0.jar:2.2.0]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>  [rt.jar:1.8.0_141]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>  [rt.jar:1.8.0_141]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_141]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1444) Large messages are not working with OpenWire protocol

2017-10-09 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on ARTEMIS-1444:
-

Github user clebertsuconic commented on the issue:

https://github.com/apache/activemq-artemis/pull/1574
  
@mtaylor did you test it?

The test you added is broken... I had to fix it with this:

```java

   private LargeServerMessage messageToLargeMessage(Message message) throws 
Exception {
  ICoreMessage coreMessage = message.toCore();
  LargeServerMessage lsm = 
getStorageManager().createLargeMessage(storageManager.generateID(), 
coreMessage);

  ActiveMQBuffer buffer = coreMessage.getReadOnlyBodyBuffer();
  byte[] body = new byte[buffer.readableBytes()];
  buffer.readBytes(body);
  lsm.addBytes(body);
  lsm.releaseResources();
  lsm.putLongProperty(Message.HDR_LARGE_BODY_SIZE, body.length);
  return lsm;
   }
```


> Large messages are not working with OpenWire protocol
> -
>
> Key: ARTEMIS-1444
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1444
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Affects Versions: 2.3.0
>Reporter: Martyn Taylor
>
> Sending a message of 4mb causes the broker to throw an exception: 
> 11:32:39,593 ERROR 
> [org.apache.activemq.artemis.core.journal.impl.JournalImpl] 
> appendAddRecord::java.lang.IllegalArgumentException: Record is too large to 
> store 11360234: java.lang.IllegalArgumentException: Record is too large to 
> store 11360234
> at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.switchFileIfNecessary(JournalImpl.java:2872)
>  [artemis-journal-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.appendRecord(JournalImpl.java:2597)
>  [artemis-journal-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.access$200(JournalImpl.java:88)
>  [artemis-journal-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl$1.run(JournalImpl.java:744)
>  [artemis-journal-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:42)
>  [artemis-commons-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:31)
>  [artemis-commons-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.utils.actors.ProcessorBase$ExecutorTask.run(ProcessorBase.java:53)
>  [artemis-commons-2.2.0.jar:2.2.0]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>  [rt.jar:1.8.0_141]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>  [rt.jar:1.8.0_141]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_141]
>  
> 11:32:39,594 WARN  [org.apache.activemq.artemis.core.server] AMQ222057: It 
> was not possible to add references due to an IO error code 6 message = null
> 11:32:39,595 ERROR 
> [org.apache.activemq.artemis.core.journal.impl.JournalImpl] 
> appendUpdateRecord:java.lang.NullPointerException: 
> java.lang.NullPointerException
> at 
> org.apache.activemq.artemis.core.journal.impl.JournalImpl$2.run(JournalImpl.java:809)
>  [artemis-journal-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:42)
>  [artemis-commons-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:31)
>  [artemis-commons-2.2.0.jar:2.2.0]
> at 
> org.apache.activemq.artemis.utils.actors.ProcessorBase$ExecutorTask.run(ProcessorBase.java:53)
>  [artemis-commons-2.2.0.jar:2.2.0]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>  [rt.jar:1.8.0_141]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>  [rt.jar:1.8.0_141]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_141]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (AMQ-6831) Broker fails to start complaining about missing/corrupt journal files after upgrading to 5.15.1

2017-10-09 Thread masc (JIRA) 

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

masc edited comment on AMQ-6831 at 10/9/17 4:45 PM:


yes, that would be possible, as it's my local dev db, it shouldn't contain 
anything sensitive.

I also found that this issue is related to the preallocation kahadb settings:
{code}
pa.preallocationScope = 
Journal.PreallocationScope.ENTIRE_JOURNAL_ASYNC.name
pa.preallocationStrategy = Journal.PreallocationStrategy.ZEROS.name
{code}

which I enabled for performance reasons.

Disabling preallocation will yield both
{code}
2017-10-09 18:34:57.512  WARN 10617 --- [pool-3-thread-1] 
o.a.a.store.kahadb.MessageDatabase   : Cannot recover message audit

java.io.IOException: Invalid location size: 1:28, size: 0
at 
org.apache.activemq.store.kahadb.disk.journal.DataFileAccessor.readRecord(DataFileAccessor.java:88)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.disk.journal.Journal.read(Journal.java:936) 
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:1151)
 [activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.recoverProducerAudit(MessageDatabase.java:784)
 [activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:674)
 [activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473) 
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493) 
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
 [activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219) 
[activemq-kahadb-store-5.15.1.jar:5.15.1]
{code}
and subsequently
{code}
2017-10-09 18:34:57.513  WARN 10617 --- [pool-3-thread-1] 
o.a.a.store.kahadb.MessageDatabase   : Cannot recover ackMessageFileMap

java.io.IOException: Invalid location size: 1:431, size: 0
at 
org.apache.activemq.store.kahadb.disk.journal.DataFileAccessor.readRecord(DataFileAccessor.java:88)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.disk.journal.Journal.read(Journal.java:936) 
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:1151)
 [activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.recoverAckMessageFileMap(MessageDatabase.java:805)
 [activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:675)
 [activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473) 
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493) 
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
 [activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219) 
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55) 
[activemq-client-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:232)
 [activemq-kahadb-store-5.15.1.jar:5.15.1]
{code}

but the broker will at least start.



was (Author: masc3d):
yes, that would be possible, as it's my local dev db, it shouldn't contain 
anything sensitive.

I also found that this issue is related to the preallocation kahadb settings:
{code}
pa.preallocationScope = 
Journal.PreallocationScope.ENTIRE_JOURNAL_ASYNC.name
pa.preallocationStrategy = Journal.PreallocationStrategy.ZEROS.name
{code}

which I enabled for performance reasons.

Disabling preallocation will yield both
{code}
java.io.IOException: Invalid location size: 1:28, size: 0
at 
org.apache.activemq.store.kahadb.disk.journal.DataFileAccessor.readRecord(DataFileAccessor.java:88)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.disk.journal.Journal.read(Journal.java:936) 
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:1151)
 [activemq-kahadb-store-5.15.1.jar:5.15.1]
at

[jira] [Comment Edited] (AMQ-6831) Broker fails to start complaining about missing/corrupt journal files after upgrading to 5.15.1

2017-10-09 Thread masc (JIRA) 

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

masc edited comment on AMQ-6831 at 10/9/17 4:42 PM:


yes, that would be possible, as it's my local dev db, it shouldn't contain 
anything sensitive.

I also found that this issue is related to the preallocation kahadb settings:
{code}
pa.preallocationScope = 
Journal.PreallocationScope.ENTIRE_JOURNAL_ASYNC.name
pa.preallocationStrategy = Journal.PreallocationStrategy.ZEROS.name
{code}

which I enabled for performance reasons.

Disabling preallocation will yield both
{code}
java.io.IOException: Invalid location size: 1:28, size: 0
at 
org.apache.activemq.store.kahadb.disk.journal.DataFileAccessor.readRecord(DataFileAccessor.java:88)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.disk.journal.Journal.read(Journal.java:936) 
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:1151)
 [activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.recoverProducerAudit(MessageDatabase.java:784)
 [activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:674)
 [activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473) 
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493) 
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
 [activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219) 
[activemq-kahadb-store-5.15.1.jar:5.15.1]
{code}
and subsequently
{code}
2017-10-09 18:34:57.513  WARN 10617 --- [pool-3-thread-1] 
o.a.a.store.kahadb.MessageDatabase   : Cannot recover ackMessageFileMap

java.io.IOException: Invalid location size: 1:431, size: 0
at 
org.apache.activemq.store.kahadb.disk.journal.DataFileAccessor.readRecord(DataFileAccessor.java:88)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.disk.journal.Journal.read(Journal.java:936) 
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:1151)
 [activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.recoverAckMessageFileMap(MessageDatabase.java:805)
 [activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:675)
 [activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473) 
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493) 
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
 [activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219) 
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55) 
[activemq-client-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:232)
 [activemq-kahadb-store-5.15.1.jar:5.15.1]
{code}

but the broker will at least start.



was (Author: masc3d):
yes, that would be possible, as it's my local dev db, it shouldn't contain 
anything sensitive.

I also found that this issue is related to the preallocation kahadb settings:
{code}
pa.preallocationScope = 
Journal.PreallocationScope.ENTIRE_JOURNAL_ASYNC.name
pa.preallocationStrategy = Journal.PreallocationStrategy.ZEROS.name
{code}

which I enabled for performance reasons.

Disabling preallocation will both
{code}
java.io.IOException: Invalid location size: 1:28, size: 0
at 
org.apache.activemq.store.kahadb.disk.journal.DataFileAccessor.readRecord(DataFileAccessor.java:88)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.disk.journal.Journal.read(Journal.java:936) 
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:1151)
 [activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.recoverProducerAudit(MessageDatabase.java:784)
 [activemq-kahadb-store-5.15.1.jar:5.15.1]
at

[jira] [Commented] (AMQ-6831) Broker fails to start complaining about missing/corrupt journal files after upgrading to 5.15.1

2017-10-09 Thread masc (JIRA) 

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

masc commented on AMQ-6831:
---

yes, that would be possible, as it's my local dev db, it shouldn't contain 
anything sensitive.

I also found that this issue is related to the preallocation kahadb settings:
{code}
pa.preallocationScope = 
Journal.PreallocationScope.ENTIRE_JOURNAL_ASYNC.name
pa.preallocationStrategy = Journal.PreallocationStrategy.ZEROS.name
{code}

which I enabled for performance reasons.

Disabling preallocation will both
{code}
java.io.IOException: Invalid location size: 1:28, size: 0
at 
org.apache.activemq.store.kahadb.disk.journal.DataFileAccessor.readRecord(DataFileAccessor.java:88)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.disk.journal.Journal.read(Journal.java:936) 
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:1151)
 [activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.recoverProducerAudit(MessageDatabase.java:784)
 [activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:674)
 [activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473) 
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493) 
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
 [activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219) 
[activemq-kahadb-store-5.15.1.jar:5.15.1]
{code}
and subsequently
{code}
2017-10-09 18:34:57.513  WARN 10617 --- [pool-3-thread-1] 
o.a.a.store.kahadb.MessageDatabase   : Cannot recover ackMessageFileMap

java.io.IOException: Invalid location size: 1:431, size: 0
at 
org.apache.activemq.store.kahadb.disk.journal.DataFileAccessor.readRecord(DataFileAccessor.java:88)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.disk.journal.Journal.read(Journal.java:936) 
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:1151)
 [activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.recoverAckMessageFileMap(MessageDatabase.java:805)
 [activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:675)
 [activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473) 
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493) 
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
 [activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219) 
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55) 
[activemq-client-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:232)
 [activemq-kahadb-store-5.15.1.jar:5.15.1]
{code}

but the broker will at least start.


> Broker fails to start complaining about missing/corrupt journal files after 
> upgrading to 5.15.1
> ---
>
> Key: AMQ-6831
> URL: https://issues.apache.org/jira/browse/AMQ-6831
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.15.1
>Reporter: masc
>
> {code}
> 2017-10-09 12:29:36.802 ERROR 4197 --- [pool-3-thread-1] 
> org.deku.leoz.node.Application   : java.io.IOException: Detected 
> missing/corrupt journal files referenced by:[0:ActiveMQ.DLQ] 3 messages 
> affected.
> java.lang.Error: java.io.IOException: Detected missing/corrupt journal files 
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1148)
>  ~[na:1.8.0_131]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  ~[na:1.8.0_131]
>   at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_131]
> Caused by: java.io.IOException: Detected missing/corrupt journal files 
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
>   at 
>

[jira] [Created] (ARTEMIS-1456) createQueue(null, ...) is failing, even though documentation says this is valid call

2017-10-09 Thread JIRA 
Jiri Daněk created ARTEMIS-1456:
---

 Summary: createQueue(null, ...) is failing, even though 
documentation says this is valid call
 Key: ARTEMIS-1456
 URL: https://issues.apache.org/jira/browse/ARTEMIS-1456
 Project: ActiveMQ Artemis
  Issue Type: Bug
  Components: Broker
Affects Versions: 2.4.0
Reporter: Jiri Daněk


Documentation at 
https://activemq.apache.org/artemis/docs/javadocs/javadoc-latest/org/apache/activemq/artemis/api/core/management/ActiveMQServerControl.html#createQueue-java.lang.String-java.lang.String-java.lang.String-
 states

bq. If address is null it will be defaulted to name. 

I have the following program

{code}
public class ManagementServiceImplTest extends ActiveMQTestBase {

   @Test
   public void testCreateDurableQueue() throws Exception {
  String address = RandomUtil.randomString();
  Configuration config = createBasicConfig().setJMXManagementEnabled(false);
  ActiveMQServer server = 
addServer(ActiveMQServers.newActiveMQServer(config, false));
  server.start();

  // invoke attribute and operation on the server
  CoreMessage message = new CoreMessage(1, 100);
  ManagementHelper.putOperationInvocation(message, ResourceNames.BROKER, 
"createQueue", null, address, null, true);

  Message reply = server.getManagementService().handleMessage(message);

  System.out.println(reply.toString());

  Assert.assertTrue(ManagementHelper.hasOperationSucceeded(reply));

  System.out.println("REZULTZ HERE:");
  for (Binding binding : 
server.getPostOffice().getBindingsForAddress(SimpleString.toSimpleString(address)).getBindings())
 {
 System.out.println(binding);
 System.out.println(((LocalQueueBinding) 
binding).getQueue().isDurable());
  }
   }
{code}

If I run it, I get {{AssertionError}} from 
{{ManagementHelper.hasOperationSucceeded}}. The cause is the following exception

{noformat}
java.lang.reflect.InvocationTargetException
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.apache.activemq.artemis.core.server.management.impl.ManagementServiceImpl.invokeOperation(ManagementServiceImpl.java:748)
at 
org.apache.activemq.artemis.core.server.management.impl.ManagementServiceImpl.handleMessage(ManagementServiceImpl.java:391)
at 
org.apache.activemq.artemis.tests.integration.management.ManagementServiceImplTest.testCreateDurableQueue(ManagementServiceImplTest.java:66)
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.runner.JUnitCore.run(JUnitCore.java:160)
at

[jira] [Commented] (ARTEMIS-1455) HQ222142: Error on resetting large message deliver - null: java.lang.NullPointerException

2017-10-09 Thread Dmitrii Tikhomirov (JIRA) 

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

Dmitrii Tikhomirov commented on ARTEMIS-1455:
-

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

> HQ222142: Error on resetting large message deliver - null: 
> java.lang.NullPointerException
> -
>
> Key: ARTEMIS-1455
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1455
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>  Components: AMQP
>Affects Versions: 2.3.0
>Reporter: Dmitrii Tikhomirov
>
> The message
> 
> HQ222142: Error on resetting large message deliver - null: 
> java.lang.NullPointerException
> 
> can be seen in the server log file.
> This issue is a clone of https://issues.jboss.org/browse/HORNETQ-1557



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMQ-6831) Broker fails to start complaining about missing/corrupt journal files after upgrading to 5.15.1

2017-10-09 Thread Christopher L. Shannon (JIRA) 

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

Christopher L. Shannon commented on AMQ-6831:
-

Yeah I just find it interesting that the description says downgrading to 5.15.0 
fixes the issue.  

[~masc3d], are you able to upload a small KahaDB store that reproduces the 
issue?

> Broker fails to start complaining about missing/corrupt journal files after 
> upgrading to 5.15.1
> ---
>
> Key: AMQ-6831
> URL: https://issues.apache.org/jira/browse/AMQ-6831
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.15.1
>Reporter: masc
>
> {code}
> 2017-10-09 12:29:36.802 ERROR 4197 --- [pool-3-thread-1] 
> org.deku.leoz.node.Application   : java.io.IOException: Detected 
> missing/corrupt journal files referenced by:[0:ActiveMQ.DLQ] 3 messages 
> affected.
> java.lang.Error: java.io.IOException: Detected missing/corrupt journal files 
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1148)
>  ~[na:1.8.0_131]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  ~[na:1.8.0_131]
>   at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_131]
> Caused by: java.io.IOException: Detected missing/corrupt journal files 
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.recoverIndex(MessageDatabase.java:965)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase$5.execute(MessageDatabase.java:717)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.disk.page.Transaction.execute(Transaction.java:779)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:714)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219) 
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55) 
> ~[activemq-client-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:232)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> {code}
> Downgrading to 5.15.0 resolves the problem.
> This is an embedded broker setup, using
> {code:none}
> val pa = brokerService.persistenceAdapter as KahaDBPersistenceAdapter
> pa.isCheckForCorruptJournalFiles = true
> pa.isIgnoreMissingJournalfiles = false
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1454) Support SASL in outgoing AMQP connections

2017-10-09 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on ARTEMIS-1454:
-

Github user asfgit closed the pull request at:

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


> Support SASL in outgoing AMQP connections
> -
>
> Key: ARTEMIS-1454
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1454
> Project: ActiveMQ Artemis
>  Issue Type: Improvement
>  Components: AMQP
>Reporter: Rob Godfrey
>Priority: Minor
>
> ARTEMIS-814 introduced the ability for Artemis to make outgoing AMQP 
> connections, however it did not support the use of SASL negotiation to secure 
> them.
> In order to secure the outgoing connection, and provide identity information 
> to the remote peer that Artemis is connecting to, we need to introduce the 
> ability for the outgoing connection to negotiate a SASL layer



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1454) Support SASL in outgoing AMQP connections

2017-10-09 Thread ASF subversion and git services (JIRA) 

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

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

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

ARTEMIS-1454: Support SASL in outgoing AMQP

Update ProtonHandler to allow for both client and server side SASL
and other related changes to allow for setting of client side mechanism


> Support SASL in outgoing AMQP connections
> -
>
> Key: ARTEMIS-1454
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1454
> Project: ActiveMQ Artemis
>  Issue Type: Improvement
>  Components: AMQP
>Reporter: Rob Godfrey
>Priority: Minor
>
> ARTEMIS-814 introduced the ability for Artemis to make outgoing AMQP 
> connections, however it did not support the use of SASL negotiation to secure 
> them.
> In order to secure the outgoing connection, and provide identity information 
> to the remote peer that Artemis is connecting to, we need to introduce the 
> ability for the outgoing connection to negotiate a SASL layer



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMQ-6831) Broker fails to start complaining about missing/corrupt journal files after upgrading to 5.15.1

2017-10-09 Thread Gary Tully (JIRA) 

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

Gary Tully commented on AMQ-6831:
-

[~cshannon] I hope not. I would need to check the journal files to verify the 
corrupt locations. A sanity check to see if a current snapshot has the same 
determination may help narrow this down.

The logs should indicate the journal locations in question? How do we know 
there is no corruption present at the moment?

> Broker fails to start complaining about missing/corrupt journal files after 
> upgrading to 5.15.1
> ---
>
> Key: AMQ-6831
> URL: https://issues.apache.org/jira/browse/AMQ-6831
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.15.1
>Reporter: masc
>
> {code}
> 2017-10-09 12:29:36.802 ERROR 4197 --- [pool-3-thread-1] 
> org.deku.leoz.node.Application   : java.io.IOException: Detected 
> missing/corrupt journal files referenced by:[0:ActiveMQ.DLQ] 3 messages 
> affected.
> java.lang.Error: java.io.IOException: Detected missing/corrupt journal files 
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1148)
>  ~[na:1.8.0_131]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  ~[na:1.8.0_131]
>   at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_131]
> Caused by: java.io.IOException: Detected missing/corrupt journal files 
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.recoverIndex(MessageDatabase.java:965)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase$5.execute(MessageDatabase.java:717)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.disk.page.Transaction.execute(Transaction.java:779)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:714)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219) 
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55) 
> ~[activemq-client-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:232)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> {code}
> Downgrading to 5.15.0 resolves the problem.
> This is an embedded broker setup, using
> {code:none}
> val pa = brokerService.persistenceAdapter as KahaDBPersistenceAdapter
> pa.isCheckForCorruptJournalFiles = true
> pa.isIgnoreMissingJournalfiles = false
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMQ-6831) Broker fails to start complaining about missing/corrupt journal files after upgrading to 5.15.1

2017-10-09 Thread Christopher L. Shannon (JIRA) 

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

Christopher L. Shannon commented on AMQ-6831:
-

[~gtully] - Do you think this issue is related to AMQ-6771 ?

> Broker fails to start complaining about missing/corrupt journal files after 
> upgrading to 5.15.1
> ---
>
> Key: AMQ-6831
> URL: https://issues.apache.org/jira/browse/AMQ-6831
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.15.1
>Reporter: masc
>
> {code}
> 2017-10-09 12:29:36.802 ERROR 4197 --- [pool-3-thread-1] 
> org.deku.leoz.node.Application   : java.io.IOException: Detected 
> missing/corrupt journal files referenced by:[0:ActiveMQ.DLQ] 3 messages 
> affected.
> java.lang.Error: java.io.IOException: Detected missing/corrupt journal files 
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1148)
>  ~[na:1.8.0_131]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  ~[na:1.8.0_131]
>   at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_131]
> Caused by: java.io.IOException: Detected missing/corrupt journal files 
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.recoverIndex(MessageDatabase.java:965)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase$5.execute(MessageDatabase.java:717)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.disk.page.Transaction.execute(Transaction.java:779)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:714)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219) 
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55) 
> ~[activemq-client-5.15.1.jar:5.15.1]
>   at 
> org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:232)
>  ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> {code}
> Downgrading to 5.15.0 resolves the problem.
> This is an embedded broker setup, using
> {code:none}
> val pa = brokerService.persistenceAdapter as KahaDBPersistenceAdapter
> pa.isCheckForCorruptJournalFiles = true
> pa.isIgnoreMissingJournalfiles = false
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMQ-6831) Broker fails to start complaining about missing/corrupt journal files after upgrading to 5.15.1

2017-10-09 Thread masc (JIRA) 

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

masc updated AMQ-6831:
--
Description: 
{code}
2017-10-09 12:29:36.802 ERROR 4197 --- [pool-3-thread-1] 
org.deku.leoz.node.Application   : java.io.IOException: Detected 
missing/corrupt journal files referenced by:[0:ActiveMQ.DLQ] 3 messages 
affected.

java.lang.Error: java.io.IOException: Detected missing/corrupt journal files 
referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1148) 
~[na:1.8.0_131]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
~[na:1.8.0_131]
at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_131]
Caused by: java.io.IOException: Detected missing/corrupt journal files 
referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
at 
org.apache.activemq.store.kahadb.MessageDatabase.recoverIndex(MessageDatabase.java:965)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase$5.execute(MessageDatabase.java:717)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.disk.page.Transaction.execute(Transaction.java:779)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:714)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473) 
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493) 
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219) 
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55) 
~[activemq-client-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:232)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
{code}

Downgrading to 5.15.0 resolves the problem.
This is an embedded broker setup, using

{code:none}
val pa = brokerService.persistenceAdapter as KahaDBPersistenceAdapter
pa.isCheckForCorruptJournalFiles = true
pa.isIgnoreMissingJournalfiles = false
{code}

  was:
{code}
2017-10-09 12:29:36.802 ERROR 4197 --- [pool-3-thread-1] 
org.deku.leoz.node.Application   : java.io.IOException: Detected 
missing/corrupt journal files referenced by:[0:ActiveMQ.DLQ] 3 messages 
affected.

java.lang.Error: java.io.IOException: Detected missing/corrupt journal files 
referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1148) 
~[na:1.8.0_131]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
~[na:1.8.0_131]
at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_131]
Caused by: java.io.IOException: Detected missing/corrupt journal files 
referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
at 
org.apache.activemq.store.kahadb.MessageDatabase.recoverIndex(MessageDatabase.java:965)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase$5.execute(MessageDatabase.java:717)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.disk.page.Transaction.execute(Transaction.java:779)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:714)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473) 
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493) 
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219) 
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55) 
~[activemq-client-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:232)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
{code}

Downgrading to 5.15.0 resolves the problem.
This is an embedded broker setup, using

{code:kotlin}
val pa = brokerService.persistenceAdapter as KahaDBPersistenceAdapter
pa.isCheckForCorruptJournalFiles =

[jira] [Updated] (AMQ-6831) Broker fails to start complaining about missing/corrupt journal files after upgrading to 5.15.1

2017-10-09 Thread masc (JIRA) 

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

masc updated AMQ-6831:
--
Description: 
{code}
2017-10-09 12:29:36.802 ERROR 4197 --- [pool-3-thread-1] 
org.deku.leoz.node.Application   : java.io.IOException: Detected 
missing/corrupt journal files referenced by:[0:ActiveMQ.DLQ] 3 messages 
affected.

java.lang.Error: java.io.IOException: Detected missing/corrupt journal files 
referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1148) 
~[na:1.8.0_131]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
~[na:1.8.0_131]
at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_131]
Caused by: java.io.IOException: Detected missing/corrupt journal files 
referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
at 
org.apache.activemq.store.kahadb.MessageDatabase.recoverIndex(MessageDatabase.java:965)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase$5.execute(MessageDatabase.java:717)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.disk.page.Transaction.execute(Transaction.java:779)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:714)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473) 
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493) 
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219) 
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55) 
~[activemq-client-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:232)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
{code}

Downgrading to 5.15.0 resolves the problem.
This is an embedded broker setup, using

{code:kotlin}
val pa = brokerService.persistenceAdapter as KahaDBPersistenceAdapter
pa.isCheckForCorruptJournalFiles = true
pa.isIgnoreMissingJournalfiles = false
{code}

  was:
```2017-10-09 12:29:36.802 ERROR 4197 --- [pool-3-thread-1] 
org.deku.leoz.node.Application   : java.io.IOException: Detected 
missing/corrupt journal files referenced by:[0:ActiveMQ.DLQ] 3 messages 
affected.

java.lang.Error: java.io.IOException: Detected missing/corrupt journal files 
referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1148) 
~[na:1.8.0_131]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
~[na:1.8.0_131]
at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_131]
Caused by: java.io.IOException: Detected missing/corrupt journal files 
referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
at 
org.apache.activemq.store.kahadb.MessageDatabase.recoverIndex(MessageDatabase.java:965)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase$5.execute(MessageDatabase.java:717)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.disk.page.Transaction.execute(Transaction.java:779)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:714)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473) 
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493) 
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219) 
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55) 
~[activemq-client-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:232)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]```

Downgrading to 5.15.0 resolves the problem.
This is an embedded broker setup, using

```
val pa = brokerService.persistenceAdapter as KahaDBPersistenceAdapter
pa.isCheckForCorruptJournalFiles = true

[jira] [Created] (AMQ-6831) Broker fails to start complaining about missing/corrupt journal files after upgrading to 5.15.1

2017-10-09 Thread masc (JIRA) 
masc created AMQ-6831:
-

 Summary: Broker fails to start complaining about missing/corrupt 
journal files after upgrading to 5.15.1
 Key: AMQ-6831
 URL: https://issues.apache.org/jira/browse/AMQ-6831
 Project: ActiveMQ
  Issue Type: Bug
Affects Versions: 5.15.1
Reporter: masc


```2017-10-09 12:29:36.802 ERROR 4197 --- [pool-3-thread-1] 
org.deku.leoz.node.Application   : java.io.IOException: Detected 
missing/corrupt journal files referenced by:[0:ActiveMQ.DLQ] 3 messages 
affected.

java.lang.Error: java.io.IOException: Detected missing/corrupt journal files 
referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1148) 
~[na:1.8.0_131]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
~[na:1.8.0_131]
at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_131]
Caused by: java.io.IOException: Detected missing/corrupt journal files 
referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
at 
org.apache.activemq.store.kahadb.MessageDatabase.recoverIndex(MessageDatabase.java:965)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase$5.execute(MessageDatabase.java:717)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.disk.page.Transaction.execute(Transaction.java:779)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:714)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473) 
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493) 
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219) 
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at 
org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55) 
~[activemq-client-5.15.1.jar:5.15.1]
at 
org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:232)
 ~[activemq-kahadb-store-5.15.1.jar:5.15.1]```

Downgrading to 5.15.0 resolves the problem.
This is an embedded broker setup, using

```
val pa = brokerService.persistenceAdapter as KahaDBPersistenceAdapter
pa.isCheckForCorruptJournalFiles = true
pa.isIgnoreMissingJournalfiles = false
```



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1455) HQ222142: Error on resetting large message deliver - null: java.lang.NullPointerException

2017-10-09 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on ARTEMIS-1455:
-

GitHub user treblereel opened a pull request:

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

ARTEMIS-1455 HQ222142: Error on resetting large message deliver - nul…

…l: java.lang.NullPointerException
JIRA: https://issues.apache.org/jira/browse/ARTEMIS-1455


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

$ git pull https://github.com/treblereel/activemq-artemis-wildfly 
ARTEMIS-1455

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

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


commit 285f0cc22e62e9402958724dac2156adf6a0df72
Author: Dmitrii Tikhomirov 
Date:   2017-10-09T09:51:32Z

ARTEMIS-1455 HQ222142: Error on resetting large message deliver - null: 
java.lang.NullPointerException




> HQ222142: Error on resetting large message deliver - null: 
> java.lang.NullPointerException
> -
>
> Key: ARTEMIS-1455
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1455
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>  Components: AMQP
>Affects Versions: 2.3.0
>Reporter: Dmitrii Tikhomirov
>
> The message
> 
> HQ222142: Error on resetting large message deliver - null: 
> java.lang.NullPointerException
> 
> can be seen in the server log file.
> This issue is a clone of https://issues.jboss.org/browse/HORNETQ-1557



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ARTEMIS-1455) HQ222142: Error on resetting large message deliver - null: java.lang.NullPointerException

2017-10-09 Thread Dmitrii Tikhomirov (JIRA) 

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

Dmitrii Tikhomirov updated ARTEMIS-1455:

Description: 
The message

HQ222142: Error on resetting large message deliver - null: 
java.lang.NullPointerException

can be seen in the server log file.
This issue is a clone of https://issues.jboss.org/browse/HORNETQ-1557


  was:
The message

HQ222142: Error on resetting large message deliver - null: 
java.lang.NullPointerException

can be seen in the server log file.


> HQ222142: Error on resetting large message deliver - null: 
> java.lang.NullPointerException
> -
>
> Key: ARTEMIS-1455
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1455
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>  Components: AMQP
>Affects Versions: 2.3.0
>Reporter: Dmitrii Tikhomirov
>
> The message
> 
> HQ222142: Error on resetting large message deliver - null: 
> java.lang.NullPointerException
> 
> can be seen in the server log file.
> This issue is a clone of https://issues.jboss.org/browse/HORNETQ-1557



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ARTEMIS-1455) HQ222142: Error on resetting large message deliver - null: java.lang.NullPointerException

2017-10-09 Thread Dmitrii Tikhomirov (JIRA) 
Dmitrii Tikhomirov created ARTEMIS-1455:
---

 Summary: HQ222142: Error on resetting large message deliver - 
null: java.lang.NullPointerException
 Key: ARTEMIS-1455
 URL: https://issues.apache.org/jira/browse/ARTEMIS-1455
 Project: ActiveMQ Artemis
  Issue Type: Bug
  Components: AMQP
Affects Versions: 2.3.0
Reporter: Dmitrii Tikhomirov


The message

HQ222142: Error on resetting large message deliver - null: 
java.lang.NullPointerException

can be seen in the server log file.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1227) Internal properties not removed from messages

2017-10-09 Thread Howard Gao (JIRA) 

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

Howard Gao commented on ARTEMIS-1227:
-

Sorry forgot this. I'll port the fix from hornetq.



> Internal properties not removed from messages
> -
>
> Key: ARTEMIS-1227
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1227
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 1.5.5, 2.1.0
>Reporter: Howard Gao
>Assignee: Howard Gao
> Fix For: unscheduled
>
>
> In a cluster if a node is shut down (or crashed) when a
> message is being routed to a remote binding, a internal
> property may be added to the message and persisted. The
> name of the property is like _AMQ_ROUTE_TOsf.my-cluster*.
> if the node starts back, it will load and reroute this message
> and if it goes to a local consumer, this property won't
> get removed and goes to the client.
> The fix is to remove this internal property before it
> is sent to any client.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1454) Support SASL in outgoing AMQP connections

2017-10-09 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on ARTEMIS-1454:
-

GitHub user rgodfrey opened a pull request:

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

ARTEMIS-1454: Support SASL in outgoing AMQP

Update ProtonHandler to allow for both client and server side SASL
and other related changes to allow for setting of client side mechanism

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

$ git pull https://github.com/rgodfrey/activemq-artemis master

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

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


commit 91029e99309dbb7b6ed2f3f7e283e8028539c89c
Author: Robert Godfrey 
Date:   2017-09-27T21:45:14Z

ARTEMIS-1454: Support SASL in outgoing AMQP

Update ProtonHandler to allow for both client and server side SASL
and other related changes to allow for setting of client side mechanism




> Support SASL in outgoing AMQP connections
> -
>
> Key: ARTEMIS-1454
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1454
> Project: ActiveMQ Artemis
>  Issue Type: Improvement
>  Components: AMQP
>Reporter: Rob Godfrey
>Priority: Minor
>
> ARTEMIS-814 introduced the ability for Artemis to make outgoing AMQP 
> connections, however it did not support the use of SASL negotiation to secure 
> them.
> In order to secure the outgoing connection, and provide identity information 
> to the remote peer that Artemis is connecting to, we need to introduce the 
> ability for the outgoing connection to negotiate a SASL layer



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ARTEMIS-1454) Support SASL in outgoing AMQP connections

2017-10-09 Thread Rob Godfrey (JIRA) 
Rob Godfrey created ARTEMIS-1454:


 Summary: Support SASL in outgoing AMQP connections
 Key: ARTEMIS-1454
 URL: https://issues.apache.org/jira/browse/ARTEMIS-1454
 Project: ActiveMQ Artemis
  Issue Type: Improvement
  Components: AMQP
Reporter: Rob Godfrey
Priority: Minor


ARTEMIS-814 introduced the ability for Artemis to make outgoing AMQP 
connections, however it did not support the use of SASL negotiation to secure 
them.

In order to secure the outgoing connection, and provide identity information to 
the remote peer that Artemis is connecting to, we need to introduce the ability 
for the outgoing connection to negotiate a SASL layer



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)