tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From FREY Thibault <tf...@slib.fr>
Subject RE: VAJ and Tomcat 3.2
Date Tue, 05 Dec 2000 08:46:12 GMT


> >Seems that the 8080 port never get's released...

>But I'm running a normal Tomcat -stop type shutdown.

>And why do Tomcat 3.1 work properly, but not 3.2?

Because 3.2 crashes with your config. Here is my congig :

* to start :

public class StartTomcat {
	public static void main(java.lang.String[] args) {
		try {
			Class aClass =
Class.forName("org.apache.tomcat.startup.Tomcat");
			java.lang.reflect.Method method = null;
			Class[] argsClass = new Class[] {String[].class};
			method = aClass.getMethod("main", argsClass);
			Object object = null;
			Object[] arguments = new Object[] {new String[] {}};
			method.invoke(object, arguments);
		}
		catch (Exception e) {
			System.out.println("Exception occurred: " +
e.getMessage());
			e.printStackTrace();
		}
	}
}

Properties for TomcatStart :

    - in Program / Properties : tomcat.home=d:\tomcat3.2\
    - in Class Path :
        - Project path : Tomcat, Servlet API, Xerces and all my stuff
        - Extra directories path :
d:\tomcat3.2\classes\;d:\tomcat3.2\webapps\examples\WEB-INF\classes\;

    where tomcat dir is d:\tomcat3.2\ and d:\tomcat3.2\classes\ are deflated
classes of d:\tomcat3.2\lib\

* to stop :

public class StopTomcat {
	public static void main(java.lang.String[] args) {
		try {
			Class aClass =
Class.forName("org.apache.tomcat.startup.Tomcat");
			java.lang.reflect.Method method = null;
			Class[] argsClass = new Class[] {String[].class};
			method = aClass.getMethod("main", argsClass);
			Object object = null;
			Object[] arguments = new Object[] {new String[]
{"-stop"}};
			method.invoke(object, arguments);
		}
		catch (Exception e) {
			System.out.println("Exception occurred: " +
e.getMessage());
			e.printStackTrace();
		}
	}
}

with the same properties than StartTomcat.

* Be sure that HttpConnectionHandler for port 8080 is set (that's default)

* If you use mod_jk, let ajp13 far away, because it is not as robust as
ajp12, even if faster


>> The only solution I found is to restart IVJ (and therefore the JVM).

>You mean restarting Visual Age, or?

Yes restarting IBM VisualAge for Java (IVJ).

When I said that IVJ doesn't close socket, 

I would say that IVJ doesn't close sockets which were not closed by program.

For example, it's the case if your modify an instance variable while
debugging,

because program craches.


Regards
Thibault FREY.

Mime
View raw message