[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:
---------------------------------
Description:
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}
was:
If pooled-connection-factory is defined in messaging-active subsystem like:
{code}
<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}
> @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)
Miroslav Novak created WFWIP-147:
------------------------------------
Summary: @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: Jeff Mesnil
If pooled-connection-factory is defined in messaging-active subsystem like:
{code}
<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 reassigned WFWIP-147:
------------------------------------
Assignee: ehsavoie Hugonnet (was: Jeff Mesnil)
> @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}
> <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] (DROOLS-3289) [DMN Designer] Default Output Value typeRef
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3289?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-3289:
----------------------------------------
[~jomarko] [~tirelli] I've asked https://github.com/kiegroup/kie-wb-common/pull/2256 to set the _default_ {{typeRef}} to {{<Undefined>}}.
This will make every DMN element have a {{null}} {{typeRef}} by default in the XML unless explicitly set by the User. This will mean where we currently have an _erroneous_ {{typeRef}} on some elements (e.g. "output" and "default output entry") it will now be excluded all together and be inherited from its parent element where such is explicitly defined.
> [DMN Designer] Default Output Value typeRef
> -------------------------------------------
>
> Key: DROOLS-3289
> URL: https://issues.jboss.org/browse/DROOLS-3289
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
>
> If the default output value of decision table is set, its {{typeRef}} doesn't respect its parent {{typeRef}}, example below.
> {code:xml}
> <dmn:output id="_8023A5BD-71A4-4C3F-A5B9-B62D5BC34345" name="output-1" typeRef="number">
> <dmn:outputValues id="_C9AEC57C-1F1E-4115-9449-F287F010EA07">
> <dmn:text>456</dmn:text>
> </dmn:outputValues>
> <dmn:defaultOutputEntry id="_36F46818-D5F9-4F58-A758-73B853EC418B" typeRef="string">
> <dmn:text>123</dmn:text>
> </dmn:defaultOutputEntry>
> </dmn:output>
> ...
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3269) [DMN Designer] Context: Default can be any expression type
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3269?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-3269:
----------------------------------------
[~jomarko] OK it makes sense, and the problem is in part that we're setting _everything_ to have a default {{typeRef}} of {{Any}} (well, used to be {{string}}).
I think when https://github.com/kiegroup/kie-wb-common/pull/2256 is merged (with a slight alteration to make the _default_ {{<Undefined>}}) many of these issues will resolve as they'd inherit their type from their parent. IMO I'd like to ask [~dadossan] to amend the foregoing PR to default to {{<Undefined>}} and then re-try these scenarios.
> [DMN Designer] Context: Default can be any expression type
> ----------------------------------------------------------
>
> Key: DROOLS-3269
> URL: https://issues.jboss.org/browse/DROOLS-3269
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Blocker
> Labels: drools-tools
> Attachments: Qclt6jQn.dmn, Screenshot from 2018-11-09 08-16-34.png
>
>
> The "default" box can be any type of expression, specially decision tables and nested contexts.
> Furthermore the "default" box on contexts is optional. We must provide a way for it to be removed. When support for _any_ type of expression we'll be able to have a {{null}} value for the expression so this should fix itself.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3304) [DMN Designer] Marshalling of magnet positions
by Matteo Mortari (Jira)
Matteo Mortari created DROOLS-3304:
--------------------------------------
Summary: [DMN Designer] Marshalling of magnet positions
Key: DROOLS-3304
URL: https://issues.jboss.org/browse/DROOLS-3304
Project: Drools
Issue Type: Bug
Components: DMN Editor
Reporter: Matteo Mortari
Assignee: Matteo Mortari
When attaching connectors to different magnets (other than "centre") re-opening a DMN diagram resets connections to the "centre" magnet. IDK if this is an issue with writing magnet positions to the XML or recreating the connections from the XML.
[~tari_manga] could you please liaise with [~roger600] to understand where the issue is?
h2. PR Acceptance test
In DMN Designer, change magnet position in:
- Source node
-- BKM(/), BKS (/), Decision(/), Input (/)
- Target node
-- BKM(/), BKS(/), Decision (/), Annotation (/)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months