Here's my setup: I have a client that looks up and uses a bean that is deployed on a
server. This server is part of a cluster, however the particular bean is only located
on that one server.
Now the problem: if I move the bean in the cluster from one server to another the next
invocation of on
addNotificationListener on an RMIAdaptor throws the following exception when adding
the notification listener I put in my previous message:
| java.rmi.MarshalException: error marshalling arguments; nested exception is:
| java.io.NotSerializableException: be.ugent.pbackx.client.MyRMIL
Sorry to bring up this old thread, but I have the same questions and the links don't
work anymore. How does one setup a remote notification listener? I can't seem to find
any help in the JBoss docs and the information on the wiki is for listener MBeans
deployed on the server.
What I tried alre
it's pretty easy:
* Compile your classes with the AspectJ compiler and packages them as you usually do.
* Put the aspectjrt.jar somewhere in the classpath ... the easiest would be the lib
dir of your server.
I'm not sure what kind of parameters you want to pass. It looks like you are using
code
the RMIAdaptor has 2 query methods which you might find useful: queryMBeans and
queryNames.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3845917#3845917
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3845917
I figured it out myself. Apparently what I wanted is not possible in 3.2.2 but it is
in 3.2.5. In 3.2.5 (and possibly earlier version too, but certainly not 3.2.2) The
ClusterPartition mbean has a NodeAddress attribute which can be set to the correct
bind address.
View the original post :
http
I have a clustered machine with 2 interfaces that's using TCP and TCPPING to connect
and have specified the bind_addr both in the TCP protocol and through the --host
switch. However the DefaultPartition keeps reporting the other interface address as
the node name.
This results in faulty HAJNDI
You need to add all your beans to a jboss.xml file that maps EJB names to JNDI names.
This is explained in the previous messages.
Furthermore I think you are looking up "ejb" instead of the actual bean you want,
which would be something like "OPCAISSESB".
View the original post :
http://www.j
At a glance, you're code seems to be ok.
Possibly you're seeing the same problem that is discussed here:
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=35509
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3841357#3841357
Reply to the post :
http://
I have a cluster of 6 machines. Each of those has 2 network interfaces, one "uplink"
to the outside world and one on which the cluster should do its messaging.
As far as cluster and ha-jndi message go it's easy to configure the bind address so
that all communications is over the second "cluster"
If you disable farming you can manually decide which bean gets deployed where in your
deployment descriptors. Or by simply deleting the correct archive in the deploy
directory (this might remove other beans too of course, so be careful)
If you don't want to give up the convenience of farming I t
I would like to experiment a with the xpetstore application and AOP so I tried to
deploy it on both JBoss 3.2.4RC2 and 4.0.0DR4 but I get a parse exception that I did
not encounter when deploying the exact same ear on 3.2.3:
16:56:24,820 INFO [STDOUT] org.jboss.ejb.plugins.cmp.ejbql.ParseExcept
I just started experimenting with Javassist and I already ran into trouble on the
first tutorial page (the method interception one). If I compile and execute the
example I get the following output (no files were changed):
--- pojo.noop(); ---
<<< Entering SimpleInterceptor
<<< Entering MethodInt
13 matches
Mail list logo
