-
Bug
-
Resolution: Done
-
Major
-
17.0.1.Final
-
None
JMS message data is thrown in server.log for error in org.jboss.resource.adapter.jms.inflow.JmsServerSession, since this can be sensitive data for users, there is no option to hide the data while having the exception.
09:54:28,428 ERROR [org.jboss.resource.adapter.jms.inflow.JmsServerSession] (default-threads - 38) Unexpected error delivering message TextMessage={ Header={ JMSMessageID=
{ID: XXXXXXXXXXXXXXXXXX}JMSDestination=
{Queue[]}JMSReplyTo=
{null} JMSDeliveryMode={PERSISTENT} JMSRedelivered={false} JMSCorrelationID={null}JMSType=
{null}JMSTimestamp=
{Wed Jul 03 09:54:23 GMT 2019}JMSDeliveryTime=
{Wed Jul 03 09:54:23 GMT 2019}JMSExpiration=
{0}JMSPriority=
{4}} Properties=
{ WHOLE EVENT MESSAGE DISPLAY HERE}}: javax.ejb.EJBTransactionRolledbackException: Problem during method invocation (onMessage)
This exception originates from this line:
- is cloned by
-
JBEAP-17164 [GSS](7.2.z) WFLY-12415 - Complete message object visible in ERROR at org.jboss.resource.adapter.jms.inflow.JmsServerSession
- Closed
- is incorporated by
-
WFLY-12419 Upgrade Generic JMS RA 2.0.2.Final
- Closed
-
WFLY-12497 Upgrade Generic JMS RA 2.0.2.Final
- Closed