File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes BEA/Weblogic and the fly likes Why duplicate submission every 60 seconds? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Products » BEA/Weblogic
Bookmark "Why duplicate submission every 60 seconds?" Watch "Why duplicate submission every 60 seconds?" New topic
Author

Why duplicate submission every 60 seconds?

James Dinho
Greenhorn

Joined: May 24, 2011
Posts: 3
Hi,
for my web application I use Weblogic 10.3.5, Jpa 2.0 and Spring 3.1.
When I execute a search feature a strange thing happens: controller calls back-end side and java routine start (jpa db connection for get results and then java operation). Every one minute (I see this in front end and back end log file) the same functionality restart until Weblogin session (720 seconds) expires (operation during in total about 1 minute ad 30 seconds) . It seems as if there is a timeout of one minute. I have analyzed the status of the request with firebug and it seems that only one request start...but in the log file I see several started of the same functionality.

Can anyone help me?
Jaikiran Pai
Marshal

Joined: Jul 20, 2005
Posts: 9317
    
109

Is Weblogic fronted by some other web server which has some kind of 60 second timeout and which then re-triggers the request?

[My Blog] [JavaRanch Journal]
James Dinho
Greenhorn

Joined: May 24, 2011
Posts: 3
Jaikiran Pai wrote:Is Weblogic fronted by some other web server which has some kind of 60 second timeout and which then re-triggers the request?

Yes, is an apache timeout problem. Thank you! ;)
 
It is sorta covered in the JavaRanch Style Guide.
 
subject: Why duplicate submission every 60 seconds?
 
Similar Threads
Websphere 5.0 - Applecation re-run after 5 Minutes
Interview question
Mutiple threads on a single reqest
Monitoring logs statement in a live log file
Long running request returns no HTTP response