There has been some talk over the last day about mbeans not deploying
for various reasons, I have another one to add :-)

Our setup has jboss 3.0.1 jetty acting as a netboot server to developers
machines, again 3.0.1.  I have configured the client jboss servers to use
the URLDirectoryScanner and specified common services using specific URLs.
All configurations are correct (note I am not talking about the security
name issue).

When the scanner is checking for deployment it uses the URLConnection
getLastModified method, which sends a GET request to the server.
Sometimes this GET request is closed without any information coming
back (I haven't chased this part up yet) but the result is that the
lastModified time reported to the scanner will be 0.

If this happens on the first scan then the lastModified date will match
the default date of 0 and therefore the mbean will not be deployed.  If
this happens on a subsequent scan then the mbean will be undeployed and
then redeployed.  This can happen to any mbean.

I spent yesterday chasing this up in the code and have verified it using
a network snooper.  I am now turning my attention to the jboss netboot
server to see why it is not handling the requests.

If anyone has an idea then please let me know, it will save some time on
my part and allow me to continue the development work I am supposed to be
doing :-).

        Kev

P.S. I haven't seen this happen on the server archives but presumably it
can.

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


-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to