[esb-issues] [JBoss JIRA] Updated: (JBESB-3513) confilct between jboss esb and infinispan hotrod client
Samuele Dell'Angelo (JIRA)
jira-events at lists.jboss.org
Tue Oct 19 09:07:54 EDT 2010
[ https://jira.jboss.org/browse/JBESB-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Samuele Dell'Angelo updated JBESB-3513:
---------------------------------------
Description:
infinispan hotrod client uses common-pool 1.5.4 and it conflicts with spring.esb that uses commons-pool 1.3. If you try to deploy a project that include infinispan hotrod client 4.1.0.FINAL, you will get an exception like this one:
java.lang.NoSuchFieldError: _lifo
at org.infinispan.client.hotrod.impl.transport.tcp.PropsKeyedObjectPoolFactory.<init>(PropsKeyedObjectPoolFactory.java:32)
at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory.start(TcpTransportFactory.java:51)
at org.infinispan.client.hotrod.RemoteCacheManager.start(RemoteCacheManager.java:282)
at org.infinispan.client.hotrod.RemoteCacheManager.<init>(RemoteCacheManager.java:224)
at org.infinispan.client.hotrod.RemoteCacheManager.<init>(RemoteCacheManager.java:231)
at it.seat.igluCache.infinispan.loaders.InfinispanServletListener.contextInitialized(InfinispanServletListener.java:31)
I've found a workaround: replace commons-pool-1.3.jar with commons-pool-1.5.4.jar in spring.esb directory.
was:
infinispan hotrod client uses common-pool 1.5.4 and it conflicts with spring.esb that uses commons-pool 1.3. If you try to deploy a project that include infinispan hotrod client 4.1.0.FINAL, you will get an exception like this one:
java.lang.NoSuchFieldError: _lifo
at org.infinispan.client.hotrod.impl.transport.tcp.PropsKeyedObjectPoolFactory.<init>(PropsKeyedObjectPoolFactory.java:32)
at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory.start(TcpTransportFactory.java:51)
at org.infinispan.client.hotrod.RemoteCacheManager.start(RemoteCacheManager.java:282)
at org.infinispan.client.hotrod.RemoteCacheManager.<init>(RemoteCacheManager.java:224)
at org.infinispan.client.hotrod.RemoteCacheManager.<init>(RemoteCacheManager.java:231)
at it.seat.igluCache.infinispan.loaders.InfinispanServletListener.contextInitialized(InfinispanServletListener.java:31)
I've found a workaround: replace commons-pool-1.3.jar with commons-pool-1.5.4.jar in in spring.esb directory.
> confilct between jboss esb and infinispan hotrod client
> -------------------------------------------------------
>
> Key: JBESB-3513
> URL: https://jira.jboss.org/browse/JBESB-3513
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.8
> Environment: jboss 5.1.0.GA with jboss esb 4.8 deployed on it.
> Reporter: Samuele Dell'Angelo
>
> infinispan hotrod client uses common-pool 1.5.4 and it conflicts with spring.esb that uses commons-pool 1.3. If you try to deploy a project that include infinispan hotrod client 4.1.0.FINAL, you will get an exception like this one:
> java.lang.NoSuchFieldError: _lifo
> at org.infinispan.client.hotrod.impl.transport.tcp.PropsKeyedObjectPoolFactory.<init>(PropsKeyedObjectPoolFactory.java:32)
> at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory.start(TcpTransportFactory.java:51)
> at org.infinispan.client.hotrod.RemoteCacheManager.start(RemoteCacheManager.java:282)
> at org.infinispan.client.hotrod.RemoteCacheManager.<init>(RemoteCacheManager.java:224)
> at org.infinispan.client.hotrod.RemoteCacheManager.<init>(RemoteCacheManager.java:231)
> at it.seat.igluCache.infinispan.loaders.InfinispanServletListener.contextInitialized(InfinispanServletListener.java:31)
> I've found a workaround: replace commons-pool-1.3.jar with commons-pool-1.5.4.jar in spring.esb directory.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the esb-issues
mailing list