1 2 Previous Next 27 Replies Latest reply: May 15, 2012 10:05 AM by Arnold Johansson RSS

    Cluster to Cluster EJB Call

    Graeme Wallace Newbie

      From jaikiran pai

       

      "https://docs.jboss.org/author/display/AS71/Clustered+EJBs once the initial node to connect to is known, the cluster topology will be sent back to the client. The client then auto-connects to the nodes within the cluster as and when appropriate. During auto connect, it requires certain configurations for the node (like security configurations) that have to be configured in the jboss-ejb-client.xml (if your client is a AS7 instance itself) or jboss-ejb-client.properties (for standalone clients).

       

      The jboss-ejb-client.xml xsd is here and allows you to configure the cluster configurations either at each node level or for all nodes within a named cluster  https://github.com/jbossas/jboss-as/blob/master/build/src/main/resources/docs/schema/jboss-ejb-client_1_1.xsd#L66

       

      Here's an example of jboss-ejb-client.xml from a testsuite which shows an example https://github.com/jbossas/jboss-as/blob/master/testsuite/integration/manualmode/src/test/java/org/jboss/as/test/manualmode/ejb/client/cluster/jboss-ejb-client.xml.

       

      Feel free to ask if you have more questions around this. "

       

       

       

      I've tried to configure the above but I'm stuck on the JBoss to JBoss configuration.

       

      I've created the jboss-ejb-client.xml as follows

       

      <jboss-ejb-client xmlns="urn:jboss:ejb-client:1.1">

          <client-context>

              <ejb-receivers>

                  <remoting-ejb-receiver outbound-connection-ref="remote-ejb-connection"/>

              </ejb-receivers>

              <clusters>

                  <cluster name="ejb" max-allowed-connected-nodes="20" cluster-node-selector="com.xxi.framework.jbossaux.cluster.RoundRobinClusterNodeSelector" connect-timeout="5000" security-realm="PasswordRealm">

                      <connection-creation-options>

                          <property name="org.xnio.Options.SSL_ENABLED" value="false"/>

                          <property name="org.xnio.Options.SASL_POLICY_NOANONYMOUS" value="true"/>

                      </connection-creation-options>

                  </cluster>

              </clusters>

          </client-context>

      </jboss-ejb-client>

       

      I know it gets picked up and read by JBoss - because if i put a dummy class name in for the cluster-node-selector it complains about ClassNotFound. (However i HAVE to put in a security-realm attribute and value otherwise the xml parsing code complains)

       

      JBoss starts successfully. I can do the lookup to the remote EJB and I can make a remote method call.

      However, the class specified in the cluster-node-selector value never gets instantiated and obviously never gets called either.

       

      On startup the following messages are printed out from remoting

       

      21:42:30,865 INFO  [org.jboss.ejb.client.remoting.VersionReceiver] (Remoting "cmc5-104" task-4) Received server version 1 and marshalling strategies [river]

      21:42:30,874 INFO  [org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver] (MSC service thread 1-6) Successful version handshake completed for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@148fc86f, receiver=Remoting connection EJB receiver [connection=Remoting connection <378fc5db>,channel=jboss.ejb,nodename=cmc5-101]} on channel Channel ID ef00ec9a (outbound) of Remoting connection 242d8a8c to cmc5-101.alpha.farecompare.com/192.168.12.161:4447

      21:42:30,875 WARN  [org.jboss.ejb.client.remoting.ChannelAssociation] (Remoting "cmc5-104" task-1) Unsupported message received with header 0xffffffff

       

      It doesnt look like remoting is being told about the other node in the cluster - as if i run a standalone client i get

       

      INFO: JBoss Remoting version 3.2.4.GA

      Apr 23, 2012 9:26:18 PM org.jboss.ejb.client.remoting.VersionReceiver handleMessage

      INFO: Received server version 1 and marshalling strategies [river]

      Apr 23, 2012 9:26:18 PM org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver associate

      INFO: Successful version handshake completed for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@4ee993e, receiver=Remoting connection EJB receiver [connection=Remoting connection <cfed7c>,channel=jboss.ejb,nodename=cmc5-101]} on channel Channel ID d2dfe8e4 (outbound) of Remoting connection 35b4e829 to cmc5-101.alpha.farecompare.com/192.168.12.161:4447

      Apr 23, 2012 9:26:18 PM org.jboss.ejb.client.remoting.ChannelAssociation$ResponseReceiver handleMessage

      WARN: Unsupported message received with header 0xffffffff

      Apr 23, 2012 9:26:18 PM org.jboss.ejb.client.remoting.VersionReceiver handleMessage

      INFO: Received server version 1 and marshalling strategies [river]

      Apr 23, 2012 9:26:18 PM org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver associate

      INFO: Successful version handshake completed for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@4ee993e, receiver=Remoting connection EJB receiver [connection=Remoting connection <23cb7f34>,channel=jboss.ejb,nodename=cmc5-102]} on channel Channel ID f2c475f8 (outbound) of Remoting connection 2aa49512 to cmc5-102.alpha.farecompare.com/192.168.12.162:4447

      Apr 23, 2012 9:26:18 PM org.jboss.ejb.client.remoting.ChannelAssociation$ResponseReceiver handleMessage

      WARN: Unsupported message received with header 0xffffffff

      Apr 23, 2012 9:26:18 PM org.jboss.ejb.client.EJBClient <clinit>

      INFO: JBoss EJB Client version 1.0.6.CR1

       

      where it receives info on both nodes in the cluster.

       

      Am i missing another piece of the configuration for the server to server call to get clustering to work or is this a bug ?

        • 1. Re: Cluster to Cluster EJB Call
          jaikiran pai Master

          What do your deployments look like and where is the client located? Where are the target beans deployed? On both servers or just the remote server?

          • 2. Re: Cluster to Cluster EJB Call
            Graeme Wallace Newbie

            I have two machines setup in a cluster - cmc5-101 and cmc5-102 - both have an EJB ear deployed with jboss-ejb3.xml in META-INF

             

            I have another machine setup with JBoss 7 - cmc-104 which is trying to connect to the EJB on the first cluster. It has jboss-ejb-client.xml in the META-INF of its deployment ear file.

             

            The standalone machine, just has a plain old java main app - that does a JNDI lookup to connect to the cluster - it uses the PropertiesBasedEJBClientConfiguration to setup the environment for the EJB call.

             

            Ideally I would like both to have a load balanced connection to the first cluster, I just started with your instructions for implementing the ClusterNodeSelector and threw it on the JBoss 7 instance to see if it would work.

            • 3. Re: Cluster to Cluster EJB Call
              Graeme Wallace Newbie

              Hi Jaikiran

               

              Any help would be appreciated.

              • 4. Re: Cluster to Cluster EJB Call
                jaikiran pai Master

                Graeme Wallace wrote:

                 

                 

                I have another machine setup with JBoss 7 - cmc-104 which is trying to connect to the EJB on the first cluster. It has jboss-ejb-client.xml in the META-INF of its deployment ear file.

                 

                What does this cmc-104 machine's jboss-ejb-client.xml look like? Also does this machine have the EJB deployed, that you are trying to lookup? What do the logs look like? Can you attach them?

                • 5. Re: Cluster to Cluster EJB Call
                  Graeme Wallace Newbie

                  <jboss-ejb-client xmlns="urn:jboss:ejb-client:1.1">

                      <client-context>

                          <ejb-receivers>

                              <remoting-ejb-receiver outbound-connection-ref="remote-ejb-connection"/>

                          </ejb-receivers>

                          <clusters>

                              <cluster name="ejb" max-allowed-connected-nodes="20" cluster-node-selector="com.xxi.framework.jbossaux.cluster.RoundRobinClusterNodeSelector" connect-timeout="5000" security-realm="PasswordRealm">

                                  <connection-creation-options>

                                      <property name="org.xnio.Options.SSL_ENABLED" value="false"/>

                                      <property name="org.xnio.Options.SASL_POLICY_NOANONYMOUS" value="true"/>

                                  </connection-creation-options>

                              </cluster>

                          </clusters>

                      </client-context>

                  </jboss-ejb-client>

                   

                   

                  cmc5-104 doesnt have the EJB deployed on it.

                   

                  Here's the startup log - looks like my RoundRobinClusterNodeSelector did get created - just never gets called.

                   

                  21:42:29,949 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.

                  21:42:29,952 INFO  [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem

                  21:42:29,953 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem

                  21:42:29,966 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem

                  21:42:29,974 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension

                  21:42:29,981 INFO  [org.jboss.as.connector] (MSC service thread 1-16) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)

                  21:42:29,982 INFO  [org.jboss.as.security] (MSC service thread 1-12) JBAS013100: Current PicketBox version=4.0.7.Final

                  21:42:30,006 INFO  [org.jboss.as.naming] (MSC service thread 1-10) JBAS011802: Starting Naming Service

                  21:42:30,020 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015400: Bound mail session [java:jboss/mail/Default]

                  21:42:30,061 INFO  [org.jboss.as.remoting] (MSC service thread 1-6) JBAS017100: Listening on /192.168.12.150:4447

                  21:42:30,070 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

                  21:42:30,082 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-5) JBoss Web Services - Stack CXF Server 4.0.2.GA

                  21:42:30,199 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-16) Starting Coyote HTTP/1.1 on http--192.168.12.150-8080

                  21:42:30,278 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]

                  21:42:30,391 INFO  [org.jboss.as.remoting] (MSC service thread 1-16) JBAS017100: Listening on /192.168.12.150:9999

                  21:42:30,397 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-11) JBAS015876: Starting deployment of "jmx-console.war"

                  21:42:30,397 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-12) JBAS015876: Starting deployment of "xxi-framework-module-service.ear"

                  21:42:30,442 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-9) JBAS015876: Starting deployment of "xxi-framework-module-service-jboss.jar"

                  21:42:30,540 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) JBAS018567: Deployment "deployment.jmx-console.war" is using a private module ("org.jboss.common-core:main") which may be changed or removed in future versions without notice.

                  21:42:30,559 INFO  [com.xxi.framework.jbossaux.cluster.RoundRobinClusterNodeSelector] (MSC service thread 1-12) RoundRobin constructor

                  21:42:30,574 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-5) JNDI bindings for session bean named JBossModuleService in deployment unit subdeployment "xxi-framework-module-service-jboss.jar" of deployment "xxi-framework-module-service.ear" are as follows:

                   

                          java:global/jbossmoduleservice/xxi-framework-module-service-jboss/JBossModuleService!com.xxi.framework.moduleservice.JBossModuleService

                          java:app/xxi-framework-module-service-jboss/JBossModuleService!com.xxi.framework.moduleservice.JBossModuleService

                          java:module/JBossModuleService!com.xxi.framework.moduleservice.JBossModuleService

                          java:global/jbossmoduleservice/xxi-framework-module-service-jboss/JBossModuleService

                          java:app/xxi-framework-module-service-jboss/JBossModuleService

                          java:module/JBossModuleService

                   

                  21:42:30,640 INFO  [org.jboss.as.osgi] (MSC service thread 1-3) JBAS011941: Register module: Module "deployment.jmx-console.war:main" from Service Module Loader

                  21:42:30,724 INFO  [org.jboss.web] (MSC service thread 1-2) JBAS018210: Registering web context: /jmx-console

                  21:42:30,865 INFO  [org.jboss.ejb.client.remoting.VersionReceiver] (Remoting "cmc5-104" task-4) Received server version 1 and marshalling strategies [river]

                  21:42:30,874 INFO  [org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver] (MSC service thread 1-6) Successful version handshake completed for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@148fc86f, receiver=Remoting connection EJB receiver [connection=Remoting connection <378fc5db>,channel=jboss.ejb,nodename=cmc5-101]} on channel Channel ID ef00ec9a (outbound) of Remoting connection 242d8a8c to cmc5-101.alpha.farecompare.com/192.168.12.161:4447

                  21:42:30,875 WARN  [org.jboss.ejb.client.remoting.ChannelAssociation] (Remoting "cmc5-104" task-1) Unsupported message received with header 0xffffffff

                  21:42:30,880 INFO  [org.jboss.as.osgi] (MSC service thread 1-14) JBAS011941: Register module: Module "deployment.xxi-framework-module-service.ear:main" from Service Module Loader

                  21:42:31,159 INFO  [org.jboss.as.osgi] (MSC service thread 1-4) JBAS011941: Register module: Module "deployment.xxi-framework-module-service.ear.xxi-framework-module-service-jboss.jar:main" from Service Module Loader

                  21:42:31,205 WARN  [com.xxi.framework.moduleservice.ModuleLoaderService] (MSC service thread 1-13) Cannot find ModuleConfigurations.xml on classpath, checking for config server

                  21:42:31,559 INFO  [com.xxi.framework.moduleproxy.JBoss7SynchronousProxy] (MSC service thread 1-13) Found MBeanServer::org.jboss.as.jmx.PluggableMBeanServerImpl

                  21:42:31,566 INFO  [stdout] (MSC service thread 1-13) trying to create subcontext xxi in context javax.naming.InitialContext@3b68c8cb

                  21:42:31,567 INFO  [stdout] (MSC service thread 1-13) trying to create subcontext modules in context org.jboss.as.naming.NamingContext@5c56a5e5

                  21:42:31,573 INFO  [com.xxi.framework.moduleservice.bind.AbstractBindCallback] (MSC service thread 1-13) trying to bind TestModule within xxi/modules

                  21:42:31,586 INFO  [com.xxi.framework.moduleproxy.JBoss7SynchronousProxy] (MSC service thread 1-13) InJBoss is true

                  21:42:31,587 INFO  [com.xxi.framework.moduleproxy.JBoss7SynchronousProxy] (MSC service thread 1-13) Setting jndiName to ejb:locationmodule/xxi-framework-location-finder-module-ejb//LocationModuleSessionBean!com.xxi.framework.locationfindermodule.api.LocationModuleAPI

                  21:42:31,596 INFO  [com.xxi.framework.moduleservice.ModuleLookupService] (MSC service thread 1-13) Trying to lookup xxi/modules/LocationModule

                  21:42:31,609 INFO  [org.jboss.ejb.client] (MSC service thread 1-13) JBoss EJB Client version 1.0.6.CR1

                  21:42:31,681 INFO  [com.xxi.framework.testmodule.impl.TestModule] (MSC service thread 1-13) DRO Durango, CO United States(US)

                  21:42:31,681 INFO  [stdout] (MSC service thread 1-13) DRO Durango, CO United States(US)

                  21:42:31,688 INFO  [com.xxi.framework.testmodule.impl.TestModule] (MSC service thread 1-13) NYC New York-All Airports, NY United States(US)

                  21:42:31,688 INFO  [stdout] (MSC service thread 1-13) NYC New York-All Airports, NY United States(US)

                  21:42:31,693 INFO  [com.xxi.framework.testmodule.impl.TestModule] (MSC service thread 1-13) BOS Boston, MA United States(US)

                  21:42:31,693 INFO  [stdout] (MSC service thread 1-13) BOS Boston, MA United States(US)

                  21:42:31,699 INFO  [com.xxi.framework.testmodule.impl.TestModule] (MSC service thread 1-13) CHI Chicago-All Airports, IL United States(US)

                  21:42:31,700 INFO  [stdout] (MSC service thread 1-13) CHI Chicago-All Airports, IL United States(US)

                  21:42:31,705 INFO  [com.xxi.framework.testmodule.impl.TestModule] (MSC service thread 1-13) DEN Denver, CO United States(US)

                  21:42:31,705 INFO  [stdout] (MSC service thread 1-13) DEN Denver, CO United States(US)

                  21:42:31,710 INFO  [com.xxi.framework.testmodule.impl.TestModule] (MSC service thread 1-13) DFW Dallas-Fort Worth, TX United States(US)

                  21:42:31,711 INFO  [stdout] (MSC service thread 1-13) DFW Dallas-Fort Worth, TX United States(US)

                  21:42:31,716 INFO  [com.xxi.framework.testmodule.impl.TestModule] (MSC service thread 1-13) HOU Houston-All Airports, TX United States(US)

                  21:42:31,717 INFO  [stdout] (MSC service thread 1-13) HOU Houston-All Airports, TX United States(US)

                  21:42:31,722 INFO  [com.xxi.framework.testmodule.impl.TestModule] (MSC service thread 1-13) SFO San Francisco, CA United States(US)

                  21:42:31,723 INFO  [stdout] (MSC service thread 1-13) SFO San Francisco, CA United States(US)

                  21:42:31,728 INFO  [com.xxi.framework.testmodule.impl.TestModule] (MSC service thread 1-13) LAX Los Angeles, CA United States(US)

                  21:42:31,729 INFO  [stdout] (MSC service thread 1-13) LAX Los Angeles, CA United States(US)

                  21:42:31,735 INFO  [com.xxi.framework.testmodule.impl.TestModule] (MSC service thread 1-13) SEA Seattle, WA United States(US)

                  21:42:31,736 INFO  [stdout] (MSC service thread 1-13) SEA Seattle, WA United States(US)

                  21:42:31,742 INFO  [com.xxi.framework.testmodule.impl.TestModule] (MSC service thread 1-13) PHX Phoenix, AZ United States(US)

                  21:42:31,742 INFO  [stdout] (MSC service thread 1-13) PHX Phoenix, AZ United States(US)

                  21:42:31,748 INFO  [com.xxi.framework.testmodule.impl.TestModule] (MSC service thread 1-13) SLC Salt Lake City, UT United States(US)

                  21:42:31,749 INFO  [stdout] (MSC service thread 1-13) SLC Salt Lake City, UT United States(US)

                  21:42:31,765 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 28) JBAS018559: Deployed "jmx-console.war"

                  21:42:31,766 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 28) JBAS018559: Deployed "xxi-framework-module-service.ear"

                  21:42:31,872 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://192.168.12.150:9990

                  21:42:31,873 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.2.Final-SNAPSHOT "Brontes" started in 3087ms - Started 232 of 320 services (87 services are passive or on-demand)

                  • 6. Re: Cluster to Cluster EJB Call
                    jaikiran pai Master

                    Graeme Wallace wrote:

                     

                    Here's the startup log - looks like my RoundRobinClusterNodeSelector did get created - just never gets called.

                     

                    Okay that makes sense. As explained in https://docs.jboss.org/author/display/AS71/Clustered+EJBs (Clustering topology section), the client (in this case cmc5-104) is sent back the clustering topology and the affinity associated with the clustered bean. In your case it's a clustered SFSB. So it's going to have a hard affinity on (any nodes belonging to) a cluster. It also has a weak affinity associated with it and that weak affinity is a *node affinity* which points to the node on which the session was created. Assuming your nodes cmc5-101 and cmc5-102 are part of a cluster named "ejb" and the session creation for the SFSB happens on cmc5-101, then the affinity sent back will be: hard affinity = cluster named "ejb" and weak affinity = node cmc5-101. Now the EJB client API implementation sees that the invocation on that session of the SFSB has these affinities and queries for a cluster context named "ejb" and a specific node within that context named cmc5-101. In this process any implementation of ClusterNodeSelector will *not* play a role since the EJB client API already knows which node to select. However, if the weak affinity cannot be satisfied (for example, if cmc5-101 server goes down) then the EJB client API uses the implementation of ClusterNodeSelector to let it decide a suitable node from within the cluster.

                     

                    You can see this functioning (i.e. your cluster node selector being called) if you bring down the node on which the session gets created. Here's an testcase which does the same https://github.com/jbossas/jboss-as/blob/master/testsuite/integration/clust/src/test/java/org/jboss/as/test/clustering/cluster/ejb3/stateful/remote/failover/RemoteEJBClientStatefulBeanFailoverTestCase.java although it uses the default cluster node selector.

                    • 7. Re: Cluster to Cluster EJB Call
                      Graeme Wallace Newbie

                      Ok. So the whole idea behind trying ClusterNodeSelector was to try and implement any sort of load balancing. In my production environment, I obviously have much bigger clusters than just two nodes. How do I get EJB calls to SLSB distributed across the whole cluster and not just the first node in the cluster ?

                      • 8. Re: Cluster to Cluster EJB Call
                        jaikiran pai Master

                        Graeme Wallace wrote:

                         

                        How do I get EJB calls to SLSB distributed across the whole cluster and not just the first node in the cluster ?

                        Clustered SLSBs are different (as compared to Clustered SFSB). Clustered SLSBs do not have a hard affinity and their weak affinity equals the cluster name (and not a specific node). So in that case, the EJB client API will invoke the cluster node selector (since it won't know which node to use from within the cluster) during invocation. This should be functional in the latest nightly builds of AS7. There was a bug in 7.1.1.Final which was fixed recently https://issues.jboss.org/browse/AS7-4223. Are you using the latest nightly build and seeing an issue there?

                        • 9. Re: Cluster to Cluster EJB Call
                          jaikiran pai Master

                          Just noticed that you were the one who reported https://issues.jboss.org/browse/AS7-4223 originally So you'll most likely be already testing it against a nightly build. If you are still running into problems with SLSB clustering in the latest nightly build, then please do let us know, I can take a more detailed look. From what I see of a recently added testcase against 4223, I expect this to work.

                          • 10. Re: Cluster to Cluster EJB Call
                            Graeme Wallace Newbie

                            I've been using nightly build from the 23rd. The day before the fix got checked in....sigh...I'll pull the latest and try it out.

                            • 11. Re: Cluster to Cluster EJB Call
                              Graeme Wallace Newbie

                              Ok. So i downloaded the latest build for May 7th and tried it out. It doesnt work

                               

                              Still cant get the cluster to report back to another EJB server all its information - only the cmc5-101 node reports back, no sign of cmc5-102 (the other member of the cluster).

                               

                              14:22:04,348 INFO  [org.jboss.ejb.client.remoting] (Remoting "cmc5-104" task-4) EJBCLIENT000017: Received server version 1 and marshalling strategies [river]

                              14:22:04,356 INFO  [org.jboss.ejb.client.remoting] (MSC service thread 1-15) EJBCLIENT000013: Successful version handshake completed for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@4fbe29da, receiver=Remoting connection EJB receiver [connection=Remoting connection <5ca2ee59>,channel=jboss.ejb,nodename=cmc5-101]} on channel Channel ID b1ed01e5 (outbound) of Remoting connection 1046bd78 to cmc5-101.alpha.farecompare.com/192.168.12.161:4447

                              14:22:04,357 WARN  [org.jboss.ejb.client.remoting.ChannelAssociation] (Remoting "cmc5-104" task-1) Unsupported message received with header 0xffffffff

                               

                              Also the instantiation message that i put in my RoundRobinClusterNodeSelector never gets emitted.

                              • 12. Re: Cluster to Cluster EJB Call
                                jaikiran pai Master

                                Are you using standalone-ha.xml? Can you post the code of your beans including the import statements for your @Clustered annotation? Also please attach the server logs.

                                • 13. Re: Cluster to Cluster EJB Call
                                  Graeme Wallace Newbie

                                  I'm not using @Clustered - didnt want the compile time dependency on JBoss jars - I'm using the clustered xml in jboss-ejb3.xml. Does this make a difference ?

                                  • 14. Re: Cluster to Cluster EJB Call
                                    jaikiran pai Master

                                    What does the jboss-ejb3.xml look like and also the corresponding bean class code?

                                    1 2 Previous Next