Announcement Announcement Module
Collapse
No announcement yet.
Struts 2 Spring 3 hibernate 3 Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Struts 2 Spring 3 hibernate 3

    My friends,
    I have a doubt. my project is generating the following log when I only trigger one action:
    Code:
    10:57:39,726 DEBUG SessionImpl:167 - opened session at timestamp: 5239258561437696
    10:57:39,726 DEBUG SessionImpl:69 - setting flush mode to: AUTO
    10:57:39,726 DEBUG SessionImpl:69 - setting cache mode to: NORMAL
    10:57:40,305 DEBUG SessionImpl:69 - closing session
    10:57:40,305 DEBUG ConnectionManager:69 - connection already null in cleanup : no action
    10:57:40,336 DEBUG SessionImpl:167 - opened session at timestamp: 5239258563936256
    10:57:40,336 DEBUG SessionImpl:69 - setting flush mode to: AUTO
    10:57:40,336 DEBUG SessionImpl:69 - setting cache mode to: NORMAL
    10:57:40,336 DEBUG SessionImpl:69 - closing session
    10:57:40,336 DEBUG ConnectionManager:69 - connection already null in cleanup : no action
    10:57:40,351 DEBUG SessionImpl:167 - opened session at timestamp: 5239258563997696
    10:57:40,351 DEBUG SessionImpl:69 - setting flush mode to: AUTO
    10:57:40,351 DEBUG SessionImpl:69 - setting cache mode to: NORMAL
    10:57:40,351 DEBUG SessionImpl:69 - closing session
    10:57:40,367 DEBUG ConnectionManager:69 - connection already null in cleanup : no action
    10:57:40,367 DEBUG SessionImpl:167 - opened session at timestamp: 5239258564063232
    10:57:40,351 DEBUG SessionImpl:167 - opened session at timestamp: 5239258563997697
    10:57:40,367 DEBUG SessionImpl:69 - setting flush mode to: AUTO
    10:57:40,367 DEBUG SessionImpl:69 - setting cache mode to: NORMAL
    10:57:40,367 DEBUG SessionImpl:69 - closing session
    10:57:40,367 DEBUG ConnectionManager:69 - connection already null in cleanup : no action
    10:57:40,367 DEBUG SessionImpl:69 - setting flush mode to: AUTO
    10:57:40,367 DEBUG SessionImpl:167 - opened session at timestamp: 5239258564063233
    10:57:40,367 DEBUG SessionImpl:69 - setting flush mode to: AUTO
    10:57:40,367 DEBUG SessionImpl:69 - setting cache mode to: NORMAL
    10:57:40,367 DEBUG SessionImpl:69 - closing session
    10:57:40,367 DEBUG ConnectionManager:69 - connection already null in cleanup : no action
    10:57:40,367 DEBUG SessionImpl:69 - setting cache mode to: NORMAL
    10:57:40,367 DEBUG SessionImpl:69 - closing session
    10:57:40,367 DEBUG ConnectionManager:69 - connection already null in cleanup : no action
    10:57:40,367 DEBUG SessionImpl:167 - opened session at timestamp: 5239258564063235
    10:57:40,383 DEBUG SessionImpl:69 - setting flush mode to: AUTO
    10:57:40,383 DEBUG SessionImpl:69 - setting cache mode to: NORMAL
    10:57:40,367 DEBUG SessionImpl:167 - opened session at timestamp: 5239258564063234
    10:57:40,383 DEBUG SessionImpl:69 - closing session
    10:57:40,383 DEBUG SessionImpl:167 - opened session at timestamp: 5239258564128768
    10:57:40,383 DEBUG SessionImpl:69 - setting flush mode to: AUTO
    10:57:40,383 DEBUG SessionImpl:69 - setting cache mode to: NORMAL
    10:57:40,383 DEBUG SessionImpl:69 - setting flush mode to: AUTO
    10:57:40,383 DEBUG SessionImpl:69 - setting cache mode to: NORMAL
    10:57:40,383 DEBUG SessionImpl:69 - closing session
    10:57:40,383 DEBUG ConnectionManager:69 - connection already null in cleanup : no action
    10:57:40,383 DEBUG ConnectionManager:69 - connection already null in cleanup : no action
    10:57:40,383 DEBUG SessionImpl:167 - opened session at timestamp: 5239258564128769
    10:57:40,383 DEBUG SessionImpl:69 - setting flush mode to: AUTO
    10:57:40,383 DEBUG SessionImpl:69 - setting cache mode to: NORMAL
    10:57:40,398 DEBUG SessionImpl:69 - closing session
    10:57:40,398 DEBUG ConnectionManager:69 - connection already null in cleanup : no action
    10:57:40,383 DEBUG SessionImpl:69 - closing session
    10:57:40,398 DEBUG ConnectionManager:69 - connection already null in cleanup : no action
    10:57:40,586 DEBUG SessionImpl:167 - opened session at timestamp: 5239258564960256
    10:57:40,586 DEBUG SessionImpl:69 - setting flush mode to: AUTO
    10:57:40,586 DEBUG SessionImpl:69 - setting cache mode to: NORMAL
    10:57:40,586 DEBUG SessionImpl:69 - closing session
    10:57:40,586 DEBUG ConnectionManager:69 - connection already null in cleanup : no action
    10:57:40,601 DEBUG SessionImpl:167 - opened session at timestamp: 5239258565021696
    10:57:40,601 DEBUG SessionImpl:69 - setting flush mode to: AUTO
    10:57:40,601 DEBUG SessionImpl:69 - setting cache mode to: NORMAL
    10:57:40,617 DEBUG SessionImpl:69 - closing session
    10:57:40,617 DEBUG ConnectionManager:69 - connection already null in cleanup : no action
    10:57:40,617 DEBUG SessionImpl:167 - opened session at timestamp: 5239258565087232
    10:57:40,617 DEBUG SessionImpl:69 - setting flush mode to: AUTO
    10:57:40,633 DEBUG SessionImpl:69 - setting cache mode to: NORMAL
    10:57:40,633 DEBUG SessionImpl:69 - closing session
    10:57:40,633 DEBUG ConnectionManager:69 - connection already null in cleanup : no action
    I would like to know if itīs normal open 5 sessions, when I start one action?
    Thanks.

  • #2
    Why wouldn't it be normal.. It depends on what your action is doing and how you have configured hibernate within spring.

    Comment


    • #3
      hi Marten,
      Then, What I'm wondering is that is a simple action. This is a link that return a success type tiles and not process nothing.
      the code:

      Code:
      public class Calendar() extends AcctionSuport{
        public String executeCalendar(){
          return SUCCESS ;
        }
      }
      why generate seven session for just that ?

      Comment


      • #4
        This action doesn't do much, but that doesn't mean nothing is executed. If you have spring security based on spring that could be a session, if you have logging, ifyou have a opensessioninviewfilter. The fact that it is a simple action doesn't mean nothing is happening on the database level (or maybe on other parts of the page!).

        Comment


        • #5
          this is normal then ..
          Thanks.

          Comment

          Working...
          X