0 Replies Latest reply on Oct 21, 2003 3:38 PM by raalst

    cleaning the bootlog (or die trying)

    raalst

      I got jboss 3.2.2 to run (on jdk1.4.2_01).
      the boot log contains complaints. I would like to know
      if I should be worried, what causes them and
      preferably how to fix them.

      I will add complete bootlog if that is requested,
      but I will start with snippet first :

      1) JK2 properties file missing

      2003-10-21 22:40:43,500 DEBUG [org.apache.jk.server.JkMain] Starting Jk2, base dir= C:\jboss\server\default
      2003-10-21 22:40:43,500 WARN [org.apache.jk.server.JkMain] No properties file found C:\jboss\server\default\conf\jk2.properties
      2003-10-21 22:40:43,610 DEBUG [org.apache.jk.server.JkMain] Substituting soTimeout channelSocket.soTimeout 20000
      2003-10-21 22:40:43,610 DEBUG [org.apache.jk.server.JkMain] Substituting port channelSocket.port 8009

      and repeatedly something about setDelegate

      2003-10-21 22:40:45,920 INFO [org.jboss.web.localhost.Engine] ContextConfig[/jbossmq-httpil]: Configured an authenticator for method BASIC
      2003-10-21 22:40:45,970 WARN [org.jboss.web.tomcat.tc4.EmbeddedTomcatService] Unable to invoke setDelegate on class loader:org.jboss.web.tomcat.tc4.WebCtxLoader$ENCLoader@96212a
      2003-10-21 22:40:46,030 INFO [org.jboss.web.localhost.Engine] StandardManager[/jbossmq-httpil]: Seeding random number generator class java.security.SecureRandom

      ps I did do a search first, but no clear answer found,
      especially not for vanilla 3.2.2.

      TIA and keep up the good work,
      Ronald van Aalst