[jboss-user] [Persistence, JBoss/CMP, Hibernate, Database] - Re: Errors in hibernate with Sybase using 4.0.4

[n_sroor]

These messages sometimes causes concern for users. However, most of the time, this message is normal and expected (hence, the DEBUG logging level instead of, say, ERROR or WARN.) 

By default, the server attempts to create the tables that support message persistence. If the tables already exist, a java.sql.SQLException will be thrown. This normally indicates that the tables already exist and do not need to be created. Of course, if the tables do not already exist they will be created, and administrators are not required to create the tables required by JMS as a separate task. 

While the stack trace is usually the feature of the log message that causes concern, it is needed in the DEBUG message. There is no standard SQL exception or message thrown for a "table already exists" type of failure. This means that there is not a general way to report the exception only when the failure is caused by some other problem. Thus, the stack trace is included to facilitate debugging when there is some other failure when creating the tables. 

The automatic creation of the tables can be disabled. Of course, with the feature disabled, the tables must have been created before the Application Server starts for the JMS system to work properly. 

Amjad Farajallah


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4147783#4147783

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4147783