JBoss Enterprise Application Platform 6.2

6.2.0 Release Notes

New Features, Known Issues, and Support Information for Red Hat JBoss Enterprise Application Platform 6.2.0

Nidhi Chaudhary

Lucas Costi

Russell Dickenson

Sande Gilda

Vikram Goyal

Eamon Logue

Darrin Mison

Scott Mumford

David Ryan

Misty Stanley-Jones

Keerat Verma

Tom Wells

Legal Notice

Copyright © 2013 Red Hat, Inc..
This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack Logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.

Abstract

These release notes contain important information related to Red Hat JBoss Enterprise Application Platform 6.2.0. Known problems, additional resources, and other current issues are addressed here.
The changes documented in these release notes are relative to the previous release, 6.1.1.

1. Overview

Red Hat JBoss Enterprise Application Platform 6 (JBoss EAP 6) is Red Hat's response to significant changes in the way organizations develop and deploy enterprise applications. As organizations seek to lower operational costs and reduce time to market for new applications, JBoss EAP 6 has been rebuilt for a vision of the future, boasting an innovative modular, cloudy-ready architecture, powerful management and automation, and world class developer productivity.
JBoss EAP 6 is Java EE 6 certified and features powerful yet flexible management, improved performance and scalability, and many new features to improve developer productivity. All with Red Hat's market-leading reputation for certification and support, ensuring your administration and development needs continue to drive forward into the future and beyond.

2. Frequently Asked Questions

Q: What has changed in this release?
Q: Where's the rest of the documentation?
Q: Where are the upgrade instructions ?
Q: What operating systems, Java Virtual Machines, and database servers is this product supported on?
Q: Is the included H2 database supported in production?
Q: What industry standards does JBoss EAP 6.2.0 support?
Q: What issues might I encounter when migrating to this release?
Q: What components are included in this release and what version are they?
Q: What Technology Previews are included in this release?
Q: Where can I find out more details about my support contract ?
Q: I found a mistake in this document. How do I report it?
Q:
What has changed in this release?
A:
JBoss EAP 6.2.0 includes many improvements and fixes. For specific details refer to Section 7, “Changes in this release”.
Q:
Where's the rest of the documentation?
A:
The full JBoss EAP 6.2.0 documentation suite can be found at https://access.redhat.com/site/documentation/JBoss_Enterprise_Application_Platform/.
Q:
Where are the upgrade instructions ?
A:
The upgrade instructions can be found in the Installation Guide. Refer to the documentation suite at https://access.redhat.com/site/documentation/JBoss_Enterprise_Application_Platform/.
Q:
What operating systems, Java Virtual Machines, and database servers is this product supported on?
A:
Refer to https://access.redhat.com/site/articles/111663 for a complete list of the operating system, Java Virtual Machine, database server and JDBC driver combinations that have been tested and verified with JBoss EAP 6.2.0.
Q:
Is the included H2 database supported in production?
A:
No. The H2 database is included only for evaluation, testing and demonstration purposes. It is not a supported configuration for a production environment. Refer to https://access.redhat.com/site/solutions/148633 for additional information.
Q:
What industry standards does JBoss EAP 6.2.0 support?
A:
Refer to https://access.redhat.com/site/articles/113373 for a complete list of supported specifications and standards.
Q:
What issues might I encounter when migrating to this release?
A:
Refer to Section 7, “Changes in this release” to learn about the differences between this release of JBoss EAP and previous releases that may cause difficulties when migrating your applications to this version.
Q:
What components are included in this release and what version are they?
A:
Refer to https://access.redhat.com/site/articles/112673 for a complete list of the included components.
Q:
What Technology Previews are included in this release?
A:
JBoss EAP 6.2.0 includes a number of Technology Preview features. Technology Preview features are not supported, may not be functionally complete, and are not intended for production use. They are included to provide customers with early access to upcoming product innovations, enabling them to test functionality and provide feedback during the development process.
Refer to Section 4, “Features Provided as Tech Preview Only” for a complete list of Technology Preview features in this release.
Q:
Where can I find out more details about my support contract ?
A:
Details of support policies are located at the following URLs:
Q:
I found a mistake in this document. How do I report it?
A:
To provide feedback on this document, file a bug at https://bugzilla.redhat.com and specify the product JBoss Enterprise Application Platform, version 6.2.0, and component documentation-6.2.0_Release_Notes.

3. New Features

The following new features have been added in JBoss EAP 6.2.0.
Generic JMS Resource Adapter
A generic JMS resource adapter is now available with EAP 6.2. This resource adapter is provided to support integration with external JMS systems that do not provide their own resource adapter and supports bot XA and non-XA use cases. Refer to section 21.9 of the Administrative Guide for configuration steps. See the Known Issues section for current known issues.
RBAC for Management Operations
Role-based access control (RBAC) has been implemented, improving granularity of access control for management operations through all management interfaces. Users and groups can be associated with one of several roles that determine the level of access to the management operations.
Management Operations for Patching
Management operations to install patches, roll-back patches, and report patch state have been implemented. These operations enable users to install CVE, single, and cumulative patches in JBoss EAP 6.2 releases and beyond. The operations are exposed in the CLI, Native, and HTTP management interfaces. The operations will be exposed in the console in a later release.
Administrative Audit Logging
New configuration options for logging of administrative actions. Management access to the audit log configuration can be scope to Auditor role defined in RBAC configuration.
PicketLink STS Quickstart
The PicketLink Security Token Service (STS) is now available as a QuickStart.
WebSphere MQ Certification
Integration with WebSphere MQ via the WebSphere MQ resource adapter has been tested and certified.
JDBC Transaction Store
JBoss transactions can be configured to store transaction state in any of the RDBMS systems tested with JBoss EAP 6.2. This enhancement eliminates the need for a shared file system for transaction recovery.
Syslog Handler Configuration
JBoss EAP 6 now provides a handler and configuration for the syslog protocol.
WSI-Basic Profile 1.2
JBoss Web Services has been tested to assure compliance with the WSI-Basic Profile 1.2.
WSI-Basic Profile 2.0
JBoss Web Services has been tested to assure compliance with the WSI-Basic Profile 2.0.
HornetQ discovery via JGroups
HornetQ now offers dynamic discovery of server connection settings via UDP and JGroups.
External JNDI Federation
A Naming subsystem configuration has been added to the JBoss EAP 6 configuration that enables an administrator to connect an external naming system to the JBoss EAP 6 JNDI. This capability replaces the ExternalContextMBean from JBoss EAP 5.
JBoss CLI Silent Mode
A 'Silent Mode' has been added to the CommandContext API for processes embedding the CLI.
Support of custom transports in the Mail subsystem
The mail subsystem has been enhanced to enable an administrator to provide a custom transport protocol.
New Hibernate Batch Loading Algorithms
Hibernate has added two batch loading algorithms to the existing Legacy algorithm: Dynamic and Padded.
Hibernate - Improved Second Level Caching of Object References for Non-Mutable Data
Oracle 12c
The Oracle 12c database has been tested and added to the list of supported configurations.

4. Features Provided as Tech Preview Only

The following configurations and features are known to have issues and are provided as tech previews only. They are not supported in a production environment.
WS-Trust/STS with JBoss Web Services
JBoss Web Services now exposes WS-Trust/STS capabilities from the underlying CXF implementation.
Adding and Removing Modules with the JBoss CLI
The CLI offers new commands to add and remove modules.
WS-AT/XA Bridge
The WS-AT/XA transaction bridge functionality is provided as a technology preview only, and is not supported in a production environment.
RestEasy validation with the Hibernate Validator
RestEasy now delivers a validation provider to support the Hibernate Validator delivered with JBoss EAP 6.
Restored ServiceMBean helper classes
Module org.jboss.as.system-jmx has been introduced to restore helper classes available in earlier versions of JBoss EAP that assist users in creating MBeans.
Multi-JSF
This feature enables a user to replace the JSF implementation provided with JBoss EAP 6 with a user-supplied JSF implementation.
Hibernate - Improved and Expanded Bytecode Enhancement Support

5. Unsupported Features

The following features are not currently supported in JBoss EAP.
STOMP Protocol with HornetQ
HornetQ has community level support for the STOMP protocol. That protocol has not received testing from Red Hat and is not supported by JBoss EAP.
REST Protocol with HornetQ
HornetQ has community level support for the REST protocol. That protocol has not received testing from Red Hat and is not supported by JBoss EAP.
Infinispan API
The direct use of the Infinispan API is not supported in JBoss EAP 6. Infinispan is used as an implementation detail for various clustering technologies internal to JBoss EAP 6. The API's module.xml incorrectly indicates that direct use is possible, even though this is not the case. This will be fixed in a future release. Direct use of the Infinispan API requires a subscription to JBoss Data Grid.
IPv6 Limitations of JDK 6
The following IPv6 limitations are caused by JDK 6, and are not defects in JBoss EAP 6.
  1. On Microsoft Windows Server, JDK 6 has only a partial IPv6 implementation. This implementation is not sufficient to run JBoss EAP 6. Full IPv6 support on Microsoft Windows Server requires JDK 7.
  2. On Red Hat Enterprise Linux, a bug in Oracle JDK 6 means that any address specified on a client (the network point establishing the connection) which contains a zone-id will fail. To use a zone-id, either upgrade to JDK 7, or use IcedTea/OpenJDK 6, which is available for Red Hat Enterprise Linux, and does not exhibit this bug. For more information about the bug, refer to http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6800096 and https://issues.jboss.org/browse/JBPAPP-8833.
