Guernsey, Byron (GE Consumer & Industrial) wrote:
The problem was a duplicate worker entry. Apparently, in JK2,
duplicates were ignored. I've written a perl script that converts the
JK2 config to a JK1 config because of the large number of entries- I'll
just need to have it validate that there are no duplicate workers.
Yes. That would be the reason for '*' in between.
Thanks for the responses though. Is there a separate mailing list for
jk1 development where I should post the suggestion to add a simple
test/error message when parsing a duplicate worker?
Sure, tomcat-dev@
Regards,
Mladen.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
