Grails

Can't start app with IBM JDK 1.6 because generated web.xml is always empty

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: Project infrastructure
  • Labels:
    None
  • Environment:
    IBM JDK 1.6 - 64 bit
    Windows 7 - 64 bit
    STS 2.8.1
    Grails 2.0

Description

When switch to the IBM JDK 1.6 (64bit) in STS 2.8.1, application can't be started because the generated web.xml is always empty.
It seemed that the "generateWebXml" in _GrailsPackage.groovy has problem in IBM JDK 1.6.

I debuged it and found the problem is in the following lines of the method "generateWebXml":

pluginManager.doWebDescriptor(webXml, sw)
webXmlFile.withWriter { it << sw.toString() }

But I can't find the "doWebDescriptor(webXml, sw)" method in webXml plugin (version 1.4.1).
Where is this method that I can continue to debug?

The steps to reproduce this problem:
1. Swith to IBM JDK 1.6 (64bit) in STS 2.8.1
2. Start the app by using "run-app"
Then we will see the error of this:

| Running Grails application
| Error 2012-02-05 13:11:37,036 [main] ERROR digester.Digester  - Parse Fatal Error at line -1 column -1: Premature end of file
Message: Premature end of file
   Line | Method
->> 114 | doStart   in org.grails.plugins.tomcat.InlineExplodedTomcatServer
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
|   102 | start     in org.grails.plugins.tomcat.TomcatServer
|   175 | doCall .  in _GrailsRun_groovy$_run_closure5_closure12
|   152 | doCall    in _GrailsRun_groovy$_run_closure5
|   120 | runInline in _GrailsRun_groovy
|    66 | doCall    in _GrailsRun_groovy$_run_closure1
^    33 | doCall .  in RunApp$_run_closure1
| Error 2012-02-05 13:11:37,136 [main] ERROR startup.ContextConfig  - Parse error in application web.xml file at file:/C:/Users/<myAccountName>/.grails/2.0.0/projects/TM/resources/web.xml
Message: Premature end of file
   Line | Method
->> 114 | doStart   in org.grails.plugins.tomcat.InlineExplodedTomcatServer

3. Check the web.xml and found it's empty.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Graeme Rocher added a comment -

It isn't in the webxml plugin, it exists in core. See the DefaultPluginManager class.

Show
Graeme Rocher added a comment - It isn't in the webxml plugin, it exists in core. See the DefaultPluginManager class.
Hide
Permalink
Aaron Brown added a comment -

Found this jira entry when I encountered a similar issue on a somewhat different system, so I wanted to share my details to help identify the common elements.

Websphere 8, which includes an IBM flavor of Java 1.6 JDK. Full version data below.
Grails 2.0.3
Command line tools - SpringSource was not involved
Windows XP (32 bit, of course. Yeah, I know, Windows XP blah blah...)

1. grails create-app testapp
2. cd testapp
3. grails run-app

Same error in the original JIRA appears, web.xml does not get generated, run-app fails. When I use Sun JDK 1.7, these errors to not appear. I have not yet tried Sun JDK 1.6 for comparison. That's next on my list.

Full Java JDK details:
C:\>java -version
java version "1.6.0"
Java(TM) SE Runtime Environment (build pwi3260sr9fp1ifix-20110329_01(SR9 FP1+IZ95654+IZ91385+IZ95150))
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr9-20110324_78506 (JIT enabled, AOT enabled)
J9VM - 20110324_078506
JIT - r9_20101028_17488ifx3
GC - 20101027_AA)
JCL - 20110203_01

