Team Server and Application setup - configure data warehouse
Team Server and Application setup - configure data warehouse for quality manager
We got following error message: An error occurred while creating data warehouse tables. Please try again.ID CRJAZ1745E hide details The database creation failed with an exception com.ibm.team.repository.common.TeamRepositoryException: CREATE BUFFERPOOL BPTEMP32K SIZE 4000 PAGESIZE 32768 at com.ibm.team.datawarehouse.service.AbstractDataWarehouseVendor.executeSql(AbstractDataWarehouseVendor.java:124) at com.ibm.team.datawarehouse.service.db2.internal.DB2DataWarehouseVendor.initializeDataWarehouse(DB2DataWarehouseVendor.java:24) 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.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:370) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:356) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56) at $Proxy1536.initializeDataWarehouse(Unknown Source) at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService$1.run(RemoteDatabaseService.java:84) at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService$3.run(RemoteDatabaseService.java:127) at com.ibm.team.repository.service.internal.rdb.ConnectionPoolService.withCurrentConnection(ConnectionPoolService.java:332) at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService.write(RemoteDatabaseService.java:117) at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService.createRemoteSchemas(RemoteDatabaseService.java:76) 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.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:370) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:356) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56) at $Proxy791.createRemoteSchemas(Unknown Source) at com.ibm.team.datawarehouse.service.internal.InternalDataWarehouseService$7.run(InternalDataWarehouseService.java:1026) Caused by: com.ibm.db2.jcc.am.io: DB2 SQL Error: SQLCODE=-601, SQLSTATE=42710, SQLERRMC=BPTEMP32K;BUFFERPOOL, DRIVER=3.57.82 at com.ibm.db2.jcc.am.bd.a(bd.java:676) at com.ibm.db2.jcc.am.bd.a(bd.java:60) at com.ibm.db2.jcc.am.bd.a(bd.java:127) at com.ibm.db2.jcc.am.km.c(km.java:2506) at com.ibm.db2.jcc.am.km.d(km.java:2483) at com.ibm.db2.jcc.am.km.b(km.java:1903) at com.ibm.db2.jcc.t4.db.h(db.java:220) at com.ibm.db2.jcc.t4.db.b(db.java:46) at com.ibm.db2.jcc.t4.t.b(t.java:38) at com.ibm.db2.jcc.t4.sb.g(sb.java:114) at com.ibm.db2.jcc.am.km.db(km.java:1898) at com.ibm.db2.jcc.am.km.a(km.java:2899) at com.ibm.db2.jcc.am.km.e(km.java:985) at com.ibm.db2.jcc.am.km.execute(km.java:969) at com.ibm.team.repository.service.internal.db.jdbcwrappers.stat.StatementStatWrapper.execute(StatementStatWrapper.java:178) at com.ibm.team.repository.service.internal.db.jdbcwrappers.errlog.StatementErrLogWrapper.execute(StatementErrLogWrapper.java:169) at com.ibm.team.repository.service.internal.db.jdbcwrappers.leak.StatementLeakWrapper.execute(StatementLeakWrapper.java:70) at com.ibm.team.datawarehouse.service.AbstractDataWarehouseVendor.executeSql(AbstractDataWarehouseVendor.java:122) ... 23 more Any Idea? Thanks S. Link |
7 answers
Caused by: com.ibm.db2.jcc.am.io: DB2 SQL Error: SQLCODE=-601, SQLSTATE=42710, SQLERRMC=BPTEMP32K;BUFFERPOOL, DRIVER=3.57.82 at com.ibm.db2.jcc.am.bd.a(bd.java:676) S. the 601 error in DB means: The name of the object to be created is identical to the existing name name of type type Which means the bufferpool named BPTEMP32K is already created in the database. What command are you running ? a repotools create tables ? I am wondering if we need to drop the bufferpool to let the script crate it or if the script should not attempt to create a bufferpool. I would expect repotools -cerateTables to create a bufferpool, not another command. |
On 10/6/2010 12:08 PM, celek wrote:
slinkwrote: We've seen this in the past, and in most cases it was caused by either a previous failure or the tablespace directory not being fresh/empty. Can you try again, after: 1. Dropping the RIDW database 2. Deleting the tablespace folder 3. Re-creating the tablespace folder 4. Re-creating the database On a related note, we're working on simplifying the data warehouse setup, to make it more like the repository database setup - that is, not try to manage table spaces and related artifacts automatically. james CLM Reporting Team Lead |
Hi James,
we did the following: - dropped the DB datawarehouse - run create DB command for datawarehouse - do not run the reprotools - try to configure over the webpage https://servername:9443/jts/setup We got the followings problems in step Jazz Team Server -> Register Application: An error occurred while attempting to register the applications.ID CRJAZ1726E hide details Error invoking registration handler for application "CCM" at https://lnxsccmt.boeblingen.de.ibm.com:9443/ccm/service/com.ibm.team.repository.service.internal.setup.IRegistrationHandlerServiceID CRJAZ1720E com.ibm.team.repository.common.TeamRepositoryException com.ibm.team.repository.service.internal.discovery.FriendsAdminRestService.postRegisterApp(FriendsAdminRestService.java:590) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:618) org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:370) org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:356) org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56) $Proxy208.postRegisterApp(Unknown Source) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:618) com.ibm.team.repository.servlet.AbstractTeamServerServlet.doModelledRestService(AbstractTeamServerServlet.java:500) com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest2(AbstractTeamServerServlet.java:1817) com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest(AbstractTeamServerServlet.java:1673) com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(AbstractTeamServerServlet.java:1584) javax.servlet.http.HttpServlet.service(HttpServlet.java:729) org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180) org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90) org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111) org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:75) javax.servlet.http.HttpServlet.service(HttpServlet.java:729) org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:120) com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:62) javax.servlet.http.HttpServlet.service(HttpServlet.java:729) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172) org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525) org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:420) org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:873) org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689) java.lang.Thread.run(Thread.java:811) Caused by: Registration handler for application "CCM" at https://lnxsccmt.boeblingen.de.ibm.com:9443/ccm/service/com.ibm.team.repository.service.internal.setup.IRegistrationHandlerService failed with status 409 and response body " HTTP Status 409 - A pending friend entry file already exists at /opt/IBM/JazzTeamServer/server/tomcat/work/Catalina/localhost/ccm/eclipse/configuration/org.eclipse.osgi/bundles/98/data/pending-jts-friend.rdf. The previous registration attempt must be finalized first. type Status report message A pending friend entry file already exists at /opt/IBM/JazzTeamServer/server/tomcat/work/Catalina/localhost/ccm/eclipse/configuration/org.eclipse.osgi/bundles/98/data/pending-jts-friend.rdf. The previous registration attempt must be finalized first. description The request could not be completed due to a conflict with the current state of the resource (A pending friend entry file already exists at /opt/IBM/JazzTeamServer/server/tomcat/work/Catalina/localhost/ccm/eclipse/configuration/org.eclipse.osgi/bundles/98/data/pending-jts-friend.rdf. The previous registration attempt must be finalized first.). Apache Tomcat/5.5.28 " (com.ibm.team.repository.common.TeamRepositoryException)ID CRJAZ1721E com.ibm.team.repository.service.internal.discovery.FriendsAdminRestService.notifyAppRegistrationHandler(FriendsAdminRestService.java:695) com.ibm.team.repository.service.internal.discovery.FriendsAdminRestService.postRegisterApp(FriendsAdminRestService.java:577) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) ... 39 more. Another problem Quality Management -> Configure Datawarehouse: The database exists, but is not configured to contain the data warehouse. Use the "Create Tables" button in Step 3 to configure the data warehouse for Jazz.ID CRJAZ1744E Can you help us with this problems? Thanks Siegbert Link |
On 10/8/2010 8:23 AM, slink wrote:
Hi James, The first few problems you report aren't related to the data warehouse - someone from the setup or repository team could provide more comment on that, but it looks harmless - I think it's just saying that the friend is already registered due to your previous setup attempt. Regarding the last comment you mention, we had a bug in beta2 where the settings that appear in the configuration of the fronting applications (e.g. qm, ccm, rm) for the data warehouse were incorrect. Assuming that the JTS setup was successful and the data warehouse got created at that time, when you get to the QM page, please re-enter the jdbc location information. That is, even if it looks correct, please make a change in the text widget to modify it. Then Test Connection again. Also, are you using DB2 or Derby for the warehouse? From the messages I assume DB2. james CLM Reporting Team Lead |
Hi James,
thanks for your answer, we tried your suggestions without success. That is what we did: At the first time we try to configure the application over the jts/setup. At the step 7 we got the following error. https://servername:9443/jts/setup#/steps/7 An error occurred while attempting to register the applications.ID CRJAZ1726E Caused by: Registration handler for application "CCM" at https://servername:9443/ccm/service/com.ibm.team.repository.service.internal.setup.IRegistrationHandlerService failed with status 409 and response body " HTTP Status 409 - A pending friend entry file already exists at /opt/IBM/JazzTeamServer/server/tomcat/work/Catalina/localhost/ccm/eclipse/configuration/org.eclipse.osgi/bundles/98/data/pending-jts-friend.rdf. The previous registration attempt must be finalized first. After that I wrote here https://servername:9443/ccm/admin#action=com.ibm.team.repository.admin.configureAdvanced under com.ibm.team.repository.service.internal.ServerDescriptionService Jazz Team Server Location: https://servername:9443/jts Public URI Root: https://servername:9443/ccm Next Step: https://servername:9443/ccm/admin#action=com.ibm.team.repository.admin.friends Create a friend for Jazz Team Server with the url https://servername:9443/jts/rootservices. Next Step, go to: https://servername:9443/jts/admin#action=com.ibm.team.repository.admin.registeredApplications Try to Register Application with the following Properties: Property Value Application Name: CCM Discovery URL: https://servername:9443/ccm/scr Auth Secret Re-type Secret Pre-Authorized User username Clear User... First Error: Caused by: Registration handler for application "CCM" at https://servername:9443/ccm/service/com.ibm.team.repository.service.internal.setup.IRegistrationHandlerService failed with status 409 and response body " HTTP Status 409 - A pending friend entry file already exists at /opt/IBM/JazzTeamServer/server/tomcat/work/Catalina/localhost/ccm/eclipse/configuration/org.eclipse.osgi/bundles/98/data/pending-jts-friend.rdf. The previous registration attempt must be finalized first. type Status report message A pending friend entry file already exists at /opt/IBM/JazzTeamServer/server/tomcat/work/Catalina/localhost/ccm/eclipse/configuration/org.eclipse.osgi/bundles/98/data/pending-jts-friend.rdf. The previous registration attempt must be finalized first. After that we renamed the file /opt/IBM/JazzTeamServer/server/tomcat/work/Catalina/localhost/ccm/eclipse/configuration/org.eclipse.osgi/bundles/98/data/pending-jts-friend.rdf and try again. When we got the following error: An error occurred while attempting to add the new application to the server.ID CRJAZ1664E Caused by: Registration handler for application "CCM" at https://servername:9443/ccm/service/com.ibm.team.repository.service.internal.setup.IRegistrationHandlerService failed with status 403 and response body " HTTP Status 403 - The application has already been registered, and so cannot be registered again. Any configuration changes must be done manually. type Status report message The application has already been registered, and so cannot be registered again. Any configuration changes must be done manually. description Access to the specified resource (The application has already been registered, and so cannot be registered again. Any configuration changes must be done manually.) has been forbidden. Apache Tomcat/5.5.28 " (com.ibm.team.repository.common.TeamRepositoryException)ID CRJAZ1721E com.ibm.team.repository.service.internal.discovery.FriendsAdminRestService.notifyAppRegistrationHandler(FriendsAdminRestService.java:695) com.ibm.team.repository.service.internal.discovery.FriendsAdminRestService.postRegisterApp(FriendsAdminRestService.java:577) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) ... 39 more We still reboot the server and try a refresh on the registered applications. Because of the unfinished CCM application registration, we got the following error when we tryp to import user here https://servername:9443/ccm/admin#action=jazz.viewPage&id=com.ibm.team.repository.users CRJAZ1832E The user configured to perform the request "https://lnxsccmt.boeblingen.de.ibm.com:9443/jts/service/com.ibm.team.repository.service.internal.IExternalUserRegistryRestService/usersByAnyName2?name=*" on the JTS is not authorized. There may not be a functional user configured for the oauth consumer , or the funtional user that is configured does not have sufficient privileges to perform the requested operation. Connection Error: Unauthorized If we try to create the user local we got the following error: The user configured to perform the request "https://servername:9443/jts/service/com.ibm.team.repository.service.internal.IExternalUserRegistryRestService/isExternalRegistryWriteable" on the JTS is not authorized. There may not be a functional user configured for the oauth consumer , or the funtional user that is configured does not have sufficient privileges to perform the requested operation. Connection Error: UnauthorizedID CRJAZ1832E hide details com.ibm.team.repository.common.TeamRepositoryException com.ibm.team.repository.service.compatibility.util.http.CrossServerHttpClient.createExceptionFromResponse(CrossServerHttpClient.java:430) com.ibm.team.repository.service.compatibility.util.http.CrossServerHttpClient.checkResponse(CrossServerHttpClient.java:375) com.ibm.team.repository.service.compatibility.util.http.CrossServerHttpClient.send(CrossServerHttpClient.java:352) com.ibm.team.repository.service.compatibility.util.http.CrossServerHttpClient.send(CrossServerHttpClient.java:270) com.ibm.team.repository.service.compatibility.util.http.CrossServerHttpClient.send(CrossServerHttpClient.java:364) com.ibm.team.repository.service.compatibility.util.http.CrossServerHttpClient.send(CrossServerHttpClient.java:239) com.ibm.team.repository.service.compatibility.AbstractCompatibilityService.send(AbstractCompatibilityService.java:45) com.ibm.team.repository.service.compatibility.user.registry.CompatibilityExternalUserRegistryService.isExternalRegistryWriteable(CompatibilityExternalUserRegistryService.java:217) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:618) org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:370) org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:356) org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56) $Proxy725.isExternalRegistryWriteable(Unknown Source) com.ibm.team.repository.service.jts.internal.userregistry.ExternalUserRegistryServiceDelegator.isExternalRegistryWriteable(ExternalUserRegistryServiceDelegator.java:181) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:618) org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:370) org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:356) org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56) $Proxy1370.isExternalRegistryWriteable(Unknown Source) com.ibm.team.repository.service.internal.AdminRestService.getUserRegistryInfo(AdminRestService.java:537) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:618) org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:370) org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:356) org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56) $Proxy1379.getUserRegistryInfo(Unknown Source) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:618) com.ibm.team.repository.servlet.AbstractTeamServerServlet.doModelledRestService(AbstractTeamServerServlet.java:500) com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest2(AbstractTeamServerServlet.java:1817) com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest(AbstractTeamServerServlet.java:1673) com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(AbstractTeamServerServlet.java:1584) javax.servlet.http.HttpServlet.service(HttpServlet.java:729) org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180) org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90) org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111) org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:75) javax.servlet.http.HttpServlet.service(HttpServlet.java:729) org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:120) com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:62) javax.servlet.http.HttpServlet.service(HttpServlet.java:729) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172) org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525) org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:420) org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:873) org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689) java.lang.Thread.run(Thread.java:811) Do you have another hint what we can do manually that the ccm application can be registered? Best regards Sandra Hoffmann and Siegbert Link |
Are you still trying to get the CCM application set up? It sounds like it was mostly there; the message
A pending friend entry file already exists at /opt/IBM/JazzTeamServer/server/tomcat/work/Catalina/localhost/ccm/eclipse/configuration/org.eclipse.osgi/bundles/98/data/pending-jts-friend.rdf. The previous registration attempt must be finalized first. meant that the application was registered, but you need to complete setup by going through the application's setup wizard steps. If you want to try and completely undo the CCM registration and redo, try these steps: 1. In the JTS admin UI, go to the "Registered Applications" page and remove the application (click on the X at the right of the application entry). For CCM and QM, an error message will appear at the top saying something like "An error occurred while deleting the friend entry: b46a5e4af7f04cef81aaa1cd45799f98"; that can be ignored. 2. In the JTS admin UI, go to the "Consumers (Inbound)" page and delete the authorized key for the application (if there is one). 3. In the application's admin UI, go to the "Friends (Outbound)" page and remove the entry for the Jazz Team Server (if there is one). 4. In the applications admin UI, go to the "Consumers (Inbound)" page and remove the authorized key for the Jazz Team Server (if there is one). 5. Log out of the admin UIs and shut down the server that the application is running in. 6. Edit the teamserver.properties file for the application (e.g. server/conf/ccm/teamserver.properties) and if there is a line containing the property name "com.ibm.team.repository.server.jts.url", delete it. 7. Search for any files named "pending-jts-friend.rdf", and delete them. For Tomcat, they will be somewhere under the server/tomcat/work/Catalina/localhost folder. For WAS, they will be under the WebSphere/AppServer/profiles/<profileName> folder. 8. Restart the application's server. 9. Register the application. If the application is running in the same server as the JTS, you can just run the JTS setup wizard again; it should detect that the application is available for registration. If the application is running in a separate server, then it can be registered in the "Registered Applications" page of the JTS admin UI. Then, the application's setup wizard must be run to finalize the setup. |
Thanks John, this helped me fixing the connection between the servers after a 2.0 -> 3.0.1 migration using the repotools export/import. 8)
|
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.