P4
FULL PRODUCT VERSION :
JDK 1.6 update 7
ADDITIONAL OS VERSION INFORMATION :
Windows XP
A DESCRIPTION OF THE PROBLEM :
Java Web Start Error:
The basic question here is how to use jardiff successfully if IP address
of the server where JNLP is hosted changes .Domain name will not be changed .It gives "Java Web Start Error:" if jardiff is used
Run JNLP from website ,it downloads the file.
The downloaded jnlp only has a host name in it. In this case it is "jnlp.concord.org".
What changes is the dns for "jnlp.concord.org". This works fine as long as jardiff is not being used,ie all the jars are downloaded again.
We need to avoid downloading the jars if there is no change.
But when jardiffs are used webstart fails. Hopefully the page above provides enough information to clarify this.
This is a problem with webstart in java 1.6
When jardiffs are being used and the IP address of the jnlp server changes(Same domain name), the application fails to launch.
Changing the IP address of a server is a relatively common thing. Our work around at this point is to change the codebase of all the jars when the server IP changes. This requires end users to download all of the jars again. I'd like to find a better solution then that.
The crux of this problem is that webstart is storing the IP address of the server each jar came from. Then when loading the jar from the cache it is verifying this IP address matches the current IP address of the server using a DNS lookup. If jardiff is not used it seems the jar is just downoaded again, however if jardiff is used then the failed verification is not handled correctly.
A general question I have is whether the IP address should be cached at all when the jar has a version. I assume the IP address is cached so timestamps from different servers aren't compared. But if the jar has a version then timestamps are not compared, the IP doesn't seem to be needed.
See the following article for more information .
http://confluence.concord.org/display/CCTR/Changing+IP+address+of+server+breaks+jardiff
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Run JNLP from website ,it downloads the file.
The downloaded jnlp only has a host name in it. In this case it is "jnlp.concord.org".
What changes is the dns for "jnlp.concord.org". This works fine as long as jardiff is not being used,ie all the jars are downloaded again.
We need to avoid downloading the jars if there is no change.
But when jardiffs are used webstart fails. Hopefully the page above provides enough information to clarify this.
This is a problem with webstart in java 1.6
When jardiffs are being used and the IP address of the jnlp server changes(Same domain name), the application fails to launch.
Changing the IP address of a server is a relatively common thing. Our work around at this point is to change the codebase of all the jars when the server IP changes. This requires end users to download all of the jars again. I'd like to find a better solution then that.
The crux of this problem is that webstart is storing the IP address of the server each jar came from. Then when loading the jar from the cache it is verifying this IP address matches the current IP address of the server using a DNS lookup. If jardiff is not used it seems the jar is just downoaded again, however if jardiff is used then the failed verification is not handled correctly.
A general question I have is whether the IP address should be cached at all when the jar has a version. I assume the IP address is cached so timestamps from different servers aren't compared. But if the jar has a version then timestamps are not compared, the IP doesn't seem to be needed.
See the following article for more information .
http://confluence.concord.org/display/CCTR/Changing+IP+address+of+server+breaks+jardiff
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
jardiff should not give error and it should verify whether there is any difference
and
ACTUAL -
#### Java Web Start Error:
ERROR MESSAGES/STACK TRACES THAT OCCUR :
#### Java Web Start Error:
REPRODUCIBILITY :
This bug can be reproduced always.
---------- BEGIN SOURCE ----------
http://confluence.concord.org/display/CCTR/Changing+IP+address+of+server+breaks+jardiff
---------- END SOURCE ----------
CUSTOMER SUBMITTED WORKAROUND :
Not available
JDK 1.6 update 7
ADDITIONAL OS VERSION INFORMATION :
Windows XP
A DESCRIPTION OF THE PROBLEM :
Java Web Start Error:
The basic question here is how to use jardiff successfully if IP address
of the server where JNLP is hosted changes .Domain name will not be changed .It gives "Java Web Start Error:" if jardiff is used
Run JNLP from website ,it downloads the file.
The downloaded jnlp only has a host name in it. In this case it is "jnlp.concord.org".
What changes is the dns for "jnlp.concord.org". This works fine as long as jardiff is not being used,ie all the jars are downloaded again.
We need to avoid downloading the jars if there is no change.
But when jardiffs are used webstart fails. Hopefully the page above provides enough information to clarify this.
This is a problem with webstart in java 1.6
When jardiffs are being used and the IP address of the jnlp server changes(Same domain name), the application fails to launch.
Changing the IP address of a server is a relatively common thing. Our work around at this point is to change the codebase of all the jars when the server IP changes. This requires end users to download all of the jars again. I'd like to find a better solution then that.
The crux of this problem is that webstart is storing the IP address of the server each jar came from. Then when loading the jar from the cache it is verifying this IP address matches the current IP address of the server using a DNS lookup. If jardiff is not used it seems the jar is just downoaded again, however if jardiff is used then the failed verification is not handled correctly.
A general question I have is whether the IP address should be cached at all when the jar has a version. I assume the IP address is cached so timestamps from different servers aren't compared. But if the jar has a version then timestamps are not compared, the IP doesn't seem to be needed.
See the following article for more information .
http://confluence.concord.org/display/CCTR/Changing+IP+address+of+server+breaks+jardiff
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Run JNLP from website ,it downloads the file.
The downloaded jnlp only has a host name in it. In this case it is "jnlp.concord.org".
What changes is the dns for "jnlp.concord.org". This works fine as long as jardiff is not being used,ie all the jars are downloaded again.
We need to avoid downloading the jars if there is no change.
But when jardiffs are used webstart fails. Hopefully the page above provides enough information to clarify this.
This is a problem with webstart in java 1.6
When jardiffs are being used and the IP address of the jnlp server changes(Same domain name), the application fails to launch.
Changing the IP address of a server is a relatively common thing. Our work around at this point is to change the codebase of all the jars when the server IP changes. This requires end users to download all of the jars again. I'd like to find a better solution then that.
The crux of this problem is that webstart is storing the IP address of the server each jar came from. Then when loading the jar from the cache it is verifying this IP address matches the current IP address of the server using a DNS lookup. If jardiff is not used it seems the jar is just downoaded again, however if jardiff is used then the failed verification is not handled correctly.
A general question I have is whether the IP address should be cached at all when the jar has a version. I assume the IP address is cached so timestamps from different servers aren't compared. But if the jar has a version then timestamps are not compared, the IP doesn't seem to be needed.
See the following article for more information .
http://confluence.concord.org/display/CCTR/Changing+IP+address+of+server+breaks+jardiff
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
jardiff should not give error and it should verify whether there is any difference
and
ACTUAL -
#### Java Web Start Error:
ERROR MESSAGES/STACK TRACES THAT OCCUR :
#### Java Web Start Error:
REPRODUCIBILITY :
This bug can be reproduced always.
---------- BEGIN SOURCE ----------
http://confluence.concord.org/display/CCTR/Changing+IP+address+of+server+breaks+jardiff
---------- END SOURCE ----------
CUSTOMER SUBMITTED WORKAROUND :
Not available