You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have filed a bug with OpenMQ that the MQ-JMSRA connectors com.sun.messaging.jms.ra.ManagedConnectionFactory does not implement javax.resource.spi.ValidatingManagedConnectionFactory. This leads to pooled connections which are deemed to be valid when they may be not. The connectors-runtime com.sun.enterprise.resource.allocator.AbstractConnectorAllocator method shows the problem:
public Set getInvalidConnections(Set connectionSet)
throws ResourceException {
if (mcf instanceof ValidatingManagedConnectionFactory) {
return ((ValidatingManagedConnectionFactory) this.mcf).
getInvalidConnections(connectionSet);
}
return null;
}
In case of a JMS Server restart this leads to broken connection pooled which in our case mainly hinders the JMS cache synchronization which slowly breaks application functionality.
@svendiedrichsen is this issue still present in the current release of Payara Server 5.x? Are you able to provide a reproducer with the correct instructions to encounter the problem?
@svendiedrichsen, have you verified that the issue is still present in the current release of Payara Server 5.x? If we do not receive any updates soon we'll close this issue.
Description
I have filed a bug with OpenMQ that the MQ-JMSRA connectors
com.sun.messaging.jms.ra.ManagedConnectionFactory
does not implementjavax.resource.spi.ValidatingManagedConnectionFactory
. This leads to pooled connections which are deemed to be valid when they may be not. The connectors-runtimecom.sun.enterprise.resource.allocator.AbstractConnectorAllocator
method shows the problem:In case of a JMS Server restart this leads to broken connection pooled which in our case mainly hinders the JMS cache synchronization which slowly breaks application functionality.
OpenMQ-Bug: eclipse-ee4j/openmq#422
You might want to work around this.
Expected Outcome
Pooled JMS connections are validated.
Current Outcome
Broken connections are kept in pool unless used.
Steps to reproduce (Only for bug reports)
Restart an external JMS server and watch the logs when i.e. producing eclipselink cache sync messages.
Environment
The text was updated successfully, but these errors were encountered: