Seems we have to do something to address this. It's a pretty easy issue to have. https://jira.terracotta.org/jira//browse/CDV-464
Let's figure something out. On Oct 15, 2007, at 4:45 AM, Geert Bevin wrote: > Hi all, > > I just helped someone on IRC who had a problem when starting the > Terracotta server. He constantly received this error message: > > WARN - Connection refused from server: 127.0.0.1:9510 > > I wrongly assumed last week that he had problems with his local linux > firewall, or that another process was tying up the port, Steve had > him do portscans, etc etc ... the usual linux sysadmin stuff. > > It turns out that he set the JAVA_OPTS environment variable through > dso-env.sh, probably to test client and server on the same machine > and in the same console. However, I assume that when the bootjar is > present when the server is started, the TC-instrumented Java classes > try to contact a server during server startup. Since this startup > isn't finished yet, the above warning message is displayed. When the > bootjar is not present, his TC server started without a problem. > > I think we should add a check as early as possible to the server > startup logic, to make sure that users haven't activated the bootjar > for the server and to tell them what to do in case it is present. > Otherwise, a problem like this can be very discouraging and most > probably turn off people that are trying Terracotta out. > > What do you think, does this seem feasible? > > Take care, > > Geert > > -- > Geert Bevin > Terracotta - http://www.terracotta.org > Uwyn "Use what you need" - http://uwyn.com > RIFE Java application framework - http://rifers.org > Music and words - http://gbevin.com > > _______________________________________________ > tc-dev mailing list > [email protected] > http://lists.terracotta.org/mailman/listinfo/tc-dev _______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
