-
Language:
English
-
Language:
English
4.3. Known Issues
Hibernate
- 1094756 - HHH-9170 HHH-9174 ORM Performance regression
- A regression that can cause performance degradation is present in this release of JBoss EAP 6. It has been traced to the
Statement.getWarnings()method (which was negatively impacted by changes made to resolve an earlier memory leak caused by a bug in the Sybase JDBC drivers).To address the performance issues, new code has been added to check the log level of warnings and ignore any messages below WARN level. These messages are cleared and not written to theserver.logfile. While this measure mitigates much of the performance degradation, the issue may still present to varying degrees, depending on the JDBC implementation being used.To avoid the performance issue completely, users can raise this threshold by setting theorg.hibernatelogging category to ERROR. Care should be taken before making this change, however, as ignoring warnings below the ERROR level can obfuscate possible problems in the database.
Patching
- 1065830 - patch conflict with pure EAP 6.2 installed using the jar installer
- If you used the JAR installer to install JBoss EAP, you may encounter conflicts when applying a cumulative patch. Due to differences in some files included with the JAR installer distribution, the patch tool can mistakenly identify these differences as user modifications.See Applying Cumulative Patches to Installer Installations for information about how to resolve these conflicts. This issue is expected to be fixed in a future release.
Scripts and Commands
- 1072227 - Wrong handling of --debug argument by standalone.[sh|bat] scripts
- This release of JBoss EAP 6 carries a bug where-in the shell script for running EAP in standalone mode (standalone.sh|bat) does not use the default port (port 8787) when the script is used with "debug" argument without a port number.As a result execution of the script (standalone.sh|bat) with "debug" argument results in an error and does not start the server.A possible workaround for this issue is to specify a port number when the script (standalone.sh|bat) is used with "debug" argument:standalone.[sh|bat] --debug [port number]This issue is expected to be resolved in a future release of the product.