[JBoss JIRA] (WFLY-9746) Revert JGroups capability reference to ChannelFactory
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-9746?page=com.atlassian.jira.plugin.... ]
Paul Ferraro updated WFLY-9746:
-------------------------------
Description:
There is regression If Artemis is configured to JGroups tcp stack to form cluster then server does not start and fail with:
{code}
13:24:02,424 INFO [org.jboss.ws.common.management] (MSC service thread 1-8) JBWS022052: Starting JBossWS 5.1.9.Final (Apache CXF 3.1.12)
13:24:02,428 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "messaging-activemq"),
("server" => "default")
]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => [
"jboss.messaging-activemq.default",
"org.wildfly.clustering.command-dispatcher-factory.tcp"
],
"WFLYCTL0180: Services with missing/unavailable dependencies" => [
"jboss.messaging-activemq.default.jms.manager is missing [jboss.messaging-activemq.default]",
"jboss.messaging-activemq.default is missing [org.wildfly.clustering.command-dispatcher-factory.tcp]"
]
}
13:24:02,438 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.messaging-activemq.default (unavailable) dependents: [service jboss.messaging-activemq.default.jms.manager]
service org.wildfly.clustering.command-dispatcher-factory.tcp (missing) dependents: [service jboss.messaging-activemq.default]
13:24:02,485 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
13:24:02,487 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:11990/management
13:24:02,487 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:11990
{code}
Configuration of jgroups and messaging-activemq subsystem:
{code}
<subsystem xmlns="urn:jboss:domain:jgroups:5.0">
<channels default="ee">
<channel name="ee" stack="udp" cluster="ejb"/>
</channels>
...
<stack name="tcp">
<transport type="TCP" socket-binding="jgroups-tcp"/>
<protocol type="org.jgroups.protocols.TCPPING">
<property name="port_range">
10
</property>
<property name="num_initial_members">
1
</property>
<property name="initial_hosts">
127.0.0.1[9600]
</property>
<property name="timeout">
3000
</property>
</protocol>
<protocol type="MERGE3"/>
<protocol type="FD_SOCK"/>
<protocol type="FD"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="pbcast.NAKACK"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="pbcast.GMS"/>
<protocol type="UFC"/>
<protocol type="MFC"/>
<protocol type="FRAG2"/>
<protocol type="RSVP"/>
</stack>
</stacks>
</subsystem>
....
<subsystem xmlns="urn:jboss:domain:messaging-activemq:2.0">
<server name="default" persistence-enabled="true" id-cache-size="200000">
<broadcast-group name="bg-group1" jgroups-stack="tcp" jgroups-channel="activemq-cluster" broadcast-period="2000" connectors="connector"/>
<discovery-group name="dg-group1" jgroups-stack="tcp" jgroups-channel="activemq-cluster" refresh-timeout="10000"/>
<cluster-connection name="my-cluster" address="jms" connector-name="connector" check-period="30000" connection-ttl="60000" call-timeout="30000" discovery-group="dg-group1"/>
...
</server>
</subsystem>
{code}
Attaching the whole config: standalone-full-ha.xml
was:
There is regression If Artemis is configured to JGroups tcp stack to form cluster then server does not start and fail with:
{code}
13:24:02,424 INFO [org.jboss.ws.common.management] (MSC service thread 1-8) JBWS022052: Starting JBossWS 5.1.9.Final (Apache CXF 3.1.12)
13:24:02,428 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "messaging-activemq"),
("server" => "default")
]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => [
"jboss.messaging-activemq.default",
"org.wildfly.clustering.command-dispatcher-factory.tcp"
],
"WFLYCTL0180: Services with missing/unavailable dependencies" => [
"jboss.messaging-activemq.default.jms.manager is missing [jboss.messaging-activemq.default]",
"jboss.messaging-activemq.default is missing [org.wildfly.clustering.command-dispatcher-factory.tcp]"
]
}
13:24:02,438 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.messaging-activemq.default (unavailable) dependents: [service jboss.messaging-activemq.default.jms.manager]
service org.wildfly.clustering.command-dispatcher-factory.tcp (missing) dependents: [service jboss.messaging-activemq.default]
13:24:02,485 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
13:24:02,487 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:11990/management
13:24:02,487 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:11990
{code}
Configuration of jgroups and messaging-activemq subsystem:
{code}
<subsystem xmlns="urn:jboss:domain:jgroups:5.0">
<channels default="ee">
<channel name="ee" stack="udp" cluster="ejb"/>
</channels>
...
<stack name="tcp">
<transport type="TCP" socket-binding="jgroups-tcp"/>
<protocol type="org.jgroups.protocols.TCPPING">
<property name="port_range">
10
</property>
<property name="num_initial_members">
1
</property>
<property name="initial_hosts">
127.0.0.1[9600]
</property>
<property name="timeout">
3000
</property>
</protocol>
<protocol type="MERGE3"/>
<protocol type="FD_SOCK"/>
<protocol type="FD"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="pbcast.NAKACK"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="pbcast.GMS"/>
<protocol type="UFC"/>
<protocol type="MFC"/>
<protocol type="FRAG2"/>
<protocol type="RSVP"/>
</stack>
</stacks>
</subsystem>
....
<subsystem xmlns="urn:jboss:domain:messaging-activemq:3.0">
<server name="default" persistence-enabled="true" id-cache-size="200000">
<broadcast-group name="bg-group1" jgroups-stack="tcp" jgroups-channel="udp" broadcast-period="2000" connectors="connector"/>
<discovery-group name="dg-group1" jgroups-stack="tcp" jgroups-channel="udp" refresh-timeout="10000"/>
<cluster-connection name="my-cluster" address="jms" connector-name="connector" check-period="30000" connection-ttl="60000" call-timeout="30000" discovery-group="dg-group1"/>
...
</server>
</subsystem>
{code}
Attaching the whole config: standalone-full-ha.xml
> Revert JGroups capability reference to ChannelFactory
> -----------------------------------------------------
>
> Key: WFLY-9746
> URL: https://issues.jboss.org/browse/WFLY-9746
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, JMS
> Affects Versions: 12.0.0.Alpha1
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Blocker
>
> There is regression If Artemis is configured to JGroups tcp stack to form cluster then server does not start and fail with:
> {code}
> 13:24:02,424 INFO [org.jboss.ws.common.management] (MSC service thread 1-8) JBWS022052: Starting JBossWS 5.1.9.Final (Apache CXF 3.1.12)
> 13:24:02,428 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "messaging-activemq"),
> ("server" => "default")
> ]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => [
> "jboss.messaging-activemq.default",
> "org.wildfly.clustering.command-dispatcher-factory.tcp"
> ],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => [
> "jboss.messaging-activemq.default.jms.manager is missing [jboss.messaging-activemq.default]",
> "jboss.messaging-activemq.default is missing [org.wildfly.clustering.command-dispatcher-factory.tcp]"
> ]
> }
> 13:24:02,438 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service jboss.messaging-activemq.default (unavailable) dependents: [service jboss.messaging-activemq.default.jms.manager]
> service org.wildfly.clustering.command-dispatcher-factory.tcp (missing) dependents: [service jboss.messaging-activemq.default]
> 13:24:02,485 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
> 13:24:02,487 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:11990/management
> 13:24:02,487 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:11990
> {code}
> Configuration of jgroups and messaging-activemq subsystem:
> {code}
> <subsystem xmlns="urn:jboss:domain:jgroups:5.0">
> <channels default="ee">
> <channel name="ee" stack="udp" cluster="ejb"/>
> </channels>
> ...
> <stack name="tcp">
> <transport type="TCP" socket-binding="jgroups-tcp"/>
> <protocol type="org.jgroups.protocols.TCPPING">
> <property name="port_range">
> 10
> </property>
> <property name="num_initial_members">
> 1
> </property>
> <property name="initial_hosts">
> 127.0.0.1[9600]
> </property>
> <property name="timeout">
> 3000
> </property>
> </protocol>
> <protocol type="MERGE3"/>
> <protocol type="FD_SOCK"/>
> <protocol type="FD"/>
> <protocol type="VERIFY_SUSPECT"/>
> <protocol type="pbcast.NAKACK"/>
> <protocol type="UNICAST3"/>
> <protocol type="pbcast.STABLE"/>
> <protocol type="pbcast.GMS"/>
> <protocol type="UFC"/>
> <protocol type="MFC"/>
> <protocol type="FRAG2"/>
> <protocol type="RSVP"/>
> </stack>
> </stacks>
> </subsystem>
> ....
> <subsystem xmlns="urn:jboss:domain:messaging-activemq:2.0">
> <server name="default" persistence-enabled="true" id-cache-size="200000">
> <broadcast-group name="bg-group1" jgroups-stack="tcp" jgroups-channel="activemq-cluster" broadcast-period="2000" connectors="connector"/>
> <discovery-group name="dg-group1" jgroups-stack="tcp" jgroups-channel="activemq-cluster" refresh-timeout="10000"/>
> <cluster-connection name="my-cluster" address="jms" connector-name="connector" check-period="30000" connection-ttl="60000" call-timeout="30000" discovery-group="dg-group1"/>
> ...
> </server>
> </subsystem>
> {code}
> Attaching the whole config: standalone-full-ha.xml
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9746) Revert JGroups capability reference to ChannelFactory
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-9746?page=com.atlassian.jira.plugin.... ]
Paul Ferraro commented on WFLY-9746:
------------------------------------
You've specified configuration from the 2.0 schema, but changed the schema version to 3.0. If you used the configuration as specified, it should work. If you want to use the 3.0 schema, you must use the correct attribute names.
e.g. for 2.0
<discovery-group name="foo" jgroups-stack="udp" jgroups-channel="activemq-cluster"/>
e.g. for 3.0
<discovery-group name="foo" jgroups-stack="udp" jgroups-cluster="activemq-cluster"/>
or
<discovery-group name="foo" jgroups-channel="ee" jgroups-cluster="activemq-cluster"/>
> Revert JGroups capability reference to ChannelFactory
> -----------------------------------------------------
>
> Key: WFLY-9746
> URL: https://issues.jboss.org/browse/WFLY-9746
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, JMS
> Affects Versions: 12.0.0.Alpha1
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Blocker
>
> There is regression If Artemis is configured to JGroups tcp stack to form cluster then server does not start and fail with:
> {code}
> 13:24:02,424 INFO [org.jboss.ws.common.management] (MSC service thread 1-8) JBWS022052: Starting JBossWS 5.1.9.Final (Apache CXF 3.1.12)
> 13:24:02,428 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "messaging-activemq"),
> ("server" => "default")
> ]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => [
> "jboss.messaging-activemq.default",
> "org.wildfly.clustering.command-dispatcher-factory.tcp"
> ],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => [
> "jboss.messaging-activemq.default.jms.manager is missing [jboss.messaging-activemq.default]",
> "jboss.messaging-activemq.default is missing [org.wildfly.clustering.command-dispatcher-factory.tcp]"
> ]
> }
> 13:24:02,438 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service jboss.messaging-activemq.default (unavailable) dependents: [service jboss.messaging-activemq.default.jms.manager]
> service org.wildfly.clustering.command-dispatcher-factory.tcp (missing) dependents: [service jboss.messaging-activemq.default]
> 13:24:02,485 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
> 13:24:02,487 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:11990/management
> 13:24:02,487 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:11990
> {code}
> Configuration of jgroups and messaging-activemq subsystem:
> {code}
> <subsystem xmlns="urn:jboss:domain:jgroups:5.0">
> <channels default="ee">
> <channel name="ee" stack="udp" cluster="ejb"/>
> </channels>
> ...
> <stack name="tcp">
> <transport type="TCP" socket-binding="jgroups-tcp"/>
> <protocol type="org.jgroups.protocols.TCPPING">
> <property name="port_range">
> 10
> </property>
> <property name="num_initial_members">
> 1
> </property>
> <property name="initial_hosts">
> 127.0.0.1[9600]
> </property>
> <property name="timeout">
> 3000
> </property>
> </protocol>
> <protocol type="MERGE3"/>
> <protocol type="FD_SOCK"/>
> <protocol type="FD"/>
> <protocol type="VERIFY_SUSPECT"/>
> <protocol type="pbcast.NAKACK"/>
> <protocol type="UNICAST3"/>
> <protocol type="pbcast.STABLE"/>
> <protocol type="pbcast.GMS"/>
> <protocol type="UFC"/>
> <protocol type="MFC"/>
> <protocol type="FRAG2"/>
> <protocol type="RSVP"/>
> </stack>
> </stacks>
> </subsystem>
> ....
> <subsystem xmlns="urn:jboss:domain:messaging-activemq:3.0">
> <server name="default" persistence-enabled="true" id-cache-size="200000">
> <broadcast-group name="bg-group1" jgroups-stack="tcp" jgroups-channel="udp" broadcast-period="2000" connectors="connector"/>
> <discovery-group name="dg-group1" jgroups-stack="tcp" jgroups-channel="udp" refresh-timeout="10000"/>
> <cluster-connection name="my-cluster" address="jms" connector-name="connector" check-period="30000" connection-ttl="60000" call-timeout="30000" discovery-group="dg-group1"/>
> ...
> </server>
> </subsystem>
> {code}
> Attaching the whole config: standalone-full-ha.xml
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (DROOLS-2323) [Guided Rule Editor] Field Value Tooltips are not well readable
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2323?page=com.atlassian.jira.plugi... ]
Jozef Marko moved RHDM-393 to DROOLS-2323:
------------------------------------------
Project: Drools (was: Red Hat Decision Manager)
Key: DROOLS-2323 (was: RHDM-393)
Workflow: GIT Pull Request workflow (was: CDW with docs v1)
Docs QE Status: NEW
Component/s: Guided Rule Editor
(was: Decision Central)
Affects Version/s: 7.6.0.Final
(was: 7.0.0)
QE Status: NEW
> [Guided Rule Editor] Field Value Tooltips are not well readable
> ---------------------------------------------------------------
>
> Key: DROOLS-2323
> URL: https://issues.jboss.org/browse/DROOLS-2323
> Project: Drools
> Issue Type: Bug
> Components: Guided Rule Editor
> Affects Versions: 7.6.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Optional
> Fix For: 7.7.0.Final
>
> Attachments: Incorrect template key help.png, Screen Shot 2018-02-01 at 10.37.02 AM.png, Screenshot from 2018-02-15 00-21-59.png
>
>
> Guided Rule Editor and its field value tooltips are not well readable for the user due to the amount of text in the tooltip. The tooltips should be updated in the following way:
> - From
> -- !Incorrect template key help.png|thumbnail!
> - To
> -- !Screen Shot 2018-02-01 at 10.37.02 AM.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (DROOLS-2323) [Guided Rule Editor] Field Value Tooltips are not well readable
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2323?page=com.atlassian.jira.plugi... ]
Jozef Marko reassigned DROOLS-2323:
-----------------------------------
Assignee: Jozef Marko (was: Michael Anstis)
> [Guided Rule Editor] Field Value Tooltips are not well readable
> ---------------------------------------------------------------
>
> Key: DROOLS-2323
> URL: https://issues.jboss.org/browse/DROOLS-2323
> Project: Drools
> Issue Type: Bug
> Components: Guided Rule Editor
> Affects Versions: 7.6.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Priority: Optional
> Fix For: 7.7.0.Final
>
> Attachments: Incorrect template key help.png, Screen Shot 2018-02-01 at 10.37.02 AM.png, Screenshot from 2018-02-15 00-21-59.png
>
>
> Guided Rule Editor and its field value tooltips are not well readable for the user due to the amount of text in the tooltip. The tooltips should be updated in the following way:
> - From
> -- !Incorrect template key help.png|thumbnail!
> - To
> -- !Screen Shot 2018-02-01 at 10.37.02 AM.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (DROOLS-2323) [Guided Rule Editor] Field Value Tooltips are not well readable
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2323?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2323:
--------------------------------
Fix Version/s: 7.7.0.Final
> [Guided Rule Editor] Field Value Tooltips are not well readable
> ---------------------------------------------------------------
>
> Key: DROOLS-2323
> URL: https://issues.jboss.org/browse/DROOLS-2323
> Project: Drools
> Issue Type: Bug
> Components: Guided Rule Editor
> Affects Versions: 7.6.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Priority: Optional
> Fix For: 7.7.0.Final
>
> Attachments: Incorrect template key help.png, Screen Shot 2018-02-01 at 10.37.02 AM.png, Screenshot from 2018-02-15 00-21-59.png
>
>
> Guided Rule Editor and its field value tooltips are not well readable for the user due to the amount of text in the tooltip. The tooltips should be updated in the following way:
> - From
> -- !Incorrect template key help.png|thumbnail!
> - To
> -- !Screen Shot 2018-02-01 at 10.37.02 AM.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFCORE-3612) CDI service loader problems
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3612?page=com.atlassian.jira.plugi... ]
Kabir Khan deleted WFCORE-3612:
-------------------------------
> CDI service loader problems
> ---------------------------
>
> Key: WFCORE-3612
> URL: https://issues.jboss.org/browse/WFCORE-3612
> Project: WildFly Core
> Issue Type: Bug
> Reporter: Kabir Khan
> Assignee: David Lloyd
> Priority: Blocker
>
> Within WildFly Swarm we need the ability to override the `javax.ws.rs.client.ClientBuilder` service file for a deployment to provide custom handling for implementing Eclipse MicroProfile.
> With a service file present in the deployment, the existing RESTEasy service file is always found first because the deployment module is added as a dependency after other non local dependencies. See https://github.com/wildfly/wildfly-core/blob/master/server/src/main/java/...
> After discussing with [~dmlloyd] on IRC, he agreed this was a bug and a better solution was for the deployment's dependency to always be first if `isLocalLast()` is false, and instead remove any spec packages that might be present on the deployment path instead.
> He explained the purpose of this ordering was to prevent a user deploying `javax.servlet.api` and breaking things, but it appears this can be achieved by alternative methods.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFCORE-3612) CDI service loader problems
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3612?page=com.atlassian.jira.plugi... ]
Kabir Khan updated WFCORE-3612:
-------------------------------
Summary: CDI service loader problems (was: Module dependency order for a deployment is wrong)
> CDI service loader problems
> ---------------------------
>
> Key: WFCORE-3612
> URL: https://issues.jboss.org/browse/WFCORE-3612
> Project: WildFly Core
> Issue Type: Bug
> Affects Versions: 3.0.8.Final
> Reporter: Ken Finnigan
> Assignee: David Lloyd
> Priority: Blocker
> Fix For: 4.0.0.Alpha10, 3.1.0.Final
>
>
> Within WildFly Swarm we need the ability to override the `javax.ws.rs.client.ClientBuilder` service file for a deployment to provide custom handling for implementing Eclipse MicroProfile.
> With a service file present in the deployment, the existing RESTEasy service file is always found first because the deployment module is added as a dependency after other non local dependencies. See https://github.com/wildfly/wildfly-core/blob/master/server/src/main/java/...
> After discussing with [~dmlloyd] on IRC, he agreed this was a bug and a better solution was for the deployment's dependency to always be first if `isLocalLast()` is false, and instead remove any spec packages that might be present on the deployment path instead.
> He explained the purpose of this ordering was to prevent a user deploying `javax.servlet.api` and breaking things, but it appears this can be achieved by alternative methods.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months