[
https://issues.apache.org/jira/browse/WOOKIE-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752268#comment-13752268
]
Scott Wilson commented on WOOKIE-417:
-------------------------------------
Sounds like the issue is a conflicting version of Log4j on the classpath. I
seem to remember an issue with SLF4J versions and compatibility affecting a
number of projects and this may be the case here, so is worth looking at.
Wookie has the following as its dependencies:
slf4j-log4j12 1.6.4
log4j 1.2.16
I suspect Webspehere may have its own version of Log4J shared across contexts,
and so the presence of another log4j jar in the Wookie WAR may then be negating
it. So one thing to try is removing the log4j jar from within
wookie/WEB-INF/lib.
> Wookie installation on WebSphere 7
> ----------------------------------
>
> Key: WOOKIE-417
> URL: https://issues.apache.org/jira/browse/WOOKIE-417
> Project: Wookie
> Issue Type: Bug
> Affects Versions: 0.14.0
> Environment: windows 7, IBM WebSphere 7 (7.0.0.19), Oracle 11g
> Reporter: Amir Rana
>
> We are not able to install Apache Wookie on WAS 7. After deploying Wookie War
> on WAS 7, during the server restart following exception occurs
> 8/20/13 15:45:26:045 PKT] 0000001b webapp E
> com.ibm.ws.webcontainer.webapp.WebApp notifyServletContextCreated SRVE0283E:
> Exception caught while initializing context: {0}
> java.lang.RuntimeException: Unable to load or initialize PersistenceManager
> class: java.lang.reflect.InvocationTargetException
> How can this issue be resolved ? This issue is blocking for us. The complete
> version of WAS is (7.0.0.19)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
