August 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-890) Thread deadlock issue in class ProjectClassLoader.java

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-890?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-890. -------------------------------- Fix Version/s: 6.3.0.Final Resolution: Done I can see how the InternalClassLoader can be accessed without having acquired a lock on the enclosing ProjectClassLoader first and this is indeed wrong. I fixed it with this commit https://github.com/droolsjbpm/drools/commit/183518527 > Thread deadlock issue in class ProjectClassLoader.java > ------------------------------------------------------- > > Key: DROOLS-890 > URL: https://issues.jboss.org/browse/DROOLS-890 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.1.0.Final > Reporter: Vivek Hingorani > Assignee: Mario Fusco > Fix For: 6.3.0.Final > > > In our project , we are using drools6.1.0.Final jars and the rules are deployed in a jar. Another application when trying to use the rules jar is getting thread deadlock problem. Stack trace is > at org.drools.core.common.ProjectClassLoader$InternalTypesClassLoader.loadClass(ProjectClassLoader,java284) > Two threads are in deadlock condition on this thread. I restarted the application and the error is gone but we need to fix this issue so that it is not reproduced later.The class is in drools-core jar -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-927) Upgrade sql-api from 2.0.0.Beta1 to 2.0.0.Final

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFCORE-927?page=com.atlassian.jira.plugin... ] Scott Marlow closed WFCORE-927. ------------------------------- > Upgrade sql-api from 2.0.0.Beta1 to 2.0.0.Final > ----------------------------------------------- > > Key: WFCORE-927 > URL: https://issues.jboss.org/browse/WFCORE-927 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Server > Affects Versions: 2.0.0.Beta4 > Reporter: Fernando Nasser > Assignee: Scott Marlow > Fix For: 2.0.0.Beta5 > > > We have <version.org.jboss.spec.javax.sql.jboss-javax-sql-api_7.0_spec>2.0.0.Beta1 when there is a 2.0.0.Final already. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5049) AMQ Artemis does not support slash character used in activation property of MDB

by Ondřej Chaloupka (JIRA)

