Bruno, I ran into the same issue with a jBoss 4 to jBoss 5 upgrade. I got jBoss to stop complaining by exploding the JAR, changing the persistence.xml file, rebuilding the jar, and redeploying. The change you make to the config really depends on your deployment environment and how you are running jBoss, I guess... although I think in the end, I just ended up getting rid of the CasPersistence declaration (and the CAS webapp seems to work fine without it in its default configuration).
- Bill On Wed, Apr 28, 2010 at 10:11 AM, Bruno Melloni <[email protected] > wrote: > Yes, that is part of what confuses me. > > > > Cas-server-core-3.3.1.jar is the jar included in the distribution – as is, > I did not even build it. The war worked like a charm on jBoss 4.3. As it > is, I get the error on jBoss 5.0 but preliminary tests (running > cas/login.jsp and cas/logout.jsp) seem to indicate that CAS is functioning > in spite of the error message. > > > > I am not sure why jBoss 5 complains about a JTA data source. I have not > reconfigured CAS to persist to my own databases and am still using CAS’ > default persistence. Stranger yet, in one of my own (unrelated) apps I > have a non-JTA datasource and it also uses > transaction-type="RESOURCE_LOCAL". That application throws no errors in > jBoss 5. > > > > b. > > > > > > *From:* Scott Battaglia [mailto:[email protected]] > *Sent:* Monday, April 26, 2010 8:26 PM > *Subject:* Re: 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: CasPersistence > > > > According to the error message it appears to not like the fact that the > datasource is a JTA data source. Is it not supposed to be RESOURCE_LOCAL if > its a JTA data source? > > > > On Mon, Apr 26, 2010 at 5:25 PM, Bruno Melloni < > [email protected]> wrote: > > We’ve been running CAS 3.3.1 on jBoss 4.3. We setup a new jBoss 5 server > and updated library set, and deployed the CAS server (as is, no rebuilds). > During jBoss startup we got the error below. > > > > I initially thought that the issue was caused by an incompatibility between > the server and libraries in the CAS 3.3.1 server app, or with the CAS code > itself. Besides the server, Spring and Spring Security were upgraded (on > the server, not the CAS application) to their 3.0.2 versions. > > > > The puzzling thing is… I do see a persistence.xml file in > cas-server-core-3.3.1.jar and it **does** contain a CasPersistence unit > with the RESOURCE_LOCAL transaction-type. Also, the ‘cleaning’ log entries > at the end seem to indicate that CAS is up and running in spite of the > error. > > > > Can someone help me decipher what is going on? > > > > Thanks, > > > > bruno > > > > *Error:* > > > > 2010-04-26 15:25:54,472 ERROR > [org.jboss.system.server.profileservice.ProfileServiceBootstrap] (main) > Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS > ERRORS FOR DETAILS): > > > > DEPLOYMENTS IN ERROR: > > Deployment "persistence.unit:unitName=#CasPersistence" is in error due to > the following reason(s): 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: CasPersistence > > > > 2010-04-26 15:25:54,503 INFO [org.apache.coyote.http11.Http11AprProtocol] > (main) Starting Coyote HTTP/1.1 on http-0.0.0.0-8080 > > 2010-04-26 15:25:54,519 INFO [org.apache.coyote.ajp.AjpAprProtocol] (main) > Starting Coyote AJP/1.3 on ajp-0.0.0.0-8009 > > 2010-04-26 15:25:54,534 INFO [org.apache.coyote.http11.Http11Protocol] > (main) Starting Coyote HTTP/1.1 on http-8443 > > 2010-04-26 15:25:54,550 INFO > [org.jboss.bootstrap.microcontainer.ServerImpl] (main) JBoss > (Microcontainer) [5.0.0.GA (build: SVNTag=JBPAPP_5_0_0_GA > date=200910202128)] Started in 1m:31s:549ms > > 2010-04-26 15:26:10,441 INFO > [org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner] > (scheduler_Worker-0) Starting cleaning of expired tickets from ticket > registry at [Mon Apr 26 15:26:10 CDT 2010] > > 2010-04-26 15:26:10,441 INFO > [org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner] > (scheduler_Worker-0) 0 found to be removed. Removing now. > > 2010-04-26 15:26:10,441 INFO > [org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner] > (scheduler_Worker-0) Finished cleaning of expired tickets from ticket > registry at [Mon Apr 26 15:26:10 CDT 2010] > > -- > > You are currently subscribed to [email protected] as: > [email protected] > > > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > > > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > > -- Bill Markmann Counterpoint Consulting, Inc. (p) 571-338-2455 (f) 202-403-3425 (e) [email protected] (w) http://www.counterpointconsulting.com/ -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
