[
https://issues.apache.org/jira/browse/OPENJPA-2740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503520#comment-16503520
]
Mark Struberg commented on OPENJPA-2740:
----------------------------------------
+1 a jstack or kill -3 would be great.
OpenJPA tries to connect to the database as on startup. The reason is to
collect metadata, like field types (one Entity class might map to different
column types in the DB), auto detecting the dialect (MySQL, Oracle, Postgres,
..), etc. That bring some benefits, but of course in some cases might also be a
downside.
> Incorrectly configured /etc/hosts file on Linux system causes OpenJPA
> createEntityManager() to hang.
> ----------------------------------------------------------------------------------------------------
>
> Key: OPENJPA-2740
> URL: https://issues.apache.org/jira/browse/OPENJPA-2740
> Project: OpenJPA
> Issue Type: Question
> Components: jpa
> Affects Versions: 2.4.2
> Environment: Linux RHEL 7.4
> Reporter: Saurabh Malode
> Priority: Major
>
> We are using OpenJPA to manage a relational database for an offline desktop
> application.
> OpenJPA does not works on Linux OS on which /etc/hosts file is having
> incorrect configuration.
>
> We have observed that, it works if the file is not present or empty.
>
> The application we have developed does not require any internet connection
> hence we want OpenJPA to work even if the host name resolution is not done.
>
> The OpenJPA API does not provides any such option to override default
> configuration for hostname resolution or an option to indicate that the
> database being used is an offline database.
>
> Please suggest any resolution for this issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
