I am having the same exact problem after upgrading iBATIS from 2.2.0.638 to
2.3.0.677 and keeping the DAO package version 2.2.0.638. I don't have this
problem with iBATIS 2.2.0.638 version at all.
We are using JTDS 1.2.2 and MSSQL 2005.
Any suggestions?
thx.
nepalon wrote:
There are two
Who can help me?I am crazy in the question.
--
View this message in context:
http://www.nabble.com/Problem-in-resultMap%3ACause%3A-java.sql.SQLException%3A-Invalid-state%2C-the-ResultSet-object-is-closed-tp16624071p16833562.html
Sent from the iBATIS - User - Java mailing list archive at
I noticed there are only two tables involved, could you try with some
different database engine ? If you still get similar exception, one should
start inspecting your code/iBatis code, if not, definitely it's a driver/db
server problem (try different driver)...
This error happens when your JDBC driver or database does not allow multiple
cursors to be open at the same time within one connection. I've seen it
before. It's usually a simple matter of finding the correct settings to
pass to your JDBC driver (on the db url) to allow multiple cursors (or
Your JDBC code does not match what iBATIS is doing. Try this:
try {
cn = ds.getConnection();
pst1 = cn.prepareStatement(select * from t_softwares);
rs1 = pst1.executeQuery();
while(rs1.next()) {
System.out.println(software: + rs1.getString(1));
pst2 = cn.prepareStatement(select *
I have tried the code and it work well:
Connection cn1 = null;
PreparedStatement pst1 = null;
PreparedStatement pst2 = null;
ResultSet rs1 = null;
ResultSet rs2 = null;
DataSource ds =
Google for sql 2005 HY010 jdbc -db2, and you'll get more info - it
looks like you're not the first person to get this error, but I didn't
see anything that led me to believe that this is a bug in iBATIS -
more likely an issue with the driver, possibly configuration.
Try simplifying the mapped
I try the code and it work well.At first, I get Connection using
DriverManager and work well.I think the bug maybe cause by DataSource that
return Connection from pool,so I try to get Connection using DataSource,but
it work well too.So I still believe the exception causing by iBatis.
Connection
I am sure my DB is configured to allow more than one ResultSet open.As you
see in the above code, the code CategoryModel model =
categoryDao.getCategoryById(273) I code can work well.The code will load the
category object the id is 273 and its parent category object whick the id is
270.In this
I once had a similar problem with DB2. The problem was that the DB was
configured to allow only one open ResultSet per connection.
With your query, you will have more than one open ResultSet - so make sure
your DB is configured to allow this.
Jeff Butler
On Sat, Apr 12, 2008 at 10:47 PM,
The DB i using is SQL Server2005.The error string(HY010) means Invalid
state, the ResultSet object is closed.Somebody says this error cause by
using miscrosoft sql server driver,but I using jtds as my dirver.
Larry Meadors wrote:
This looks like a DB2 issue, you may want to search for that
Which specific version of iBATIS are you using?
Brandon Goodin
On Thu, Apr 10, 2008 at 9:48 PM, nepalon [EMAIL PROTECTED] wrote:
There are two class.：
public class CategoryModel implements Serializable
{
private int id;
private String name;
private int
I have try ibatis version 2.3.0.677 and 2.3.1.710,spring version 2.0.7 and
2.5.3.
--
View this message in context:
http://www.nabble.com/Problem-in-resultMap%3ACause%3A-java.sql.SQLException%3A-Invalid-state%2C-the-ResultSet-object-is-closed-tp16624071p16645060.html
Sent from the iBATIS - User
There are two class.：
public class CategoryModel implements Serializable
{
private int id;
private String name;
private int parentCategoryId;
private CategoryModel parentCategory;
// setter/getter
..
}
public class
14 matches
Mail list logo
