For those people that are stuck, there is a very onerous workaround to this issue where you can maintain an extra entry in the last position of the backing list such as:

backingList.add("blank")

And then you can make this entry invisible with CSS (for example, if your bodyClass is "blockList":

.blockList .if-list-item:last-child

You just have to make sure you maintain the "blank" entry @ the end of the list, no matter what kind of adding/removing you do to the list. I just have this inside all of my add/remove functions:

backingList.remove("blank");
// manipulate the list however you want
backingList.add("blank");

Unable to reproduce the error with the attached test case, with the ICEfaces 4.1.1 release libraries, on Payara-Web 4.1.1.164 (Web Profile), GlassFish5, Tomcat7.

I reproduced the 'NoRowAvailableException' error on Payara/GlassFish5 by adding a constructor to the AceListBean.java:
public AceListBean(List<String> list)

This error cannot be reproduced on Tomcat.

Removing the "@Named" annotation from the bean makes this error disappear on Payara/GlassFish5.

rev 51373 resolves this issue. It should be noted that the problem could be replicated using JSF managed beans and did not require CDI to reproduce. I will attach a CDI project that can also be tested on Tomcat 8 though (using maven). You would have to install the SNAPSHOT from rev 51373 to test it using maven. The QA test also has been modified to use JSF annotations for testing.

issue with deploying the aceListCDI war to payara was the context.xml file in the war. It is for tomcat only and loads tomcat classes so that was the exception on Payara. Just remove this file from the war and it deploys fine.

Re-open to reclassify as Invalid, since no product changes are required to resolve.

Re-open to mark Fixed again, as there was a code change requires to resolve the original issue.