Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-14604

(7.1.z) IllegalStateException: Constructor is unexpectedly inaccessible

    XMLWordPrintable

Details

    • EAP 7.1.3

    Description

      Looks like the upgrade of JBoss Marshalling to 2.0.4.Final-redhat-1 introduced JBMAR-219 .
      This is no longer an issue with new builds of Oracle and OpenJDK, but the issue is still present on IBM JDK. Even on the latest update as of now (8.0.5.11).

      Most of the batch integration tests are failing with

      java.lang.IllegalStateException: Constructor is unexpectedly inaccessible
	at org.jboss.marshalling.reflect.SerializableClass.invokeConstructorNoException(SerializableClass.java:377)
	at org.jboss.marshalling.reflect.SerializableClass.callNonInitConstructor(SerializableClass.java:332)
	at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:248)
	at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:130)
	at org.jboss.marshalling.cloner.SerializingCloner.cloneFields(SerializingCloner.java:391)
	at org.jboss.marshalling.cloner.SerializingCloner.initSerializableClone(SerializingCloner.java:311)
	at org.jboss.marshalling.cloner.SerializingCloner.initSerializableClone(SerializingCloner.java:279)
	at org.jboss.marshalling.cloner.SerializingCloner.initSerializableClone(SerializingCloner.java:279)
	at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:254)
	at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:130)
	at org.jberet.util.BatchUtil.clone(BatchUtil.java:132)

      This is a regression against EAP 7.1.1

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBMAR-219 Access exceptions on older JDK 8

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved
          is caused by

          Task - Represents a small unit of work that is not end-user facing. JBMAR-215 Java 9: Eliminate uses of reflection setAccessible()

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-14754 (7.1.z) Upgrade jboss-marshalling from 2.0.4.Final-redhat-1 to 2.0.5

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified

          Activity

            People

              rhn-cservice-bbaranow Bartosz Baranowski
              pmackay@redhat.com Peter Mackay
              Peter Mackay Peter Mackay
              Peter Mackay Peter Mackay
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: