IndexOutOfBoundsException

[Metta]

The following exception was thrown on the platform this morning - I'm hoping you might be able to shed some light on the cause.

The Exception was:

javax.jms.JMSException: Failed to look up destination eemeiQueue. Reason: exception occured during lookup: java.lang.IndexOutOfBoundsException: Index: 0, Size:0

[IIT Software]

Which SwiftMQ release do you use?

Do you use Spring's JmsTemplate?

[Metta]

We're running v7.0.2 and do not use Spring's JmsTemplate.

[IIT Software]

Did you hard kill (e.g. kill -9) the router before you got that exception? In that case the store might become inconsistent and may thow this kind of exception. See your info.log if the router was killed and restarted.

[Metta]

No the router has remained up and running throughout.  

Restarting the client (Tomcat based web application) appears to have resolved the issue for now.  

This is the first time this issue has occured.

[IIT Software]

We don't have an open issue concerning IndexOutOfBoundsException nor do we have a fix between 7.0.2 and the current 7.3.0. Are you sure this was thrown from a SwiftMQ class and not from Tomcat. Would also be great if you could provide a more detailed stack trace.

[Metta]

Hi there, we've been doing some digging - unfrotunately there is no detailed stacktrack but it does look as though the exception was thrown in a Mule (1.4.3) class

org.mule.providers.jms.Jm11Support.getJndiDestination()

Although looking at that method, this exception has to have been thrown while executing the following line of code:

     temp = context.lookup(name);

[Metta]

We never did find out the cause for this java.lang.IndexOutOfBoundsException issue.  I'm guessing the current response would be to upgrade to 2.x so we're going to do that.

[Metta]

We never did find out the cause for this java.lang.IndexOutOfBoundsException issue.  I'm guessing the current response would be to upgrade to 2.x so we're going to do that.