[ https://issues.jboss.org/browse/WFLY-5049?page=com.atlassian.jira.plugin.... ] Ondřej Chaloupka commented on WFLY-5049: ---------------------------------------- Hi Jeff, yeap, sorry, it was typo, there are two different queues. MDB consumes from MDBTriggerQueue. Remote server uses default configuration where connection factory {{RemoteConnectionFactory}} is defined and which I expect the MDB server connects through. I'm adding the example of configuration files for you can check. These configuration work perfectly until you use instead of queue name {{MDBTriggerQueue}} name like {{queue/MDBTriggerQueue}}. > AMQ Artemis does not support slash character used in activation property of MDB > ------------------------------------------------------------------------------- > > Key: WFLY-5049 > URL: https://issues.jboss.org/browse/WFLY-5049 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.Alpha6 > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Attachments: ejb-jar.xml, mdb-deployed-standalone-full.xml, remote-activemq-broker-standalone-full.xml > > > When using slash character {{/}} in configuration of artemis messaging subsystem as jms queue name then MDB fails to connect to remote messaging server. > My settings is following - I have a remote messaging server where queue is defined like > {code} > <jms-queue name="queue/crashRecoveryQueue" entries="java:jboss/queue/crashRecoveryQueue"/> > {code} > Then there is a server where MDB is deployed. That server configures connection factory > {code} > <pooled-connection-factory name="messaging-broker-remote" transaction="xa" entries="java:/RemoteJmsXA" connectors="messaging-broker-http-remote"/> > {code} > http connector > {code} > <http-connector name="messaging-broker-http-remote" socket-binding="remote-messaging"> > <param name="http-upgrade-endpoint" value="http-acceptor"/> > </http-connector> > {code} > outbound socket binding > {code} > <outbound-socket-binding name="remote-messaging"> > <remote-destination host="127.0.0.1" port="8280"/> > </outbound-socket-binding> > {code} > and resource reference for ejb subsystem > {code} > <mdb> > <resource-adapter-ref resource-adapter-name="messaging-broker-remote"/> > <bean-instance-pool-ref pool-name="mdb-strict-max-pool"/> > </mdb> > {code} > The MDB uses ejb-jar with activation properties > {code} > <?xml version="1.0" encoding="UTF-8"?> > <ejb-jar id="EJBJar_1060639024453" version="3.0" > xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd" > metadata-complete="false"> > <enterprise-beans> > <message-driven> > <ejb-name>JMSCrashMessageDrivenBean</ejb-name> > <ejb-class>org.jboss.as.test.jbossts.crashrec.jms.mdb.JMSCrashMessageDrivenBean</ejb-class> > <activation-config> > <activation-config-property> > <activation-config-property-name>destination</activation-config-property-name> > <activation-config-property-value>queue/MDBTriggerQueue</activation-config-property-value> > </activation-config-property> > <activation-config-property> > <activation-config-property-name>destinationType</activation-config-property-name> > <activation-config-property-value>javax.jms.Queue</activation-config-property-value> > </activation-config-property> > </activation-config> > </message-driven> > </enterprise-beans> > </ejb-jar> > {code} > The server does not show any warning that the connection was not found, just MDB does not receive any message from the queue. > If I use {{MDBTriggerQueue}} instead of {{queue/MDBTriggerQueue}} the same setup starts working perfectly. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-939) Embedded host controller should set launch type attribute to EMBEDDED

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-939?page=com.atlassian.jira.plugin... ] Ken Wills updated WFCORE-939: ----------------------------- Summary: Embedded host controller should set launch type attribute to EMBEDDED (was: Embedded host controller should set lunch type attribute to EMBEDDED) > Embedded host controller should set launch type attribute to EMBEDDED > --------------------------------------------------------------------- > > Key: WFCORE-939 > URL: https://issues.jboss.org/browse/WFCORE-939 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Domain Management > Affects Versions: 2.0.0.Beta4 > Reporter: Petr Kremensky > Assignee: Ken Wills > > *DomainRootDefinition.java* always set launch type to {noformat}new LaunchTypeHandler(ServerEnvironment.LaunchType.DOMAIN){noformat} even if the host controller process is embedded. > Looking into the LaunchType class, I believe that EMBEDDED value should be used. > {noformat} > /** The manner in which a server can be launched */ > public static enum LaunchType { > /** Launched by a Host Controller in a managed domain */ > DOMAIN(ProcessType.DOMAIN_SERVER), > /** Launched from the command line */ > STANDALONE(ProcessType.STANDALONE_SERVER), > /** Launched by another process in which the server is embedded */ > EMBEDDED(ProcessType.EMBEDDED_SERVER), > ... > {noformat} > \\ > *Additional info:* > {noformat}./standalone.sh > launch-type STANDALONE > {noformat} > {noformat}./domain.sh > launch-type DOMAIN > {noformat} > {noformat}[disconnected /] embed-server > launch-type EMBEDDED > {noformat} > {noformat}[disconnected /] embed-host-controller > launch-type DOMAIN > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5049) AMQ Artemis does not support slash character used in activation property of MDB

by Ondřej Chaloupka (JIRA)

