Unable to start JTS after CLM6.0.1 installation
Hi, I have been fighting this install and wanted to see if anyone could help.
My Problem is that JTS is unable to start after CLM6.0.1 installation.
<SERVER>
- Windows Server 2008 R2 Standard
- 64 bit
** But I used DOORS Next Generation of CLM6.0.1 before CLM6.0.2 was installed.
1. Installed IBM CLM6.0.2 using intallation manager and start the Jazz Team Server
2. During User Settings using setup wizard, error occured at application registeration step
3. Deleted the CLM6.0.2 using Installation Manager and Jazz Team Server folder
4. Installed IBM CLM6.0.1 using Installation Manager and start the JTS.
This is the Jazz Team Server console message : http://i66.tinypic.com/11sjlht.png
Please refer to translation.
* 오후 -> afternoon
* clm서버가 작성되었습니다. -> clm server was drawn up.
* 4553개 파일이 복사되었습니다. -> 4553 files was copied.
* clm 서버가 시작하는 중입니다. -> clm server is starting.
And error was occured that is same with 2th step.
error ID : CRJAZ1726E -> Cannot register the application at Jazz Team Server.
This is Error message : http://i67.tinypic.com/347jtaq.jpg
5. Deleted the CLM6.0.1 and Installed the CLM6.0.1 using Installation Manager
6. During User setup, Another Problem was occured at detect URL step.
error ID : CRJAZ1579E -> The configuration test resulted in errors. Resolve the errors to continue.
7. After I reboot the computer and reinstalled the CLM6.0.1, Another Problem was occured.
Jazz Team Server is unable to start.
--------------------------This is the jazz team server's console message---------------------------------------
4월 28, 2016 1:45:48 afternoon com.ibm.java.diagnostics.healthcenter.agent.mbean.HCLaunchMBean <init>
INFO: Agent version "3.0.4.20150622"
4월 28, 2016 1:45:48 afternoon com.ibm.java.diagnostics.healthcenter.agent.mbean.HCLaunchMBean createJMXConnector
INFO: IIOP will be listening on the next available system assigned port. Use com.ibm.java.diagnostics.healthcenter.agent
.iiop.port to specify a port
4월 28, 2016 1:45:48 afternoon com.ibm.java.diagnostics.healthcenter.agent.mbean.HCLaunchMBean createJMXConnector
SEVERE: Health Center agent failed to start.
java.io.IOException: Cannot bind to URL [rmi://scmserver:1972/jmxrmi]: javax.naming.NoPermissionException [Root exceptio
n is java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.AccessException: Registry.Registry.bind disallowed; origin /192.168.10.192 is non-local host]
at javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:838)
at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:443)
at com.ibm.java.diagnostics.healthcenter.agent.mbean.HCLaunchMBean.createJMXConnector(HCLaunchMBean.java:687)
at com.ibm.java.diagnostics.healthcenter.agent.mbean.HCLaunchMBean.startMBeanServer(HCLaunchMBean.java:471)
at com.ibm.java.diagnostics.healthcenter.agent.mbean.HCLaunchMBean$JmxStarterThread.run(HCLaunchMBean.java:267)
Caused by: javax.naming.NoPermissionException [Root exception is java.rmi.ServerException: RemoteException occurred in s
erver thread; nested exception is:
java.rmi.AccessException: Registry.Registry.bind disallowed; origin /192.168.10.192 is non-local host]
at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:156)
at com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:239)
at javax.naming.InitialContext.bind(InitialContext.java:431)
at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:655)
at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:438)
... 3 more
Caused by: java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.AccessException: Registry.Registry.bind disallowed; origin /192.168.10.192 is non-local host
at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:437)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:285)
at sun.rmi.transport.Transport$2.run(Transport.java:215)
at sun.rmi.transport.Transport$2.run(Transport.java:212)
at java.security.AccessController.doPrivileged(AccessController.java:452)
at sun.rmi.transport.Transport.serviceCall(Transport.java:211)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:580)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:841)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.access$400(TCPTransport.java:632)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler$1.run(TCPTransport.java:697)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler$1.run(TCPTransport.java:694)
at java.security.AccessController.doPrivileged(AccessController.java:386)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:694)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1157)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:627)
at java.lang.Thread.run(Thread.java:809)
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:288)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:265)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:391)
at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:150)
... 7 more
Caused by: java.rmi.AccessException: Registry.Registry.bind disallowed; origin /192.168.10.192 is non-local host
at sun.rmi.registry.RegistryImpl.checkAccess(RegistryImpl.java:270)
at sun.rmi.registry.RegistryImpl.bind(RegistryImpl.java:162)
at sun.rmi.registry.RegistryImpl_Skel.dispatch(Unknown Source)
at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:427)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:285)
at sun.rmi.transport.Transport$2.run(Transport.java:215)
at sun.rmi.transport.Transport$2.run(Transport.java:212)
at java.security.AccessController.doPrivileged(AccessController.java:452)
at sun.rmi.transport.Transport.serviceCall(Transport.java:211)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:580)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:841)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.access$400(TCPTransport.java:632)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler$1.run(TCPTransport.java:697)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler$1.run(TCPTransport.java:694)
at java.security.AccessController.doPrivileged(AccessController.java:386)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:694)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1157)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:627)
at java.lang.Thread.run(Thread.java:809)
4월 28, 2016 1:45:48 afternoon com.ibm.java.diagnostics.healthcenter.agent.mbean.HCLaunchMBean startAgent
INFO: Health Center agent did not start correctly.
clm server is starting. Failed on starting clm server. Identify the detail log.
2 answers
Ideally you choose a separate installation folder for each of them and on windows you avoid to install into Program Files. Take a path such as C:\CLM\6.0.1\ as root for an install.
If you install into the same folder, completely delete the install folder after uninstall to get rid of backup data.
I would suggest to approach support. They can ask for other logs and more information. I can't see anything in the logs and the description is a bit confusing and lacks some information. E.g. it would have been interesting what the "CRJAZ1579E -> The configuration test resulted in errors." Just rebooting will usually not solve a problem like the ones there.
Comments
Thanks for your fast answer!!
I already tried to install the CLM6.0.1 into another folder. For example - Desktop\JazzTeamServer
But same problem was occured. (CRJAZ1579E -> The configuration test resulted in errors. Resolve the errors to continue.)
So, After rebooting the computer, I installed CLM6.0.1 into Desktop's folder of User's account not Administrator account. Then, JTS unable to start.( 7.After I reboot the computer and reinstalled the CLM6.0.1, Another Problem was occured. Jazz Team Server is unable to start. )
Lastly, I installed CLM6.0.1 into Desktop's folder of Administrator account.
But JTS(server.startup.bat) still unable to start and I wrote the error message (--------------------------This is the jazz team server's console message---------------------------------------)
There are no jts's log file in <Jazz Team Server Directory>\server\logs .
I want to know jts's log file location. Please let me know.
Thank you^^.
Ideally you choose a separate installation folder for each of them and on windows you avoid to install into Program Files. Take a path such as C:\CLM\6.0.1\ as root for an install.
Don't install into a desktop folder and not into program files since you might have to run the startup as admin if you do so - even if logged in as admin.
In general, your information does not seem to contain anything to work with.
Some remarks.
1st: with 6.0.1 the memory consumption is higher (I have 32 GB in my laptop and it works).
Startup times are a lot longer for me and performance is lower especially if DCC is installed.
Hi, thanks for your help!
I reinstalled CLM6.0.1 in the C:\CLM\6.0.1.
So, JTS is working now. Thank you.
But, During User Settings using setup wizard, another error was occured at application registeration step.
- error ID : CRJAZ2287E
-> an error occurred while communicating with the server at "https://server:9443/lqe/scr". Varify that the server is available and that there are no firewalls or other artifacts between these two endpoints that could present a confirmation dialog
If the CLM startup process is failing to start the HealthCenter because of the RMI bind error: