RE: [ebxmlms-general] Triggering a Incoming Listener

[Steven H. <sh...@te...>]

I probably didn't explain properly.

This is a production system, which up until last Friday was working fine.
For reasons unknown, hermes stopped executing the handler for this
particular message type causing an outage for these documents.  There were
no error logs, our client alerted us.  

Thankfully, these messages were relatively low impact.

Last night, after reading through the source code and gaining a stronger
understanding of the system, we executed the following steps:

Hermes shutdown
Apphandler shutdown
Ran the SQL: 'Trunc msh.mshconfig' 
move aside of the 'objects*' files in  '~msh/objectStore'
Start of hermes
Start of apphandler

Hermes and the app handler immediately found the 56 delayed messages and
started extracting them for handling by the rest of our system, something it
steadfastly refused to do.

We are unsure if a restart of just hermes/tomcat would have just fixed the
problem.  But removing the config and the serialised objects was undertaken
to give it an extra kick along.

The signature of the documents in the database was that hermes believed they
were 'undelivered' (that is, a c_sequencenumber of -9998, not -9999), so
they should have been found by the query that looks for undelivered
messages.  I'll will attempt to read the code further to understand where
this could have gone amiss.

-----Original Message-----
From: ebx...@li...
[mailto:ebx...@li...] On Behalf Of David
Webber (XML)
Sent: Tuesday, 7 June 2005 12:07 AM
To: ebx...@li...
Subject: Re: [ebxmlms-general] Triggering a Incoming Listener

Steven,

You have to change the default handler, also check the CPA settings in the
CPA table in Hermes.

The documentation tells you how to write your own handler - and to modify
the existing one.

See the PDF file from the freebxml.org site on the dangerous goods example.

DW