JPA 2.0 Context Propagation Outside of a JTA Transaction
The propagation of Extended Persistence Contexts (XPC) was not taking into account the existence of a transaction, with the XPC always being propagated. That behaviour is not in accordance with the JPA 2.0 specification. The handling of XPC has been modified so that when there is no transaction active the XPC's propagation is ignored and the bean being invoked has its own Persistence Context instead of the XPC.
If your application expects extended persistence contexts to be propagated outside of JTA transactions, you need to consider if your application needs to be modified. Refer to the JBoss EAP 6 Migration Guide for instructions on updating your application.
JBoss Enterprise Application Platform 5 provided a system property (JBPAPP-923.alwaysPropagate) to enable this behaviour. This system property is not available in JBoss EAP 6.
For more information about this decision, refer to https://issues.jboss.org/browse/AS7-1663.
PicketLink IDM
The PicketLink IDM (Identity Management) is not supported in JBoss EAP 6.
Tanuki Service Wrapper
The Tanuki Service Wrapper is not supported with JBoss EAP 6. More information can be found at https://issues.jboss.org/browse/JBPAPP-8651.
XA Recovery on Microsoft SQL Server 2008
XA recovery does not work with Microsoft SQL Server 2008 R1. This features does work with Microsoft SQL Server 2008 R2 SP2. For more information refer to the following URLs:
XA Recovery on MySQL
The MySQL JDBC driver does not implement XA recovery properly. For more information refer to https://issues.jboss.org/browse/JBPAPP-2576.
JBoss OSGi
JBoss OSGi, an implementation of the OSGi specification, has been demoted from Technology Preview to Unsupported. For additional information refer to https://access.redhat.com/site/solutions/362814.

6. Components

The JBoss EAP 6 component matrix is available at the following location: https://access.redhat.com/knowledge/articles/112673.

7. Changes in this release

7.1. Bug Fixes

Application Client

999465 - appclient.xml wrong naming version

The naming subsystem would fail to start because of an incorrect version number in the appclient.xml file, causing a dependency issue. This version has been corrected, and the appclient launches successfully.
1003104 - appclient hang when executing .jar file outside an .ear

An issue existed with the appclient code that prevented the direct execution of .jar files. Additional code has been added to the appclient to correct this issue, and jar files can now be executed directly.

Class Loading

959478 - Add sun.nio.cs & sun.nio.ext paths to sun.jdk module

Missing packages in the sun.jdk module resulted in a ServiceConfigurationError exception being thrown when attempting to load custom character sets when using sun.jdk. This release of JBoss EAP 6 has added the missing packages sun.nio.cs and sun.nio.cs.ext, and as a result, custom character sets can be used with the sun.jdk module.

CLI

977407 - jboss-cli.sh throws IllegalArgumentException when using tab complete

In some situations the jboss-cli tool was exiting when the tab completion feature was triggered by the user. This has been fixed and tab completion now works as expected.
990227 - jboss-cli.sh freeze when run unattended - e.g. from scripts

In previous versions of Red Hat JBoss Enterprise Application Platform, if the server was automated with a script that closed, or set to null, STDIN, the server would exit upon reaching a point where user input was required. In the most recent release of the product, however, this was not the case and the server would hang in that scenario. This release of the product includes an updated verions of Aesh (Another Extendable Shell) that reinstates the original behavior. Servers started with an automated script exit as expected, and no longer hang when requiring user input.
977426 - jboss-cli.sh throws NullPointerException while not connected and in batch mode

Attempting to add a command to a batch with the jboss-cli tool when it was disconnected from the server would cause the jboss-cli to exit. This has been corrected. Attempting to add commands to a batch when disconnected from a server will now result in the following error message being displayed to the user:
Command is not supported or unavailable in the current context: Failed to load operation description: not connected

Clustering

974967 - jvmRoute in standalone.xml can create org.infinispan.marshall.NotSerializableException

When using mod_jk with a load balancer and the sticky session flag to create a farming architecture, distributed applications would fail to deploy because clustering was not enabled. This was because without clustering configuration the LOCAL_ADDRESS of the RegistryService was initialised to a default value which was not serializable. This non-serializable LOCAL_ADDRESS prevented successful deployment in this scenario. Now LOCAL_ADDRESS is initialised to a serializable value and deployment of distributable applications works as expected in this scenario.
918791 - Starting a server with multiple web apps, causes deployment failures

In some cases, web applications on a clustered server would fail to deploy if multiple applications were being deployed. Each application in this situation would attempt to lock the cache manager to create its cache, and the first application that obtained a lock would deploy successfully. However, depending on the time taken to deploy, any other deployments could timeout while waiting for access to the cache manager and fail to deploy. JBoss EAP 6 now includes a GlobalComponentRegistryService which handles this scenario and applications now deploy successfully in this situation.

Domain Management

983980 - EAP6 CLI command should not allow same runtime-name to be used at another deploy

Two deployments with the same runtime name would incorrectly be allowed to be deployed onto the same JBoss EAP 6 instance.

As a result, the instance may enter an inconsistent state in using the runtime name for the wrong deployment.

This issue has been fixed in this release of JBoss EAP 6, and a runtime name is now only allowed to be used once per JBoss EAP 6 instance. If an attempt is made to deploy an application with a runtime name already in use, the following error will be displayed:
There is already a deployment called ${name} with the same runtime name ${runtime-name} on server group ${server-group}
1021763 - Domain controller fails to restart due to an inconsistent rollback of a redeploy

The handler for the full-replace-deployment includes logic that deletes deployment content which has been added as part of an operation which is being rolled back. This logic was not checking whether the added content was the same as the existing content, so that if it was, the existing content would incorrectly be deleted.

As a result of this situation, if the same content is redeployed in a managed domain using the deploy --force CLI command, and if the redeploy failed for any reason (for example, because a depended-upon service such as a datasource is missing on a server), then the deployment would also fail and the content would be removed from all hosts as part of the rollback process. However, the existing configuration item for the deployment would remain, and if the host was restarted, an attempt to deploy non-existent content would be made, resulting in a failure to boot.

This issue has been fixed in this release of JBoss EAP 6. The rollback logic now recognizes that if the content was unchanged, it will not remove the content as part of the rollback process.

As a result, the rollback will leave the domain in a consistent state equivalent to what it was before the redeploy attempt was made, and the content will remain available on all hosts along with the configuration referencing the content.
960820 - Recursive expression resolution

Expressions contained in the output of other expressions were not being resolved. This meant that it was not possible to use expressions in configuration to refer to other expressions, such as one that referred to a vault expression. This occurred because the output of expression resolution was not checked for the existence of further expressions to resolve.

Expression resolution is now recursive. When an expression is resolved, a check is made for any further expressions to resolve in the output. This continues until no further expressions are found.

Expressions can now be used to refer to other expressions in configuration.

EJB

991444 - EJB2 CMP wrong cache access if optimistic-locking=true

When optimistic locking was configured for EJB2 Entity Beans, cached entity beans were never being found in the cache. This occurred because the cache lookup was being performed using the wrong identifier. The entity primary key was being used to locate the correct transaction cache instead of the transaction identifier. This has been corrected and cache access for EJB2 Entity Beans now works as expected when optimistic locking is enabled.
1005110 - ClassLoader memory leak with EJB Asynchronous invocations

In some situations, asynchronous EJB calls could result in the deployment’s classloader being "leaked".

This occurred because the execute method could lead to new thread creation. When this occurs the new thread assigns itself the context classloader of the parent thread, which would be the classloader of the deployment. To prevent this the Thread Context Classloader (TCCL) is set to null before the execute method is invoked, and then restored afterwards.

Asynchronous EJB calls can no longer result in deployment classloader leaks.
1019894 - EJB should not be remotely accessible until all of its dependencies have been started

In some situations EJBs could be remotely invoked before they were fully started, resulting in an unresponsive EJB client. This occurred because remote interfaces were bound before any dependencies of the EJB were fully resolved. Thus a bean could be invoked before it was fully able to respond. This has been fixed and an EJB’s remote interfaces are not available until all of its dependencies have been resolved.
1005093 - Security context associated with EJB asynchronous invocations can potentially be corrupted over time by the caller thread

An EJB that is called asynchronously from a servlet can potentially lose its security context if the servlet invocation completes first. This occurred when security context of the servlet was cleared because both the servlet and the EJB threads share the same SecurityContext instance. Now the SecurityContext attributes are copied from the instance on the servlet thread to a new instance of the SecurityContext object on the EJB thread. Updates to SecurityContext instances on one thread no longer affect instances on other threads as expected.

Hibernate

998841 - Permanent fix of HHH-8447 (HQL delete with multiple subqueries failing (incorrect alias used))

If a HQL delete query contained multiple subqueries, only the first subquery would use the correct root table alias. The generated SQL for the other subqueries would use an incorrect alias.

This issue was caused by improper processing of multiple subqueries when generating the SQL query.

This issue has been fixed in this release of JBoss EAP 6 so that HQL delete queries with multiple subqueries will now use the correct root table alias when generating SQL for all subqueries.
947946 - Incorrect "to_char" function in HSQL dialect

