[kringdahl]

Yeah, the only challenge with moving to 2.1 or 2.2 is that we're running AS 4.2.2 which uses JBoss AOP 1.5. I was trying to avoid having to deal with custom class loading due to the dependence on AOP 2.0

[manik]

So I'm guessing you are using POJO Cache?

[kringdahl]

Yes that's right, we are using Pojo Cache

[fredrikj]

I'm pretty sure that upgrading to JBC 2.1.0 GA and JGroups 2.6.2 did resolve the "not in started state" errors for us. Unfortunately we ran into other issues when using sync replication on versions > 2.0.0 so we're still running 2.0.0.

[manik]

What other issues are these? Have you brought these up on the forums or raised JIRAs?

[fredrikj]

Posted here: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=135172

[kringdahl]

Just to loop back on my efforts to integrate JBoss Cache 2.1.1.GA with AS 4.2.2.GA. I have this mostly working. It required upgrading the AOP deployer in the AS to JBoss AOP 2.0.0 (I used CR8) and also using the new pluggable-instrumentor.jar as the javaagent. JBoss Cache 2.1.1.GA appears to have solved the startup issue I was previously seeing...at least I have not been able to reproduce it since and it was regularly reproducible in my environment in the past. Just a couple of questions regarding 2.1.1.GA though:

1) Is 2.1.0.GA the latest Pojo Cache release? Right now, I have taken Pojo Cache 2.1.0.GA and Core Cache 2.1.1.GA. I do not see any newer releases in the SF downloads page or the maven repositories, not even for 2.2.0.

2) (Maybe this should go to the Pojo Cache forum but it's all sort of related) We are seeing a new problem where Lists and Sets are not working properly following the upgrade. Specifically, we use a JDBC cache loader. The lists work fine until we bring the cluster down and back up again. When we do, all of the lists and sets appear as empty. What's weirder, if we execute .size() or take some other action on the collection, the list attributes come in. Has anyone seen this before? I'm fairly certain this is related to the AOP switch. I've triple checked that the aop config file is correct.

[manik]

"kringdahl" wrote:
Just to loop back on my efforts to integrate JBoss Cache 2.1.1.GA with AS 4.2.2.GA. I have this mostly working. It required upgrading the AOP deployer in the AS to JBoss AOP 2.0.0 (I used CR8) and also using the new pluggable-instrumentor.jar as the javaagent.

Great. Perhaps you could document what you did on this wiki page to help others who would like to do the same? Would be much appreciated. :-)

"kringdahl" wrote:

1) Is 2.1.0.GA the latest Pojo Cache release? Right now, I have taken Pojo Cache 2.1.0.GA and Core Cache 2.1.1.GA. I do not see any newer releases in the SF downloads page or the maven repositories, not even for 2.2.0.

Yes, 2.1.0 is the latest. The reason being we didn't want to make another GA release on POJO Cache with a CR of JBoss AOP. Both jbosscache-core and jbosscache-pojo will go GA with 2.2.0 though.

"kringdahl" wrote:
2) (Maybe this should go to the Pojo Cache forum but it's all sort of related) We are seeing a new problem where Lists and Sets are not working properly following the upgrade. Specifically, we use a JDBC cache loader. The lists work fine until we bring the cluster down and back up again. When we do, all of the lists and sets appear as empty. What's weirder, if we execute .size() or take some other action on the collection, the list attributes come in. Has anyone seen this before? I'm fairly certain this is related to the AOP switch. I've triple checked that the aop config file is correct.

Yes - could you please raise this on the POJO Cache forums and we'll attend to it there.

Thanks!
Manik