I am having a weblogic cluster with two Managed Server as ManagedServer1 and ManagedServer2.
I have target my JMS module on cluster and resources with in the JMS Module (Connection Factory and Topic) to JMS Server.
JMSServer is targeted to migratable target with preffered server as ManagedServer1.
I am using clusteraddress as providerURL to access JMS stuff.
After i start my application JMS services are pinned on ManagedServer1. At the start of application i create a subscriber on Topic and resigter my MessageMDB on to the subscriber. Its working fine. Now when ManagedServer1 goes down then JMS services are successfully migrated to ManagedServer2 but MessageMDB is not able to consume messages. I think problem is with its registration. After services got migrated i need to re-create a subscriber with migrated Topic and re-register MessageMDB on to it.
Now problem is to capture the JMS Service migrated event at which i can do this (re-registration) action. I have tried to use post migrated script but got class cast exception as follows
at weblogic.jms.frontend.FEConnectionFactoryImpl_1030_WLStub.connectionCreateRequest(Unknown Source)
Can any one help in above exception or can tell any other way to capture event either by using JMX API or so on.