A bug in the HSQL dialect implementation of the to_char function resulted in incorrect conversions of objects to strings, and when used in a comparison would result in a java.lang.IllegalArgumentException exception.

In this release of JBoss EAP 6, the to_char function in the HSQL dialect has been fixed by properly converting objects to a string. As a result, comparisons made using the to_char should no longer throw java.lang.IllegalArgumentException exceptions.
990587 - [HHH-7959] Hibernate/Infinispan 2nd Level Caches set to transaction-mode=NONE stop functioning after an explicit eviction

An Infinispan second-level cache configured with transaction-mode=NONE would be invalidated when programmatically forcing an eviction. This invalid state would result in performance degradation, and TRACE level log messages of Could not invalidate region: null.

This issue was caused by unhandled null values related to attempting to use a TransactionManager in a non-transactional configuration, resulting in NullPointerExceptions.

This issue has been fixed in this release of JBoss EAP 6 so that proper null checks now allow the eviction and valid state to occur. As a result, programmatically forcing an eviction on an Infinispan second-level cache configured with transaction-mode=NONE will no longer trigger an invalid state and associated performance degradation.
1018146 - [HHH-8605] ManyToManyTest.testManyToManyWithFormula fails on mssql2008R2, mssql2012, sybase157

On Sybase and Microsoft SQL Server, HQL queries which had tuples in subqueries would throw exceptions. Neither Sybase nor Microsoft SQL Server support tuples in subqueries, such as the following query:

delete from Table1 where (col1, col2) in (select col1, col2 from Table2)

This issue occurred because the Hibernate dialects for Sybase and Microsoft SQL Server did not configure the supportsTuplesInSubqueries property to false.

In this release of JBoss EAP 6, the Hibernate dialects for Sybase and Microsoft SQL Server have been updated to accurately reflect the lack of support for tuples in subqueries. As a result, warnings are now produced rather than throwing exceptions.
1003468 - HHH-8464 Using JPA2 specific quoting character (double quote) for JoinColumn results in DuplicateMappingException.

Using a JPA2-specific quoting character ( ") for a JoinColumn would result in a DuplicateMappingException. This issue was caused by the quoting character not being normalized internally.

This issue has been fixed in this release so that using " for a JoinColumn is now normalized properly, and will no longer result a DuplicateMappingException.
991578 - HHH-8390 Foreign key reference generated before unique constraint exists

Creating a schema in which a foreign key was declared before it was defined as unique or as a primary key, would fail on Oracle and possibly other dialects.

This issue has been fixed in this release of JBoss EAP 6 by forcing unique key constraints to be created before foreign key constraints as part of the schema export process.

As a result, exported schemas should no longer fail on Oracle because of a foreign key being declared before a unique constraint exists.
977520 - HHH-8318 "delete" with "member of" query fails

An bug in the conversion of HQL delete queries that contained a member of clause would result in incorrect SQL being generated. As a result, the incorrect SQL delete query would fail. This issue was caused by the member of subquery using an incorrect alias.

This issue has been fixed in this release of JBoss EAP 6 by making member of subqueries use the correct alias when used as part of a HQL delete query, and as a result, will now produce correct SQL.

HornetQ

1019378 - Message Redistribution could lead to loss of messages if paging and reading with batched Transactions

In a rare circumstances, if messages were being acknowledged too fast with big chunks on a HornetQ server, a message redistribution could read a record before the transaction was instantiated on the page system. This situation would result in message loss.

This issue has been fixed in this release of JBoss EAP 6 by making sure the paging system will correctly instantiate a page transaction, and only writing the file after the page transaction is instantiated.

As a result of this fix, under the same circumstances there will be no lost messages.
988321 - WARN - Replication Large MessageID 164 is not available on backup server. Ignoring replication message

After a certain sequence of events, a large message deletion may be called twice, resulting in an erroneous warning message on a backup HornetQ server, similar to below:
11:33:23,825 WARN  [org.hornetq.core.server] (Old I/O client worker ([id: 0x2b37b4ea, /192.168.40.1:60844 => /192.168.40.1:5445])) HQ222090: Replication Large MessageID 164  is not available on backup server. Ignoring replication message

This issue was fixed by stopping the erroneous warning from appearing in the JBoss EAP 6 logs. As a result, on a backup HornetQ server there should no longer be erroneous warning messages related to large messages not being available.

Installer

977736 - Appclient starting script and configuration file shouldn't be installed without appclient option selected

When using the installer for JBoss EAP 6, if the AppClient+ check box on the Pack Installation screen was cleared, AppClient files would still be installed.

This issue with the installer has been fixed in this release of JBoss EAP 6 so that AppClient files will only be installed if the AppClient+ check box is selected.
1013973 - Installer: Cannot use Ctrl+c to quit installation (windows)

An issue with specifying a JLine dependency resulted in the Ctrl-C keyboard command not functioning in the console installer of JBoss EAP 6 on Microsoft Windows Server.

In this release of JBoss EAP 6, JLine has been updated so that when Ctrl-C is entered during a console installation on Microsoft Windows Server, the installer now quits as expected. Also note that the Insert key is read as the same character as Ctrl-C, and will also quit the console installer if pressed.
1013972 - Tab Extends for auto-completing home directory path is not working correctly

In the console installer for JBoss EAP 6, using the Tab key to autocomplete home directory paths would not work as expected. Instead of autocompleting the home directory paths, on Microsoft Windows Server nothing was shown, and on Linux /home was incorrectly inserted.

This issue has been fixed in this release of JBoss EAP 6, so that when entering ~ and pressing Tab, the home directory path is autocompleted as expected. On Microsoft Windows Server the path is C:\Users\USERNAME, and on Linux it is /home/USER.
963304 - Native components check box is invisible when installing EAP 6.0.0 through jar installer

On Unix-derived operating systems the installer did not properly check the system-release file if there was more than one *-release file present in the /etc/ directory. This resulted in the installer not recognizing the server operating system, and consequently did not show the Native Components check box on the Pack Installation screen. This issue has been fixed in this release of JBoss EAP 6, and the installer now properly checks the system-release file on Unix-derived operating systems. As a result, the Native Components check box on the Pack Installation screen is shown as expected.

JCA

952277 - disable xa-data-source causes that data-source loses its attribute enabled set to false and after reload it becomes enabled

When an XA data source was set to disabled, and the data source was already disabled, the data source was enabled on the next restart. The cause of this issue has now been resolved. In the same circumstances, the data source now remains disabled.
1007608 - Memory leak if hashCode of Transaction isn't stable

The JCA TransactionSynchronizer was found to leak memory if the Transaction hashCode was not stable. This memory leak could cause OutOfMemoryErrors after a period of time.

An update to the JCA component has corrected this potential lead and the associated OutOfMemoryErrors no longer present.

JSF

991276 - WAR_BUNDLE_JSF_IMPL does not work inside an EAR

If a JSF implementation was packaged in a WAR, WAR_BUNDLE_JSF_IMPL could be used to allow it to work rather than the container’s implementation. This option was not working if it was instead packaged in an EAR. The cause of this issue was that only the (sub-)deployment was checked for the JSF marker, causing it not to be found when it was in a distinct top-level deployment (EAR). To resolve this issue, an additional check has been implemented to check the top-level deployment for the JSF marker.

Maven Repository

1011918 - Unable to get dependencies for jbossws-cxf-client -- Failure to find org.apache.ws.security:wss4j:jar:1.6.11-redhat-1

The build process was changed in this release of JBoss EAP to provide more conventional Maven POM files which are more consistent with community Maven POMs. The POM files in the EAP Maven repository now have dependencies on some community artifact versions.

Users should refer to the JBoss Enterprise Application Platform Developer Guide for information on how to configure the appropriate Maven BOM file. Configuring the appropriate Maven BOM file will ensure that the user build includes the correct transitive dependency version (the JBoss EAP version will be used for supported artifacts and the community version for unsupported artifacts).

Other

985204 - Socket not closed when web executor drops task

This release of JBoss EAP corrects a bug which caused web connector sockets to not be closed properly when tasks were dropped by the executor. The cause was traced to the QueueExecutor class not throwing a RejectedExecutionException when there was no handoffExecutor set (as QueuelessExecutor does). In these cases the task would be dropped, which was not the expected behavior. The QueueExecutor class has been updated to throw the required exception when a task cannot be added to the queue and, as a result, sockets are now closed correctly.
901210 - Cleanup deploy directories - AS7-6031

This release of JBoss EAP 6.2 includes a fix that ensures files and directories created in the JBOSS_HOME/tmp and JBOSS_HOME/tmp/vfs folders are removed before they can interfere with newly (re)started EAP instances.

In previous versions of JBoss EAP, older files may have been left behind after a server is shutdown unexpectedly (as JBoss EAP removes files in JBOSS_HOME/tmp and JBOSS_HOME/tmp/vfs as part of the shutdown process).

The fix in this release provides a failsafe to mitigate that scenario. If a JBoss EAP 6.2 server does not shut down gracefully the server will not have an opportunity to clean up these temporary files. Upon restart however, the server now queries the above locations and, if files from a previous instance are present, it initiates a rename/remove process that allows the creation of fresh files for the new instance (the old directories are renamed so as to avoid interfering with newly created files). These processes happen in parallel.

Upon restarting JBoss EAP (either gracefully or otherwise) old temporary files are now removed (either at shutdown or restart), to ensure they do not take up unnecessary disk space.

NOTE Users should avoid using the -Xrs JAVA_OPT as this limits signals processing and can result in the size of the tmp/vfs directories continuing to grow.

PicketLink

977761 - PLINK2-25 characterEncoding parameter not used in for Post Requests in ServiceProviderAuthenticator

A timing issue was found in Picketlink which resulted in parameters being read from post requests in the ServiceProviderAuthenticator using the default encoding instead of the desired encoding. The issue was caused when PicketLink read its parameters before the Tomcat valve had set the encoding. To resolve this issue the encoding has been moved so that it is the very first step in the authenticate method.

Remoting

1025319 - Trouble with EJB invocation from a server with/without SSL

When creating an outbound remote connection, the service that creates the connection would apply the default settings after applying user-defined configuration settings. This resulted in the default settings incorrectly overriding any user-defined settings that had the same key.

As a result of this situation, SSL could not be disabled on remote EJB connections which originated from the server.

This issue has been fixed in this release of JBoss EAP 6. User-defined settings are now applied after the default settings, which ensures that user-defined settings take precedence.

As a result, SSL can now be disabled on outbound remote connections.
1025185 - Remoting subsystem: Concurrent modification exception during server shutdown

A service in the remoting subsystem would iterate over a collection in a non-thread-safe manner.

As a result of this issue, a ConcurrentModificationException exception would occasionally be thrown during server shutdown. Other than this exception, the shutdown would complete normally.
WARN  [org.jboss.msc.service.fail] (MSC service thread 1-55) MSC000004: Failure during stop of service jboss.remoting.endpoint.management.channel.management: java.util.ConcurrentModificationException
	at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793) [rt.jar:1.6.0_45]
	at java.util.HashMap$KeyIterator.next(HashMap.java:828) [rt.jar:1.6.0_45]
	at java.util.AbstractCollection.addAll(AbstractCollection.java:305) [rt.jar:1.6.0_45]
	at java.util.HashSet.<init>(HashSet.java:100) [rt.jar:1.6.0_45]
	at org.jboss.as.remoting.AbstractChannelOpenListenerService.stop(AbstractChannelOpenListenerService.java:123)
