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

CRJAZ1118I error on attempting to launch JTS on Websphere.

JTS Version: 3.0
Websphere : 7.0.0.13
OS : Windows.

Deployed JTS on Websphere but on attempting to load the JTS page:
https://myserver:9443/jts/admin, I get the following error:

Error!
An internal system error occured while processing the request.
Error 500: java.lang.RuntimeException: CRJAZ1118I Unable to load server configuration.


Exception in System.out.log states:

00000018 servlet E com.ibm.ws.webcontainer.servlet.ServletWrapper service SRVE0068E: Uncaught exception created in one of the service methods of the servlet equinoxbridgeservlet in application jts_war. Exception created : java.lang.RuntimeException: CRJAZ1118I Unable to load server configuration.
at com.ibm.team.repository.common.transport.internal.configuration.OverridablePropertyFileServerConfiguration.failedToLoadServiceConfiguration(OverridablePropertyFileServerConfiguration.java:77)
at com.ibm.team.repository.common.transport.internal.configuration.OverridablePropertyFileServerConfiguration.getConfigFileInputStream(OverridablePropertyFileServerConfiguration.java:115)


The .log file contains entry stating:

!MESSAGE Error starting bundle: initial@reference:file:plugins/com.ibm.team.repository.web.jts_1.1.0.v20101110_2242.jar/
!STACK 0
org.osgi.framework.BundleException: A fragment bundle cannot be started: com.ibm.team.repository.web.jts_1.1.0.v20101110_2242


Any pointers to resolve the issue would be helpful.

0 votes



One answer

Permanent link
We've seen deployment problems in WAS when deploying a newer build when an older one was deployed. Even if you undeploy the older war files first, it appears that the WAS cache of the old deployed bits doesn't always get cleaned out properly. If you're deploying in WAS and had a previous build deployed, try undeploying, then clean up the WAS cache as described in

http://www-01.ibm.com/support/docview.wss?uid=swg21455119

Another thing that causes deployment problems is when running on Linux with a low open file limit. If running on Linux, follow the configuration steps in

http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0/topic/com.ibm.jazz.install.doc/topics/c_special_considerations_linux.html

Also, if running in WAS, there may be more information in the SystemErr.log file.

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: Jan 16 '11, 3:27 p.m.

Question was seen: 7,969 times

Last updated: Jan 16 '11, 3:27 p.m.

Confirmation Cancel Confirm