Bug 268109 - Tomcat 5.5.27 - Cant startup the OSGI framework
Summary: Tomcat 5.5.27 - Cant startup the OSGI framework
Status: RESOLVED DUPLICATE of bug 268464
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: BIRT (show other bugs)
Version: 2.3.1   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 2.5.0 M7   Edit
Assignee: Jandor Bian CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 268464
Blocks:
  Show dependency tree
 
Reported: 2009-03-11 09:37 EDT by Jan Debertshaeuser CLA
Modified: 2009-03-24 23:55 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Debertshaeuser CLA 2009-03-11 09:37:22 EDT 
When I use BIRT-Framework in our Webapplication we get the following stack trace:

org.eclipse.birt.core.exception.BirtException: Cant startup the OSGI framework
at org.eclipse.birt.core.framework.Platform.startup(Platform.java:91)
...

We have another installation of the same webapplication which works fine.
So after some research we found out that the problem is the context definition in the tomcat server.xml

The working installation is defined as:

<Context path="/application" docBase="/opt/application/Application.war">
...
</Context>

The installation that is NOT working is defined as:

<Context path="/application/test" docBase="/opt/application/Application.war">
...
</Context>

So tomcat unzips the WAR file in the webapps directory as "application#test" which seems to cause the problem that the BIRT runtime is not able to start because it does not find the required plugins.

If we change the context definition to just a basic URL like "/application" instead of using a "subfolder" like "/application/test" it works fine.

CentOS 4.4
Tomcat 5.5.27
JDK 1.5.0_12
BIRT (according to plugin Version) 2.3.1

Thanks a lot,

Jan
Comment 1 Jandor Bian CLA 2009-03-12 22:30:27 EDT 
After debug we found out this is a eclipse bug, and I have submit it. See the following bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=268464
Comment 2 Jan Debertshaeuser CLA 2009-03-13 03:12:02 EDT 
(In reply to comment #1)
> After debug we found out this is a eclipse bug, and I have submit it. See the
> following bug:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=268464
> 

Thank you !
Comment 3 Wei Yan CLA 2009-03-24 23:55:13 EDT 

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