SLED5NZPN8 This fix permits .jsp’s to share backend sessions and also provided a possible portlet performance improvement.
Is there some connection pooling for domino backend ? something to do with the local notesthread init / term stuff ?
Thanks
Subject: connection pooling? yes
Can’t speak specifically for the JSP improvements, but the remote java back-end classes (supported by NCSO.jar) do allow connection pooling. Here’s a recent article that covers this:
Subject: RE: connection pooling? yes
be sure I read your article Steve ! 
Was wondering if this fix for 6.03 was for local access (removing the init / terme thread pb) or something else.
Thanks Steve
Subject: RE: connection pooling? yes
Sorry, sinitThread/stermThread are still needed.
Subject: What’s in this 6.03 fix for JSP and session sharing ?
Michael,
Back-end connection pooling (i.e. the ability to allow multiple sessions to be created with the same ORB - orb = NotesFactory.createORB(); … session = NotesFactory.createSession(“myhost”, orb, request)
has been available in versions prior to 6.03. Since these only cover remote sessions they wouldn’t cover init/term calls.
I would imagine that the fix pulls .jsps inline with the above. Maybe someone from IBM could shed more light on this.
Regards
Wayne
Subject: What’s in this 6.03 fix for JSP and session sharing ?
What’s in the fix is a new class in the tag library, DominoSessionManager, which does not use the orb mechanism described in Steve N’s article. Instead, it really caches the backend Session object when the ‘duration’ attribute of the domino:session tag indicates it should.
By default, for backward compatibility, the duration of a jsp-session is the jsp page. That is problematic if you try to use a controller which jsp:includes other jsps, so in addition to ‘page’, other values for ‘duration’ are ‘request’ and ‘session’ (the length of the HttpSession).
Since local Sessions are in your session, and they keep some Notes thread-local stuff, the Sessions are required to be destroyed in the thread that created them - the tags hide managing this from you, but the DSM really only caches remote Sessions that will last longer than the jsp page.