I have made some changes in codebase deployed it to webserver for DEV env. And asked user to test it's not working the java loading screen comes and disappears I read somewhere it's a problem with multiple JRE or firewall but no user has only one JRE/JAWS(1.4.2_07) on his machine. The QA env was containing the old code so It run fine even with JRE/JAWS(1.4.2_07) Hmmm.. (not again!! ) No I checked with jaws 1.5.0_11 and JRE 1.4.2_05 and dev is also running fine but I can't upgrade JAWS on user machine as it is not used in his organization yet,I also checked with jaws 1.2 and JRE 1.4.2_05 and it's running fine for dev again it should work "out of the box". On my machine JRE/JAWS(1.4.2_05) is displaying the same behavior as on user machine JRE/JAWS(1.4.2_07). So I thought let's get the code from webserver put it locally for both dev and QA make changes in JNLP so it can pick resources from local file system and check it for JRE/JAWS(1.4.2_05) and it's running fine both in case of qa and dev story so far
First of all am I pointing to the right location or not?
The docs directory is same as what I am pointing to because once I delete any of the resource the program fails to launch both in case of dev/qa
OK so I started with three version 1.2.,1.4.2_05,1.5.0_11 all three using JRE 1.4.2_05
1.2 And 1.5.x are running fine in both cases (dev/qa) also there was one particular version 1.4.2_11 that is working fine also on my colleague's machine,
Problem is with 1.4.2_05 it loads the jar required and than there is one javaw.exe(that is for application itself we can assume)running in background for ever but no application appears in case of dev,
It works fine in case of qa.
I see four possibilities
1. I made some changes in code deployed on dev that is faulty that is why it is not running
(As we can see its running fine with other clients this can�t be true)
2. There is some issue with the client compatibility
(This can�t be true first because the client loads the jars and enables jvm to run javaw.exe also same client is performing fine in case of qa)
3. There is some issue with the server compatibility
(This also can�t be true as program is running fine when I use any client other than 1.4.2_05)
Than I tried downloaded code on my local machine of both the qa and dev in separate folder made changes in jnlp so I can load jars from local file system using them
And in this case both clients are running smoothly against the code of qa and dev both
So I don�t see it as a code level problem.
So why in 1.4.2_05 + (dev/qa) combination the thing disappears after downloading the jar with one javaw.exe in background?
I am totally confused as of now 4. This can be an issue of client+server compatibility.
sorry for the long post
Is there something that I am missing?
Or making a false assumption?
P.S. I am following �uninstall ritual [ April 05, 2007: Message edited by: prateek urmaliya ]
this message brought to you by .... PIE! .... it's yummy! ;)
Story like this gets better after being told a few times. Or maybe it's just a tiny ad: