Bug 810358

Summary: Deployment Failures on EAP6 - beta one due to invalid class paths for nested jars.
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Matty Larose <mlarose>
Component: EEAssignee: Ivo Studensky <istudens>
Status: CLOSED INSUFFICIENT_DATA QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.0.0CC: atangrin, istudens, mlarose, sdouglas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-23 13:54:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Matty Larose 2012-04-05 17:47:59 UTC
Description of problem:

Seeing alot of these messages when deploying our app on EAP6 - Beta1 

11:03:39,672 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry ss_css2.jar in "/content/Halogen.war/WEB-INF/lib/pd4ml-3.6.0fx1.jar"  does not point to a valid jar for a Class-Path reference.

Version-Release number of selected component (if applicable):

EAP6 - Beta1 

How reproducible:


Steps to Reproduce:
1. Copy war to deploy directory with server in standalone mode
2. deploy war.

  
Actual results:

Deploy fails, 


Expected results:
Deploy succeed

Additional info:

Suspect this is fixed upstream with AS7.1.1

https://issues.jboss.org/browse/AS7-4348

Comment 3 David M. Lloyd 2014-05-28 15:42:11 UTC
Can we verify this has been fixed?

Comment 4 Stuart Douglas 2014-09-04 01:36:37 UTC
This should definitely be closed. Those WARN messages do not indicate a deployment failure, so without the actual cause of the deployment failure we don't have any information on what the actual problem was.

Comment 5 Ivo Studensky 2015-06-23 13:54:31 UTC
based on comment 4

Comment 6 Red Hat Bugzilla 2023-09-14 01:28:23 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days