Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Intelligence (Analytics)
WebSphere 7 -- CannotStartupOSGIPlatform
lenburt
Hi there -- i thought i posted this earlier in the week but i do not see it out there now.
I am trying to deploy an application to WebSphere 7 -- BIRT 3.7.1 -- we have it running fine under 2.6.1.
Just trying the installation verification (test.rptdesign) i get the following stack trace.....any ideas?...i assume i am missing some configuration. There seems to be a problem with the Registry provider? -- thx, len
error.CannotStartupOSGIPlatform
org.eclipse.birt.core.exception.BirtException: error.CannotStartupOSGIPlatform
at org.eclipse.birt.core.framework.Platform.startup(Platform.java:81)
at org.eclipse.birt.report.service.ReportEngineService.setEngineContext(ReportEngineService.java:328)
at org.eclipse.birt.report.service.BirtViewerReportService.setContext(BirtViewerReportService.java:1022)
at org.eclipse.birt.report.servlet.ViewerServlet.__getContext(ViewerServlet.java:148)
at org.eclipse.birt.report.servlet.BirtSoapMessageDispatcherServlet.doGet(BirtSoapMessageDispatcherServlet.java:151)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:718)
at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
at org.eclipse.birt.report.servlet.BirtSoapMessageDispatcherServlet.service(BirtSoapMessageDispatcherServlet.java:122)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1655)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1595)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:131)
at com.cgi.cacs.birt.filters.CACSBirtSecurityFilter.doFilter(CACSBirtSecurityFilter.java:201)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116)
at org.eclipse.birt.report.filter.ViewerFilter.doFilter(ViewerFilter.java:68)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:77)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:895)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:932)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:500)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3810)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:276)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:931)
at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1583)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:183)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:455)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:384)
at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:83)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1550)
Caused by: org.eclipse.birt.core.framework.FrameworkException: Cant register the ExtensionRegistry classpath
at org.eclipse.birt.core.framework.jar.ServiceLauncher.startup(ServiceLauncher.java:99)
at org.eclipse.birt.core.framework.Platform.startup(Platform.java:75)
... 38 more
Caused by: org.eclipse.core.runtime.CoreException: Extension registry provider is already set.
at org.eclipse.core.internal.registry.RegistryProviderFactory.setDefault(RegistryProviderFactory.java:31)
Find more posts tagged with
Comments
JasonW
Can you give some more detail on how you have birt deployed and how you are running it? As you know BIRT 3.7 uses a POJO runtime. This allows the engine to be deployed as a set of Jars instead of using plugins. In 3.7.2 we will also be adding an additional package download that functions similar to the 2.6.2 and earlier runtime. It will continue to use osgi. If you want to give it a try, you can use the RC1 candidate download located here:
http://download.eclipse.org/birt/downloads/build.php?build=M-R1-3.7.2RC1-201201171144
Look for Report Engine OSGi deployment.
Jason
lenburt
Jason -- i have just figured out the issue --- we have a servlet filter in our application which in the init method goes out and initializes the BIRT engine (3.7.1). We are certifying on both WebLogic and WebSphere so i have had both running on my Windows machine for testing. It seems that both containers cannot be running at the same time on the same machine or BIRT initialization will have problems. I do not really understand what is going on under the covers but when i brought down my WebLogic instance, the WebSphere instance started working without throwing that error.
Obviously this is not a typical production runtime situation so i am fine with only having one app server at a time running on a machine.
I will stick with 3.7.1 for now but thanks for the offer of a pre-release. regards, len
lenburt
duplicate
lenburt
duplicate
lenburt
duplicate
lenburt
Ok , looks like i still have the issue...i did a reboot of my machine, restarted WebSphere and still got the error.
Jason -- i may try that pre-release you suggested of 3.7.2. -- len
lenburt
Jason - here is some additional information on the problem; i have attached the full stack trace from the WebSphere error log along with the o/s version and WebSphere version.
Here is how i reproduce the problem:
1) download the BIRT 3.7.1 runtime
2) deploy the included birt.war
3) try the verification URL jsp (e.g.
http://xwineccacs11.ams.com:9081/birt/index.jsp)
4) click the link to trigger the BIRT Viewer
5) error.CannotStartupOSGIPlatform occurs
This works fine on WebLogic 10.x.
This also works fine with the 2.6.2 engine download under WebSphere 7 so i am not sure where the problem lies.
I did notice that in the 2.6.2 runtime there is a 'platform' dir under WEB-INF but in 3.7.x that is not there.
I did try the 3.7.2 RC that you provided the link to and had the same results.
Are there others out there who are using the BIRT Viewer with 3.7.1?....what am i missing?
any help is appreciated. regards, len
JasonW
Did you try the OSGi runtime or the normal 3.7.2 runtime?
http://birtworld.blogspot.com/2012/01/birt-runtime-addition.html
Also can you try to re-war the WebViewerExample directory?
Jason
lenburt
Jason - ok, the first time i did try the 'normal' 3.7.2 runtime and that failed. I just tried the verification test with the OSGI birt.war and that worked. I will rebuild the war with our application and give it a try. Is the basic difference that the OSGI package uses jar files instead of plugins? -- thx, len
JasonW
That is correct.
Jason