[ https://issues.jboss.org/browse/WFLY-5049?page=com.atlassian.jira.plugin.... ] Ondřej Chaloupka updated WFLY-5049: ----------------------------------- Attachment: ejb-jar.xml Settings of activation properties for ejb where MDB resides > AMQ Artemis does not support slash character used in activation property of MDB > ------------------------------------------------------------------------------- > > Key: WFLY-5049 > URL: https://issues.jboss.org/browse/WFLY-5049 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.Alpha6 > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Attachments: ejb-jar.xml, mdb-deployed-standalone-full.xml, remote-activemq-broker-standalone-full.xml > > > When using slash character {{/}} in configuration of artemis messaging subsystem as jms queue name then MDB fails to connect to remote messaging server. > My settings is following - I have a remote messaging server where queue is defined like > {code} > <jms-queue name="queue/crashRecoveryQueue" entries="java:jboss/queue/crashRecoveryQueue"/> > {code} > Then there is a server where MDB is deployed. That server configures connection factory > {code} > <pooled-connection-factory name="messaging-broker-remote" transaction="xa" entries="java:/RemoteJmsXA" connectors="messaging-broker-http-remote"/> > {code} > http connector > {code} > <http-connector name="messaging-broker-http-remote" socket-binding="remote-messaging"> > <param name="http-upgrade-endpoint" value="http-acceptor"/> > </http-connector> > {code} > outbound socket binding > {code} > <outbound-socket-binding name="remote-messaging"> > <remote-destination host="127.0.0.1" port="8280"/> > </outbound-socket-binding> > {code} > and resource reference for ejb subsystem > {code} > <mdb> > <resource-adapter-ref resource-adapter-name="messaging-broker-remote"/> > <bean-instance-pool-ref pool-name="mdb-strict-max-pool"/> > </mdb> > {code} > The MDB uses ejb-jar with activation properties > {code} > <?xml version="1.0" encoding="UTF-8"?> > <ejb-jar id="EJBJar_1060639024453" version="3.0" > xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd" > metadata-complete="false"> > <enterprise-beans> > <message-driven> > <ejb-name>JMSCrashMessageDrivenBean</ejb-name> > <ejb-class>org.jboss.as.test.jbossts.crashrec.jms.mdb.JMSCrashMessageDrivenBean</ejb-class> > <activation-config> > <activation-config-property> > <activation-config-property-name>destination</activation-config-property-name> > <activation-config-property-value>queue/MDBTriggerQueue</activation-config-property-value> > </activation-config-property> > <activation-config-property> > <activation-config-property-name>destinationType</activation-config-property-name> > <activation-config-property-value>javax.jms.Queue</activation-config-property-value> > </activation-config-property> > </activation-config> > </message-driven> > </enterprise-beans> > </ejb-jar> > {code} > The server does not show any warning that the connection was not found, just MDB does not receive any message from the queue. > If I use {{MDBTriggerQueue}} instead of {{queue/MDBTriggerQueue}} the same setup starts working perfectly. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5049) AMQ Artemis does not support slash character used in activation property of MDB

by Ondřej Chaloupka (JIRA)

[ https://issues.jboss.org/browse/WFLY-5049?page=com.atlassian.jira.plugin.... ] Ondřej Chaloupka updated WFLY-5049: ----------------------------------- Attachment: mdb-deployed-standalone-full.xml remote-activemq-broker-standalone-full.xml Adding server configuration files where {{mdb-deployed-standalone-full.xml}} presents the test server where MDB runs. There is no queues configured but there is defined connection factory which points to remote eap server which is configured by {{remote-activemq-broker-standalone-full.xml}} and where queues are deployed. > AMQ Artemis does not support slash character used in activation property of MDB > ------------------------------------------------------------------------------- > > Key: WFLY-5049 > URL: https://issues.jboss.org/browse/WFLY-5049 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.Alpha6 > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Attachments: mdb-deployed-standalone-full.xml, remote-activemq-broker-standalone-full.xml > > > When using slash character {{/}} in configuration of artemis messaging subsystem as jms queue name then MDB fails to connect to remote messaging server. > My settings is following - I have a remote messaging server where queue is defined like > {code} > <jms-queue name="queue/crashRecoveryQueue" entries="java:jboss/queue/crashRecoveryQueue"/> > {code} > Then there is a server where MDB is deployed. That server configures connection factory > {code} > <pooled-connection-factory name="messaging-broker-remote" transaction="xa" entries="java:/RemoteJmsXA" connectors="messaging-broker-http-remote"/> > {code} > http connector > {code} > <http-connector name="messaging-broker-http-remote" socket-binding="remote-messaging"> > <param name="http-upgrade-endpoint" value="http-acceptor"/> > </http-connector> > {code} > outbound socket binding > {code} > <outbound-socket-binding name="remote-messaging"> > <remote-destination host="127.0.0.1" port="8280"/> > </outbound-socket-binding> > {code} > and resource reference for ejb subsystem > {code} > <mdb> > <resource-adapter-ref resource-adapter-name="messaging-broker-remote"/> > <bean-instance-pool-ref pool-name="mdb-strict-max-pool"/> > </mdb> > {code} > The MDB uses ejb-jar with activation properties > {code} > <?xml version="1.0" encoding="UTF-8"?> > <ejb-jar id="EJBJar_1060639024453" version="3.0" > xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd" > metadata-complete="false"> > <enterprise-beans> > <message-driven> > <ejb-name>JMSCrashMessageDrivenBean</ejb-name> > <ejb-class>org.jboss.as.test.jbossts.crashrec.jms.mdb.JMSCrashMessageDrivenBean</ejb-class> > <activation-config> > <activation-config-property> > <activation-config-property-name>destination</activation-config-property-name> > <activation-config-property-value>queue/MDBTriggerQueue</activation-config-property-value> > </activation-config-property> > <activation-config-property> > <activation-config-property-name>destinationType</activation-config-property-name> > <activation-config-property-value>javax.jms.Queue</activation-config-property-value> > </activation-config-property> > </activation-config> > </message-driven> > </enterprise-beans> > </ejb-jar> > {code} > The server does not show any warning that the connection was not found, just MDB does not receive any message from the queue. > If I use {{MDBTriggerQueue}} instead of {{queue/MDBTriggerQueue}} the same setup starts working perfectly. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-898) Rename drools-osgi* modules to kie-osgi*

by Petr Široký (JIRA)

Petr Široký created DROOLS-898: ---------------------------------- Summary: Rename drools-osgi* modules to kie-osgi* Key: DROOLS-898 URL: https://issues.jboss.org/browse/DROOLS-898 Project: Drools Issue Type: Task Reporter: Petr Široký Assignee: Petr Široký The {{drools-osgi}} module no longer contains only Drools specific integration. For quite some time there is also jBPM related code and recently also OptaPlanner. We should rename the module to {{kie-osgi}} to be consistent with the other components (e.g. {{kie-maven-plugin}}, {{kie-server}}, etc) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-898) Rename drools-osgi* modules to kie-osgi*

by Petr Široký (JIRA)

[ https://issues.jboss.org/browse/DROOLS-898?page=com.atlassian.jira.plugin... ] Petr Široký updated DROOLS-898: ------------------------------- Affects Version/s: 6.3.0.CR2 > Rename drools-osgi* modules to kie-osgi* > ---------------------------------------- > > Key: DROOLS-898 > URL: https://issues.jboss.org/browse/DROOLS-898 > Project: Drools > Issue Type: Task > Affects Versions: 6.3.0.CR2 > Reporter: Petr Široký > Assignee: Petr Široký > > The {{drools-osgi}} module no longer contains only Drools specific integration. For quite some time there is also jBPM related code and recently also OptaPlanner. We should rename the module to {{kie-osgi}} to be consistent with the other components (e.g. {{kie-maven-plugin}}, {{kie-server}}, etc) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-363) ManagementResourceRegistration.getOverrideModel never returns null

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-363?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-363: ------------------------------------ Fix Version/s: 3.0.0.Alpha1 (was: 2.0.0.CR1) > ManagementResourceRegistration.getOverrideModel never returns null > ------------------------------------------------------------------ > > Key: WFCORE-363 > URL: https://issues.jboss.org/browse/WFCORE-363 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 3.0.0.Alpha1 > > > ManagementResourceRegistration.getOverrideModel ends up returning the wildcard registration if there is no override registration. This isn't correct. > The fix isn't trivial because fixing it results in nasty failures in the smoke tests. From looking at the uses of this method (which all involve a null check) I assume there are some bugs in the code that calls this method that get exposed once it does what it should. > This bug is the cause of the initial failure of my WFLY-2880 fix. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-273) ServerInventory#reconnectServer should take auto-start into account

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-273?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-273: ------------------------------------ Fix Version/s: 3.0.0.Alpha1 (was: 2.0.0.CR1) > ServerInventory#reconnectServer should take auto-start into account > ------------------------------------------------------------------- > > Key: WFCORE-273 > URL: https://issues.jboss.org/browse/WFCORE-273 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Emanuel Muckenhuber > Assignee: Ken Wills > Fix For: 3.0.0.Alpha1 > > > When reconnecting to stopped (but not removed) servers, the ServerInventory should take the auto-start property into account. Otherwise the process will just get removed, however started with the next :reload of the HC. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2015