dAHHH ... BLOODY CLOB!
have you ensured that the write to the clob is in the same transaction as the select for update statement that gets the handle to the clob? you can do this programatically in the saveInfo() method, or preferably, in the deployment descriptor. i think the clob handle is set to null if rollback or commit is called between the select for update and the write to the clob. i know i had this problem (or a similar one) and solved it, just can't remember how. suppose that's what documentation is for! paul http://www.iii.co.uk Interactive Investor International is a leading UK Internet personal finance service that provides individuals with the capability to identify, compare, monitor and buy online a number of financial products and services. Interactive Investor Trading Limited, a subsidiary of Interactive Investor International plc, is regulated by the SFA.
RE: IIS, Orion, virtual host
You can't have two applications on one machine listening on the same port, although they could both use the same IP. Try setting them both to use x.20 and put orion on a different port. Paul -Original Message- From: olivier [mailto:[EMAIL PROTECTED]] Sent: 25 April 2001 13:30 To: Orion-Interest Subject: RE: IIS, Orion, virtual host this is the error message I have: Error starting HTTP-Server: Address in use: JVM_Bind -Original Message- From: Ron White [mailto:[EMAIL PROTECTED]] Sent: 25 April 2001 13:22 To: Orion-Interest Cc: [EMAIL PROTECTED] Subject: RE: IIS, Orion, virtual host What exactly is the error message? There are a couple of different ones pertaining to different config files. Thanks, Ron White -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of olivier Sent: Wednesday, April 25, 2001 3:51 AM To: Orion-Interest Subject: IIS, Orion, virtual host Hi, For some reason, I have set 2 IP addresse to my machine (NT). x.x.x.20 and x.x.x.21. (modification in the connection setting and the hosts file) I have configured IIs to use x.20, on port 80, and Orion x.21 on port 80. Is is because the port are the same that I can't start both of them at the same time (they complain that the address is in use). Or is it possible and I don't know how to do it ??? Thanks, olivier http://www.iii.co.uk Interactive Investor International is a leading UK Internet personal finance service that provides individuals with the capability to identify, compare, monitor and buy online a number of financial products and services. Interactive Investor Trading Limited, a subsidiary of Interactive Investor International plc, is regulated by the SFA.
RE: Problem ( solution) with ejbStore() and Oracle CLOBs
No joy with this but thanks anyway. I haven't noticed any problems with the original solution (below) in the last couple of weeks. -Original Message- From: Dan North [mailto:[EMAIL PROTECTED]] Sent: 11 April 2001 18:00 To: Orion-Interest Subject: Re: Problem ( solution) with ejbStore() and Oracle CLOBs This is more likely to be to do with isolation level than transactionality (although the two are closely related). You might try setting: entity-deployment name="YourBean" isolation="repeatable_read" ... /entity-deployment in your orion-ejb-jar.xml. Disclaimer: I could well be wrong, I often am! Regards, Dan/tastapod At 15:48 11/04/2001 +0100, you wrote: Hi, I have a BMP entity bean that maps to an Oracle table with a CLOB field. I can read the CLOB in OK but when trying to write to it I get an 'ORA-01002: fetch out of sequence' error. This error can be caused by a commit being called between retrieving the CLOB locator with a SELECT... FOR UPDATE and trying to write to the CLOB's output stream. I solved this for ejbCreate() by setting the create() method's transaction attribute to 'Required'. However, I can't give the ejbStore() method a transaction attribute as it can only be called by the container. I have got around this like so: By default, ejbStore() is called by the container after every call to any method in the bean instance, whether or not the bean's state is changed. Implementing the public boolean isModified() method stops ejbStore() being called every time as the container first checks that true is returned by this method. Setting a 'Required', 'Requires New' or 'Mandatory' transaction attribute for all methods that set the 'modified' boolean to true seems to ensure that ejbStore() is now only called inside a transaction. This seems to solve the problem but I'd like to be sure that my assumptions are correct and that this WILL prevent ejbStore() from ever being called outside a transaction. Also, is it possible to set a transaction attribute for ejbStore()? Thanks, Paul http://www.iii.co.uk Interactive Investor International is a leading UK Internet personal finance service that provides individuals with the capability to identify, compare, monitor and buy online a number of financial products and services. Interactive Investor Trading Limited, a subsidiary of Interactive Investor International plc, is regulated by the SFA. -- Dan North VP Development - Cadrion Software Ltd - +44 (0)20 7440 9550 CONFIDENTIALITY This e-mail and any attachments are confidential and may also be privileged. If you are not the named recipient, please notify the sender immediately and do not disclose the contents to another person, use it for any purpose, or store or copy the information in any medium http://www.iii.co.uk Interactive Investor International is a leading UK Internet personal finance service that provides individuals with the capability to identify, compare, monitor and buy online a number of financial products and services. Interactive Investor Trading Limited, a subsidiary of Interactive Investor International plc, is regulated by the SFA.
Problem ( solution) with ejbStore() and Oracle CLOBs
Hi, I have a BMP entity bean that maps to an Oracle table with a CLOB field. I can read the CLOB in OK but when trying to write to it I get an 'ORA-01002: fetch out of sequence' error. This error can be caused by a commit being called between retrieving the CLOB locator with a SELECT... FOR UPDATE and trying to write to the CLOB's output stream. I solved this for ejbCreate() by setting the create() method's transaction attribute to 'Required'. However, I can't give the ejbStore() method a transaction attribute as it can only be called by the container. I have got around this like so: By default, ejbStore() is called by the container after every call to any method in the bean instance, whether or not the bean's state is changed. Implementing the public boolean isModified() method stops ejbStore() being called every time as the container first checks that true is returned by this method. Setting a 'Required', 'Requires New' or 'Mandatory' transaction attribute for all methods that set the 'modified' boolean to true seems to ensure that ejbStore() is now only called inside a transaction. This seems to solve the problem but I'd like to be sure that my assumptions are correct and that this WILL prevent ejbStore() from ever being called outside a transaction. Also, is it possible to set a transaction attribute for ejbStore()? Thanks, Paul http://www.iii.co.uk Interactive Investor International is a leading UK Internet personal finance service that provides individuals with the capability to identify, compare, monitor and buy online a number of financial products and services. Interactive Investor Trading Limited, a subsidiary of Interactive Investor International plc, is regulated by the SFA.
