4.5.2

Question

Hi there,
I am using WL 4.5.2 on Sun unix. When my server'side bean try to get a
connection from the
connection pool, I get this error message.
I am using LDAPRealm, however, It works well with Weblogic default realm.
java.lang.NullPointerException
at
weblogic.ejb.internal.StatefulEJBHome.postFind(StatefulEJBHome.java:128)
at
weblogic.security.ldaprealm.LDAPUserEntityHomeImpl.findByPrimaryKey(LDAPUser
EntityHomeImpl.java:101)
at weblogic.security.ldaprealm.LDAPRealm.getUser(LDAPRealm.java:168)
at weblogic.security.acl.Security.getUser(Security.java:282)
at weblogic.jdbcbase.jts.Driver.connect(Driver.java:115)
at java.sql.DriverManager.getConnection(Compiled Code)
at java.sql.DriverManager.getConnection(DriverManager.java:137)
at
com.galdos.db.DBConnection.getJDBCConnection(DBConnection.java:129)
at
com.galdos.db.DBConnection.getJDBCConnection(DBConnection.java:112)
at com.galdos.ejb.EJBSessionBean.open(EJBSessionBean.java:172)
at
com.galdos.ejb.UserManager.UserManagerBean.getPrimaryKey(UserManagerBean.jav
a:630)
at
com.galdos.ejb.UserManager.UserManagerBeanEOImpl.getPrimaryKey(UserManagerBe
anEOImpl.java:188)
at
com.galdos.ejb.UserManager.UserManagerBeanEOImpl_WLSkel.invoke(UserManagerBe
anEOImpl_WLSkel.java:121)
at
weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAda
pter.java:261)
at
weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandle
r.java:49)
at
weblogic.rmi.extensions.BasicRequestDispatcher$BasicExecuteRequest.execute(B
asicRequestDispatcher.java:128)
at weblogic.t3.srvr.ExecuteThread.run(Compiled Code)
Tue Aug 01 11:44:06 GMT-07:00 2000:<I> <EJB> Ignoring exception during
rollback
of transaction: '965155359530_1', rollback was triggered by EJB exception:
java.rmi.RemoteException: ; nested exception is:
java.sql.SQLException: java.lang.NullPointerException
java.sql.SQLException: java.lang.NullPointerException
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Exception.<init>(Compiled Code)
at java.sql.SQLException.<init>(SQLException.java:82)
at weblogic.jdbcbase.jts.Driver.connect(Driver.java:344)
at java.sql.DriverManager.getConnection(Compiled Code)
at java.sql.DriverManager.getConnection(DriverManager.java:137)
at
com.galdos.db.DBConnection.getJDBCConnection(DBConnection.java:129)
at
com.galdos.db.DBConnection.getJDBCConnection(DBConnection.java:112)
at com.galdos.ejb.EJBSessionBean.open(EJBSessionBean.java:172)
at
com.galdos.ejb.UserManager.UserManagerBean.getPrimaryKey(UserManagerBean.jav
a:630)
at
com.galdos.ejb.UserManager.UserManagerBeanEOImpl.getPrimaryKey(UserManagerBe
anEOImpl.java:188)
at
com.galdos.ejb.UserManager.UserManagerBeanEOImpl_WLSkel.invoke(UserManagerBe
anEOImpl_WLSkel.java:121)
at
weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAda
pter.java:261)
at
weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandle
r.java:49)
at
weblogic.rmi.extensions.BasicRequestDispatcher$BasicExecuteRequest.execute(B
asicRequestDispatcher.java:128)
at weblogic.t3.srvr.ExecuteThread.run(Compiled Code)
rollback exception:
java.lang.IllegalStateException: java.lang.NullPointerException
at weblogic.jts.internal.CoordinatorImpl.rollback(Compiled Code)
at weblogic.jts.internal.TxContext.rollback(TxContext.java:268)
at
weblogic.ejb.internal.StatelessEJBObject.rollback(StatelessEJBObject.java:13
8)
at
weblogic.ejb.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:260)
at
com.galdos.ejb.UserManager.UserManagerBeanEOImpl.getPrimaryKey(UserManagerBe
anEOImpl.java:194)
at
com.galdos.ejb.UserManager.UserManagerBeanEOImpl_WLSkel.invoke(UserManagerBe
anEOImpl_WLSkel.java:121)
at
weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAda
pter.java:261)
at
weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandle
r.java:49)
at
weblogic.rmi.extensions.BasicRequestDispatcher$BasicExecuteRequest.execute(B
asicRequestDispatcher.java:128)
at weblogic.t3.srvr.ExecuteThread.run(Compiled Code)
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Exception.<init>(Compiled Code)
at java.lang.RuntimeException.<init>(RuntimeException.java:47)
at
java.lang.IllegalStateException.<init>(IllegalStateException.java:45)
at weblogic.jts.internal.TxContext.rollback(TxContext.java:274)
at
weblogic.ejb.internal.StatelessEJBObject.rollback(StatelessEJBObject.java:13
8)
at
weblogic.ejb.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:260)
at
com.galdos.ejb.UserManager.UserManagerBeanEOImpl.getPrimaryKey(UserManagerBe
anEOImpl.java:194)
at
com.galdos.ejb.UserManager.UserManagerBeanEOImpl_WLSkel.invoke(UserManagerBe
anEOImpl_WLSkel.java:121)
at
weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAda
pter.java:261)
at
weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandle
r.java:49)
at
weblogic.rmi.extensions.BasicRequestDispatcher$BasicExecuteRequest.execute(B
asicRequestDispatcher.java:128)
at weblogic.t3.srvr.ExecuteThread.run(Compiled Code)
anybody can give me some hints?
Thanks a lot
Michael

Answer 1

Try turning on verbose gc to see if the VM might be garbage collecting.
          mark
          Ryan Powers wrote:
          > I am using weblogic 4.5.2. I am seeing some strange behavior handling http
          > requests. Basically the server seem to hang or hiccup periodically outside
          > of the code that I have written. For instance, I am posting to a servlet.
          > The servlet invokes an ejb, get a return and responds to the calling client.
          > When run under load, the maximum time of the entire method invocation inside
          > the servlet is about .6 seconds. Never more. However, the client
          > applciation is seeing a few requests take anywhere from 2 - 3.5 seconds.
          > This is repeatable. It seems weblogic is hanging slightly periodically
          > throughout the test. This occurs in a small percentage of cases (less than
          > 1%). But this delayed response is not acceptable and difficult to explain.
          > I have tried using iis to front end the http requests and proxy them to
          > weblogic. I have also tried using a jsp implementation instead of a
          > servlet. And I have tried installing service pack 1. None of it seems to
          > help.
          >
          > Has anyone seen anything like this, or have any ideas what could be causing
          > it. I would try a newer release of weblogic to see if it helped. But I am
          > pretty much locked into this version.