[jira] [Commented] (ARTEMIS-1749) Examples doesn't work on Windows

2018-04-06 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on ARTEMIS-1749:
-

Github user ingo1121 commented on the issue:

https://github.com/apache/activemq-artemis/pull/1983
  
Hi!

Sorry for the mess with the git tree!

 

I have some question, though: 

 

1.  What is your normal build procedure? On my fork, I’ve made a Jenkins 
job, that just does a ”mvn install” ob the root directory; no profiles or 
anything. Is that reasonable?
2.  I tried to make a ”full example” integration test; by running ”mvn 
-Pexamples verify” on the examples directory. Unfortuatly it quickly runs out 
of steam (both on Windows and RHEL). Is this something that should be fixed? 
Should I register a JIRA? I notice that a lot of Java processes are left behind…

 

Regards

Ingemar

 

 

Från: clebertsuconic  
Skickat: den 3 april 2018 00:52
Till: apache/activemq-artemis 
Kopia: ingo1121 ; Mention 
Ämne: Re: [apache/activemq-artemis] ARTEMIS-1749 - Fixes the 
ssl-enabled-crl-mqtt (#1983)

 

I fixed it.. but your PR was way too messed up. if I had merged your 
merges.. we would have created a mess on master. please no merge commits on PRs.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub 
 , 
or mute the thread 

 .  

 




> Examples doesn't work on Windows
> 
>
> Key: ARTEMIS-1749
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1749
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Affects Versions: 2.5.0
> Environment: Windows 10
> JDK 1.8.0_112
> apache-maven-3.5.0
>Reporter: Ingemar Allqvist
>Assignee: Justin Bertram
>Priority: Major
>
> The examples:
> "ssl-enabled-dual-authentication"
> "stomp"
> "stomp-dual-authentication"
> Doesn't work on Windows (10?). The Maven build produces an error, and the 
> server doesn't start:
> server-out: _    _   _
> server-out:    / \  | |_  ___ __  __(_) _
> server-out:   / _ \|  _ \ __|/ _ \  \/  | |/  __/
> server-out:  / ___ \ | \/ |_/  __/ |\/| | |\___ \
> server-out: /_/   \_\|   \__\|_|  |_|_|/___ /
> server-out: Apache ActiveMQ Artemis 2.4.0
> server-out:
> server-out:
> server-err:Exception in thread "main" java.net.URISyntaxException: Illegal 
> character in opaque part at index 2: 
> C:\WS\program\artemis-2\examples\features\standard\ssl-enabled-dual-authentication\target\server0/etc/broker.xml
> server-err: at java.net.URI$Parser.fail(Unknown Source)
> server-err: at java.net.URI$Parser.checkChars(Unknown Source)
> server-err: at java.net.URI$Parser.parse(Unknown Source)
> server-err: at java.net.URI.(Unknown Source)
> server-err: at 
> org.apache.activemq.artemis.dto.ServerDTO.getConfigurationURI(ServerDTO.java:39)
> server-err: at 
> org.apache.activemq.artemis.dto.ServerDTO.getConfigurationFile(ServerDTO.java:47)
> server-err: at 
> org.apache.activemq.artemis.cli.commands.Run.execute(Run.java:75)
> server-err: at 
> org.apache.activemq.artemis.cli.Artemis.internalExecute(Artemis.java:149)
> server-err: at 
> org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:96)
> server-err: at 
> org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:123)
> server-err: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> server-err: at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> server-err: at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> server-err: at java.lang.reflect.Method.invoke(Unknown Source)
> server-err: at 
> org.apache.activemq.artemis.boot.Artemis.execute(Artemis.java:129)
> server-err: at org.apache.activemq.artemis.boot.Artemis.main(Artemis.java:49)



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

[jira] [Commented] (ARTEMIS-1761) Log one warning if cluster could not be formed because it's not possible to connect to other cluster node

2018-04-06 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on ARTEMIS-1761:
-

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

https://github.com/apache/activemq-artemis/pull/1975#discussion_r179841255
  
--- Diff: 
artemis-server/src/main/java/org/apache/activemq/artemis/core/server/cluster/impl/BridgeImpl.java
 ---
