Our production environment is a clustered Glassfish v2ur2 environment. The cluster is configured to use an external (REMOTE) instance of OpenMQ that is also configured as a cluster. Our application is using EclipseLink for the JPA implementation. We want to use a Coordinated Cache to keep application Entities in sync but have run into a showstopper due to an open bug in GlassFish.
https://glassfish.dev.java.net/issues/show_bug.cgi?id=6580
While EclipseLink is calling topicSession.createSubscriber(topic) and clearly this is for a non-durable subscription, Glassfish is attempting to make this a durable subscription, but without a client ID. Of course this results in an exception being raised and everything goes to hell. So how can we get around this issue? Does OpenMQ expose an InitialContext where EclipseLink can connect to acquire the ConnectFactory and Topic, allowing us to by-pass Glassfish all together?
At this point Glassfish is the impedance and I can't find any options around this issue.
[Message sent by forum member 'cmathrusse' (cmathrusse)]
http://forums.java.net/jive/thread.jspa?messageID=351305