LO25824: DOMINO BUILDERS CAN BE RESOURCE INTENSIVE.

APAR status

• Closed as fixed if next.

Error description

• ISSUE
  The current Domino pooling can be resource intensive.
  
  SYMPTOMS
    -Limited connection pooling, as described in Domino
    Getting Started guide. In short, could only pool the
    Domino Sessions when "Use regen credentials"  was
    specified in the Domino builder.  Meaning, all users
    have the same Domino credentials. In this case, a set
    of Domino sessions (with same credentials) are pooled
    and reused for each http request or Domino Helper call.
  
    -If no pooling was configured,  or if the Runtime Credentials
    input was set to "specify credentials" or "use ltpa token"
    the builder would create a new Session -- which results in
    an underlying tcp/ip connection -- for every http request.
    This is a typical use case.
  
    -Also, if the model contained multiple domino builders
    (perhaps getting data from another database; a typical
    use case), another lotus.domino.Session (and underlying
    tcp/ip connection) would be created with the same
    servername/username/pw combination.   In short, at least
    one new tcp/ip connection to Domino for each http request,
    sometimes more if the model contains multiple Domino builders.
  
  
  ENVIRONMENT
    WPF 6.0.2 and earlier.
  
  RECREATION:
    The recreation of the memory error experienced by the customer
    if very involved and beyond the scope of a simple set of
  steps.
    However, the exception seen by the customer is
  
    java.lang.OutOfMemoryError: JVMCI015:OutOfMemoryError, cannot
  create anymore threads due to memory or resource constraints
   at java.lang.Thread.start(Native Method)
   at lotus.priv.CORBA.iiop.IIOPConnection.<init>(Unknown Source)
   at lotus.priv.CORBA.iiop.ConnectionTable.get(Unknown Source)
   at lotus.priv.CORBA.iiop.ConnectionTable.get(Unknown Source)
   at lotus.priv.CORBA.iiop.Generic.getConnection(Unknown Source)
   at lotus.priv.CORBA.iiop.Generic.locate(Unknown Source)
   at lotus.priv.CORBA.iiop.RepImpl.invokePreamble(Unknown Source)
   at lotus.priv.CORBA.iiop.RepImpl.invoke(Unknown Source)
   at lotus.priv.CORBA.portable.ObjectImpl._invoke(Unknown Source)
   at lotus.domino.corba._IObjectServerStub.createSession(Unknown
  Source)
   at lotus.domino.cso.Session.initSession(Unknown Source)
   at lotus.domino.cso.Session.<init>(Unknown Source)
   at lotus.domino.cso.Session.createSession(Unknown Source)
   at lotus.domino.NotesFactory.createSessionUP(Unknown Source)
   at lotus.domino.NotesFactory.createSession(Unknown Source)
   at
  com.bowstreet.builders.webapp.methods.DominoSessionFactory.makeO
  bject(DominoSessionFactory.java:61)
   at
  com.bowstreet.builders.webapp.methods.DominoSessionPool.getSessi
  on(DominoSessionPool.java:129)
   at
  com.bowstreet.builders.webapp.methods.DominoUtil.getNotesSession
  Internal(DominoUtil.java:1464)
   at
  com.bowstreet.builders.webapp.methods.DominoUtil.getNotesSession
  (DominoUtil.java:431)
   at
  com.bowstreet.builders.webapp.methods.DominoHelper.getDominoSess
  ion(DominoHelper.java:425)
   ... 214 mor
  

Local fix

• No work around is available.
  

Problem summary

• Fixed in 6.0.2.1
  

Problem conclusion

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

• R602 PSY

     UP