@@ -930,9 +930,7 @@ protected void connect() {
scheduleRetryConnectFixedTimeout(this.retryInterval);
return;
 } else {
-   if (logger.isDebugEnabled()) {
-  logger.debug("Bridge " + this + " is unable to connect 
to destination. Retrying", e);
--- End diff --

Can you still keep the log.debug?

Didn't I see you doing this somewhere else? is that the same issue?


> Log one warning if cluster could not be formed because it's not possible to 
> connect to other cluster node
> -
>
> Key: ARTEMIS-1761
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1761
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Affects Versions: 1.5.6, 2.5.0
>Reporter: Radovan Stancel
>Priority: Major
>
> If discovery-group receives connector which is not possible to use to create 
> cluster connection (using such connector fails) then server should log one 
> warning. Currently server is logging this on DEBUG level which is confusing 
> and it's not clear why cluster was not formed. It's just silently retrying 
> bad connector on background (on debug level).
> Current debug logs:
> {code}
> 14:43:45,777 DEBUG 
> [org.apache.activemq.artemis.core.server.cluster.impl.BridgeImpl] (Thread-4 
> (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$3@3f47a5c5))
>  Bridge ClusterConnecti
> onBridge@516796ab [name=sf.my-cluster.6eca14fb-4535-11e7-bc50-3ca9f4349bfc, 
> queue=QueueImpl[name=sf.my-cluster.6eca14fb-4535-11e7-bc50-3ca9f4349bfc, 
> postOffice=PostOfficeImpl [server=ActiveMQServerImpl::serverUU
> ID=5630528e-4535-11e7-9213-3c970e9648c8]]@2d035848 
> targetConnector=ServerLocatorImpl 
> (identity=(Cluster-connection-bridge::ClusterConnectionBridge@516796ab 
> [name=sf.my-cluster.6eca14fb-4535-11e7-bc50-3ca9f4349bf
> c, queue=QueueImpl[name=sf.my-cluster.6eca14fb-4535-11e7-bc50-3ca9f4349bfc, 
> postOffice=PostOfficeImpl 
> [server=ActiveMQServerImpl::serverUUID=5630528e-4535-11e7-9213-3c970e9648c8]]@2d035848
>  targetConnector=Server
> LocatorImpl [initialConnectors=[TransportConfiguration(name=http-connector, 
> factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory)
>  ?httpUpgradeEndpoint=https-acceptor
> ame=default=true=9080=localhost], 
> discoveryGroupConfiguration=null]]::ClusterConnectionImpl@386706758[nodeUUID=5630528e-4535-11e7-9213-3c970e9648c8,
>  connector=TransportConfiguration(
> name=http-connector, 
> factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory)
>  
> ?httpUpgradeEndpoint=https-acceptor=default=true=8080=loca
> lhost, address=jms, 
> server=ActiveMQServerImpl::serverUUID=5630528e-4535-11e7-9213-3c970e9648c8])) 
> [initialConnectors=[TransportConfiguration(name=http-connector, 
> factory=org-apache-activemq-artemis-core-remoting
> -impl-netty-NettyConnectorFactory) 
> ?httpUpgradeEndpoint=https-acceptor=default=true=9080=localhost],
>  discoveryGroupConfiguration=null]] is unable to connect to des
> tination. Retrying: ActiveMQNotConnectedException[errorType=NOT_CONNECTED 
> message=Unable to connect to server using configuration 
> TransportConfiguration(name=http-connector, 
> factory=org-apache-activemq-artemis-c
> ore-remoting-impl-netty-NettyConnectorFactory) 
> ?httpUpgradeEndpoint=https-acceptor=default=true=9080=localhost]
>     at 
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.connect(ClientSessionFactoryImpl.java:245)
>  [artemis-core-client-1.5.5.001-redhat-1.jar:1.5.5.001-redhat-1]
>     at 
> org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:685)
>  [artemis-core-client-1.5.5.001-redhat-1.jar:1.5.5.001-redhat-1]
>     at 
> org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:659)
>  [artemis-core-client-1.5.5.001-redhat-1.jar:1.5.5.001-redhat-1]
>     at 
> org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionBridge.createSessionFactory(ClusterConnectionBridge.java:136)
>  [artemis-server-1.5.5.001-redhat-1.jar:1.5.5.001-redhat-1]
>     at 
> org.apache.activemq.artemis.core.server.cluster.impl.BridgeImpl.connect(BridgeImpl.java:857)
>

[jira] [Commented] (ARTEMIS-1749) Examples doesn't work on Windows

2018-04-06 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on ARTEMIS-1749:
-

Github user ingo1121 commented on the issue:

https://github.com/apache/activemq-artemis/pull/1983
  
Been absent on vacation. Back now. Sorry if i messed up the revision-tree!

 Anyway, now the examples in Windows is, is far as I can judge, consistent 
with examples on RHEL7. 


> Examples doesn't work on Windows
> 
>
> Key: ARTEMIS-1749
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1749
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Affects Versions: 2.5.0
> Environment: Windows 10
> JDK 1.8.0_112
> apache-maven-3.5.0
>Reporter: Ingemar Allqvist
>Assignee: Justin Bertram
>Priority: Major
>
> The examples:
> "ssl-enabled-dual-authentication"
> "stomp"
> "stomp-dual-authentication"
> Doesn't work on Windows (10?). The Maven build produces an error, and the 
> server doesn't start:
> server-out: _    _   _
> server-out:    / \  | |_  ___ __  __(_) _
> server-out:   / _ \|  _ \ __|/ _ \  \/  | |/  __/
> server-out:  / ___ \ | \/ |_/  __/ |\/| | |\___ \
> server-out: /_/   \_\|   \__\|_|  |_|_|/___ /
> server-out: Apache ActiveMQ Artemis 2.4.0
> server-out:
> server-out:
> server-err:Exception in thread "main" java.net.URISyntaxException: Illegal 
> character in opaque part at index 2: 
> C:\WS\program\artemis-2\examples\features\standard\ssl-enabled-dual-authentication\target\server0/etc/broker.xml
> server-err: at java.net.URI$Parser.fail(Unknown Source)
> server-err: at java.net.URI$Parser.checkChars(Unknown Source)
> server-err: at java.net.URI$Parser.parse(Unknown Source)
> server-err: at java.net.URI.(Unknown Source)
> server-err: at 
> org.apache.activemq.artemis.dto.ServerDTO.getConfigurationURI(ServerDTO.java:39)
> server-err: at 
> org.apache.activemq.artemis.dto.ServerDTO.getConfigurationFile(ServerDTO.java:47)
> server-err: at 
> org.apache.activemq.artemis.cli.commands.Run.execute(Run.java:75)
> server-err: at 
> org.apache.activemq.artemis.cli.Artemis.internalExecute(Artemis.java:149)
> server-err: at 
> org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:96)
> server-err: at 
> org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:123)
> server-err: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> server-err: at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> server-err: at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> server-err: at java.lang.reflect.Method.invoke(Unknown Source)
> server-err: at 
> org.apache.activemq.artemis.boot.Artemis.execute(Artemis.java:129)
> server-err: at org.apache.activemq.artemis.boot.Artemis.main(Artemis.java:49)



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

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

