DB2 Error: [IBM][CLI Driver] CLI0106E Connection is closed. SQLSTATE=08003))
Tracy Rucker
I have looked at IBM reason for this message but know what it means to the weblogic
server. Our DBA isn't getting any errors on his side.
Can anyone help,
Thanks, Tracy
Tracy Rucker
I forgot to mention what IBM stated, they said:
CLI0106E Connection is closed.
Cause: The connection specified by the connection handle is no longer active.
Action: Establish a new connection.
Joseph Weinstein
Tracy Rucker wrote:
> I forgot to mention what IBM stated, they said:
>
> CLI0106E Connection is closed.
> Cause: The connection specified by the connection handle is no longer active.
>
> Action: Establish a new connection.
Can you show us the whole stacktrace of this exception? It would be in
the jdbc log file once you turn on jdbc logging. Essentially, it means
*something* has killed the JDBC driver's connection. It could be a firewall
or network problem, if it isn't the DBMS.
Joe
Joseph Weinstein
Tracy Rucker wrote:
> Here is the whole statement, sure hope you can help..... Thanks for your time :
> )
>
Sure. The stuff below isn't the SQLException you cited in the original
post. The stuff below is server log output. The full staccktrace of the
SQLException will be in the jdbc.log file.
Joe
>
> ####<Apr 7, 2003 10:44:57 AM CDT> <Error> <JTA> <ho00060web5> <prod2appserver3>
> <ExecuteThread: '9' for queue: 'default'> <> <169:59f8c41f6915bb44> <000000> <Name=[EJB
> com.alfains.myalfa.policy.policylist.ejb.entity.policylist.PolicyListEBEJB.findByAlphaSC(java.lang.String,int)],Xid=169:59f8c41f6915bb44(391392),Status=Committed,HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
> since begin=0,seconds left=120,activeThread=Thread[ExecuteThread: '9' for queue:
> 'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=committed,assigned=prod2appserver3),SCInfo[Prod2domain+prod2appserver3]=(state=committed),properties=({weblogic.transaction.name=[EJB
> com.alfains.myalfa.policy.policylist.ejb.entity.policylist.PolicyListEBEJB.findByAlphaSC(java.lang.String,int)],
> weblogic.jdbc=t3://10.36.59.20:7204, LOCAL_ENTITY_TX=true}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=prod2appserver3+10.36.59.20:7204+Prod2domain+,
> Resources={})],CoordinatorURL=prod2appserver3+10.36.59.20:7204+Prod2domain+) completed
> heuristically:
> (weblogic.jdbc.jts.Connection, HeuristicHazard, (javax.transaction.xa.XAException:
> [IBM][CLI Driver] CLI0106E Connection is closed. SQLSTATE=08003)) >
> ####<Apr 7, 2003 10:44:57 AM CDT> <Notice> <EJB> <ho00060web5> <prod2appserver3>
> <ExecuteThread: '9' for queue: 'default'> <> <> <010014> <Error attempting to
> rollback transaction: java.lang.IllegalStateException: Transaction can no longer
> be rolled back. Name=[EJB com.alfains.myalfa.policy.policylist.ejb.entity.policylist.PolicyListEBEJB.findByAlphaSC(java.lang.String,int)],Xid=169:59f8c41f6915bb44(391392),Status=Committed,HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
> since begin=0,seconds left=120,ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=committed,assigned=prod2appserver3),SCInfo[Prod2domain+prod2appserver3]=(state=committed),properties=({weblogic.transaction.name=[EJB
> com.alfains.myalfa.policy.policylist.ejb.entity.policylist.PolicyListEBEJB.findByAlphaSC(java.lang.String,int)],
> weblogic.jdbc=t3://10.36.59.20:7204, LOCAL_ENTITY_TX=true}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=prod2appserver3+10.36.59.20:7204+Prod2domain+,
> Resources={})],CoordinatorURL=prod2appserver3+10.36.59.20:7204+Prod2domain+).
> xid=169:59f8c41f6915bb44, status=Committed>
> java.lang.IllegalStateException: Transaction can no longer be rolled back. Name=[EJB
> com.alfains.myalfa.policy.policylist.ejb.entity.policylist.PolicyListEBEJB.findByAlphaSC(java.lang.String,int)],Xid=169:59f8c41f6915bb44(391392),Status=Committed,HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
> since begin=0,seconds left=120,ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=committed,assigned=prod2appserver3),SCInfo[Prod2domain+prod2appserver3]=(state=committed),properties=({weblogic.transaction.name=[EJB
> com.alfains.myalfa.policy.policylist.ejb.entity.policylist.PolicyListEBEJB.findByAlphaSC(java.lang.String,int)],
> weblogic.jdbc=t3://10.36.59.20:7204, LOCAL_ENTITY_TX=true}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=prod2appserver3+10.36.59.20:7204+Prod2domain+,
> Resources={})],CoordinatorURL=prod2appserver3+10.36.59.20:7204+Prod2domain+).
> xid=169:59f8c41f6915bb44, status=Committed
> at weblogic.transaction.internal.TransactionImpl.throwIllegalStateException(TransactionImpl.java:1492)
> at weblogic.transaction.internal.ServerTransactionImpl.internalRollback(ServerTransactionImpl.java:305)
> at weblogic.transaction.internal.ServerTransactionImpl.rollback(ServerTransactionImpl.java:290)
> at weblogic.ejb20.internal.BaseEJBHome.handleSystemException(BaseEJBHome.java:269)
> at weblogic.ejb20.internal.BaseEJBHome.postHomeInvoke(BaseEJBHome.java:399)
> at weblogic.ejb20.internal.EntityEJBHome.finder(EntityEJBHome.java:465)
> at com.alfains.myalfa.policy.policylist.ejb.entity.policylist.PolicyListEBEJB_wnlglv_HomeImpl.findByAlphaSC(PolicyListEBEJB_wnlglv_HomeImpl.java:242)
> at com.alfains.myalfa.lookup.controller.AlphaCodeSearchServlet.doPost(AlphaCodeSearchServlet.java:145)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
> at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
> at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
> at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2546)
> at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2260)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Tracy Rucker
Here is the whole statement, sure hope you can help..... Thanks for your time :
)
####<Apr 7, 2003 10:44:57 AM CDT> <Error> <JTA> <ho00060web5> <prod2appserver3>
Tracy Rucker
Sender: "Tracy Rucker" <tru...@alfains.com>
Reply-To: "Tracy Rucker" <tru...@alfains.com>
Subject: Re: DB2 Error: [IBM][CLI Driver] CLI0106E Connection is closed.
Newsgroups: weblogic.developer.interest.jdbc
X-User-Info: 68.16.91.170
References: <3e96cb20$2...@newsgroups.bea.com> <3e96cd3a$1...@newsgroups.bea.com> <3E96E484...@bea.com.remove_this> <3e96ec6e$1...@newsgroups.bea.com> <3E96EFFC...@bea.com.remove_this>
NNTP-Posting-Host: 68.16.91.170
X-Original-NNTP-Posting-Host: 68.16.91.170
Message-ID: <3e96f1fd$1...@newsgroups.bea.com>
Date: 11 Apr 2003 09:49:01 -0800
X-Trace: newsgroups.bea.com 1050079741 68.16.91.170 (11 Apr 2003 09:49:01 -0800)
X-Original-Trace: 11 Apr 2003 09:49:01 -0800, 68.16.91.170
Organization: BEA NEWS SITE
Lines: 107
XPident: Unknown
Path: newsgroups.bea.com!not-for-mail
Xref: newsgroups.bea.com weblogic.developer.interest.jdbc:16623
Unfortunately I don't have access to the production servers where this is actually
going on. I will see if I can get our Networking person to give me this log file
but I'm not sure if he will be willing. Will let you know in a bit, thanks again.
Tracy Rucker
Sender: "Tracy Rucker" <tru...@alfains.com>
Reply-To: "Tracy Rucker" <tru...@alfains.com>
Subject: Re: DB2 Error: [IBM][CLI Driver] CLI0106E Connection is closed.
Newsgroups: weblogic.developer.interest.jdbc
X-User-Info: 68.16.91.170
References: <3e96cb20$2...@newsgroups.bea.com> <3e96cd3a$1...@newsgroups.bea.com> <3E96E484...@bea.com.remove_this> <3e96ec6e$1...@newsgroups.bea.com> <3E96EFFC...@bea.com.remove_this>
NNTP-Posting-Host: 68.16.91.170
X-Original-NNTP-Posting-Host: 68.16.91.170
Date: 11 Apr 2003 09:58:32 -0800
X-Trace: newsgroups.bea.com 1050080312 68.16.91.170 (11 Apr 2003 09:58:32 -0800)
X-Original-Trace: 11 Apr 2003 09:58:32 -0800, 68.16.91.170Xref: newsgroups.bea.com weblogic.developer.interest.jdbc:16624
Unfortunately I don't have access to the production servers where this is actually
going on. I will see if I can get our Networking person to give me this log file
but I'm not sure if he will be willing. Will let you know in a bit, thanks again.
Joseph Weinstein <joe.rem...@bea.com.remove_this> wrote:
Tracy Rucker
message from our networking guy:
We don't have JDBC logging turned on right now. Let's see how disabling connection
shrinking works first. If it doesn't we will enable jdbc logging.
Could shrinking be the problem? I think he has it set to 15 minutes. I my orginial
thought was that it is more of an F-5 problem that is setting on top of the weblogic
server but no one agrees with me. What do you think?
As you can tell we have multiple problems and have a deadline of April 24th to
meet for this product. Any help is greatly appreciated. Thanks, Tracy
Joseph Weinstein
Tracy Rucker wrote:
> message from our networking guy:
> We don't have JDBC logging turned on right now. Let's see how disabling connection
> shrinking works first. If it doesn't we will enable jdbc logging.
>
> Could shrinking be the problem? I think he has it set to 15 minutes. I my orginial
> thought was that it is more of an F-5 problem that is setting on top of the weblogic
> server but no one agrees with me. What do you think?
>
> As you can tell we have multiple problems and have a deadline of April 24th to
> meet for this product. Any help is greatly appreciated. Thanks, Tracy
Sure. What version of weblogic is this? Shrinking should contribute to this, but
shrinking is a waste of cycles. I recommend defining the pool to has as many
connections as you expect to need, as the initial and max capacity. All connections
will be made at startup, and will always be available.
Tracy Rucker
We are using 6.1 sp3 at present. I will relay the message about shrinking but I
have a couple more questions. Is it necessary to set the initial and max capacity
the same? I have read in documentation where that is recommended but noone will
listen to me on that subject either. Also about the F-5 load balancer, do other
companies use an outside load balancer to direct traffic to weblogic server? If
so do you know of any problems? I can't say Thanks enough, Tracy
Joseph Weinstein
Tracy Rucker wrote:
> We are using 6.1 sp3 at present. I will relay the message about shrinking but I
> have a couple more questions. Is it necessary to set the initial and max capacity
> the same?
No, but that's the most stable.
> I have read in documentation where that is recommended but noone will
> listen to me on that subject either.
I can talk to them if you want.
> Also about the F-5 load balancer, do other
> companies use an outside load balancer to direct traffic to weblogic server? If
> so do you know of any problems?
I have no knowledge of such....
> I can't say Thanks enough, Tracy
We want you successful...
Joe
Tracy Rucker
Thanks so much for your help today. Networking has changed some things and we are
trying
that for now. If they can't get it to work with their changes, they have said
that they will try your
suggestions. We've been having this same problem for over 3 weeks so maybe something
will get them stirred to try something new. I may be in touch Monday if they don't
get it resolved. Maybe they will listen to me sooner or later. I'm sorry I've
complained but it's really hard to not be able to at least look at the console
and have your opinion respected. I'm real hands on and it's about to kill me.
Thanks again for your help and your patience, Tracy
Joseph Weinstein
Tracy Rucker wrote:
> Thanks so much for your help today. Networking has changed some things and we are
> trying that for now. If they can't get it to work with their changes, they have said
> that they will try your suggestions. We've been having this same problem for over 3 weeks so maybe something
> will get them stirred to try something new. I may be in touch Monday if they don't
> get it resolved. Maybe they will listen to me sooner or later. I'm sorry I've
> complained but it's really hard to not be able to at least look at the console
> and have your opinion respected. I'm real hands on and it's about to kill me.
> Thanks again for your help and your patience, Tracy
Not a problem. They're paying me fairly regularly, and some of the money came from you... ;-)