[jira] [Created] (ARTEMIS-1660) create-journal-table.oracle does create identity for column id

2018-02-03 Thread Benjamin Graf (JIRA) 
Benjamin Graf created ARTEMIS-1660:
--

 Summary: create-journal-table.oracle does create identity for 
column id
 Key: ARTEMIS-1660
 URL: https://issues.apache.org/jira/browse/ARTEMIS-1660
 Project: ActiveMQ Artemis
  Issue Type: Bug
Affects Versions: 2.4.0
Reporter: Benjamin Graf


Statement contains identity column for id. That's wrong according to generic 
create statement and leaves invalid storage for userrecordtype 32/45



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

[jira] [Commented] (ARTEMIS-1656) OpenWire scalability improvements

2018-02-03 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on ARTEMIS-1656:
-

Github user franz1981 commented on the issue:

https://github.com/apache/activemq-artemis/pull/1849
  
I'm running the some sanity tests on it.
perf-wire now OpenWire is just 10/20% less than Core protocol for non 
durable messages (depending on message size), it has a much better scalability 
(like Core) and memory footprint thanks to transport buffer pooling.


> OpenWire scalability improvements
> -
>
> Key: ARTEMIS-1656
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1656
> Project: ActiveMQ Artemis
>  Issue Type: Improvement
>Reporter: Francesco Nigro
>Assignee: Francesco Nigro
>Priority: Minor
>
> OpenWire is using the synchronized OpenWireFormat instance belonging to 
> OpenWireProtocolManager: it won't allow to scale with the number of 
> connections.



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

[jira] [Commented] (ARTEMIS-1656) OpenWire scalability improvements

2018-02-03 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on ARTEMIS-1656:
-

GitHub user franz1981 opened a pull request:

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

ARTEMIS-1656 OpenWire scalability improvements

It includes:
- direct transport buffer pooling
- groupId SimpleString pooling
- exclusive OpenWireFormat per session and connection (in/out) to avoid 
contention
- cached trace check on JBoss server logger to avoid contention
- changed lastSent volatile set into lazy set to avoid full barrier cost on 
x86
- stateless OpenWireMessageConverter

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

$ git pull https://github.com/franz1981/activemq-artemis open_wire_tests

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

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


commit 75564032def0c1aa79de824a51e53eab0c2a8791
Author: Francesco Nigro 
Date:   2018-02-03T07:03:36Z

ARTEMIS-1656 OpenWire scalability improvements

It includes:
- direct transport buffer pooling
- groupId SimpleString pooling
- exclusive OpenWireFormat per session and connection (in/out) to avoid 
contention
- cached trace check on JBoss server logger to avoid contention
- changed lastSent volatile set into lazy set to avoid full barrier cost on 
x86
- stateless OpenWireMessageConverter




> OpenWire scalability improvements
> -
>
> Key: ARTEMIS-1656
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1656
> Project: ActiveMQ Artemis
>  Issue Type: Improvement
>Reporter: Francesco Nigro
>Assignee: Francesco Nigro
>Priority: Minor
>
> OpenWire is using the synchronized OpenWireFormat instance belonging to 
> OpenWireProtocolManager: it won't allow to scale with the number of 
> connections.



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

[jira] [Updated] (ARTEMIS-1659) AMQ224000: Failure in initialisation: java.lang.IllegalStateException: java.lang.IllegalStateException: Cursor 28 had already been created

2018-02-03 Thread Tom Ross (JIRA) 

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

Tom Ross updated ARTEMIS-1659:
--

To reproduce the issue follow the steps:

- Create two new brokers, one master and one slave
- Start master
- Start slave
- Stop master (confirming slave has become active)
- Restart master (wait for fallback, and confirm replication completes)

- Add new address and queue config to both master and slave broker.xml (whilst 
still running), e.g.


 
 
 
 


- now fail the master.

The exception can be seen the slave log file

