Hi Prasad,

Thanks for your response, but as you can see from my mail, I was not having problem at 
the time of creation of a record. Instead it was at the time of updation of the same.
However, after much R&D, I seem to have figured out that it has something to do with 
the JDBC driver in SP4 of Weblogic 6.1 as mentioned @ 
http://e-docs.bea.com/wls/docs61/notes/issues.html#1076904.
So, I got my own Oracle JDBC driver - classes12.zip & put that in the CLASSPATH in 
startWebLogic.cmd before weblogic_sp.jar entry & it worked for me :) 
Maybe, you can try out the same & see if your problems also get resolved with this 
driver.

Cheers,
Prateek

-----Original Message-----
From: Prasad Lanka [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 27, 2002 8:38 PM
To: [EMAIL PROTECTED]
Subject: Re: Weblogic 6.1 sp4 & JDK 1.4.1_01 CMP problem


hi,

I too faced the same problem in WL 6.1 SP 4 but with a numeric field.  This
field is part of a foreign key to a mapping table.  When I am trying to insert
the record, it failed with error - 'parent record not found'.  I disabled the
constraint and insert the value.  While we were trying to insert an int value
412, the data that got inserted is in an exponential form.  After debugging for
two days, I decided to use PreparedStatements to insert.  But...  a friend
adviced me to move the numeric (int variables) in the ejbCreate() method.
Earlier these fields were after the date fields, later i moved them before the
date fields and to my surprise, I could insert the record.  I really dont
understand why it worked now.  I verified the ..RDBMS.java file that is
generated when we run ejbc command.  The code is fine in that file.

Prateek, try the above option.  But can anyone explain me why it worked after
moving the fields.  One of my friends tells that it might be 'coz of buffer
overflow.  But he too is not sure.

My problem was there in WL SP2 and above.  In the WL 6.1 base version, I could
insert the record without any modification.  We had experienced lot of problems
on WL 6.1 SP 2 and above, code that worked fine on WL 6.1 base version.  I
doubt that the problem might be J2EE 1.3 version which SP 2 and above support.

regards,
prasad.

-----Original Message-----
From: Prateek.Prakash [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 27, 2002 6:26 PM
To: EJB-INTEREST
Cc: Prateek.Prakash
Subject: Weblogic 6.1 sp4 & JDK 1.4.1_01 CMP problem


Hi Friends,

We have CMPs that insert data into Oracle 8i database. So far everything was
working fine when we were using Weblogic 6.1 sp3 on JDK 1.4.0. But last week
when we migrated to Weblogic 6.1 sp4 on JDK 1.4.1_01, we started facing this
problem wherein whenever we update a string column which is part of the
composite primary key of a table though a CMP, the data in the database gets
corrupted for this field. This happens only during updation & not during the
creation of that record.
Yeah, I know Weblogic doesn't officially support JDK 1.4.x but so far
everything had been working fine for us on JDK 1.4.0. We checked this out if it
was a JDK specific error by running Weblogic 6.1 sp3 on JDK 1.4.1_01 but that
did not seem to cause any problems.
So, in all probability this has something to do with the service pack 4 of
Weblogic.
Any help/pointers in this regard would be greatly appreciated.

TIA,
Prateek


rateekp/pointers in this regard would be greatly appreciated.ce pack 4
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".

Reply via email to