This discussion is archived
1 Reply Latest reply: Apr 12, 2012 9:57 AM by 929352 RSS

Infinispan 4.2.1 on Weblogic 12c

929352 Newbie
Currently Being Moderated
Hello,
My web application tries to instantiate a DefaultCacheManager using an infinispan-config.xml.

When I deploy the application on Weblogic 12c, I am seeing the following exception:

Caused By: java.io.IOException:
Exception Description: Duplicate Property named [properties] found on class [org.infinispan.config.GlobalConfiguration$GlobalJmxStatisticsType]
at org.infinispan.config.InfinispanConfiguration.newInfinispanConfiguration(InfinispanConfiguration.java:264)
at org.infinispan.config.InfinispanConfiguration.newInfinispanConfiguration(InfinispanConfiguration.java:282)
at org.infinispan.config.InfinispanConfiguration.newInfinispanConfiguration(InfinispanConfiguration.java:136)
at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:243)
at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:229)

Further down the stack trace, I see the following:

Caused By: javax.xml.bind.JAXBException:
Exception Description: Duplicate Property named [properties] found on class [org.infinispan.config.GlobalConfiguration$GlobalJmxStatisticsType]
- with linked exception:
[Exception [EclipseLink-50072] (Eclipse Persistence Services - 2.3.2.v20111125-r10461): org.eclipse.persistence.exceptions.JAXBException
Exception Description: Duplicate Property named [properties] found on class [org.infinispan.config.GlobalConfiguration$GlobalJmxStatisticsType]]
at org.eclipse.persistence.jaxb.JAXBContext$TypeMappingInfoInput.createContextState(JAXBContext.java:832)
at org.eclipse.persistence.jaxb.JAXBContext.<init>(JAXBContext.java:143)
at org.eclipse.persistence.jaxb.JAXBContextFactory.createContext(JAXBContextFactory.java:142)
at org.eclipse.persistence.jaxb.JAXBContextFactory.createContext(JAXBContextFactory.java:129)
at org.eclipse.persistence.jaxb.JAXBContextFactory.createContext(JAXBContextFactory.java:93)
at org.eclipse.persistence.jaxb.JAXBContextFactory.createContext(JAXBContextFactory.java:83)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:263)
at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:250)
at javax.xml.bind.ContextFinder.find(ContextFinder.java:447)
at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:652)
at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:599)
at org.infinispan.config.InfinispanConfiguration.newInfinispanConfiguration(InfinispanConfiguration.java:221)
at org.infinispan.config.InfinispanConfiguration.newInfinispanConfiguration(InfinispanConfiguration.java:282)
at org.infinispan.config.InfinispanConfiguration.newInfinispanConfiguration(InfinispanConfiguration.java:136)
at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:243)
at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:229)


I am NOT using EclipseLink or any other JPA provider in my web application. Neither am I using JAXB. I am assuming that the EclipseLink JAXB provider is being provided by WebLogic. I looked at the decompiled class GlobalConfiguration$GlobalStatisticsType and saw the "properties" property occuring only once.

This worked well on JBoss 5.

I tried looking for any articles or blogs for Infinispan deployment on WebLogic and couldn't find any.

Does anybody have any suggestions for me?

Thanks.
  • 1. Re: Infinispan 4.2.1 on Weblogic 12c
    929352 Newbie
    Currently Being Moderated
    It was the JAXB implementation that was the problem.

    EclipseLink Moxy 2.3.2 is the JAXB provider in WebLogic 12c.

    Eclipse has fixed a bug in this area https://bugs.eclipse.org/bugs/show_bug.cgi?id=376509

    The fix in the nightly build for Moxy 2.3.3.

    Not sure what the procedure is for applying EclipseLink patches to WLS.

    In the meantime, upgrading to Infinispan 5.1.3 as suggested in its forums. This solves the problem.

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points