Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-3411

EJB/JPA error when call to persist

XMLWordPrintable

    • Hide
      • I have an entity with ID = 1 stored in the database.

      Steps to reproduce:
      1) Create a new object using the JSF interface, add like ID the number 1.
      2) Try to save (internally the application calls the EJB method to persist the entity), we get an exception because of duplicate primary key.
      3) Change the ID (using the interface) with other number, for example 2. We are using the same referenced object in memory.
      4) Try to save again, we will get an exception like this: "Communication failure detected when attempting to perform read query outside of a transaction"

      As I said before, this error is not fired with the same eclipselink version on glassfish 4.

      Show
      I have an entity with ID = 1 stored in the database. Steps to reproduce: 1) Create a new object using the JSF interface, add like ID the number 1. 2) Try to save (internally the application calls the EJB method to persist the entity), we get an exception because of duplicate primary key. 3) Change the ID (using the interface) with other number, for example 2. We are using the same referenced object in memory. 4) Try to save again, we will get an exception like this: "Communication failure detected when attempting to perform read query outside of a transaction" As I said before, this error is not fired with the same eclipselink version on glassfish 4.
    • Compatibility/Configuration

      I'm getting an exception when I try to persist an object for second time, after get an exception because of duplicate primary key.

      I have tested the same application on GlassFish 4 with JSF(Mojarra) 2.2.6, EclipsLink 2.5.1 and this error is not fired, all works fine.

      I also tried changing the default datasource setting in Wildfly.

              dlloyd@redhat.com David Lloyd
              Lynx6 Wilber Saca (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: