This content has been marked as final.
Show 2 replies
-
1. juddi configuration question
tcunning May 14, 2011 4:58 PM (in response to rajasundaram)jUDDI doesn't enforce the tier limits.
Is this the same error you were having in the thread before on the production machine? Have you increased the connection pool and verified that the setting took?
Have you definitely gone in and made sure that org.jboss.soa.esb.failure.detect.removeDeadEPR is set to true? Can you try removing all the juddi tables in the database?
-
2. juddi configuration question
rajasundaram May 14, 2011 8:43 PM (in response to tcunning)Yes we added the remove dead elf property on esb box where we deployed our esbs but we didn't make changes on client location. And yes we increased connections to high number 150. And whenever we restart our servers we drop all tables in juddi. Is there anyways to monitor jms connections