When the service is started, log4j prompts cocould not bind factory to JNDI, log4jjndi

Source: Internet
Author: User

When the service is started, log4j prompts cocould not bind factory to JNDI, log4jjndi

Log4j prompt when the service is started

WARN SessionFactoryObjectFactory: 121-cocould not bind factory to JNDI

Javax. naming. NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java. naming. factory. initial

Cause: <session-factory name = "foo">,

With the configuration of the name attribute, hibernate will try to register this sessionfacotry into jndi, resulting in the above error


Solution: delete the name configuration and retain only the <session-factory>

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.