-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 4 posts ] 
Author Message
 Post subject: WARN SessionFactoryObjectFactory:101
PostPosted: Fri Dec 29, 2006 11:01 pm 
Newbie

Joined: Thu Dec 28, 2006 7:10 pm
Posts: 3
Can anyone tell me the meaning of the warning:

WARN SessionFactoryObjectFactory:101 - InitialContext did not implement EventContext.

Thanks.


Top
 Profile  
 
 Post subject:
PostPosted: Sat Dec 30, 2006 4:37 am 
Expert
Expert

Joined: Tue Dec 28, 2004 7:02 am
Posts: 573
Location: Toulouse, France
Are you using JNDI? What is your environment? Do you run in an appserver?

_________________
Baptiste
PS : please don't forget to give credits below if you found this answer useful :)


Top
 Profile  
 
 Post subject:
PostPosted: Sat Dec 30, 2006 1:04 pm 
Newbie

Joined: Thu Dec 28, 2006 7:10 pm
Posts: 3
Thanks for your response.

I'm using c3p0, which I believe uses JNDI. Database is MySQL.

I am using Tomcat/Apache Axis. The code using hibernate is a webservice. This is running on Windows XP.

<!DOCTYPE hibernate-configuration PUBLIC
"-//Hibernate/Hibernate Configuration DTD 3.0//EN"
"http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd">
<hibernate-configuration>
<session-factory name="Test">

<property name="max_fetch_depth">0</property>

<property name="jdbc.batch_versioned_data">true</property>
<property name="jdbc.use_streams_for_binary">true</property>

<property name="proxool.pool_alias">pool1</property>

<property name="dialect">org.hibernate.dialect.MySQLDialect</property>

<property name="connection.driver_class">com.mysql.jdbc.Driver</property>
<property name="connection.url">jdbc:mysql://localhost/test</property>
<property name="connection.username">root</property>
<property name="connection.password"></property>
<!-- We are going to switch from Hibernate's builtin
connection pooling to the C3PO connection pool -->
<!--<property name="connection.pool_size">1</property>-->
<property name="hibernate.c3p0.min_size">2</property>
<property name="hibernate.c3p0.max_size">20</property>
<property name="hibernate.c3p0.timeout">1800</property>
<property name="hibernate.c3p0.max_statements">50</property>

<property name="hibernate.show_sql">false</property>
<property name="hibernate.cache.use_query_cache">false</property>
<property name="hibernate.jdbc.batch_size">0</property>


...


Top
 Profile  
 
 Post subject:
PostPosted: Tue Jan 02, 2007 3:15 am 
C3P0 Developer
C3P0 Developer

Joined: Tue Jan 06, 2004 8:58 pm
Posts: 145
Hi. c3p0 DataSources are JNDI bindable, but for applications that don't otherwise bind or look up c3p0 DataSources, c3p0 won't touch JNDI. SessionFactoryObjectFactory is not a c3p0-related ObjectFactory. (There is a c3p0 ObjectFactory class, C3P0JavaBeanObjectFactory, which is used when JNDI References to c3p0 DataSources are dereferenced.)

Anyway, I don't think the warning you are seeing is c3p0-related.

Good luck!


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 4 posts ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.