Apache Tomcat server.xml parse exception - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

aleksandar.sharkoski
Posts: 4
Joined: Tue Oct 05, 2010 12:46 pm

Apache Tomcat server.xml parse exception

I was trying to create installer for my J2EE application but got nowhere due to parsing exception on tomcat's server xml.
To make things simpler I tried to create installer which would install empty tomcat server and register it as windows service.
This is what I did:
Downloaded apache-tomcat-6.0.26 from the official site,(tried with 5.53 too)
Downloaded Advanced installer 7.7 trial from this site,
Started Advanced Installer and created new Tomcat project using the wizard,
- File>New and from the java tab "Tomcat Web Application"
- Next>Next>Exe setup file>Next>next>
- checked the "Tomcat files are placed directly in application folder" checkbox and pointed to the root of my tomcat root foldfer
- checked all checkboxes to offer the user to specify custom ports and selected "automatically use free port" for every port field
- next>next> unchecked java validation> next> next and finish
- the project builds and after that I run the setup file
- it lets me chose different ports for tomcat. On my pc 8080 was busy so it offered 8081 and also 8005 to 8006, I also uncheck the "run tomcat after install "
After the installation is complete I try to start the service manually but no luck.
Tomcat logs an parsing exception on service.xml config file.
The config file is really messed up. You can get the "original" and "generated" service.xml files and see the differences.

OS: Windows 7 professional, 64Bit edition.

Is there some known workaround for these? Does someone else had this problem?
Perhaps some older version of Advanced Installer that doesn't have this bug?


Regards,
--
Aleksandar
Attachments
generated.xml
server.xml from the application installation dir.
(35.97 KiB) Downloaded 341 times
original.xml
The original server.xml file that comes in the tomcat 6 distribution.
(19.55 KiB) Downloaded 308 times
aleksandar.sharkoski
Posts: 4
Joined: Tue Oct 05, 2010 12:46 pm

Re: Apache Tomcat server.xml parse exception

More specifically, the error is in connector and listeners tags in server.xml.
The tomcat service can be successfully started if I go to server.xml in the installed directory of my test app and manually replace the connector and listeners tags.

--
Aleksandar
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Apache Tomcat server.xml parse exception

Hi Aleksandar,

I'm not sure why this happens. Can you please send us the .AIP (project) file you are using and a verbose log of the installation to support at advancedinstaller dot com so we can investigate them?

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Apache Tomcat server.xml parse exception

Hi,

This behavior is caused by a bug in Advanced Installer. Thank you for bringing it to our attention. A bugfix will be included in a future version.
Until then you can try this:
- go to "Files and Folders" page
- right-click "Application Folder" and select "Properties" menu
- go to "Synchronize" tab and click on "Filters" button
- in Edit Filters dialog go to "Exclude Filters" tab
- create a new filter with this pattern:

Code: Select all

server.xml
- select "Apply pattern only to files"
- rebuild your project

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
aleksandar.sharkoski
Posts: 4
Joined: Tue Oct 05, 2010 12:46 pm

Re: Apache Tomcat server.xml parse exception

Thanks, Ill try this right away.
aleksandar.sharkoski
Posts: 4
Joined: Tue Oct 05, 2010 12:46 pm

Re: Apache Tomcat server.xml parse exception

This worked just fine.
Thanks again.

Return to “Common Problems”