[JBoss JIRA] (WFLY-1402) Too Many Dependencies
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-1402?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-1402:
-----------------------------------------------
Ivo Studensky <istudens(a)redhat.com> changed the Status of [bug 1138111|https://bugzilla.redhat.com/show_bug.cgi?id=1138111] from POST to MODIFIED
> Too Many Dependencies
> ---------------------
>
> Key: WFLY-1402
> URL: https://issues.jboss.org/browse/WFLY-1402
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 8.0.0.Alpha1
> Environment: W7 64 bit
> Reporter: Michael McGovern
> Assignee: Stuart Douglas
> Fix For: 8.0.0.Alpha2
>
>
> Large app ~ 1000 SLSB gets
> Caused by: java.lang.IllegalArgumentException: Too many dependencies specified (max is 16383)
> at org.jboss.msc.service.ServiceBuilderImpl.doAddDependency(ServiceBuilderImpl.java:216) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
> at org.jboss.msc.service.ServiceBuilderImpl.addDependenciesNoCheck(ServiceBuilderImpl.java:158) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
> at org.jboss.msc.service.ServiceBuilderImpl.addDependencies(ServiceBuilderImpl.java:152) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
> at org.jboss.msc.service.ServiceBuilderImpl.addDependencies(ServiceBuilderImpl.java:142) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
> at org.jboss.as.naming.deployment.JndiNamingDependencyProcessor.deploy(JndiNamingDependencyProcessor.java:59)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.0.0.Alpha1.jar:8.0.0.Alpha1]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (WFCORE-156) Defer the WFLY-184 validation until service start
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFCORE-156?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on WFCORE-156:
------------------------------------------------
Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 1149612|https://bugzilla.redhat.com/show_bug.cgi?id=1149612] from NEW to ASSIGNED
> Defer the WFLY-184 validation until service start
> -------------------------------------------------
>
> Key: WFCORE-156
> URL: https://issues.jboss.org/browse/WFCORE-156
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
>
> The WFLY-184 fix rejects the combination of any-ipv6-address and java.net.preferIPv4Stack=true in Stage.RUNTIME, but does so during service installation rather than in service start. The effect of this is failures occur even if the interface resource isn't being used; e.g. on a host controller.
> This also leads to inconsistent behavior between "add" and "write-attribute", as the write-attribute handler doesn't install the service, and thus doesn't fail. It just sets reload-required.
> Fix is to move the check into NetworkInterfaceService.start() and to make those services ON_DEMAND so the check won't occur until the interface is actually needed.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (WFCORE-156) Defer the WFLY-184 validation until service start
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFCORE-156?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated WFCORE-156:
-------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1149612
> Defer the WFLY-184 validation until service start
> -------------------------------------------------
>
> Key: WFCORE-156
> URL: https://issues.jboss.org/browse/WFCORE-156
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
>
> The WFLY-184 fix rejects the combination of any-ipv6-address and java.net.preferIPv4Stack=true in Stage.RUNTIME, but does so during service installation rather than in service start. The effect of this is failures occur even if the interface resource isn't being used; e.g. on a host controller.
> This also leads to inconsistent behavior between "add" and "write-attribute", as the write-attribute handler doesn't install the service, and thus doesn't fail. It just sets reload-required.
> Fix is to move the check into NetworkInterfaceService.start() and to make those services ON_DEMAND so the check won't occur until the interface is actually needed.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (WFCORE-156) Defer the WFLY-184 validation until service start
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-156:
---------------------------------------
Summary: Defer the WFLY-184 validation until service start
Key: WFCORE-156
URL: https://issues.jboss.org/browse/WFCORE-156
Project: WildFly Core
Issue Type: Enhancement
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
The WFLY-184 fix rejects the combination of any-ipv6-address and java.net.preferIPv4Stack=true in Stage.RUNTIME, but does so during service installation rather than in service start. The effect of this is failures occur even if the interface resource isn't being used; e.g. on a host controller.
This also leads to inconsistent behavior between "add" and "write-attribute", as the write-attribute handler doesn't install the service, and thus doesn't fail. It just sets reload-required.
Fix is to move the check into NetworkInterfaceService.start() and to make those services ON_DEMAND so the check won't occur until the interface is actually needed.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (ELY-95) Password types should generate a salt if none is given
by David Lloyd (JIRA)
David Lloyd created ELY-95:
------------------------------
Summary: Password types should generate a salt if none is given
Key: ELY-95
URL: https://issues.jboss.org/browse/ELY-95
Project: WildFly Elytron
Issue Type: Enhancement
Components: Password Types
Reporter: David Lloyd
Password types such as {{crypt-md5}} should be able to generate a password from a {{ClearPasswordSpec}} by generating a simple random salt.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (WFLY-3943) There is no testing of the messaging subsystem integration with the JGroups subsystem
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-3943?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-3943:
-----------------------------------
Description:
HornetQServerAdd and HornetQServerService have integration with the JGroups subsystem in order to add a dependency on a ChannelFactory for use with broadcast and discovery groups. But it seems there is no testing of this integration.
At the time I filed this it was broken, due to WFLY-3944, since fixed.
This JIRA is about the fact lack of testing that would have caught the WFLY-3944 bug. Also, https://github.com/wildfly/wildfly/pull/6725 passed the testsuite with a code change that was binary incompatible with the version of HQ that was integrated at the time.
was:
HornetQServerAdd and HornetQServerService have integration with the JGroups subsystem in order to add a dependency on a ChannelFactory for use with broadcast and discovery groups. But it seems there is no testing of this integration.
Looks like it's currently broken. That problem is likely a clustering bug, as there was a recent major change in this area, and this works in the 6.x branch.
This JIRA is about the fact lack of testing that would have caught the bug. Also, https://github.com/wildfly/wildfly/pull/6725 passed the testsuite with a code change that was binary incompatible with the version of HQ that was integrated at the time.
I'll file a separate issue for the problem I'm referring to. To reproduce it change the bg-group1 element in standalone-full-ha.xml to replace the socket-binding element with the following:
{code}
<jgroups-stack>udp</jgroups-stack>
<jgroups-channel>hq-bg</jgroups-channel>
<!--<socket-binding>messaging-group</socket-binding>-->
{code}
At boot this appears in the logs:
{code}
10:00:58,707 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "messaging"),
("hornetq-server" => "default")
]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.messaging.default is missing [jboss.jgroups.stack.udp]"]}
10:00:58,930 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.jgroups.stack.udp (missing) dependents: [service jboss.messaging.default]
{code}
> There is no testing of the messaging subsystem integration with the JGroups subsystem
> -------------------------------------------------------------------------------------
>
> Key: WFLY-3943
> URL: https://issues.jboss.org/browse/WFLY-3943
> Project: WildFly
> Issue Type: Task
> Components: JMS
> Reporter: Brian Stansberry
> Assignee: Jeff Mesnil
> Priority: Critical
> Attachments: standalone-full-ha.xml
>
>
> HornetQServerAdd and HornetQServerService have integration with the JGroups subsystem in order to add a dependency on a ChannelFactory for use with broadcast and discovery groups. But it seems there is no testing of this integration.
> At the time I filed this it was broken, due to WFLY-3944, since fixed.
> This JIRA is about the fact lack of testing that would have caught the WFLY-3944 bug. Also, https://github.com/wildfly/wildfly/pull/6725 passed the testsuite with a code change that was binary incompatible with the version of HQ that was integrated at the time.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (WFLY-3943) There is no testing of the messaging subsystem integration with the JGroups subsystem
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-3943?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFLY-3943:
----------------------------------------
Never mind my last comment. WFLY-3944 is resolved, which likely explains why you don't see that specific problem any more.
> There is no testing of the messaging subsystem integration with the JGroups subsystem
> -------------------------------------------------------------------------------------
>
> Key: WFLY-3943
> URL: https://issues.jboss.org/browse/WFLY-3943
> Project: WildFly
> Issue Type: Task
> Components: JMS
> Reporter: Brian Stansberry
> Assignee: Jeff Mesnil
> Priority: Critical
> Attachments: standalone-full-ha.xml
>
>
> HornetQServerAdd and HornetQServerService have integration with the JGroups subsystem in order to add a dependency on a ChannelFactory for use with broadcast and discovery groups. But it seems there is no testing of this integration.
> Looks like it's currently broken. That problem is likely a clustering bug, as there was a recent major change in this area, and this works in the 6.x branch.
> This JIRA is about the fact lack of testing that would have caught the bug. Also, https://github.com/wildfly/wildfly/pull/6725 passed the testsuite with a code change that was binary incompatible with the version of HQ that was integrated at the time.
> I'll file a separate issue for the problem I'm referring to. To reproduce it change the bg-group1 element in standalone-full-ha.xml to replace the socket-binding element with the following:
> {code}
> <jgroups-stack>udp</jgroups-stack>
> <jgroups-channel>hq-bg</jgroups-channel>
> <!--<socket-binding>messaging-group</socket-binding>-->
> {code}
> At boot this appears in the logs:
> {code}
> 10:00:58,707 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "messaging"),
> ("hornetq-server" => "default")
> ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.messaging.default is missing [jboss.jgroups.stack.udp]"]}
> 10:00:58,930 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service jboss.jgroups.stack.udp (missing) dependents: [service jboss.messaging.default]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (WFLY-3943) There is no testing of the messaging subsystem integration with the JGroups subsystem
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-3943?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-3943:
-----------------------------------
Affects Version/s: (was: 9.0.0.Alpha1)
Did you try with a build of the current master? I put 9.0.0.Alpha1 in "Affects Version" but I shouldn't have, as I don't really know if the problem existed there. The clustering change is relatively recent.
> There is no testing of the messaging subsystem integration with the JGroups subsystem
> -------------------------------------------------------------------------------------
>
> Key: WFLY-3943
> URL: https://issues.jboss.org/browse/WFLY-3943
> Project: WildFly
> Issue Type: Task
> Components: JMS
> Reporter: Brian Stansberry
> Assignee: Jeff Mesnil
> Priority: Critical
> Attachments: standalone-full-ha.xml
>
>
> HornetQServerAdd and HornetQServerService have integration with the JGroups subsystem in order to add a dependency on a ChannelFactory for use with broadcast and discovery groups. But it seems there is no testing of this integration.
> Looks like it's currently broken. That problem is likely a clustering bug, as there was a recent major change in this area, and this works in the 6.x branch.
> This JIRA is about the fact lack of testing that would have caught the bug. Also, https://github.com/wildfly/wildfly/pull/6725 passed the testsuite with a code change that was binary incompatible with the version of HQ that was integrated at the time.
> I'll file a separate issue for the problem I'm referring to. To reproduce it change the bg-group1 element in standalone-full-ha.xml to replace the socket-binding element with the following:
> {code}
> <jgroups-stack>udp</jgroups-stack>
> <jgroups-channel>hq-bg</jgroups-channel>
> <!--<socket-binding>messaging-group</socket-binding>-->
> {code}
> At boot this appears in the logs:
> {code}
> 10:00:58,707 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "messaging"),
> ("hornetq-server" => "default")
> ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.messaging.default is missing [jboss.jgroups.stack.udp]"]}
> 10:00:58,930 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service jboss.jgroups.stack.udp (missing) dependents: [service jboss.messaging.default]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years