HTTPConnection in startup servlet works only with hot deploy

[venuwin]

Hi,

* We are developing a J2EE application in which we have to download some XML when the WAR file(Say MyApp.WAR.) is deployed.

* I have put the downloading XML logic to be called from a startup servlet. So far so good.

* I have 5 customers for whom i would have to have 5 WAR files like MyApp1.WAR,MyApp2.WAR,MyApp3.WAR,MyApp4.WAR,MyApp5.WAR but all these WAR files have to download XMLs which are unique for each WAR.

Real Problem comes when i restart JBoss. The deployer does not proceed further after the line in my code where i read the input stream, which results in the failure of all further deployments in the same server.

u = new URL (url);
httpConn = ( HttpURLConnection ) u.openConnection ( );
 httpConn.setRequestMethod ( "GET" ) ;
Log.info(AppConstants.LOG_CATEGORY," before http connection");
httpConn.connect () ;
Log.info(AppConstants.LOG_CATEGORY,"after http connection");
if(httpConn !=null)
 {
 try
 {
 inputStream=httpConn.getInputStream(); // here is where it hangs
 }catch (Exception e) {
Log.error(AppConstants.LOG_CATEGORY,"Exception fetching inputstream :"+e);
 }

* In the above code, it doesnt even throw an exception, just hangs .

* to fix this, i have to remove all 5 WAR files out of deploy folder, start JBoss and then place all the WAR files back to the deploy folder. It works fine.
* I don't understand why it works only with Hot deploy and not with a restart.
* Please let me know if anything could be done on this (or) in case you need more info.

Thanks
Venu

[peterj]

Where is the above code located?

Do you have your servlets set for load-on-startup?

What is the value of the variable 'url' in the above code?

[venuwin]

the code is in startup servlet
yes it is defined for load-on-startup in web.xml

[skajotde]

Do you have isolated classloaders ?

If no, probably you are doing something after deploying this is required to proper deploy. And on next deploy eg some static variable is on server (it is the same classloader) and deploying finish successful.

[venuwin]

there is no question of some variable after deploy. The deployer hangs at the line where i try to read the input stream of XML URL. Your idea is ruled out. Please avoid giving vague answers .

[jaikiran]

"venuwin" wrote:
there is no question of some variable after deploy. The deployer hangs at the line where i try to read the input stream of XML URL. Your idea is ruled out. Please avoid giving vague answers .

Venu,

Everyone here is trying to help you. Please do not be rude to fellow posters.

[venuwin]

Jaikiran,

already enough info is given in my first post. I am even not of that kind. When you are posting something, please see to that the problem is fully understood or ask for more info. I am glad to hear from our folks for more info.

[jaikiran]

Venu, you probably missed this question

"PeterJ" wrote:

What is the value of the variable 'url' in the above code?

[venuwin]

Jai,

the value is http://static.xyz.com/cat/up.xml

[peterj]

OK, that rules out some obscure timing issue, which could have been the problem if the url was http://localhost:8080/xxxxx.

I cannot think of any plausible reason why an outbound connection would have an issue during jbossas startup (even jbossas itself has at time made such requests).

All I can think of at this time to try turning off load-on-startup.

[jaikiran]

In addition to what Peter said, is static.xyz.com some external site or is it a virtual host that you have setup?

[venuwin]

Hi Peter,

the URL http://static.xyz.com/cat/up.xml refers to the local machine only. But just to make the code work with any URL for that matter, we have not replaced it with localhost. Would that make a difference. If so, why does it work after JBoss startup. Or does JBoss has some problems in inbound connections before it could start completely ?

[skajotde]

"venuwin" wrote:
there is no question of some variable after deploy. The deployer hangs at the line where i try to read the input stream of XML URL. Your idea is ruled out. Please avoid giving vague answers .

there was question about cause of problem. I give one of answer and asked are you using isolated classloader. Maybe your code (or some jboss code) modify java way connecting to http and on next deploy old classess are holded. Thanks for rude answer ;/

[peterj]

Is http://static.xyz.com/cat/up.xml handled by the JBossAS you are starting up or by some other process (such as IIS or HTTPD)?

If it is handled by JBossAS, then you have hit a timing hole - the app server is just not ready to service your request - you will have to wait until the app server is finished initializing. Hence my suggestion of removing load-on-startup. An alternative that might work is to create a deploy.last directory within the deploy directory and place you WAR files there. They will then not be deployed until everything else is deployed.

And to echo Kamil's sentiments, if I would have realized that you would have been rude to someone who you think did not adequately answer your question, I never would have responded to your original post because honestly, other than the possible timing issue, I have no idea what the problem is, I am just trying to eliminate possibilities (which I am sure is what Kamil was attempting also).

[venuwin]

Hi Peter and Kamil,

I'm sorry if i had hurt any one of you. Would try this and let you know. The logic has been removed from startup servlet and put in a separate thread which would be invoked on first hit of index.jsp. This works fine.

Thanks Men !