Hi Asad

As per my understanding , this has nothing to do with the bean
You are not closing the resultsets properly
Look into all the connections, statements and the resultsets.

This exception comes when you are not closing the previously opened
resultset

Regards
Hemant



                    "Asadullah
                    Khan"                To:     <[EMAIL PROTECTED]>, 
<[EMAIL PROTECTED]>
                    <asadkhan@cmcl       cc:
                    td.com>              Subject:     Re:      Re: database updates

                    08/20/02 05:20
                    PM






Hi,
    I am getting the following error,
when I call the result set

[IsoacqBatchBean]  Here in rs.next() -
[IsoacqBatchBean] java.sql.SQLException: Exhausted Resultset
[IsoacqBatchBean]       at
oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:114)
[IsoacqBatchBean]       at
oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:156)
[IsoacqBatchBean]       at
oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:219)
[IsoacqBatchBean]       at
oracle.jdbc.driver.OracleStatement.prepare_for_new_get(OracleStatement.java
:2285)
[IsoacqBatchBean]       at
oracle.jdbc.driver.OracleStatement.getStringValue(OracleStatement.java:2430
)
[IsoacqBatchBean]       at
oracle.jdbc.driver.OracleResultSetImpl.getString(OracleResultSetImpl.java:2
85)
[IsoacqBatchBean]       at
org.opentools.minerva.jdbc.ResultSetInPool.getString(ResultSetInPool.java:6
54)
[IsoacqBatchBean]       at
com.cmcltd.paymentgateway.isoacq.Batch.IsoacqBatchBean.getSTAN(IsoacqBatchB
ean.java:609)
[IsoacqBatchBean]       at
com.cmcltd.paymentgateway.isoacq.Batch.IsoacqBatchBean.batch(IsoacqBatchBea
n.java:237)
[IsoacqBatchBean]       at java.lang.reflect.Method.invoke(Native Method)
[IsoacqBatchBean]       at
org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(Statele
ssSessionContainer.java:472)

I am using stateless session beans

regards
Asad
----- Original Message -----
 From: Hemant Arora
 To: [EMAIL PROTECTED]
 Sent: Tuesday, August 20, 2002 5:28 PM
 Subject: Re: database updates

 Hi Asad

 Is there any error thrown by the Second bean
 And can you tell which beans are you using Stateful or stateless

 Regards
 Hemant



                     Asadullah Khan
                     <asadkhan@CMCLTD.       To:
 [EMAIL PROTECTED]
                     COM>                    cc:
                     Sent by: A              Subject:     database updates
                     mailing list for
                     Enterprise
                     JavaBeans
                     development
                     <EJB-INTEREST@JAV
                     A.SUN.COM>


                     08/20/02 04:33 PM
                     Please respond to
                     Asadullah Khan






 Hi all,
     I have a code, which runs fine in jsp, and in java client, but when I
 write the code in session bean, I am not getting the desired output.I am
 using Jboss 2.2

 Actually my code is something like this.

 I call a session bean (sb1) to do some processing, after
 processing it calls a entity bean and updates the status (say Active) in
 the database.

 Then I call a second session bean(sb2), which looks for the status(Active)
 in the database,and
 does processing according to the status.

 when I call the above beans (sb1 & sb2) in a jsp,
 sb2 is able to correctly get the updated status and do processing well.

 but when I call the beans in a session bean,
 though sb1 is able to call the entity bean and update the status,
 when sb2 is accessing the database,It is not able to get the status data
 from result set, though result set is not null.
 any help over this would be greatly appreciated.

 regards
 Asad



 -----------------------Disclaimer------------------------

 The views of the author may not necessarily reflect those
 of the Company. All liability is excluded to the extent
 permitted by law for any claims arising as a result of the
 use of this medium to transmit information by or to
 IT Solutions (India) Pvt. Ltd.

 We have taken precautions to minimize the risk of
 transmitting software viruses, but we advise you to
 carry out your own virus checks on any attachment to
 this message.  We cannot accept liability for any loss or
 damage caused by software viruses.

 ------------------------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".




-----------------------Disclaimer------------------------

The views of the author may not necessarily reflect those
of the Company. All liability is excluded to the extent
permitted by law for any claims arising as a result of the
use of this medium to transmit information by or to
IT Solutions (India) Pvt. Ltd.

We have taken precautions to minimize the risk of
transmitting software viruses, but we advise you to
carry out your own virus checks on any attachment to
this message.  We cannot accept liability for any loss or
damage caused by software viruses.

------------------------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".

Reply via email to