2018-04-06 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on ARTEMIS-1787:
-

Github user clebertsuconic commented on the issue:

https://github.com/apache/activemq-artemis/pull/1994
  
same thing I asked on the JIRA. Why it shouldn't? why only on noLocal?

trying to get some context on the why it should not be included...


it would be nice to include such thing on the commit description please.


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



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

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

2018-04-06 Thread clebert suconic (JIRA) 

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

clebert suconic commented on ARTEMIS-1787:
--

Why? :) Why it should not include the connectionID?

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



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

[jira] [Commented] (ARTEMIS-1701) Zone ID not stripped properly from IPv6 addresses

2018-04-06 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on ARTEMIS-1701:
-

Github user asfgit closed the pull request at:

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


> Zone ID not stripped properly from IPv6 addresses
> -
>
> Key: ARTEMIS-1701
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1701
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 2.4.0
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
>




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

[jira] [Commented] (ARTEMIS-1701) Zone ID not stripped properly from IPv6 addresses

2018-04-06 Thread ASF subversion and git services (JIRA) 

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

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

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

ARTEMIS-1701 strip zone id from IPv6 host


> Zone ID not stripped properly from IPv6 addresses
> -
>
> Key: ARTEMIS-1701
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1701
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 2.4.0
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
>




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

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

