My Oracle Support Banner

Weblogic Becomes Unreachable With The Exception: Read Timed Out (Doc ID 2079288.1)

Last updated on SEPTEMBER 28, 2018

Applies to:

Oracle Communications ASAP - Version 7.0.0 and later
Information in this document applies to any platform.


Weblogic becomes unreachable with the exception: Read timed out  

Errors seen in logs:

<Warning> <EJB> <BEA-010216> <The Message-Driven EJB: ErrorResponse is throwing exception when processing the messages. Delivery failed after 385 attempts. The EJB container will suspend the message delivery for 60 seconds before retry.>

<Warning> <EJB> <xxxxxxx> <xxxxxxx> <[ACTIVE] ExecuteThread: '13' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1445343621618> <BEA-010065> <MessageDrivenBean threw an Exception in onMessage(). The exception was:
java.lang.StringIndexOutOfBoundsException: String index out of range: -1.
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(
at com.mslv.asap.activation.srp.ErrorResponseBean.getExceptionName(
at com.mslv.asap.activation.srp.ErrorResponseBean.onMessage(
at weblogic.ejb.container.internal.MDListener.execute(
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(
at weblogic.ejb.container.internal.MDListener.onMessage(
at weblogic.jms.client.JMSSession.onMessage(
at weblogic.jms.client.JMSSession.execute(
at weblogic.jms.client.JMSSession$



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

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