I integrated TIBCO (rv 6.x) with WLS 6.0 MDBs about 6 months ago. There are a couple of articles on the BEA site (in their JMS FAQ if I remember correctly).
It was a while since I did it and it was only as a proof of concept, but it was fairly easy and seemed to work quite well. I was only using Pub/Sub with TIBCO. BEA provided examples for MQ Series, Sonic MQ, Fiorani and IBUS. Based on these it was straightforward to extend to TIBCO. nI do not know for Orion as I have never used it. Cheers Lawrence -----Original Message----- From: Weston Toby [mailto:[EMAIL PROTECTED]] Sent: Tuesday, 12. February 2002 16:03 To: [EMAIL PROTECTED] Subject: Message Driven Bean (JMS) Hi.. has anyone any experience with intergrating 3rd party vendors (MQSeries, Tibco, Sonic etc) into Orion or BEA App Servers. I have to develop a prototype and documentation seems a bit thin on the ground. Are there any tutorials, examlpes, discussions out there? Help appreciated Toby -----Original Message----- From: Duncan Alexander [mailto:[EMAIL PROTECTED]] Sent: Dienstag, 12. Februar 2002 12:44 To: [EMAIL PROTECTED] Subject: Re: Transaction related problem in Weblogic Server Ankur, It looks to me like SQL server is copping out on you here and wrapping the subsequent error in an EJBException. >>[weblogic.jdbc.mssqlserver4.TdsException: I/O exception while talking to >>the server When you say 4-500 Entity beans, is that separate instances of the same bean type? On an aside if you are using a finder to load 4-500 entities and requesting data from each of them, have you considered accessing this directly from a session layer (EJB1.1). Or using a Home method (EJB2.0)? If Im on the wrong track here then ignore those last questions. regards DGA -----Original Message----- From: A mailing list for Enterprise JavaBeans development [mailto:[EMAIL PROTECTED]] On Behalf Of Ankur Kumar Sent: 12 February 2002 01:08 To: [EMAIL PROTECTED] Subject: [EJB-INT] Transaction related problem in Weblogic Server Hi Guys, I'm using Weblogic Server 6.1 & using Session facade architecture in my project. I faced a hazardous problem, which is causing WL to shut down & so it's fatal. The problem occurs when a Session Bean (TX: RequiresNew) interacts with 400-500 Entity Beans objects (TX: Supports) to fetch some information. It might be due to incorrect handling of transactions. Here is the text, which I took out from log file: --------------- nested within: ------------------ javax.ejb.EJBException - with nested exception: [weblogic.jdbc.mssqlserver4.TdsException: I/O exception while talking to the server, java.io.IOException: Broken pipe] at com.bluefishwireless.administration.bluefishaccesspoint.AEBBluefishAcces sPoi ntBean.ejbFindAllBluefishAccessPoint(AEBBluefishAccessPointBean.java:472 ) at com.bluefishwireless.administration.bluefishaccesspoint.AEBBluefishAcces sPoi ntBean_qiw7r3_Impl.ejbFindAllBluefishAccessPoint(AEBBluefishAccessPointB ean_ qiw7r3_Impl.java:252) at java.lang.reflect.Method.invoke(Native Method) at weblogic.ejb20.manager.BeanManagedPersistenceManager.enumFinder(BeanMana gedP ersistenceManager.java:89) at weblogic.ejb20.manager.BaseEntityManager.enumFinder(BaseEntityManager.ja va:5 98) at weblogic.ejb20.internal.EntityEJBHome.finder(EntityEJBHome.java:447) at com.bluefishwireless.administration.bluefishaccesspoint.AEBBluefishAcces sPoi ntBean_qiw7r3_HomeImpl.findAllBluefishAccessPoint(AEBBluefishAccessPoint Bean _qiw7r3_HomeImpl.java:153) at com.bluefishwireless.administration.bluefishaccesspoint.AEBBluefishAcces sPoi ntBean_qiw7r3_HomeImpl_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296) at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef. java :93) at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:2 65) at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.ja va:2 2) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120) ####<Dec 4, 2001 1:54:38 PM EST> <Error> <JTA> <ham.syd.bluefishwireless.com> <myserver> <ExecuteThread: '10' for queue: 'default'> <> <188:b5b3a6967f28edb9> <000000> <Name=[EJB com.bluefishwireless.administration.bluefishaccesspoint.AEBBluefishAcces sPoi ntBean.findAllBluefishAccessPoint()],Xid=188:b5b3a6967f28edb9(2015687),S tatu s=Rolled back. [Reason=Unknown],HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRep lies OwedOthers=0,seconds since begin=0,seconds left=10,activeThread=Thread[ExecuteThread: '10' for queue: 'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=rolle dbac k,assigned=myserver),SCInfo[mydomain+myserver]=(state=rolledback),proper ties =({weblogic.transaction.name=[EJB com.bluefishwireless.administration.bluefishaccesspoint.AEBBluefishAcces sPoi ntBean.findAllBluefishAccessPoint()], weblogic.jdbc=t3://10.1.64.64:7001, LOCAL_ENTITY_TX=true}),OwnerTransactionManager=ServerTM[ServerCoordinato rDes criptor=(CoordinatorURL=myserver+10.1.64.64:7001+mydomain+, Resources={})],CoordinatorURL=myserver+10.1.64.64:7001+mydomain+) completed heuristically: (weblogic.jdbc.jts.Connection, HeuristicHazard, (javax.transaction.xa.XAException: I/O exception while talking to the server, java.io.EOFException)) > ####<Dec 4, 2001 1:54:38 PM EST> <Notice> <EJB> <ham.syd.bluefishwireless.com> <myserver> <ExecuteThread: '10' for queue: 'default'> <> <> <010014> <Error attempting to rollback transaction: javax.transaction.SystemException: Heuristic hazard: (weblogic.jdbc.jts.Connection, HeuristicHazard, (javax.transaction.xa.XAException: I/O exception while talking to the server, java.io.EOFException)) > javax.transaction.SystemException: Heuristic hazard: (weblogic.jdbc.jts.Connection, HeuristicHazard, (javax.transaction.xa.XAException: I/O exception while talking to the server, java.io.EOFException)) at weblogic.transaction.internal.ServerTransactionImpl.internalRollback(Ser verT ransactionImpl.java:327) at weblogic.transaction.internal.ServerTransactionImpl.rollback(ServerTrans acti onImpl.java:291) at weblogic.ejb20.internal.BaseEJBHome.handleSystemException(BaseEJBHome.ja va:2 67) at weblogic.ejb20.internal.EntityEJBHome.finder(EntityEJBHome.java:458) at com.bluefishwireless.administration.bluefishaccesspoint.AEBBluefishAcces sPoi ntBean_qiw7r3_HomeImpl.findAllBluefishAccessPoint(AEBBluefishAccessPoint Bean _qiw7r3_HomeImpl.java:153) at com.bluefishwireless.administration.bluefishaccesspoint.AEBBluefishAcces sPoi ntBean_qiw7r3_HomeImpl_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296) at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef. java :93) at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:2 65) at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.ja va:2 2) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120) I will really appreciate any feedback asap. Ankur Kumar Bluefish Wireless ======================================================================== === To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help". =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help". =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help". Visit us at http://www.clearstream.com IMPORTANT MESSAGE Internet communications are not secure and therefore Clearstream International does not accept legal responsibility for the contents of this message. The information contained in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any views expressed in this e-mail are those of the individual sender, except where the sender specifically states them to be the views of Clearstream International or of any of its affiliates or subsidiaries. END OF DISCLAIMER =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
