Hello, We see a lot of hexdump information appear in the catalina.out log file (example below). What can this mean, as we have not noticed this before? A search on google catalina+tomcat+hexdump does not reveil much. There is nothing about it in the documentation.
Maybe this is also usefull to mention, but we are not sure if it is related: We are, at the same time, having troubles with the database connection to oracle. Queries are executed normally but; processes and sessions are not released after the query has returned the resultset (open_cursors are, they stay stable). This takes more and more processes and eventually ending in ora-00020 processes exceeded. We have not had that before. Details: Tomcat: 4.1.12 JKD: 1.4.1_b02 OS: Solaris 7 + required patches. Database: Oracle 8i Sincerely, Filip. --begin example-- 12 34 00 53 00 51 52 45 53 4f 55 52 43 45 3d 4d | .4.S.QRESOURCE=M 59 41 43 43 4f 55 4e 54 26 52 45 46 45 52 45 52 | YACCOUNT&REFERER 3d 52 45 51 55 45 53 54 5f 4f 56 45 52 56 49 45 | =REQUEST_OVERVIE 57 26 41 43 54 49 4f 4e 3d 52 45 51 55 45 53 54 | W&ACTION=REQUEST 5f 44 45 54 41 49 4c 26 52 45 51 55 45 53 54 49 | _DETAIL&REQUESTI 44 3d 34 33 39 33 33 | D=43933 12 34 00 53 00 51 52 45 53 4f 55 52 43 45 3d 4d | .4.S.QRESOURCE=M 59 41 43 43 4f 55 4e 54 26 52 45 46 45 52 45 52 | YACCOUNT&REFERER 3d 52 45 51 55 45 53 54 5f 4f 56 45 52 56 49 45 | =REQUEST_OVERVIE 57 26 41 43 54 49 4f 4e 3d 52 45 51 55 45 53 54 | W&ACTION=REQUEST 5f 44 45 54 41 49 4c 26 52 45 51 55 45 53 54 49 | _DETAIL&REQUESTI 44 3d 34 33 39 31 32 | D=43912 --end example--
