It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×7,479
×4,320
×2,352
×489

question asked: Jul 16 '15, 2:58 a.m.
question was seen: 5,381 times
last updated: Sep 29 '15, 1:51 a.m.

Related questions

CLM 6.0 LQE and LDX failing to start on Websphere 8.5.5.6

0
Peter Morgenthaler (102●8●15) | asked Jul 16 '15, 2:58 a.m.

I have just upgraded a basic CLM install from 5.0.2 to 6.0.0 which has gone as expected. Have then added RS/LQE/LDX/RELM/DCC and tried to run jts/setup.

The first time running all apps were registered and RS/RELM/DCC all setup fine. LQE and LDX were also detected and allowed me to setup an Oracle DB for them to use however the LDX had a failure - unspecified.

So I unistalled the components, cleared the websphere cache, reinstalled LQE and LDX however now they will not start at all to even get to setup just showing an Internal Server error.

The errors in the log are in the Websphere SystemOut.log

[16/07/15 15:49:05:421 ACST] 00000127 webapp        E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: [Servlet Error]-[com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor]: java.lang.NoClassDefFoundError: org.apache.http.impl.conn.ManagedHttpClientConnectionFactory (initialization failure)
 at java.lang.J9VMInternals.initialize(J9VMInternals.java:175)
 at org.apache.http.impl.conn.PoolingHttpClientConnectionManager$InternalConnectionFactory.<init>(PoolingHttpClientConnectionManager.java:493)
 at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.<init>(PoolingHttpClientConnectionManager.java:149)
 at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.<init>(PoolingHttpClientConnectionManager.java:138)
 at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.<init>(PoolingHttpClientConnectionManager.java:114)
 at com.ibm.team.integration.core.common.http.HttpClientFactory.createHttpClient(HttpClientFactory.java:260)
 at com.ibm.team.integration.core.common.http.HttpClientFactory.build(HttpClientFactory.java:168)

Any suggestions as to what the issue is?

Do I need the LQE as part of RS?

I assume the LDX is part of RELM? - Which is not a component we need to use.

Accepted answer

1
permanent link
Ryan Park (46●1●3) | answered Jul 20 '15, 10:26 p.m.
Hi Peter,

Please add JRS Shared Library for all lqe, ldx and rs as well, which step has been missed in interactive guide on information center.

Regards,
Ryan
Peter Morgenthaler selected this answer as the correct answer

2 other answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Don Yang (7.7k●21●114●139) | answered Jul 16 '15, 8:55 p.m.
edited Jul 16 '15, 8:56 p.m.
Hi, Peter

If you want to re-register LQE/LDX application when RELM is involved, you need to:

  1. Locate the lqe.properties file. By default, the lqe.properties file is in the /server/conf/lqe folder. The location is also the value for this JVM system property: -Dlqe.config.location , which is in the same folder.
  2. In the lqe.properties file, set this LQE property: configMode=true .

(the same should apply to LDX)

Restart WAS with LQE/LDX and try to run jts/setup again

I am not sure if you need RELM or not from your description. Lifecycle Query Engine is supported as a data source for use with Rational Engineering Lifecycle Manager, but is an unsupported technical preview feature for any other CLM 6.0 application. LQE as a data source for reporting on configurations is also in technical preview, even with Rational Engineering Lifecycle Manager. See the details in

https://jazz.net/help-dev/clm/index.jsp?re=1&topic=/com.ibm.team.jp.lqe2.doc/topics/c_lqe_ov.html&scope=null

So if you dont use RELM and reporting on the new configuration data source is not required, you dont need to have LQE.
LDX is a small instance of LQE and it is actually used by CLM backlink query. So if you have LPA in 6.0 CLM, you would want to have LDX in order for you  to still see the backlink in QM and RM.

Hopefully these help.

0
permanent link
Keith Wells (1) | answered Sep 10 '15, 7:46 a.m.
JAZZ DEVELOPER
LQE and LDX do not require any shared library setup/configuration. The NoClassDefFoundError reported by Peter is a result of not setting the Websphere Classloader order for the module and the war files to be PARENT_LAST.

http://www-01.ibm.com/support/knowledgecenter/SSYMRC_6.0.0/com.ibm.jazz.install.doc/topics/t_deploy_was.html?lang=en-us
The steps for LQE and LDX from this document:

Configure the Lifecycle Query Engine (LQE) application

Procedure

  1. In WebSphere Integrated Solutions Console click Applications > Application Types > WebSphere enterprise applications.
  2. Click lqe_war to open it and then click Manage Modules.
  3. Click lqe, locate the Class loader order field and select Classes loaded with local class loader first (parent last).
  4. Click OK and save your changes.
  5. Go back to the lqe_war application and click Class loading and update detection.
  6. On the Class loader page, select Classes loaded with local class loader first (parent last).
  7. Click Apply and Save directly to the master configuration.
After setting the class loader for LQE and LDX, the server should be restarted.


Comments
Peter Morgenthaler commented Sep 13 '15, 8:24 p.m.

I have two environments that if I DONT add the shared library then it wont start. I can confirm that I have set the class loader feature as per the instructions above and the LQE and LDX do not function. If I set the shared library they function as expected.

Donald Nong commented Sep 14 '15, 2:27 a.m. | edited Sep 14 '15, 2:28 a.m.

@wellsk Keith, not just Peter had this problem after following the instructions in the Knowledge Center. I am curious why JRS/LQE/LDX cannot see the libraries bundled in the .war file. Just think about it, same as LQE and LDX, JRS bundles the same set of common Apache libraries, and yet it is required to configure the shared library for JRS to use the same libraries located in WAS_SharedLibrary. Why?

Keith Wells commented Sep 15 '15, 9:30 a.m.
JAZZ DEVELOPER

There might be something in your configuration which results in the need for the shared library. The LQE team has not encountered this before now.  We would like to understand your setup / environment better.

Are you using the default embedded Derby database, or did you configure LQE for a relational DB, and if so,which RDBMS?
Did you set the server wide System environment var "-Dlqe.config.location" for LQE and "-Dldx.config.location" for LDX? Donald, if the Classloader is set to PARENT_LAST, the WAS classloader will use the LQE libs including the Apache libs.

Peter Morgenthaler commented Sep 15 '15, 7:53 p.m.

Hi, Below is our environment.

RHEL x64 - 6.5 (latest updates)

Websphere 8.5.5.6 - Java 7

CLM 6.0.0 ifix02

DBMS Oracle 11G

Under Websphere ->
Application servers > JazzTest01 > Process definition > Java Virtual Machine > Custom properties
Variables defined as follows
DISPLAY = lcoalhost:1.0
ORACLE_JDBC_DRIVER_FILE = file:////opt/IBM/JTS/server/conf/
ldx.config.location = file:///opt/IBM/JTS/server/conf/ldx/lqe.properties
lqe.config.location = file:///opt/IBM/JTS/server/conf/ldx/lqe.properties
java.awt.headless = true
startup_log4j.configuration = file:///opt/IBM/JTS/server/conf/startup_log4j.properties

Peter Morgenthaler commented Sep 15 '15, 7:55 p.m.

Refer to PMR 50447,220,616 for details from support.

Peter Morgenthaler commented Sep 29 '15, 1:51 a.m.

@wellsk On my test environment I have removed the shared libs, confirmed that the class loading is Parent last and restarted Websphere and confirm tha the LQE does not start. Same behaviour for the LDX.

showing 5 of 6 show 1 more comments

Your answer

Register or 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.