Show
Aaron Brown added a comment - Found this jira entry when I encountered a similar issue on a somewhat different system, so I wanted to share my details to help identify the common elements. Websphere 8, which includes an IBM flavor of Java 1.6 JDK. Full version data below. Grails 2.0.3 Command line tools - SpringSource was not involved Windows XP (32 bit, of course. Yeah, I know, Windows XP blah blah...) 1. grails create-app testapp 2. cd testapp 3. grails run-app Same error in the original JIRA appears, web.xml does not get generated, run-app fails. When I use Sun JDK 1.7, these errors to not appear. I have not yet tried Sun JDK 1.6 for comparison. That's next on my list. Full Java JDK details: C:\>java -version java version "1.6.0" Java(TM) SE Runtime Environment (build pwi3260sr9fp1ifix-20110329_01(SR9 FP1+IZ95654+IZ91385+IZ95150)) IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr9-20110324_78506 (JIT enabled, AOT enabled) J9VM - 20110324_078506 JIT - r9_20101028_17488ifx3 GC - 20101027_AA) JCL - 20110203_01
Hide
Permalink
Martin Connolly added a comment -

Same problem here - Windows 7 Pro 64-bit SP1, STS 2.9.1, Grails 2.0.3, IBM JDK 6 SR10 FP1. With Grails 1.3.8 all works perfectly.

Show
Martin Connolly added a comment - Same problem here - Windows 7 Pro 64-bit SP1, STS 2.9.1, Grails 2.0.3, IBM JDK 6 SR10 FP1. With Grails 1.3.8 all works perfectly.
Burt Beckwith made changes -
Field Original Value New Value
Description When switch to the IBM JDK 1.6 (64bit) in STS 2.8.1, application can't be started because the generated web.xml is always empty.
It seemed that the "generateWebXml" in _GrailsPackage.groovy has problem in IBM JDK 1.6.

I debuged it and found the problem is in the following lines of the method "generateWebXml":

   pluginManager.doWebDescriptor(webXml, sw)
   webXmlFile.withWriter { it << sw.toString() }

But I can't find the "doWebDescriptor(webXml, sw)" method in webXml plugin (version 1.4.1).
Where is this method that I can continue to debug?

The steps to reproduce this problem:
1. Swith to IBM JDK 1.6 (64bit) in STS 2.8.1
2. Start the app by using "run-app"
Then we will see the error of this:

| Running Grails application
| Error 2012-02-05 13:11:37,036 [main] ERROR digester.Digester - Parse Fatal Error at line -1 column -1: Premature end of file
Message: Premature end of file
   Line | Method
->> 114 | doStart in org.grails.plugins.tomcat.InlineExplodedTomcatServer
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
| 102 | start in org.grails.plugins.tomcat.TomcatServer
| 175 | doCall . in _GrailsRun_groovy$_run_closure5_closure12
| 152 | doCall in _GrailsRun_groovy$_run_closure5
| 120 | runInline in _GrailsRun_groovy
| 66 | doCall in _GrailsRun_groovy$_run_closure1
^ 33 | doCall . in RunApp$_run_closure1
| Error 2012-02-05 13:11:37,136 [main] ERROR startup.ContextConfig - Parse error in application web.xml file at file:/C:/Users/<myAccountName>/.grails/2.0.0/projects/TM/resources/web.xml
Message: Premature end of file
   Line | Method
->> 114 | doStart in org.grails.plugins.tomcat.InlineExplodedTomcatServer

3. Check the web.xml and found it's empty. 		When switch to the IBM JDK 1.6 (64bit) in STS 2.8.1, application can't be started because the generated web.xml is always empty.
It seemed that the "generateWebXml" in _GrailsPackage.groovy has problem in IBM JDK 1.6.

I debuged it and found the problem is in the following lines of the method "generateWebXml":

{code}
pluginManager.doWebDescriptor(webXml, sw)
webXmlFile.withWriter { it << sw.toString() }
{code}

But I can't find the "doWebDescriptor(webXml, sw)" method in webXml plugin (version 1.4.1).
Where is this method that I can continue to debug?

The steps to reproduce this problem:
1. Swith to IBM JDK 1.6 (64bit) in STS 2.8.1
2. Start the app by using "run-app"
Then we will see the error of this:

{code}
| Running Grails application
| Error 2012-02-05 13:11:37,036 [main] ERROR digester.Digester - Parse Fatal Error at line -1 column -1: Premature end of file
Message: Premature end of file
   Line | Method
