tomee-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fabio Jun Takada Chino (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TOMEE-2223) Incorrect JPA entity used when running under docker
Date Tue, 21 Aug 2018 01:40:00 GMT

    [ https://issues.apache.org/jira/browse/TOMEE-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16586785#comment-16586785
] 

Fabio Jun Takada Chino commented on TOMEE-2223:
-----------------------------------------------

Hi,

In the first few attempts, I was lucky enough to replicate the issue and attach the debugger
to see what is happening. The issue is not related to OpenJPA but with the incorrect generation
of the EJB proxies that is mixing the inner instances after it.

In order to save time, I wrote a single base abstract class called BaseRepository<EntityType,
KeyType> that has a constructor that receives the actual class that will be used to access
the database (field entityClass). This class has a method called find(KeyType) that calls
em.find(this.entityClass, key). Each concrete class is implemented as EntityARepository extends
BaseRepository<EntityA,String> passing EntityA.class to the base constructor and EntityBRepository
extends BaseRepository<EntityB,KeyOfEntityB>

When the issue occurs, I'm calling an EJB that is an instance of EntityARepository, the proxy
says that it is indeed a proxy to EntityARepository but, when I intercept the method find()
from BaseRepository, the proxy is calling a concreate instance of EntityBRepository instead.

I already used this construction before in other JEE servers and earlier versions of TomEE
and it never happened before. In fact, is is not happening outside the docker container.

Thanks in advance,

Fabio

 

 

 

 

 

 

 

> Incorrect JPA entity used when running under docker
> ---------------------------------------------------
>
>                 Key: TOMEE-2223
>                 URL: https://issues.apache.org/jira/browse/TOMEE-2223
>             Project: TomEE
>          Issue Type: Bug
>          Components: TomEE Core Server
>    Affects Versions: 7.0.5
>         Environment: * Docker version 17.12.1-ce, build 7390fc6;
> * Official Ubuntu 18.04 (x64) docker image with OpenJDK 8 installed;
> * apache-tomee-webprofile-7.0.5;
> * Apache Derby 10.14.2.0 (embedded);
>            Reporter: Fabio Jun Takada Chino
>            Priority: Minor
>
> While packing a very simple web application inside a docker container based on the official
Ubuntu 18.04 image, I found a very inconvenient error related to OpenJPA using the wrong entity
to access the database.
> When it happens, the following exception can be found in the log:
> {{org.apache.openjpa.persistence.ArgumentException : The given value "test" cannot be
converted into an identity for "class EntityB".  The value is the wrong type (java.lang.String)}}{{
using the wrong entity to store information inside}}
> The major problem with this code is that the actual method is trying to access the entity
EntityA instead of EntityB. The conversion error occurs because the ID for EntityB is a composite
value while the ID for EntityA is indeed a string.
> Given that, I tried to trace the issue using a remote debugger but, when I activate,
the problem vanishes. It does not matter if the debugger is connected or not. Since it is
not a critical application, I can workaround it by leaving the remote debugger enabled but
it would be a real issue for production environment.
> The docker image I'm using as the base can be found in the Docker Hub with the name opencs/ubuntu-openjdk-8-headless.
> The application is a single WAR file with some EJBs, JPA entities, a few servlets and
a few JSF pages. Almost all JPA entities have single primary keys but one of them have a composite
key with 2 strings.
> Thanks in advance,
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message