anonymous wrote : When the logger is created, we use getClass() which returns
TreeCache.class and *not* ServiceMBeanSupport.class ! So logging works, just tested
again with INFO and WARN. Maybe you're picking up the wrong log4j.props ? Do you use
-Dlog4j.configuration, eg.
|
| -Dlog4j.configuration=file:c:\log4j.properties ?
I'm picking up the correct log4j.xml but it seems this is a more complex problem than
i thought - I have to derive my own class from TreeCache to be able to use RPC calls -
maybe here is my problem located, i'll have to dig into this further.
anonymous wrote :
| The same thread will of course see its changes made in the same TX. Only other
threads are blocked. This is all as designed.
|
Hmm makes it hard - maybe you could think of adding a method that tells the user if
the cache is in an uncommited transaction?
anonymous wrote : Do you have a small test case that reproduces the problem ?
Actually not really - the test case i use is part of a rather complex framework and
can not easily be separated (I use lots of wrappers and have a lot of dependecies but
i'll see if i can produce a simple test case).
anonymous wrote : There is :-) Have a look at ClusterPartition.startService() and
search for the CONFIG event. You can set some user-defined bytes in an IpAddress,
using {set,get}AdditionalData().
Took me a while to figure out that you are talking about the jboss clustering classes
:)
I tried it but it seems that it doesn't work once the channel is connected. I do get
access to the channel by using a class that is derived from TreeCache but the creation
of the channel is immediatly followed by a connect in the startService()-method if
TreeCache.
My suggestion would be to apply this patch to TreeCache (current cvs head):
| 200c200
| <
| ---
| > protected HashMap channelConfig=null;
| 1000a1001,1009
| > /**
| > * Set configuration options for JChannel, that are passed
| > * down as a CONFIG event upon connection.
| > * @param channelConfig configuration options for the channel
| > */
| > public void setChannelConfig(HashMap channelConfig) {
| > this.channelConfig=channelConfig;
| > }
| >
| 1053a1063,1066
| > if( channelConfig != null ) {
| > channel.down(new org.jgroups.Event(org.jgroups.Event.CONFIG,
channelConfig));
| > channel.getProtocolStack().flushEvents();
| > }
|
This adds a setChannelConfig() method where a HashMap can be supplied that is passed
down the channel right before it connects.
-markus
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3842232#3842232
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3842232
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
