Last updated on AUGUST 02, 2016
Applies to:Oracle Communications Order and Service Management - Version 7.2.0 and later
Information in this document applies to any platform.
Why does cartridge deploy fail after changing the OSM log level?
Setup is: 1 proxy server, 1 admin server, 2 managed servers (second managed server not running)
1. start all servers and deploy test cartridge. Cartridge deploys fine
2. Unpack oms.ear
3. update the log4j.xml file set log level to WARN
4. Repack oms.ear
5. Restart oms
6. upversion test cartridge and try to redeploy, deployment runs until timeout with the following re-occuring message
2014-03-11 10:41:28.278/1701.070 Oracle Coherence GE 126.96.36.199 (thread=[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)', member=1): Expected an insert/update for 1001, but none have been received
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms