The logbridge update causes this.
If you copy over the old artifact to JBOSS_HOME/lib (and rename it to jboss-logbridge.jar)
the start message is back:
20:36:18,171 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8
080
20:36:18,187 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
20:36:18,203 INFO [ServerImpl] JBoss (Microcontainer) [5.1.0.Beta1 (build: SVNT
ag=JBoss_5_1_0_Beta1 date=200903071800)] Started in 38s:391ms
- <version.org.jboss.logbridge>1.0.0.CR1</version.org.jboss.logbridge>
+ <version.org.jboss.logbridge>1.0.0.CR2</version.org.jboss.logbridge>
Scott Stark wrote:
I stepped through the logging statement and it is a log4j delegate
that
is sending msgs to some appenders, but I did not look into it in detail.
Somehow we are not getting to the console or file appenders.
Scott Stark wrote:
> Its definitely going through this line 493 in AbstractServerImpl:
>
> log.info("JBoss (Microcontainer) [" +
> jbossPackage.getImplementationVersion() + "] Started in " + watch);
>
>
> but nothing is showing up in the console or ther server logs.
>
> [509][valkyrie: log]$ grep 'JBoss (Microcontainer)' *.log
> boot.log:10:11:46,427 INFO [ServerImpl] Starting JBoss
> (Microcontainer)...
> [510][valkyrie: log]$
>
> Something has to have changed with the log behavior.
>
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-development