There's additional information in the server log after startup about MBeans 
being the root cause:

=ERROR [main] (org.jboss.deployment.scanner.URLDeploymentScanner:527) - 
Incomplete Deployment listing:
  | 
  | --- Incompletely deployed packages ---
  | [EMAIL PROTECTED] { 
url=file:/C:/jboss-4.0.2/server/default/deploy/administration.ear }
  |   deployer: [EMAIL PROTECTED]
  |   status: Deployment FAILED reason: URL 
file:/C:/jboss-4.0.2/server/default/tmp/deploy/tmp56868administration.ear-contents/system_web-exp.war/
 deployment failed
  |   state: FAILED
  |   watch: file:/C:/jboss-4.0.2/server/default/deploy/administration.ear
  |   altDD: null
  |   lastDeployed: 1117826809387
  |   lastModified: 1117826796000
  |   mbeans:
  | 
  | --- MBeans waiting for other MBeans ---
  | ObjectName: jboss.web.deployment:id=324750195,war=system_web.war
  |   State: FAILED
  |   Reason: org.jboss.deployment.DeploymentException: URL 
file:/C:/jboss-4.0.2/server/default/tmp/deploy/tmp56868administration.ear-contents/system_web-exp.war/
 deployment failed
  | 
  | --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
  | ObjectName: jboss.web.deployment:id=324750195,war=system_web.war
  |   State: FAILED
  |   Reason: org.jboss.deployment.DeploymentException: URL 
file:/C:/jboss-4.0.2/server/default/tmp/deploy/tmp56868administration.ear-contents/system_web-exp.war/
 deployment failed
  | 
  | 
  | =DEBUG [main] 
(org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread:151) - 
Notified that enabled: true
  | =DEBUG [main] (org.jboss.deployment.scanner.URLDeploymentScanner:300) - 
Started jboss.deployment:flavor=URL,type=DeploymentScanner
  | =DEBUG [main] (org.jboss.system.ServiceController:433) - Starting dependent 
components for: jboss.deployment:flavor=URL,type=DeploymentScanner dependent 
components: []
  | =DEBUG [main] (org.jboss.deployment.MainDeployer:971) - End deployment 
start on package: jboss-service.xml
  | =DEBUG [main] (org.jboss.deployment.MainDeployer:776) - Deployed package: 
file:/C:/jboss-4.0.2/server/default/conf/jboss-service.xml
  | =DEBUG [main] (org.jboss.web.tomcat.tc5.Tomcat5:518) - Saw 
org.jboss.system.server.started notification, starting connectors
  | = INFO [main] (org.apache.coyote.http11.Http11Protocol:188) - Starting 
Coyote HTTP/1.1 on http-0.0.0.0-8080
  | = INFO [main] (org.apache.jk.common.ChannelSocket:366) - JK: ajp13 
listening on /0.0.0.0:8009
  | = INFO [main] (org.apache.jk.server.JkMain:342) - Jk running ID=0 
time=0/250  config=null
  | = INFO [main] (org.jboss.system.server.Server:456) - JBoss (MX MicroKernel) 
[4.0.2 (build: CVSTag=JBoss_4_0_2 date=200505022023)] Started in 2m:1s:635ms

Also, I forgot to say, I'm using j2sdk1.4.2_06.

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3880214#3880214

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3880214


-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.  
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
_______________________________________________
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to