-
Bug
-
Resolution: Done
-
Blocker
-
10.0.0.CR2
-
None
It is required for EAP7 to contain all features from EAP6.
Per https://issues.jboss.org/browse/ANDIAMO-7, in EAP6 every serious log message (warn, error, fatal) should have a unique code that can be used to identify it.
However, we found 160 serious log messages in EAP7.0.0.DR11 without id.
List of serious log messages without id from a smoke test (link to Jenkins run will be provided when the automated test case is finished):
/jboss-eap-7.0-src/ejb3/src/main/java/org/jboss/as/ejb3/remote/protocol/versionone/VersionOneProtocolChannelReceiver.java:318 EjbLogger.REMOTE_LOGGER.warn("Could not send a cluster removal message for cluster: " + registry.getGroup() + " to the client on channel " + channelAssociation.getChannel(), ioe); /jboss-eap-7.0-src/jpa/eclipselink/src/main/java/org/jipijapa/eclipselink/JBossLogger.java:86 getLoggerForCategory("logging").warnv("Received message for log level {0}, but no such level is defined in SessionLog! Logging at INFO level...", level); /jboss-eap-7.0-src/connector/src/main/java/org/jboss/as/connector/services/resourceadapters/deployment/AbstractResourceAdapterDeploymentService.java:178 DEPLOYMENT_CONNECTOR_LOGGER.error("Error during recovery shutdown", e); /jboss-eap-7.0-src/connector/src/main/java/org/jboss/as/connector/services/resourceadapters/deployment/AbstractResourceAdapterDeploymentService.java:199 DEPLOYMENT_CONNECTOR_LOGGER.warn("Exception during stopping resource adapter", nfe); /jboss-eap-7.0-src/connector/src/main/java/org/jboss/as/connector/subsystems/datasources/XaDataSourceService.java:64 ConnectorLogger.SUBSYSTEM_DATASOURCES_LOGGER.error("Error during recovery shutdown", e);
Giving blocker priority as this issue blocks RFE verification.
- clones
-
-
- Closed
-
