Bugs item #598335, was opened at 2002-08-21 16:25
Message generated for change (Settings changed) made by ejort
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=598335&group_id=22866
Category: None
>Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Kevin Conner (kevinconner)
Assigned to: Nobody/Anonymous (nobody)
Summary: Mbeans not deploying/redeploying
Initial Comment:
OS: windows NT/windows 2000/Solaris
JDK 1.3.0, 1.3.1, 1.4.0
This is a transcript of emails sent to the jboss-
users list.
First Email:
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.
Second Email:
> Would it be possible to solve this problem by
recognizing the
> communication
> failure, marking it with a special value in
lastModified, and
> doing nothing
> until a real response was obtained?
The only problem is that this isn't a communication
failure. The
request is getting to the server and the server is
closing the socket
without generating a response.
The current getLastModified code does not
differentiate between a
FileNotFoundException (404 response), a general
IOException and a
successful connect without any response. The
exists method is
similar in that it may cause a mbean to be
undeployed because of
a communication glitch and not a 404 response.
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 :-).
Of course you may find that when you go to
redeploy you will get hit
again and will end up with an undeployed mbean.
But you can't cope
with everything :-). At least this window only
happens when you
believe there is a change to apply.
Kev
P.S. I'm still no further on the netboot server side,
the problem
disappears once I add a certain amount of
debugging :-).
Third Email:
> 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
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=598335&group_id=22866
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
