On 5/14/2013 5:27 AM, Mark Thomas wrote:
On 14/05/2013 04:34, Chirag Dewan wrote:
You need to destroy the connector to close the port.
Mark,
That seems to work. :)
Now the port is free. But is it the right approach?
You had a problem you couldn't solve. Someone with an @apache.org e-mail
address (i.e. an Apache committer and probably a Tomcat committer -
something you can easily check) provided a solution that worked and you
are asking if that solution is correct? I am trying very hard not to be
to be extremely sarcastic right now.
Mark, remember that most people's e-mail clients will only show the
"friendly" name of the e-mail sender if it's available, not the full
e-mail address, so he probably didn't see your @Apache.org address.
Those of us who have been participating (or at least lurking) here for a
while understand that you know pretty much everything there is to know
about tomcat, but a new poster may not, so I'd give him the benefit of
the doubt on this.
D
Is this something we need to do in Tomcat 7 specifically?
There was a lot of lifecycle clean-up in Tomcat 7 including:
- using the same interface for all components
- adding JMX registration consistently
- making sure things were symmetric (what is done in init() is undone in
destroy(), what is done in start() is undone in stop())
It is likely that binding and unbinding of the port were different in
Tomcat 6 but I haven't checked svn to confirm this.
Sockets in Tomcat 7 connectors are bound in init() and unbound in
destroy() by default although you can change this to start() and stop()
by setting the bindOnInit attribute on the connector to false.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
