[jangut]

I am running Update 3 for EAP 6.3 and when I put a lambda expression (java 1.8 feature) in a CDI bean the deployment fails with:

JBAS015852: Could not index class org/jboss/as/quickstarts/helloworld/HelloService.class at /c:/install/jboss-eap-6.3.3/bin/content/jboss-helloworld.war/WEB-INF/classes: java.lang.IllegalStateException: Unknown tag! pos=5 poolCount = 80

at org.jboss.jandex.Indexer.processConstantPool(Indexer.java:606) [jandex-1.0.3.Final-redhat-2.jar:1.0.3.Final-redhat-2]

...

Seems to me that lambdas can not be user in conjunction with CDI in Update 3 for EAP 6.3. Is that a correct statement or something is wrong at my end?

-jan

[sflanigan]

That does sound similar to these issues: [WFLY-2287] Java 8 Class files not loading in Beta1 - JBoss Issue Tracker and [JANDEX-14] Jandex doesn't work with invokedynamic constant pool tag - JBoss Issue Tracker.

[ctomc]

Yes fix is updating jandex, preferably to 1.2.x.Final version.

if you want to do it manually download  https://repository.jboss.org/nexus/service/local/repositories/central/content/org/jboss/jandex/1.2.3.Final/jandex-1.2.3.…

and put it into JBOSS_HOME\modules\system\layers\base\org\jboss\jandex\main and then update reference to the new file in module.xml

EAP 6.4.x builds already have this fixed. With patch for 6.3 coming.

[jangut]

Thanks Tomaz. That solved the issue.

[blackbeltdev]

https://access.redhat.com/articles/111663

makes no mention of JDK 1.8 as being a supported platform for 6.3. I'm still waiting on our OPs team to provide installer to verify. Can someone from RedHat clarify this please?

[blackbeltdev]

FYI..

In case anyone is interested I found this link on customer portal with official answer:

Support for Java 8 in EAP - Red Hat Customer Portal

"Starting with 6.3 update 3 (6.3.3) and continuing with 6.4, Oracle Java SE 8 is both a supported and tested configuration."