MDB behavior on failed deployment

Question

I have an MDB that is failing due to a user exception when WL first starts up and tries to initialize the free bean pool. WL seems to try twice and then gives up. The console shows that the JMS connection is active, but the Pooled Beans Current Count is zero. No messages are processed from the queue.
What is the implemented behavior for this scenario. Will the EJB ever recover? Is there a way to specify the number of retries or the time between retries? I'm running WLS 8.1 SP6.

Answer 1

So what you are saying is that radio and checkboxes don't retain their state when validation fails?
Checkboxes are always troublesome because of their design. If not selected, they don't submit any value - so you have to specifically unset them.
My first instinct would be to look at the formbean which you are populating from, and see what (if anything) modifies its values.
- for originally loading the new user page is it an action or JSP? Does it apply any default values to the form?
- check the "input" page you redirect to when validation fails. Is it an action or a JSP?
- is the same form being uses on the newUser jsp and whatever action you are submitting it to?
- is there a form reset() method?
My theory is that the "input" page you are redirecting to when validation fails is an action, and it sets some values on the form prior to loading.
But thats just a guess at this point. Its hard to debug this without a working example. Its been a while since I worked with struts, and never with annotations providing the validation.
Suggestion for debugging: dump the contents of the form bean at strategic points in the process to see that the values are what you think they should be.
- running the save action
- just after validation
- on the jsp page.
Hope this helps some,
evnafets