13 Replies Latest reply on Jun 13, 2013 6:01 PM by Lance Goforth

    Unable to get remote connection to connect via ejb:/

    Lance Goforth Newbie

      I had an application that was working fine under JBoss AS 7.1 and 7.2, but since they were nearing time to go to production I wanted to move them to a non-beta platform and have been trying to get them to work under EAP 6.1 with no luck.  I've tried all the examples and quickstarts I could find.    This is only one of several projects I have to keep working on so it's been very frustrating.

       

      Here is what I have so far in my test.

       

      The test connection:

       

             SecurityEntityManager securityManager = (SecurityEntityManager) getInitialContext().lookup(getLookupName());

       

      ...

       

                public static String getLookupName() {

             StringBuffer sb = new StringBuffer();

       

             final String appName = "";

             final String moduleName = "psa-server-jboss-ejb3";

             final String distinctName = "";

             final String beanName = "SecurityEntityManagerEJB";

                               final String viewClassName = SecurityEntityManager.class.getName();

       

             sb.append("ejb:");

             sb.append(appName);

             sb.append("/");

             sb.append(moduleName);

             sb.append("/");

             sb.append(distinctName);

             sb.append("/");

             sb.append(beanName);

             sb.append("!");

             sb.append(viewClassName);

       

             log.debug("  jndi lookup: >" + sb.toString());

                               log.debug(" ");

                               return sb.toString();

                }

       

                public Context getInitialContext() throws NamingException {

             InitialContext initialContext = null;

       

             Properties jndiProperties = new Properties();

             jndiProperties.put("jboss.naming.client.ejb.context", Boolean.TRUE);

             jndiProperties.put(Context.URL_PKG_PREFIXES, "org.jboss.ejb.client.naming");

             jndiProperties.put(javax.naming.Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory");

             jndiProperties.put(javax.naming.Context.PROVIDER_URL, "remote://10.110.40.25:4447");

             jndiProperties.put(javax.naming.Context.SECURITY_PRINCIPAL, "psaadmin");

             jndiProperties.put(javax.naming.Context.SECURITY_CREDENTIALS, "....");

       

             initialContext = new InitialContext(jndiProperties);

       

                               return initialContext;

                }

       

       

       

      The jboss-ejb-client.properties file:

      endpoint.name=PSA-Client-V2

      remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED=false

       

      remote.connections=default

       

      remote.connection.default.username=psaadmin

      remote.connection.default.password=...

      remote.connection.default.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false

       

       

       

      I enabled tracing based on another discussion I found here.  So here is the results of that when I try to run the test program:

       

      0    [main] DEBUG org.jboss.logging  - Logging Provider: org.jboss.logging.Log4jLoggerProvider

      19   [main] DEBUG org.jboss.ejb.client.EJBClientPropertiesLoader  - Looking for jboss-ejb-client.properties using classloader sun.misc.Launcher$AppClassLoader@1d9f953d

      37   [main] DEBUG org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector  - EJB client context org.jboss.ejb.client.EJBClientContext@a761fe will have no EJB receivers associated with it since there was no EJB client configuration available to create the receivers

      40   [main] DEBUG org.jboss.naming.remote.client.InitialContextFactory  - Looking for jboss-naming-client.properties using classloader sun.misc.Launcher$AppClassLoader@1d9f953d

      41   [main] DEBUG org.jboss.naming.remote.client.InitialContextFactory  - jboss.naming.client.endpoint.create.options. has the following options {}

      42   [main] TRACE org.jboss.naming.remote.client.InitialContextFactory  - Options {} have been merged with defaults {org.xnio.Options.THREAD_DAEMON=>true} to form {org.xnio.Options.THREAD_DAEMON=>true}

      42   [main] DEBUG org.jboss.naming.remote.client.InitialContextFactory  - jboss.naming.client.remote.connectionprovider.create.options. has the following options {}

      42   [main] TRACE org.jboss.naming.remote.client.InitialContextFactory  - Options {} have been merged with defaults {org.xnio.Options.SSL_ENABLED=>false} to form {org.xnio.Options.SSL_ENABLED=>false}

      49   [main] INFO  org.xnio  - XNIO Version 3.0.7.GA-redhat-1

      53   [main] INFO  org.xnio.nio  - XNIO NIO Implementation Version 3.0.7.GA-redhat-1

      54   [main] TRACE org.xnio.nio  - Starting up with selector provider sun.nio.ch.KQueueSelectorProvider

      57   [main] TRACE org.xnio.nio  - Using polling selector type for temporary selectors.

      64   [main] INFO  org.jboss.remoting  - JBoss Remoting version 3.2.16.GA-redhat-1

      78   [main] TRACE org.xnio.nio  - CAS org.xnio.nio.NioXnioWorker@77fddc31 00000001 -> 00000002

      79   [main] TRACE org.xnio.nio  - CAS org.xnio.nio.NioXnioWorker@77fddc31 00000002 -> 00000003

      79   [Remoting "config-based-naming-client-endpoint" read-1] TRACE org.xnio.nio  - Starting worker thread Thread[Remoting "config-based-naming-client-endpoint" read-1,5,main]

      79   [Remoting "config-based-naming-client-endpoint" read-1] DEBUG org.xnio.nio  - Started channel thread 'Remoting "config-based-naming-client-endpoint" read-1', selector sun.nio.ch.KQueueSelectorImpl@509f5011

      79   [Remoting "config-based-naming-client-endpoint" write-1] TRACE org.xnio.nio  - Starting worker thread Thread[Remoting "config-based-naming-client-endpoint" write-1,5,main]

      79   [Remoting "config-based-naming-client-endpoint" write-1] DEBUG org.xnio.nio  - Started channel thread 'Remoting "config-based-naming-client-endpoint" write-1', selector sun.nio.ch.KQueueSelectorImpl@5557c2bd

      79   [Remoting "config-based-naming-client-endpoint" read-1] TRACE org.xnio.nio.selector  - Beginning select on sun.nio.ch.KQueueSelectorImpl@509f5011

      79   [Remoting "config-based-naming-client-endpoint" write-1] TRACE org.xnio.nio.selector  - Beginning select on sun.nio.ch.KQueueSelectorImpl@5557c2bd

      83   [main] TRACE org.jboss.remoting.endpoint  - Completed open of endpoint "config-based-naming-client-endpoint" <47315d34>

      84   [main] TRACE org.jboss.remoting.endpoint  - Allocated tick to 1 of endpoint "config-based-naming-client-endpoint" <47315d34> (opened Connection provider for remote)

      130  [main] TRACE org.jboss.remoting.endpoint  - Adding connection provider registration named 'remote': Remoting remote connection provider 5d6d2633 for endpoint "config-based-naming-client-endpoint" <47315d34>

      133  [main] DEBUG org.jboss.naming.remote.client.InitialContextFactory  - jboss.naming.client.connect.options. has the following options {}

      133  [main] TRACE org.jboss.naming.remote.client.InitialContextFactory  - Options {} have been merged with defaults {org.xnio.Options.SASL_POLICY_NOANONYMOUS=>false} to form {org.xnio.Options.SASL_POLICY_NOANONYMOUS=>false}

      139  [main] DEBUG com.psasoft.tools  -   jndi lookup: >ejb:/psa-server-jboss-ejb3//SecurityEntityManagerEJB!com.psasoft.security.interfaces.SecurityEntityManager

      139  [main] DEBUG com.psasoft.tools  - 

      164  [main] INFO  org.jboss.ejb.client  - JBoss EJB Client version 1.0.21.Final-redhat-1

      Exception in thread "main" java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:psa-server-jboss-ejb3, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@4026e9f9

                at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:727)

                at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:116)

                at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)

                at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:253)

                at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:198)

                at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:181)

                at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:144)

                at com.sun.proxy.$Proxy0.validateUsername(Unknown Source)

                at com.psasoft.tools.TestRemoteConnection.<init>(TestRemoteConnection.java:33)

                at com.psasoft.tools.TestRemoteConnection.main(TestRemoteConnection.java:18)

      181  [Thread-2] TRACE org.jboss.remoting.resource  - Closing endpoint "config-based-naming-client-endpoint" <47315d34> synchronously

      182  [Thread-2] TRACE org.jboss.remoting.resource  - Closing Remoting remote connection provider 5d6d2633 for endpoint "config-based-naming-client-endpoint" <47315d34> asynchronously

      182  [Thread-2] TRACE org.jboss.remoting.resource  - Completed close of Remoting remote connection provider 5d6d2633 for endpoint "config-based-naming-client-endpoint" <47315d34>

      183  [Thread-2] TRACE org.jboss.remoting.resource  - Closing Registration of 'remote': Remoting remote connection provider 5d6d2633 for endpoint "config-based-naming-client-endpoint" <47315d34> asynchronously

      183  [Thread-2] TRACE org.jboss.remoting.resource  - Closing Remoting remote connection provider 5d6d2633 for endpoint "config-based-naming-client-endpoint" <47315d34> asynchronously

      183  [Thread-2] TRACE org.jboss.remoting.resource  - Completed close of Registration of 'remote': Remoting remote connection provider 5d6d2633 for endpoint "config-based-naming-client-endpoint" <47315d34>

      183  [Thread-2] TRACE org.jboss.remoting.endpoint  - Finished phase 1 shutdown of endpoint "config-based-naming-client-endpoint" <47315d34>

      184  [Thread-2] TRACE org.xnio.nio  - Initiating shutdown of org.xnio.nio.NioXnioWorker@77fddc31

      184  [Thread-2] TRACE org.xnio.nio  - CAS org.xnio.nio.NioXnioWorker@77fddc31 80000003 -> 80000002

      185  [Thread-2] TRACE org.jboss.remoting.resource  - Closing Remoting local connection provider 6855a338 for endpoint "config-based-naming-client-endpoint" <47315d34> asynchronously

      185  [Thread-2] TRACE org.jboss.remoting.resource  - Completed close of Remoting local connection provider 6855a338 for endpoint "config-based-naming-client-endpoint" <47315d34>

      185  [Remoting "config-based-naming-client-endpoint" write-1] TRACE org.xnio.nio.selector  - Selected on sun.nio.ch.KQueueSelectorImpl@5557c2bd

      185  [Remoting "config-based-naming-client-endpoint" write-1] TRACE org.xnio.nio  - Shutting down channel thread "Thread[Remoting "config-based-naming-client-endpoint" write-1,5,main]"

      185  [Remoting "config-based-naming-client-endpoint" read-1] TRACE org.xnio.nio.selector  - Selected on sun.nio.ch.KQueueSelectorImpl@509f5011

      185  [Remoting "config-based-naming-client-endpoint" read-1] TRACE org.xnio.nio  - Shutting down channel thread "Thread[Remoting "config-based-naming-client-endpoint" read-1,5,main]"

      190  [Remoting "config-based-naming-client-endpoint" write-1] TRACE org.xnio.safe-close  - Closing resource sun.nio.ch.KQueueSelectorImpl@5557c2bd

      190  [Remoting "config-based-naming-client-endpoint" read-1] TRACE org.xnio.safe-close  - Closing resource sun.nio.ch.KQueueSelectorImpl@509f5011

      191  [Remoting "config-based-naming-client-endpoint" read-1] TRACE org.xnio.nio  - CAS org.xnio.nio.NioXnioWorker@77fddc31 80000002 -> 80000001

      191  [Remoting "config-based-naming-client-endpoint" write-1] TRACE org.xnio.nio  - CAS org.xnio.nio.NioXnioWorker@77fddc31 80000001 -> 80000000

      192  [Remoting "config-based-naming-client-endpoint" write-1] TRACE org.xnio.nio  - CAS org.xnio.nio.NioXnioWorker@77fddc31 80000000 -> c0000000 (close complete)

      192  [Remoting "config-based-naming-client-endpoint" write-1] TRACE org.jboss.remoting.resource  - Completed close of endpoint "config-based-naming-client-endpoint" <47315d34>

       

       

      I've had various errors but always seem to come back to this one.  I had never used a user in the application realm, but added one to test that, and got past the connection errors.  So now it seems to be a simple lookup error, but I can't figure out what it is and seem to be going in circles.

       

      Any help would be appreciated.

       

      Lance

        • 1. Re: Unable to get remote connection to connect via ejb:/
          Wolf-Dieter Fink Master

          Hello Lance,

           

          the problem is that you mix two different approaches, the ejb-client and the remote-naming project.

          If you use the InitialContext and the URL "remote://...." this it remote naming in this case you do not have to add the ejb: prefix and don't add a jboss-ejb-client.properties.

           

          The recommended way is the ejb-client, add the jboss-ejb-client.properties to the classpath and ONLY Context.URL_PKG_PREFIXES, "org.jboss.ejb.client.naming" to the IC properties.

          Than use the name with ejb: prefix for lookup.

          • 2. Re: Unable to get remote connection to connect via ejb:/
            Lance Goforth Newbie

            I added to the jboss-ejb-client.properties file these two lines:

             

             

            remote.connection.default.host=10.110.40.25

            remote.connection.default.port=4447

             

            I changed the getInitialContext() method to:

             

             

                      public Context getInitialContext() throws NamingException {

                                InitialContext initialContext = null;

             

                    Properties jndiProperties = new Properties();

                    jndiProperties.put(Context.URL_PKG_PREFIXES, "org.jboss.ejb.client.naming");

             

                    initialContext = new InitialContext(jndiProperties);

             

                                return initialContext;

                      }

             

             

            The result is this:

             

            0    [main] DEBUG com.psasoft.tools  -   jndi lookup: >ejb:/psa-server-jboss-ejb3//SecurityEntityManagerEJB!com.psasoft.security.interfaces.SecurityEntityManager

            1    [main] DEBUG com.psasoft.tools  - 

            19   [main] DEBUG org.jboss.logging  - Logging Provider: org.jboss.logging.Log4jLoggerProvider

            42   [main] INFO  org.jboss.ejb.client  - JBoss EJB Client version 1.0.21.Final-redhat-1

            54   [main] DEBUG org.jboss.ejb.client.EJBClientPropertiesLoader  - Looking for jboss-ejb-client.properties using classloader sun.misc.Launcher$AppClassLoader@69cd2e5f

            70   [main] DEBUG org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector  - EJB client context org.jboss.ejb.client.EJBClientContext@462ba11b will have no EJB receivers associated with it since there was no EJB client configuration available to create the receivers

            Exception in thread "main" java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:psa-server-jboss-ejb3, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@30ec4a87

                      at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:727)

                      at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:116)

                      at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)

                      at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:253)

                      at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:198)

                      at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:181)

                      at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:144)

                      at com.sun.proxy.$Proxy0.validateUsername(Unknown Source)

                      at com.psasoft.tools.TestRemoteConnection.<init>(TestRemoteConnection.java:33)

                      at com.psasoft.tools.TestRemoteConnection.main(TestRemoteConnection.java:18)

             

            Basically the same result but with less output.

            • 3. Re: Unable to get remote connection to connect via ejb:/
              Wolf-Dieter Fink Master

              Do you have changes in the security configuration and use a different Realm? This is because you call a SecurityEntityManagerEJB.

              How your server.log show the deployment name

              • 4. Re: Unable to get remote connection to connect via ejb:/
                Lance Goforth Newbie

                No, it's just called SecurityEntityManagerEJB because it controls the user access to our own application, it has nothing to do with JBoss security.  It was just the first bean called in the application so it was the one I was testing with.

                 

                The deployment log shows this is the jndi info for that bean:

                 

                 

                09:27:03,616 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named SecurityEntityManagerEJB in deployment unit deployment "psa-server-jboss-ejb3.jar" are as follows:

                 

                 

                          java:global/psa-server-jboss-ejb3/SecurityEntityManagerEJB!com.psasoft.security.interfaces.SecurityEntityManagerLocal

                          java:app/psa-server-jboss-ejb3/SecurityEntityManagerEJB!com.psasoft.security.interfaces.SecurityEntityManagerLocal

                          java:module/SecurityEntityManagerEJB!com.psasoft.security.interfaces.SecurityEntityManagerLocal

                          java:global/psa-server-jboss-ejb3/SecurityEntityManagerEJB!com.psasoft.security.interfaces.SecurityEntityManager

                          java:app/psa-server-jboss-ejb3/SecurityEntityManagerEJB!com.psasoft.security.interfaces.SecurityEntityManager

                          java:module/SecurityEntityManagerEJB!com.psasoft.security.interfaces.SecurityEntityManager

                          java:jboss/exported/psa-server-jboss-ejb3/SecurityEntityManagerEJB!com.psasoft.security.interfaces.SecurityEntityManager

                 

                • 5. Re: Unable to get remote connection to connect via ejb:/
                  Wolf-Dieter Fink Master

                  I don't see a mistake here at the moment

                  Do you have tried a the ejb-remote quickstart?

                   

                  I need to check whether a jar deployment is different to ear.

                  Hope will find a bit time next week.

                  • 6. Re: Unable to get remote connection to connect via ejb:/
                    Lance Goforth Newbie

                    My test I posted was based on the ejb-remote quickstart. 

                     

                    I could try the module being ".jar" if it makes a difference to the deployment.

                    • 7. Re: Unable to get remote connection to connect via ejb:/
                      Lance Goforth Newbie

                      Adding ".jar" to the module didn't make any difference.

                       

                      Removing the module entirely changed the message.  That resulted in the jndi name being:

                       

                      ejb:/SecurityEntityManagerEJB!com.psasoft.security.interfaces.SecurityEntityManager

                       

                      And the error resulting is:

                       

                      Exception in thread "main" java.lang.ClassCastException: org.jboss.ejb.client.naming.ejb.EjbNamingContext cannot be cast to com.psasoft.security.interfaces.SecurityEntityManager

                          at com.psasoft.tools.TestRemoteConnection.<init>(TestRemoteConnection.java:31)

                          at com.psasoft.tools.TestRemoteConnection.main(TestRemoteConnection.java:18)

                       

                      Kind of like the initial context worked, but the returned object from the lookup wasn't the interface I was expecting.

                      • 8. Re: Unable to get remote connection to connect via ejb:/
                        Wolf-Dieter Fink Master

                        Did not meant to add .jar to the module.

                         

                        What do you deploy, from the JNDI name it looks like you deploy the application only in a JAR file and not as a EAP with application XML.

                        Or did you use an ear and change app-name and module name via descriptor?

                        Could you show the deployment structure and the DD?

                        • 9. Re: Unable to get remote connection to connect via ejb:/
                          Lance Goforth Newbie

                          I have always deployed it as a single jar file, and have never used an application xml.

                           

                          What do you wish to see for the deployment structure?

                           

                          I have a persistence.xml in the META-INF of the jar I'm deploying, I have a dependancy list in the manifest of the jar - I'm not sure what else you are asking?

                          • 10. Re: Unable to get remote connection to connect via ejb:/
                            Lance Goforth Newbie

                            I thought I would try deploying with an EAR file to see if it made any difference.  I added this application.xml file:

                             

                            <application>

                              <display-name>PSA EJB3 Server</display-name>

                             

                              <module>

                                <ejb>psa-server-jboss-ejb3.jar</ejb>

                              </module>

                             

                            </application>

                             

                            And the deployment jdni messages were:

                             


                            java:global/psa-ejb3/psa-server-jboss-ejb3/SecurityEntityManagerEJB!com.psasoft.security.interfaces.SecurityEntityManagerLocal

                            java:app/psa-server-jboss-ejb3/SecurityEntityManagerEJB!com.psasoft.security.interfaces.SecurityEntityManagerLocal

                            java:module/SecurityEntityManagerEJB!com.psasoft.security.interfaces.SecurityEntityManagerLocal

                            java:global/psa-ejb3/psa-server-jboss-ejb3/SecurityEntityManagerEJB!com.psasoft.security.interfaces.SecurityEntityManager

                            java:app/psa-server-jboss-ejb3/SecurityEntityManagerEJB!com.psasoft.security.interfaces.SecurityEntityManager

                            java:module/SecurityEntityManagerEJB!com.psasoft.security.interfaces.SecurityEntityManager

                            java:jboss/exported/psa-ejb3/psa-server-jboss-ejb3/SecurityEntityManagerEJB!com.psasoft.security.interfaces.SecurityEntityManager

                             

                            So I changed my test jdni to

                             

                            >ejb:psa-ejb3/psa-server-jboss-ejb3/SecurityEntityManagerEJB!com.psasoft.security.interfaces.SecurityEntityManager

                            But got basically the same error

                             

                            44   [main] INFO  org.jboss.ejb.client  - JBoss EJB Client version 1.0.21.Final-redhat-1

                            56   [main] DEBUG org.jboss.ejb.client.EJBClientPropertiesLoader  - Looking for jboss-ejb-client.properties using classloader sun.misc.Launcher$AppClassLoader@69cd2e5f

                            72   [main] DEBUG org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector  - EJB client context org.jboss.ejb.client.EJBClientContext@785f8172 will have no EJB receivers associated with it since there was no EJB client configuration available to create the receivers

                            Exception in thread "main" java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:psa-ejb3, moduleName:psa-server-jboss-ejb3, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@2087c268

                                      at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:727)

                                      at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:116)

                                      at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)

                                      at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:253)

                                      at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:198)

                                      at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:181)

                                      at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:144)

                                      at com.sun.proxy.$Proxy0.validateUsername(Unknown Source)

                                      at com.psasoft.tools.TestRemoteConnection.<init>(TestRemoteConnection.java:33)

                                      at com.psasoft.tools.TestRemoteConnection.main(TestRemoteConnection.java:18)

                             

                             

                            If it is of any use - I was also looking at the web management console and trying to view the JDNI Bindings when the server threw several errors on some of my modules.  The security module included which was:

                             

                            15:35:53,501 ERROR [org.jboss.as.naming] (HttpManagementService-threads - 9) JBAS011812: Failed to obtain jndi view value for entry java:PSA-Security-EntityManagerFactory.: javax.naming.NameNotFoundException: PSA-Security-EntityManagerFactory -- service jboss.naming.context.java.jboss.PSA-Security-EntityManagerFactory

                                      at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:103) [jboss-as-naming-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]

                                      at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:197) [jboss-as-naming-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]

                                      at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:183) [jboss-as-naming-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]

                                      at org.jboss.as.naming.management.JndiViewOperation.addEntries(JndiViewOperation.java:134) [jboss-as-naming-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]

                                      at org.jboss.as.naming.management.JndiViewOperation.access$000(JndiViewOperation.java:49) [jboss-as-naming-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]

                                      at org.jboss.as.naming.management.JndiViewOperation$1.execute(JndiViewOperation.java:74) [jboss-as-naming-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]

                                      at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:440) [jboss-as-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]

                                      at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:322) [jboss-as-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]

                                      at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:229) [jboss-as-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]

                                      at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:224) [jboss-as-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]

                                      at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:194) [jboss-as-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]

                                      at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:115) [jboss-as-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]

                                      at org.jboss.as.controller.ModelControllerImpl$3.execute(ModelControllerImpl.java:398) [jboss-as-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]

                                      at org.jboss.as.controller.ModelControllerImpl$3.execute(ModelControllerImpl.java:388) [jboss-as-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]

                                      at org.jboss.as.domain.http.server.DomainApiHandler.processRequest(DomainApiHandler.java:320)

                                      at org.jboss.as.domain.http.server.DomainApiHandler.doHandle(DomainApiHandler.java:226)

                                      at org.jboss.as.domain.http.server.DomainApiHandler.handle(DomainApiHandler.java:233)

                                      at org.jboss.as.domain.http.server.security.SubjectAssociationHandler.handle(SubjectAssociationHandler.java:51)

                                      at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78)

                                      at org.jboss.sun.net.httpserver.AuthFilter.doFilter(AuthFilter.java:69)

                                      at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:81)

                                      at org.jboss.sun.net.httpserver.ServerImpl$Exchange$LinkHandler.handle(ServerImpl.java:710)

                                      at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78)

                                      at org.jboss.as.domain.http.server.RealmReadinessFilter.doFilter(RealmReadinessFilter.java:47)

                                      at org.jboss.as.domain.http.server.DmrFailureReadinessFilter.doFilter(DmrFailureReadinessFilter.java:45)

                                      at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:81)

                                      at org.jboss.sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:682)

                                      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_11]

                                      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_11]

                                      at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_11]

                                      at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final-redhat-1.jar:2.1.0.Final-redhat-1]

                             

                            And if it makes any difference - I'm not on a redhat distribution of linux, but on Slackware 12.2

                            • 11. Re: Unable to get remote connection to connect via ejb:/
                              Wolf-Dieter Fink Master

                              So let me ask some dumb questions:

                               

                              - does the client classpath include the correct jboss-client.jar from EAP61/bin/client?

                              - are you on the same system? If not does the client work if using localhost?

                              - how do you start the server with -b0.0.0.0 or ip address?

                              - is there a firewall in between blocking ports

                              - do you connect the correct server?

                              - how the remoting connector is configured regarding security? Do you change the default config? What if you remove the security-realm from the remoting connector - you should be able to connect without user/psw

                              • 12. Re: Unable to get remote connection to connect via ejb:/
                                Lance Goforth Newbie

                                I removed everything from my classpath down to bare bones - and made sure the jboss-client.jar was the one from the eap61/bin/client, so yes, I'm pretty sure it's the right one.

                                 

                                Not on the same system - I have the EAP 6.1 on the same server that I had the AS 7.2 alpha that was working - the client is on my local machine.  Since the 7.2 was working, that eliminates the firewall issue too.

                                 

                                I don't start it with -b - but just sh standalone.sh right now - I have the ip set in the standalone.xml - should there be another entry for name="remoting" ?

                                 

                                    <interfaces>

                                        <interface name="management"> 

                                            <inet-address value="${jboss.bind.address.management:10.110.40.25}"/>

                                        </interface>

                                        <interface name="public">

                                            <inet-address value="${jboss.bind.address:10.110.40.25}"/>

                                        </interface>

                                        <interface name="unsecure">

                                            <inet-address value="${jboss.bind.address.unsecure:10.110.40.25}"/>

                                        </interface>

                                    </interfaces>

                                 

                                 

                                I changed the standalone.xml remoting section to be:

                                 

                                        <subsystem xmlns="urn:jboss:domain:remoting:1.1">

                                            <connector name="remoting-connector" socket-binding="remoting" />

                                        </subsystem>

                                 

                                and removed the username and password from the jboss-ejb-client.properties file, with no changes.

                                • 13. Re: Unable to get remote connection to connect via ejb:/
                                  Lance Goforth Newbie

                                  Did I miss answering any of your questions?