Terracotta Discussion Forums

I'm trying to connect to the Terracotta server using the Admin Console over a VPN connection and am having problems.

On the server I can see it listening on port 9520 and when I connect in the client I see a new socket established, but the client login screen just says "Timed-out".

My client is running on Windows XP with Java 1.5.0_15. The server is running on CentOS with Sun Java 1.5.0_17.

The server log file doesn't show anything on an attempted connection. I haven't been able to find any client log files.

What should I be looking at next?

Randy

You can try changing the console's default timeout of 8 seconds:

export JAVA_OPTS="-Dcom.tc.admin.connect-timeout=20000"
admin.sh&

Changing that setting makes it take longer to timeout, but no different in the behavior.

I ran WireShart and got a packet capture of the connection. On my local machine I can see traffic coming back from the server in time, I'm just not quite sure what it means. Maybe the attached PCAP file can help.

Be sure the server box has a valid address defined in /etc/hosts. JMX can get tripped up with the sort of /etc/hosts files that come out-of-the-box in many Linux distros.

In /etc/hosts the machine has its IP address with the machine's name:

10.0.100.152 name
127.0.0.1 localhost.localdomain localhost

Also, I've been able to get a Windows machine set up on the same network as the TC server and the Admin Console works from there. I have a workaround, but I'm still curios as to why it doesn't work over the VPN.

From the packet capture I can see some minimal amount of traffic coming back over the VPN. Could it be because with the VPN open I have multiple active network adapters on my computer?

Did anyone ever figure this out.

I have the same issue. running my laptop at my office works fine, but over vpn no luck.

I was getting timeout issues first then I increased the timeout variable in the batch script. Now I can connect, but the QUARTZ instance does not show up. Even though I know its running. is there a similar setting for the quartz instance timeout?

I am having this same problem, connecting from my work network to our EC2 servers... the weird part is that this only happens with terracotta enterprise. With open source (we have it running as well on a different port and jmx opened up in a diff port from EE) it works fine (i am using the corresponding dev console for each).

I check in Liferay

football jerseys
nfl jersey store
wholesale baseball jerseys
cheap football jerseys
baseball jerseys