2018-04-06 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on ARTEMIS-1776:
-

Github user asfgit closed the pull request at:

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


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



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

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

2018-04-06 Thread ASF subversion and git services (JIRA) 

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

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

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

ARTEMIS-1776 Blocked Bridge is not resuming after reconnect

This is still part of ARTEMIS-1776 fix, which still part of the same release as 
we are on now.
Hence I'm not opening a new JIRA for this one.


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



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

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

2018-04-06 Thread ASF subversion and git services (JIRA) 

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

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

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

ARTEMIS-1776 Blocked Bridge is not resuming after reconnect

This is still part of ARTEMIS-1776 fix, which still part of the same release as 
we are on now.
Hence I'm not opening a new JIRA for this one.


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



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

[jira] [Commented] (ARTEMIS-1789) Permission check failed when resolving DNS under a security manager

2018-04-06 Thread Justin Bertram (JIRA) 

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

Justin Bertram commented on ARTEMIS-1789:
-

I believe this can be addressed by back-porting the fix from ARTEMIS-1701 to 
the 1.x branch.

> Permission check failed when resolving DNS under a security manager
> ---
>
> Key: ARTEMIS-1789
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1789
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Affects Versions: 1.5.5
>Reporter: Jeff Mesnil
>Priority: Major
>
> When our application server is running with a security managert, Artemis 
> reports an error because it does not have the permission to resolve IP 
> addresses:
> {code}
> AMQ212007: connector.create or connectorFactory.createConnector should never 
> throw an exception, implementation is badly behaved, but we will deal with it 
> anyway.: java.security.AccessControlException: WFSM01: Permission check 
> failed (permission "("java.net.SocketPermission" "localhost" "resolve")" in 
> code source "(vfs:/content/JMSResourceDefinitionsTestCase.jar  certificates>)" of "ModuleClassLoader for Module 
> "deployment.JMSResourceDefinitionsTestCase.jar" from Service Module Loader")
> at 
> org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:295)
> at 
> org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:192)
> at java.lang.SecurityManager.checkConnect(SecurityManager.java:1048)
> at 
> org.wildfly.security.manager.WildFlySecurityManager.checkConnect(WildFlySecurityManager.java:390)
> at java.net.InetAddress.getAllByName0(InetAddress.java:1268)
> at java.net.InetAddress.getAllByName(InetAddress.java:1192)
> at java.net.InetAddress.getAllByName(InetAddress.java:1126)
> at java.net.InetAddress.getByName(InetAddress.java:1076)
> at java.net.InetSocketAddress.(InetSocketAddress.java:220)
> at 
> org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector.createConnection(NettyConnector.java:600)
> at 
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.openTransportConnection(ClientSessionFactoryImpl.java:1036)
> at 
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.createTransportConnection(ClientSessionFactoryImpl.java:1076)
> at 
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.establishNewConnection(ClientSessionFactoryImpl.java:1254)
> at 
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.getConnection(ClientSessionFactoryImpl.java:891)
> at 
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.getConnectionWithRetry(ClientSessionFactoryImpl.java:795)
> at 
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.connect(ClientSessionFactoryImpl.java:238)
> at 
> org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:772)
> at 
> org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:755)
> at 
> org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createXAConnection(ActiveMQConnectionFactory.java:338)
> at 
> org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection.setup(ActiveMQRAManagedConnection.java:769)
> at 
> org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection.(ActiveMQRAManagedConnection.java:161)
> at 
> org.apache.activemq.artemis.ra.ActiveMQRAManagedConnectionFactory.createManagedConnection(ActiveMQRAManagedConnectionFactory.java:151)
> {code}
> The solution may be to explicitly resolve the InetAddress(s) in a privileged 
> block before passing them in to Netty.



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

[jira] [Commented] (ARTEMIS-1701) Zone ID not stripped properly from IPv6 addresses

2018-04-06 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on ARTEMIS-1701:
-

GitHub user jbertram opened a pull request:

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

ARTEMIS-1701 strip zone id from IPv6 host



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

$ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-1701

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

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


