multiple ORACLE Documaker instances reading single jms/hornetq issue.

Documaker's snail waxed zero size PDF's on our production environment, and it took me a day to figure it out, whats wrong with it! :(

below is the setup we had in our production environment.

whats happening here is, that two Documaker instances are reading from single/same jms/hornetq queue, and as Documaker does not have any identifier mechanism for soap messages, as it seems both tries to hold the message and somehow destroys the soap message arrived from ETPM in jms queue, so both Documaker instances endup with generating ZERO size PDF's.

the workaround is to run single Documaker instance per jms/hornetq queue. But this way you d'nt have real time fail-over for Documaker, you have to do manual switching in case of failure!

cheers.

ETPM, Documaker, JMS, LDAP, Database, Conceptual and abstract workflow diagram

ladies, if you are unable to understand how ORACLE ETPM, ORACLE Documaker, JMS/HornetQ, LDAP/OpenDS and Database/Exadata should work together, here is the lazy drawn diagram, i hope you will get an idea about what i have been implementing recently :)

you may consider it as ETPM application data center conceptual design as well;

Cheers