Troubleshooting

These are some suggestions to decide if the Coherence cache is operating as expected with Siebel CRM.

Situation	Advice
Find out if the Siebel server is connected to the Coherence cache	In the application log file for the application object manager, you'll see the following message that indicates success connecting to the remote Coherence cache. `GenericLog GenericError Connected to Coherence Cache with <cachename> name`
Find out if the connection from an object manager to the cache failed.	In the application log file for the object manager in question you'll see entries like this: `UCacheLog UCacheErrorLog [UCACHE] Error encountered in creating the cache 'siebelcache'- Could not establish a connection with the server. Possible cause - Server is not running or POF is not configured at the server side or trying to connect to different port` `GenericLog GenericError Coherence Cache does not exist with <cachename> name`
Find out if the cache became unreachable after successfully connecting.	If the cache goes down after the Siebel server has successfully connected to it, you'll see entries in the application log file like this: `UCacheLog UCacheErrorLog [UCACHE] Error encountered in inserting key 'ProfAttrState1:0-1'- Could not connect to the server. Please contact Siebel Administrator for troubleshooting.`

Situation

Advice

Find out if the Siebel server is connected to the Coherence cache

In the application log file for the application object manager, you'll see the following message that indicates success connecting to the remote Coherence cache.

GenericLog GenericError Connected to Coherence Cache with <cachename> name

Find out if the connection from an object manager to the cache failed.

In the application log file for the object manager in question you'll see entries like this:

UCacheLog UCacheErrorLog [UCACHE] Error encountered in creating the cache 'siebelcache'- Could not establish a connection with the server. Possible cause - Server is not running or POF is not configured at the server side or trying to connect to different port

GenericLog GenericError Coherence Cache does not exist with <cachename> name

Find out if the cache became unreachable after successfully connecting.

If the cache goes down after the Siebel server has successfully connected to it, you'll see entries in the application log file like this:

UCacheLog UCacheErrorLog [UCACHE] Error encountered in inserting key 'ProfAttrState1:0-1'- Could not connect to the server. Please contact Siebel Administrator for troubleshooting.