commit 5725f7e2fa995ad554535baf58a7aa9917836a00
Author: Justin Bertram 
Date:   2018-02-23T21:05:00Z

ARTEMIS-1701 strip zone id from IPv6 host




> Zone ID not stripped properly from IPv6 addresses
> -
>
> Key: ARTEMIS-1701
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1701
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 2.4.0
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
>




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

[jira] [Reopened] (ARTEMIS-1701) Zone ID not stripped properly from IPv6 addresses

2018-04-06 Thread Justin Bertram (JIRA) 

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

Justin Bertram reopened ARTEMIS-1701:
-

> Zone ID not stripped properly from IPv6 addresses
> -
>
> Key: ARTEMIS-1701
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1701
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 2.4.0
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
>




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

[jira] [Updated] (ARTEMIS-1701) Zone ID not stripped properly from IPv6 addresses

2018-04-06 Thread Justin Bertram (JIRA) 

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

Justin Bertram updated ARTEMIS-1701:

Fix Version/s: (was: 2.5.0)

> Zone ID not stripped properly from IPv6 addresses
> -
>
> Key: ARTEMIS-1701
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1701
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 2.4.0
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
>




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

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

2018-04-06 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on ARTEMIS-1653:
-

Github user franz1981 commented on the issue:

https://github.com/apache/activemq-artemis/pull/1997
  
@clebertsuconic @nlippke I know that the failing COUNT sounds weird, but it 
is quite simple to be reproduced with DB2 through the test attached :+1: 


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



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

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

2018-04-06 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on ARTEMIS-1653:
-

GitHub user franz1981 opened a pull request:

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

ARTEMIS-1653 Allow database tables to be created externally

The previous commit about this feature wasn't using the row count query
ResultSet.
The mechanics has been changed to allow the row count query
to fail, because DROP and CREATE aren't transactional and immediate
in most DBMS.
It includes a test that stress its mechanics if used with DBMS like
DB2 10.5 and Oracle 12c.
Additional checks and logs have been added to trace each steps.

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

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

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

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


commit 1e2b5270854ba19a87a3ba0fa308751ce9cc5122
Author: Francesco Nigro 
Date:   2018-04-03T08:11:04Z

ARTEMIS-1653 Allow database tables to be created externally

The previous commit about this feature wasn't using the row count query
ResultSet.
The mechanics has been changed to allow the row count query
to fail, because DROP and CREATE aren't transactional and immediate
in most DBMS.
It includes a test that stress its mechanics if used with DBMS like
DB2 10.5 and Oracle 12c.
Additional checks and logs have been added to trace each steps.




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



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

[jira] [Created] (ARTEMIS-1789) Permission check failed when resolving DNS under a security manager

2018-04-06 Thread Jeff Mesnil (JIRA) 
Jeff Mesnil created ARTEMIS-1789:


 Summary: Permission check failed when resolving DNS under a 
security manager
 Key: ARTEMIS-1789
 URL: https://issues.apache.org/jira/browse/ARTEMIS-1789
 Project: ActiveMQ Artemis
  Issue Type: Bug
Affects Versions: 1.5.5
Reporter: Jeff Mesnil


When our application server is running with a security managert, Artemis 
reports an error because it does not have the permission to resolve IP 
addresses:

