Sometimes(50% of the time) the loop is successful, but then sometimes I get
an "ejbRemove(): java.lang.NullPointerException".
What's happening? Did the bean remove itself before I called the remove
method? Is there a problem with the pool?
Can you please post the stack trace of the NullPointerException?
- Matt
"Matthew Shinn" <matthe...@bea.com> wrote in message
news:3C433B7C...@bea.com...
What do you do at line 51 in PerformanceBean.java?
Regards,
Slava Imeshev
"Kenneth Chin" <klc...@the-ark.com> wrote in message
news:3c433f98$1...@newsgroups.bea.com...
"Slava Imeshev" <ime...@yahoo.com> wrote in message
news:3c434d2e$1...@newsgroups.bea.com...
public void ejbRemove() throws java.rmi.RemoteException {
// To Do
System.out.println("Calling ejbRemove");
try{
if (_prepStmt != null) _prepStmt.close();
_prepStmt=null;
System.out.println("set _prepStmt to null");
if (_rs != null) _rs.close();
_rs=null;
System.out.println("set _rs to null");
if (_conn!=null) _conn.close();
_conn=null;
System.out.println("set _conn to null");
} //line 51!
catch(Exception e){
System.out.println("ejbRemove(): " + e.getMessage());
throw new java.rmi.RemoteException(e.getMessage());
}
}
"Slava Imeshev" <ime...@yahoo.com> wrote in message
news:3c434d2e$1...@newsgroups.bea.com...
catch (Exception e) {
System.out.println("ejbRemove exception:");
e.printStackTrace();
// You should consider using javax.ejb.EJBException instead
throw new RemoteException("ejbRemoveException", e);
}
-- Rob
The thing is...this only started happening when I upgraded to WLS6.1
But I'm not entirely positive if it wouldn't have happened in previous
versions because I've only
just begun fully testing the ejb.
So I really don't know what's happening here.
"Rob Woollen" <r...@nomail.com> wrote in message
news:3C44C925...@nomail.com...
Thanks again.
Also, we figured out the problem and have fixed it. The problem was we were
closing the statement before we closed
the resultset. I believe when you close the statement, you lose your
resultset, hence the nullpointer.
What's weird is that sometimes it would work, and sometimes it doesn't. I
guess when closing the statement, the resultset
doesn't get lost immediately.
"Rob Woollen" <r...@nomail.com> wrote in message
news:3C460BED...@nomail.com...
java.lang.NullPointerException
at java.util.Hashtable.put(Hashtable.java:380)
at weblogic.security.acl.AbstractListableRealm.authInternal(AbstractList
ableRealm.java:186)
at weblogic.security.acl.AbstractListableRealm.authenticate(AbstractList
ableRealm.java:127)
at weblogic.security.acl.AbstractListableRealm.getUser(AbstractListableR
ealm.java:110)
at weblogic.security.acl.CachingRealm.authenticate(CachingRealm.java:956
)
at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:863)
at weblogic.security.acl.Realm.authenticate(Realm.java:200)
at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at weblogic.security.acl.internal.Security.authenticate(Security.java:13
2)
at weblogic.iiop.IIOPJVMConnection.getUser(IIOPJVMConnection.java:65)
at weblogic.iiop.IIOPJVMConnection.claimSocket(IIOPJVMConnection.java:17
8)
at weblogic.iiop.IIOPJVMConnection.claimSocket(IIOPJVMConnection.java:16
1)
at weblogic.socket.JVMSocketManager.accept(JVMSocketManager.java:167)
at weblogic.t3.srvr.ListenThread$RJVMListenRequest.execute(ListenThread.
java:546)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
please reply soon at
gupta_...@yahoo.com
Thanks and regards
Ram
That is likely a weblogic bug. The problem is, version 6.0 was EOL-ed
quite some time ago. The best option for you would be upgrating
to 6.1 or 8.1.
Regards,
Slava Imeshev
"Ramkrishna kumar" <noad...@noaddress.given> wrote in message news:28267497.1092825858495.JavaMail.root@jserv5...