aspose file tools*
The moose likes Websphere and the fly likes RAD publish timeouts Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Websphere
Bookmark "RAD publish timeouts" Watch "RAD publish timeouts" New topic
Author

RAD publish timeouts

Brian Mulholland
Ranch Hand

Joined: Mar 12, 2009
Posts: 61
My project is moving from WAS 6 to WAS 7. The app has been deployed elsewhere in WAS, but now we're testing a developer deployment, and getting publishing problems on a machine where I have published to WAS 7 under RAD successfully in the past. The difference is we upgraded DB2 to 9.5 since the last time I tried. There may be other differences, but that is one.

So the publish takes awhile, I see some debug messages from my app telling me it is initting AND getting data from the database. But inevitably, the publish fails. In addition to a timeout popup, in the console I see:

[5/28/10 13:16:43:096 EDT] 00000014 HttpConnectio E HttpConnection.run: java.lang.IllegalStateException: 0 response bytes written, but Content-Length header equals 51487
[5/28/10 13:16:43:096 EDT] 00000014 FfdcProvider I com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on C:\Program Files\IBM\SDP\runtimes\base_v7\profiles\WTE_APPSRV7_FEP1\logs\ffdc\server1_4ba74ba7_10.05.28_13.16.43.0964887782656570167823.txt com.ibm.ws.http.HttpConnection.run 483


So I went to that files and it says:

[5/28/10 13:16:43:096 EDT] FFDC Exception:java.lang.IllegalStateException SourceId:com.ibm.ws.http.HttpConnection.run ProbeId:483 Reporter:com.ibm.ws.management.connector.soap.SOAPConnection@51445144
java.lang.IllegalStateException: 0 response bytes written, but Content-Length header equals 51487
at com.ibm.ws.http.HttpResponse.finish(HttpResponse.java:97)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:754)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:497)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1527)

What goes on here? Why would the app init and seem to run, but then the publish fail? These errors are so vague they aren't really helping point me at anything.
 
It is sorta covered in the JavaRanch Style Guide.
 
subject: RAD publish timeouts