[cas-user] Upgrading from 3.4.5 to 3.4.11 troubles

Bryan Wooten

unread,

Mar 30, 2012, 9:35:26 AM3/30/12

to cas-...@lists.jasig.org

All,

I am trying to up 3.4.11 and am seeing two errors. The first is this:

ThreadName=Thread-1;|2012-03-30 06:58:29,073 ERROR [org.quartz.core.JobRunShell] - <Job DEFAULT.ticketRegistryCleanerJobDetail thr

ew an unhandled Exception: >

org.springframework.scheduling.quartz.JobMethodInvocationFailedException: Invocation of method 'clean' on target class [class org.

jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner] failed; nested exception is javax.persistence.PersistenceException

: org.hibernate.type.SerializationException: could not deserialize

at org.springframework.scheduling.quartz.MethodInvokingJobDetailFactoryBean$MethodInvokingJob.executeInternal(MethodInvoki

ngJobDetailFactoryBean.java:273)

at org.springframework.scheduling.quartz.QuartzJobBean.execute(QuartzJobBean.java:86)

at org.quartz.core.JobRunShell.run(JobRunShell.java:202)

at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:525)

Is this because my 3.4.11 installation is using the same JPA ticket registry DB as my 3.4.5 installation? Do I need a new DB for 3.4.11?

The second error I see is this when I hit the login page:

ThreadName=http-thread-pool-9021-(2);|StandardWrapperValve[cas]: PWC1406: Servlet.service() for servlet cas threw exception

org.springframework.webflow.execution.ActionExecutionException: Exception thrown executing [AnnotatedAction@1d8e362 targetAction =

[EvaluateAction@2c66be expression = generateLoginTicketAction.generate(flowRequestContext), resultExpression = [null]], attribute

s = map[[empty]]] in state 'generateLoginTicket' of flow 'login' -- action execution attributes were 'map[[empty]]'

at org.springframework.webflow.execution.ActionExecutor.execute(ActionExecutor.java:60)

at org.springframework.webflow.engine.ActionState.doEnter(ActionState.java:101)

at org.springframework.webflow.engine.State.enter(State.java:194)

at org.springframework.webflow.engine.Transition.execute(Transition.java:227)

at org.springframework.webflow.engine.DecisionState.doEnter(DecisionState.java:51)

I think there may be an issue with my custom login page but I am not sure. I did modify it to have all the hidden fields that 3.4.11 introduced.

As always, any help is appreciated.

Thanks,

Bryan

-- 
You are currently subscribed to cas-...@lists.jasig.org as: jasig-cas-user...@googlegroups.com
To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user

Rex Posadas

unread,

Mar 30, 2012, 12:40:55 PM3/30/12

to cas-...@lists.jasig.org

To All,

When I try to load the management screen I get the following error:  “The requested API doesn' exist”.  I am loading this screen via https://mydomain:8443/cas/services/manage.html

I can log in just fine with https://mydomain:8443/cas/login . So, at least the works. Is there a configuration change I need to make?

Any ideas on a fix?

Thanks,

Rex

Marvin S. Addison

unread,

Mar 30, 2012, 1:34:56 PM3/30/12

to cas-...@lists.jasig.org

> jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner]
> failed; nested exception is javax.persistence.PersistenceException :
> org.hibernate.type.SerializationException: could not deserialize

> Is this because my 3.4.11 installation is using the same JPA ticket

> registry DB as my 3.4.5 installation? Do I need a new DB for 3.4.11?

Yes. You need to clean out your registry prior to upgrading.

> [EvaluateAction@2c66be expression =
> generateLoginTicketAction.generate(flowRequestContext),
> resultExpression = [null]], attribute s = map[[empty]]] in state
> 'generateLoginTicket' of flow 'login' -- action execution attributes
> were 'map[[empty]]' at
> org.springframework.webflow.execution.ActionExecutor.execute(ActionExecutor.java:60)
>

> I think there may be an issue with my custom login page but I am not
> sure. I did modify it to have all the hidden fields that 3.4.11
> introduced.

Your hunch sounds right. Troubleshooting Spring Webflow errors is hard
because of complexities and machinery inside the SWF engine. Despite
that, turn up the logging for org.springframework.webflow to DEBUG or
TRACE and see it provides anything helpful. Feel free to post additional
log info and we'll see if we can help.

M

jleleu

unread,

Mar 31, 2012, 8:10:22 AM3/31/12

to cas-...@lists.jasig.org

Hi Rex,

Do you see the error message in your logs or on your screen ? And if it's this last case, what do you have in your logs ?
Thanks.
Best regards,
Jérôme

Reply all

Reply to author

Forward