Hi all,

Is there a simple way to step WAS from listing a specific warning in the SystemOut.log ?
I'm seeing too many of these CWYDB0806W and can't see the wood for the trees.

WAS v7

Thanks,
Mark.

------------------------------
Mark Shaw
------------------------------

Hi Mark,

I can't find CWYDB0806W message anywhere, can you tell us more about what the rest of the message text is?  Maybe double check that is the exact message number?

Regards,

------------------------------
Bill Holtzhauser III
------------------------------

Hi Bill,

Here is the full Warning, WAS is running IBM BPM v7

JDBCRACWYBC_J W com.ibm.j2ca.jdbc.commands.JDBCRetrieveCommand doContainerRetrieve CWYDB0806W: The Retrieve operation found no matches in the database for the child business object, EsbdevLkuvalue2, with the given key value or values. Explanation=No matching rows were detected in the database for the child business object with the given key values. This is not an error condition. The message indicates that there are no child objects matching the key values provided. UserAction=This warning can generally be ignored. However, if you expect child objects to be retrieved, check the database rows to ensure that the keys match and that records exist in the appropriate tables.

https://www.ibm.com/support/knowledgecenter/SS8JB4_19.x/com.ibm.wbpm.ref.doc/adapt_msgs/CWYDB.html

I just wondered if its possible to set an 'ignore' the logging somewhere, although I doubt it.

Thanks
Mark.

------------------------------
Mark Shaw
------------------------------

Original Message:
Sent: Mon October 19, 2020 03:15 PM
From: Bill Holtzhauser
Subject: Warning spamming logs

Hi Mark,

I can't find CWYDB0806W message anywhere, can you tell us more about what the rest of the message text is?  Maybe double check that is the exact message number?

Regards,

------------------------------
Bill Holtzhauser III
------------------------------

Hi Mark,


I see that message now in the link you provided, but still if you search google for CWYDB0806W the only place you will find it is here in this discussion!

I see that it is a BPM message, I am guessing that that version of BPM is out of support, I know that WAS v7 is out of support (these are very old versions).
Also, it would follow logically that if this warning message was going to be restricted from being written that it would be up to the code that is writing it to provide a way to restrict it.  An example of this is the security code in WAS throws a warning message (SECJ0371W) when someone tries to use an expired LPTA token, and in some environments this can happen a massive amount of times and it does fill up the logs... so APAR https://www.ibm.com/support/pages/apar/PI54477 was written.
In WAS I could not find  a"filter" for a specific message in the default logging that goes to SystemOut.log, you could set the trace specification to only show errors but then ALL informational and warning messages would not be written.

Sorry, but maybe someone that knows more about BPM could say if its possible to restrict this in the BPM code

------------------------------
Bill Holtzhauser
------------------------------

Original Message:
Sent: Mon October 19, 2020 03:57 PM
From: Mark Shaw
Subject: Warning spamming logs

Hi Bill,

Here is the full Warning, WAS is running IBM BPM v7

JDBCRACWYBC_J W com.ibm.j2ca.jdbc.commands.JDBCRetrieveCommand doContainerRetrieve CWYDB0806W: The Retrieve operation found no matches in the database for the child business object, EsbdevLkuvalue2, with the given key value or values. Explanation=No matching rows were detected in the database for the child business object with the given key values. This is not an error condition. The message indicates that there are no child objects matching the key values provided. UserAction=This warning can generally be ignored. However, if you expect child objects to be retrieved, check the database rows to ensure that the keys match and that records exist in the appropriate tables.

https://www.ibm.com/support/knowledgecenter/SS8JB4_19.x/com.ibm.wbpm.ref.doc/adapt_msgs/CWYDB.html

I just wondered if its possible to set an 'ignore' the logging somewhere, although I doubt it.

Thanks
Mark.

------------------------------
Mark Shaw
------------------------------


Original Message:
Sent: Mon October 19, 2020 03:15 PM
From: Bill Holtzhauser
Subject: Warning spamming logs

Hi Mark,

I can't find CWYDB0806W message anywhere, can you tell us more about what the rest of the message text is?  Maybe double check that is the exact message number?

Regards,

------------------------------
Bill Holtzhauser III

WAS traditional and Liberty differ a bit here.  Liberty has a capability to hide a specific message by specifying that message in the logging configuration's hideMessage attribute. WAS doesn't have that same capability. 

More usefully for this case, WAS also has the ability to control the logging level for each logger individually.  You could use that to adjust the logging level of the logger that emitted the CWYDB0806W message to Error level so as to block the warning message from being printed.  For example, your trace spec could be set to *=info:com.ibm.xyz.SomeClass=severe

------------------------------
Don Bourne
WebSphere Observability Architect
------------------------------

Original Message:
Sent: Tue October 20, 2020 07:44 AM
From: Bill Holtzhauser
Subject: Warning spamming logs

Hi Mark,


I see that message now in the link you provided, but still if you search google for CWYDB0806W the only place you will find it is here in this discussion!

I see that it is a BPM message, I am guessing that that version of BPM is out of support, I know that WAS v7 is out of support (these are very old versions).
Also, it would follow logically that if this warning message was going to be restricted from being written that it would be up to the code that is writing it to provide a way to restrict it.  An example of this is the security code in WAS throws a warning message (SECJ0371W) when someone tries to use an expired LPTA token, and in some environments this can happen a massive amount of times and it does fill up the logs... so APAR https://www.ibm.com/support/pages/apar/PI54477 was written.
In WAS I could not find  a"filter" for a specific message in the default logging that goes to SystemOut.log, you could set the trace specification to only show errors but then ALL informational and warning messages would not be written.

Sorry, but maybe someone that knows more about BPM could say if its possible to restrict this in the BPM code

------------------------------
Bill Holtzhauser
------------------------------


Original Message:
Sent: Mon October 19, 2020 03:57 PM
From: Mark Shaw
Subject: Warning spamming logs

Hi Bill,

Here is the full Warning, WAS is running IBM BPM v7

JDBCRACWYBC_J W com.ibm.j2ca.jdbc.commands.JDBCRetrieveCommand doContainerRetrieve CWYDB0806W: The Retrieve operation found no matches in the database for the child business object, EsbdevLkuvalue2, with the given key value or values. Explanation=No matching rows were detected in the database for the child business object with the given key values. This is not an error condition. The message indicates that there are no child objects matching the key values provided. UserAction=This warning can generally be ignored. However, if you expect child objects to be retrieved, check the database rows to ensure that the keys match and that records exist in the appropriate tables.

https://www.ibm.com/support/knowledgecenter/SS8JB4_19.x/com.ibm.wbpm.ref.doc/adapt_msgs/CWYDB.html

I just wondered if its possible to set an 'ignore' the logging somewhere, although I doubt it.

Thanks
Mark.

------------------------------
Mark Shaw


Original Message:
Sent: Mon October 19, 2020 03:15 PM
From: Bill Holtzhauser
Subject: Warning spamming logs

Hi Mark,

I can't find CWYDB0806W message anywhere, can you tell us more about what the rest of the message text is?  Maybe double check that is the exact message number?

Regards,

------------------------------
Bill Holtzhauser III