New Jdeveloper 11.1.1.6 reproducable issues

New fusion and Jdeveloper version 11.1.1.6 is available since last week.

I hear there are a lot of upgrates for SOA and BPM.
For ADF there are some enchancements for touch-enabled devices and bug fixes.

Some inderesting bug fixes in relase notes that we care about are:

12434470	reopening search and select dialog shows old data in the table
12825879	lov on query does not validate correctly and fires a blind query
12825973	lovs do not display changed values during the current session
12991181	af:inputlistofvalues in af:table only shows 25 rows
12376375	attributedescriptor.setreadonly(true) doesn't make the field readonly

I went through the posted bugs since 11.1.1.4 in this blog and unfortunately most of them still reproduce in 11.1.1.6:

Rollback does not refresh current row of af:table after validation errors.

Attribute Validation on Input List of Values attribute

Number precision and scale bug

Range paging and Table Selected Row Bugs

Tab selection and Enable User Customization on Session bug.

ExecuteEmptyRowSet and Range Paging. (Fixed in 11.1.2)

Partial Page Rendering ChangeEventPolicy="ppr" bug. (Fixed in 11.1.2)

Dependent LOV in table shows invalid values

Invalid values in choice lists

Application Module cannot get principal when you use transaction controller in task flows (Fixed in 11.1.2)

Table Filter Number format bug

Cannot use a region in a page more than one time

Access Keys are accessible even from a modal popup

Bad performance on quering Roles in weblogic Enterprise Manager

There are about 400 application roles defined in our application.
In a production environment there are about 1000 users that have groups of these roles so there are about 7000 role assignments.
We the policy store to be Database based for production environment (as it is recommended by documentation) in order to support clustering Weblogic environment.
Then the hole performance of Enterprise Manager was much worse than in file based. It took about 8 minutes to query the roles. This was happening also in every action , create, assign, remove role.
We run statistics and clean procedure in the database Policy Store but with no improvement.

So Service Request in oracle support is posted and they managed to reproduce it and post a bug: 13597913.

As a workaround we still use File Based Policy Store and synchronize system-jazn-date files between clustered servers.