Missing Session Confirmation Number

1,632 views
Skip to first unread message

ATG Developer

unread,
Mar 9, 2009, 5:30:56 AM3/9/09
to ATG_Tech
Hi,

I am trying to migrate from ATG5.6.1 --> ATG 9.0

We have been using request earlier in our jsps by using the implicit
JSP request object, which we have converted to <%
DynamoHttpServletRequest drequest = ServletUtil.getDynamoRequest
(request); %>

Now, i am getting an error while submitting a form stating Session
timed out and please press back and reload to continue.

I understand the session is not sustained with the request. Can
someone please give some pointers on what the issue could be?

I am using JBoss 4.2 eap, ORacle10g and ATG 9.0 on Windows.


14:34:37,991 INFO [STDOUT] /atg/dynamo/servlet/pagecompile/
DropletEventServlet
14:34:37,991 INFO [STDOUT]

14:47:49,503 INFO [STDOUT] Missing session confirmation number:
Request URI: /store/productlist.jsp, Referer:
http://localhost:8080/store/productlist.jsp?CATID=100986&navAction=jump&navCount=0

Regards,
VJ

Nooruddin Shaik

unread,
Mar 9, 2009, 4:12:59 PM3/9/09
to atg_...@googlegroups.com
Did you add the following in your web.xml?
      <context-param>
          <param-name>atg.session.parentContextName</param-name>
          <param-value>/dyn</param-value>
       </context-param>

  <servlet>
    <servlet-name>SessionNameContextServlet</servlet-name>
    <servlet-class>atg.nucleus.servlet.SessionNameContextServlet</servlet-class>
  </servlet>

Thanks
Shaik

Kartikeya

unread,
Mar 9, 2009, 5:38:10 PM3/9/09
to atg_...@googlegroups.com
ATG has added a param _dynSessConf to all DSP taglib and JHTML generated forms and property setting anchor tags.
This param contains a session confirmation number (a randomly generated long number ) associated with a session. If
_dynSessConf is missing or doesn't match the confirmation number you'll see the warning in your logs and it may skip the
processing of your pages as well.
 
You can either turn off this functionality by setting the following properties to false of  /atg/dynamo/Configuration component:
1. enforceSessionConfirmation
2. warnOnSessionConfirmationFailure
 
Or, delete all the old compiled pages and runtime cached jars.
 
Hope this helps.
 
-Kartik 


Reply all
Reply to author
Forward
0 new messages