Maybe some of you have this experience and can help me.
I have a situation while monitoring a Oracle Service Bus machine in wich only a generic BEA error code is raised on certain services. The exception is:
Transport error (error code=BEA-380001): Error
This service running on OSB is based on SOAP Request X Response and client has designed the envelopes with two exception tags, as following:
<soapenv:Fault> here goes the Business Exception XYZ </soapenv:Fault><fault> here goes the BEA-380001 message </fault>
Just the second tag is being reported to Java agent and error section of its metrics.
Can I somehow have the content of <soapenv:Fault> on my exception list of this agent? How to do that?
-->> Environment.- WebLogic Server 10.3.6.0- APM 10.1 (agents and cluster)
Thank you.Alexandre França
I suspect this may need further investigation into a tracer addition or customisation of the OOTB Soap Fault Tracer for the current exception handling.
Guenter_Grossberger and Hiko_Davis to provide SME advice after Thanksgiving weekend
I still researching this issue, meanwhile, any of you have an idea of how to get the string from <soapenv:Fault> xml envelope tag?
What version of Java are you using?
java version "1.8.0_60"Java(TM) SE Runtime Environment (build 1.8.0_60-b27)Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)
I think it's best at this point to open a ticket as this error message suggests an issue with the SOAP envelope and it may have customer details which you will not want to share here.
There should be an application log which details the exact issue with the request you're making, according to Oracle.