My Oracle Support Banner

Oracle Service Bus Crashes if Blank Message is Sent to Configured JMS Queue (Doc ID 841267.1)

Last updated on SEPTEMBER 24, 2023

Applies to:

Oracle Service Bus - Version 2.6 and later
Information in this document applies to any platform.

Symptoms

A JMS Proxy service is filling up the logs with several exceptions after receiving a blank message from JMS queue.


ERROR
<Jun 2, 2009 6:46:02 AM MDT> <Error> <WliSbTransports> <BEA-381502>
<Exception in JmsInboundMDB.onMessage, com.bea.wli.sb.transports.TransportException: Failed to generate the alert: Invalid xml: Expected element 'inbound@http://www.bea.com/wli/sb/transports'
instead of 'URI@http://www.bea.com/wli/sb/transports' here com.bea.wli.sb.transports.TransportException: Failed to generate the alert: Invalid xml:
Expected element 'inbound@http://www.bea.com/wli/sb/transports' instead of 'URI@http://www.bea.com/wli/sb/transports' here
at com.bea.wli.sb.transports.TransportException.newInstance(TransportException.java:146)
at com.bea.wli.sb.transports.TransportManagerImpl.receiveMessage(TransportManagerImpl.java:319)
at com.bea.wli.sb.transports.jms.JmsInboundMDB.onMessage(JmsInboundMDB.java:108)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:429)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:335)
Truncated. see log file for complete stacktrace
com.bea.wli.sb.pipeline.PipelineException: Failed to generate the alert: Invalid xml: Expected element 'inbound@http://www.bea.com/wli/sb/transports' instead of 'URI@http://www.bea.com/wli/sb/transports' here
at stages.logging.runtime.AlertRuntimeStep.processMessage(AlertRuntimeStep.java:195)
at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:319)
at com.bea.wli.sb.stages.impl.SequenceRuntimeStep.processMessage(SequenceRuntimeStep.java:33)
at com.bea.wli.sb.pipeline.PipelineStage.processMessage(PipelineStage.java:93)
at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:834)
Truncated. see log file for complete stacktrace
>
<Jun 2, 2009 6:46:02 AM MDT> <Error> <ALSB Security> <BEA-386012> <An error ocurred while evaluating the message-level username XPath selector: [ALSB Security:386014]the result of the XPath selector is empty>
<Jun 2, 2009 6:46:02 AM MDT> <Error> <ALSB Kernel> <BEA-382004> <Failed to process request message for service ProxyService
CMD_1.1/PublishUCMAccount_v1.1/V1.1/ProxyServices/PublishUCMAccount_v11_PS: com.bea.wli.sb.pipeline.PipelineException: Failed to generate the alert: Invalid xml:
Expected element 'inbound@http://www.bea.com/wli/sb/transports' instead of 'URI@http://www.bea.com/wli/sb/transports' here
com.bea.wli.sb.pipeline.PipelineException: Failed to generate the alert: Invalid xml: Expected element 'inbound@http://www.bea.com/wli/sb/transports' instead of 'URI@http://www.bea.com/wli/sb/transports' here
at stages.logging.runtime.AlertRuntimeStep.processMessage(AlertRuntimeStep.java:195)
at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:319)
at com.bea.wli.sb.stages.impl.SequenceRuntimeStep.processMessage(SequenceRuntimeStep.java:33)
at com.bea.wli.sb.pipeline.PipelineStage.processMessage(PipelineStage.java:93)
at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:834)
Truncated. see log file for complete stacktrace
>
<Jun 2, 2009 6:46:02 AM MDT> <Error> <ALSB Kernel> <BEA-380001>
<Exception on TransportManagerImpl.receiveMessage, com.bea.wli.sb.pipeline.PipelineException:
Failed to generate the alert: Invalid xml: Expected element 'inbound@http://www.bea.com/wli/sb/transports' instead of 'URI@http://www.bea.com/wli/sb/transports' here com.bea.wli.sb.pipeline.PipelineException: Failed
to generate the alert: Invalid xml: Expected element 'inbound@http://www.bea.com/wli/sb/transports' instead of 'URI@http://www.bea.com/wli/sb/transports'


The exceptions will keep recurring, the server may finally go out of memory and throw OutOfMemoryErrors.

Cause

To view full details, sign in with your My Oracle Support account.

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

In this Document
Symptoms
Cause
Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.