->> 114 | doStart in org.grails.plugins.tomcat.InlineExplodedTomcatServer
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
| 102 | start in org.grails.plugins.tomcat.TomcatServer
| 175 | doCall . in _GrailsRun_groovy$_run_closure5_closure12
| 152 | doCall in _GrailsRun_groovy$_run_closure5
| 120 | runInline in _GrailsRun_groovy
| 66 | doCall in _GrailsRun_groovy$_run_closure1
^ 33 | doCall . in RunApp$_run_closure1
| Error 2012-02-05 13:11:37,136 [main] ERROR startup.ContextConfig - Parse error in application web.xml file at file:/C:/Users/<myAccountName>/.grails/2.0.0/projects/TM/resources/web.xml
Message: Premature end of file
   Line | Method
->> 114 | doStart in org.grails.plugins.tomcat.InlineExplodedTomcatServer
{code}

3. Check the web.xml and found it's empty.
Affects Version/s 2.0 final [ 11041 ]
Assignee Burt Beckwith [ burtbeckwith ]
Hide
Permalink
Burt Beckwith added a comment -

I was able to get an app running by making two changes. It appears that the XML issue is due to Xalan, so adding an exclude for that in BuildConfig.groovy was the first step:

inherits('global') {
   excludes 'serializer'
}

With that I got segmentation faults and when I disabled the reloading agent those went away:

grails -noreloading run-app

Please test these changes and see if your application runs. I'll check with the developer of the reloading agent to see if there's a better workaround.

Show
Burt Beckwith added a comment - I was able to get an app running by making two changes. It appears that the XML issue is due to Xalan, so adding an exclude for that in BuildConfig.groovy was the first step: inherits('global') { excludes 'serializer' } With that I got segmentation faults and when I disabled the reloading agent those went away: grails -noreloading run-app Please test these changes and see if your application runs. I'll check with the developer of the reloading agent to see if there's a better workaround.
Hide
Permalink
Daniel Mikusa added a comment -

Burt,

Tested your suggestions and they worked for me.

Show
Daniel Mikusa added a comment - Burt, Tested your suggestions and they worked for me.
Hide
Permalink
Francis McKenzie added a comment - - edited

Burt, thanks very much for posting the tips above. I only needed the 'serializer' exclude to get a Grails 2.0.3 app running on IBM JDK 1.7.0, hosted on an OpenVZ VPS running Ubuntu 11.10.

However, I had other problems caused by the fact that ArtefactHandlers were being called in a different order on the IBM JDK - see http://jira.grails.org/browse/GRAILS-5241 This meant that my plugin's ArtefactHandler was being called before Grails's built-in ArtefactHandlers (i.e. those for Controllers, TagLibs, Services, etc.) To fix the problem, I had to recode my plugin's ArtefactHandler to explicitly exclude any Artefacts ending in "Controller", "TagLib" or "Service".

Show
Francis McKenzie added a comment - - edited Burt, thanks very much for posting the tips above. I only needed the 'serializer' exclude to get a Grails 2.0.3 app running on IBM JDK 1.7.0, hosted on an OpenVZ VPS running Ubuntu 11.10. However, I had other problems caused by the fact that ArtefactHandlers were being called in a different order on the IBM JDK - see http://jira.grails.org/browse/GRAILS-5241 This meant that my plugin's ArtefactHandler was being called before Grails's built-in ArtefactHandlers (i.e. those for Controllers, TagLibs, Services, etc.) To fix the problem, I had to recode my plugin's ArtefactHandler to explicitly exclude any Artefacts ending in "Controller", "TagLib" or "Service".
Hide
Permalink
Aitor Alzola added a comment -

Same problem here, (ibm jdk 1.6, Grails 2.0.1), but the proposed workaround is not working for me. Is there any plans/ideas to get this fixed?

Thanks in advance.

Show
Aitor Alzola added a comment - Same problem here, (ibm jdk 1.6, Grails 2.0.1), but the proposed workaround is not working for me. Is there any plans/ideas to get this fixed? Thanks in advance.

People

  • Assignee:
    Burt Beckwith
    Reporter:
    Steven Guo
Vote (2)
Watch (4)

Dates

  • Created:
    Updated: