JCO Connection constructor: Pool already initialized

Question

Hi Folks,
while i'm configuring a JCO connection to R/3, i got a little problem:
In my class constructor i initialize a client pool.
JCO.addClientPool(sapSID, sapMaxConnections, sapMandant, sapUser, sapPasswort, sapLanguage, sapSystem, sapSystemNumber);
JCO.getClientPoolManager().getPool(sapSID).setMaxWaitTime(maxWaitTime);
problem:
when there is already a client pool, the application crashes
solution:
check if there is already a connection-pool with this name
i tried the following:
1) Check if there's a pool with the name
          if (JCO.getClientPoolManager().getPool(sapSID).getName()==sapSID) {
==> which leads to a null pointer exception because logically there is no pool and as the doc says "if there's no pool, .getPool(String) will return null, which leads to:
2) Check if null
          if (JCO.getClientPoolManager().getPool(sapSID)==null) {
but unfortunately. this won't work either.. null point exception again.
anyone got a hint?
thx in advance,
lars
Message was edited by:
        Lars Paetzold

Answer 1

i remove the waittime part now, but it won't work anyway:
java.lang.NullPointerException
if (JCO.getClientPoolManager().getPool(sapSID)==null) {
     if (JCO.getClientPoolManager().getPool(sapSID).getName().toString()==sapSID.toString()) {
     } else {
          JCO.addClientPool(sapSID, sapMaxConnections, sapMandant, sapUser,
                              sapPasswort, sapLanguage, sapSystem, sapSystemNumber);     
if i'm not checking if there is any kind of pool, everything works fine until i call the application a second time and the pool is already initialized