> It might be better to change the code so that the getLastModified > and exists can be rolled into one method, returning a does not > exist (1), comms error (2), lastModified unknown (3) or > lastModified time (4). It can then choose to ignore the information > for 2 and 3 but not 1 and 4. This will then cope with some of the > network's (or server's) foibles :-).
I've made a stab at this, changing the internal Scanner class for
URLDirectoryScanner. The problem still occurs but it does not
force a redeployment of the mbean. This is fine for our current
purpose and I've rolled it out to our netboot environments.
Of course this does not deal with the issue of what is happening on
the netboot server side, it is still closing the connection without
sending a response. I'll try to find some time to look at it at a
later date :-).
Can someone please take a look at the changes I've made? If they are
acceptable can they be rolled into the current versions? If not can
they be used as a basis for a fix?
Thanks,
Kev
Kevin Conner
Orchard Information Systems Limited
Newcastle Technopole, Kings Manor
Newcastle Upon Tyne, NE1 6PA. United Kingdom
Registered in England, Number 1900078
Tel: +44 (0) 191-2032536 Fax: +44 (0) 191 2302515
URLDirectoryScanner.java
Description: Binary data
