-
1. Re: problem deploy in jboss 4.0.5.
peterj Jan 17, 2007 11:04 AM (in response to litalh)Is there a stack trace earlier in the log? That should show the root cause. Most likely, something to do with the META-INF/jboss-service.xml file, though it could even be a class not found issue.
-
2. Re: problem deploy in jboss 4.0.5.
litalh Jan 22, 2007 4:49 AM (in response to litalh)hi,
These are the debug information when trying to deploy:
2007-01-16 19:29:52,280 DEBUG [org.jboss.deployment.MainDeployer] Starting deployment of package: http://localhost:8080/AppSight/download/installer?filename=/jboss/AppSightInstallerService.deployer
2007-01-16 19:29:52,280 DEBUG [org.jboss.deployment.MainDeployer] Starting deployment (init step) of package at: http://localhost:8080/AppSight/download/installer?filename=/jboss/AppSightInstallerService.deployer
2007-01-16 19:29:52,280 DEBUG [org.jboss.deployment.MainDeployer] Copying http://localhost:8080/AppSight/download/installer?filename=/jboss/AppSightInstallerService.deployer -> C:\jboss\jboss-4.0.5.GA_Inst\jboss-4.0.5.GAInst\server\default\tmp\deploy\tmp14799installer
2007-01-16 19:29:53,639 DEBUG [org.jboss.deployment.JARDeployer] Found entry: 'META-INF/jboss-service.xml', matching: 'jboss-service.xml', rejecting jar
2007-01-16 19:29:53,639 DEBUG [org.jboss.deployment.MainDeployer] No deployer found for url: http://localhost:8080/AppSight/download/installer?filename=/jboss/AppSightInstallerService.deployer
2007-01-16 19:29:53,639 DEBUG [org.jboss.deployment.MainDeployer] deployment waiting for deployer: http://localhost:8080/AppSight/download/installer?filename=/jboss/AppSightInstallerService.deployer
2007-01-16 19:29:53,639 DEBUG [org.jboss.deployment.MainDeployer] Watching new file: http://localhost:8080/AppSight/download/installer?filename=/jboss/AppSightInstallerService.deployer
2007-01-16 19:29:53,639 DEBUG [org.jboss.deployment.MainDeployer] Deployment of package: http://localhost:8080/AppSight/download/installer?filename=/jboss/AppSightInstallerService.deployer is waiting for an appropriate deployer.
It seems there is something with the jboss-server.xml. Do you know what might be the problem with it ? Any idea what I need to check on it ?
Thanks again,
Lital