Context is read only exception

[Justin Howard]

Hi All,

I am using Hibernate. It works fine, but I have this exception in my logs. What should I look for ?

   
WARN SessionFactoryObjectFactory:123 - Could not unbind factory from JNDI
javax.naming.NamingException: Context is read only
	at org.apache.naming.NamingContext.checkWritable(NamingContext.java:903)
	at org.apache.naming.NamingContext.unbind(NamingContext.java:243)
	at org.apache.naming.NamingContext.unbind(NamingContext.java:282)
	at org.apache.naming.SelectorContext.unbind(SelectorContext.java:241)
	at javax.naming.InitialContext.unbind(Unknown Source)
	at org.hibernate.impl.SessionFactoryObjectFactory.removeInstance(SessionFactoryObjectFactory.java:116)
	at org.hibernate.impl.SessionFactoryImpl.close(SessionFactoryImpl.java:715)
	at com.aexp.freelancerdb.actions.SavePosAction.doPost(SavePosAction.java:107)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:630)
	at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:436)
	at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:374)
	at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:302)
	at com.aexp.freelancerdb.servlet.Controller.doPost(Controller.java:42)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)


 

Thanks

[Paul Sturrock]

Tomcat's JNDI implementation is read only I believe. The error you are seeing is the SessionFactory trying to remove itself from JNDI, so its not that serious, all you are getting is an ungraceful shutdown. How do you configure your SessionFactory to bind it in JNDI in the first place?

[Justin Howard]

Thanks for the reply.

   
<Context debug="5" reloadable="true">
  	<Logger className="org.apache.catalina.logger.FileLogger" prefix="jndi_ds_log" suffix=".txt" timestamp="true"/>
	<Resource 
		name="jdbc/dsnappname"
		auth="Container"
		type="javax.sql.DataSource"
		factory="org.apache.commons.dbcp.BasicDataSourceFactory"
		driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDriver" 
		url="full url"
		username="user"
		password="pass"
		maxActive="100"
		maxIdle="30"
		maxWait="10000"
		removeAbandoned="true" />	
</Context>

This is in my hibernate.cfg.xml

   
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE hibernate-configuration PUBLIC
 "-//Hibernate/Hibernate Configuration DTD 3.0//EN"
 "http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd">

<hibernate-configuration>
        <session-factory>
                <!-- Database connection settings -->
                <property name="dialect">org.hibernate.dialect.SQLServerDialect</property>
  				<property name="connection.datasource">java:comp/env/jdbc/dsnappname</property>
				<property name="connection.pool_size">1</property>
                <!-- Echo all sql to sdtout -->
                <property name="show_sql">false</property>

               <!-- List all the Java classes we have mapped here -->
				<mapping resource="com/aexp/appname/emp/Contractor.hbm.xml"/>
					
		   </session-factory>
</hibernate-configuration>

Thanks

[Paul Sturrock]

None of that will bind the SessionFactory in JNDI - do you have a hibernate.properties file kicking around in your deployment too? Its the hibernate.session_factory_name property that tells Hibernate to bind the SessionFactory in JNDI itself, if you are not using that I'm assuming you are trying to bind it manually?

[Justin Howard]

Thanks for the reply.

No I dont have any hibernate.properties file. Just the cfg.xml file.
When does the binding actually take place.

Thanks

[Paul Sturrock]

The binding takes place (if Hibernate is doing it) when you create your SessionFactory. If you don't specify hibernate.session_factory_name Hibernate does not try to bind anything. Have you ever set it? Could you have an older version of your configuration deployed somehow?