Running JBE on a remote machine - any issues?
I have my jazz server running in secure mode behind a firewall. The associated build engine (jbe) is being run on the open network outside of the firewall. When I kick a build off, there is no action anywhere - in the build queue or the console of jbe. In the case where I have my jbe local, it all works fine.
Are there any issues other than the obvious of ports? Also about ports - which ones do I need to open up as outgoing from the internal network to the external? The jbe is logging into the repository with https://<ipaddress>:9443/jazz. Team Concert from the same machine is able to connect to the project area on the server - so it's not a client-->server connectivity issue. Any help is appreciated. |
3 answers
The jazz build engine (jbe) is simply a client of the repository, so you
should not need any ports opened for its operation. If your Team Concert client is able to connect from the same machine, then jbe should be able to, using the same repository address, user, and password. From your description, you're requesting a build, and its sitting forever in the Pending state. If so, be sure that the -engineId parameter when you start the engine is referencing the correct engine that you've defined in the repository. Also, in the engine editor, be sure that the engine has your build definition checked in its "supported definitions" section. When you say "no action in the console of jbe", do you mean absolutely nothing? You should at least see something like this: Running build loop... Waiting for request... If you are seeing nothing, be sure you are running jbe with a java 5 vm, either on your path or with the -vm argument. Java 1.4 is not supported. We've seen cases that the engine just hangs when attempting to run it with java 1.4. |
|
Thanks for your reply.
I am indeed starting the JBE with the same set repository address, userId and pass as the client. I checked the engineId and it is the same between the definition and its usage in JBE. Jus for kicks, I created yet another engineId but that doesn't work also. The engine definition is marked active and does have my build definition checked under 'supported definitions'. When I start the JBE, I do indeed see the messages you suggest, Running build loop... Waiting for request... and then when I kick the build off, I do not see anything - I expect to see the 'Found a build...' message but it never appears and the build stays in 'Pending...' state. I am indeed using java 5. The difference between the set of machine where I am able to do a remote build and this one is only that server here is behind a firewall and running secure while the other one was not. |
|
The default polling interval is 30 seconds. So you'd need to wait at least
30 seconds to see any action. You can override by starting jbe with -sleeptime <seconds> Can you show me the command line you are using to start jbe ? Let me know which jazz build (M3?) you are using. I can build you a jar with some debug information to help us get to the bottom of this. |
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.