'Double Execution' of Struts Actions

[RonS]

I'm new to Struts and although my application is working, I'm having trouble
figuring out some strange behavior. I've been converting straight JSP/Servlets
to JSP/ActionForm/Actions. It seems that whenever I convert a Servlet to an
Action the JSP and it's associated Action are executed twice on every submission.

The app works fine, but my logs show that the first execution is the 'real'
one (the reported values are what show up on the user web page). But there is
also a log of another pass through the code. I can't figure out where this one
is coming from or going to.

Anyone else seen anything like this?
Thanks - Ron

 

[Wendy Smoak]

I'm new to Struts and although my application is working, I'm having trouble
figuring out some strange behavior. I've been converting straight JSP/Servlets
to JSP/ActionForm/Actions. It seems that whenever I convert a Servlet to an
Action the JSP and it's associated Action are executed twice on every submission.

The app works fine, but my logs show that the first execution is the 'real'
one (the reported values are what show up on the user web page). But there is
also a log of another pass through the code. I can't figure out where this one
is coming from or going to.

Anyone else seen anything like this?

Do you have any JavaScript, possibly onClick() handlers doing a submit();
without a return;? (Both the JavaScript submit and the actual button click
will "work" and you'll get two submits.)

I just tracked one of these down in my own app, and it was a Filter that
called chain.doFilter(...) twice.

 

[RonS]

Do you have any JavaScript, possibly onClick() handlers doing a submit();
without a return;? (Both the JavaScript submit and the actual button click
will "work" and you'll get two submits.)

I just tracked one of these down in my own app, and it was a Filter that
called chain.doFilter(...) twice.

Thanks Wendy
No JavaScript in the app. I'll check for the double chain.doFilter and let you
know.

 

[RonS]

Do you have any JavaScript, possibly onClick() handlers doing a submit();
without a return;? (Both the JavaScript submit and the actual button click
will "work" and you'll get two submits.)

I just tracked one of these down in my own app, and it was a Filter that
called chain.doFilter(...) twice.

No JavaScript and only one chain.doFilter(...) per Filter. Any other
suggestions? ... anyone?