Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1320132

Summary: [GSS] (6.4.z) naming context is not setup when starting the persistence unit
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Carsten Lichy-Bittendorf <clichybi>
Component: JPAAssignee: Chao Wang <chaowan>
Status: CLOSED CURRENTRELEASE QA Contact: Martin Simka <msimka>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4.6CC: bmaxwell, chaowan, dosoudil, jawilson, jbilek, jtruhlar, msochure, scott.marlow
Target Milestone: CR1   
Target Release: EAP 6.4.10   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-17 12:57:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1339868    

Description Carsten Lichy-Bittendorf 2016-03-22 11:42:25 UTC
Description of problem:
lookup of env-entry throws NameNotFoundException during persistence unit startup

Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
1. add env-entry in application.xml
2. try to lookup during persistent unit startup, e.g.  
public class MyType implements UserType {
...
    @Override
    public int[] sqlTypes() {
        try {
            Object ctx = new InitialContext().lookup("java:app/env");
            log.info("java:app/env from JPA = " + ctx);
        } catch (Exception e) {
            log.error("unable to get java:app/env from JPA", e);
        }

        return new int[] { Types.VARCHAR };
    }

Actual results:
NameNotFoundException

Expected results:
value of env-entry is available

Additional info:
On 21.03.2016 23:47, Stuart Douglas wrote:
> This should fix it (I think): https://github.com/stuartwdouglas/wildfly/tree/jpa-java-namespace
>
> Stuart

Comment 3 JBoss JIRA Server 2016-06-03 02:06:23 UTC
Scott Marlow <scott.marlow> updated the status of jira WFLY-6441 to Closed

Comment 6 Jiří Bílek 2016-08-18 07:04:19 UTC
Verified with EAP 6.4.10.CP.CR2

Comment 7 JBoss JIRA Server 2016-08-19 03:47:37 UTC
Jason Greene <jason.greene> updated the status of jira WFLY-6441 to Reopened

Comment 8 JBoss JIRA Server 2016-08-19 03:48:29 UTC
Jason Greene <jason.greene> updated the status of jira WFLY-6441 to Resolved

Comment 9 Petr Penicka 2017-01-17 12:57:36 UTC
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.