SqlMapSession session = sqlMapClient.openSession(conn);
try {
session.queryForList("getItemFormat","myname");
} finally {
session.close ();
}
Jeff Butler
On 12/18/06, Ashish Kulkarni <[EMAIL PROTECTED]> wrote:
Hi
How do i replace my existing code with
sqlMapClient.openSession(myConnection);
My excisting code is as below
client.setUserConnection(conn);
client.queryForList("getItemFormat","myname" );
Regards
Ashish
On 12/18/06, Clinton Begin <[EMAIL PROTECTED]> wrote:
>
> GACK.. setUserConnection() is another API we should deprecate.
>
> A cleaner way to do it is:
>
> SqlMapSession session = sqlMapClient.openSession(myConnection);
> try {
> //....do work.....
> } finally {
> session.close ();
> }
>
> Cheers,
> Clinton
>
> On 12/18/06, Jeff Butler < [EMAIL PROTECTED]> wrote:
> >
> > This is very similar to this issue:
> >
> > http://issues.apache.org/jira/browse/IBATIS-66
> >
> > Make sure you're calling client.setUserConnection(null) after
> > processing each query.
> >
> > Jeff Butler
> >
> >
> >
> > On 12/18/06, Ashish Kulkarni <[EMAIL PROTECTED] > wrote:
> > >
> > > Hi
> > > I have attached the sqlmap and xml file with all the sql statements
> > > along this mail.
> > >
> > >
> > >
> > >
> > > On 12/18/06, Larry Meadors <[EMAIL PROTECTED] > wrote:
> > > >
> > > > Can you post your configuration (database and sqlmap)?
> > > >
> > > > Larry
> > > >
> > > >
> > > > On 12/18/06, Ashish Kulkarni < [EMAIL PROTECTED]> wrote:
> > > > > Hi
> > > > > We have a web application running in websphere, and for a while
> > > > we are
> > > > > seeing some hung threads in websphere,
> > > > > do we did some java dump as insturcted by IBM and we are seeing
> > > > some of the
> > > > > following messages in the dump.
> > > > >
> > > > > In our java program before calling SQL statemenet we do the
> > > > following
> > > > > SqlMapClient client =// get connection client from servlet
> > > > context
> > > > > client.setUserConnection(conn);
> > > > > // do furthr processing of calling SQL statements.
> > > > >
> > > > > I am not sure if this is the issue, but this is the messsage in
> > > > the dump
> > > > >
> > > > > com.ibatis.common.util.Throttle.increment seems to be
> > > > > currently executing on
> > > > > 11 servlet threads.
> > > > > Since 100% (11 out of 11) of the threads doing servlet
> > > > work seem
> > > > > to be
> > > > > executing this method, it would seem that there
> > > > > is some possibility that this method and its call
> > > > path
> > > > > may warrant investigation.
> > > > > Servlets affected:
> > > > > com.pfizer.maps.servlet.MapsBaseServlet [11
> > > > > occurrances]
> > > > > Callers (servlet threads only):
> > > > > com.ibm.ws.util.ThreadPool$Worker.run [5]
> > > > >
> > > > > com.pfizer.maps.data.planning.GetPlanningData.getTotalData
> > > > > [2]
> > > > >
> > > > > com.pfizer.maps.data.planning.GetProductionData.getTotalData
> > > > > [2]
> > > > >
> > > > >
> > > > com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI
> > > > > [1]
> > > > >
> > > > > com.ibm.ws.webcontainer.servlet.ServicingServletState.service
> > > > > [1]
> > > > >
> > > > > This is ibaits version
> > > > >
> > > > > Implementation-Title: iBatis sql map
> > > > > Implementation-Version: 2.1.5 build# 582
> > > > >
> > > > > Can anyone explain what this is, and how can we fix this
> > > > >
> > > > > Ashish
> > > > >
> > > > >
> > > >
> > >
> > >
> > >
> >
>
