Given the current implementation, discarding all of an unresponsive client's
registrations after some configurable timeout is one solution. Scott has already fixed
a related bug: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=47243
Long term I suggest configurable transports for JMX no
complains with some socket errors before continuing
(depends on how long I suspend the client).
Server is JBoss 3.2.5 (default + my services). Client uses 3.2.5 jbossall-client.jar.
This is a show stopper problem for me. I'd appreciate any suggestions.
Thanks in advance,
jj
View the original
Apache,
all is well.
Thanks for the help.
jj
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3835759#3835759
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3835759
would be appreciated. Thanks in advance,
jj
Server output:
...
2004-05-14 17:19:08,927 INFO [org.jboss.system.server.Server] JBoss (MX MicroKernel)
[3.2.3 (build: CVSTag=JBoss_3_2_3 date=200311301445)] Started in 23s:481ms
2004-05-14 17:19:15,356 DEBUG [org.apache.tomcat.util.threads.Threa
Run the 'build-all' target first before running the examples.
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3826585#3826585";>View
the original post
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3826585>Reply
to the post
-
Using 323, I have a remote client that recieves jmx notifications by implementing
RMINotificationListener. I instantiate many of these clients. They all receive
notifications correctly.
However, if I kill one of the clients (just as my users do with 'kill -9' whenever
they feel like it), the s
Your listener stub must be deployed on the server. The same can be said for a filter
class you may decide to use. I generally jar the listener stub and the filter together
and then just deploy the jar file.
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3826580#3826580";>View
the ori
I have a remote application that correctly receives filtered notifications (JBoss
3.2.3). Here is the pertinent code:
| InitialContext ctx = new InitialContext(props);
| server = (RMIAdaptor) ctx.lookup("jmx/invoker/RMIAdaptor");
| ...
| Listener liste