...

This issue has been fixed in this release of JBoss EAP 6. Iteration over the collection is now done in a thread-safe manner, with the collection object’s monitor held by the iterating thread.

As a result, ConcurrentModificationException exceptions are no longer thrown.

RPMs

998319 - RPMs put important data in /var/tmp

RPMs put important data in /var/tmp, including /domain/data. /var/tmp is meant to contain temporary data which could be removed at any time. /domain/data should not be redirected to /var/tmp/ since it contains important data that should not be lost, including the transaction recovery journal and HornetQ large message store and journal.

This error has been fixed for this release of JBoss EAP 6. For new installations, /usr/share/jbossas/domain/data will be a directory instead of a link.

However, for existing installations, one of the following must be performed:
  • Re-install and migrate the config and data files (including the temp directories) to the new installation directories, or
  • Uninstall tmpwatch to disable clean up of /var/tmp/jbossas, or
  • Configure tmpwatch not to remove the files that jbossas puts in to /var/tmp/jbossas.

Scripts and Commands

998913 - standalone.bat still sets -XX:+TieredCompilation JVM option

An issue has been resolved in the standalone.bat batch file, used on Microsoft Windows Server. The batch file previously contained a JVM option which set tiered compilation: -XX:+TieredCompilation. This setting has been removed as it is known to cause performance problems in some circumstances.
916960 - Standalone.bat does not work if parentheses are on path to EAP.

In previous releases of JBoss EAP, batch files provided - e.g. standalone.bat and add-user.bat failed to work as expected on Microsoft Windows Server if the path in which they were stored contained parentheses or spaces. The batch files have been improved by use of quotation characters to ensure that the full path is evaluated. As a result, the batch files now works as expected with paths including parentheses and spaces.

Security

920160 - Unauthorized access to a web application protected with a custom authorization module results in HTTP 200 (OK) instead of HTTP 403 (Forbidden)

In JBoss EAP 6.1.0, unauthorized access to a web application protected with a custom authorization module resulted in an HTTP response of 200 (OK) instead of HTTP 403 (Forbidden). This issue has been resolved and the correct response is now provided.

Server

1022223 - Deployment descriptor overlays do not override JSPs

Deployment descriptor overlays should allow an administrator to override a JSP in a deployment. However the overlay functionality did not work because JBoss Web does not use VFS for serving content, and so the JSP files were not visible. An additional test of the deployment method has been added and the overriding of deployment descriptors now works as expected.

Transaction Manager

1016120 - Transaction JDBC object store does not start on PostgreSQL Plus 9.2

The JBoss Transaction Manager did not have a properly configured driver class for PostgreSQL Plus 9.2. This resulted in a ClassNotFoundException exception when attempting to use a JDBC transaction object store on PostgreSQL Plus 9.2.

In this release of JBoss EAP 6, the JBoss Transaction Manager as been updated with a PostgreSQL Plus 9.2 driver class ( jdbc.drivers.postgres_driver), and JDBC object stores can now be used with PostgreSQL Plus 9.2 servers.

Web

997009 - requiredSecret attribute on the AJP connector

When using a load balancing Apache server in front of JBoss EAP 5.x, you can set the "requiredSecret" attribute of the AJP connector. This is used to only allow requests from load-balancer workers with the same secret keyword, to be accepted.

In JBoss EAP 6.0.x and 6.1.x it was not possible to configure this value. This issue has now resolved and you can now set a system property to your required value for the "requiredSecret" attribute:
org.apache.coyote.ajp.DEFAULT_REQUIRED_SECRET=yoursecretvalue
996558 - Https connection hangs after adding https connector

When adding an HTTPS connector via the management CLI, any attempted connection would hang, despite each command completing successful. The cause of the issue was that the connector was started as soon as it was created, yet its configuration was incomplete, preventing the connector working as expected. A workaround in this instance was to wrap the configuration commands in a batch, end-batch sequence, so that all configuration statements were completed together. The root cause of this issue has been resolved and access to a HTTP connector is successful, whether or not the configuration statements are completed in sequence or as a management CLI batch.

Web Console

947913 - Admin Console: The Resource Adapter Properties becomes editable clicking in the configured Resource Adapters.

When viewing the properties of a resource adapter (RA) in the web management console, it was possible that the adapter’s properties became editable fields, allowing existing fields to be changed or deleted, and new fields added. These fields should have been presented as read-only fields, since there is no functionality for editing them in the web management console. If any such field was edited, the edited values would remain in their edited form, yet not be stored in the resource adapter’s configuration file. This issue was now been resolved and the properties of all resource adapters now remain presented as read-only fields.
900063 - Missing error message when creation of Custom Handler fails

In previous JBoss EAP 6 releases, when the creation of a custom logging handler in the web management console failed, no feedback was given to the user. As a result, the user might reasonably assume that the custom logging handler was created. To resolve this issue, an error message now appears in these circumstances, making it clear to the user that the creation failed.
1012539 - "Started?" field in messaging bridge settings in incorrect

The runtime information field Started? has been removed from the Profile → Messaging → Connections → Bridges screen in this release of JBoss EAP 6.

This was because the field was found to sometimes display incorrect information and, since it was not editable, provided no functionality to users.
996889 - Unable to change port offset for servers in domain

When changing the port offset for servers in a domain, the action failed with the resulting message: "Internal server error". The underlying cause was that the value of socket-binding-group on the server-config resource was undefined, so the attempt to change the server configuration, no value was pre-selected in the Socket binding select box. Consequently the first part of composite operation failed. The root cause has now been resolved and the port offset for servers in a domain can now be set in the web management console.

Web Services

1026992 - Picketlink STS doesn't work with CXF update

The fix applied to JBoss EAP to address CVE-2013-2133 implies authorization checks by the container before running JAXWS handlers attached to EJB3 based WS endpoints. As a consequence, some PicketLink usage scenario can be affected, as the PicketLink SAML2Handler is meant for establishing the security principal that will later used.

Customers can disable the additional authorization checks and keep on using the existing PicketLink deployments either by setting the org.jboss.ws.cxf.disableHandlerAuthChecks system property to true or by specifying the org.jboss.ws.cxf.disableHandlerAuthChecks property in a jboss-webservices.xml descriptor as follows:
<?xml version="1.1" encoding="UTF-8"?>
<webservices xmlns="http://www.jboss.com/xml/ns/javaee"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  version="1.2" xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee">

  <property>
    <name>org.jboss.ws.cxf.disableHandlerAuthChecks</name>
    <value>true</value>
  </property>
</webservices>

The descriptor is to be placed in META-INF within the customer deployment for which the handler authorization checks are to be disabled.

The system property setup will affect any deployment on the server, instead.

Note that enabling the org.jboss.ws.cxf.disableHandlerAuthChecks property renders a system vulnerable to CVE-2013-2133. If the application expects security restrictions declared on EJB methods to be applied and does not apply them independent to the JAX-WS handler, then the property should not be enabled. The property should only be used for backwards-compatibility purposes when needed to avoid application breakage.
988318 - CLI - after undefine operation on wsdl-host attribute of webservices subsystem and reload war with webservice can not be deployed

A bug that caused application deployments to fail when the wsdl-host attribute was undefined has been corrected in this release of JBoss EAP 6.
999223 - wsconsume.sh fails with the default target version - 2.2

