[JBoss JIRA] (WFCORE-2929) Missing default values in ldap-key-store description in management model.
by Yeray Borges (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2929?page=com.atlassian.jira.plugi... ]
Yeray Borges reopened WFCORE-2929:
----------------------------------
> Missing default values in ldap-key-store description in management model.
> -------------------------------------------------------------------------
>
> Key: WFCORE-2929
> URL: https://issues.jboss.org/browse/WFCORE-2929
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Ondrej Lukas
> Assignee: Yeray Borges
> Labels: user_experience
> Fix For: 3.0.0.Beta28
>
>
> Some attributes of Elytron {{ldap-key-store}} resource have defined some default value, but description of these attributes in CLI is missing default values. According to XSD following attributes of {{ldap-key-store}} have assigned some default value:
> * {{search-recursive}} has default value {{true}}
> * {{search-time-limit}} has default value {{10000}}
> * {{filter-alias}} has default value {{(alias-attribute=\{0\})}}
> * {{filter-certificate}} has default value {{(certificate-attribute=\{0\})}}
> * {{filter-iterate}} has default value {{(alias-attribute=*)}}
> * {{alias-attribute}} has default value {{cn}}
> * {{certificate-attribute}} has default value {{usercertificate}}
> * {{certificate-type}} has default value {{X.509}}
> * {{certificate-chain-attribute}} has default value {{userSMIMECertificate}}
> * {{certificate-chain-encoding}} has default value {{PKCS7}}
> * {{key-attribute}} has default value {{userPKCS12}}
> * {{key-type}} has default value {{PKCS12}}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JGRP-2203) ASYM_ENCRYPT: no merge when coord is killed
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2203?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-2203:
--------------------------------
A similar issue exists when we have \{A,B,C\} and C leaves gracefully and {{change_key_on_leave}} is true.
* A creates a new secret key, encrypts view \{A,B\} and broadcasts it.
* B drops the view because it cannot decrypt it.
* B then asks A for the secret key
* A sends the new secret key to B
* B is now able to decrypt the (retransmitted) view \{A,B\}
Perhaps the common solution for this issue and the issue described above is to have the coordinator send a {{FETCH_SECRET_KEY}} message to all members so they fetch the new secret key via the key exchange protocol.
> ASYM_ENCRYPT: no merge when coord is killed
> -------------------------------------------
>
> Key: JGRP-2203
> URL: https://issues.jboss.org/browse/JGRP-2203
> Project: JGroups
> Issue Type: Bug
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 4.0.5
>
> Attachments: asym-encrypt.xml
>
>
> When we have \{A,B,C\} and A is killed, B and C never end up with the same view. (This works when A leaves gracefully).
> The sample config is attached as asym-encrypt.xml
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFCORE-3059) suggest-capabilities returns suffix when the capability contains a dot
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3059?page=com.atlassian.jira.plugi... ]
Darran Lofthouse commented on WFCORE-3059:
------------------------------------------
[~brian.stansberry] Do you think this is a security issue or does it sound more like a general domain management issue?
> suggest-capabilities returns suffix when the capability contains a dot
> ----------------------------------------------------------------------
>
> Key: WFCORE-3059
> URL: https://issues.jboss.org/browse/WFCORE-3059
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Claudio Miranda
>
> Given the following operation to add credential-store.
> {code}
> /profile=full/subsystem=elytron/credential-store=store.foo:add(relative-to=jboss.server.data.dir, credential-reference={clear-text=pass123},create)
> /profile=full/subsystem=elytron/credential-store=store2:add(relative-to=jboss.server.data.dir, credential-reference={clear-text=pass123},create)
> {code}
> There is a problem related to the naming used in "store.foo", the suggest-capabilities operation will return only the suffix "foo" instead of the resource name "store.foo"
> {code}
> /host=master/core-service=capability-registry:suggest-capabilities(name=org.wildfly.security.credential-store,dependent-address=[("profile" => "full"),("subsystem" => "elytron"),("credential-store" => "*")])
> {
> "outcome" => "success",
> "result" => [
> "store2",
> "foo"
> ]
> }
> {code}
> This presents a problem for capability-reference, as the auto complete on CLI (using tab) and Web Console returns "foo" and "store2" as value.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-8852) Clean up managed domain handling of the transaction subsystem's 'probe' operation
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-8852?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-8852:
-----------------------------
Fix Version/s: 11.0.0.Beta1
> Clean up managed domain handling of the transaction subsystem's 'probe' operation
> ---------------------------------------------------------------------------------
>
> Key: WFLY-8852
> URL: https://issues.jboss.org/browse/WFLY-8852
> Project: WildFly
> Issue Type: Sub-task
> Components: Transactions
> Reporter: Brian Stansberry
> Assignee: Michael Musgrove
> Fix For: 11.0.0.Beta1
>
>
> Subtask for this item from the parent issue:
> {quote}
> The transaction subsystem's "probe" operation. A read-only, runtime-only op registered on the profile resource but which is functionally a no-op if invoked on the profile resource. But WFCORE-2858 would mean this now gets rolled out to all servers in the domain that use the profile, triggering an actual probe on all. So, if we do WFCORE-2858 we could:
> a) Accept this, and let the op roll out. That should be an RFE though, with analysis that rolling it out would be harmless.
> b) Remove the op from the profile. It never did anything useful (just a no-op that isn't rolled out) so removing it is only
> a semi-breaking change.
> c) Add OperationEntry.Flag.HOST_CONTROLLER_ONLY to the operation definition to prevent that rollout.
> Choice c) would let WFCORE-2858 go forward and preserve the status quo for this op, with a) and b) still options for the future, so that's what will be done as part of this work.
> {quote}
> The parent issue will do choice c); this issue is to decide the final status.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ELY-1282) Regression against ER1, When HTTP mechanism misconfigured, then deployment doesn't fail anymore
by Martin Choma (JIRA)
Martin Choma created ELY-1282:
---------------------------------
Summary: Regression against ER1, When HTTP mechanism misconfigured, then deployment doesn't fail anymore
Key: ELY-1282
URL: https://issues.jboss.org/browse/ELY-1282
Project: WildFly Elytron
Issue Type: Bug
Reporter: Martin Choma
Assignee: Darran Lofthouse
Priority: Blocker
When only one disabled mechanism is configured for undertow deployment
{code}
<http-authentication-factory name="elytron-http-authn-factory" http-server-mechanism-factory="wrongConfigurableHttpServerMechanismFactory" security-domain="ApplicationDomain">
<mechanism-configuration>
<mechanism mechanism-name="BASIC">
<mechanism-realm realm-name="Some realm"/>
</mechanism>
</mechanism-configuration>
</http-authentication-factory>
<configurable-http-server-mechanism-factory name="wrongConfigurableHttpServerMechanismFactory" http-server-mechanism-factory="aggregateHttpServerMechanismFactory">
<filters>
<filter pattern="BASIC" enabling="false"/>
</filters>
</configurable-http-server-mechanism-factory>
<application-security-domains>
<application-security-domain name="ApplicationDomain" http-authentication-factory="elytron-http-authn-factory"/>
</application-security-domains>
{code}
And in web.xml is configured BASIC authentication
{code}
<login-config>
<auth-method>BASIC</auth-method>
<realm-name>Test realm</realm-name>
</login-config>
{code}
Till ER1 such configuration leads to deployment failure and message "There are no mechanisms available from the HttpAuthenticationFactory"
{code}
07:48:46,765 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "elytron-app.war" (runtime-name: "elytron-app.war")
07:48:46,883 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-5) ISPN000128: Infinispan version: Infinispan 'Chakra' 8.2.6.Final-redhat-1
07:48:46,887 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443
07:48:46,984 INFO [org.jboss.ws.common.management] (MSC service thread 1-3) JBWS022052: Starting JBossWS 5.1.8.Final-redhat-1 (Apache CXF 3.1.11.redhat-1)
07:48:47,333 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 63) MSC000001: Failed to start service jboss.undertow.deployment.default-server.default-host./elytron-app: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./elytron-app: java.lang.RuntimeException: java.lang.IllegalStateException: WFLYUT0084: There are no mechanisms available from the HttpAuthenticationFactory.
at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:84)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
at org.jboss.threads.JBossThread.run(JBossThread.java:320)
Caused by: java.lang.RuntimeException: java.lang.IllegalStateException: WFLYUT0084: There are no mechanisms available from the HttpAuthenticationFactory.
at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:241)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:99)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:81)
... 6 more
Caused by: java.lang.IllegalStateException: WFLYUT0084: There are no mechanisms available from the HttpAuthenticationFactory.
at org.wildfly.extension.undertow.ApplicationSecurityDomainDefinition$ApplicationSecurityDomainService.initialSecurityHandler(ApplicationSecurityDomainDefinition.java:460)
at org.wildfly.extension.undertow.ApplicationSecurityDomainDefinition$ApplicationSecurityDomainService.lambda$applyElytronSecurity$2(ApplicationSecurityDomainDefinition.java:422)
at io.undertow.servlet.core.DeploymentManagerImpl.setupSecurityHandlers(DeploymentManagerImpl.java:415)
at io.undertow.servlet.core.DeploymentManagerImpl.access$600(DeploymentManagerImpl.java:119)
at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:211)
at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:174)
at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)
at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1704)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1704)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1704)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1704)
at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:239)
... 8 more
07:48:47,341 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "elytron-app.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.undertow.deployment.default-server.default-host./elytron-app" => "java.lang.RuntimeException: java.lang.IllegalStateException: WFLYUT0084: There are no mechanisms available from the HttpAuthenticationFactory.
Caused by: java.lang.RuntimeException: java.lang.IllegalStateException: WFLYUT0084: There are no mechanisms available from the HttpAuthenticationFactory.
Caused by: java.lang.IllegalStateException: WFLYUT0084: There are no mechanisms available from the HttpAuthenticationFactory."}}
07:48:47,370 INFO [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "elytron-app.war" (runtime-name : "elytron-app.war")
07:48:47,373 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0186: Services which failed to start: service jboss.undertow.deployment.default-server.default-host./elytron-app: java.lang.RuntimeException: java.lang.IllegalStateException: WFLYUT0084: There are no mechanisms available from the HttpAuthenticationFactory.
{code}
In ER2 application is deployed succesfully
{code}
07:50:31,041 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "elytron-app.war" (runtime-name: "elytron-app.war")
07:50:31,136 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443
07:50:31,160 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-7) ISPN000128: Infinispan version: Infinispan 'Chakra' 8.2.7.Final-redhat-1
07:50:31,216 INFO [org.jboss.ws.common.management] (MSC service thread 1-3) JBWS022052: Starting JBossWS 5.1.8.Final-redhat-1 (Apache CXF 3.1.11.redhat-1)
07:50:31,661 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 62) WFLYUT0021: Registered web context: '/elytron-app' for server 'default-server'
07:50:31,683 INFO [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "elytron-app.war" (runtime-name : "elytron-app.war")
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-9076) Make the IIOP migration warnings more user friendly
by Tomasz Adamski (JIRA)
[ https://issues.jboss.org/browse/WFLY-9076?page=com.atlassian.jira.plugin.... ]
Tomasz Adamski updated WFLY-9076:
---------------------------------
Description:
JBEAP-10124 changed the behaviour of jacorb:migrate operation to print migration warnings instead of throwing an error in case inconsistent configuration was used. We should update the warning messages to more user friendly form as now it may not be totally clear for user what is expected of him to do.
*reproduce*
Add the following snippet into EAP7.1 standalone.xml configuration
{code:xml}
<extension module="org.jboss.as.jacorb"/>
...
<subsystem xmlns="urn:jboss:domain:jacorb:1.4">
<orb socket-binding="jacorb" ssl-socket-binding="jacorb-ssl">
<initializers security="identity" transactions="on"/>
</orb>
<security client-supports="ServerAuth" client-requires="ServerAuth" server-supports="ServerAuth" server-requires="ServerAuth"/>
<ior-settings>
<transport-config integrity="required" confidentiality="supported" trust-in-client="required" trust-in-target="supported"
detect-replay="required" detect-misordering="required"/>
<as-context auth-method="none" realm="ApplicationRealm" required="true"/>
<sas-context caller-propagation="supported"/>
</ior-settings>
</subsystem>
{code}
run the following command from $JBOSS_HOME/bin directory
{noformat}
[pkremens@localhost bin] $ ./jboss-cli.sh 'embed-server, /subsystem=jacorb:describe-migration' | grep --after-context=7 migration-warnings
{noformat}
*actual*
{noformat}
"migration-warnings" => [
"WFLYIIOP0111: SSL has not been configured but ssl-port property has been specified - the connection will use clear-text protocol",
"WFLYIIOP0105: Inconsistent transport-config configuration: integrity is not supported but it is not configured with NONE value",
"WFLYIIOP0105: Inconsistent transport-config configuration: confidentiality is not supported but it is not configured with NONE value",
"WFLYIIOP0105: Inconsistent transport-config configuration: trust-in-client is not supported but it is not configured with NONE value",
"WFLYIIOP0104: Inconsistent transport-config configuration: detect-misordering is supported but it is configured with NONE value",
"WFLYIIOP0104: Inconsistent transport-config configuration: detect-replay is supported but it is configured with NONE value"
]
{noformat}
*expected*
Warning messages clearly states what is expected from user to make the configuration valid.
{noformat}
...
"WFLYIIOP0105: Inconsistent transport-config configuration: trust-in-client is not supported, please remove it or configure it to NONE value",
...
{noformat}
cc: [~dsimko], [~ochaloup]
> Make the IIOP migration warnings more user friendly
> ---------------------------------------------------
>
> Key: WFLY-9076
> URL: https://issues.jboss.org/browse/WFLY-9076
> Project: WildFly
> Issue Type: Enhancement
> Components: IIOP
> Affects Versions: 11.0.0.Alpha1
> Reporter: Tomasz Adamski
> Assignee: Tomasz Adamski
> Fix For: 11.0.0.Beta1
>
>
> JBEAP-10124 changed the behaviour of jacorb:migrate operation to print migration warnings instead of throwing an error in case inconsistent configuration was used. We should update the warning messages to more user friendly form as now it may not be totally clear for user what is expected of him to do.
> *reproduce*
> Add the following snippet into EAP7.1 standalone.xml configuration
> {code:xml}
> <extension module="org.jboss.as.jacorb"/>
> ...
> <subsystem xmlns="urn:jboss:domain:jacorb:1.4">
> <orb socket-binding="jacorb" ssl-socket-binding="jacorb-ssl">
> <initializers security="identity" transactions="on"/>
> </orb>
> <security client-supports="ServerAuth" client-requires="ServerAuth" server-supports="ServerAuth" server-requires="ServerAuth"/>
> <ior-settings>
> <transport-config integrity="required" confidentiality="supported" trust-in-client="required" trust-in-target="supported"
> detect-replay="required" detect-misordering="required"/>
> <as-context auth-method="none" realm="ApplicationRealm" required="true"/>
> <sas-context caller-propagation="supported"/>
> </ior-settings>
> </subsystem>
> {code}
> run the following command from $JBOSS_HOME/bin directory
> {noformat}
> [pkremens@localhost bin] $ ./jboss-cli.sh 'embed-server, /subsystem=jacorb:describe-migration' | grep --after-context=7 migration-warnings
> {noformat}
> *actual*
> {noformat}
> "migration-warnings" => [
> "WFLYIIOP0111: SSL has not been configured but ssl-port property has been specified - the connection will use clear-text protocol",
> "WFLYIIOP0105: Inconsistent transport-config configuration: integrity is not supported but it is not configured with NONE value",
> "WFLYIIOP0105: Inconsistent transport-config configuration: confidentiality is not supported but it is not configured with NONE value",
> "WFLYIIOP0105: Inconsistent transport-config configuration: trust-in-client is not supported but it is not configured with NONE value",
> "WFLYIIOP0104: Inconsistent transport-config configuration: detect-misordering is supported but it is configured with NONE value",
> "WFLYIIOP0104: Inconsistent transport-config configuration: detect-replay is supported but it is configured with NONE value"
> ]
> {noformat}
> *expected*
> Warning messages clearly states what is expected from user to make the configuration valid.
> {noformat}
> ...
> "WFLYIIOP0105: Inconsistent transport-config configuration: trust-in-client is not supported, please remove it or configure it to NONE value",
> ...
> {noformat}
> cc: [~dsimko], [~ochaloup]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-9074) NPE o.j.a.ejb3.component.stateful.StatefulComponentSessionIdGeneratingInterceptor.processInvocation()
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-9074?page=com.atlassian.jira.plugin.... ]
David Lloyd commented on WFLY-9074:
-----------------------------------
Ah, didn't register that when I read this earlier. Thanks.
> NPE o.j.a.ejb3.component.stateful.StatefulComponentSessionIdGeneratingInterceptor.processInvocation()
> -----------------------------------------------------------------------------------------------------
>
> Key: WFLY-9074
> URL: https://issues.jboss.org/browse/WFLY-9074
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 10.1.0.Final
> Reporter: Darryl Miles
>
> https://issues.jboss.org/browse/WFLY-6663 (see fix for this other bug, maybe the 1 line wait method is needed somewhere else too?)
> Much more intermittent matter (I guess the time window is smaller).
> 16:14:04,428 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 19) MSC000001: Failed to start service jboss.deployment.subunit."com.domain.ear-0.0.1-SNAPSHOT.ear"."com-domain-ejb.main-0.0.1-SNAPSHOT.jar".component.MainStartupEjbImpl.START: org.jboss.msc.service.StartException in service jboss.deployment.subunit."com.domain.ear-0.0.1-SNAPSHOT.ear"."com-domain-ejb.main-0.0.1-SNAPSHOT.jar".component.MainStartupEjbImpl.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance
> at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:57)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance
> at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:163)
> at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:134)
> at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:88)
> at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:124)
> at org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:138)
> at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54)
> ... 6 more
> Caused by: javax.ejb.EJBException: java.lang.RuntimeException: WFLYNAM0059: Resource lookup for injection failed: env/com.domain.ejb.main.impl.MainStartupEjbImpl/mainEjb
> at org.jboss.as.ejb3.tx.BMTInterceptor.handleException(BMTInterceptor.java:83)
> at org.jboss.as.ejb3.tx.EjbBMTInterceptor.checkStatelessDone(EjbBMTInterceptor.java:91)
> at org.jboss.as.ejb3.tx.EjbBMTInterceptor.handleInvocation(EjbBMTInterceptor.java:106)
> at org.jboss.as.ejb3.tx.BMTInterceptor.processInvocation(BMTInterceptor.java:58)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.weld.injection.WeldInjectionContextInterceptor.processInvocation(WeldInjectionContextInterceptor.java:43)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.component.singleton.StartupCountDownInterceptor.processInvocation(StartupCountDownInterceptor.java:25)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)
> at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
> at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161)
> ... 11 more
> Caused by: java.lang.RuntimeException: WFLYNAM0059: Resource lookup for injection failed: env/com.domain.ejb.main.impl.MainStartupEjbImpl/mainEjb
> at org.jboss.as.naming.deployment.ContextNames$BindInfo$1$1.getReference(ContextNames.java:319)
> at org.jboss.as.ee.component.ManagedReferenceFieldInjectionInterceptorFactory$ManagedReferenceFieldInjectionInterceptor.processInvocation(ManagedReferenceFieldInjectionInterceptorFactory.java:97)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ee.component.ManagedReferenceFieldInjectionInterceptorFactory$ManagedReferenceFieldInjectionInterceptor.processInvocation(ManagedReferenceFieldInjectionInterceptorFactory.java:107)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ee.component.ManagedReferenceFieldInjectionInterceptorFactory$ManagedReferenceFieldInjectionInterceptor.processInvocation(ManagedReferenceFieldInjectionInterceptorFactory.java:107)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ee.component.ManagedReferenceFieldInjectionInterceptorFactory$ManagedReferenceFieldInjectionInterceptor.processInvocation(ManagedReferenceFieldInjectionInterceptorFactory.java:107)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ee.component.AroundConstructInterceptorFactory$1.processInvocation(AroundConstructInterceptorFactory.java:28)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.weld.injection.WeldInterceptorInjectionInterceptor.processInvocation(WeldInterceptorInjectionInterceptor.java:56)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.weld.ejb.Jsr299BindingsCreateInterceptor.processInvocation(Jsr299BindingsCreateInterceptor.java:100)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.tx.EjbBMTInterceptor.handleInvocation(EjbBMTInterceptor.java:103)
> ... 28 more
> Caused by: javax.naming.NameNotFoundException: env/com.domain.ejb.main.impl.MainStartupEjbImpl/mainEjb [Root exception is java.lang.IllegalStateException: WFLYEE0046: Failed to instantiate component view]
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:153)
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:83)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189)
> at org.jboss.as.naming.deployment.ContextNames$BindInfo$1$1.getReference(ContextNames.java:316)
> ... 45 more
> Caused by: java.lang.IllegalStateException: WFLYEE0046: Failed to instantiate component view
> at org.jboss.as.ee.component.ViewManagedReferenceFactory.getReference(ViewManagedReferenceFactory.java:58)
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:143)
> ... 50 more
> Caused by: java.lang.NullPointerException
> at org.jboss.as.ejb3.component.stateful.StatefulComponentSessionIdGeneratingInterceptor.processInvocation(StatefulComponentSessionIdGeneratingInterceptor.java:57)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
> at org.jboss.as.ee.component.ViewService$DefaultViewInstanceFactory.createViewInstance(ViewService.java:305)
> at org.jboss.as.ee.component.ViewService$View.createInstance(ViewService.java:184)
> at org.jboss.as.ee.component.ViewService$View.createInstance(ViewService.java:174)
> at org.jboss.as.ee.component.ViewManagedReferenceFactory.getReference(ViewManagedReferenceFactory.java:56)
> ... 51 more
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-9074) NPE o.j.a.ejb3.component.stateful.StatefulComponentSessionIdGeneratingInterceptor.processInvocation()
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-9074?page=com.atlassian.jira.plugin.... ]
Paul Ferraro commented on WFLY-9074:
------------------------------------
[~dmlloyd] {quote}could this be related to the recent clustering-related startup changes?{quote}
Given that this was filed against 10.1.0.Final, no.
> NPE o.j.a.ejb3.component.stateful.StatefulComponentSessionIdGeneratingInterceptor.processInvocation()
> -----------------------------------------------------------------------------------------------------
>
> Key: WFLY-9074
> URL: https://issues.jboss.org/browse/WFLY-9074
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 10.1.0.Final
> Reporter: Darryl Miles
>
> https://issues.jboss.org/browse/WFLY-6663 (see fix for this other bug, maybe the 1 line wait method is needed somewhere else too?)
> Much more intermittent matter (I guess the time window is smaller).
> 16:14:04,428 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 19) MSC000001: Failed to start service jboss.deployment.subunit."com.domain.ear-0.0.1-SNAPSHOT.ear"."com-domain-ejb.main-0.0.1-SNAPSHOT.jar".component.MainStartupEjbImpl.START: org.jboss.msc.service.StartException in service jboss.deployment.subunit."com.domain.ear-0.0.1-SNAPSHOT.ear"."com-domain-ejb.main-0.0.1-SNAPSHOT.jar".component.MainStartupEjbImpl.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance
> at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:57)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance
> at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:163)
> at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:134)
> at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:88)
> at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:124)
> at org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:138)
> at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54)
> ... 6 more
> Caused by: javax.ejb.EJBException: java.lang.RuntimeException: WFLYNAM0059: Resource lookup for injection failed: env/com.domain.ejb.main.impl.MainStartupEjbImpl/mainEjb
> at org.jboss.as.ejb3.tx.BMTInterceptor.handleException(BMTInterceptor.java:83)
> at org.jboss.as.ejb3.tx.EjbBMTInterceptor.checkStatelessDone(EjbBMTInterceptor.java:91)
> at org.jboss.as.ejb3.tx.EjbBMTInterceptor.handleInvocation(EjbBMTInterceptor.java:106)
> at org.jboss.as.ejb3.tx.BMTInterceptor.processInvocation(BMTInterceptor.java:58)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.weld.injection.WeldInjectionContextInterceptor.processInvocation(WeldInjectionContextInterceptor.java:43)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.component.singleton.StartupCountDownInterceptor.processInvocation(StartupCountDownInterceptor.java:25)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)
> at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
> at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161)
> ... 11 more
> Caused by: java.lang.RuntimeException: WFLYNAM0059: Resource lookup for injection failed: env/com.domain.ejb.main.impl.MainStartupEjbImpl/mainEjb
> at org.jboss.as.naming.deployment.ContextNames$BindInfo$1$1.getReference(ContextNames.java:319)
> at org.jboss.as.ee.component.ManagedReferenceFieldInjectionInterceptorFactory$ManagedReferenceFieldInjectionInterceptor.processInvocation(ManagedReferenceFieldInjectionInterceptorFactory.java:97)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ee.component.ManagedReferenceFieldInjectionInterceptorFactory$ManagedReferenceFieldInjectionInterceptor.processInvocation(ManagedReferenceFieldInjectionInterceptorFactory.java:107)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ee.component.ManagedReferenceFieldInjectionInterceptorFactory$ManagedReferenceFieldInjectionInterceptor.processInvocation(ManagedReferenceFieldInjectionInterceptorFactory.java:107)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ee.component.ManagedReferenceFieldInjectionInterceptorFactory$ManagedReferenceFieldInjectionInterceptor.processInvocation(ManagedReferenceFieldInjectionInterceptorFactory.java:107)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ee.component.AroundConstructInterceptorFactory$1.processInvocation(AroundConstructInterceptorFactory.java:28)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.weld.injection.WeldInterceptorInjectionInterceptor.processInvocation(WeldInterceptorInjectionInterceptor.java:56)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.weld.ejb.Jsr299BindingsCreateInterceptor.processInvocation(Jsr299BindingsCreateInterceptor.java:100)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.tx.EjbBMTInterceptor.handleInvocation(EjbBMTInterceptor.java:103)
> ... 28 more
> Caused by: javax.naming.NameNotFoundException: env/com.domain.ejb.main.impl.MainStartupEjbImpl/mainEjb [Root exception is java.lang.IllegalStateException: WFLYEE0046: Failed to instantiate component view]
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:153)
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:83)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189)
> at org.jboss.as.naming.deployment.ContextNames$BindInfo$1$1.getReference(ContextNames.java:316)
> ... 45 more
> Caused by: java.lang.IllegalStateException: WFLYEE0046: Failed to instantiate component view
> at org.jboss.as.ee.component.ViewManagedReferenceFactory.getReference(ViewManagedReferenceFactory.java:58)
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:143)
> ... 50 more
> Caused by: java.lang.NullPointerException
> at org.jboss.as.ejb3.component.stateful.StatefulComponentSessionIdGeneratingInterceptor.processInvocation(StatefulComponentSessionIdGeneratingInterceptor.java:57)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
> at org.jboss.as.ee.component.ViewService$DefaultViewInstanceFactory.createViewInstance(ViewService.java:305)
> at org.jboss.as.ee.component.ViewService$View.createInstance(ViewService.java:184)
> at org.jboss.as.ee.component.ViewService$View.createInstance(ViewService.java:174)
> at org.jboss.as.ee.component.ViewManagedReferenceFactory.getReference(ViewManagedReferenceFactory.java:56)
> ... 51 more
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-5413) On IIOP migration default properties are not persisted
by Tomasz Adamski (JIRA)
[ https://issues.jboss.org/browse/WFLY-5413?page=com.atlassian.jira.plugin.... ]
Tomasz Adamski closed WFLY-5413.
--------------------------------
Fix Version/s: 11.0.0.CR1
Resolution: Done
In current upstream default properties are also persisted.
> On IIOP migration default properties are not persisted
> ------------------------------------------------------
>
> Key: WFLY-5413
> URL: https://issues.jboss.org/browse/WFLY-5413
> Project: WildFly
> Issue Type: Enhancement
> Components: IIOP
> Affects Versions: 10.0.0.CR1
> Reporter: Ondra Chaloupka
> Assignee: Tomasz Adamski
> Fix For: 11.0.0.CR1
>
>
> If there are some enumeration set in {{jacorb}} subsystem that should be migrate to new {{iiop}} subsystem with the {{:migrate}} operation then if value of such property matches the the defaults set for the new {{iiop}} such property with value is not persisted to XML.
> It would be nice if properties would be persisted for user can see what's happened after migration directly and not being confused that migration forgot for some value. Or he will need to check what are defaults and if all settings was migrated correctly.
> The example of such properties which do not persist because of its default values are
> * initializers: security="none"
> * security: client-supports="ServerAuth" server-supports="MutualAuth"
> * security: client-requires="None" server-requires="None"
> * transport-config: detect-misordering="none"
> * as-context: auth-method="username_password" required="false"
> * sas-context caller-propagation="none"
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months