[JBoss JIRA] (WFLY-8915) Unexpected update of configuration file standalone.xml if an archive is dropped to deployments folder
by Wolf-Dieter Fink (JIRA)
Wolf-Dieter Fink created WFLY-8915:
--------------------------------------
Summary: Unexpected update of configuration file standalone.xml if an archive is dropped to deployments folder
Key: WFLY-8915
URL: https://issues.jboss.org/browse/WFLY-8915
Project: WildFly
Issue Type: Bug
Affects Versions: 11.0.0.Alpha1
Reporter: Wolf-Dieter Fink
Assignee: Jason Greene
Priority: Minor
It is not expected that the standalone.xml is written and versions or other content is updated.
e.g. the top level element
<server xmlns="urn:jboss:domain:x.y">
It is expected that the standalone configuration is updated with the latest namespace versions, or other changes, if the configuration needs to be persisted.
But for any unmanged deployment it is not expected and not necessary to update the configuration file.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFLY-8032) CheckValidConnectionSQL can open a transaction, preventing application from changing transaction isolation level (PostgreSQL)
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-8032?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-8032:
-----------------------------------------------
Jiří Bílek <jbilek(a)redhat.com> changed the Status of [bug 1195079|https://bugzilla.redhat.com/show_bug.cgi?id=1195079] from ON_QA to VERIFIED
> CheckValidConnectionSQL can open a transaction, preventing application from changing transaction isolation level (PostgreSQL)
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-8032
> URL: https://issues.jboss.org/browse/WFLY-8032
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 10.1.0.Final
> Reporter: Tomas Hofman
> Assignee: Tomas Hofman
> Fix For: 11.0.0.Beta1
>
>
> PostgreSQL driver only allows changing the transaction isolation level when transaction is not opened. Under certain circumstances, an application can receive a connection with already opened transaction and an attempt to change transaction isolation level will lead to exception.
> This happens with the PostgreSQL driver and with CheckValidConnectionSQL checker configured to run a select statement to verify connections retrieved from the pool.
> The scenario is as follows:
> # A connection is retrieved from the pool for the 1st app and CheckValidConnectionSQL verifies it by running a select statement (autocommit is set to true by default). This statement is run directly via the jdbc connection, not the wrapper.
> # 1st app receives the connection, sets autocommit=false, perform some work and commits a transaction.
> # The connection is returned to the pool, {{cleanup()}} method is called on LocalManagedConnection wrapper, which sets autocommit=true. This however doesn't reset autocommit on the wrapped jdbc connection yet, which would only happen just before executing another SQL statement f.i.
> # The same connection is retrieved from the pool for the 2nd app and CheckValidConnectionSQL runs the query. Because the jdbc connection has still autocommit=false, new transaction is opened.
> # 2nd app receives the connection and calls {{setTransactionIsolation()}}, which throws an exception because the transaction is open.
> Possible solution could be that the {{cleanup()}} method propagates the autocommit=true to the wrapped jdbc connection immediately.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2942) Adding credential-reference with non-exist alias to authentication-configuration through CLI results to NPE
by Ondrej Lukas (JIRA)
Ondrej Lukas created WFCORE-2942:
------------------------------------
Summary: Adding credential-reference with non-exist alias to authentication-configuration through CLI results to NPE
Key: WFCORE-2942
URL: https://issues.jboss.org/browse/WFCORE-2942
Project: WildFly Core
Issue Type: Bug
Components: Security
Reporter: Ondrej Lukas
Assignee: Darran Lofthouse
Priority: Critical
When Elytron authentication-configuration is added with credential-reference with non-exist alias through CLI then it results to NullPointerException.
See:
{code}
/subsystem=elytron/credential-store=cs:add(location=cs.jceks,create=true,relative-to=jboss.server.data.dir,credential-reference={clear-text=pass})
/subsystem=elytron/credential-store=cs:add-alias(alias=exist,secret-value=pass)
/subsystem=elytron/authentication-configuration=cfg1:add(credential-reference={store=cs,alias=exist})
{"outcome" => "success"}
/subsystem=elytron/authentication-configuration=cfg2:add(credential-reference={store=cs,alias=nonexist})
{
"outcome" => "failed",
"failure-description" => {"WFLYCTL0080: Failed services" => {"org.wildfly.security.authentication-configuration.cfg2" => "Failed to start service
Caused by: java.lang.IllegalStateException: java.lang.NullPointerException
Caused by: java.lang.NullPointerException"}},
"rolled-back" => true
}
{code}
NPE in server log:
{code}
ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service org.wildfly.security.authentication-configuration.cfg2: org.jboss.msc.service.StartException in service org.wildfly.security.authentication-configuration.cfg2: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1978)
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:745)
Caused by: java.lang.IllegalStateException: java.lang.NullPointerException
at org.wildfly.extension.elytron.AuthenticationClientDefinitions$1.lambda$getValueSupplier$17(AuthenticationClientDefinitions.java:364)
at java.util.function.Function.lambda$andThen$5(Function.java:88)
at org.wildfly.extension.elytron.AuthenticationClientDefinitions$1.lambda$getValueSupplier$18(AuthenticationClientDefinitions.java:370)
at org.wildfly.extension.elytron.TrivialService.start(TrivialService.java:53)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
... 3 more
Caused by: java.lang.NullPointerException
at org.wildfly.extension.elytron.AuthenticationClientDefinitions$1.lambda$getValueSupplier$17(AuthenticationClientDefinitions.java:359)
... 8 more
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2942) Adding credential-reference with non-exist alias to authentication-configuration through CLI results to NPE
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2942?page=com.atlassian.jira.plugi... ]
Ondrej Lukas updated WFCORE-2942:
---------------------------------
Labels: user_experience (was: )
> Adding credential-reference with non-exist alias to authentication-configuration through CLI results to NPE
> -----------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-2942
> URL: https://issues.jboss.org/browse/WFCORE-2942
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 3.0.0.Beta23
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Priority: Critical
> Labels: user_experience
>
> When Elytron authentication-configuration is added with credential-reference with non-exist alias through CLI then it results to NullPointerException.
> See:
> {code}
> /subsystem=elytron/credential-store=cs:add(location=cs.jceks,create=true,relative-to=jboss.server.data.dir,credential-reference={clear-text=pass})
> /subsystem=elytron/credential-store=cs:add-alias(alias=exist,secret-value=pass)
> /subsystem=elytron/authentication-configuration=cfg1:add(credential-reference={store=cs,alias=exist})
> {"outcome" => "success"}
> /subsystem=elytron/authentication-configuration=cfg2:add(credential-reference={store=cs,alias=nonexist})
> {
> "outcome" => "failed",
> "failure-description" => {"WFLYCTL0080: Failed services" => {"org.wildfly.security.authentication-configuration.cfg2" => "Failed to start service
> Caused by: java.lang.IllegalStateException: java.lang.NullPointerException
> Caused by: java.lang.NullPointerException"}},
> "rolled-back" => true
> }
> {code}
> NPE in server log:
> {code}
> ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service org.wildfly.security.authentication-configuration.cfg2: org.jboss.msc.service.StartException in service org.wildfly.security.authentication-configuration.cfg2: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1978)
> 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:745)
> Caused by: java.lang.IllegalStateException: java.lang.NullPointerException
> at org.wildfly.extension.elytron.AuthenticationClientDefinitions$1.lambda$getValueSupplier$17(AuthenticationClientDefinitions.java:364)
> at java.util.function.Function.lambda$andThen$5(Function.java:88)
> at org.wildfly.extension.elytron.AuthenticationClientDefinitions$1.lambda$getValueSupplier$18(AuthenticationClientDefinitions.java:370)
> at org.wildfly.extension.elytron.TrivialService.start(TrivialService.java:53)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
> ... 3 more
> Caused by: java.lang.NullPointerException
> at org.wildfly.extension.elytron.AuthenticationClientDefinitions$1.lambda$getValueSupplier$17(AuthenticationClientDefinitions.java:359)
> ... 8 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2942) Adding credential-reference with non-exist alias to authentication-configuration through CLI results to NPE
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2942?page=com.atlassian.jira.plugi... ]
Ondrej Lukas updated WFCORE-2942:
---------------------------------
Affects Version/s: 3.0.0.Beta23
> Adding credential-reference with non-exist alias to authentication-configuration through CLI results to NPE
> -----------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-2942
> URL: https://issues.jboss.org/browse/WFCORE-2942
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 3.0.0.Beta23
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Priority: Critical
> Labels: user_experience
>
> When Elytron authentication-configuration is added with credential-reference with non-exist alias through CLI then it results to NullPointerException.
> See:
> {code}
> /subsystem=elytron/credential-store=cs:add(location=cs.jceks,create=true,relative-to=jboss.server.data.dir,credential-reference={clear-text=pass})
> /subsystem=elytron/credential-store=cs:add-alias(alias=exist,secret-value=pass)
> /subsystem=elytron/authentication-configuration=cfg1:add(credential-reference={store=cs,alias=exist})
> {"outcome" => "success"}
> /subsystem=elytron/authentication-configuration=cfg2:add(credential-reference={store=cs,alias=nonexist})
> {
> "outcome" => "failed",
> "failure-description" => {"WFLYCTL0080: Failed services" => {"org.wildfly.security.authentication-configuration.cfg2" => "Failed to start service
> Caused by: java.lang.IllegalStateException: java.lang.NullPointerException
> Caused by: java.lang.NullPointerException"}},
> "rolled-back" => true
> }
> {code}
> NPE in server log:
> {code}
> ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service org.wildfly.security.authentication-configuration.cfg2: org.jboss.msc.service.StartException in service org.wildfly.security.authentication-configuration.cfg2: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1978)
> 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:745)
> Caused by: java.lang.IllegalStateException: java.lang.NullPointerException
> at org.wildfly.extension.elytron.AuthenticationClientDefinitions$1.lambda$getValueSupplier$17(AuthenticationClientDefinitions.java:364)
> at java.util.function.Function.lambda$andThen$5(Function.java:88)
> at org.wildfly.extension.elytron.AuthenticationClientDefinitions$1.lambda$getValueSupplier$18(AuthenticationClientDefinitions.java:370)
> at org.wildfly.extension.elytron.TrivialService.start(TrivialService.java:53)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
> ... 3 more
> Caused by: java.lang.NullPointerException
> at org.wildfly.extension.elytron.AuthenticationClientDefinitions$1.lambda$getValueSupplier$17(AuthenticationClientDefinitions.java:359)
> ... 8 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-99) standalone.bat script does not parse JAVA_OPTS containing '|' symbol properly
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFCORE-99?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFCORE-99:
-----------------------------------------------
Radovan STANCEL <rstancel(a)redhat.com> changed the Status of [bug 1145185|https://bugzilla.redhat.com/show_bug.cgi?id=1145185] from ASSIGNED to NEW
> standalone.bat script does not parse JAVA_OPTS containing '|' symbol properly
> -----------------------------------------------------------------------------
>
> Key: WFCORE-99
> URL: https://issues.jboss.org/browse/WFCORE-99
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 1.0.0.Alpha6
> Environment: Windows OS
> Reporter: Jay SenSharma
> Assignee: Tomaz Cerar
> Fix For: 1.0.0.Alpha9
>
>
> *Scenario -1*
> - With the following line of JAVA_OPTS in "standalone.bat.conf" file
> {code}
> set "JAVA_OPTS=%JAVA_OPTS% -Dhttp.nonProxyHosts=localhost|127.0.0.1|10.10.10.*"
> {code}
> Error while starting WildFly
> {code}
> C:\wildfly-9.0.0.Alpha1-SNAPSHOT\bin>standalone.bat
> Calling "C:\wildfly-9.0.0.Alpha1-SNAPSHOT\bin\standalone.conf.bat"
> Setting JAVA property to "C:\JDKs\jdk1.7.0_67\bin\java"
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> {code}
> *Scenario -2*
> - In Windows "^" sign is the escape character so we tried altering the JAVA_OPTS as following in the "standalone.bat.conf" file:
> {code}
> set "JAVA_OPTS=%JAVA_OPTS% -Dhttp.nonProxyHosts=localhost^|127.0.0.1^|10.10.10.*"
> {code}
> Now WildFly server starts but still we see the following messages in windows console:
> {code}
> C:\wildfly-9.0.0.Alpha1-SNAPSHOT\bin>standalone.bat
> Calling "C:\wildfly-9.0.0.Alpha1-SNAPSHOT\bin\standalone.conf.bat"
> Setting JAVA property to "C:\JDKs\jdk1.7.0_67\bin\java"
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> ===============================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: "C:\wildfly-9.0.0.Alpha1-SNAPSHOT"
> JAVA: "C:\JDKs\jdk1.7.0_67\bin\java"
> JAVA_OPTS: "-client -Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=
> org.jboss.byteman -Dhttp.nonProxyHosts=localhost^|127.0.0.1^|10.10.10.*"
> ===============================================================================
> 15:50:35,453 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.4.Final
> 15:50:35,781 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final
> 15:50:35,953 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly 1.0.0.Alpha5 "Kenny" starting
> {code}
> *NOTE*: It is also not possible to pass such JAVA_OPTS via command line, because it causes the same error:
> {code}
> C:\wildfly-9.0.0.Alpha1-SNAPSHOT\bin>standalone.bat -Dhttp.nonProxyHosts=localhost|127.0.0.1|10.10.10.*
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ELY-1240) Attribute security-domain from Elytron authentication-configuration does not propagate credentials with OAUTHBEARER mechanism
by Ondrej Lukas (JIRA)
Ondrej Lukas created ELY-1240:
---------------------------------
Summary: Attribute security-domain from Elytron authentication-configuration does not propagate credentials with OAUTHBEARER mechanism
Key: ELY-1240
URL: https://issues.jboss.org/browse/ELY-1240
Project: WildFly Elytron
Issue Type: Bug
Reporter: Ondrej Lukas
Assignee: Darran Lofthouse
Priority: Blocker
When client-server schema as 'Client -> Server A -> Server B' is used and intermediate server (server A) uses authentication-configuration.security-domain and OAUTHBEARER mechanism is used then application (i.e. EJB) from intermediate server cannot authenticate to server B. It seems that OAUTHBEARER mechanism cannot be chosen by SASL mechanism selector when bearer token is not explicitly provided.
Intermediate server should be able to obtain credentials for OAuth from given security domain and use them for authentication [1].
See reproducer for more details.
We request blocker flag since this issue breaks feature in RFE EAP7-284 Client / Server Security Context Propagation for Remoting and Running As a given user and RFE EAP7-568 Server side configuration for Elytron Client.
Exception from intermediate server:
{code}
ERROR [org.jboss.as.ejb3.invocation] (default task-5) WFLYEJB0034: EJB Invocation failed on component Intermediate for method public abstract java.lang.String example.ejb.WhoAmIBeanRemote.whoAmI(): javax.ejb.EJBException: java.lang.IllegalStateException: EJBCLIENT000024: Not able to find EJB matching "StatelessEJBLocator for "/server-side/WhoAmIBean", view is interface example.ejb.WhoAmIBeanRemote, affinity is None"
at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:188)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:277)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:332)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:240)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:327)
at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:73)
at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:89)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
at org.jboss.as.ejb3.remote.EJBRemoteTransactionPropagatingInterceptor.processInvocation(EJBRemoteTransactionPropagatingInterceptor.java:89)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:47)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
at org.jboss.as.ejb3.security.IdentityOutflowInterceptor.processInvocation(IdentityOutflowInterceptor.java:73)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
at org.jboss.as.ejb3.security.RolesAllowedInterceptor.processInvocation(RolesAllowedInterceptor.java:63)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
at org.jboss.as.ejb3.security.SecurityDomainInterceptor.processInvocation(SecurityDomainInterceptor.java:44)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
at org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor.processInvocation(StartupAwaitInterceptor.java:22)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
at org.jboss.as.ejb3.deployment.processors.EjbSuspendInterceptor.processInvocation(EjbSuspendInterceptor.java:57)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:67)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:256)
at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:609)
at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:57)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53)
at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:198)
at org.wildfly.security.auth.server.SecurityIdentity.runAsFunctionEx(SecurityIdentity.java:380)
at org.jboss.as.ejb3.remote.AssociationImpl.invokeWithIdentity(AssociationImpl.java:460)
at org.jboss.as.ejb3.remote.AssociationImpl.invokeMethod(AssociationImpl.java:455)
at org.jboss.as.ejb3.remote.AssociationImpl.lambda$receiveInvocationRequest$0(AssociationImpl.java:165)
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:745)
Caused by: java.lang.IllegalStateException: EJBCLIENT000024: Not able to find EJB matching "StatelessEJBLocator for "/server-side/WhoAmIBean", view is interface example.ejb.WhoAmIBeanRemote, affinity is None"
at org.jboss.ejb.client.EJBClientContext.discoverAffinityNone(EJBClientContext.java:719)
at org.jboss.ejb.client.EJBClientContext.performLocatedAction(EJBClientContext.java:701)
at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:162)
at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:112)
at com.sun.proxy.$Proxy47.whoAmI(Unknown Source)
at example.ejb.Intermediate.whoAmI(Intermediate.java:21)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:327)
at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:90)
at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:101)
at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
at org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:40)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53)
at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:275)
... 46 more
Suppressed: javax.security.sasl.SaslException: Authentication failed: none of the mechanisms presented by the server (OAUTHBEARER) are supported
at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:438)
at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:246)
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
at org.xnio.nio.WorkerThread.run(WorkerThread.java:567)
at ...asynchronous invocation...(Unknown Source)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:545)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:513)
at org.jboss.remoting3.ConnectionInfo$None.getConnection(ConnectionInfo.java:84)
at org.jboss.remoting3.ConnectionInfo.getConnection(ConnectionInfo.java:57)
at org.jboss.remoting3.EndpointImpl.doGetConnection(EndpointImpl.java:464)
at org.jboss.remoting3.EndpointImpl.getConnectedIdentity(EndpointImpl.java:410)
at org.jboss.remoting3.Endpoint.getConnectedIdentity(Endpoint.java:126)
at org.jboss.remoting3.Endpoint.getConnectedIdentity(Endpoint.java:139)
at org.jboss.remoting3.Endpoint.getConnection(Endpoint.java:216)
at org.jboss.ejb.protocol.remote.RemotingEJBDiscoveryProvider.lambda$discover$0(RemotingEJBDiscoveryProvider.java:103)
at java.security.AccessController.doPrivileged(Native Method)
at org.jboss.ejb.protocol.remote.RemotingEJBDiscoveryProvider.discover(RemotingEJBDiscoveryProvider.java:103)
at org.wildfly.discovery.impl.AggregateDiscoveryProvider.discover(AggregateDiscoveryProvider.java:58)
at org.wildfly.discovery.Discovery.discover(Discovery.java:94)
at org.jboss.ejb.client.EJBClientContext.discover(EJBClientContext.java:442)
at org.jboss.ejb.client.EJBClientContext.discoverAffinityNone(EJBClientContext.java:714)
... 76 more
{code}
[1] https://issues.jboss.org/browse/JBEAP-11377?focusedCommentId=13416866&pag...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month