[esb-issues] [JBoss JIRA] Closed: (JBESB-1210) NameAlreadyBoundException : remaining name hibernate
Kevin Conner (JIRA)
jira-events at lists.jboss.org
Sat Oct 20 05:09:03 EDT 2007
[ http://jira.jboss.com/jira/browse/JBESB-1210?page=all ]
Kevin Conner closed JBESB-1210.
-------------------------------
Resolution: Duplicate Issue
> NameAlreadyBoundException : remaining name hibernate
> ----------------------------------------------------
>
> Key: JBESB-1210
> URL: http://jira.jboss.com/jira/browse/JBESB-1210
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.2.1 IR2
> Reporter: Tom Cunningham
> Assigned To: Tom Cunningham
> Fix For: 4.2.1
>
>
> I'm seeing this on startup periodically - not fatal, but noisy :
> 22:45:18,599 WARN [SessionFactoryObjectFactory] Could not bind factory to JNDI
> javax.naming.NameAlreadyBoundException; remaining name 'hibernate'
> at org.jnp.server.NamingServer.createSubcontext(NamingServer.java:465)
> at org.jnp.interfaces.NamingContext.createSubcontext(NamingContext.java:944)
> at org.jnp.interfaces.NamingContext.createSubcontext(NamingContext.java:926)
> at org.hibernate.util.NamingHelper.bind(NamingHelper.java:69)
> at org.hibernate.impl.SessionFactoryObjectFactory.addInstance(SessionFactoryObjectFactory.java:90)
> at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:306)
> at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1294)
> at org.jboss.soa.esb.monitoring.MonitoringSessionFactory.init(MonitoringSessionFactory.java:80)
> at org.jboss.soa.esb.monitoring.MonitoringSessionFactory.getInstance(MonitoringSessionFactory.java:68)
> at org.jboss.soa.esb.monitoring.client.OperationsCollector.getClassPatterns(OperationsCollector.java:63)
> at org.jboss.soa.esb.monitoring.client.OperationsCollector.collectData(OperationsCollector.java:133)
> at org.jboss.soa.esb.monitoring.client.OperationsCollectorAction.collectOperations(OperationsCollectorAction.java:72)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:102)
> at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.process(OverriddenActionLifecycleProcessor.java:74)
> at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:273)
> at org.jboss.soa.esb.listeners.message.MessageAwareListener$1.run(MessageAwareListener.java:303)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
> at java.lang.Thread.run(Thread.java:613)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the esb-issues
mailing list