JBoss Enterprise Application Platform 6.4 Update 10 Release Notes
Important: This update is not the latest cumulative patch, it is recommended to apply the latest update, see these links for the latest:
In order to better meet customer expectations, micro releases for JBoss EAP 6 have been discontinued and replaced with updates delivered on a repeating schedule, targeting a new release every 6 weeks.
Each new update will contain a number of bug fixes for customer reported issues and potentially a number of security fixes. We expect that the updates will substantially reduce the number of individual patches that we produce and that customers must manage to keep their installations up to date.
Note: JBoss EAP 6.4 Update 10 (or later) requires 6.4 Update 09 to be applied first see this article for more information.
For more information see the following Red Hat Knowledgebase articles: Maintenance Release Changes in EAP 6.2+ and Updated Patch Management with EAP 6.2+
This update includes all fixes and changes from This content is not included.JBoss EAP 6.4 Update 9 / Release Notes
This update includes the following bug fixes or changes:
| ID | Component | Summary |
|---|---|---|
| This content is not included.1287732 | CDI/Weld | If a module META-INF descriptor is overlayed the beans.xml need to be added to the overlay as well - otherwise no CDI injection [details] |
| This content is not included.1351768 | CLI | CLI fails to find deployment artifact located in a Windows Share UNC path |
| This content is not included.1340342 | Clustering | Race condition in ServiceProviderRegistryService |
| This content is not included.1312064 | Domain Management | HTTP Server used for management doesn't support non-ascii characters in BASIC authentication |
| This content is not included.1280235 | Domain Management | ManagedDatagramSocketBinding.close throws NPE |
| This content is not included.1344515 | EJB | Bug in EJB's Timeout handling on Future.get() |
| This content is not included.1350355 | EJB | EJBs accessible too early (spec violation) - part 2 - (supplementation) This content is not included.[details] |
| This content is not included.1346242 | EJB | InvalidBytecodeException when an EJB local interface declares static method [details] |
| This content is not included.1327944 | EJB | Calling remote asynchronous void method causes OutOfMemoryError in direct buffer memory |
| This content is not included.1326114 | Hibernate | HHH-10679 - Subselect not used when batch loading by id [details] |
| This content is not included.1337337 | Hibernate | HHH-10757, HHH-9021 - "select new ..." with NULL CAST fails with QuerySyntaxException: unexpected AST node: NULL |
| This content is not included.1340465 | HornetQ | Duplicate messages in replicated HA topology |
| This content is not included.1348322 | HornetQ | HornetQ Server should always remove old files beyond getMaxSavedReplicatedJournalsSize This content is not included.[details] |
| This content is not included.1320132 | JPA | naming context is not setup when starting the persistence unit [details] |
| This content is not included.1347845 | JSF | JAVASERVERFACES-4137 - Enable CLIENTSTATESAVINGPASSWORD By Default In JSF 1.2 |
| This content is not included.1353145 | JSF | JAVASERVERFACES-2544 - Endless Loop By Unsynchronized WeakHashMap |
| This content is not included.1283482 | Logging | Log manager's module naming does does not support slots [details] |
| This content is not included.1295665 | Logging | Syslog handler does not connect to syslog |
| This content is not included.1295657 | Logging | October dates are not logged properly |
| This content is not included.1295660 | Logging | TCP reconnect will only attempt to reconnect once |
| This content is not included.1274572 | Logging | Log rotation fails on Windows if target already exists |
| This content is not included.1349223 | Logging | logging custom-handler does not load module with slot |
| This content is not included.1286272 | MSC | DuplicateService Exception if services are used in multiple modules of an EAR deployment [details] |
| This content is not included.1346552 | Microcontainer and Deployers | If there are two deploy directories a deployment failure in one undeployes everything in the other |
| This content is not included.1257023 | Other | JANDEX -o option is not working |
| This content is not included.1257022 | Other | Jandex fails to reindex index JAR file |
| This content is not included.1257021 | Other | JarIndexer mishandles paths with the extension in multiple elements |
| This content is not included.1244847 | Other | JANDEX-33 - Infinite loop when a JAR contains a CRC error on a .class file |
| This content is not included.1342685 | PicketLink | IDP initiated (unsolicited) responses should not contain InResponseTo attributes This content is not included.[details] |
| This content is not included.1353338 | PicketLink | picketlink does not return SessionIndex in LogoutRequest This content is not included.[details] |
| This content is not included.1360527 | RESTEasy | Accept header matching |
| This content is not included.1315936 | RESTEasy | Custom error page is ignored for 405 Method Not Allowed |
| This content is not included.1270708 | Security | authentication fails with password containing umlauts |
| This content is not included.1277699 | Server | TempFileProviderService threads consume high CPU [details] |
| This content is not included.1360851 | Server | Re-invoking InterceptorContext.proceed() throws CannotProceedException |
| This content is not included.1299189 | Server | JBAS014612: Operation ("clean-obsolete-content") failed .. StringIndexOutOfBoundsException when OS puts metadata files in content repo [details] |
| This content is not included.1271673 | Server | Filesystem deployment scanner deployment failure removes other scanners ' deployments [details] |
| This content is not included.1358822 | Server | BZ1290960 caused issue with some missing dependencies [details] |
| This content is not included.1350259 | Web | Random ClassCastException for ErrorReportValve at start up [details] |
Note: This update should only be applied to installer or zip-based installations.
To apply this update using the CLI on Unix-based systems, run the following command from JBOSS_HOME:
bin/jboss-cli.sh "patch apply path/to/jboss-eap-6.4.10-patch.zip"
To apply this update using the CLI on Windows-based systems, run the following command from JBOSS_HOME:
bin\jboss-cli.bat "patch apply path\to\jboss-eap-6.4.10-patch.zip"
These commands will apply the update to the installation that contains the CLI script. Other scenarios and use of the management console are covered in the This content is not included.JBoss EAP 6.4 Installation Guide