I'm using v3 latest promoted build (3/26/2009). After running the
server for a while, I noticed there are 2 server.log files, both are
actively logged:
/v3/glassfish/domains/domain1/logs > ll
total 480
-rw-r--r-- 1 staff 58938 Mar 27 22:40 server.log
-rw-r--r-- 1 staff 176221 Mar 27 22:40 server_2009-03-27.log
-rw-r--r-- 1 staff 4096 Mar 27 21:50 jvm.log
server.log and server_2009-03-27.log have the same timestamp. What's
more interesting is, autodeploy and EJB events are logged into
server.log, and web container events are logged to
server_2009-03-27.log. I was looking for errors in server.log after my
app failed but couldn't find any as they have been diverted to
server_2009-03-27.log.
The format of server_2009-03027 (see below) is different from
server.log. At least its dateTime format is different from server.log.
Any idea what's happening here?
2009-03-27 18:14:18 createObjectName with
StandardEngine[com.sun.appserv].StandardHost[__asadmin]
2009-03-27 18:14:18 createObjectName with
StandardEngine[com.sun.appserv].StandardHost[server]
2009-03-27 21:50:18 createObjectName with
StandardEngine[com.sun.appserv].StandardHost[__asadmin]
2009-03-27 21:50:18 preRegister with
com.sun.appserv:type=Logger,host=__asadmin
2009-03-27 21:50:18 createObjectName with
StandardEngine[com.sun.appserv].StandardHost[server]
2009-03-27 21:50:18 preRegister with com.sun.appserv:type=Logger,host=server
2009-03-27 22:23:12 StandardWrapperValve[Servlet1]: PWC1406:
Servlet.service() for servlet Servlet1 threw exception
java.lang.ClassCastException: java.lang.String cannot be cast to
java.util.concurrent.Future
2009-03-27 22:40:02 StandardWrapperValve[Servlet1]: PWC1406:
Servlet.service() for servlet Servlet1 threw exception
java.lang.ClassCastException: java.lang.String cannot be cast to
java.util.concurrent.Future
-cheng