Hi Farah fjuma,

Thanks much!

The issue that I reported in ticket was getting when I set InitialContext in Callable and use that outside callable to lookup bean. When I moved bean lookup, it worked fine. But in our code, it is spread around a lot of files and need some solution to return IntialContext or bean. I tried the authentication context setting code on top class and put the code there in Callable. Then it worked for for endpoints that didn't take much. But for those doing more lookups and complex operations, getting error.

The specified item was not found.  The exception is here.

Caused by: javax.ejb.EJBException: WFTXN0021: Failed to acquire a connection for this operation

at org.jboss.ejb.protocol.remote.EJBClientChannel.processInvocation(EJBClientChannel.java:471)

at org.jboss.ejb.protocol.remote.RemoteEJBReceiver$1.lambda$handleDone$0(RemoteEJBReceiver.java:91)

at org.xnio.FinishedIoFuture.addNotifier(FinishedIoFuture.java:79)

at org.jboss.ejb.protocol.remote.RemoteEJBReceiver$1.handleDone(RemoteEJBReceiver.java:76)

at org.jboss.ejb.protocol.remote.RemoteEJBReceiver$1.handleDone(RemoteEJBReceiver.java:74)

at org.xnio.IoFuture$HandlingNotifier.notify(IoFuture.java:208)

at org.xnio.AbstractIoFuture$NotifierRunnable.run(AbstractIoFuture.java:720)

...

Caused by: javax.transaction.SystemException: WFTXN0021: Failed to acquire a connection for this operation

at org.wildfly.transaction.client.provider.remoting.RemotingRemoteTransactionPeer.begin(RemotingRemoteTransactionPeer.java:212)

at org.wildfly.transaction.client.RemoteTransaction.setLocation(RemoteTransaction.java:222)

at org.jboss.ejb.protocol.remote.EJBClientChannel.writeTransaction(EJBClientChannel.java:557)

at org.jboss.ejb.protocol.remote.EJBClientChannel.processInvocation(EJBClientChannel.java:367)

... 12 more

Caused by: org.wildfly.security.auth.AuthenticationException: JBREM000308: Authentication failed (no mechanisms left), tried: (none)

at org.jboss.remoting3.ConnectionPeerIdentityContext.doAuthenticate(ConnectionPeerIdentityContext.java:368)

at org.jboss.remoting3.ConnectionPeerIdentityContext.authenticate(ConnectionPeerIdentityContext.java:174)

But it works fine using the wildfly-config.xml. When I rename this file and use programamtic approach, this error comes when client does many remote actions & gets error always at the same point. But the operation is same. For eg: read a set of files and update in DB via EJB call one by one. Here at a particular files, the error comes. Is there any limitation when we use programmatic approach, when InitialContext is closed and created? That is the only action happens. But the same works with configuration file.

Here is the modified code:

// create your authentication configuration

                        AuthenticationConfiguration namingConfig = AuthenticationConfiguration.empty()

                        .useProviders(() -> new Provider[] { new WildFlyElytronProvider() })                      

                        .setSaslMechanismSelector(SaslMechanismSelector.NONE.addMechanism("PLAIN"))

                        .useRealm("SSLRealm")

                        .useName(userName)

                        .usePassword(pass);

                        // create your authentication context

                        AuthenticationContext context = AuthenticationContext.empty()

                        .with(MatchRule.ALL.matchHost("localhost"), namingConfig);

                        ContextManager<AuthenticationContext> contextManager = authenticationContext.getInstanceContextManager(); 

                        contextManager.setGlobalDefault(authenticationContext);

 

                        // create a callable that creates and uses an InitialContext

                        Callable<String> callable = () -> {

                        String paswd = null;

                      

                            try {

                            final Properties ejbProperties = new Properties();

                                ejbProperties.put("java.naming.factory.initial", "org.wildfly.naming.client.WildFlyInitialContextFactory");

                                ejbProperties.put("java.naming.provider.url", System.getProperty("java.naming.provider.url"));

                              

                                  // Lookup EJBs & perform operations

                                  new InitialContext(ejbProperties).lookup(...)

                                  ...

 

 

           // use your authentication context to run your callable

           try {

                context.runCallable(callable);

            } catch (Exception e) {

                 e.printStackTrace();

            }

Is there any reason for the above error, why it's working on configuration file based approach but not when through code?

Is this the known issue mentioned here?

[JBEAP-9662] Invocations on UserTransaction obtained from InitialContext don't take user credentials into account - JBos…

It's working fine like configuration file based approach if I set security principal & credentials in the InitialContext.

Ref: mock-artifacts/ejbclient/eap7.1-provider-url-with-transactions-secured at master · jmartisk/mock-artifacts · GitHub

I wonder why it need security principal & credentials in the InitialContext since the global authentication context already set as below:

            // create your authentication configuration

            AuthenticationConfiguration namingConfig = AuthenticationConfiguration.empty()          

            .setSaslMechanismSelector(SaslMechanismSelector.NONE.addMechanism(sasl).forbidMechanism("JBOSS-LOCAL-USER"))

            //.useProviders( () -> new Provider[] { new WildFlyElytronProvider() } )          

            .useDefaultProviders()

            .useName(username)

            .usePassword(password)

            .useRealm(realm);

            // create your authentication context

            AuthenticationContext authenticationContext = AuthenticationContext.empty()

            .with(MatchRule.ALL.matchHost(host), namingConfig);

            ContextManager<AuthenticationContext> contextManager = authenticationContext.getInstanceContextManager(); 

            contextManager.setGlobalDefault(authenticationContext);