![]() |
Telelogic SYNERGY (steve huntington) | ![]() |
Topic Title: Java client startup issues on HP-UX Topic Summary: Created On: 3-Apr-2006 18:34 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: I contacted the Telelogic support to get help on this issue, and they had a very tough time with it. Eventually, a fellow employee of mine figured out a way to get rid of the error. We are still not certain of the root cause of it. Since we had limited room (not enough for two installations), we linked the client installation for our second server to the first one. We figured we just needed to make separate esd.adr and .router.adr files, and then everything else would be fine. That was not the case for the Java client, although it was the case for the classic one. We figured it must stem from something internal to the cmsynergy script that gets CCM_HOME from its own path instead of the actual CCM_HOME environment variable. To test this, we removed the links in the second installation to cmsynergy and cmsynergy.lax, and created copies of them instead. After doing this, we successfully connected to the second server. Our installation is very unique here, but the conclusion is that if you have two servers with their own Synergy services (router, esd), limited room for the installation of the client, and you link the client installation, make sure cmsynergy and cmsynergy.lax are copies and make sure you changed your esd.adr and .router.adr files to have the correct information. | |
![]() |
|
Hello, |
|
![]() |
|
![]() |
|
That should work, both the Java client and the Classic client work just fine in a heterogeneous environment (all our servers run Solaris, and most Unix clients run on Linux or HP-UX). It seems that you have the 'engine_daemon=TRUE' set on either $CCM_HOME/etc/ccm.ini or at $HOME/.ccm.ini, and therefore you need to have the ESD process running on the host you set as the 'Engine Host' on the Java client startup dialog. Are you sure you are using the right engine host?
|
|
![]() |
|
![]() |
|
I wanted to avoid this extra twist because it is so complicated, but the rest of the issue is that we have three servers, each standalone servers of Synergy. The issue is that when we had just one server, everything worked fine, but now with trying to connect to a second and third one, there are issues. On the first server, the classic and Java client work fine. When I change my path and CCM_HOME environment variable to use the second one, the classic works, but the Java one does not.
To add even more confusing facts, if I use the first server as the host with the Java client while my path and CCM_HOME point at the second server, it connects to the first server. I'm guessing it has something to do with the second installation being wrong and pointing at the first server's ESD, but I really do not know. It doesn't seem to make sense that I am connecting to the first server while my path and CCM_HOME point to the second. I know this is rather complicated, that's why I was hoping to avoid this extra info.
|
|
![]() |
|
![]() |
|
It really sounds like you have it all mixed up :-) So, I assume you have three "full server installations", i.e. you are running three sets of router/objreg/lmgr daemons on three different hosts, and each host has also at least one Informix database instances, each with a set of databases.
Yes, that can be done and can be controlled. I actually have one production server which runs four installations at the same time on the same machine (Continuus/CM 5.1, Continuus/CM 5.1CS, and two Synergy/CM 6.3 installations). The trick here is that the *client* installation has to have the right $CCM_HOME/etc/.router.adr file. Also, if you run more than one router or ESD on the same host (each for different installation), you have to have a different port number for each. |
|
![]() |
|
![]() |
|
You are correct in saying I have three "full server installations." I wish that I could've had just one server with several instances of Synergy, but I am restricted by the rules here. For applications on servers, we have to have a complete standalone instance on three separate machines, one for development, one for testing, and one for production.
I have made three different client installations available in HP-UX for people to use, with the .router.adr changed for each one. I also changed the esd.adr file in each installation. Other than that, I left them completely the same. I'm amazed through all of that confusion that you understood my installation here, very impressive. Since the installations are on different machines, there is no restriction on the ESD ports needing to be different, is there? |
|
![]() |
|
![]() |
|
Jason, for me it sounds like you are just using a wrong machine name as the 'engine host' machine on the client startup dialog. The Java client caches the last engine host, and it's very easy to use a wrong value there.
If each router&esd is running on a different machine, then yes, you can use the same port numbers on each installation. |
|
![]() |
|
![]() |
|
I contacted the Telelogic support to get help on this issue, and they had a very tough time with it. Eventually, a fellow employee of mine figured out a way to get rid of the error. We are still not certain of the root cause of it. Since we had limited room (not enough for two installations), we linked the client installation for our second server to the first one. We figured we just needed to make separate esd.adr and .router.adr files, and then everything else would be fine. That was not the case for the Java client, although it was the case for the classic one. We figured it must stem from something internal to the cmsynergy script that gets CCM_HOME from its own path instead of the actual CCM_HOME environment variable. To test this, we removed the links in the second installation to cmsynergy and cmsynergy.lax, and created copies of them instead. After doing this, we successfully connected to the second server.
Our installation is very unique here, but the conclusion is that if you have two servers with their own Synergy services (router, esd), limited room for the installation of the client, and you link the client installation, make sure cmsynergy and cmsynergy.lax are copies and make sure you changed your esd.adr and .router.adr files to have the correct information.
|
|
![]() |
Telelogic SYNERGY
» SYNERGY/CM
»
Java client startup issues on HP-UX
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.