Friday, November 23, 2012

AM Session DB - To be improved

In amsessiondb.log, you'll see the following being captured:


Starting...  true
/data/webserver/jdk1.6.0_31/jre/bin/java -Xms128m -Xmx512m -classpath /home/webadm/bin/tools/amsfo/jmq/imq/lib/imq.jar:/home/webadm/bin/tools/amsfo/jmq/imq/lib/jms.jar:/home/webadm/bin/tools/amsfo/ext/je.jar:/home/webadm/bin/tools/amsfo/locale:/home/webadm/bin/tools/amsfo/lib/am_sessiondb.jar:. com.sun.identity.ha.jmqdb.client.FAMHaDB
Initializing and connecting to the Message Queue server ...
Successfully started.
done. \n
Error: Connection to Broker Lost. Broker could be down.
Error: Connection to Broker Lost. Broker could be down.
Starting...  true
/data/webserver/jdk1.6.0_31/jre/bin/java -Xms128m -Xmx512m -classpath /home/webadm/bin/tools/amsfo/jmq/imq/lib/imq.jar:/home/webadm/bin/tools/amsfo/jmq/imq/lib/jms.jar:/home/webadm/bin/tools/amsfo/ext/je.jar:/home/webadm/bin/tools/amsfo/locale:/home/webadm/bin/tools/amsfo/lib/am_sessiondb.jar:. com.sun.identity.ha.jmqdb.client.FAMHaDB
Initializing and connecting to the Message Queue server ...
Successfully started.
done. \n
Error: Connection to Broker Lost. Broker could be down.
Error: Connection to Broker Lost. Broker could be down.
Starting...  true
/data/webserver/jdk1.6.0_31/jre/bin/java -Xms128m -Xmx512m -classpath /home/webadm/bin/tools/amsfo/jmq/imq/lib/imq.jar:/home/webadm/bin/tools/amsfo/jmq/imq/lib/jms.jar:/home/webadm/bin/tools/amsfo/ext/je.jar:/home/webadm/bin/tools/amsfo/locale:/home/webadm/bin/tools/amsfo/lib/am_sessiondb.jar:. com.sun.identity.ha.jmqdb.client.FAMHaDB
Initializing and connecting to the Message Queue server ...
Successfully started.


Useful? Not at all.. The basic element of timestamp is not even there.

.

No comments:

Post a Comment