This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 257690 - cannot deploy on jboss 4.2
Summary: cannot deploy on jboss 4.2
Status: RESOLVED DUPLICATE of bug 261243
Alias: None
Product: WTP ServerTools
Classification: WebTools
Component: jst.server (show other bugs)
Version: 3.1   Edit
Hardware: PC All
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Rob Stryker CLA
QA Contact: Tim deBoer CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-05 05:20 EST by Dimitar Giormov CLA
Modified: 2009-02-05 17:07 EST (History)
5 users (show)

See Also:


Attachments
ear file from jboss deploy folder. (13.98 KB, application/octet-stream)
2008-12-11 03:06 EST, Dimitar Giormov CLA
no flags Details
web xml from the tmp folder (64.00 KB, text/xml)
2008-12-11 03:07 EST, Dimitar Giormov CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dimitar Giormov CLA 2008-12-05 05:20:31 EST
I am not sure if this is the right component if not please redirect.

Trying to deploy on jboss J2ee 1.4 or 5.0 projects using the J2ee Smoke test and the deploy fails with:

2:17:53,655 ERROR [MainDeployer] Could not initialise deployment: file:/Users/gormov/jboss-4.2.3.GA/server/default/deploy/ear14.ear
org.jboss.deployment.DeploymentException: Failed to parse WEB-INF/web.xml; - nested throwable: (org.jboss.deployment.DeploymentException: Invalid XML: file=file:/Users/gormov/jboss-4.2.3.GA/server/default/tmp/deploy/tmp64801ear14.ear-contents/web14-exp.war//WEB-INF/web.xml@1:87; - nested throwable: (org.xml.sax.SAXParseException: Content is not allowed in trailing section.))
	at org.jboss.web.AbstractWebContainer.parseMetaData(AbstractWebContainer.java:755)
	at org.jboss.web.AbstractWebContainer.init(AbstractWebContainer.java:356)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
	at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
	at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
	at org.jboss.deployment.SubDeployerInterceptorSupport.init(SubDeployerInterceptorSupport.java:119)
	at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.init(SubDeployerInterceptorSupport.java:172)
	at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:87)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
	at $Proxy45.init(Unknown Source)
	at org.jboss.deployment.MainDeployer.init(MainDeployer.java:872)
	at org.jboss.deployment.MainDeployer.init(MainDeployer.java:895)
	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:809)
	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
	at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
	at $Proxy9.deploy(Unknown Source)
	at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
	at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:610)
	at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
	at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
	at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
Caused by: org.jboss.deployment.DeploymentException: Invalid XML: file=file:/Users/gormov/jboss-4.2.3.GA/server/default/tmp/deploy/tmp64801ear14.ear-contents/web14-exp.war//WEB-INF/web.xml@1:87; - nested throwable: (org.xml.sax.SAXParseException: Content is not allowed in trailing section.)
	at org.jboss.metadata.XmlFileLoader.getDocument(XmlFileLoader.java:342)
	at org.jboss.metadata.XmlFileLoader.getDocument(XmlFileLoader.java:272)
	at org.jboss.web.AbstractWebContainer.parseMetaData(AbstractWebContainer.java:748)
	... 42 more
Caused by: org.xml.sax.SAXParseException: Content is not allowed in trailing section.
	at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
	at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
	at org.jboss.metadata.XmlFileLoader.getDocument(XmlFileLoader.java:328)
	... 44 more
Comment 1 Dimitar Giormov CLA 2008-12-05 05:33:59 EST
also there were no errors in eclipse error log
Comment 2 Angel Vera CLA 2008-12-05 08:02:46 EST
The exception seems to indicate that the jboss code is failing in parsing the web.xml at line 87. 

Sending over to the Rob for further investigation, this might not be a WTP failure but rather an adopter failure.
Comment 3 Max Rydahl Andersen CLA 2008-12-05 08:59:31 EST
what is in the web.xml file ?
Comment 4 Dimitar Giormov CLA 2008-12-10 04:33:12 EST
I could not find anything strange in the web.xml

It was auto generated by XDoclet 1.2.3
the project contained 1 servlet.
Comment 5 Rob Stryker CLA 2008-12-10 16:46:12 EST
Can you attach either the web.xml (from the server, not your project space) or the generated ear file? 
Comment 6 Dimitar Giormov CLA 2008-12-11 03:06:55 EST
Created attachment 120158 [details]
ear file from jboss deploy folder.
Comment 7 Dimitar Giormov CLA 2008-12-11 03:07:24 EST
Created attachment 120159 [details]
web xml from the tmp folder
Comment 8 Rob Stryker CLA 2008-12-11 10:55:00 EST
After extracting the ear, and extracting the war, there is trailing content inside the web.xml. All sorts of giberish. It seems the ear was not properly created. 

Just clicking on the web.xml attachment shows a parse error, so clearly the web.xml is not well-formed. 

How would I run these smoke tests to help debug this? 
Comment 9 Dimitar Giormov CLA 2008-12-15 03:36:54 EST
http://wiki.eclipse.org/J2EE_Smoke_Test_(WTP_3.0)

up till the ejb part is enough. (J2ee 1.4)

Looking at the source of XML I cannot find anything wrong with it.
And the parser gives an error somewhere in the commented lines.
Comment 10 Dimitar Giormov CLA 2009-01-26 05:11:47 EST
something I didn't tried till soon 
Try the same scenario with WTP 3.0.4
and it works, so the problem is clearly in 3.1 code.
Comment 11 Dimitar Giormov CLA 2009-01-26 05:21:28 EST
it looks like this is the reason
https://bugs.eclipse.org/bugs/show_bug.cgi?id=261243

I will put the bug as depends on
Comment 12 kiril mitov CLA 2009-02-03 05:08:43 EST
Reproduced under gentoo linux. Mark OS as All
Comment 13 Angel Vera CLA 2009-02-05 17:07:54 EST
Having fixed the depending problem. I am confident that the changes will apply
to this bug, and the problem is indeed caused by the same bug. 

Thus, I am removing the depends on, and marking as dup of 261243.


*** This bug has been marked as a duplicate of bug 261243 ***