[JBoss JIRA] (WFLY-5752) Can't rename the "ejb" cache container
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-5752?page=com.atlassian.jira.plugin.... ]
Paul Ferraro commented on WFLY-5752:
------------------------------------
Why would you need to rename the ejb cache container?
> Can't rename the "ejb" cache container
> --------------------------------------
>
> Key: WFLY-5752
> URL: https://issues.jboss.org/browse/WFLY-5752
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, EJB
> Reporter: Ladislav Thon
> Assignee: Paul Ferraro
> Priority: Blocker
> Attachments: tinyRemoteEjb-server-ee7.jar
>
>
> When I rename the {{ejb}} cache container, deploying a simple app that contains an EJB ends with a horrible error message. This is a blocker, because renaming a cache container is required for a 2clusters scenario (standalone client invoking a remote EJB in cluster A, that EJB in turns invokes a remote EJB in cluster B, and forwards the response to the original client).
> More details:
> 1. build current WildFly master and {{unzip .../wildfly/build/target/wildfly-10.0.0.CR5-SNAPSHOT.zip}}
> 2. {{cp tinyRemoteEjb-server-ee7.jar wildfly-10.0.0.CR5-SNAPSHOT/standalone/deployments/}} # the JAR is attached
> 3. change the {{wildfly-10.0.0.CR5-SNAPSHOT/standalone/configuration/standalone-full-ha.xml}} file like this:
> {code}
> <!-- in the "ejb3" subsystem -->
> <passivation-store name="infinispan" cache-container="ejb2" max-size="10000"/>
> <remote cluster="ejb2" connector-ref="http-remoting-connector" thread-pool-name="default"/>
> <!-- in the "infinispan" subsystem -->
> <cache-container name="ejb2" ...>
> {code}
> 4. {{./wildfly-10.0.0.CR5-SNAPSHOT/bin/standalone.sh -c standalone-full-ha.xml}}
> This leads to:
> {code}
> 14:11:22,473 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "tinyRemoteEjb-server-ee7.jar")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => [
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".CdiValidatorFactoryService",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".WeldStartService",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.CREATE",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.JndiBindingsService",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.START",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.VIEW.\"cz.ladicek.tinyRemoteEjb.server.MyBean\".REMOTE",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.WeldInstantiator",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.WeldInterceptorBindingsService",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".deploymentCompleteService",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".jndiDependencyService",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".moduleDeploymentRuntimeInformation",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".moduleDeploymentRuntimeInformationStart",
> "jboss.naming.context.java.app.tinyRemoteEjb-server-ee7.tinyRemoteEjb-server-ee7.MyBeanImpl",
> "jboss.naming.context.java.app.tinyRemoteEjb-server-ee7.tinyRemoteEjb-server-ee7.\"MyBeanImpl!cz.ladicek.tinyRemoteEjb.server.MyBean\"",
> "jboss.naming.context.java.global.tinyRemoteEjb-server-ee7.MyBeanImpl",
> "jboss.naming.context.java.global.tinyRemoteEjb-server-ee7.\"MyBeanImpl!cz.ladicek.tinyRemoteEjb.server.MyBean\"",
> "jboss.naming.context.java.module.tinyRemoteEjb-server-ee7.tinyRemoteEjb-server-ee7.MyBeanImpl",
> "jboss.naming.context.java.module.tinyRemoteEjb-server-ee7.tinyRemoteEjb-server-ee7.\"MyBeanImpl!cz.ladicek.tinyRemoteEjb.server.MyBean\""
> ],
> "Services that may be the cause:" => ["jboss.clustering.registry.ejb2.client-mappings"]
> }}
> 14:11:22,476 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "ejb3"),
> ("service" => "remote")
> ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.ejb.remoting.connector.client-mappings.installer is missing [jboss.clustering.registry.ejb2.client-mappings]"]}
> {code}
> This works perfectly fine in 10.0.0.CR4, so I did a {{git bisect}} and traced the problem to this commit: https://github.com/wildfly/wildfly/commit/232dff042f The error message mentions that an {{...ejb2.client-mappings}} service is missing, which is consistent with the commit message (also mentions client mappings).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFCORE-1175) CLI prints unexpected ANSI characters to output with "echo" command
by Marek Kopecký (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1175?page=com.atlassian.jira.plugi... ]
Marek Kopecký moved JBEAP-2088 to WFCORE-1175:
----------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-1175 (was: JBEAP-2088)
Workflow: GIT Pull Request workflow (was: CDW v1)
Component/s: CLI
(was: CLI)
Target Release: (was: 7.0.0.GA)
Affects Version/s: 2.0.3.Final
(was: 7.0.0.ER2 (Beta))
Affects Testing: (was: Regression)
> CLI prints unexpected ANSI characters to output with "echo" command
> -------------------------------------------------------------------
>
> Key: WFCORE-1175
> URL: https://issues.jboss.org/browse/WFCORE-1175
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 2.0.3.Final
> Reporter: Marek Kopecký
> Assignee: Ståle Pedersen
> Priority: Blocker
>
> *Description of problem:*
> CLI prints unexpected ANSI character to output with "echo" command.
> * This is regression against EAP 7.0.0.DR13
> * This is blocker for GA release.
> * This is not beta blocker.
> * This is probably AESH issue, so I assign [~stalep], but it is also CLI issue, so [~aloubyansky] may be assigned to this
> *How reproducible:*
> Always
> *Steps to Reproduce:*
> # ./standalone.sh
> # ./jboss-cli.sh --connect controller=127.0.0.1 command="echo test-echo" > out.txt
> # vim out.txt
> #* "cat out.txt" can't be used for reproducing, because console hide unexpected ANSI characters
> *Actual results:*
> {noformat}
> ^[[0G^[[2Ktest-echo
> {noformat}
> *Expected results:*
> {noformat}
> test-echo
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-4853) Provide two cluster test case for EJBClient
by Ladislav Thon (JIRA)
[ https://issues.jboss.org/browse/WFLY-4853?page=com.atlassian.jira.plugin.... ]
Ladislav Thon commented on WFLY-4853:
-------------------------------------
I hope we can get this merged soon. This test would (hopefully :-) ) prevent WFLY-5752.
> Provide two cluster test case for EJBClient
> -------------------------------------------
>
> Key: WFLY-4853
> URL: https://issues.jboss.org/browse/WFLY-4853
> Project: WildFly
> Issue Type: Feature Request
> Components: Test Suite
> Affects Versions: 10.0.0.Alpha4
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
>
> The Wildfly test suite is missing a test case for testing EJBClient interactions over two clusters, which does exist in the EAP test cycle. This test case aims to duplicate that multi-node SmartFrog test in the Wildfly testsuite so that errors are identified early.
> The test setup:
> - two clusters
> {noformat}
> ejb-forwarder = {node0, node1}
> ejb={node3, node4}
> {noformat}
> where each node of cluster ejb-forwarder has a remote outbound connection to node3
> - a forwarding SFSB deployment on cluster ejb-forwarder, which forwards invocations to cluster ejb
> - a non-forwarding deployment on cluster ejb
> - a client which makes invocations on the clustered deployment on ejb-forwarder every 10 ms
> The test execution:
> - once the servers and deployments have been deployed, each server is shut down and then restarted in turn, at which time the test ends.
> The expected behaviour:
> - at least 90% of client invocations will complete without exception
> - test client invocations on ejb-forwarder will fail over from node0 to node1 (or vice versa, depending on which node of cluster ejb-forwarder is down)
> - server-client invocations on ejb will fail-over from node3 to node 4 (or vice versa depending on which node of cluster ejb is down)
> The invocation transaction attribute set up:
> - invocations from the client to ejb-forwarder are not in transaction scope
> - invocations from ejb-forwarder to ejb are in transaction scope with attribute REQUIRED
> This allows exercising invocations from a managed transaction context, which uncovered a number of issues...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-5752) Can't rename the "ejb" cache container
by Ladislav Thon (JIRA)
[ https://issues.jboss.org/browse/WFLY-5752?page=com.atlassian.jira.plugin.... ]
Ladislav Thon updated WFLY-5752:
--------------------------------
Description:
When I rename the {{ejb}} cache container, deploying a simple app that contains an EJB ends with a horrible error message. This is a blocker, because renaming a cache container is required for a 2clusters scenario (standalone client invoking a remote EJB in cluster A, that EJB in turns invokes a remote EJB in cluster B, and forwards the response to the original client).
More details:
1. build current WildFly master and {{unzip .../wildfly/build/target/wildfly-10.0.0.CR5-SNAPSHOT.zip}}
2. {{cp tinyRemoteEjb-server-ee7.jar wildfly-10.0.0.CR5-SNAPSHOT/standalone/deployments/}} # the JAR is attached
3. change the {{wildfly-10.0.0.CR5-SNAPSHOT/standalone/configuration/standalone-full-ha.xml}} file like this:
{code}
<!-- in the "ejb3" subsystem -->
<passivation-store name="infinispan" cache-container="ejb2" max-size="10000"/>
<remote cluster="ejb2" connector-ref="http-remoting-connector" thread-pool-name="default"/>
<!-- in the "infinispan" subsystem -->
<cache-container name="ejb2" ...>
{code}
4. {{./wildfly-10.0.0.CR5-SNAPSHOT/bin/standalone.sh -c standalone-full-ha.xml}}
This leads to:
{code}
14:11:22,473 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "tinyRemoteEjb-server-ee7.jar")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => [
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".CdiValidatorFactoryService",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".WeldStartService",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.CREATE",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.JndiBindingsService",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.START",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.VIEW.\"cz.ladicek.tinyRemoteEjb.server.MyBean\".REMOTE",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.WeldInstantiator",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.WeldInterceptorBindingsService",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".deploymentCompleteService",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".jndiDependencyService",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".moduleDeploymentRuntimeInformation",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".moduleDeploymentRuntimeInformationStart",
"jboss.naming.context.java.app.tinyRemoteEjb-server-ee7.tinyRemoteEjb-server-ee7.MyBeanImpl",
"jboss.naming.context.java.app.tinyRemoteEjb-server-ee7.tinyRemoteEjb-server-ee7.\"MyBeanImpl!cz.ladicek.tinyRemoteEjb.server.MyBean\"",
"jboss.naming.context.java.global.tinyRemoteEjb-server-ee7.MyBeanImpl",
"jboss.naming.context.java.global.tinyRemoteEjb-server-ee7.\"MyBeanImpl!cz.ladicek.tinyRemoteEjb.server.MyBean\"",
"jboss.naming.context.java.module.tinyRemoteEjb-server-ee7.tinyRemoteEjb-server-ee7.MyBeanImpl",
"jboss.naming.context.java.module.tinyRemoteEjb-server-ee7.tinyRemoteEjb-server-ee7.\"MyBeanImpl!cz.ladicek.tinyRemoteEjb.server.MyBean\""
],
"Services that may be the cause:" => ["jboss.clustering.registry.ejb2.client-mappings"]
}}
14:11:22,476 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "ejb3"),
("service" => "remote")
]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.ejb.remoting.connector.client-mappings.installer is missing [jboss.clustering.registry.ejb2.client-mappings]"]}
{code}
This works perfectly fine in 10.0.0.CR4, so I did a {{git bisect}} and traced the problem to this commit: https://github.com/wildfly/wildfly/commit/232dff042f The error message mentions that an {{...ejb2.client-mappings}} service is missing, which is consistent with the commit message (also mentions client mappings).
was:
When I rename the {{ejb}} cache container, deploying a simple app that contains an EJB ends with a horrible error message. This is a blocker, because renaming a cache container is required for a 2clusters scenario (standalone client invoking a remote EJB in cluster A, that EJB in turns invokes a remote EJB in cluster B, and forwards the response to the original client).
More details:
1. {{unzip jboss-eap-7.0.0.ER2.zip}} # though ER1 is affected as well
2. {{cp tinyRemoteEjb-server-ee7.jar jboss-eap-7.0/standalone/deployments/}} # the JAR is attached
3. change the {{jboss-eap-7.0/standalone/configuration/standalone-full-ha.xml}} file like this:
{code}
<!-- in the "ejb3" subsystem -->
<passivation-store name="infinispan" cache-container="ejb2" max-size="10000"/>
<remote cluster="ejb2" connector-ref="http-remoting-connector" thread-pool-name="default"/>
<!-- in the "infinispan" subsystem -->
<cache-container name="ejb2" ...>
{code}
4. {{./jboss-eap-7.0/bin/standalone.sh -c standalone-full-ha.xml}}
This leads to:
{code}
14:11:22,473 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "tinyRemoteEjb-server-ee7.jar")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => [
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".CdiValidatorFactoryService",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".WeldStartService",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.CREATE",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.JndiBindingsService",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.START",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.VIEW.\"cz.ladicek.tinyRemoteEjb.server.MyBean\".REMOTE",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.WeldInstantiator",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.WeldInterceptorBindingsService",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".deploymentCompleteService",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".jndiDependencyService",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".moduleDeploymentRuntimeInformation",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".moduleDeploymentRuntimeInformationStart",
"jboss.naming.context.java.app.tinyRemoteEjb-server-ee7.tinyRemoteEjb-server-ee7.MyBeanImpl",
"jboss.naming.context.java.app.tinyRemoteEjb-server-ee7.tinyRemoteEjb-server-ee7.\"MyBeanImpl!cz.ladicek.tinyRemoteEjb.server.MyBean\"",
"jboss.naming.context.java.global.tinyRemoteEjb-server-ee7.MyBeanImpl",
"jboss.naming.context.java.global.tinyRemoteEjb-server-ee7.\"MyBeanImpl!cz.ladicek.tinyRemoteEjb.server.MyBean\"",
"jboss.naming.context.java.module.tinyRemoteEjb-server-ee7.tinyRemoteEjb-server-ee7.MyBeanImpl",
"jboss.naming.context.java.module.tinyRemoteEjb-server-ee7.tinyRemoteEjb-server-ee7.\"MyBeanImpl!cz.ladicek.tinyRemoteEjb.server.MyBean\""
],
"Services that may be the cause:" => ["jboss.clustering.registry.ejb2.client-mappings"]
}}
14:11:22,476 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "ejb3"),
("service" => "remote")
]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.ejb.remoting.connector.client-mappings.installer is missing [jboss.clustering.registry.ejb2.client-mappings]"]}
{code}
This works perfectly fine in 7.0.0.DR13, so I did a {{git bisect}} and traced the problem to this commit: https://github.com/jbossas/jboss-eap7/commit/232dff042f The error message mentions that an {{...ejb2.client-mappings}} service is missing, which is consistent with the commit message (also mentions client mappings).
> Can't rename the "ejb" cache container
> --------------------------------------
>
> Key: WFLY-5752
> URL: https://issues.jboss.org/browse/WFLY-5752
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, EJB
> Reporter: Ladislav Thon
> Assignee: Paul Ferraro
> Priority: Blocker
> Attachments: tinyRemoteEjb-server-ee7.jar
>
>
> When I rename the {{ejb}} cache container, deploying a simple app that contains an EJB ends with a horrible error message. This is a blocker, because renaming a cache container is required for a 2clusters scenario (standalone client invoking a remote EJB in cluster A, that EJB in turns invokes a remote EJB in cluster B, and forwards the response to the original client).
> More details:
> 1. build current WildFly master and {{unzip .../wildfly/build/target/wildfly-10.0.0.CR5-SNAPSHOT.zip}}
> 2. {{cp tinyRemoteEjb-server-ee7.jar wildfly-10.0.0.CR5-SNAPSHOT/standalone/deployments/}} # the JAR is attached
> 3. change the {{wildfly-10.0.0.CR5-SNAPSHOT/standalone/configuration/standalone-full-ha.xml}} file like this:
> {code}
> <!-- in the "ejb3" subsystem -->
> <passivation-store name="infinispan" cache-container="ejb2" max-size="10000"/>
> <remote cluster="ejb2" connector-ref="http-remoting-connector" thread-pool-name="default"/>
> <!-- in the "infinispan" subsystem -->
> <cache-container name="ejb2" ...>
> {code}
> 4. {{./wildfly-10.0.0.CR5-SNAPSHOT/bin/standalone.sh -c standalone-full-ha.xml}}
> This leads to:
> {code}
> 14:11:22,473 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "tinyRemoteEjb-server-ee7.jar")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => [
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".CdiValidatorFactoryService",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".WeldStartService",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.CREATE",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.JndiBindingsService",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.START",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.VIEW.\"cz.ladicek.tinyRemoteEjb.server.MyBean\".REMOTE",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.WeldInstantiator",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.WeldInterceptorBindingsService",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".deploymentCompleteService",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".jndiDependencyService",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".moduleDeploymentRuntimeInformation",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".moduleDeploymentRuntimeInformationStart",
> "jboss.naming.context.java.app.tinyRemoteEjb-server-ee7.tinyRemoteEjb-server-ee7.MyBeanImpl",
> "jboss.naming.context.java.app.tinyRemoteEjb-server-ee7.tinyRemoteEjb-server-ee7.\"MyBeanImpl!cz.ladicek.tinyRemoteEjb.server.MyBean\"",
> "jboss.naming.context.java.global.tinyRemoteEjb-server-ee7.MyBeanImpl",
> "jboss.naming.context.java.global.tinyRemoteEjb-server-ee7.\"MyBeanImpl!cz.ladicek.tinyRemoteEjb.server.MyBean\"",
> "jboss.naming.context.java.module.tinyRemoteEjb-server-ee7.tinyRemoteEjb-server-ee7.MyBeanImpl",
> "jboss.naming.context.java.module.tinyRemoteEjb-server-ee7.tinyRemoteEjb-server-ee7.\"MyBeanImpl!cz.ladicek.tinyRemoteEjb.server.MyBean\""
> ],
> "Services that may be the cause:" => ["jboss.clustering.registry.ejb2.client-mappings"]
> }}
> 14:11:22,476 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "ejb3"),
> ("service" => "remote")
> ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.ejb.remoting.connector.client-mappings.installer is missing [jboss.clustering.registry.ejb2.client-mappings]"]}
> {code}
> This works perfectly fine in 10.0.0.CR4, so I did a {{git bisect}} and traced the problem to this commit: https://github.com/wildfly/wildfly/commit/232dff042f The error message mentions that an {{...ejb2.client-mappings}} service is missing, which is consistent with the commit message (also mentions client mappings).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-5752) Can't rename the "ejb" cache container
by Ladislav Thon (JIRA)
[ https://issues.jboss.org/browse/WFLY-5752?page=com.atlassian.jira.plugin.... ]
Ladislav Thon updated WFLY-5752:
--------------------------------
Affects Version/s: (was: 10.0.0.CR5)
> Can't rename the "ejb" cache container
> --------------------------------------
>
> Key: WFLY-5752
> URL: https://issues.jboss.org/browse/WFLY-5752
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, EJB
> Reporter: Ladislav Thon
> Assignee: Paul Ferraro
> Priority: Blocker
> Attachments: tinyRemoteEjb-server-ee7.jar
>
>
> When I rename the {{ejb}} cache container, deploying a simple app that contains an EJB ends with a horrible error message. This is a blocker, because renaming a cache container is required for a 2clusters scenario (standalone client invoking a remote EJB in cluster A, that EJB in turns invokes a remote EJB in cluster B, and forwards the response to the original client).
> More details:
> 1. {{unzip jboss-eap-7.0.0.ER2.zip}} # though ER1 is affected as well
> 2. {{cp tinyRemoteEjb-server-ee7.jar jboss-eap-7.0/standalone/deployments/}} # the JAR is attached
> 3. change the {{jboss-eap-7.0/standalone/configuration/standalone-full-ha.xml}} file like this:
> {code}
> <!-- in the "ejb3" subsystem -->
> <passivation-store name="infinispan" cache-container="ejb2" max-size="10000"/>
> <remote cluster="ejb2" connector-ref="http-remoting-connector" thread-pool-name="default"/>
> <!-- in the "infinispan" subsystem -->
> <cache-container name="ejb2" ...>
> {code}
> 4. {{./jboss-eap-7.0/bin/standalone.sh -c standalone-full-ha.xml}}
> This leads to:
> {code}
> 14:11:22,473 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "tinyRemoteEjb-server-ee7.jar")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => [
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".CdiValidatorFactoryService",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".WeldStartService",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.CREATE",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.JndiBindingsService",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.START",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.VIEW.\"cz.ladicek.tinyRemoteEjb.server.MyBean\".REMOTE",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.WeldInstantiator",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.WeldInterceptorBindingsService",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".deploymentCompleteService",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".jndiDependencyService",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".moduleDeploymentRuntimeInformation",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".moduleDeploymentRuntimeInformationStart",
> "jboss.naming.context.java.app.tinyRemoteEjb-server-ee7.tinyRemoteEjb-server-ee7.MyBeanImpl",
> "jboss.naming.context.java.app.tinyRemoteEjb-server-ee7.tinyRemoteEjb-server-ee7.\"MyBeanImpl!cz.ladicek.tinyRemoteEjb.server.MyBean\"",
> "jboss.naming.context.java.global.tinyRemoteEjb-server-ee7.MyBeanImpl",
> "jboss.naming.context.java.global.tinyRemoteEjb-server-ee7.\"MyBeanImpl!cz.ladicek.tinyRemoteEjb.server.MyBean\"",
> "jboss.naming.context.java.module.tinyRemoteEjb-server-ee7.tinyRemoteEjb-server-ee7.MyBeanImpl",
> "jboss.naming.context.java.module.tinyRemoteEjb-server-ee7.tinyRemoteEjb-server-ee7.\"MyBeanImpl!cz.ladicek.tinyRemoteEjb.server.MyBean\""
> ],
> "Services that may be the cause:" => ["jboss.clustering.registry.ejb2.client-mappings"]
> }}
> 14:11:22,476 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "ejb3"),
> ("service" => "remote")
> ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.ejb.remoting.connector.client-mappings.installer is missing [jboss.clustering.registry.ejb2.client-mappings]"]}
> {code}
> This works perfectly fine in 7.0.0.DR13, so I did a {{git bisect}} and traced the problem to this commit: https://github.com/jbossas/jboss-eap7/commit/232dff042f The error message mentions that an {{...ejb2.client-mappings}} service is missing, which is consistent with the commit message (also mentions client mappings).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-5752) Can't rename the "ejb" cache container
by Ladislav Thon (JIRA)
[ https://issues.jboss.org/browse/WFLY-5752?page=com.atlassian.jira.plugin.... ]
Ladislav Thon updated WFLY-5752:
--------------------------------
Attachment: tinyRemoteEjb-server-ee7.jar
> Can't rename the "ejb" cache container
> --------------------------------------
>
> Key: WFLY-5752
> URL: https://issues.jboss.org/browse/WFLY-5752
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, EJB
> Affects Versions: 10.0.0.CR5
> Reporter: Ladislav Thon
> Assignee: Paul Ferraro
> Priority: Blocker
> Attachments: tinyRemoteEjb-server-ee7.jar
>
>
> When I rename the {{ejb}} cache container, deploying a simple app that contains an EJB ends with a horrible error message. This is a blocker, because renaming a cache container is required for a 2clusters scenario (standalone client invoking a remote EJB in cluster A, that EJB in turns invokes a remote EJB in cluster B, and forwards the response to the original client).
> More details:
> 1. {{unzip jboss-eap-7.0.0.ER2.zip}} # though ER1 is affected as well
> 2. {{cp tinyRemoteEjb-server-ee7.jar jboss-eap-7.0/standalone/deployments/}} # the JAR is attached
> 3. change the {{jboss-eap-7.0/standalone/configuration/standalone-full-ha.xml}} file like this:
> {code}
> <!-- in the "ejb3" subsystem -->
> <passivation-store name="infinispan" cache-container="ejb2" max-size="10000"/>
> <remote cluster="ejb2" connector-ref="http-remoting-connector" thread-pool-name="default"/>
> <!-- in the "infinispan" subsystem -->
> <cache-container name="ejb2" ...>
> {code}
> 4. {{./jboss-eap-7.0/bin/standalone.sh -c standalone-full-ha.xml}}
> This leads to:
> {code}
> 14:11:22,473 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "tinyRemoteEjb-server-ee7.jar")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => [
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".CdiValidatorFactoryService",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".WeldStartService",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.CREATE",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.JndiBindingsService",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.START",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.VIEW.\"cz.ladicek.tinyRemoteEjb.server.MyBean\".REMOTE",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.WeldInstantiator",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.WeldInterceptorBindingsService",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".deploymentCompleteService",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".jndiDependencyService",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".moduleDeploymentRuntimeInformation",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".moduleDeploymentRuntimeInformationStart",
> "jboss.naming.context.java.app.tinyRemoteEjb-server-ee7.tinyRemoteEjb-server-ee7.MyBeanImpl",
> "jboss.naming.context.java.app.tinyRemoteEjb-server-ee7.tinyRemoteEjb-server-ee7.\"MyBeanImpl!cz.ladicek.tinyRemoteEjb.server.MyBean\"",
> "jboss.naming.context.java.global.tinyRemoteEjb-server-ee7.MyBeanImpl",
> "jboss.naming.context.java.global.tinyRemoteEjb-server-ee7.\"MyBeanImpl!cz.ladicek.tinyRemoteEjb.server.MyBean\"",
> "jboss.naming.context.java.module.tinyRemoteEjb-server-ee7.tinyRemoteEjb-server-ee7.MyBeanImpl",
> "jboss.naming.context.java.module.tinyRemoteEjb-server-ee7.tinyRemoteEjb-server-ee7.\"MyBeanImpl!cz.ladicek.tinyRemoteEjb.server.MyBean\""
> ],
> "Services that may be the cause:" => ["jboss.clustering.registry.ejb2.client-mappings"]
> }}
> 14:11:22,476 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "ejb3"),
> ("service" => "remote")
> ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.ejb.remoting.connector.client-mappings.installer is missing [jboss.clustering.registry.ejb2.client-mappings]"]}
> {code}
> This works perfectly fine in 7.0.0.DR13, so I did a {{git bisect}} and traced the problem to this commit: https://github.com/jbossas/jboss-eap7/commit/232dff042f The error message mentions that an {{...ejb2.client-mappings}} service is missing, which is consistent with the commit message (also mentions client mappings).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-5752) Can't rename the "ejb" cache container
by Ladislav Thon (JIRA)
[ https://issues.jboss.org/browse/WFLY-5752?page=com.atlassian.jira.plugin.... ]
Ladislav Thon updated WFLY-5752:
--------------------------------
Affects Version/s: 10.0.0.CR5
> Can't rename the "ejb" cache container
> --------------------------------------
>
> Key: WFLY-5752
> URL: https://issues.jboss.org/browse/WFLY-5752
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, EJB
> Affects Versions: 10.0.0.CR5
> Reporter: Ladislav Thon
> Assignee: Paul Ferraro
> Priority: Blocker
> Attachments: tinyRemoteEjb-server-ee7.jar
>
>
> When I rename the {{ejb}} cache container, deploying a simple app that contains an EJB ends with a horrible error message. This is a blocker, because renaming a cache container is required for a 2clusters scenario (standalone client invoking a remote EJB in cluster A, that EJB in turns invokes a remote EJB in cluster B, and forwards the response to the original client).
> More details:
> 1. {{unzip jboss-eap-7.0.0.ER2.zip}} # though ER1 is affected as well
> 2. {{cp tinyRemoteEjb-server-ee7.jar jboss-eap-7.0/standalone/deployments/}} # the JAR is attached
> 3. change the {{jboss-eap-7.0/standalone/configuration/standalone-full-ha.xml}} file like this:
> {code}
> <!-- in the "ejb3" subsystem -->
> <passivation-store name="infinispan" cache-container="ejb2" max-size="10000"/>
> <remote cluster="ejb2" connector-ref="http-remoting-connector" thread-pool-name="default"/>
> <!-- in the "infinispan" subsystem -->
> <cache-container name="ejb2" ...>
> {code}
> 4. {{./jboss-eap-7.0/bin/standalone.sh -c standalone-full-ha.xml}}
> This leads to:
> {code}
> 14:11:22,473 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "tinyRemoteEjb-server-ee7.jar")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => [
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".CdiValidatorFactoryService",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".WeldStartService",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.CREATE",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.JndiBindingsService",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.START",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.VIEW.\"cz.ladicek.tinyRemoteEjb.server.MyBean\".REMOTE",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.WeldInstantiator",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.WeldInterceptorBindingsService",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".deploymentCompleteService",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".jndiDependencyService",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".moduleDeploymentRuntimeInformation",
> "jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".moduleDeploymentRuntimeInformationStart",
> "jboss.naming.context.java.app.tinyRemoteEjb-server-ee7.tinyRemoteEjb-server-ee7.MyBeanImpl",
> "jboss.naming.context.java.app.tinyRemoteEjb-server-ee7.tinyRemoteEjb-server-ee7.\"MyBeanImpl!cz.ladicek.tinyRemoteEjb.server.MyBean\"",
> "jboss.naming.context.java.global.tinyRemoteEjb-server-ee7.MyBeanImpl",
> "jboss.naming.context.java.global.tinyRemoteEjb-server-ee7.\"MyBeanImpl!cz.ladicek.tinyRemoteEjb.server.MyBean\"",
> "jboss.naming.context.java.module.tinyRemoteEjb-server-ee7.tinyRemoteEjb-server-ee7.MyBeanImpl",
> "jboss.naming.context.java.module.tinyRemoteEjb-server-ee7.tinyRemoteEjb-server-ee7.\"MyBeanImpl!cz.ladicek.tinyRemoteEjb.server.MyBean\""
> ],
> "Services that may be the cause:" => ["jboss.clustering.registry.ejb2.client-mappings"]
> }}
> 14:11:22,476 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "ejb3"),
> ("service" => "remote")
> ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.ejb.remoting.connector.client-mappings.installer is missing [jboss.clustering.registry.ejb2.client-mappings]"]}
> {code}
> This works perfectly fine in 7.0.0.DR13, so I did a {{git bisect}} and traced the problem to this commit: https://github.com/jbossas/jboss-eap7/commit/232dff042f The error message mentions that an {{...ejb2.client-mappings}} service is missing, which is consistent with the commit message (also mentions client mappings).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-5752) Can't rename the "ejb" cache container
by Ladislav Thon (JIRA)
Ladislav Thon created WFLY-5752:
-----------------------------------
Summary: Can't rename the "ejb" cache container
Key: WFLY-5752
URL: https://issues.jboss.org/browse/WFLY-5752
Project: WildFly
Issue Type: Bug
Components: Clustering, EJB
Reporter: Ladislav Thon
Assignee: Paul Ferraro
Priority: Blocker
When I rename the {{ejb}} cache container, deploying a simple app that contains an EJB ends with a horrible error message. This is a blocker, because renaming a cache container is required for a 2clusters scenario (standalone client invoking a remote EJB in cluster A, that EJB in turns invokes a remote EJB in cluster B, and forwards the response to the original client).
More details:
1. {{unzip jboss-eap-7.0.0.ER2.zip}} # though ER1 is affected as well
2. {{cp tinyRemoteEjb-server-ee7.jar jboss-eap-7.0/standalone/deployments/}} # the JAR is attached
3. change the {{jboss-eap-7.0/standalone/configuration/standalone-full-ha.xml}} file like this:
{code}
<!-- in the "ejb3" subsystem -->
<passivation-store name="infinispan" cache-container="ejb2" max-size="10000"/>
<remote cluster="ejb2" connector-ref="http-remoting-connector" thread-pool-name="default"/>
<!-- in the "infinispan" subsystem -->
<cache-container name="ejb2" ...>
{code}
4. {{./jboss-eap-7.0/bin/standalone.sh -c standalone-full-ha.xml}}
This leads to:
{code}
14:11:22,473 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "tinyRemoteEjb-server-ee7.jar")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => [
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".CdiValidatorFactoryService",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".WeldStartService",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.CREATE",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.JndiBindingsService",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.START",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.VIEW.\"cz.ladicek.tinyRemoteEjb.server.MyBean\".REMOTE",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.WeldInstantiator",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.WeldInterceptorBindingsService",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".deploymentCompleteService",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".jndiDependencyService",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".moduleDeploymentRuntimeInformation",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".moduleDeploymentRuntimeInformationStart",
"jboss.naming.context.java.app.tinyRemoteEjb-server-ee7.tinyRemoteEjb-server-ee7.MyBeanImpl",
"jboss.naming.context.java.app.tinyRemoteEjb-server-ee7.tinyRemoteEjb-server-ee7.\"MyBeanImpl!cz.ladicek.tinyRemoteEjb.server.MyBean\"",
"jboss.naming.context.java.global.tinyRemoteEjb-server-ee7.MyBeanImpl",
"jboss.naming.context.java.global.tinyRemoteEjb-server-ee7.\"MyBeanImpl!cz.ladicek.tinyRemoteEjb.server.MyBean\"",
"jboss.naming.context.java.module.tinyRemoteEjb-server-ee7.tinyRemoteEjb-server-ee7.MyBeanImpl",
"jboss.naming.context.java.module.tinyRemoteEjb-server-ee7.tinyRemoteEjb-server-ee7.\"MyBeanImpl!cz.ladicek.tinyRemoteEjb.server.MyBean\""
],
"Services that may be the cause:" => ["jboss.clustering.registry.ejb2.client-mappings"]
}}
14:11:22,476 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "ejb3"),
("service" => "remote")
]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.ejb.remoting.connector.client-mappings.installer is missing [jboss.clustering.registry.ejb2.client-mappings]"]}
{code}
This works perfectly fine in 7.0.0.DR13, so I did a {{git bisect}} and traced the problem to this commit: https://github.com/jbossas/jboss-eap7/commit/232dff042f The error message mentions that an {{...ejb2.client-mappings}} service is missing, which is consistent with the commit message (also mentions client mappings).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-5751) Service can't be installed if the path contains a closed bracket
by Paul Wildberg (JIRA)
[ https://issues.jboss.org/browse/WFLY-5751?page=com.atlassian.jira.plugin.... ]
Paul Wildberg commented on WFLY-5751:
-------------------------------------
Maybe there are some more double quotation marks missing,
e.g. jboss-clie.bat in \wildfly-9.0.1.Final\bin\ in line 67 (set "LOGGING_CONFIG=-Dlogging.configuration=file:%JBOSS_HOME%\bin\jboss-cli-logging.properties") - the path of JBOSS_HOME\... is not in double quotation marks.
The whole line is in double quotation marks, but I'm not sure that it works.
> Service can't be installed if the path contains a closed bracket
> ----------------------------------------------------------------
>
> Key: WFLY-5751
> URL: https://issues.jboss.org/browse/WFLY-5751
> Project: WildFly
> Issue Type: Bug
> Components: Batch
> Affects Versions: 9.0.1.Final, 9.0.2.Final, 10.0.0.CR4
> Environment: all Windows versions
> Reporter: Paul Wildberg
> Assignee: Cheng Fang
> Priority: Critical
> Labels: jboss
>
> Problem:
> If you start "service.bat install" in e.g. in C:\Program Files (x86)\wildfly-9.0.1.Final\bin\service you will get:
> Using the X86-64bit version of prunsrv
> "\wildfly-9.0.1.Final\domain\log" can not be used syntatically at this point (don't know if it is correct, I translated it from german. Original it is "kann syntaktisch an dieser Stelle nicht verarbeitet werden.")
> Cause:
> This is because of the ) in "Program Files (x86)" and this is a problem because in the service.bat in line 175 and 179 (set LOGPATH=%JBOSS_HOME%\domain\log - in version 9.0.1 and 9.0.2 - in Version 10 it may be in another line) the path is not set in double quotation marks.
> All other paths are set in double quotation marks.
> Solution:
> Set the path in double quotation marks:
> set LOGPATH="%JBOSS_HOME%\domain\log"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (ELY-383) Update ServerAuthenticationContext to carry an identity from start to end
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/ELY-383?page=com.atlassian.jira.plugin.sy... ]
David Lloyd commented on ELY-383:
---------------------------------
Actually, the transition from the "INITIAL Ⓐ" to "AUTHORIZED Ⓑ" states is better done as "INITIAL Ⓐ" to "AUTHORIZED Ⓐ", and from there to "AUTHORIZED Ⓑ".
> Update ServerAuthenticationContext to carry an identity from start to end
> -------------------------------------------------------------------------
>
> Key: ELY-383
> URL: https://issues.jboss.org/browse/ELY-383
> Project: WildFly Elytron
> Issue Type: Task
> Components: API / SPI
> Reporter: David Lloyd
> Assignee: David Lloyd
> Fix For: 1.1.0.Beta3
>
> Attachments: Blank Flowchart - ServerAuthenticationContext.png
>
>
> The {{ServerAuthenticationContext}} should capture the identity in force for its domain when it is constructed. Any authorization attempt should always apply to the current identity - either the captured identity, or whatever the last successfully authorized identity was in the context.
> The attached state diagram should accurately summarize how authorization identity flows through. Authentication identity is only available during the "NAME ASSIGNED" state; once authorization occurs, the authentication identity is no longer useful and is disposed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months