Bug 1346242 - [GSS] (6.4.z) InvalidBytecodeException when an EJB local interface declares static method
Summary: [GSS] (6.4.z) InvalidBytecodeException when an EJB local interface declares s...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: EJB
Version: 6.4.0,6.4.1,6.4.2,6.4.3,6.4.4,6.4.5,6.4.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR1
: EAP 6.4.10
Assignee: Peter Palaga
QA Contact: Jan Martiska
URL:
Whiteboard:
Depends On:
Blocks: eap6410-payload 1346403
TreeView+ depends on / blocked
 
Reported: 2016-06-14 11:03 UTC by wfink
Modified: 2019-11-14 08:23 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-01-17 12:56:04 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-4316 0 Major Resolved InvalidBytecodeException when an EJB local interface declares static method 2017-11-22 20:52:18 UTC
Red Hat Knowledge Base (Solution) 2374301 0 None None None 2016-06-14 11:21:49 UTC

Description wfink 2016-06-14 11:03:59 UTC 
Description of problem:
An EJB which is compiled and deployed with Java7 works correct.
But if build and deployed with Java8 the deployment or start fail with the following cause:
Caused by: org.jboss.classfilewriter.InvalidBytecodeException: Cannot load variable at 1. Local Variables: Local Variables: [StackEntry [descriptor=Ljava/lang/String;, type=OBJECT]]
Comment 1 Peter Palaga 2016-06-21 12:25:43 UTC 
Sent https://github.com/jbossas/jboss-invocation/pull/11
Comment 2 Peter Palaga 2016-06-21 12:56:13 UTC 
Sent a PR with a test case that checks that the fix in jboss-invocation works https://github.com/jbossas/jboss-eap/pull/2798
Comment 3 Peter Palaga 2016-06-21 13:21:56 UTC 
Created a new "test BZ" https://bugzilla.redhat.com/show_bug.cgi?id=1348569
Comment 5 Jiří Bílek 2016-08-09 13:59:43 UTC 
Verified with EAP 6.4.10.CP.CR1
Comment 6 Petr Penicka 2017-01-17 12:56:04 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.
Note You need to log in before you can comment on or make changes to this bug.