Skip to Main Content

Oracle Database Express Edition (XE)

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

What can I do to resolve the FLASH error when using OEM for Express Edition 18c

kimvanJun 8 2021

Is there a 19c Express edition to upgrade to?

Comments

mkeith
Hi Francis,

It appears that my first reply was lost, so will re-post.

When using JMS the reconnect policy should reconnect to the topic, but only if the should-remove-connection-on-error setting in sessions.xml is false. Alternatively you can set it directly on the CacheSynchronizationManager by invoking setShouldRemoveConnectionOnError(false).

Note that for RMIJNDI cache sync the RMI Registry is not used. It may be that whatever type of object you are using does not support transparent failover so you may need to reacquire a stub (e.g. for vanilla RMI objects).

HTH,
-Mike
413051
I am already setting should-remove-connection-on-error to false. Should this make cache synchronization continue to work after the OC4J instance running the JMS server has been restarted? Here is the relevant section of my sessions.xml (for JMS):
<cache-synchronization-manager>
<clustering-service>oracle.toplink.remote.jms.JMSClusteringService</clustering-service>
<should-remove-connection-on-error>false</should-remove-connection-on-error>
<jms-topic-connection-factory-name>jms/TopicConnectionFactory</jms-topic-connection-factory-name>
<jms-topic-name>jms/TopLinkCacheSyncTopic</jms-topic-name>
</cache-synchronization-manager>

I don't really understand your last paragraph... What do I have to do to make my objects support transparent failover? All of the objects that I am using TopLink to persist are simple Serializable JavaBeans.

Francis
mkeith
Hi Francis,

It appears as if by default the reconnection policy does not reconnect, so you will have to subclass the JMSDistributedSessionReconnectPolicy clas and set it on the clustering service (e.g. clusteringService.setReconnectPolicy(new MyReconnectPolicy())). You will want to override the reconnect(RemoteConnection) method to call clusteringService.createRemoteConnection(). Note that you wil have to set the clustering service on your policy instance when you set the policy so that you can access the service from within the reconnect callback. I would also recommend setting the logging to log-debug so that you can see what is happening.

For the RMI, it looks like from your stack trace an RMI object is broken. If you are using JavaBeans then it is is not a TopLink-managed one but it won't be affected or fixed by cache sync.

-Mike
1 - 3

Post Details

Added on Jun 8 2021
1 comment
112 views