In previous versions of JBoss EAP, it was found that WSConsume failed to compile JAXWS 2.2 level sources when OpenJDK version 1.6 was used.

This has been resolved in this release.

Weld

956631 - CLONE - Cross-context forward/include call from another web app breaks HttpRequestContext cleanup

For forwarded requests, WeldListener would clean-up a bound context request when the servlet that was processing it finished, even though it was being sent to another servlet.

As a result, when the other servlet would try to access the context, it would produce a NullPointerException.

This issue has been fixed in this release of JBoss EAP 6 by not cleaning up a bound context if the servlet is being redirected.

As a result, using getRequestDispatcher().include() to forward requests between servlets should no longer produce exceptions related to incorrect WeldListener clean-ups.
910185 - Weld's TypeSafeObserverResolver cache is unbounded

The Weld class TypeSafeObserverResolver used by TransactionalObserverNotifier does not have any configuration options for limiting or expiring entries. Usually the number of CDI qualifiers is small, but this may not be true if an application uses AnnotationLiteral-derived classes with arbitrary data in the annotation.

As a result, the TypeSafeObserverResolver cache could grow very large and cause an OutOfMemoryError if a large number of distinct qualifiers are used.

This issue has been fixed in this release of JBoss EAP 6 by implementing a configurable upper boundary for the resolved cache in TypeSafeObserverResolver.

Users can configure the org.jboss.weld.resolution.cacheSize property to limit the maximum number of resolved cache entries. The default value of the maximum boundary is 1048576 cache entries.

Web Services

969924 - Picketlink STS doesn't work with CXF update

The fix applied to JBoss EAP to address CVE-2013-2133 implies authorization checks by the container before running JAXWS handlers attached to EJB3 based WS endpoints. As a consequence, some PicketLink usage scenario can be affected, as the PicketLink SAML2Handler is meant for establishing the security principal that will later used.

Customers can disable the additional authorization checks and keep on using the existing PicketLink deployments either by setting the org.jboss.ws.cxf.disableHandlerAuthChecks system property to true or by specifying the org.jboss.ws.cxf.disableHandlerAuthChecks property in a jboss-webservices.xml descriptor as follows:
  <?xml version="1.1" encoding="UTF-8"?>
  <webservices xmlns="http://www.jboss.com/xml/ns/javaee"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    version="1.2" xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee">

    <property>
      <name>org.jboss.ws.cxf.disableHandlerAuthChecks</name>
      <value>true</value>
    </property>

  </webservices>

The descriptor is to be placed in `META-INF` within the customer deployment for which the handler authorization checks are to be disabled. The system property setup will affect any deployment on the server, instead. Note that enabling the `org.jboss.ws.cxf.disableHandlerAuthChecks` property renders a system vulnerable to CVE-2013-2133. If the application expects security restrictions declared on EJB methods to be applied and does not apply them independent to the JAX-WS handler, then the property should not be enabled. The property should only be used for backwards-compatibility purposes when needed to avoid application breakage.

mod_cluster

958991 - mod_cluster core when use ProxyPass / balancer://bal and CreateBalancers 1

A regression found in versions 6.1.0 and 6.1.1 of JBoss EAP caused setting CreateBalancers 1 in /conf.d/mod_cluster.conf without setting the stickysession=JSESSIONID|jsessionid configuration to result in a segmentation fault. This issue has been resolved in JBoss EAP 6.2. The stickysession element has now been added to the CreateBalancers configuration.
960243 - Regression in ProxyPass integration

