Tomcat update -> failure

[Gregory Guthrie]

Problem with Apache(1.3.22)+Tomcat(3.3) after update:

I have a working 2.2.17 system, and am running Apache+Tomcat.

Having not used it for awhile, or updated in 4-6 months, I did an apt-get install" of tomcat and apache, to get the most current versions. It did an update, and now it is broken.  -(

Apache seems to work fine, and has the prescribed tomcat attachments in /etc/apache/httpd.conf, but tomcat fails. Browser symptoms: all .jsp pages give "not found".

1) At first none of the servlet or JSP pages worked.
Once the first request is made, tomcat keeps getting errors, about one per second, like this (forever)

PoolTcpEndpoint Endpoint ServerSocket[addr=localhost/127.0.0.1,port=0,localport
=8009] ignored exception java.net.SocketException Socket closed
java.net.SocketException Socket closed
        at java.net.PlainSocketImpl.close(PlainSocketImpl.java408)
        at java.net.Socket.close(Socket.java383)
        at java.net.ServerSocket.implAccept(ServerSocket.java206)
        at java.net.ServerSocket.accept(ServerSocket.java181)
        at org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(Unknown Source)
        at org.apache.tomcat.util.net.TcpWorkerThread.runIt(Unknown Source)
        at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(Unknown Source)
        at java.lang.Thread.run(Thread.java)
PoolTcpEndpoint Endpoint ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8081] ignored exception java.net.SocketException Socket closed
java.net.SocketException Socket closed
        at java.net.PlainSocketImpl.close(PlainSocketImpl.java408)
        at java.net.Socket.close(Socket.java383)
        at java.net.ServerSocket.implAccept(ServerSocket.java206)
        at java.net.ServerSocket.accept(ServerSocket.java181)
        at org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(Unknown Source)

I found that the workers.properties file was not in the right (referenced in config files), so I repaired that.
  (why did the (re-)install goof this up?)

2) Now the servlet examples work, all html works, either through Apache or directly by tomcat (:8081),
    but all .Jsp examples fail: "page not found"
        omega/etc/tomcat/logs# more mod_jk.log
        [jk_uri_worker_map.c (335)]: jk_uri_worker_map_t::uri_worker_map_close, NULL parameter
        [jk_uri_worker_map.c (185)]: In jk_uri_worker_map_t::uri_worker_map_free, NULL parameters
        ...

and log/stdout.log shows:
        Unable to open log file: /usr/share/tomcat/logs/servlet-${yyyyMMdd}.log!  Using stderr as the default.
        Unable to open log file: /usr/share/tomcat/logs/jasper-${yyyyMMdd}.log!  Using stderr as the default.
        Unable to open log file: /usr/share/tomcat/logs/examples.log!  Using stderr as the default.
        Unable to open log file: /usr/share/tomcat/logs/servlet_examples.log!  Using stderr as the default.

and in stdout, a bunch of good startup stuff, and then:
2002-01-11 14:18:28 - /examples: Error creating validation mark  - java.io.FileNotFoundException: /usr/share/tomcat/work/DEFAULT/examples/webxmlval.txt
        at java.io.FileOutputStream.<init>(FileOutputStream.java)
        at java.io.FileOutputStream.<init>(FileOutputStream.java)
        at org.apache.tomcat.facade.WebXmlReader.processWebXmlFile(Unknown Source)
        at org.apache.tomcat.facade.WebXmlReader.contextInit(Unknown Source)
        at org.apache.tomcat.core.Context.init(Unknown Source)
        at org.apache.tomcat.core.ContextManager.init(Unknown Source)
        at org.apache.tomcat.startup.EmbededTomcat.initContextManager(Unknown Source)
        at org.apache.tomcat.startup.EmbededTomcat.execute1(Unknown Source)
        at org.apache.tomcat.startup.EmbededTomcat$1.run(Unknown Source)
        at org.apache.tomcat.util.compat.Jdk11Compat.doPrivileged(Unknown Source)
        at org.apache.tomcat.startup.EmbededTomcat.execute(Unknown Source)
        at org.apache.tomcat.util.IntrospectionUtils.execute(Unknown Source)
        at org.apache.tomcat.startup.Main.execute(Unknown Source)
        at org.apache.tomcat.startup.Main.main(Unknown Source)
...
2002-01-11 14:18:41 - Http10Interceptor: Starting on 8081
2002-01-11 14:18:41 - Ajp12Interceptor: Starting on 8007
2002-01-11 14:18:41 - Ajp13Interceptor: Starting on 8009
2002-01-11 14:18:41 - Ajp12Interceptor: Can't create stop file: /usr/share/tomcat/conf/ajp12.id - java.io.FileNotFoundException: /usr/share/tomcat/conf/ajp12.id
        at java.io.FileOutputStream.<init>(FileOutputStream.java)
        at java.io.FileOutputStream.<init>(FileOutputStream.java)
        at java.io.FileWriter.<init>(FileWriter.java)
        at org.apache.tomcat.modules.server.Ajp12Interceptor.engineState(Unknown Source)
        at org.apache.tomcat.core.ContextManager.setState(Unknown Source)
        at org.apache.tomcat.core.ContextManager.start(Unknown Source)
        at org.apache.tomcat.startup.EmbededTomcat.start(Unknown Source)
        at org.apache.tomcat.startup.EmbededTomcat.execute1(Unknown Source)
        at org.apache.tomcat.startup.EmbededTomcat$1.run(Unknown Source)
        at org.apache.tomcat.util.compat.Jdk11Compat.doPrivileged(Unknown Source
)

And stdout.log accumulates the "socket exceptions" as above, forever.
        PoolTcpEndpoint: Endpoint ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8081] ignored exception:   java.net.SocketException: Socket closed
        java.net.SocketException: Socket closed

4) I do notice tha tApache reports: /etc/apache/logs/error.log
        [Fri Jan 11 14:17:28 2002] [notice] Apache/1.3.22 (Unix) Debian GNU/Linux mod_jk configured -- resuming normal operations
        [Fri Jan 11 14:17:28 2002] [notice] Accept mutex: sysvsem (Default: sysvsem)
        [Fri Jan 11 14:18:41 2002] [notice] SIGUSR1 received.  Doing graceful restart
        [Fri Jan 11 14:18:42 2002] [notice] Apache/1.3.22 (Unix) Debian GNU/Linux mod_jk configured -- resuming normal operations
        [Fri Jan 11 14:18:42 2002] [notice] Accept mutex: sysvsem (Default: sysvsem)
        [Fri Jan 11 14:30:37 2002] [crit] (98)Address already in use: make_sock: could not bind to port 80


All help appreciated.
(please also reply directly, unreliable listserve connection)
--------------------------------------------------------
Gregory Guthrie
--------------------------------------------------------