org.hibernate.service.UnknownServiceException: Unknown service requested

Question

I am writing a unit test to for my AbstractHibernateRepository save method. I'm using spring test runner but I get the following exception when it runs:

org.hibernate.service.UnknownServiceException: Unknown service requested [org.hibernate.engine.jdbc.connections.spi.ConnectionProvider]
at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:201)

My Test:

@RunWith(SpringJUnit4ClassRunner.class)
@ContextConfiguration("file:src/main/webapp/WEB-INF/spring/spring-hibernate.xml")
public class AbstractHibernateRepoTest extends AbstractHibernateRepo<Video> {
    @Autowired private SessionFactory sessionFactory;
    private Video video;

    public AbstractHibernateRepoTest() 
    {
        super(Video.class);
    }

    @Before
    public void setUp ()
    {
        video = new Video();
        video.setId("xyz");
        video.setName("Video Name");
        video.setSrc("Source");
        video.setThumbnail("Thumbnail");
        Session session = sessionFactory.openSession();
        session.beginTransaction();
        session.save(video) ;
        session.close();
    }

    @Test
    public void testSaveMethod ()
    {
        video.setId("asa");
        String id = (String) save(video);
        Assert.assertEquals(video.getId(), id);
    }

    @After
    public void breakDown ()
    {
        sessionFactory.close();
    }
}

Repository:

    @Autowired private SessionFactory sessionFactory;
    private final Class<T> clazz;

    public AbstractHibernateRepo(Class<T> clazz) 
    {
        this.clazz = clazz;
    }

    @SuppressWarnings("unchecked")
    @Transactional(rollbackFor = HibernateException.class)
    @Override
    public T findById(Serializable id) 
    {
        if (id == null)
            throw new NullPointerException();

        return (T) getSessionFactory().getCurrentSession().get(getClazz(), id);
    }

    @Override
    @Transactional(rollbackFor = HibernateException.class)
    public Serializable save(T entity) 
    {
        if (entity == null)
            throw new NullPointerException();

        return getSessionFactory().getCurrentSession().save(entity);
    }

    @Override
    @Transactional(rollbackFor = HibernateException.class)
    public void delete(T entity) 
    {
        if (entity == null)
            throw new NullPointerException();

        getSessionFactory().getCurrentSession().delete(entity);
    }

    @Override
    @Transactional(rollbackFor = HibernateException.class)
    public void update(T entity) 
    {
        if (entity == null)
            throw new NullPointerException();

        getSessionFactory().getCurrentSession().update(entity);
    }
}

Spring Config:

<tx:annotation-driven transaction-manager="transactionManager"/> 

<!-- Root Context: defines shared resources visible to all other web components -->
<bean id="dataSource" class="org.apache.commons.dbcp2.BasicDataSource">
    <property name="driverClassName" value="org.h2.Driver"/>
    <property name="url" value="jdbc:h2:mem:db1;DB_CLOSE_DELAY=-1;MVCC=TRUE"/>
    <property name="username" value="someuser"/>
    <property name="password" value="somepassword"/>
</bean>

<bean id="sessionFactory" class="org.springframework.orm.hibernate4.LocalSessionFactoryBean">
    <property name="dataSource" ref="dataSource"/>
    <property name="packagesToScan" value="com.package.model"/>
    <property name="hibernateProperties">
        <props>
            <prop key="hibernate.show_sql">true</prop>
            <prop key="hibernate.hbm2ddl.auto">update</prop>
            <prop key="hibernate.dialect">org.hibernate.dialect.H2Dialect</prop>
        </props>
    </property>
</bean>

<bean id="transactionManager" class="org.springframework.orm.hibernate4.HibernateTransactionManager">
    <property name="sessionFactory" ref="sessionFactory"/>
    <property name="dataSource" ref="dataSource"/>
</bean>

What's causing this problem and how can I fix it?

Solution 1

I might be totally off here, but to me this seems to be a session handling exception. In @Before you open and close session, then in save() you get the current session, which is maybe the one you just closed, leading to an exception. Try if it works if you don't close it in @Before (I know it's not the solution, just to test the theory). You can also try opening a new session in repository instead of getting the current one (also not the solution). The only difference I see compared with our working test setup is that in @Before we also call our repository methods, marked as @Transactional, instead of creating a session directly.

Solution 2

I ran into a similar error except the unknown service was [org.hibernate.cache.spi.RegionFactory] which only occurred when the spring context was started a second time. The problem was due to a partially destroyed beanFactory and transaction manager cache in org.springframework.transaction.interceptor.TransactionAspectSupport. The solution was to call org.springframework.transaction.interceptor.TransactionAspectSupport#clearTransactionManagerCache.

Solution 3

I ran into this same error. I discovered the cause in my case. My experience may help someone else.

I was calling ServiceRegistryBuilder.destroy() in my sessionFactoryCreatedmethod rather than my sessionFactoryClosed method.

Basically, I destroyed my service registry then tried to get a new session, and this makes Hibernate produce the misleading error message.

Therefore, I suggest if people get this error, check they are not closing their session or registry and then trying to get it again.

Solution 4

For any future Google searchers:

When I saw this problem it was caused by an error in the sql script that was being run before the tests started. Scrolling back far enough through the logs revealed the error, so it's worth looking back to check that an UnknownServiceException isn't just a side effect of another problem.

Solution 5

I'm adding onto another answer here from Ramanpreet Singh. I experienced this issue when I used kill -9 on tomcat. I can reliably re-create the problem this way. I have to start up my server, gracefully close it, then start it up again to clear up the problem.

View more solutions