|
Re: Failing when deployed (Websphere) [message #639227 is a reply to message #639056] |
Mon, 15 November 2010 16:01 |
|
Josh,
I assume you have seen this link:
http://wiki.eclipse.org/BIRT/FAQ/Deployment#Q:_How_do_I_inst all_BIRT_in_WebSphere.3F
Could this be a permission problem?
Jason
On 11/15/2010 2:12 AM, Josh wrote:
> Hi,
>
> I have developed a J2EE Web application using the report viewer as my
> basis. I have it running perfectly on my local machine in Websphere,
> however when I deploy it, I get the following errors on startup:-
> Log file in WEB-INF\platform\configuration
>
> !SESSION 2010-11-12 20:38:54.710
> -----------------------------------------------
> eclipse.buildId=unknown
> java.fullversion=J2RE 1.5.0 IBM J9 2.3 Windows Server 2003 x86-32
> j9vmwi3223ifx-20080811 (JIT disabled)
> J9VM - 20080809_21892_lHdSMr
> JIT - 20080620_1845_r8
> GC - 200806_19
> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_AU
>
> !ENTRY org.eclipse.update.configurator 4 0 2010-11-12 20:38:54.710
> !MESSAGE Plugin does not have a valid identifier:
> plugins/org.apache.derby.core_10.5.1.1_v20100129/
>
> !ENTRY org.eclipse.update.configurator 4 0 2010-11-12 20:38:54.710
> !MESSAGE Plugin does not have a valid version:
> plugins/org.apache.derby.core_10.5.1.1_v20100129/
>
> !ENTRY org.eclipse.update.configurator 4 0 2010-11-12 20:38:54.913
> !MESSAGE Plugin does not have a valid identifier:
> plugins/org.eclipse.birt.report.data.oda.jdbc_2.6.1.v2010090 9/
>
> !ENTRY org.eclipse.update.configurator 4 0 2010-11-12 20:38:54.913
> !MESSAGE Plugin does not have a valid version:
> plugins/org.eclipse.birt.report.data.oda.jdbc_2.6.1.v2010090 9/
>
> !ENTRY org.eclipse.update.configurator 4 0 2010-11-12 20:38:54.913
> !MESSAGE Plugin does not have a valid identifier:
> plugins/org.eclipse.birt.report.data.oda.sampledb_2.6.1.v201 00909/
>
> !ENTRY org.eclipse.update.configurator 4 0 2010-11-12 20:38:54.913
> !MESSAGE Plugin does not have a valid version:
> plugins/org.eclipse.birt.report.data.oda.sampledb_2.6.1.v201 00909/
>
> !ENTRY org.eclipse.update.configurator 4 0 2010-11-12 20:38:57.960
> !MESSAGE Could not install bundle
> plugins/org.apache.derby.core_10.5.1.1_v20100129/ Error converting
> plugin at C:\Products\WebSphere\AppServer\profiles\AppSrv01\installedA
> pps\LXCell\SPEAR_systest_2_5_0_155.ear\spear_web.war\WEB-INF
> \platform\plugins\org.apache.derby.core_10.5.1.1_v20100129.
>
> !ENTRY org.eclipse.update.configurator 4 0 2010-11-12 20:39:00.163
> !MESSAGE Could not install bundle
> plugins/org.eclipse.birt.report.data.oda.jdbc_2.6.1.v2010090 9/ Error
> converting plugin at
> C:\Products\WebSphere\AppServer\profiles\AppSrv01\installedA
> pps\LXCell\SPEAR_systest_2_5_0_155.ear\spear_web.war\WEB-INF
> \platform\plugins\org.eclipse.birt.report.data.oda.jdbc_2.6. 1.v20100909.
>
> !ENTRY org.eclipse.update.configurator 4 0 2010-11-12 20:39:00.179
> !MESSAGE Could not install bundle
> plugins/org.eclipse.birt.report.data.oda.sampledb_2.6.1.v201 00909/
> Error converting plugin at
> C:\Products\WebSphere\AppServer\profiles\AppSrv01\installedA
> pps\LXCell\SPEAR_systest_2_5_0_155.ear\spear_web.war\WEB-INF
> \platform\plugins\org.eclipse.birt.report.data.oda.sampledb_
> 2.6.1.v20100909.
>
> Exception in Websphere logs:-
> [15/11/10 17:31:44:759 EST] 00000031 SystemErr R
> org.eclipse.birt.report.exception.ViewerException: Fatal error occurred
> when try to startup report engine.
> [15/11/10 17:31:44:759 EST] 00000031 SystemErr R at
> org.eclipse.birt.report.service.ReportEngineService.setEngin
> eContext(ReportEngineService.java:326)
> [15/11/10 17:31:44:759 EST] 00000031 SystemErr R at
> org.eclipse.birt.report.service.BirtViewerReportService.setC
> ontext(BirtViewerReportService.java:1022)
> [15/11/10 17:31:44:759 EST] 00000031 SystemErr R at
> org.eclipse.birt.report.listener.ViewerServletContextListene
> r.contextInitialized(ViewerServletContextListener.java:62)
> [15/11/10 17:31:44:775 EST] 00000031 SystemErr R at
> com.ibm.ws.wswebcontainer.webapp.WebApp.notifyServletContext
> Created(WebApp.java:916)
> [15/11/10 17:31:44:775 EST] 00000031 SystemErr R at
> com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFi
> nish(WebApp.java:354)
> [15/11/10 17:31:44:775 EST] 00000031 SystemErr R at
> com.ibm.ws.wswebcontainer.webapp.WebApp.initialize(WebApp.ja va:337)
> [15/11/10 17:31:44:775 EST] 00000031 SystemErr R at
> com.ibm.ws.wswebcontainer.webapp.WebGroup.addWebApplication(
> WebGroup.java:92)
> [15/11/10 17:31:44:775 EST] 00000031 SystemErr R at
> com.ibm.ws.wswebcontainer.VirtualHost.addWebApplication(Virt
> ualHost.java:157)
> [15/11/10 17:31:44:775 EST] 00000031 SystemErr R at
> com.ibm.ws.wswebcontainer.WebContainer.addWebApp(WebContaine r.java:671)
> [15/11/10 17:31:44:775 EST] 00000031 SystemErr R at
> com.ibm.ws.wswebcontainer.WebContainer.addWebApplication(Web
> Container.java:624)
> [15/11/10 17:31:44:775 EST] 00000031 SystemErr R at
> com.ibm.ws.webcontainer.component.WebContainerImpl.install(W
> ebContainerImpl.java:395)
> [15/11/10 17:31:44:775 EST] 00000031 SystemErr R at
> com.ibm.ws.webcontainer.component.WebContainerImpl.start(Web
> ContainerImpl.java:611)
> [15/11/10 17:31:44:775 EST] 00000031 SystemErr R at
> com.ibm.ws.runtime.component.ApplicationMgrImpl.start(Applic
> ationMgrImpl.java:1306)
> [15/11/10 17:31:44:775 EST] 00000031 SystemErr R at
> com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDep
> loyedObjectStart(DeployedApplicationImpl.java:1165)
> [15/11/10 17:31:44:775 EST] 00000031 SystemErr R at
> com.ibm.ws.runtime.component.DeployedModuleImpl.start(Deploy
> edModuleImpl.java:587)
> [15/11/10 17:31:44:775 EST] 00000031 SystemErr R at
> com.ibm.ws.runtime.component.DeployedApplicationImpl.start(D
> eployedApplicationImpl.java:832)
> [15/11/10 17:31:44:775 EST] 00000031 SystemErr R at
> com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplica
> tion(ApplicationMgrImpl.java:952)
> [15/11/10 17:31:44:775 EST] 00000031 SystemErr R at
> com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializ
> er.run(ApplicationMgrImpl.java:2166)
> [15/11/10 17:31:44:775 EST] 00000031 SystemErr R at
> com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchIniti
> alizer.run(WsComponentImpl.java:342)
> [15/11/10 17:31:44:775 EST] 00000031 SystemErr R at
> com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473)
>
> I have debugged to the point where I have determined that the birt osgi
> application is not loading with all it's components (I believe this is
> effectively what's being reported in the log in the configuration area),
> however I haven't been able to figure out why it's doing this.
>
> Any guidance would be appreciated.
>
> Regards, Josh.
>
|
|
|
Re: Failing when deployed (Websphere) [message #639353 is a reply to message #639227] |
Tue, 16 November 2010 08:55 |
Josh Hall Messages: 31 Registered: October 2010 |
Member |
|
|
Yes, I had read those instructions. The key changes I had made to get BIRT running under Websphere were:-
* changing the class loader order to PARENT_LAST for the Server, EAR and WAR modules
* opening up the Java 2 Security policy files to java.security.AllPermission
I'm on Websphere 6.1/BIRT 2.6.1, so some of the things on those posts weren't applicable.
My hunch is that BIRT is attempting to start up under the Websphere version of OSGi, which might explain the errors reported in the logs in the platform/configuration area. I am not sure how to prove this theory or what to do if that is the case.
With the PARENT_LAST setting, I can't quite see how this would happen, but then again, I am not across the whole OSGi thing either,,,
suggestions?
|
|
|
Re: Failing when deployed (Websphere) [message #639483 is a reply to message #639353] |
Tue, 16 November 2010 17:29 |
|
It should be trying to startup a copy of OSGi in your temp directory.
Can you open a bug for this as the dev team should have access to Websphere.
Jason
On 11/16/2010 3:55 AM, Josh wrote:
> Yes, I had read those instructions. The key changes I had made to get
> BIRT running under Websphere were:- * changing the class loader order to
> PARENT_LAST for the Server, EAR and WAR modules
> * opening up the Java 2 Security policy files to
> java.security.AllPermission
>
> I'm on Websphere 6.1/BIRT 2.6.1, so some of the things on those posts
> weren't applicable.
>
> My hunch is that BIRT is attempting to start up under the Websphere
> version of OSGi, which might explain the errors reported in the logs in
> the platform/configuration area. I am not sure how to prove this theory
> or what to do if that is the case.
>
> With the PARENT_LAST setting, I can't quite see how this would happen,
> but then again, I am not across the whole OSGi thing either,,,
> suggestions?
|
|
|
|
Powered by
FUDForum. Page generated in 0.03893 seconds