[wildfly-dev] Version notifications at library init

[Brian Stansberry]

> On Mar 29, 2017, at 6:44 AM, Rostislav Svoboda <rsvoboda at redhat.com> wrote:
> 
> 
>> Some existing ids would need to change to comply but that doesn’t seem like
>> a big deal.
> 
> Maybe not for community, but can be trouble for product. Customers are encouraged to parse logs based on message IDs.
> 

I think the likelihood that people are relying on parsing out our version # messages is really low. If they did a convention of reserving 0 for these might be a benefit for them too.

Here’s what we log now (standalone-full-ha.xml):

06:49:15,205 INFO  [org.jboss.modules] (main) JBoss Modules version 1.6.0.Beta6
06:49:15,503 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.7.SP1
06:49:15,638 INFO  [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: WildFly Full 11.0.0.Beta1-SNAPSHOT (WildFly Core 3.0.0.Beta12-SNAPSHOT) starting
06:49:16,987 INFO  [org.wildfly.security] (ServerService Thread Pool -- 35) ELY00001: WildFly Elytron version 1.1.0.Beta33
06:49:17,202 INFO  [org.xnio] (MSC service thread 1-6) XNIO version 3.5.0.Beta2
06:49:17,208 INFO  [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.5.0.Beta2
06:49:17,238 INFO  [org.jboss.as.jaxrs] (ServerService Thread Pool -- 49) WFLYRS0016: RESTEasy version 3.0.21.Final
06:49:17,271 INFO  [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 52) WFLYCLJG0001: Activating JGroups subsystem. JGroups version 3.6.13
06:49:17,392 INFO  [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=5.0.0.Beta1
06:49:17,407 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0003: Undertow 1.4.11.Final starting
06:49:17,409 INFO  [org.jboss.as.connector] (MSC service thread 1-8) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.2.Final)
06:49:17,705 INFO  [org.jboss.remoting] (MSC service thread 1-6) JBoss Remoting version 5.0.0.Beta19
06:49:18,544 INFO  [org.jboss.ws.common.management] (MSC service thread 1-6) JBWS022052: Starting JBossWS 5.1.8.Final (Apache CXF 3.1.10)

8 of those have ids. Perhaps WFLYSRV0049 would be a problem, although the final “started” message is more likely what would be monitored and it shows the versions too.

-- 
Brian Stansberry
Manager, Senior Principal Software Engineer
JBoss by Red Hat