>  AMQ224000: Failure in initialisation: java.lang.IllegalStateException: 
> java.lang.IllegalStateException: Cursor 28 had already been created
> ---
>
> Key: ARTEMIS-1659
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1659
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 2.0.0
> Environment:  Artemis 2
>Reporter: Tom Ross
>Priority: Major
>
> The following exception can be seen in the amq log file 
> {noformat}
> 08:07:04,658 ERROR [org.apache.activemq.artemis.core.server] AMQ224000: 
> Failure in initialisation: java.lang.IllegalStateException: 
> java.lang.IllegalStateException: Cursor 28 had already been created
> at 
> org.apache.activemq.artemis.core.server.QueueConfig$Builder.build(QueueConfig.java:151)
>  [artemis-server-2.0.0.amq-700013-redhat-1.jar:2.0.0.amq-700013-redhat-1]
> at 
> org.apache.activemq.artemis.core.server.impl.PostOfficeJournalLoader.initQueues(PostOfficeJournalLoader.java:154)
>  [artemis-server-2.0.0.amq-700013-redhat-1.jar:2.0.0.amq-700013-redhat-1]
> at 
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.loadJournals(ActiveMQServerImpl.java:2481)
>  [artemis-server-2.0.0.amq-700013-redhat-1.jar:2.0.0.amq-700013-redhat-1]
> at 
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.initialisePart2(ActiveMQServerImpl.java:2258)
>  [artemis-server-2.0.0.amq-700013-redhat-1.jar:2.0.0.amq-700013-redhat-1]
> at 
> org.apache.activemq.artemis.core.server.impl.SharedNothingBackupActivation.run(SharedNothingBackupActivation.java:342)
>  [artemis-server-2.0.0.amq-700013-redhat-1.jar:2.0.0.amq-700013-redhat-1]
> at 
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$ActivationThread.run(ActiveMQServerImpl.java:2866)
>  [artemis-server-2.0.0.amq-700013-redhat-1.jar:2.0.0.amq-700013-redhat-1]
> Caused by: java.lang.IllegalStateException: Cursor 28 had already been created
> at 
> org.apache.activemq.artemis.core.paging.cursor.impl.PageCursorProviderImpl.createSubscription(PageCursorProviderImpl.java:100)
>  [artemis-server-2.0.0.amq-700013-redhat-1.jar:2.0.0.amq-700013-redhat-1]
> at 
> org.apache.activemq.artemis.core.server.QueueConfig$Builder.build(QueueConfig.java:149)
>  [artemis-server-2.0.0.amq-700013-redhat-1.jar:2.0.0.amq-700013-redhat-1]
> ... 5 more
> {noformat}



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

[jira] [Created] (ARTEMIS-1659) AMQ224000: Failure in initialisation: java.lang.IllegalStateException: java.lang.IllegalStateException: Cursor 28 had already been created

2018-02-03 Thread Tom Ross (JIRA) 
Tom Ross created ARTEMIS-1659:
-

 Summary:  AMQ224000: Failure in initialisation: 
java.lang.IllegalStateException: java.lang.IllegalStateException: Cursor 28 had 
already been created
 Key: ARTEMIS-1659
 URL: https://issues.apache.org/jira/browse/ARTEMIS-1659
 Project: ActiveMQ Artemis
  Issue Type: Bug
  Components: Broker
Affects Versions: 2.0.0
 Environment:  Artemis 2
Reporter: Tom Ross


The following exception can be seen in the amq log file 
{noformat}
08:07:04,658 ERROR [org.apache.activemq.artemis.core.server] AMQ224000: Failure 
in initialisation: java.lang.IllegalStateException: 
java.lang.IllegalStateException: Cursor 28 had already been created
at 
org.apache.activemq.artemis.core.server.QueueConfig$Builder.build(QueueConfig.java:151)
 [artemis-server-2.0.0.amq-700013-redhat-1.jar:2.0.0.amq-700013-redhat-1]
at 
org.apache.activemq.artemis.core.server.impl.PostOfficeJournalLoader.initQueues(PostOfficeJournalLoader.java:154)
 [artemis-server-2.0.0.amq-700013-redhat-1.jar:2.0.0.amq-700013-redhat-1]
at 
org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.loadJournals(ActiveMQServerImpl.java:2481)
 [artemis-server-2.0.0.amq-700013-redhat-1.jar:2.0.0.amq-700013-redhat-1]
