We are using portal 3.1.4. Until this weekend, I believe no one has put in batch report parameters. We tested some changes, and it worked until we went to production. The LID versions work. The test environment works. In production, inquiry, next, previous, and delete work; however, add, change, and validate do not for every batch program tried. The response is immediate. The message is "Request timed out. No additional details to provide" followed by "Error retrieving form data: error code 200." There are no errors recorded in latm.log, ladb.log, IOS.log, WebSphere logs, and IIS logs. I have compared the servlet and static content on the webserver. I have done univver in various directoris to compare versions. I have looked at the logan.env, PoolMgr.properties, eli.properties, and lajs.cfg. I have changed my test environment for a few things, and nothing makes test fail. I was hoping someone had some suggestions.
The environment/portal was decommission on 7/31/2008, so we purchased the extended support which ran through 5/31/2009 and couldn't be extended. I think it is one of those situations where no one previously liked putting in batch jobs in portal, and we have someone who likes to only use portal.
Patching the parser isn't the issue as it is working in the test environments which are the same version.