class Order extends EntityObject {

public void save() {
hibernateSupport.save(this); //if relace hibernate with jdbc here, every things is ok
}

public void setID(String id ) {
this.id = id;
save();
}

public void setName(String value ) {
this.id = id;
save();
}

public void setMemo(String value ) {
this.id = id;
save();
}

public void setAddress(String value ) {
this.id = id;
save();
}

。。。。。。。。
}

class HibernateSupport {
public void save(EntiryObject obj) {
Session sess = factory.openSession();
Transaction tx = null;
try {
tx = sess.beginTransaction();
session.save(obj);
tx.commit();
} catch (Exception e) {
if (tx!=null) tx.rollback();
throw e;
} finally {
sess.close();
}
}
}
System need save and find these entity object frequently, I know these code are very urgly, i dont' want to refactor
them since they are form some stable framework.They can work well in test jsp or test java code, but it will make performance problem
in production env. some times,the system is become very slow , every time it will spent the hibernate code more then 500ms to make
make a save or query operation. When i change the hibernate code to direct jdbc without change the basic structure, everything is ok,
every save call only need 10~50ms. I also find some funny things, in some pc , these code can work well, and in some pc become is very
slow and dircect jdbc is always work well. when i change NIC of slow pc , both of hibernate and dircect jdbc can work well.
Doese it means hibernate make a lot's of request from network ? so is there anyone can give me some advices?
The database is DB28.1, app serve is tomcat 4.1x, and I have used the c3p0 connection pool.

ps. hibernate is 2.1.1, and never use any relations between objects.

You have to learn about the different usages of the Session and database transactions. Don't open a Session for every single operation. Come back once you understand the concepts discussed on that page:

http://www.hibernate.org/168.html

Appreciate your advices, Christian
I know these code are very urgly, but i canno t change them for some reasons. The frame work cannot know how to start and end a session in a transaction. Actually, The framework is not very flexsible, it don't directly call the save method at all, also never use any transaction. I don't dare to change them. i only can change the save method, and choice ejb , jdbc, or hibernate.

So i want to know
1. Since it can work well at jdbcconnection-per-operation pattern, Why it cannot do the same work at hibernate session-per-operation pattern at some pc ?
2. About i mentionted the netcard problem, Could you give me some helpful explain ?

Could you help me ?

ps. I don't want to use filter to make a session-per-request pattern.

Because a Hibernate Session does much more than a JDBC connection. I also doubt your JDBC solution scales. I don't know what the "netcard" problem is. Make sure you check the SQL execution log of Hibernate (enable show_sql in the configuration) to see what Hibernate executes.

You need to refactor or to drop this code. Hibernate, JDBC or EJB can not help for performance if you ignore design patterns and use ugly "frameworks".

When i use direct jdbc, the performance is ok, but i have to persuade sb to
modify these code. If i have to refactor this framework, i can persuade nobody to do .
netcard maybe is NIC.
I have try to use session-per-request in some part of app, and don't watch the imporvement of performance. Maybe i have to remove the transaction for every operation , The app is a little app, few people use it, although use the ulgy pattern, i don't think it should be so slow.

Don't use Hibernate. Use jdbc.