Billing and Revenue Management (MOSC)

MOSC Banner

Getting Signals in different opcodes post restart in production

edited Apr 2, 2015 10:18AM in Billing and Revenue Management (MOSC) 7 commentsAnswered

Post production deployment restart yesterday, we are getting signals in many interfacing opcodes.

Point to note here is

1. we haven't made any changes to the opcodes that are signalling.

2. Not all instances are throwing signals.

3. Signalled opcodes work fine when instances are re-tried.

Without enabling debug log, this is the signal noticed

Received Signal 11

22449:  /u01/euser_cmdm2/app/pin_eu/portal/7.3/bin/cm

7eaeeec8 waitid   (0, 580e, ffbfb620, 3)

7eade868 waitpid  (580e, ffbfb774, 0, 0, ffbfb7cc, 79fbc2c0) + 60

7ead15e8 system   (ffbfb8c8, 7eb6bc10, 20000, 1, 7eb623f0, ffbfb7cc) + 2ec

7faa8634 printExceptionReport (b, bc00, 2, 5aec, 7fb2edec, d) + 240

7f7e01cc sigsegv_handler (b, 14b4, 3ab84, 0, 7f81ad28, 1400) + 34

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center