0 Replies Latest reply: Aug 9, 2011 4:59 AM by Martin Phillips RSS

Class Path ... entry does not point to a valid jar for a  Class-Path reference.

Martin Phillips Newbie

I get rather a lot of these warning messages when deploying my rar file to AS7, and a more recent snapshot too

 

 

09:21:40,406 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry com.ibm.mqjms.jar in "/C:/jboss-as-7.1.0.Alpha1-SNAPSHOT/bin/content/wmq.jmsra.rar/com.ibm.mq.jms.admin.jar"  does not point to a valid jar for a Class-Path reference.

09:21:40,406 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry com.ibm.msg.client.jms.jar in "/C:/jboss-as-7.1.0.Alpha1-SNAPSHOT/bin/content/wmq.jmsra.rar/com.ibm.msg.client.jms.internal.jar"  does not point to a valid jar for a Class-Path reference.

09:21:40,406 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry com.ibm.msg.client.provider.jar in "/C:/jboss-as-7.1.0.Alpha1-SNAPSHOT/bin/content/wmq.jmsra.rar/com.ibm.msg.client.jms.internal.jar"  does not point to a valid jar for a Class-Path reference.

09:21:40,406 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry com.ibm.mq.jmqi.jar in "/C:/jboss-as-7.1.0.Alpha1-SNAPSHOT/bin/content/wmq.jmsra.rar/com.ibm.msg.client.wmq.factories.jar"  does not point to a valid jar for a Class-Path reference.

09:21:40,406 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry com.ibm.mq.jmqi.jar in "/C:/jboss-as-7.1.0.Alpha1-SNAPSHOT/bin/content/wmq.jmsra.rar/com.ibm.msg.client.wmq.jar"  does not point to a valid jar for a Class-Path reference.

 

There are more warnings but I won't bore you with them all.

 

Taking the first one, com.ibm.mq.jms.admin.jar, for an example, it does indeed have a Class-path: entry in it's manifest file pointing at com.ibm.mqjms.jar.  com.ibm.mqjms.jar is in the root of the rar file, so I'm rather confused why we're getting a warning on deployment.

 

Another thing that confuses me is why  .../bin/content  appears to be the path to the jar being warned about - I would have expected it to be extracted to a temp directory of some sort and /bin seems a strange place for a temp directory.