users@genericjmsra.java.net

Re: GenericJMSRA seems to cause ClassCastExceptions in Cluster

From: <huberc_at_butterbrot.org>
Date: Wed, 22 Oct 2008 16:36:44 +0200 (CEST)

Found the solution to this. The instance on the remote server had troubles
reading the mq-libs. After fixing that the error messages disappeared.

On Wed, 22 Oct 2008, huberc_at_butterbrot.org wrote:

> Hi everyone,
>
> i got a problem using the genericjmsra in a cluster environment and hope
> someone here can give me a clue.
>
> I have a cluster with two nodeagents each managing one instance. One instance
> is running the machine of the DAS the other one runs on a different server.
>
> I did configure and deploy the genericjmsra, connector connection pool,
> connector resource and admin object in the same way as i did before on a
> single server instance where everything is working fine. The only difference
> is that the components are deployed and enabled on the server and the cluster
> target.
>
> Starting up the first instance works fine. But when i start the second
> instance i see the following exceptions in the log file:
>
> [#|2008-10-22T14:02:37.823+0200|WARNING|sun-appserver9.1|com.sun.genericjmsra|_ThreadID=10;_ThreadName=main;_RequestID=6a711907-206d-4be2-b146-d9c6f9c885be;|javax.nam
> ing.Reference
> java.lang.ClassCastException: javax.naming.Reference
> at
> com.sun.genericra.inbound.EndpointConsumer.initializeAdministeredObjects(EndpointConsumer.java:334)
> at
> com.sun.genericra.inbound.EndpointConsumer.<init>(EndpointConsumer.java:74)
> at
> com.sun.genericra.inbound.EndpointConsumer.<init>(EndpointConsumer.java:79)
> at
> com.sun.genericra.GenericJMSRA.getXAResources(GenericJMSRA.java:278)
> at
> com.sun.enterprise.resource.ResourceInstaller.recoverInboundTransactions(ResourceInstaller.java:896)
> at
> com.sun.enterprise.resource.ResourceInstaller.recoverXAResources(ResourceInstaller.java:334)
> at
> com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:205)
> at
> com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:442)
> at
> com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(OnDemandServer.java:120)
> at com.sun.enterprise.server.PEMain.run(PEMain.java:409)
> at com.sun.enterprise.server.PEMain.main(PEMain.java:336)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at com.sun.enterprise.server.PELaunch.main(PELaunch.java:412)
> | #]
>
> It does not matter in which order the instances get started, the errors
> always appear on the remote instance. I tried to erase the instance
> directories to enforce the configuration being obtained from the DAS again.
> But that did not change anything.
>
> Are there any known issues with genericjmsra in cluster environments? Are
> there any additional configuration options?
>
> If you need more input on this, please let me know and i will try to provide
> it.
>
> Thanks,
> Chris
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_genericjmsra.dev.java.net
> For additional commands, e-mail: users-help_at_genericjmsra.dev.java.net
>
>
>