[JBoss JIRA] Created: (EJBTHREE-1730) Specification violation [EJB3 JPA 6.2.1.2] - You have not defined a non-jta-data-source for a RESOURCE_LOCAL
3:21 p.m.
Specification violation [EJB3 JPA 6.2.1.2] - You have not defined a non-jta-data-source
for a RESOURCE_LOCAL
------------------------------------------------------------------------------------------------------------
Key: EJBTHREE-1730
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1730
Project: EJB 3.0
Issue Type: Bug
Components: ejb3
Environment: JBoss v5.0
Spring 2.5
Reporter: Spec Dev
The same application that works fine in JBoss 4.2.2 fails in JBoss v5.0 with the following
exception:
13:42:16,343 ERROR [AbstractKernelController] Error installing to Start:
name=persistence.unit:unitName=#MyPU state=Create
java.lang.RuntimeException: Specification violation [EJB3 JPA 6.2.1.2] - You have not
defined a non-jta-data-source for a RESOURCE_LOCAL enabled persistence context named:
MyPU
The persistence unit for the application uses a datasource configured and managed by
Spring.
<?xml version="1.0" encoding="UTF-8"?>
<persistence version="1.0"
xmlns="http://java.sun.com/xml/ns/persistence"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
<persistence-unit name="MyPU"
transaction-type="RESOURCE_LOCAL">
<provider>org.hibernate.ejb.HibernatePersistence</provider>
<properties>
<property name="hibernate.format_sql"
value="true"/>
<property name="hibernate.order_updates"
value="true"/>
<property name="hibernate.hbm2ddl.auto"
value="validate"/>
<property name="hibernate.dialect"
value="org.hibernate.dialect.Oracle10gDialect"/>
<!-- property name="hibernate.transaction.factory_class"
value="org.hibernate.transaction.JTATransactionFactory"/-->
<property name="hibernate.transaction.manager_lookup_class"
value="org.hibernate.transaction.JBossTransactionManagerLookup"/>
</properties>
</persistence-unit>
</persistence>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:19 p.m.
New subject: [JBoss JIRA] Resolved: (EJBTHREE-1730) Specification violation [EJB3 JPA 6.2.1.2] - You have not defined a non-jta-data-source for a RESOURCE_LOCAL
[
https://jira.jboss.org/jira/browse/EJBTHREE-1730?page=com.atlassian.jira....
]
Carlo de Wolf resolved EJBTHREE-1730.
-------------------------------------
Resolution: Rejected
Assignee: Carlo de Wolf
Specification violation [EJB3 JPA 6.2.1.2] - You have not defined a non-jta-data-source
for a RESOURCE_LOCAL enabled persistence context named: MyPU
e.g. you must specify a <non-jta-datasource>, see also 6.2.1.5.
Specification violation [EJB3 JPA 6.2.1.2] - You have not defined a
non-jta-data-source for a RESOURCE_LOCAL
------------------------------------------------------------------------------------------------------------
Key: EJBTHREE-1730
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1730
Project: EJB 3.0
Issue Type: Bug
Components: ejb3
Environment: JBoss v5.0
Spring 2.5
Reporter: Spec Dev
Assignee: Carlo de Wolf
The same application that works fine in JBoss 4.2.2 fails in JBoss v5.0 with the
following exception:
13:42:16,343 ERROR [AbstractKernelController] Error installing to Start:
name=persistence.unit:unitName=#MyPU state=Create
java.lang.RuntimeException: Specification violation [EJB3 JPA 6.2.1.2] - You have not
defined a non-jta-data-source for a RESOURCE_LOCAL enabled persistence context named:
MyPU
The persistence unit for the application uses a datasource configured and managed by
Spring.
<?xml version="1.0" encoding="UTF-8"?>
<persistence version="1.0"
xmlns="http://java.sun.com/xml/ns/persistence"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
<persistence-unit name="MyPU"
transaction-type="RESOURCE_LOCAL">
<provider>org.hibernate.ejb.HibernatePersistence</provider>
<properties>
<property name="hibernate.format_sql"
value="true"/>
<property name="hibernate.order_updates"
value="true"/>
<property name="hibernate.hbm2ddl.auto"
value="validate"/>
<property name="hibernate.dialect"
value="org.hibernate.dialect.Oracle10gDialect"/>
<!-- property name="hibernate.transaction.factory_class"
value="org.hibernate.transaction.JTATransactionFactory"/-->
<property name="hibernate.transaction.manager_lookup_class"
value="org.hibernate.transaction.JBossTransactionManagerLookup"/>
</properties>
</persistence-unit>
</persistence>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:19 p.m.
New subject: [JBoss JIRA] Reopened: (EJBTHREE-1730) Specification violation [EJB3 JPA 6.2.1.2] - You have not defined a non-jta-data-source for a RESOURCE_LOCAL
[
https://jira.jboss.org/jira/browse/EJBTHREE-1730?page=com.atlassian.jira....
]
Spec Dev reopened EJBTHREE-1730:
--------------------------------
Why the new restriction?
In JBoss 4.2.2 I was able to not define a non-jta datasource.
I delegated the configuration of the datasource to Spring for specific reasons.
The specs say nothing about forcing the definition of a non-jta datasource.
Hence the code is broken and needs fixing.
Here is a snippet of my Spring config:
<!-- %%%%%%%%%%%%%%%%%%%%%%%%%% JPA Entity Manager
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% -->
<bean id="persistenceUnitManager"
class="org.springframework.orm.jpa.persistenceunit.DefaultPersistenceUnitManager">
<property name="defaultDataSource" ref="dataSource" />
</bean>
<bean id="entityManagerFactory"
class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean">
<property name="persistenceUnitManager"
ref="persistenceUnitManager" />
</bean>
<bean id="jpaDialect"
class="org.springframework.orm.jpa.vendor.HibernateJpaDialect" />
<!-- %%%%%%%%%%%%%%%%%%%%%%%%%% Transaction Manager
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% -->
<bean id="txManager"
class="org.springframework.orm.jpa.JpaTransactionManager">
<property name="entityManagerFactory"
ref="entityManagerFactory" />
<property name="jpaDialect" ref="jpaDialect"/>
</bean>
Specification violation [EJB3 JPA 6.2.1.2] - You have not defined a
non-jta-data-source for a RESOURCE_LOCAL
------------------------------------------------------------------------------------------------------------
Key: EJBTHREE-1730
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1730
Project: EJB 3.0
Issue Type: Bug
Components: ejb3
Environment: JBoss v5.0
Spring 2.5
Reporter: Spec Dev
Assignee: Carlo de Wolf
The same application that works fine in JBoss 4.2.2 fails in JBoss v5.0 with the
following exception:
13:42:16,343 ERROR [AbstractKernelController] Error installing to Start:
name=persistence.unit:unitName=#MyPU state=Create
java.lang.RuntimeException: Specification violation [EJB3 JPA 6.2.1.2] - You have not
defined a non-jta-data-source for a RESOURCE_LOCAL enabled persistence context named:
MyPU
The persistence unit for the application uses a datasource configured and managed by
Spring.
<?xml version="1.0" encoding="UTF-8"?>
<persistence version="1.0"
xmlns="http://java.sun.com/xml/ns/persistence"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
<persistence-unit name="MyPU"
transaction-type="RESOURCE_LOCAL">
<provider>org.hibernate.ejb.HibernatePersistence</provider>
<properties>
<property name="hibernate.format_sql"
value="true"/>
<property name="hibernate.order_updates"
value="true"/>
<property name="hibernate.hbm2ddl.auto"
value="validate"/>
<property name="hibernate.dialect"
value="org.hibernate.dialect.Oracle10gDialect"/>
<!-- property name="hibernate.transaction.factory_class"
value="org.hibernate.transaction.JTATransactionFactory"/-->
<property name="hibernate.transaction.manager_lookup_class"
value="org.hibernate.transaction.JBossTransactionManagerLookup"/>
</properties>
</persistence-unit>
</persistence>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:21 p.m.
New subject: [JBoss JIRA] Resolved: (EJBTHREE-1730) Specification violation [EJB3 JPA 6.2.1.2] - You have not defined a non-jta-data-source for a RESOURCE_LOCAL
[
https://jira.jboss.org/jira/browse/EJBTHREE-1730?page=com.atlassian.jira....
]
Carlo de Wolf resolved EJBTHREE-1730.
-------------------------------------
Resolution: Rejected
On 4.2.2.GA:
22:19:54,532 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
--- MBeans waiting for other MBeans ---
ObjectName: persistence.units:unitName=MyPU
State: FAILED
Reason: java.lang.RuntimeException: You have not defined a non-jta-data-source for a
RESOURCE_LOCAL enabled persistence context named: MyPU
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: persistence.units:unitName=MyPU
State: FAILED
Reason: java.lang.RuntimeException: You have not defined a non-jta-data-source for a
RESOURCE_LOCAL enabled persistence context named: MyPU
Specification violation [EJB3 JPA 6.2.1.2] - You have not defined a
non-jta-data-source for a RESOURCE_LOCAL
------------------------------------------------------------------------------------------------------------
Key: EJBTHREE-1730
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1730
Project: EJB 3.0
Issue Type: Bug
Components: ejb3
Environment: JBoss v5.0
Spring 2.5
Reporter: Spec Dev
Assignee: Carlo de Wolf
The same application that works fine in JBoss 4.2.2 fails in JBoss v5.0 with the
following exception:
13:42:16,343 ERROR [AbstractKernelController] Error installing to Start:
name=persistence.unit:unitName=#MyPU state=Create
java.lang.RuntimeException: Specification violation [EJB3 JPA 6.2.1.2] - You have not
defined a non-jta-data-source for a RESOURCE_LOCAL enabled persistence context named:
MyPU
The persistence unit for the application uses a datasource configured and managed by
Spring.
<?xml version="1.0" encoding="UTF-8"?>
<persistence version="1.0"
xmlns="http://java.sun.com/xml/ns/persistence"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
<persistence-unit name="MyPU"
transaction-type="RESOURCE_LOCAL">
<provider>org.hibernate.ejb.HibernatePersistence</provider>
<properties>
<property name="hibernate.format_sql"
value="true"/>
<property name="hibernate.order_updates"
value="true"/>
<property name="hibernate.hbm2ddl.auto"
value="validate"/>
<property name="hibernate.dialect"
value="org.hibernate.dialect.Oracle10gDialect"/>
<!-- property name="hibernate.transaction.factory_class"
value="org.hibernate.transaction.JTATransactionFactory"/-->
<property name="hibernate.transaction.manager_lookup_class"
value="org.hibernate.transaction.JBossTransactionManagerLookup"/>
</properties>
</persistence-unit>
</persistence>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:14 a.m.
New subject: [JBoss JIRA] Reopened: (EJBTHREE-1730) Specification violation [EJB3 JPA 6.2.1.2] - You have not defined a non-jta-data-source for a RESOURCE_LOCAL
[
https://jira.jboss.org/jira/browse/EJBTHREE-1730?page=com.atlassian.jira....
]
Spec Dev reopened EJBTHREE-1730:
--------------------------------
Carlo, thanks for your assistance.
However, I have to insist that this is working just fine in JBoss v4.2.2GA.
It seems like JBoss v5.0 tries to deploy the JPA entities itself instead of deferring to
Spring.
Here are the logs from starting JBoss v4.2.2.GA and from starting JBoss v5.0 using the
same war file.
Note how the "PersistenceUnitDeployment" does not get called for JBoss
v4.2.2.GA.
JBoss v4.2.2.GA:
----------------------------------
09:00:32,359 INFO [Server] Starting JBoss (MX MicroKernel)...
09:00:32,359 INFO [Server] Release ID: JBoss [Trinity] 4.2.2.GA (build:
SVNTag=JBoss_4_2_2_GA date=200710221139)
09:00:32,359 INFO [Server] Home Dir: C:\JBoss\jboss-4.2.2.GA
09:00:32,359 INFO [Server] Home URL: file:/C:/JBoss/jboss-4.2.2.GA/
09:00:32,359 INFO [Server] Patch URL: null
09:00:32,359 INFO [Server] Server Name: sdu360_ny
09:00:32,359 INFO [Server] Server Home Dir: C:\JBoss\jboss-4.2.2.GA\server\sdu360_ny
09:00:32,359 INFO [Server] Server Home URL:
file:/C:/JBoss/jboss-4.2.2.GA/server/sdu360_ny/
09:00:32,359 INFO [Server] Server Log Dir: C:\JBoss\jboss-4.2.2.GA\server\sdu360_ny\log
09:00:32,359 INFO [Server] Server Temp Dir: C:\JBoss\jboss-4.2.2.GA\server\sdu360_ny\tmp
09:00:32,359 INFO [Server] Root Deployment Filename: jboss-service.xml
initializing com.acs.is.framework.logging.config.LoggingConfig...
09:00:32,625 INFO [ServerInfo] Java version: 1.5.0_15,Sun Microsystems Inc.
09:00:32,625 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_15-b04,Sun
Microsystems Inc.
09:00:32,625 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
09:00:32,984 INFO [Server] Core system initialized
09:00:35,062 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/
09:00:35,062 INFO [Log4jService$URLWatchTimerTask] Configuring from URL:
resource:jboss-log4j.xml
09:00:35,515 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) -
JBoss Inc.
09:00:35,515 INFO [TransactionManagerService] Setting up property manager MBean and JMX
layer
09:00:35,781 INFO [TransactionManagerService] Starting recovery manager
09:00:35,890 INFO [TransactionManagerService] Recovery manager started
09:00:35,890 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
09:00:38,343 INFO [EJB3Deployer] Starting java:comp multiplexer
09:00:38,640 INFO [STDOUT] no object for null
09:00:38,640 INFO [STDOUT] no object for null
09:00:38,656 INFO [STDOUT] no object for null
09:00:38,671 INFO [STDOUT] no object for {urn:jboss:bean-deployer}supplyType
09:00:38,687 INFO [STDOUT] no object for {urn:jboss:bean-deployer}dependsType
09:00:40,671 INFO [NativeServerConfig] JBoss Web Services - Native
09:00:40,671 INFO [NativeServerConfig] jbossws-native-2.0.1.SP2 (build=200710210837)
09:00:41,609 INFO [Embedded] Catalina naming disabled
09:00:41,765 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows
optimal performance in production environments was not found on the java.library.path:
C:\jdk1.5.0_15\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Program
Files\Java\jre1.6.0_06\bin\client;C:\Program
Files\Java\jre1.6.0_06\bin;C:\oraclexe\app\oracle\product\10.2.0\server\bin;c:\ruby\bin;C:\Program
Files\ThinkPad\Utilities;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program
Files\Intel\Wireless\Bin\;C:\Program Files\ATI Technologies\ATI.ACE\;C:\Program
Files\Diskeeper Corporation\Diskeeper\;C:\Program
Files\ThinkPad\ConnectUtilities;C:\Program Files\Common Files\Lenovo;C:\Program
Files\Lenovo\Client Security Solution;C:\Program Files\Intel\Wireless\Bin\;C:\Program
Files\Intel\Wireless\Bin\;C:\Program Files\MySQL\MySQL Server
5.1\bin;C:\grails-1.0-RC2\bin;C:\Program Files\Perforce;C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\;C:\Program Files\QuickTime\QTSystem\;C:\Program
Files\Java\jdk1.5.0_12\bin;C:\ant\apache-ant-1.7.0\bin;C:\db-derby-10.3.2.1-bin\bin;C:\apache-maven-2.0.9/bin;.
09:00:41,843 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080
09:00:41,843 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
09:00:41,843 INFO [Catalina] Initialization processed in 230 ms
09:00:41,843 INFO [StandardService] Starting service jboss.web
09:00:41,843 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.1.GA
09:00:41,890 INFO [Catalina] Server startup in 51 ms
09:00:41,984 INFO [TomcatDeployer] deploy, ctxPath=/,
warUrl=.../deploy/jboss-web.deployer/ROOT.war/
09:00:42,546 INFO [TomcatDeployer] deploy, ctxPath=/invoker,
warUrl=.../deploy/http-invoker.sar/invoker.war/
09:00:42,687 INFO [TomcatDeployer] deploy, ctxPath=/jbossws,
warUrl=.../deploy/jbossws.sar/jbossws-context.war/
09:00:42,765 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil,
warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
09:00:43,468 INFO [TomcatDeployer] deploy, ctxPath=/web-console,
warUrl=.../deploy/management/console-mgr.sar/web-console.war/
09:00:44,062 INFO [MailService] Mail Service bound to java:/Mail
09:00:44,265 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in
.../deploy/jboss-ha-local-jdbc.rar
09:00:44,296 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in
.../deploy/jboss-ha-xa-jdbc.rar
09:00:44,312 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in
.../deploy/jboss-local-jdbc.rar
09:00:44,359 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in
.../deploy/jboss-xa-jdbc.rar
09:00:44,421 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in
.../deploy/jms/jms-ra.rar
09:00:44,468 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in
.../deploy/mail-ra.rar
09:00:44,500 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in
.../deploy/quartz-ra.rar
09:00:44,515 INFO [QuartzResourceAdapter] start quartz!!!
09:00:44,578 INFO [SimpleThreadPool] Job execution threads will use class loader of
thread: main
09:00:44,593 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
09:00:44,593 INFO [RAMJobStore] RAMJobStore initialized.
09:00:44,593 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler'
initialized from default resource file in Quartz package: 'quartz.properties'
09:00:44,593 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
09:00:44,609 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED
started.
09:00:45,140 INFO [ConnectionFactoryBindingService] Bound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name
'java:DefaultDS'
09:00:45,390 INFO [A] Bound to JNDI name: queue/A
09:00:45,390 INFO [B] Bound to JNDI name: queue/B
09:00:45,390 INFO [C] Bound to JNDI name: queue/C
09:00:45,390 INFO [D] Bound to JNDI name: queue/D
09:00:45,390 INFO [ex] Bound to JNDI name: queue/ex
09:00:45,406 INFO [testTopic] Bound to JNDI name: topic/testTopic
09:00:45,406 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
09:00:45,406 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
09:00:45,421 INFO [testQueue] Bound to JNDI name: queue/testQueue
09:00:45,453 INFO [UILServerILService] JBossMQ UIL service available at :
/127.0.0.1:8093
09:00:45,484 INFO [DLQ] Bound to JNDI name: queue/DLQ
09:00:45,609 INFO [ConnectionFactoryBindingService] Bound ConnectionManager
'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name
'java:JmsXA'
09:00:45,750 INFO [ConnectionFactoryBindingService] Bound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=jdbc/ProcessingDataSource' to JNDI name
'java:jdbc/ProcessingDataSource'
09:00:45,750 INFO [ConnectionFactoryBindingService] Bound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=jdbc/ArchiveDataSource' to JNDI name
'java:jdbc/ArchiveDataSource'
09:00:45,750 INFO [ConnectionFactoryBindingService] Bound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=jdbc/LegacyDataSource' to JNDI name
'java:jdbc/LegacyDataSource'
09:00:45,765 INFO [ConnectionFactoryBindingService] Bound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=instance1/KronosDS' to JNDI name
'java:instance1/KronosDS'
09:00:45,859 WARN [JAXWSDeployerHookPreJSE] Cannot load servlet class:
com.acs.cfs.kidstar.webservice.KidStarPortletJSEEndpoint
09:00:45,890 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/ROOT.war/
09:00:46,359 INFO [WebappClassLoader]
validateJarFile(C:\JBoss\jboss-4.2.2.GA\server\sdu360_ny\.\deploy\ROOT.war\WEB-INF\lib\servlet-api-2.5.jar)
- jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class:
javax/servlet/Servlet.class
09:00:47,062 INFO [[/]] Initializing Spring root WebApplicationContext
09:00:47,062 INFO [ContextLoader] Root WebApplicationContext: initialization started
09:00:47,109 INFO [XmlWebApplicationContext] Refreshing
org.springframework.web.context.support.XmlWebApplicationContext@66b06b: display name
[Root WebApplicationContext]; startup date [Thu Feb 19 09:00:47 CST 2009]; root of context
hierarchy
09:00:47,203 INFO [XmlBeanDefinitionReader] Loading XML bean definitions from
ServletContext resource [/WEB-INF/spring/applicationContext.xml]
09:00:47,546 INFO [XmlBeanDefinitionReader] Loading XML bean definitions from
ServletContext resource [/WEB-INF/spring/applicationContext-security.xml]
09:00:47,781 INFO [XmlBeanDefinitionReader] Loading XML bean definitions from
ServletContext resource [/WEB-INF/spring/applicationContext-webservices.xml]
09:00:47,796 INFO [XmlWebApplicationContext] Bean factory for application context
[org.springframework.web.context.support.XmlWebApplicationContext@66b06b]:
org.springframework.beans.factory.support.DefaultListableBeanFactory@1a40fff
-----------------------------------------------------------------------------------------------------------------------------------------------------
JBoss v5.0GA (jdk6):
----------------------------------
09:09:54,718 INFO [ServerImpl] Starting JBoss (Microcontainer)...
09:09:54,718 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.GA (build:
SVNTag=JBoss_5_0_0_GA date=200812042120)
09:09:54,718 INFO [ServerImpl] Bootstrap URL: null
09:09:54,718 INFO [ServerImpl] Home Dir: C:\JBoss\jboss-5.0.0.GA
09:09:54,718 INFO [ServerImpl] Home URL: file:/C:/JBoss/jboss-5.0.0.GA/
09:09:54,718 INFO [ServerImpl] Library URL: file:/C:/JBoss/jboss-5.0.0.GA/lib/
09:09:54,718 INFO [ServerImpl] Patch URL: null
09:09:54,718 INFO [ServerImpl] Common Base URL: file:/C:/JBoss/jboss-5.0.0.GA/common/
09:09:54,718 INFO [ServerImpl] Common Library URL:
file:/C:/JBoss/jboss-5.0.0.GA/common/lib/
09:09:54,718 INFO [ServerImpl] Server Name: sdu360il
09:09:54,718 INFO [ServerImpl] Server Base Dir: C:\JBoss\jboss-5.0.0.GA\server
09:09:54,718 INFO [ServerImpl] Server Base URL: file:/C:/JBoss/jboss-5.0.0.GA/server/
09:09:54,718 INFO [ServerImpl] Server Config URL:
file:/C:/JBoss/jboss-5.0.0.GA/server/sdu360il/conf/
09:09:54,718 INFO [ServerImpl] Server Home Dir: C:\JBoss\jboss-5.0.0.GA\server\sdu360il
09:09:54,718 INFO [ServerImpl] Server Home URL:
file:/C:/JBoss/jboss-5.0.0.GA/server/sdu360il/
09:09:54,718 INFO [ServerImpl] Server Data Dir:
C:\JBoss\jboss-5.0.0.GA\server\sdu360il\data
09:09:54,718 INFO [ServerImpl] Server Library URL:
file:/C:/JBoss/jboss-5.0.0.GA/server/sdu360il/lib/
09:09:54,718 INFO [ServerImpl] Server Log Dir:
C:\JBoss\jboss-5.0.0.GA\server\sdu360il\log
09:09:54,718 INFO [ServerImpl] Server Native Dir:
C:\JBoss\jboss-5.0.0.GA\server\sdu360il\tmp\native
09:09:54,718 INFO [ServerImpl] Server Temp Dir:
C:\JBoss\jboss-5.0.0.GA\server\sdu360il\tmp
09:09:54,718 INFO [ServerImpl] Server Temp Deploy Dir:
C:\JBoss\jboss-5.0.0.GA\server\sdu360il\tmp\deploy
09:09:55,203 INFO [ServerImpl] Starting Microcontainer,
bootstrapURL=file:/C:/JBoss/jboss-5.0.0.GA/server/sdu360il/conf/bootstrap.xml
09:09:55,703 INFO [VFSCacheFactory] Initializing VFSCache
[org.jboss.virtual.plugins.cache.IterableTimedVFSCache]
09:09:55,703 INFO [VFSCacheFactory] Using VFSCache [IterableTimedVFSCache{lifetime=1800,
resolution=60}]
09:09:55,937 INFO [CopyMechanism] VFS temp dir:
C:\JBoss\jboss-5.0.0.GA\server\sdu360il\tmp
09:09:55,953 INFO [ZipEntryContext] VFS force nested jars copy-mode is enabled.
09:09:56,718 INFO [ServerInfo] Java version: 1.6.0_06,Sun Microsystems Inc.
09:09:56,718 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 10.0-b22,Sun
Microsystems Inc.
09:09:56,718 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
09:09:56,765 INFO [JMXKernel] Legacy JMX core initialized
09:09:58,140 INFO [ProfileServiceImpl] Loading profile: sdu360il from:
org.jboss.system.server.profileservice.repository.SerializableDeploymentRepository@a4ed99(root=C:\JBoss\jboss-5.0.0.GA\server,
key=org.jboss.profileservice.spi.ProfileKey@d6ccf6ce[domain=default,server=default,name=sdu360il])
09:09:58,140 INFO [ProfileImpl] Using
repository:org.jboss.system.server.profileservice.repository.SerializableDeploymentRepository@a4ed99(root=C:\JBoss\jboss-5.0.0.GA\server,
key=org.jboss.profileservice.spi.ProfileKey@d6ccf6ce[domain=default,server=default,name=sdu360il])
09:09:58,140 INFO [ProfileServiceImpl] Loaded profile:
ProfileImpl@1ec41c0{key=org.jboss.profileservice.spi.ProfileKey(a)d6ccf6ce[domain=default,server=default,name=sdu360il]}
09:09:59,750 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/
09:10:04,984 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core
09:10:04,984 INFO [NativeServerConfig] 3.0.4.SP1
09:10:23,281 INFO [Ejb3DependenciesDeployer] Encountered deployment
AbstractVFSDeploymentContext@20254712{vfsfile:/C:/JBoss/jboss-5.0.0.GA/server/sdu360il/deploy/ROOT.war/}
09:10:23,281 INFO [Ejb3DependenciesDeployer] Encountered deployment
AbstractVFSDeploymentContext@20254712{vfsfile:/C:/JBoss/jboss-5.0.0.GA/server/sdu360il/deploy/ROOT.war/}
09:10:23,281 INFO [Ejb3DependenciesDeployer] Encountered deployment
AbstractVFSDeploymentContext@20254712{vfsfile:/C:/JBoss/jboss-5.0.0.GA/server/sdu360il/deploy/ROOT.war/}
09:10:27,328 INFO [JMXConnectorServerService] JMX Connector server:
service:jmx:rmi://127.0.0.1/jndi/rmi://127.0.0.1:1090/jmxconnector
09:10:27,468 INFO [MailService] Mail Service bound to java:/Mail
09:10:28,968 WARN [JBossASSecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has
been detected that the MessageSucker component which sucks messages from one node to
another has not had its password changed from the installation default. Please see the
JBoss Messaging user guide for instructions on how to do this.
09:10:29,000 WARN [AnnotationCreator] No ClassLoader provided, using TCCL:
org.jboss.managed.api.annotation.ManagementComponent
09:10:29,156 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) -
JBoss Inc.
09:10:29,156 INFO [TransactionManagerService] Setting up property manager MBean and JMX
layer
09:10:29,390 INFO [TransactionManagerService] Initializing recovery manager
09:10:29,593 INFO [TransactionManagerService] Recovery manager configured
09:10:29,593 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
09:10:29,625 INFO [TransactionManagerService] Starting transaction recovery manager
09:10:30,765 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080
09:10:30,765 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
09:10:30,765 INFO [StandardService] Starting service jboss.web
09:10:30,765 INFO [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.1.GA
09:10:30,843 INFO [Catalina] Server startup in 135 ms
09:10:30,859 INFO [TomcatDeployment] deploy, ctxPath=/jbossws,
vfsUrl=jbossws.sar/jbossws-management.war
09:10:31,437 INFO [TomcatDeployment] deploy, ctxPath=/web-console,
vfsUrl=management/console-mgr.sar/web-console.war
09:10:31,734 INFO [TomcatDeployment] deploy, ctxPath=/invoker,
vfsUrl=http-invoker.sar/invoker.war
09:10:31,875 INFO [RARDeployment] Required license terms exist, view
vfszip:/C:/JBoss/jboss-5.0.0.GA/server/sdu360il/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
09:10:31,890 INFO [RARDeployment] Required license terms exist, view
vfszip:/C:/JBoss/jboss-5.0.0.GA/server/sdu360il/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
09:10:31,953 INFO [RARDeployment] Required license terms exist, view
vfszip:/C:/JBoss/jboss-5.0.0.GA/server/sdu360il/deploy/jms-ra.rar/META-INF/ra.xml
09:10:31,968 INFO [RARDeployment] Required license terms exist, view
vfszip:/C:/JBoss/jboss-5.0.0.GA/server/sdu360il/deploy/mail-ra.rar/META-INF/ra.xml
09:10:31,984 INFO [RARDeployment] Required license terms exist, view
vfszip:/C:/JBoss/jboss-5.0.0.GA/server/sdu360il/deploy/quartz-ra.rar/META-INF/ra.xml
09:10:32,078 INFO [SimpleThreadPool] Job execution threads will use class loader of
thread: main
09:10:32,109 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
09:10:32,109 INFO [RAMJobStore] RAMJobStore initialized.
09:10:32,109 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler'
initialized from default resource file in Quartz package: 'quartz.properties'
09:10:32,109 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
09:10:32,109 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED
started.
09:10:33,343 INFO [ConnectionFactoryBindingService] Bound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name
'java:DefaultDS'
09:10:33,593 WARN [QuartzTimerServiceFactory] sql failed: CREATE TABLE
QRTZ_JOB_DETAILS(JOB_NAME VARCHAR(80) NOT NULL, JOB_GROUP VARCHAR(80) NOT NULL,
DESCRIPTION VARCHAR(120) NULL, JOB_CLASS_NAME VARCHAR(128) NOT NULL, IS_DURABLE VARCHAR(1)
NOT NULL, IS_VOLATILE VARCHAR(1) NOT NULL, IS_STATEFUL VARCHAR(1) NOT NULL,
REQUESTS_RECOVERY VARCHAR(1) NOT NULL, JOB_DATA BINARY NULL, PRIMARY KEY
(JOB_NAME,JOB_GROUP))
09:10:33,656 INFO [SimpleThreadPool] Job execution threads will use class loader of
thread: main
09:10:33,656 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
09:10:33,656 INFO [JobStoreCMT] Using db table-based data access locking
(synchronization).
09:10:33,687 INFO [JobStoreCMT] Removed 0 Volatile Trigger(s).
09:10:33,687 INFO [JobStoreCMT] Removed 0 Volatile Job(s).
09:10:33,687 INFO [JobStoreCMT] JobStoreCMT initialized.
09:10:33,687 INFO [StdSchedulerFactory] Quartz scheduler
'JBossEJB3QuartzScheduler' initialized from an externally provided properties
instance.
09:10:33,687 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
09:10:33,718 INFO [JobStoreCMT] Freed 0 triggers from 'acquired' /
'blocked' state.
09:10:33,718 INFO [JobStoreCMT] Recovering 0 jobs that were in-progress at the time of
the last shut-down.
09:10:33,734 INFO [JobStoreCMT] Recovery complete.
09:10:33,750 INFO [JobStoreCMT] Removed 0 'complete' triggers.
09:10:33,750 INFO [JobStoreCMT] Removed 0 stale fired job entries.
09:10:33,750 INFO [QuartzScheduler] Scheduler JBossEJB3QuartzScheduler_$_NON_CLUSTERED
started.
09:10:33,984 INFO [ServerPeer] JBoss Messaging 1.4.1.GA server [0] started
09:10:34,140 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing
enabled, lease period 10000 milliseconds
09:10:34,140 INFO [ConnectionFactory]
org.jboss.jms.server.connectionfactory.ConnectionFactory@1285ffb started
09:10:34,140 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing
enabled, lease period 10000 milliseconds
09:10:34,140 INFO [ConnectionFactory]
org.jboss.jms.server.connectionfactory.ConnectionFactory@1a95b8 started
09:10:34,140 INFO [QueueService] Queue[/queue/DLQ] started, fullSize=200000,
pageSize=2000, downCacheSize=2000
09:10:34,156 WARN [ConnectionFactoryJNDIMapper] supportsFailover attribute is true on
connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory
but post office is non clustered. So connection factory will *not* support failover
09:10:34,156 WARN [ConnectionFactoryJNDIMapper] supportsLoadBalancing attribute is true
on connection factory:
jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is
non clustered. So connection factory will *not* support load balancing
09:10:34,156 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing
enabled, lease period 10000 milliseconds
09:10:34,156 INFO [ConnectionFactory]
org.jboss.jms.server.connectionfactory.ConnectionFactory@e88380 started
09:10:34,156 INFO [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000,
pageSize=2000, downCacheSize=2000
09:10:34,265 INFO [ConnectionFactoryBindingService] Bound ConnectionManager
'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name
'java:JmsXA'
09:10:34,375 INFO [ConnectionFactoryBindingService] Bound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=jdbc/ProcessingDataSource' to JNDI name
'java:jdbc/ProcessingDataSource'
09:10:34,406 INFO [ConnectionFactoryBindingService] Bound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=jdbc/ArchiveDataSource' to JNDI name
'java:jdbc/ArchiveDataSource'
09:10:34,437 INFO [ConnectionFactoryBindingService] Bound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=jdbc/LegacyDataSource' to JNDI name
'java:jdbc/LegacyDataSource'
09:10:34,468 INFO [ConnectionFactoryBindingService] Bound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=instance1/KronosDS' to JNDI name
'java:instance1/KronosDS'
09:10:34,468 INFO [EjbDeployer] installing bean:
ejb/#KronosBatchSchedulerService,uid17222336
09:10:34,468 INFO [EjbDeployer] with dependencies:
09:10:34,468 INFO [EjbDeployer] and supplies:
09:10:34,468 INFO [EjbDeployer] jndi:KronosBatchSchedulerService
09:10:34,515 INFO [PersistenceUnitDeployment] Starting persistence unit
persistence.unit:unitName=#Kidstar
09:10:34,515 ERROR [AbstractKernelController] Error installing to Start:
name=persistence.unit:unitName=#Kidstar state=Create
java.lang.RuntimeException: Specification violation [EJB3 JPA 6.2.1.2] - You have not
defined a non-jta-data-source for a RESOURCE_LOCAL enabled persistence context named:
Kidstar
at
org.jboss.jpa.deployment.PersistenceUnitInfoImpl.<init>(PersistenceUnitInfoImpl.java:124)
at
org.jboss.jpa.deployment.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:285)
--------------------------------------------------------------------------------------------------------------------
Specification violation [EJB3 JPA 6.2.1.2] - You have not defined a
non-jta-data-source for a RESOURCE_LOCAL
------------------------------------------------------------------------------------------------------------
Key: EJBTHREE-1730
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1730
Project: EJB 3.0
Issue Type: Bug
Components: ejb3
Environment: JBoss v5.0
Spring 2.5
Reporter: Spec Dev
Assignee: Carlo de Wolf
The same application that works fine in JBoss 4.2.2 fails in JBoss v5.0 with the
following exception:
13:42:16,343 ERROR [AbstractKernelController] Error installing to Start:
name=persistence.unit:unitName=#MyPU state=Create
java.lang.RuntimeException: Specification violation [EJB3 JPA 6.2.1.2] - You have not
defined a non-jta-data-source for a RESOURCE_LOCAL enabled persistence context named:
MyPU
The persistence unit for the application uses a datasource configured and managed by
Spring.
<?xml version="1.0" encoding="UTF-8"?>
<persistence version="1.0"
xmlns="http://java.sun.com/xml/ns/persistence"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
<persistence-unit name="MyPU"
transaction-type="RESOURCE_LOCAL">
<provider>org.hibernate.ejb.HibernatePersistence</provider>
<properties>
<property name="hibernate.format_sql"
value="true"/>
<property name="hibernate.order_updates"
value="true"/>
<property name="hibernate.hbm2ddl.auto"
value="validate"/>
<property name="hibernate.dialect"
value="org.hibernate.dialect.Oracle10gDialect"/>
<!-- property name="hibernate.transaction.factory_class"
value="org.hibernate.transaction.JTATransactionFactory"/-->
<property name="hibernate.transaction.manager_lookup_class"
value="org.hibernate.transaction.JBossTransactionManagerLookup"/>
</properties>
</persistence-unit>
</persistence>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:38 a.m.
New subject: [JBoss JIRA] Resolved: (EJBTHREE-1730) Specification violation [EJB3 JPA 6.2.1.2] - You have not defined a non-jta-data-source for a RESOURCE_LOCAL
[
https://jira.jboss.org/jira/browse/EJBTHREE-1730?page=com.atlassian.jira....
]
Carlo de Wolf resolved EJBTHREE-1730.
-------------------------------------
Resolution: Rejected
Open a forum thread or file a support case if you have problems configuring your
application correctly.
Specification violation [EJB3 JPA 6.2.1.2] - You have not defined a
non-jta-data-source for a RESOURCE_LOCAL
------------------------------------------------------------------------------------------------------------
Key: EJBTHREE-1730
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1730
Project: EJB 3.0
Issue Type: Bug
Components: ejb3
Environment: JBoss v5.0
Spring 2.5
Reporter: Spec Dev
Assignee: Carlo de Wolf
The same application that works fine in JBoss 4.2.2 fails in JBoss v5.0 with the
following exception:
13:42:16,343 ERROR [AbstractKernelController] Error installing to Start:
name=persistence.unit:unitName=#MyPU state=Create
java.lang.RuntimeException: Specification violation [EJB3 JPA 6.2.1.2] - You have not
defined a non-jta-data-source for a RESOURCE_LOCAL enabled persistence context named:
MyPU
The persistence unit for the application uses a datasource configured and managed by
Spring.
<?xml version="1.0" encoding="UTF-8"?>
<persistence version="1.0"
xmlns="http://java.sun.com/xml/ns/persistence"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
<persistence-unit name="MyPU"
transaction-type="RESOURCE_LOCAL">
<provider>org.hibernate.ejb.HibernatePersistence</provider>
<properties>
<property name="hibernate.format_sql"
value="true"/>
<property name="hibernate.order_updates"
value="true"/>
<property name="hibernate.hbm2ddl.auto"
value="validate"/>
<property name="hibernate.dialect"
value="org.hibernate.dialect.Oracle10gDialect"/>
<!-- property name="hibernate.transaction.factory_class"
value="org.hibernate.transaction.JTATransactionFactory"/-->
<property name="hibernate.transaction.manager_lookup_class"
value="org.hibernate.transaction.JBossTransactionManagerLookup"/>
</properties>
</persistence-unit>
</persistence>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:35 p.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-1730) Specification violation [EJB3 JPA 6.2.1.2] - You have not defined a non-jta-data-source for a RESOURCE_LOCAL
[
https://jira.jboss.org/jira/browse/EJBTHREE-1730?page=com.atlassian.jira....
]
Spec Dev commented on EJBTHREE-1730:
------------------------------------
For anyone having this issue, please edit jpa-deployers-jboss-beans.xml in <server
profile>\deployers\ejb3.deployer\META-INF and comment out the following beans:
- PersistenceParsingDeployer
- PersistenceDeployer
- PersistenceUnitDeployer
My application was tested to work fine in JBoss 4.2.2GA and 4.2.3GA.
JBoss 5.0 would not work as desired unless the entries above were commented out.
Specification violation [EJB3 JPA 6.2.1.2] - You have not defined a
non-jta-data-source for a RESOURCE_LOCAL
------------------------------------------------------------------------------------------------------------
Key: EJBTHREE-1730
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1730
Project: EJB 3.0
Issue Type: Bug
Components: ejb3
Environment: JBoss v5.0
Spring 2.5
Reporter: Spec Dev
Assignee: Carlo de Wolf
The same application that works fine in JBoss 4.2.2 fails in JBoss v5.0 with the
following exception:
13:42:16,343 ERROR [AbstractKernelController] Error installing to Start:
name=persistence.unit:unitName=#MyPU state=Create
java.lang.RuntimeException: Specification violation [EJB3 JPA 6.2.1.2] - You have not
defined a non-jta-data-source for a RESOURCE_LOCAL enabled persistence context named:
MyPU
The persistence unit for the application uses a datasource configured and managed by
Spring.
<?xml version="1.0" encoding="UTF-8"?>
<persistence version="1.0"
xmlns="http://java.sun.com/xml/ns/persistence"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
<persistence-unit name="MyPU"
transaction-type="RESOURCE_LOCAL">
<provider>org.hibernate.ejb.HibernatePersistence</provider>
<properties>
<property name="hibernate.format_sql"
value="true"/>
<property name="hibernate.order_updates"
value="true"/>
<property name="hibernate.hbm2ddl.auto"
value="validate"/>
<property name="hibernate.dialect"
value="org.hibernate.dialect.Oracle10gDialect"/>
<!-- property name="hibernate.transaction.factory_class"
value="org.hibernate.transaction.JTATransactionFactory"/-->
<property name="hibernate.transaction.manager_lookup_class"
value="org.hibernate.transaction.JBossTransactionManagerLookup"/>
</properties>
</persistence-unit>
</persistence>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:10 a.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-1730) Specification violation [EJB3 JPA 6.2.1.2] - You have not defined a non-jta-data-source for a RESOURCE_LOCAL
[
https://jira.jboss.org/jira/browse/EJBTHREE-1730?page=com.atlassian.jira....
]
Marc Kropholler commented on EJBTHREE-1730:
-------------------------------------------
As an alternative to commenting out the jboss beans, you can rename persistence.xml to
e.g. jpa-persistence.xml and explicitly configure
org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean to use this file using
setPersistenceXmlLocation. JBoss won't throw an exception then.
Specification violation [EJB3 JPA 6.2.1.2] - You have not defined a
non-jta-data-source for a RESOURCE_LOCAL
------------------------------------------------------------------------------------------------------------
Key: EJBTHREE-1730
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1730
Project: EJB 3.0
Issue Type: Bug
Components: ejb3
Environment: JBoss v5.0
Spring 2.5
Reporter: Spec Dev
Assignee: Carlo de Wolf
The same application that works fine in JBoss 4.2.2 fails in JBoss v5.0 with the
following exception:
13:42:16,343 ERROR [AbstractKernelController] Error installing to Start:
name=persistence.unit:unitName=#MyPU state=Create
java.lang.RuntimeException: Specification violation [EJB3 JPA 6.2.1.2] - You have not
defined a non-jta-data-source for a RESOURCE_LOCAL enabled persistence context named:
MyPU
The persistence unit for the application uses a datasource configured and managed by
Spring.
<?xml version="1.0" encoding="UTF-8"?>
<persistence version="1.0"
xmlns="http://java.sun.com/xml/ns/persistence"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
<persistence-unit name="MyPU"
transaction-type="RESOURCE_LOCAL">
<provider>org.hibernate.ejb.HibernatePersistence</provider>
<properties>
<property name="hibernate.format_sql"
value="true"/>
<property name="hibernate.order_updates"
value="true"/>
<property name="hibernate.hbm2ddl.auto"
value="validate"/>
<property name="hibernate.dialect"
value="org.hibernate.dialect.Oracle10gDialect"/>
<!-- property name="hibernate.transaction.factory_class"
value="org.hibernate.transaction.JTATransactionFactory"/-->
<property name="hibernate.transaction.manager_lookup_class"
value="org.hibernate.transaction.JBossTransactionManagerLookup"/>
</properties>
</persistence-unit>
</persistence>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6100
days inactive
6368
days old
7 comments
3 participants
participants (3)
-
Carlo de Wolf (JIRA) -
Marc Kropholler (JIRA)
-
Spec Dev (JIRA)