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

Error when starting the Jetty server (Extensions workshop)

Questions
Tags
Users
Badges
Namit Pande
(63●1●13●19) Feb 22 '18, 2:02 p.m.

Hello,

I am on step 1.6 of the Setting up the IBM RTC SDK document and trying to test the Jetty based server launch. Unfortunately, at step _d, after clicking Run on the Create RTC Test Database step, console is reporting errors. 

Here are some of the errors from the log file:
org.osgi.framework.BundleException: The bundle "org.junit4_4.8.1.v20100525 [146]" could not be resolved. Reason: Missing Constraint: Require-Bundle: org.junit; bundle-version="4.8.1"
at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1317)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1301)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:319)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:374)
at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1067)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:561)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:546)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:459)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:440)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:227)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:337)

!ENTRY org.eclipse.osgi 4 0 2018-02-22 13:30:34.738
!MESSAGE Bundle initial@reference:file:plugins/org.eclipse.core.filesystem.linux.ppc64_1.4.0.R36x_v20130402-0505.jar/ was not resolved.

!ENTRY org.eclipse.osgi 4 0 2018-02-22 13:30:34.738
!MESSAGE Bundle com.ibm.team.osgi.patch_5.0.2000.v20150702_0054 [15] is not active.

!ENTRY org.eclipse.osgi 4 0 2018-02-22 13:30:34.738
!MESSAGE Bundle initial@reference:file:plugins/org.eclipse.core.resources.win32.x86_3.5.100.v20100505-1345.jar/ was not resolved.

!ENTRY org.eclipse.osgi 4 0 2018-02-22 13:30:34.738
!MESSAGE Bundle com.ibm.team.jfs.app.config.nl2a_1.1.1.v201505131349 [21] is not active.

!ENTRY org.eclipse.osgi 4 0 2018-02-22 13:30:34.738
!MESSAGE Bundle com.ibm.team.jfs.app.auth.nl1_1.0.4.v201505131347 [22] is not active.

!ENTRY org.eclipse.osgi 4 0 2018-02-22 13:30:34.738
!MESSAGE Bundle com.ibm.team.jfs.app.xml.nl2_1.1.1.v201109280231 [28] is not active.

!ENTRY org.eclipse.osgi 4 0 2018-02-22 13:30:34.738
!MESSAGE Bundle com.ibm.team.http.client.impl.nl2_1.1.1.v201109280231 [29] is not active.

!ENTRY org.eclipse.osgi 4 0 2018-02-22 13:30:34.738
!MESSAGE Bundle com.ibm.team.jfs.app.nl1_1.2.1.v201211071552 [33] is not active.

!ENTRY org.eclipse.osgi 4 0 2018-02-22 13:30:34.738
!MESSAGE Bundle com.ibm.team.jfs.app.servlet.nl2_1.2.2.v201307311200 [34] is not active.

!ENTRY org.eclipse.osgi 4 0 2018-02-22 13:30:34.738
!MESSAGE Bundle org.eclipse.jdt.compiler.apt_1.0.350.v20111011-0800_R362_J7 [35] is not active.
...
Please provide any pointers you may have. Thanks.

Regards,
NP

0 votes

1 answer
3,793 views
0 votes

Accepted answer

Permanent link
Ralph Schoon
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER (64.6k●3●36●49) Feb 26 '18, 2:33 a.m.

If you had mentioned the RTC version an answer might have been possible. There are issues with the 6.0.4 and 6.0.5 SDKs with PMRs open and being worked on. 6.0.3 works.

Namit Pande selected this answer as the correct answer

0 votes

Comments
Namit Pande
Feb 26 '18, 9:48 a.m.
Hi Ralph, I am on 6.0.1 with Tomcat. So I have some other issue seems like. I was under impression that the 6.0.4 and 6.0.5 issues were fixed.  I am upgrading the production site to 6.0.5 this weekend. Is there any workaround in 6.0.5? If not, then is there any rough estimate when the bug will be fixed? Thanks.

Ralph Schoon
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Feb 26 '18, 11:22 a.m.
6.0.1 should not be impacted, I blogged about that. Maybe retry the create test DB. 6.0.5: you don't need the SDK on a production server. There was a fix out but that did not fix everything. I can not tell how long it will take. I would suggest to use 6.0.3 for development at this time.

Namit Pande
Feb 26 '18, 11:33 a.m.
So what you are saying that I can just setup SDK in test and code it as to my need and still deploy in production without setting up the SDK? If that is so, I can start setting up 6.0.3 with liberty right away. Sorry, pardon my ignorance, I am very new to this. Thanks.

Ralph Schoon
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Feb 27 '18, 2:06 a.m.
Yes, the SDK is only needed for developing/debugging. Once you have packaged (read the new workshop Lab 6 fo some new tips) you can deploy on any server. I would also encourage to use a dedicated test system for deployment and initial testing on that system and not the production system. In the workshop the Tomcat system is both your SCM repository and your deployment test system. That is for simplicity and not because it is suggested to be done in real life.

1 vote

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.

Ask a question
Guidelines
FAQ
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
× 11,106

Question asked: Feb 22 '18, 2:02 p.m.

Question was seen: 3,793 times

Last updated: Feb 27 '18, 2:06 a.m.

Confirmation Cancel Confirm