at 
org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.initialisePart2(ActiveMQServerImpl.java:2258)
 [artemis-server-2.0.0.amq-700013-redhat-1.jar:2.0.0.amq-700013-redhat-1]
at 
org.apache.activemq.artemis.core.server.impl.SharedNothingBackupActivation.run(SharedNothingBackupActivation.java:342)
 [artemis-server-2.0.0.amq-700013-redhat-1.jar:2.0.0.amq-700013-redhat-1]
at 
org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$ActivationThread.run(ActiveMQServerImpl.java:2866)
 [artemis-server-2.0.0.amq-700013-redhat-1.jar:2.0.0.amq-700013-redhat-1]
Caused by: java.lang.IllegalStateException: Cursor 28 had already been created
at 
org.apache.activemq.artemis.core.paging.cursor.impl.PageCursorProviderImpl.createSubscription(PageCursorProviderImpl.java:100)
 [artemis-server-2.0.0.amq-700013-redhat-1.jar:2.0.0.amq-700013-redhat-1]
at 
org.apache.activemq.artemis.core.server.QueueConfig$Builder.build(QueueConfig.java:149)
 [artemis-server-2.0.0.amq-700013-redhat-1.jar:2.0.0.amq-700013-redhat-1]
... 5 more
{noformat}



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

[jira] [Commented] (ARTEMIS-1658) Core queue lookup with Artemis RA no longer works with 1x address model

2018-02-03 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on ARTEMIS-1658:
-

Github user asfgit closed the pull request at:

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


> Core queue lookup with Artemis RA no longer works with 1x address model
> ---
>
> Key: ARTEMIS-1658
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1658
> Project: ActiveMQ Artemis
>  Issue Type: Improvement
>Affects Versions: 2.4.0
>Reporter: Martyn Taylor
>Priority: Major
>
> Artemis 1.x RA would do a core queue lookup if it could not find the
>  Destination in JNDI. We need to ensure that we can support the old
>  address model for backwards compatability.
>  



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

[jira] [Commented] (ARTEMIS-1658) Core queue lookup with Artemis RA no longer works with 1x address model

2018-02-03 Thread ASF subversion and git services (JIRA) 

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

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

Commit 355ae86c5e6d0413cc0b0d62ace3e40f4bc4cb8e 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=355ae86 ]

ARTEMIS-1658 Add prefix option to ActivationSpec 

checkstyle fix

> Core queue lookup with Artemis RA no longer works with 1x address model
> ---
>
> Key: ARTEMIS-1658
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1658
> Project: ActiveMQ Artemis
>  Issue Type: Improvement
>Affects Versions: 2.4.0
>Reporter: Martyn Taylor
>Priority: Major
>
> Artemis 1.x RA would do a core queue lookup if it could not find the
>  Destination in JNDI. We need to ensure that we can support the old
>  address model for backwards compatability.
>  



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

[jira] [Commented] (ARTEMIS-1658) Core queue lookup with Artemis RA no longer works with 1x address model

2018-02-03 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on ARTEMIS-1658:
-

GitHub user michaelandrepearce opened a pull request:

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

ARTEMIS-1658 Add prefix option to ActivationSpec

checkstyle fix

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

$ git pull https://github.com/michaelandrepearce/activemq-artemis FIX

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

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


commit 355ae86c5e6d0413cc0b0d62ace3e40f4bc4cb8e
Author: Michael André Pearce 
Date:   2018-02-03T08:31:22Z

ARTEMIS-1658 Add prefix option to ActivationSpec 

checkstyle fix




> Core queue lookup with Artemis RA no longer works with 1x address model
> ---
>
> Key: ARTEMIS-1658
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1658
> Project: ActiveMQ Artemis
>  Issue Type: Improvement
>Affects Versions: 2.4.0
>Reporter: Martyn Taylor
>Priority: Major
>
> Artemis 1.x RA would do a core queue lookup if it could not find the
>  Destination in JNDI. We need to ensure that we can support the old
>  address model for backwards compatability.
>  



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