Hi,
recently I had two problems somehow related. <br/>
1) Setting the setConnectTimeout for an URLConnection has no effect<br/>
2) Deploying a war file from a servlet using JSR88 times out with the following error:<br/>
Deployment of application failed - Upload file failed: no server response received
<p>
After doing some research for problem 1) I found a <a href="
http://forums.java.net/jive/thread.jspa?messageID=206189">topic</a> with the solution. Setting the jvm option [b]com.sun.enterprise.server.ss.ASQuickStartup[/b] to [b]false[/b] solved the connect timeout issue.
</p>
<p>Regarding problem 2) I've tried deploying using a client application and everything worked well. When I tried to execute the same code from a servlet, ~10s later it fails and the ProgressListener I'm using to monitor the ProgressObject returned by the DeploymentManager.distribute method gives me the message: Deployment of application failed - Upload file failed: no server response received
</p>
<p>
Setting the jvm-option [b]com.sun.enterprise.server.ss.ASQuickStartup[/b] to [b]false[/b] also solved the problem.
</p>
<p>Anyone knows what is the true purpose of the option [b]com.sun.enterprise.server.ss.ASQuickStartup[/b]? Why is the [b]DeploymentManager.distribute[/b] method affected? And what implications it may have on other APIs that use connection resources?
</p>
Thanks,<br/>
Vitor
[Message sent by forum member 'bytec0de' (bytec0de)]
http://forums.java.net/jive/thread.jspa?messageID=207962