A regression in an earlier version of mod_proxy_cluster.so (bug 960246) returned HTTP 503 errors when accessing a directory (for example <filename class="directory">/app/clusterbench/requestinfo/</filename>. This issue has been corrected in this release of JBoss EAP and mod_proxy_cluster.so now works as expected when accessing directories.
963720 - mod_cluster: proxy DNS lookup failure with IPv6 on Solaris

In previous versions of EAP 6 it was found that attempting to use IPv6 addresses within a Solaris system would result in a DNS lookup failure.

The source of this issue was traced to the IPv6 zone-id string of IPv6 adresses.

Since this information is of no use to the HTTPD, the string is no longer used and mod_cluster now operates as expected on Solaris systems.

7.2. Enhancements

Domain Management

978984 - Update the add-user utility to allow for file name overrides.

The add user script ( adduser.sh and adduser.bat) has been enhanced to allow different properties files to be specified for both users and groups.

The user file can be specified with the -up or --user-properties parameters.

The group file can be specified with the -gp or --group-properties parameters.

Example Usage:
[admin@server bin]$ ./add-user.sh -up audit-users.properties -gp audit-groups.properties

Note

The add-user command is intended to operate on existing properties files. Any alternate properties files specified in command line arguments must exist or the following error will occur: "JBAS015234: No audit-users.properties files found"

EJB

981341 - Add CLI operations to start/stop MDB delivery

This release of JBoss EAP 6 includes a new DeliveryActive activation configuration property that is used only for the Message Driven Beans (MDB) component to activate or deactivate message delivery.

The management operations :start-delivery and :stop-delivery (and the read-only delivery-active runtime attribute) can now be used to start and stop delivery on the MDB resource (under /deployment=deployment_name/subsystem=ejb3/message-driven-bean=mdb_name).

By default, the new property is activated and delivery of messages occurs as soon as the MDB is deployed.

Hibernate

952284 - Hibernate SchemaValidation on synonyms

JBoss EAP 6 has been enhanced by providing the ability for Hibernate entities to be validated against table synonyms. Previously, the schema validation would only validate tables and views.

To enable this new functionality, the hibernate.synonyms=true property must be set.

For example, the following will now pass Hibernate schema validation:
"CREATE SYNONYM foo_synonym FOR foo_table"

@Table(name = "foo_synonym")

Installer

1013954 - Installer: Add ability to change management ports for domain

The JBoss EAP 6 installer has been updated to allow the configuration of management ports for domain mode servers. Previously, the installer could configure management ports for a standalone server, however management ports for a domain server had to be manually configured after installation via configuration files.

This installer enhancement allows management ports for domain servers to be configured at installation, without having to manually configure them later.
900724 - Make the installer accept automation config files from different sources

The JBoss EAP 6 installer now accepts an automation configuration file from a network location.

Previously, an automation configuration file had to be on the same machine on which the installer was being run.

The automation configuration file can be specified to a network location using http or ftp with the following syntax:

java -jar installer.jar http://network-host/automation.xml or java -jar installer.jar ftp://network-host/automation.xml
1006548 - Installer: Create infinispan cache

The JBoss EAP 6 installer has been updated to provide the ability to configure an Infinispan cache.

Previously, Infinispan cache configuration would have to be done manually after JBoss EAP 6 had been installed.

As a result of this enhancement, Infinispan cache configuration can now be done at installation, without needing to manually configure it later.
1006532 - Installer: JDBC driver installer feature

The JBoss EAP 6 installer has been enhanced to provide the ability to install JDBC drivers. JDBC drivers than can be installed using this feature include:
  • IBM DB2
  • Microsoft SQL Server
  • MySQL
  • Oracle
  • PostgreSQL
  • Sybase

Previously, JDBC drivers would have to be installed manually after JBoss EAP 6 had been installed.

As a result of this enhancement, JDBC drivers can now be installed during the JBoss EAP 6 installation, eliminating the need to manually install them later.
1006533 - Installer: Add security-domain configuration

The JBoss EAP 6 installer has been enhanced to provide the ability to configure a security domain.

Previously, security domains would have to be configured manually after JBoss EAP 6 had been installed.

As a result of this enhancement, a security domain can now be configured at installation, without the need to manually configure it later.
1006535 - Installer: Add password vault configuration

The JBoss EAP 6 installer has been enhanced to provide the ability to configure a password vault.

Previously, a password vault would have to be configured manually after JBoss EAP 6 had been installed.

As a result of this enhancement, a password vault can now be configured at installation, without the need to manually configure it later.
1006540 - Installer: Enable LDAP authentication

The JBoss EAP 6 installer has been enhanced to provide the ability to configure LDAP authentication on management interfaces.

Previously, LDAP authentication would have to be configured manually after JBoss EAP 6 had been installed.

As a result of this enhancement, LDAP authentication on management interfaces can now be configured at installation, without the need to manually configure it later.
901180 - Installer: Add SSL keystore to management interface

The installer for JBoss EAP 6 has been enhanced to provide the ability to configure an SSL keystore for securing management interfaces.

Previously, SSL configuration for management interfaces would have to be done manually after installation.

As a result of this enhancement, SSL keystore configuration for management interfaces can now be configured at installation, without the need to manually configure it later.

Scripts and Commands

732889 - Instructions for installing JBoss as Windows service do not work

The service.bat batch file for managing JBoss EAP installed as a service on Microsoft Windows Server has been upgraded, with improved error checking. The added checks are aimed at testing for conditions which would prevent the service running as expected.

Web Console

990879 - Administration Console contains community branding

In JBoss EAP 6.1.1 the web management console displayed a favicon of AS7, not the Red Hat logo. This has now been resolved and the correct favicon now appears when in the web management console.

Web Services

999570 - Client side CXF bus incorrectly caches service endpoint information

This version of JBoss EAP 6 includes new functionality that allows users to create a JAXWS client within a new Bus, whose WSDL definition cache would be empty.

As WSDL definitions are cached within the Apache CXF Bus that is used for serving the JAXWS client being created, a stale definition could be used if a different WSDL is served at the specified URL and the same Bus is in use. This enhancement provides a means to avoid that scenario.

The new functionality is used as follows through the new org.jboss.wsf.stack.cxf.client.UseNewBusFeature JBossWS JAXWS Feature: Service service = Service.create(new URL(wsdlLocation), new QName(…), new org.jboss.wsf.stack.cxf.client.UseNewBusFeature());

JMS

1011074 - Change value for address-full-policy from BLOCK to PAGE on the distributed configurations

In previous versions of JBoss EAP, the JMS configuration property address-full-policy was set to BLOCK in the product’s configuration, meaning that once the maximum configured capacity for messages to a given address was reached, producers would be prevented from sending any further messages to that address.

This behaviour has been modified to conform more closely with customer expectations. The new default setting is PAGE, which pages messages received while the consumer is over the maximum capacity to disk. These messages will occupy disk space if they are not consumed.

This behaviour can be modified by setting the address-policy-full configuration back to BLOCK (or, additionally DROP or FAIL) if required.

Logging

999665 - [ERD] EAP62_1120 [RFE] New log file on restart

The SizeRotationFileHandler has a new attribute RotateOnBoot that will cause the file handler to create a new file on server restart.

7.3. Known Issues

CLI

1031173 - jboss-cli.bat does not work when EAP installed into directory with spaces

The jboss-cli tool will not launch successfully on the Microsoft Windows Server operating system if JBoss EAP is installed in a directory that has spaces or other special characters such as parentheses in its path. The following error message is the outcome if JBoss EAP is installed in the directory C:\JBoss EAP\jboss-eap-6.2:
Error: Could not find or load main class EAP\jboss-eap-6.2\bin\jboss-cli-logging.properties

This can be worked around by editing the jboss-cli.bat file and editing line 62 of jboss-cli.bat to move the first " character from the beginning of JAVA_OPTS to after the assignment so it looks like the following.
set JAVA_OPTS="%JAVA_OPTS% -Djboss.modules.system.pkgs=com.sun.java.swing -Dlogging.configuration=file:%JBOSS_HOME%\bin\jboss-cli-logging.properties"

This error can also be avoided by not installing JBoss EAP 6 in a directory with spaces or parentheses in its name.

This will be fixed in a future release.
1019232 - jboss-cli.sh throws NullPointerException when using tab complete on data-source node

The jboss-cli tool will throw an exception and exit when the user attempts to use the tab completion feature in some circumstances. One noted case is when using the built-in data-source operation as follows: data-source --name=ExampleDS a and then pressing the TAB key. This is due to inadequate exception handling in the command parser for these situations and will be fixed in the next release.
988283 - CLI GUI - write attribute dialog for string value should enclose value in generated command to double quotes

Attempting to set a value using the jboss-cli tool that contains a property will only save the character $ in the value instead of the property unless the entire value is contained in double-quotes. This is due because the CLI command line parser will incorrectly parse any ${X} expression as only $ unless it is contained in double-quotes.

As a workaround ensure that values that contain expressions are enclosed in double-quotes, e.g:
[standalone@localhost:9999 subsystem=webservices] :write-attribute(name=wsdl-host, value="${jboss.bind.address:127.0.0.1}")

Beware that commands generated by jboss-cli in GUI mode do not automatically include the quotes.

Clustering

900378 - CDI beans with SET replication trigger are not replicating

Due to a bug in the Weld component, the setAttribute method is not called correctly. This causes CDI beans with the SET replication trigger to fail to be replicated. The workaround is to use the SET_AND_NON_PRIMITIVE_GET trigger for these beans. This will be fixed in a future release.
900483 - Stale session data received when using DIST SYNC on node shutdown

During testing, some cases showed that stale session data was received when a node shut down and DIST SYNC or DIST ASYNC cache mode was used. This issue is still under investigation.

Documentation

1026813 - Describe implementation details of behaviour of servlet startup init method with exception

The behaviour of the server when exceptions are thrown by servlets in their init() method or by ServletContextListener.contextInitialized is not defined by the Servlet specification and the JBoss EAP Developer Guide does not provide an explanation of JBoss EAP 6 behaves in this situation.

The behaviour of JBoss EAP 6 in these situations can be summarized as follows:
  • If an exception is thrown by the servlet init() method, then the application will still be deployed but the servlet will not be available.
  • If an exception is thrown by ServletContextListener.contextInitialized then the deployment will fail.

A future version of the JBoss EAP Developer Guide will provide more details.
1021607 - RBAC: Explain the two kinds of non-addressability that we have

Some resources are non-addressable to server-group and host scoped roles in order to provide a simplified view of the management model to improve usability. This is distinct from resources that are non-addressable to protect sensitive data.

For server-group scoped roles this means that resources in the `profile`, `socket binding group`, `deployment`, `deployment override`, `server group`, `server config` and `server` portions of the management model will not be visible if they are not related to the server-groups specified for the role.

For host-scoped roles this means that resources in the `/host=*` portion of the management model will not be visible if they are not related to the server groups specified for the role.

However in some cases this simplified view can hide information that while it is outside the scope of what the user is managing, it can provide guidance to the user as to a course of action. An example of this is http://bugzilla.redhat.com/show_bug.cgi?id=1015524.

In a future release, some of these non-addressable resources might be changed to be addressable but non-readable. This will not affect the security of the server because they were not non-addressable for security reasons. Red Hat recommends that you do not rely on the non-addressability of resources to hide information unless the non-addressability is defined in a sensitivity constraint.

Domain Management

1015524 - RBAC: unable to deploy the same deployment which was already deployed by user from different server-group scope

When role-based access controls are enabled, management users with server-group scoped roles might have new deployments fail with the following message:
"JBAS014807: Management resource '[(\"deployment\" => \"example.war\")]' not found"

This occurs because a deployment with the same name already exists in the domain. This is correct behaviour. However because the management user is scoped to a server group, they will be unable to see if such a deployment already exists in another server group. This makes it difficult to avoid this confusing error.

To workaround this limitation, Red Hat recommends that either non-scoped roles are assigned to the users responsible for adding deployments to a domain, or that a list of deployment names is maintained so that management users are aware of them.
1034700 - whoami operation doesn't work with security manager enabled

The :whoami operation does not run correctly when JBoss EAP 6 is running with the Java Security Manager enabled. Attempting to run this operation in this situation results in an exception being thrown of type IllegalArgumentException.
1035231 - RBAC: access control doesn't work with security manager

When JBoss EAP 6 is run with the Java Security Manager enabled, the Role-Based Access-Control system is effectively disabled because in this situation all authenticated users are treated as SuperUsers. The only way to use Role-Based Access-Control currently is without the Java Security Manager enabled.
1035232 - EAP Domain mode is not working properly with Security manager

Servers in a managed domain will not launch successfully if they are configured to use a Java Security Manager without specifying the classname of the Security Manager. This is commonly done when using the default Security Manager by specifying -Djava.security.manager in either domain.conf or as a command line parameter.

In this situation servers will fail to launch with the following message:
                    Error occurred during initialization of VM java.lang.InternalError: Could not create SecurityManager: true

This occurs because a system property without a value is passed by Host Controllers to their managed servers with the value of true. This means that the servers will attempt to use a Java Security Manager with the classname of true. To avoid this, explicitly define the classname of the default Security Manager in the configuration as follows:
                    -Djava.security.manager=java.lang.SecurityManager
1021607 - RBAC: Explain the two kinds of non-addressability that we have

Some resources are non-addressable to server-group and host scoped roles in order to provide a simplified view of the management model to improve usability. This is distinct from resources that are non-addressable to protect sensitive data.

For server-group scoped roles this means that resources in the profile, socket binding group, deployment, deployment override, server group, server config and server portions of the management model will not be visible if they are not related to the server-groups specified for the role.

For host-scoped roles this means that resources in the /host=* portion of the management model will not be visible if they are not related to the server groups specified for the role.

However in some cases this simplified view can hide information that while it is outside the scope of what the user is managing, it can provide guidance to the user as to a course of action. An example of this is 1015524.

In a future release, some of these non-addressable resources might be changed to be addressable but non-readable. This will not affect the security of the server because they were not non-addressable for security reasons. Red Hat recommends that you do not rely on the non-addressability of resources to hide information unless the non-addressability is defined in a sensitivity constraint.
1024109 - NPE in DelegatingServerInventory

Management requests sent to a Host Controller immediately after the Host Controller launches may fail with an exception of type NullPointerException. This is because there is a period of time between when the Host Controller becomes able to receive requests and when the server management system is fully started. This period of time is usually less than one second, but any requests received in that time will fail.

This should only occur in automated environments, such as a script that starts the Host Controller and then immediately attempts to invoke a management operation on one of its servers.

Currently, Red Hat recommends the following workaround for scripts or any other automation that attempts to perform management operations immediately after launching a Host Controller:
  1. Include a slight delay (one or two seconds) to allow enough time for all of a Host Controller's systems to start.
  2. Include error handling logic.
  3. Use polling logic to account for changing request results as a server launches.

This will be fixed in a future release.

EJB

1019372 - Cluster node selection process do not respect whether the nodes are able to handle the EJB request

When a cluster did not have the same EJBs deployed on each node, client EJB invocations were sometimes routed to cluster nodes that did not have the EJBs deployed. This occurred because ejb-client did not confirm that a destination node was able to handle the invocation before sending the request. ejb-client now performs this confirmation and invocations are routed to the correct nodes as expected.
1017673 - ConcurrentModificationException in TimerService.getTimers()

If a bean attempts to create a new timer at the same time as another thread is calling the getTimers() method, an exception of ConcurrentModificationException is thrown. This occurs because the getTimers() method does not call synchronized() on the timers. This will be fixed in the next release.

Hibernate

900321 - HHH-7287 Problem in caching proper natural-id-values when obtaining result by naturalIdQuery using NaturalIdLoadAccess

The Hibernate interface NaturalIdLoadAccess behaves inconsistently when trying to load entities from the Level Two (L2) Cache following an update of their natural-id values from a non-transactional scenario.

Hibernate currently does not support proper L2 caching of entities with natural identifiers in scenarios where there is a mix of transactional and non-transactional access to the database.

Installer

1032892 - Unable to use tab filling for path starting with a drive letter on windows.

In the console installer of JBoss EAP 6 on Microsoft Windows Server, tab completion for directory paths which start with a drive letter is not working.

When entering a path which starts with a drive letter, for example C:\, and pressing the Tab key, nothing is shown. In this situation, it is expected that it will show the contents of that directory.

This issue will be fixed in a future release.
977805 - Starting JBoss Administration Console from start menu is not working on Solaris

The start menu shortcuts for the Administration Console on Solaris do not work for a JBoss EAP 6 instance that has been installed using the installer.

Instead of opening the Administration Console in a web browser, the following error message is displayed:
Error showing url: HTTP Error: Method Not Allowed

This issue is caused by the xdg-open command not functioning as expected on Solaris.

As a workaround to using the start menu shortcuts, the Administration Console can be accessed directly in a web browser. If configured with the default ports, the URLs for the Administration Console are below: For standalone mode: http://localhost:8080/console For domain mode: http://localhost:9990/console

JCA

1033008 - Generic JMS RA is not consistent with the EE spec - it does *not* ignore the parameters when session is created in the transaction context

When a session is created in a transaction’s context and parameters are passed to the generic JMS resource adapter, a Null Pointer Exception (NPE) occurs. The issue occurs because the processing of parameters is atempted, when the Java EE specification states that they are not to be processed. The root cause of the issue is under investigation, but until then a workaround is to set the session to be transacted, as per the following example. With this workaround, the NPE will not occur.
connection.createSession(true, Session.SESSION_TRANSACTED);
1023193 - JMS generic RA shows 'lock owned during cleanup' warning during periodic crash recovery

A minor issue with periodic recovery has been identified, where warning messages beginning with the following text are logged.
WARN  [org.jboss.resource.adapter.jms.JmsManagedConnection] (Periodic Recovery) Lock owned during cleanup: java.lang.Throwable: Lock owned during cleanup

The underlying cause of the issue is that the generic JMS adapter mishandles the second periodic recovery call. In accordance with the Object Transaction Service specification, when the transaction manager is set to be run on the Java Transaction Service (JTS) the periodic recovery calls rollback for the same XID twice. The issue is that the generic JMS adapter incorrectly handles the second call of the rollback for the same XID and the above warnings are logged. Note that despite the warning messages, recovery occurs correctly.
991389 - Connection factory isn't activated in generic-jms-ra.rar resource adapter after server reload with jts transactions mode set.

When a JBoss EAP server is configured with a resource adapter deployed using generic-jms-ra.rar, the connection factory is deregistered when the server is reloaded. The cause of the issue is that the generic resource adapter does not correctly handle the reload if the transaction subsystem is configured to run on the JBoss Transactions System (JTS). The root cause of this issue is being investigated.

A workaround is to add a JCA descriptor XML file to the RAR archive with the connection properties specified.

JSF

1029387 - WFLY-2493 EL cannot access public methods/fields of non-public classes

When trying to access the public method or field of a non-public class via EL the following error message results:
"java.lang.IllegalAccessException: Class javax.el.BeanELResolver can not access a member of class X with modifiers "private"

This issue has been resolved via a workaround, in which etAccessible(true) on the method before invoking it, thus suppress Java access checking.
1017242 - FacesMessages doesn't work properly in root context application

There is a known issue with the JSF component shipped in JBoss EAP 6.2. It has been reported that FaceMessages are not being reliably redirected when running an application in root context. This issue will be addressed in a future release of the product.

Other

901231 - Usage of finalize() needs extra guards on IBM JDK

JBoss Enterprise Application Platform 6 can experience intermittent failures when running on the IBM JDK 6 and 7. This is because the IBM garbage collector is much more aggressive than that of other JVMs. This can sometimes result in memory being reclaimed in situations that were unanticipated and did not manifest when testing on other JVMs.

Until this issue is resolved Red Hat recommends not using the IBM JDK 6 or 7 to run JBoss Enterprise Application Platform 6.

Scripts and Commands

956281 - Starting EAP 6.1 on windows with 32bit jvm can result in failure to start JVM

On Windows 8 32-bit JVMs, the default max perm gen space setting causes the JVM to not be created, which then prevents the server from starting. To work around this issue, remove the -XX:MaxPermSize=256m parameter from the startup parameters of the JVM. This will allow the JVM to be created and the server to start.

Security

979369 - Different behaviours of HttpSession creation with programmatic login()

It has been discovered that the behavior of HttpSession creation differs when used together with a programmatic login:
  • without SSO: Session is not created while calling login() method - i.e. subsequent requests are unauthenticated;
  • with non-clustered SSO: Session IS created while calling login() method, but the first call doesn’t set the authentication status there - i.e. subsequent requests are unauthenticated; the user is authenticated after the second call of login() method, because the session is already present;
  • with clustered SSO: Session is created while calling login() method and subsequent requests are authenticated.

The cause of the difference in behavior is being investigated. No known workaround is available.

Server

1036872 - Cannot configure a security policy file setting that disables policy files specifies in JRE's java.security file

An issue has been identified in using the special prefix of = to disable the default policy files. The underlying cause is that when the Host Controller started a server, it provided null as the value of the java.security.policy setting, leading to the use of the policy files specified in the java.security file and possibly permission failures preventing server booting.

Several workarounds are available:

1) Edit the JVM’s java.security file (typically at $JAVA_HOME/lib/security/java.security) and comment out any "policy.url" settings. For example

