CLM 4.0.1: "There is a bug in the Jazz server" (CRJAZ1579E)?
I tried to configure the CLM 4.0.1 with jts/setup. The cluster has only one member running and the others were stopped. WAS 8.0.3 and DB2 9.7 are in the backend. IBM HTTPS serves a reverse proxy server here.
When the setup ran into the step 2, the following error showed up. It says "There is a bug in the Jazz server". What bug? How do I workaround it?
The configuration test resulted in errors. Resolve the errors to continue.
For more details, open the help system and search for CRJAZ1579E. ID CRJAZ1579E
The method getPrerequisiteServices() was called on the AbstractActivationManagerOwner for com.ibm.team.repository.service.internal.BaseServerDescriptionService when the service not activated. The method should only be called when the service is activated. If you see this error please report the problem to the Jazz Application Frameworks team, because there is a bug in the Jazz server.
com.ibm.team.repository.common.transport.internal.registry.ServiceNotActivatedException
com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.getPrerequisiteServices(AbstractActivationManagerOwner.java:922)
com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.withServiceDependencies(AbstractActivationManagerOwner.java:1258)
com.ibm.team.repository.common.transport.internal.registry.OsgiServicesManager.withServiceDependencies(OsgiServicesManager.java:661)
com.ibm.team.repository.common.transport.internal.registry.ServiceConfiguration.validateProperties(ServiceConfiguration.java:419)
com.ibm.team.repository.service.internal.ServerConfigurationRestService$2.processUpdate(ServerConfigurationRestService.java:356)
com.ibm.team.repository.service.internal.ServerConfigurationRestService.processConfigUpdates(ServerConfigurationRestService.java:249)
com.ibm.team.repository.service.internal.ServerConfigurationRestService.postConfigurationValidation(ServerConfigurationRestService.java:353)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
java.lang.reflect.Method.invoke(Method.java:611)
org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
$Proxy883.postConfigurationValidation(Unknown Source)
3 answers
I found a forum post with a suggested answer: https://jazz.net/forum/questions/81025/why-am-i-getting-a-crjaz1579e-error-on-step-2-of-installing-rrc.
I am using a 10 Gb VM running Windows 2008 datacentre.
The setup is derby/tomcat and I have done no configuration at this stage.
Tomcat is not running as a service or being run by an administrator.
If I run JTS 'as an Administrator' the error does not occur.
If I run JTS in the standard way, I can not access the express setup because an error appears stating that the database has been misconfigured.
If I bookmark express setup and go straight to that page the error appears.
When I then start Tomcat 'not as an administrator' I get errors stating I cannot rename tomcat-users.xml.old. This error reappears if I do not shut down 'as an administrator".
Comments
Hi Bo,
Thanks.
No database is involved yet. That is the step 2 of jts/setup which gave the error. Did not see useful information in jts.log about the errors, at least, not to me.
@frankxning: When the JTS server starts up, it attempts to connect to the database that is configured in its teamserver.properties file. This is typically set to the packaged Derby by default at conf/jts/derby/repositoryDB. However, since your server is clustered, it is likely that the instructions to cluster included changing your teamserver.properties file to point to a non-Derby database (since Derby is not supported in a cluster). If your server cannot connect to whatever database is in your teamserver.properties when it starts up, then this error will appear.
So just to be clear, there are no errors in your jts.log that contain any more information than what you provided? Feel free to paste the errors here if you'd like me to assess them.
Hi Bo,
It did not even go to those steps to select DB vendor and do DB2 setting yet. This is the step 2 for public URI which gave me the error. That does not make sense and did not happen to 4.0.0.0 and 4.0.0.1. This is new in 4.0.1.0.
@frankxning: If you did not already configure your DB2 settings before you attempted to run jts/setup, then that is likely your problem.
See step 7 of the Info Center topic "Creating an application server and deploying applications":
7. After the installation is complete, open each application's teamserver.properties file to comment out the default Derby connection and enable the connection to your enterprise database. This step must be performed or you will not be able connect to the server to run the setup wizard. Derby database is not supported in a clustered environment.
Well, my intent was not to set up cluster at first place. There has been no manual steps to update the teamserver.properties file for database servers for jts/setup. I will remove WXS from the install to see how that goes.
Instead of removing WXS from the install, you can also follow the instructions to disable clustering for your CLM. See step 3 of the CLM Info Center topic Enabling and Disabling clusters.