SOA logs showing unrelated composites in the same notification message (Doc ID 2095728.1)

Last updated on FEBRUARY 15, 2016

Applies to:

Oracle SOA Suite - Version 11.1.1.7.0 to 11.1.1.7.7 [Release 11gR1]
Information in this document applies to any platform.

Symptoms

In the SOA diagnostic logs there are several entries that are referring to combinations of composites that are not related.

Example

[2015-10-29T10:55:42.604+01:00] [soa_server4] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: ] [ecid: fd377c9ea4bddf3a:-1ddde1c6:15064ab319f:-7fec-0000000007305674,0] [APP: soa-infra] [J2EE_APP.name: soa-infra] [J2EE_MODULE.name: fabric] [WEBSERVICE.name: AIA-Notification-2.3-Service] [WEBSERVICE_PORT.name: AIA-Notification-2.3-SOAP-Port] [composite_instance_id: 55743132] [composite_name: compositeA!5.3.3.0] [component_name: SalesOrder] JMS Adapter compositeB:PublishEvent [ Produce_Message_ptt::Produce_Message(ListEvent) ] JMSMessageProducer_init: Successfully created MessageProducer for [default destination = queue/AIA_OUT_JMSQ]

 

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms