Geek Answers Handbook

Why aren't explicit class path entries found in the start of the WebSphere Liberty profile?

When I launch my application with a WebSphere Liberty profile (release 2013.11.0.0 - 8.5.5.Next Alpha with extended content), many warnings appear:

W SRVE9967W: The manifest class path dhbcore.jar can not be found in jar file wsjar:file:[blablabla] or its parent.
W SRVE9967W: The manifest class path jms.jar can not be found in jar file wsjar:file:[blablabla] or its parent.
W SRVE9967W: The manifest class path com.ibm.mq.jmqi.jar can not be found in jar file wsjar:file:[blablabla] or its parent.
W SRVE9967W: The manifest class path dhbcore.jar can not be found in jar file wsjar:file:[blablabla] or its parent.
W SRVE9967W: The manifest class path rmm.jar can not be found in jar file wsjar:file:[blablabla] or its parent.
W SRVE9967W: The manifest class path jndi.jar can not be found in jar file wsjar:file:[blablabla] or its parent.
W SRVE9967W: The manifest class path ldap.jar can not be found in jar file wsjar:file:[blablabla] or its parent.
W SRVE9967W: The manifest class path fscontext.jar can not be found in jar wsjar:file:[blablabla] or its parent.
W SRVE9967W: The manifest class path providerutil.jar can not be found in jar file wsjar:file:[blablabla] or its parent.
W SRVE9967W: The manifest class path jta.jar can not be found in jar file wsjar:file:[blablabla] or its parent.
W SRVE9967W: The manifest class path com.ibm.mq.ese.jar can not be found in jar wsjar:file:[blablabla] or its parent.

I tried to fix this using server start --cleanas indicated in this forum thread , but that didn't help. There is a similar question here on Stackoverflow, but before the PMR was opened at IBM, as suggested, maybe someone already had this problem and solved it already.

+4
source share
1 answer

, JAR ( wsjar:file:...) META-INF/MANIFEST.MF Class-Path, JAR (, dhbcore.jar), JAR .

, , , .. : Class-Path JAR.

: 8.5.5.4 <logging hideMessage="SRVE9967W"> . ( ). . .

+8

More articles:


All Articles