OK, thanks Manik, I will try it later.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4203857#4203857
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4203857
___
jboss-user mailing
This line in your config:
| cache.jdbc.sql-concat=1 || 2
|
may be the issue. AFAIR that was a hack for Derby's non-standard SQL string
concatenation. Try removing that line altogether, or replacing it with
| cache.jdbc.sql-concat=concat(1,2)
|
See the
BTW, i was using JDK1.6 and following is some log output:
2008-12-26 13:28:16,415 [Thread-1] DEBUG (AdjListJDBCCacheLoader.java:147) -
executing sql: select fqn from jbosscache where parent=? (/testRegion)
| 2008-12-26 13:28:16,509 [Thread-1] INFO (ReadThread.java:40) - currently
node
It seems no body care about my problem :(
Anyway, I'm still doing the test and finally find that whenever I write the
following code in my run() method of the reader Thread, the reader has a big
chance to get null from a specific node which should have value, the code is:
@Override
|
