You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Mark Struberg (JIRA)" <ji...@apache.org> on 2018/11/10 20:06:00 UTC

[jira] [Commented] (OPENJPA-2740) Incorrectly configured /etc/hosts file on Linux system causes OpenJPA createEntityManager() to hang.

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

Mark Struberg commented on OPENJPA-2740:
----------------------------------------

ping ping. [~saurabh_malode] can you still reproduce it? would be cool if we could get a stack dump from that process.

You can also remove any lines which come from your own application, we are really just interested in the openjpa, etc parts.

txs!

> 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)