[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [smila-dev] processing bug in v0.8

Hi Tom,

sorry, I've never seen this before.

Cheers,
Juergen.

Am 18.04.2012 11:31, schrieb Thomas Menzel:

Hi folks,

 

Has someone of you encountered this problem before?

… I know, I know, this is an old version - but it runs at a customer.

 

2012-04-12 10:52:07,552 ERROR [QueueWorker-Listener@552327108               ]

listener.ListenerWorker                       -

org.eclipse.smila.connectivity.queue.worker.ListenerException:

[Add_SuchkernPipeline, thread:0] processMessage

        at

org.eclipse.smila.connectivity.queue.worker.internal.listener.ListenerWorker.parseMessage(ListenerWorker.java:295)

        at

org.eclipse.smila.connectivity.queue.worker.internal.listener.ListenerWorker.run(ListenerWorker.java:123)

        at java.lang.Thread.run(Thread.java:662)

Caused by: org.eclipse.smila.datamodel.xml.DeserializationException:

java.io.StreamCorruptedException: invalid stream header: 00000000

        at

org.eclipse.smila.datamodel.xml.XmlSerializationUtils.deserialize(XmlSerializationUtils.java:200)

        at

org.eclipse.smila.connectivity.queue.worker.internal.listener.ListenerWorker.parseMessage(ListenerWorker.java:261)

        ... 2 more

Caused by: java.io.StreamCorruptedException: invalid stream header: 00000000

        at

java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:782)

        at java.io.ObjectInputStream.<init>(ObjectInputStream.java:279)

        at

org.eclipse.smila.datamodel.xml.XmlSerializationUtils.deserialize(XmlSerializationUtils.java:196)

        ... 3 more

 

 

It appears that under processing load the internal AMQ contains an illegal JMS entry, i.e. one that just contains zeros and no record and hence the exception when parsing.

The result is that the message is never remove from the AMQ and smila then re-tries it again and again, till kingdom come, causing 99% load on the server.

 

I will create a fix in the branch for this by just logging an ERROR here and pushing the message into the DLQ but I was wondering what might create this message - hence the question.

 

PS: manual resolution is to shutdown smila and kill the AMQ store.

 

Thomas Menzel @ brox IT-Solutions GmbH

 



Taglocity Tags: smila