Makarand,
this
could also be a problem that was reported some days ago
regarding the thread safetey of WSSecurityEngine (in WSS4J
1.1.0).
This
can cause the same symptoms. I'll just working on that topic
for
version 1.1.0. The next version of WSS4J (the head of SVN) does
not
have
this problem because of a different way to instantiate the
WSSecurityEngine parts.
Regrads,
Werner
-----Ursprüngliche Nachricht-----
Von: makarand sovani [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 26. Oktober 2005 02:43
An: [email protected]
Betreff: How to initialize bouncy castle libraries on Tomcat Startup ?We have a web services application which uses Tomcat + Axis + ws4j combination. Sometimes we get decryption failure while processing concurent encrypted messages. We believe this happens becuase the bouncy castle libraries do not get initialized fully.We would like to initialize WSSecurityEngine object completely upon Tomcat ( + axis) startup. This way the library will be initialized completely.Is there configuration we can specify in server-config.wsdd file which will process a handler or initialize library upon Tomcat startup. Something similar to load-on-startup parameter in web.xml file ?Any pointers will be appreciated.Thanks,Makarand
