14 Replies Latest reply on Apr 16, 2012 4:28 AM by Gerd Wagner Branched to a new discussion.

    JBoss 7.1: Server to server communication

    Gerd Wagner Newbie

      Hi,

       

      I'm using two standalone JBoss 7.1.1 servers A,B. From inside a bean method on server A I try to lookup a remote bean on server B. The lookup code I tried is:

       

           Properties props = new Properties();

           props.put("endpoint.name","endpoint");

           props.put("remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED","false");

           props.put("remote.connections","default");

           props.put("remote.connection.default.host","pcgwa-and");

           props.put("remote.connection.default.port","4547");

           props.put("remote.connection.default.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS","false");

           EJBClientConfiguration ejbClientConfiguration = new PropertiesBasedEJBClientConfiguration(props);

           ContextSelector<EJBClientContext> ejbClientContextSelector = new ConfigBasedEJBClientContextSelector(ejbClientConfiguration);

           EJBClientContext.setSelector(ejbClientContextSelector);

       

           Properties env = new Properties();

           env.put(Context.INITIAL_CONTEXT_FACTORY, org.jboss.naming.remote.client.InitialContextFactory.class.getName());

           env.put(Context.PROVIDER_URL, "remote://pcgwa-and:4547");

           env.put(Context.SECURITY_PRINCIPAL, "admin");

           env.put(Context.SECURITY_CREDENTIALS, "SHD_APP");

           InitialContext context = new InitialContext(env);

          

           CentralConnection centralCon = (CentralConnection) context.lookup("ejb:pos.central/pos.central-ejb/CentralConnectionBean!de.shd.pos.central.spi.CentralConnection");

       

      This code works fine if I use it from a simple Java client (main method). If I use it from inside a Bean method I get the following exception

      1. ava.lang.SecurityException: EJB client context selector may not be changed

                      at org.jboss.ejb.client.EJBClientContext.setSelector(EJBClientContext.java:181)

       

      What is the right way to access a remote bean on server B from inside a bean method on server A?

       

      Thanks in advance

       

      Gerd

        • 1. Re: JBoss 7.1: Server to server communication
          jaikiran pai Master

          Gerd, welcome to the forums!

           

          Gerd Wagner wrote:

           

          What is the right way to access a remote bean on server B from inside a bean method on server A?

           

          See https://docs.jboss.org/author/display/AS71/EJB+invocations+from+a+remote+server+instance

          • 2. Re: JBoss 7.1: Server to server communication
            Gerd Wagner Newbie

            Thanks jaikiran for your quick answer. I just had to solve some security issues on the destination side that weren't mentioned in your article, see https://community.jboss.org/message/721362#721362.

            After that it worked alright.

             

            Playing around with the two servers I found that when the destination server goes down, the client server has no chance to reconnect. Is there a way to get around this problem?

            • 3. Re: JBoss 7.1: Server to server communication
              jaikiran pai Master

              Gerd Wagner wrote:

               

               

              Playing around with the two servers I found that when the destination server goes down, the client server has no chance to reconnect. Is there a way to get around this problem?

              The reconnect is expected to happen automatically when the destination server is up again and when the client tries an invocation on the bean. Is that not happening? Can you provide more details including any exception stacktraces?

              • 4. Re: JBoss 7.1: Server to server communication
                Gerd Wagner Newbie

                Reconnect does not work for me in the following case:

                 

                Im running both servers on the same Win 7 machine. Node names and port offset is set as described in

                https://docs.jboss.org/author/display/AS71/EJB+invocations+from+a+remote+server+instance

                 

                My JVM version is:

                java version "1.7.0"

                Java(TM) SE Runtime Environment (build 1.7.0-b147)

                Java HotSpot(TM) 64-Bit Server VM (build 21.0-b17, mixed mode)

                Servers are run in CMD/DOS boxes and are started using batch files.

                 

                Scenario:

                - Start destination server and wait till it's up then start client server.

                - Test will work alright

                - Stop destination server by closing its CMD window

                - Client server will issue

                    ERROR [org.jboss.remoting.remote.connection] (Remoting "store" read-1) JBREM000200: Remote connection failed: java.io.IOException: Eine vorhandene Verbindung wurde vom Remotehost geschlossen (= An existing connection was closed by the remote host)

                 

                - Restart destination server

                - Any further test will fail with the exception quoted below.

                 

                Note: The problem does not occur when the destination server is stopped by using ctrl+c in the command window.

                 

                 

                 

                 

                 

                08:30:03,784 ERROR [org.jboss.ejb3.invocation] (EJB default - 4) JBAS014134: EJB Invocation failed on component HelloBean for method public abstract java.lang.String gerd.ejb.Hello.sayDestHello(): jav

                ax.ejb.EJBException: java.lang.RuntimeException: java.lang.IllegalStateException: No EJB receiver available for handling [appName:destTest1App,modulename:destTest1Ejb,distinctname:] combination for in

                vocation context org.jboss.ejb.client.EJBClientInvocationContext@6e5f8fab

                        at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:166) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]

                        at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:230) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]

                        at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:304) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]

                        at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:190) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]

                        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]

                        at org.jboss.as.ejb3.remote.EJBRemoteTransactionPropagatingInterceptor.processInvocation(EJBRemoteTransactionPropagatingInterceptor.java:80) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]

                        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]

                        at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]

                        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]

                        at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]

                        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]

                        at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]

                        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]

                        at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:43) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]

                        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]

                        at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]

                        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]

                        at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]

                        at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]

                        at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.invokeMethod(MethodInvocationMessageHandler.java:302) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]

                        at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$200(MethodInvocationMessageHandler.java:64) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]

                        at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:196) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]

                        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0]

                        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0]

                        at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0]

                        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0]

                        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0]

                        at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0]

                        at org.jboss.threads.JBossThread.run(JBossThread.java:122)

                Caused by: java.lang.RuntimeException: java.lang.IllegalStateException: No EJB receiver available for handling [appName:destTest1App,modulename:destTest1Ejb,distinctname:] combination for invocation c

                ontext org.jboss.ejb.client.EJBClientInvocationContext@6e5f8fab

                        at gerd.ejb.HelloBean.sayDestHello(HelloBean.java:130) [test1Ejb.jar:]

                        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0]

                        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0]

                        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0]

                        at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0]

                        at org.jboss.as.ee.component.ManagedReferenceMethodInterceptorFactory$ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptorFactory.java:72) [jboss-as-ee-7.1.1.F

                inal.jar:7.1.1.Final]

                        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]

                        at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]

                        at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:36) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]

                        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]

                        at org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47)

                        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]

                        at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]

                        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]

                        at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]

                        at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:53) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]

                        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]

                        at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]

                        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]

                        at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:228) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]

                        ... 27 more

                Caused by: java.lang.IllegalStateException: No EJB receiver available for handling [appName:destTest1App,modulename:destTest1Ejb,distinctname:] combination for invocation context org.jboss.ejb.client.

                EJBClientInvocationContext@6e5f8fab

                        at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:584) [jboss-ejb-client-1.0.5.Final.jar:1.0.5.Final]

                        at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:119) [jboss-ejb-client-1.0.5.Final.jar:1.0.5.Final]

                        at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:181) [jboss-ejb-client-1.0.5.Final.jar:1.0.5.Final]

                        at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136) [jboss-ejb-client-1.0.5.Final.jar:1.0.5.Final]

                        at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121) [jboss-ejb-client-1.0.5.Final.jar:1.0.5.Final]

                        at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104) [jboss-ejb-client-1.0.5.Final.jar:1.0.5.Final]

                        at $Proxy15.sayDestHello(Unknown Source)        at gerd.ejb.HelloBean.sayDestHello(HelloBean.java:123) [test1Ejb.jar:]

                        ... 46 more

                • 5. Re: JBoss 7.1: Server to server communication
                  jaikiran pai Master

                  - Stop destination server by closing its CMD window

                  - Client server will issue

                      ERROR [org.jboss.remoting.remote.connection] (Remoting "store" read-1) JBREM000200: Remote connection failed: java.io.IOException: Eine vorhandene Verbindung wurde vom Remotehost geschlossen (= An existing connection was closed by the remote host)

                   

                  - Restart destination server

                  - Any further test will fail with the exception quoted below.

                   

                  Note: The problem does not occur when the destination server is stopped by using ctrl+c in the command window.

                  Are you sure when you close the CMD window and then restart the destination server, the destination server starts cleanly? Do you see anything in the logs?

                  • 6. Re: JBoss 7.1: Server to server communication
                    Gerd Wagner Newbie

                    Here's the complete output of the restart after closing the CMD window:

                     

                     

                    D:\kassetools\jboesse7>D:\kassetools\jboesse7\central\jboss-as-7.1.1.Final\bin\standalone.bat -server-config=standalone-full.xml -Djboss.node.name=central -Djboss.socket.binding.port-offset=100

                    Calling "D:\kassetools\jboesse7\central\jboss-as-7.1.1.Final\bin\standalone.conf.bat"

                    ===============================================================================

                     

                      JBoss Bootstrap Environment

                     

                      JBOSS_HOME: D:\kassetools\jboesse7\central\jboss-as-7.1.1.Final

                     

                      JAVA: C:\jdk1.7.0_x64\bin\java

                     

                      JAVA_OPTS: -XX:+TieredCompilation -Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.prefe

                    rIPv4Stack=true -Dorg.jboss.resolver.warning=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djboss.server.default.config=standalone.xml -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,ad

                    dress=5006

                     

                    ===============================================================================

                     

                    Listening for transport dt_socket at address: 5006

                    10:17:40,463 Information [org.jboss.modules] JBoss Modules version 1.1.1.GA

                    10:17:40,608 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA

                    10:17:40,644 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting

                    10:17:41,287 INFO  [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)

                    10:17:41,287 INFO  [org.xnio] XNIO Version 3.0.3.GA

                    10:17:41,295 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA

                    10:17:41,301 INFO  [org.jboss.remoting] JBoss Remoting version 3.2.3.GA

                    10:17:41,320 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers

                    10:17:41,327 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 37) JBAS010280: Activating Infinispan subsystem.

                    10:17:41,323 INFO  [org.jboss.as.configadmin] (ServerService Thread Pool -- 32) JBAS016200: Activating ConfigAdmin Subsystem

                    10:17:41,334 INFO  [org.jboss.as.jacorb] (ServerService Thread Pool -- 38) JBAS016300: Activating JacORB Subsystem

                    10:17:41,348 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 54) JBAS013101: Activating Security Subsystem

                    10:17:41,350 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 58) JBAS015537: Activating WebServices Extension

                    10:17:41,351 INFO  [org.jboss.as.osgi] (ServerService Thread Pool -- 49) JBAS011940: Activating OSGi Subsystem

                    10:17:41,352 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 48) JBAS011800: Activating Naming Subsystem

                    10:17:41,352 INFO  [org.jboss.as.security] (MSC service thread 1-10) JBAS013100: Current PicketBox version=4.0.7.Final

                    10:17:41,382 INFO  [org.jboss.as.connector] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)

                    10:17:41,449 INFO  [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on pcgwa-and/192.168.15.116:4547

                    10:17:41,459 INFO  [org.jboss.as.naming] (MSC service thread 1-15) JBAS011802: Starting Naming Service

                    10:17:41,463 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-9) JBAS015400: Bound mail session [java:jboss/mail/Default]

                    10:17:41,468 INFO  [org.jboss.jaxr] (MSC service thread 1-15) JBAS014000: Started JAXR subsystem, binding JAXR connection factory into JNDI as: java:jboss/jaxr/ConnectionFactory

                    10:17:41,473 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

                    10:17:41,487 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) JBAS010404: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.0)

                    10:17:41,496 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) JBAS010403: Deploying JDBC-compliant driver class com.intersys.jdbc.CacheDriver (version 2010.1)

                    10:17:41,511 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-14) Starting Coyote HTTP/1.1 on http-pcgwa-and-192.168.15.116-8180

                    10:17:41,539 WARN  [org.jboss.as.messaging] (MSC service thread 1-7) JBAS011600: AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAI

                    O to enable the AIO journal

                    10:17:41,543 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-8) JBoss Web Services - Stack CXF Server 4.0.2.GA

                    10:17:41,588 Information [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-6) live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,shared

                    Store=true,journalDirectory=D:\kassetools\jboesse7\central\jboss-as-7.1.1.Final\standalone\data\messagingjournal,bindingsDirectory=D:\kassetools\jboesse7\central\jboss-as-7.1.1.Final\standalone\data\m

                    essagingbindings,largeMessagesDirectory=D:\kassetools\jboesse7\central\jboss-as-7.1.1.Final\standalone\data\messaginglargemessages,pagingDirectory=D:\kassetools\jboesse7\central\jboss-as-7.1.1.Final\s

                    tandalone\data\messagingpaging)

                    10:17:41,593 Information [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-6) Waiting to obtain live lock

                    10:17:41,640 INFO  [org.hornetq.core.persistence.impl.journal.JournalStorageManager] (MSC service thread 1-6) Using NIO Journal

                    10:17:41,711 INFO  [org.hornetq.core.server.impl.FileLockNodeManager] (MSC service thread 1-6) Waiting to obtain live lock

                    10:17:41,713 INFO  [org.hornetq.core.server.impl.FileLockNodeManager] (MSC service thread 1-6) Live Server Obtained live lock

                    10:17:41,719 INFO  [org.jboss.as.remoting] (MSC service thread 1-10) JBAS017100: Listening on PCGWA-AND/192.168.15.116:10099

                    10:17:41,723 WARN  [jacorb.codeset] (MSC service thread 1-11) Warning - unknown codeset (Cp1252) - defaulting to ISO-8859-1

                    10:17:41,737 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-12) JBAS015012: Started FileSystemDeploymentService for directory D:\kassetools\jboesse7\central\jboss-as-7.1.1.Final\

                    standalone\deployments

                    10:17:41,760 INFO  [org.jboss.as.jacorb] (MSC service thread 1-11) JBAS016330: CORBA ORB Service started

                    10:17:41,812 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) JBAS010400: Bound data source [java:jboss/datasources/erpDS]

                    10:17:41,813 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/posDS]

                    10:17:41,812 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]

                    10:17:41,830 INFO  [org.jboss.as.jacorb] (MSC service thread 1-4) JBAS016328: CORBA Naming Service started

                    10:17:41,974 INFO  [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-6) Started Netty Acceptor version 3.2.5.Final-a96d88c pcgwa-and:5555 for CORE protocol

                    10:17:41,976 INFO  [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-6) Started Netty Acceptor version 3.2.5.Final-a96d88c pcgwa-and:5545 for CORE protocol

                    10:17:41,977 Information [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-6) Server is now live

                    10:17:41,977 Information [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-6) HornetQ Server version 2.2.13.Final (HQ_2_2_13_FINAL_AS7, 122) [6fab93b2-849e-11e1-b488-de8220524153]

                    ) started

                    10:17:41,980 Information [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-11) trying to deploy queue jms.topic.testTopic

                    10:17:42,000 INFO  [org.jboss.as.messaging] (MSC service thread 1-11) JBAS011601: Bound messaging object to jndi name java:/topic/test

                    10:17:42,002 INFO  [org.jboss.as.messaging] (MSC service thread 1-11) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/topic/test

                    10:17:42,016 INFO  [org.jboss.as.messaging] (MSC service thread 1-6) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory

                    10:17:42,017 INFO  [org.jboss.as.messaging] (MSC service thread 1-5) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory

                    10:17:42,018 INFO  [org.jboss.as.messaging] (MSC service thread 1-5) JBAS011601: Bound messaging object to jndi name java:/RemoteConnectionFactory

                    10:17:42,019 Information [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) trying to deploy queue jms.queue.testQueue

                    10:17:42,026 INFO  [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011601: Bound messaging object to jndi name java:/queue/test

                    10:17:42,026 INFO  [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/test

                    10:17:42,030 INFO  [org.jboss.as.deployment.connector] (MSC service thread 1-7) JBAS010406: Registered connection factory java:/JmsXA

                    10:17:42,038 INFO  [org.hornetq.ra.HornetQResourceAdapter] (MSC service thread 1-7) HornetQ resource adaptor started

                    10:17:42,039 INFO  [org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-7) IJ020002: Deployed: file://RaActivatorhornetq-ra

                    10:17:42,041 INFO  [org.jboss.as.deployment.connector] (MSC service thread 1-3) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]

                    10:17:42,216 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "destTest1App.ear"

                    10:17:42,247 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "destTest1Ejb.jar"

                    10:17:42,320 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-12) JNDI bindings for session bean named DestHelloBean in deployment unit subd

                    eployment "destTest1Ejb.jar" of deployment "destTest1App.ear" are as follows:

                     

                            java:global/destTest1App/destTest1Ejb/DestHelloBean!gerd.dest.ri.DestHello

                            java:app/destTest1Ejb/DestHelloBean!gerd.dest.ri.DestHello

                            java:module/DestHelloBean!gerd.dest.ri.DestHello

                            java:jboss/exported/destTest1App/destTest1Ejb/DestHelloBean!gerd.dest.ri.DestHello

                            java:global/destTest1App/destTest1Ejb/DestHelloBean

                            java:app/destTest1Ejb/DestHelloBean

                            java:module/DestHelloBean

                     

                    10:17:42,415 INFO  [org.jboss.as] (MSC service thread 1-10) JBAS015951: Admin console listening on http://192.168.15.116:10090

                    10:17:42,416 INFO  [org.jboss.as] (MSC service thread 1-10) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 2153ms - Started 240 of 325 services (82 services are passive or on-demand)

                    10:17:42,446 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "destTest1App.ear"

                    • 7. Re: JBoss 7.1: Server to server communication
                      jaikiran pai Master

                      Can you enable TRACE level logs of org.jboss.ejb.client package on the client server and get those logs when you close the CMD window on the destination window? Please attach those logs.

                      • 8. Re: JBoss 7.1: Server to server communication
                        jaikiran pai Master

                        Also please get the logs (separately) for the same package from the client server when you do a Ctrl+C on the destination server.

                        • 9. Re: JBoss 7.1: Server to server communication
                          Gerd Wagner Newbie

                          Logs:

                          Dest_Server_After_Close_Window.log --> Log of destination server restart after last run was ended with window close.

                          Dest_Server_After_Ctrl_C.log --> Log of destination server restart after last run was ended with Ctrl C.

                          • 10. Re: JBoss 7.1: Server to server communication
                            jaikiran pai Master

                            I was actually expecting the logs from the client server when you shutdown the destination server

                            • 11. Re: JBoss 7.1: Server to server communication
                              Gerd Wagner Newbie

                              Attached the client side logs:

                              Client_Server_After_Dest_Close_Window.log --> Log of client running when destination server was shut down using window close.

                              Client_Server_After_Dest_Ctrl_C.log --> Log of client running when destination server was shut down using Ctrl C.

                              • 12. Re: JBoss 7.1: Server to server communication
                                jaikiran pai Master

                                I suspect it's related to https://issues.jboss.org/browse/AS7-4510. I've sent a pull request containing a fix for that. Once it's merged upstream, I'll let you know and you can try the latest AS7 build.

                                • 13. Re: JBoss 7.1: Server to server communication
                                  jaikiran pai Master

                                  The pull request for this has been merged upstream, so you can try this against the latest nightly build https://community.jboss.org/thread/167590

                                  1 of 1 people found this helpful