Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

On startup: Bundle com.ibm.team.app.web@start not found

I've beat my head against a wall on this one for some time now, so it's about time that I 'stop and ask for directions'.

I'm using RTC 3.0 with Derby and Tomcat 5.5 on Windows 7.

After starting up tomcat (both as a service and via server.startup.bat), I get the familiar 'unable to connect' upon visiting any of the root/ccm/jts pages. However, netstat shows that the server is listening on the correct port. All tomcat logs are clean and the catalina log shows a successful startup. However, I am getting a couple log files within the 'work' directory that look like trouble:

...\work\jts\eclipse\configuration\<timestamp>.log
...\work\ccm\eclipse\configuration\<timestamp>.log

Within both of these logs is the following:


!SESSION 2011-04-19 21:29:57.488 -----------------------------------------------
eclipse.buildId=unknown
java.fullversion=J2RE 1.5.0 IBM J9 2.3 Windows 7 amd64-64 j9vmwa6423ifx-20100510 (JIT enabled)
J9VM - 20100509_57823_LEdSMr
JIT - 20091016_1845ifx7_r8
GC - 20091026_AA
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US

!ENTRY org.eclipse.osgi 4 0 2011-04-19 21:29:57.488
!MESSAGE Bundle com.ibm.team.app.web@start not found.

!ENTRY org.eclipse.osgi 4 0 2011-04-19 21:29:57.639
!MESSAGE Error starting bundle: initial@reference:file:plugins/com.ibm.team.repository.web.jts_1.1.0.v20110208_0112.jar/
!STACK 0
org.osgi.framework.BundleException: A fragment bundle cannot be started: com.ibm.team.repository.web.jts_1.1.0.v20110208_0112 [46]
at org.eclipse.osgi.framework.internal.core.BundleFragment.startWorker(BundleFragment.java:228)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:280)
at org.eclipse.core.runtime.adaptor.EclipseStarter.startBundle(EclipseStarter.java:1128)
at org.eclipse.core.runtime.adaptor.EclipseStarter.startBundles(EclipseStarter.java:1121)
at org.eclipse.core.runtime.adaptor.EclipseStarter.loadBasicBundles(EclipseStarter.java:640)
at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:301)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.eclipse.equinox.servletbridge.FrameworkLauncher.start(FrameworkLauncher.java:288)
at org.eclipse.equinox.servletbridge.BridgeServlet.init(BridgeServlet.java:65)
at javax.servlet.GenericServlet.init(GenericServlet.java:212)
at com.ibm.team.repository.server.servletbridge.JazzServlet.init(JazzServlet.java:35)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1139)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:966)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3996)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4266)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:760)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:740)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:544)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:634)
at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:561)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:496)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1203)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:319)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:120)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1022)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:736)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at org.apache.catalina.core.StandardService.start(StandardService.java:448)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:700)
at org.apache.catalina.startup.Catalina.start(Catalina.java:552)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433)

!ENTRY org.eclipse.osgi 4 0 2011-04-19 21:29:57.932
!MESSAGE Bundle com.ibm.team.repository.web.jts_1.1.0.v20110208_0112 [46] is not active.


I already tried reinstalling and it didn't help any. I thought maybe the firewall was getting in the way, but disabling it did nothing. I'm pretty new to Windows 7 though, so I may have missed something. If it wasn't for these two logs, I'd continue down the firewall/windows settings route.

Some of the constants in the log look funny, so I'm going to continue there. Would this sort of problem prevent the root web content from loading? I realize these are mostly tomcat issues, but the osgi bundle loading is a jazz issue.

Any help will be appreciated.

0 votes



One answer

Permanent link
I reinstalled a third time with a freshly downloaded repo and now tomcat works, but the osgi error logging still occurs. This must be an expected failure?

0 votes

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: Apr 19 '11, 10:17 p.m.

Question was seen: 4,925 times

Last updated: Apr 19 '11, 10:17 p.m.

Confirmation Cancel Confirm