]
Daniel Carrion commented on WFLY-6441:
--------------------------------------
Getting the following in thread dump after some code associated to this commit was
changed:
--
at
org.jboss.as.ee.component.BasicComponent.waitForComponentStart(BasicComponent.java:117)
locked <0x00000000c56881e0> (a
org.jboss.as.ejb3.component.stateless.StatelessSessionComponent)
--
Causes freeze during deployment after upgrade from JBoss EAP 6.4.9 to JBoss 6.4.10.
Rolling back to previous JPA code in 6.4.10 fixes issue.
naming context is not setup when starting the persistence unit
--------------------------------------------------------------
Key: WFLY-6441
URL:
https://issues.jboss.org/browse/WFLY-6441
Project: WildFly
Issue Type: Enhancement
Components: JPA / Hibernate
Affects Versions: JBoss AS7 7.1.1.Final, JBoss AS7 7.2.0.Final, 9.0.2.Final,
10.0.0.Final
Reporter: Scott Marlow
Assignee: Scott Marlow
Priority: Major
Fix For: 10.1.0.CR1, 10.1.0.Final
ookup 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