[JBoss JIRA] (WFWIP-147) @JMSConnectionFactoryDefinition with property resourceAdapater to pooled-connection-factory defined in messaging-active subsystem does not work
by Miroslav Novak (Jira)
[ https://issues.jboss.org/browse/WFWIP-147?page=com.atlassian.jira.plugin.... ]
Miroslav Novak commented on WFWIP-147:
--------------------------------------
[~ehugonnet] I've added steps to reproduce. Could you try it, please?
> @JMSConnectionFactoryDefinition with property resourceAdapater to pooled-connection-factory defined in messaging-active subsystem does not work
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFWIP-147
> URL: https://issues.jboss.org/browse/WFWIP-147
> Project: WildFly WIP
> Issue Type: Bug
> Components: JMS
> Reporter: Miroslav Novak
> Assignee: ehsavoie Hugonnet
> Priority: Blocker
>
> If pooled-connection-factory is defined in messaging-active subsystem like:
> {code}
> <http-connector name="connector" socket-binding="messaging-socket-binding" endpoint="acceptor" server-name="default"/>
> <pooled-connection-factory name="activemq-ra-remote" entries="java:/testJmsXA " connectors="connector" transaction="xa"/>
> {code}
> and deployment tries to use it to create @JMSConnectionFactoryDefinition like:
> {code}
> @JMSConnectionFactoryDefinition(
> name="java:/jms/myRemoteJmsCf",
> resourceAdapter="activemq-ra-remote")
> {code}
> then deploy fails with:
> {code}
> 13:21:18,284 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "mdb-activemq-1.0-SNAPSHOT.jar")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.raactivator.\"mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_java_/jms/myRemoteJmsCf\"" => "WFLYJCA0046: Failed to start RA deployment [mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_java_/jms/myRemoteJmsCf]
> Caused by: org.jboss.jca.deployers.common.DeployException: IJ020051: Unable to start org.wildfly.extension.messaging.activemq.ActiveMQResourceAdapter
> Caused by: java.lang.IllegalArgumentException: must provide either TransportType or DiscoveryGroupAddress and DiscoveryGroupPort for ResourceAdapter Connection Factory"}}
> 13:21:18,295 INFO [org.jboss.as.server] (ServerService Thread Pool -- 48) WFLYSRV0010: Deployed "mdb-activemq-1.0-SNAPSHOT.jar" (runtime-name : "mdb-activemq-1.0-SNAPSHOT.jar")
> 13:21:18,297 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service jboss.connection-factory.reference-factory.jboss.naming.context.java.jms.myRemoteJmsCf (missing) dependents: [service jboss.naming.context.java.jms.myRemoteJmsCf]
> WFLYCTL0186: Services which failed to start: service jboss.raactivator."mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_java_/jms/myRemoteJmsCf": WFLYJCA0046: Failed to start RA deployment [mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_java_/jms/myRemoteJmsCf]
> WFLYCTL0448: 5 additional services are down due to their dependencies being missing or failed
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFWIP-147) @JMSConnectionFactoryDefinition with property resourceAdapater to pooled-connection-factory defined in messaging-active subsystem does not work
by Miroslav Novak (Jira)
[ https://issues.jboss.org/browse/WFWIP-147?page=com.atlassian.jira.plugin.... ]
Miroslav Novak updated WFWIP-147:
---------------------------------
Steps to Reproduce:
Steps to reproduce:
{code}
git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git
cd eap-tests-hornetq/scripts/
git checkout EAP7-1006
groovy -DEAP_ZIP_URL=file:///<path_to_wf_zip> PrepareServers7.groovy
export WORKSPACE=$PWD
export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap
export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap
export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap
export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap
cd ../jboss-hornetq-testsuite/
mvn clean test -Dtest=RemoteBrokerTestCase#testSubsystemCFDToRemoteBroker -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.2.0.GA.CR1 | tee log
{code}
> @JMSConnectionFactoryDefinition with property resourceAdapater to pooled-connection-factory defined in messaging-active subsystem does not work
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFWIP-147
> URL: https://issues.jboss.org/browse/WFWIP-147
> Project: WildFly WIP
> Issue Type: Bug
> Components: JMS
> Reporter: Miroslav Novak
> Assignee: ehsavoie Hugonnet
> Priority: Blocker
>
> If pooled-connection-factory is defined in messaging-active subsystem like:
> {code}
> <http-connector name="connector" socket-binding="messaging-socket-binding" endpoint="acceptor" server-name="default"/>
> <pooled-connection-factory name="activemq-ra-remote" entries="java:/testJmsXA " connectors="connector" transaction="xa"/>
> {code}
> and deployment tries to use it to create @JMSConnectionFactoryDefinition like:
> {code}
> @JMSConnectionFactoryDefinition(
> name="java:/jms/myRemoteJmsCf",
> resourceAdapter="activemq-ra-remote")
> {code}
> then deploy fails with:
> {code}
> 13:21:18,284 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "mdb-activemq-1.0-SNAPSHOT.jar")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.raactivator.\"mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_java_/jms/myRemoteJmsCf\"" => "WFLYJCA0046: Failed to start RA deployment [mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_java_/jms/myRemoteJmsCf]
> Caused by: org.jboss.jca.deployers.common.DeployException: IJ020051: Unable to start org.wildfly.extension.messaging.activemq.ActiveMQResourceAdapter
> Caused by: java.lang.IllegalArgumentException: must provide either TransportType or DiscoveryGroupAddress and DiscoveryGroupPort for ResourceAdapter Connection Factory"}}
> 13:21:18,295 INFO [org.jboss.as.server] (ServerService Thread Pool -- 48) WFLYSRV0010: Deployed "mdb-activemq-1.0-SNAPSHOT.jar" (runtime-name : "mdb-activemq-1.0-SNAPSHOT.jar")
> 13:21:18,297 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service jboss.connection-factory.reference-factory.jboss.naming.context.java.jms.myRemoteJmsCf (missing) dependents: [service jboss.naming.context.java.jms.myRemoteJmsCf]
> WFLYCTL0186: Services which failed to start: service jboss.raactivator."mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_java_/jms/myRemoteJmsCf": WFLYJCA0046: Failed to start RA deployment [mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_java_/jms/myRemoteJmsCf]
> WFLYCTL0448: 5 additional services are down due to their dependencies being missing or failed
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-10380) ThreadPoolExecutor leak under SM due to lack of privileged block
by Miroslav Novak (Jira)
[ https://issues.jboss.org/browse/WFLY-10380?page=com.atlassian.jira.plugin... ]
Miroslav Novak commented on WFLY-10380:
---------------------------------------
[~jmesnil] [~clebert.suconic] I've cloned the jira to: https://issues.apache.org/jira/browse/ARTEMIS-2171
> ThreadPoolExecutor leak under SM due to lack of privileged block
> ----------------------------------------------------------------
>
> Key: WFLY-10380
> URL: https://issues.jboss.org/browse/WFLY-10380
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Reporter: David Lloyd
> Priority: Critical
> Labels: security-manager
>
> Still researching the source of these leaks.
> The way the leak happens is, a {{java.util.concurrent.ThreadPoolExecutor}} is constructed from an unprivileged context. The pool starts up and threads are created without a problem, however, the thread pool is never shut down. The finalizer runs but since it tries to shut down the pool with an access control context that was captured during construction, it fails because the context did not have the {{modifyThread}} {{RuntimePermission}}, and the thread pool never shuts down.
> We need to identify the points where TPEs are being constructed without controlled privileges.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-11327) ThreadPoolExecutor leak under SM due to lack of privileged block
by Miroslav Novak (Jira)
Miroslav Novak created WFLY-11327:
-------------------------------------
Summary: ThreadPoolExecutor leak under SM due to lack of privileged block
Key: WFLY-11327
URL: https://issues.jboss.org/browse/WFLY-11327
Project: WildFly
Issue Type: Bug
Components: JMS
Reporter: Miroslav Novak
Still researching the source of these leaks.
The way the leak happens is, a {{java.util.concurrent.ThreadPoolExecutor}} is constructed from an unprivileged context. The pool starts up and threads are created without a problem, however, the thread pool is never shut down. The finalizer runs but since it tries to shut down the pool with an access control context that was captured during construction, it fails because the context did not have the {{modifyThread}} {{RuntimePermission}}, and the thread pool never shuts down.
We need to identify the points where TPEs are being constructed without controlled privileges.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-11326) The org.jdom module should be removed
by Brian Stansberry (Jira)
Brian Stansberry created WFLY-11326:
---------------------------------------
Summary: The org.jdom module should be removed
Key: WFLY-11326
URL: https://issues.jboss.org/browse/WFLY-11326
Project: WildFly
Issue Type: Task
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 16.0.0.Alpha1
Follow up on WFLY-11325 by removing the module.
I've assigned this to myself instead of just Unassigned to help increase the chances I remember to do it, but once WF 16 starts, if WFLY-11325 was resolved in 15, anyone should feel free to take this and do it.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-11325) The org.jdom module should be deprecated
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-11325?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFLY-11325:
------------------------------------
Summary: The org.jdom module should be deprecated (was: The org.jdom module should be deprecated and later removed)
> The org.jdom module should be deprecated
> ----------------------------------------
>
> Key: WFLY-11325
> URL: https://issues.jboss.org/browse/WFLY-11325
> Project: WildFly
> Issue Type: Bug
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Major
> Fix For: 15.0.0.Alpha1
>
>
> The org.jdom module is jboss.api=unsupported in EAP and is not actually used by WF or added as a dependency by it to deployments. It looks like it probably should have been made private way back in 2012 when it was made 'unsupported' in EAP. The 'unsupported' is inappropriate in WF so it got removed, resulting in it becoming 'public'.
> The only module that depends on org.jdom is org.jaxen. Jaxen's pom declares it as an optional dependency. Here is the production code use of jdom by jaxen:
> {code}
> src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.Attribute;
> src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.CDATA;
> src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.Comment;
> src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.Document;
> src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.Element;
> src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.Namespace;
> src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.ProcessingInstruction;
> src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.Text;
> src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.input.SAXBuilder;
> src/java/main/org/jaxen/jdom/XPathNamespace.java:import org.jdom.Element;
> src/java/main/org/jaxen/jdom/XPathNamespace.java:import org.jdom.Namespace;
> {code}
> DocumentNavigator is nowhere used by WF or its libraries. XPathNamespace is only used by DocumentNavigator. So, our uses of jaxen don't require jdom. That dependency should be optional so galleon can skip provisioning it in optimized installations.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-11325) The org.jdom module should be deprecated
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-11325?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFLY-11325:
------------------------------------
Fix Version/s: 15.0.0.Alpha1
> The org.jdom module should be deprecated
> ----------------------------------------
>
> Key: WFLY-11325
> URL: https://issues.jboss.org/browse/WFLY-11325
> Project: WildFly
> Issue Type: Bug
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Major
> Fix For: 15.0.0.Alpha1
>
>
> The org.jdom module is jboss.api=unsupported in EAP and is not actually used by WF or added as a dependency by it to deployments. It looks like it probably should have been made private way back in 2012 when it was made 'unsupported' in EAP. The 'unsupported' is inappropriate in WF so it got removed, resulting in it becoming 'public'.
> The only module that depends on org.jdom is org.jaxen. Jaxen's pom declares it as an optional dependency. Here is the production code use of jdom by jaxen:
> {code}
> src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.Attribute;
> src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.CDATA;
> src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.Comment;
> src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.Document;
> src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.Element;
> src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.Namespace;
> src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.ProcessingInstruction;
> src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.Text;
> src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.input.SAXBuilder;
> src/java/main/org/jaxen/jdom/XPathNamespace.java:import org.jdom.Element;
> src/java/main/org/jaxen/jdom/XPathNamespace.java:import org.jdom.Namespace;
> {code}
> DocumentNavigator is nowhere used by WF or its libraries. XPathNamespace is only used by DocumentNavigator. So, our uses of jaxen don't require jdom. That dependency should be optional so galleon can skip provisioning it in optimized installations.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-11325) The org.jdom module should be deprecated and later removed
by Brian Stansberry (Jira)
Brian Stansberry created WFLY-11325:
---------------------------------------
Summary: The org.jdom module should be deprecated and later removed
Key: WFLY-11325
URL: https://issues.jboss.org/browse/WFLY-11325
Project: WildFly
Issue Type: Bug
Reporter: Brian Stansberry
Assignee: Brian Stansberry
The org.jdom module is jboss.api=unsupported in EAP and is not actually used by WF or added as a dependency by it to deployments. It looks like it probably should have been made private way back in 2012 when it was made 'unsupported' in EAP. The 'unsupported' is inappropriate in WF so it got removed, resulting in it becoming 'public'.
The only module that depends on org.jdom is org.jaxen. Jaxen's pom declares it as an optional dependency. Here is the production code use of jdom by jaxen:
{code}
src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.Attribute;
src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.CDATA;
src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.Comment;
src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.Document;
src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.Element;
src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.Namespace;
src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.ProcessingInstruction;
src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.Text;
src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.input.SAXBuilder;
src/java/main/org/jaxen/jdom/XPathNamespace.java:import org.jdom.Element;
src/java/main/org/jaxen/jdom/XPathNamespace.java:import org.jdom.Namespace;
{code}
DocumentNavigator is nowhere used by WF or its libraries. XPathNamespace is only used by DocumentNavigator. So, our uses of jaxen don't require jdom. That dependency should be optional so galleon can skip provisioning it in optimized installations.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months