Bug 1320132 - [GSS] (6.4.z) naming context is not setup when starting the persistence unit
Summary: [GSS] (6.4.z) naming context is not setup when starting the persistence unit
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: JPA
Version: 6.4.6
Hardware: All
OS: All
unspecified
medium
Target Milestone: CR1
: EAP 6.4.10
Assignee: Chao Wang
QA Contact: Martin Simka
URL:
Whiteboard:
Depends On:
Blocks: eap6410-payload
TreeView+ depends on / blocked
 
Reported: 2016-03-22 11:42 UTC by Carsten Lichy-Bittendorf
Modified: 2020-07-16 08:44 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-01-17 12:57:36 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEAP-3993 0 Major Verified naming context is not setup when starting the persistence unit 2017-06-14 14:06:01 UTC
Red Hat Issue Tracker WFLY-6441 0 Major Closed naming context is not setup when starting the persistence unit 2017-06-14 14:06:01 UTC
Red Hat Knowledge Base (Solution) 2206151 0 None None None 2016-03-22 12:00:31 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.