Hi all,
I ran into a problem that stumped me and hope someone can give a clue.
I have an EJB that is part of a more complex suite. The task is to get the EJB deployed on GF cluster and run the suite against it. When I deploy the EJB on the admin server (target=server) I can access the EJB by using the admin server iiop port. So far so good, everything behaves as expected. But when I try to deploy the EJB on the complete cluster (target=cluster) and tell the suite to access it via the cluster iiop port it fails, the EJB cannot be created.
After a lot of research and messing with the server's logger I found the following "warning" in the admin server log caused by deploying said EJB on the cluster:
javax.management.InstanceNotFoundException: "This operation failed, because it could not be handled by this domain.
An example of such an operation is creating application server instances or clusters when they are not supported by the given domain.
The actual error is: MBean instance not found: com.sun.appserv:j2eeType=EJBModule,name=XATestAC2,J2EEServer=i2_lt0468,J2EEApplication=null,category=runtime"
com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.manufactureAndRegisterMBean(SunoneInterceptor.java:663)
When both instances are up I get two of those messages each one referring to one of the instances as the J2EEServer. From a first glance this would read as if the two instances would not support clusters. But the domain is set up as a cluster and the admin server states this after startup.
Do you have to modify the EJB when deploying it on the cluster? Could it be that this domain only pretends to be a cluster??
I am really really puzzled here. Any help would be greatly appreciated.
Thanks,
Chris
[Message sent by forum member 'candlejack' (candlejack)]
http://forums.java.net/jive/thread.jspa?messageID=308132