#policy.url.1=file:${java.home}/lib/security/java.policy #policy.url.2=file:${user.home}/.java.policy

Note that this will disable use of these policy files by any users of the JVM installation. If this is a concern, it is best to set up a separate JVM installation for EAP use and alter its configuration.

2) Remove the leading "=" from java.security.policy value; e.g.

-Djava.security.policy=$PWD/server.policy

With these steps taken, only the settings in the specified policy file will be used.

Transaction Manager

1027126 - Server failed to start with standalone-xts.xml and jdbc object store running on mysql 5.5

When the transaction manager is configured to run XTS transactions, use a JDBC object store hosted on MySQL 5.5, and the driver has been put in the deployments directory, the server fails to start. The resulting error includes the text New missing/unsatisfied dependencies. This error does not occur when other database platforms are used. This issue is under investigation and is expected to be resolved in a future release.
1017816 - Not possible to change UID generation from uuid to socket in EAP config

When the process ID generation method is changed to process-id-socket-binding instead of process-id-uuid, an error message starting with the following text results:
                        ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 44) JBAS014613: Operation ("add") failed - address: ([("subsystem" => "transactions")]) - failure description: "JBAS014746: process-id-uuid may not be null"

The cause of this issue is that the handling of the configuration parameter is incorrect. This will be resolved in a future release. No workaround is possible, so the default method of process ID generation must be used.
1009981 - Periodic recovery on committed transactions

When the server is under an excessive load, the server’s log may contain messages like those below, indicating that a transaction rollback had occurred.
17:20:00,441 ERROR [stderr] (Periodic Recovery) javax.transaction.xa.XAException
17:20:00,441 ERROR [stderr] (Periodic Recovery)         at org.hornetq.core.client.impl.ClientSessionImpl.rollback(ClientSessionImpl.java:1692)
17:20:00,441 ERROR [stderr] (Periodic Recovery)         at org.hornetq.core.client.impl.DelegatingSession.rollback(DelegatingSession.java:494)
17:20:00,441 ERROR [stderr] (Periodic Recovery)         at org.hornetq.jms.server.recovery.HornetQXAResourceWrapper.rollback(HornetQXAResourceWrapper.java:126)
17:20:00,441 ERROR [stderr] (Periodic Recovery)         at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.handleOrphan(XARecoveryModule.java:738)
17:20:00,441 ERROR [stderr] (Periodic Recovery)         at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoverySecondPass(XARecoveryModule.java:644)
17:20:00,441 ERROR [stderr] (Periodic Recovery)         at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.bottomUpRecovery(XARecoveryModule.java:417)
17:20:00,441 ERROR [stderr] (Periodic Recovery)         at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:194)
17:20:00,441 ERROR [stderr] (Periodic Recovery)         at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:789)
17:20:00,441 ERROR [stderr] (Periodic Recovery)         at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371)