{code}
AMQ212007: connector.create or connectorFactory.createConnector should never 
throw an exception, implementation is badly behaved, but we will deal with it 
anyway.: java.security.AccessControlException: WFSM01: Permission check 
failed (permission "("java.net.SocketPermission" "localhost" "resolve")" in 
code source "(vfs:/content/JMSResourceDefinitionsTestCase.jar )" of "ModuleClassLoader for Module 
"deployment.JMSResourceDefinitionsTestCase.jar" from Service Module Loader")
at 
org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:295)
at 
org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:192)
at java.lang.SecurityManager.checkConnect(SecurityManager.java:1048)
at 
org.wildfly.security.manager.WildFlySecurityManager.checkConnect(WildFlySecurityManager.java:390)
at java.net.InetAddress.getAllByName0(InetAddress.java:1268)
at java.net.InetAddress.getAllByName(InetAddress.java:1192)
at java.net.InetAddress.getAllByName(InetAddress.java:1126)
at java.net.InetAddress.getByName(InetAddress.java:1076)
at java.net.InetSocketAddress.(InetSocketAddress.java:220)
at 
org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector.createConnection(NettyConnector.java:600)
at 
org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.openTransportConnection(ClientSessionFactoryImpl.java:1036)
at 
org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.createTransportConnection(ClientSessionFactoryImpl.java:1076)
at 
org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.establishNewConnection(ClientSessionFactoryImpl.java:1254)
at 
org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.getConnection(ClientSessionFactoryImpl.java:891)
at 
org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.getConnectionWithRetry(ClientSessionFactoryImpl.java:795)
at 
org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.connect(ClientSessionFactoryImpl.java:238)
at 
org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:772)
at 
org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:755)
at 
org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createXAConnection(ActiveMQConnectionFactory.java:338)
at 
org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection.setup(ActiveMQRAManagedConnection.java:769)
at 
org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection.(ActiveMQRAManagedConnection.java:161)
at 
org.apache.activemq.artemis.ra.ActiveMQRAManagedConnectionFactory.createManagedConnection(ActiveMQRAManagedConnectionFactory.java:151)
{code}

The solution may be to explicitly resolve the InetAddress(s) in a privileged 
block before passing them in to Netty.



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

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

2018-04-06 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on ARTEMIS-1776:
-

GitHub user clebertsuconic opened a pull request:

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

ARTEMIS-1776 Blocked Bridge is not resuming after reconnect

This is still part of ARTEMIS-1776 fix, which still part of the same 
release as we are on now.
Hence I'm not opening a new JIRA for this one.

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

$ git pull https://github.com/clebertsuconic/activemq-artemis bridge

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

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


commit 91ed6e3a726b58d04d4155543f1701c6ee0d0ba2
Author: Clebert Suconic 
Date:   2018-04-06T14:00:43Z

ARTEMIS-1776 Blocked Bridge is not resuming after reconnect

This is still part of ARTEMIS-1776 fix, which still part of the same 
release as we are on now.
Hence I'm not opening a new JIRA for this one.




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



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

[jira] [Closed] (ARTEMIS-1772) Reduce memory footprint and allocations of QueueImpl

2018-04-06 Thread Francesco Nigro (JIRA) 

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

Francesco Nigro closed ARTEMIS-1772.

Resolution: Fixed

> Reduce memory footprint and allocations of QueueImpl
> 
>
> Key: ARTEMIS-1772
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1772
> Project: ActiveMQ Artemis
>  Issue Type: New Feature
>Reporter: Francesco Nigro
>Assignee: Francesco Nigro
>Priority: Major
>
> Each message referenced into QueueImpl is using Atomic* and boxed types that 
> could be turned into primitive types, reducing the number of allocations and 
> increasing the precision of the memory footprint estimation.



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

[jira] [Reopened] (ARTEMIS-1774) Node Manager Store table name should be configurable

2018-04-06 Thread Francesco Nigro (JIRA) 

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

Francesco Nigro reopened ARTEMIS-1774:
--

It is not finished yet.

> Node Manager Store table name should be configurable
> 
>
> Key: ARTEMIS-1774
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1774
> Project: ActiveMQ Artemis
>  Issue Type: Improvement
>  Components: Broker
>Affects Versions: 2.5.0
>Reporter: Francesco Nigro
>Assignee: Francesco Nigro
>Priority: Major
> Fix For: 2.5.1
>
>




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

[jira] [Created] (ARTEMIS-1788) JDBC HA should use JDBC Network Timeout

2018-04-06 Thread Francesco Nigro (JIRA) 
Francesco Nigro created ARTEMIS-1788:


 Summary: JDBC HA should use JDBC Network Timeout
 Key: ARTEMIS-1788
 URL: https://issues.apache.org/jira/browse/ARTEMIS-1788
 Project: ActiveMQ Artemis
  Issue Type: Improvement
  Components: Broker
Affects Versions: 2.5.0
Reporter: Francesco Nigro
Assignee: Francesco Nigro
 Fix For: 2.5.1


The JDBC Node Manager doesn't use the JDBC Network Timeout used on the rest of 
the Journal.



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