Under heavy load, the processing time taken by a transaction can overlap with the timing of the periodic recovery process’s activity. The periodic recovery process detects the transaction still in progress and attempts to initiate a rollback but in fact the transaction continues to completion. At the time the periodic recovery attempts but fails the rollback, it records the rollback failure in the server log. The underlying cause of this issue will be addressed in a future release, but in the meantime a workaround is available.

Increase the interval between the two phases of the recovery process by setting the property com.arjuna.ats.jta.orphanSafetyInterval to higher than the default of 10000 milliseconds. A value of 40000 milliseconds is recommended. Please note that this does not solve the issue, instead it decreases the probability that it will occur and that the warning message will be shown in the log.

Web

918130 - JBossWeb connectors start before application deployments are completed in EAP 6

A timing issue with JBossWeb connectors on startup has been discovered, in which the connectors start and accept requests before applications are fully deployed. In these circumstances, client connections via either a load balancer or direct to JBoss EAP are returned a 404 message. This issue affects JBoss EAP versions 6.0.1 and greater. No workaround is available but the issue is under investigation.

Web Console

995439 - JTS transactions are not correctly enabled

When JTS is enabled in the Transactions section of the web management console ("Profile → Container → Transactions"), it it is necessary to also set the attribute transactions to the value on in the JacORB subystem. The intended behaviour is that transactions are enabled when JTS is enabled. The cause of this issue is under investigation. Until it is resolved, the workaround is to ensure that the transactions attribute is also set to on. Note that the transactions subsystem is available only in the full and full-ha profiles.
1014048 - RBAC: Log in right after log out wont clear UI properly in domain mode

In some cases, when logging out of the Web Console, the console is partially rendered before logging in as another user. This leads to "mixed" content where parts of the screen are rendered as if the old user was logged in and parts of the screen as the new user was logged in. As a workaround, close the browser window (not just the active tab) and log in as the new user.
1014219 - RBAC: Control element visibility for users with multiple scoped roles

It has been reported that in this release of JBoss EAP 6 some users assigned to multiple roles will see operations in the console that they do not have access to perform. For exaple; a user with roles host-master-administrator and host-slave-monitor should be only able to see control elements (such as the Add button on the server configurations page) in context of host slave. This button should not be visible when operating in context of host master (however it is).

Operations that are incorrectly visible will fail if attemted as the correct access control is enforced in the execution of the operation. There is no security violation.

No workaround available for this issue at the moment however it will be resolved in a future release of the product.
1026823 - Provide a reliable way to clear "ROLE" headers set by "Run as" dialog

In this release of JBoss EAP 6, it has been reported that when a SuperUser acts of behalf of another user (with the Run As… link), their role is not reset after the action is taken.

The workaround for this issue is to close the browser window (not just the active tab) and re-access the Web Console. This issue will be addressed in a future release of the product.
1017655 - Web services configuration validation errors

In this release of JBoss EAP 6, invalid values for WSDL Host, WSDL Port and WSDL Secure Port under Profiles > Web > Web Services are not rejected by the web console.

Some invalid values cause an error message, while others are ignored without showing an error message. None of the invalid values are stored in the configuration.

This issue will be resolved in a future release of the product.
1016546 - RBAC: [Usability] Unclear error message when trying to configure Auditor role as Administrator

When the user doesn’t have the permission to execute an operation, the general purpose error message is shown: "". This error message is somewhat confusing, because the user tries to execute an operation instead of accessing a resource.

In this release of JBoss EAP 6, if a user attempts to perform an operation which they do not have permission to execute, they will receive the error following error message:
You don’t have the permissions to access this resource!

This can be confusing to users as they are attempting to perform an operation, not attempting to access a resource. This error text will be clarified in a future release of the product.
1029851 - management console - even after cancel the process to upload a deployment file, the content is added to data directory

A Known Issue exists in this release of JBoss EAP 6 that causes the upload of files through the Manage Deployments screen to complete, even if the upload is cancelled by the user.

Cancelling the operation results in the uploaded file being added to the data directory, but prevents it being added as a deployment to the domain.xml file. This means that the file cannot be removed through either the CLI or Web management interfaces.

This issue will be addressed in a future release of the product.
1027586 - RBAC: Web console is too coarse-grained with application resources

In this release of JBoss EAP 6, when a resource is defined as an application resource, the console may not reflect that definition. This is because the console often groups several resources under one view. The controls in the views are available if all related resources are writable. If any of these resources is configured as an application resource, however, the related controls will still be disabled.

The current workaround is to, if possible, configure all resource types associated with a subsystem as application resources.

Web Services

900032 - JBossWS IPv6 issues

mod_cluster

980246 - mod_cluster-manager may break up aliases from a single VirtualHost, causing a messy page

In this release of JBoss EAP, it has been reported that deploying multiple applications, each with a unique virtual-server and each virtual-server with multiple aliases, the mod_cluster_manager may incorrectly display the same Virtual Host multiple time (once for each alias).

This is not the expected behavior, which would be to have all Virtual Hosts displayed only once on the manager page together with all aliases. This issue is under investigation and will be resolved in a later version of JBoss EAP.
901227 - node-timeout, worker-timeout, flush-wait and ttl mod_cluster attributes in web console

There is a known issue in the JBoss EAP 6 web-based Management Console that prevents users from viewing or setting a -1 value for the following mod_cluster attributes:
  • node-timeout
  • worker-timeout
  • flush-wait
  • ttl

If a -1 value is already set, the Management Console incorrectly displays the attribute’s value as 0. When attempting to use the Management Console to set the attribute’s value to -1, the Management Console warns Invalid numeric value.

As a workaround, users are still able to set the affected attributes to a -1 value by using the Management CLI.

The cause of this issue is currently under investigation.
1030965 - Number of registered contexts negatively affects mod_cluster performance

A performance issue has been identified on the Apache HTTP Server with mod_cluster configured as a load balancer. httpd shared memory operations on the workers->nodes table negatively affects the performance of the load balancer. As a result, performance of the httpd load balancer decreases as the number of registered contexts increases.

To workaround this issue, attempt to lower the number of registered contexts.

A solution is being engineered that modifies the httpd to utilize local memory rather than shared memory. A fix is expected in a future release.
900047 - SystemMemoryUsageLoadMetric is not correct on Linux/Unix

The SystemMemoryUsageLoadMetric does not show useful information on Linux or UNIX operating systems. For these systems, HeapMemoryUsageLoadMetric provides more useful information. The solution to this problem will be to change the algorithm of SystemMemoryUsageLoadMetric to subtract the buffers/cache value from the used number. The best method for doing this is under investigation.

Apache Server (httpd) and Connectors

900620 - APR natives are not being loaded if UAC is in place (Windows Server 2008 R2)

On Microsoft Windows servers, Apache portable runtime (APR) libraries will fail to load with User Account Control (UAC) enabled. After installing the libraries, an administrator user will need to right-click the JBoss directory and set "Full control" to "Allow" for the desired user in the Properties → Security tab. This will correct the access rights for UAC.

Domain Management,Web Services

987898 - Write to wsdl-url attribute for WS endpoint ends with 'Unknown attribute wsdl-url' instead of 'Attribute wsdl-url is not writable'

Five attributes of deployed SOAP Web Services endpoints (name, context, class, type, and wsdl-url) are not accessible in the management tools. This was because they are not exposed to the management model by the Web Services subsystem. This will be fixed in a future release.

EJB,Naming

923836 - remote:// protocol does not work over SSL with IBM JDK

There is a Known Issue in this release of JBoss Enterprise Application Platform 6 wherein the remote naming lookup fails intermittently on an IBM JDK with the following exception:
org.jboss.remoting3.NotOpenException: Endpoint is not open.

This issue appears to present when the client uses the IBM JDK. In instances where the server is on the IBM JDK and the and the client uses another JDK, the issue does not present.

The issue is being investigated for a resolution.

IPv6 support

900609 - Opened IPv4 sockets on Windows when server is bound to IPv6

If JBoss EAP 6 is started in Microsoft Windows Server with the IPv4 stack disabled and the IPv6 stack enabled, IPv4 sockets are still opened. This issue is still under investigation.
900564 - Wrong format of IPv6 addresses in log entries

IPv6 addresses should be formatted with square brackets ([ and ]) around them, such as in http://[2620:52:0:105f::ffff:2]:9990. The brackets are missing in the log files for JBoss EAP 6. This issue is expected to be fixed in a future release.

JDR

917683 - JDR utility generates wrong archive entry name running on Windows

A bug has been found in the JDR utility when used in Microsoft Windows Server environments. It has been reported that the utility will append the last character of the originating $JBOSS_HOME directory to the JBOSS_HOME directory created inside the archive.

For example, for an originating JBOSS_HOME directory named jboss-eap-6.2 the JDR utility would produce an archive directory called JBOSS_HOME2.

The cause of this bug is still being investigated and no workaround to prevent it exists.

RESTEasy

958896 - RESTEasy: Invalid Content-Type in response - Bad behavior when invalid accept header is specified in request header

An issue has been discovered in the RESTEasy subsystem where an incorrect HTTP 200 response is sent when there is an invalid accept header in a received HTTP request.

When an invalid accept header is provided, the correct response should be HTTP 500. This issue is currently under investigation.

A. Revision History

Revision History
Revision 2.0-16Wed Dec 4 2013Russell Dickenson
JBoss Enterprise Application Platform 6.2.0 GA Release.