redis.clients.jedis.exceptions.JedisDataException_redis.clients.jedis

來源:互聯網
上載者:User

redis報錯資訊:

三月 22, 2018 10:21:52 上午 org.apache.catalina.core.ApplicationDispatcher invoke嚴重: Servlet.service() for servlet jsp threw exceptionredis.clients.jedis.exceptions.JedisDataException: DENIED Redis is running in protected mode because protected mode is enabled, no bind address was specified, no authentication password is requested to clients. In this mode connections are only accepted from the loopback interface. If you want to connect from external computers to Redis you may adopt one of the following solutions: 1) Just disable protected mode sending the command 'CONFIG SET protected-mode no' from the loopback interface by connecting to Redis from the same host the server is running, however MAKE SURE Redis is not publicly accessible from internet if you do so. Use CONFIG REWRITE to make this change permanent. 2) Alternatively you can just disable the protected mode by editing the Redis configuration file, and setting the protected mode option to 'no', and then restarting the server. 3) If you started the server manually just for testing, restart it with the '--protected-mode no' option. 4) Setup a bind address or an authentication password. NOTE: You only need to do one of the above things in order for the server to start accepting connections from the outside.    at redis.clients.jedis.Protocol.processError(Protocol.java:117)    at redis.clients.jedis.Protocol.process(Protocol.java:142)    at redis.clients.jedis.Protocol.read(Protocol.java:196)    at redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:288)    at redis.clients.jedis.Connection.getBinaryBulkReply(Connection.java:207)    at redis.clients.jedis.BinaryJedis.get(BinaryJedis.java:157)    at com.radiadesign.catalina.session.RedisSessionManager.loadSessionFromRedis(RedisSessionManager.java:397)    at com.radiadesign.catalina.session.RedisSessionManager.findSession(RedisSessionManager.java:330)    at org.apache.catalina.connector.Request.doGetSession(Request.java:2906)    at org.apache.catalina.connector.Request.getSession(Request.java:2298)    at org.apache.catalina.connector.RequestFacade.getSession(RequestFacade.java:895)    at javax.servlet.http.HttpServletRequestWrapper.getSession(HttpServletRequestWrapper.java:231)    at org.apache.catalina.core.ApplicationHttpRequest.getSession(ApplicationHttpRequest.java:570)    at org.apache.catalina.core.ApplicationHttpRequest.getSession(ApplicationHttpRequest.java:515)    at org.apache.jasper.runtime.PageContextImpl.initialize(PageContextImpl.java:137)    at org.apache.jasper.runtime.JspFactoryImpl.internalGetPageContext(JspFactoryImpl.java:109)    at org.apache.jasper.runtime.JspFactoryImpl.getPageContext(JspFactoryImpl.java:60)    at org.apache.jsp.page.errors_jsp._jspService(errors_jsp.java:122)    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)    at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)    at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:438)    at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:396)    at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:340)    at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:292)    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)    at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:720)    at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:468)    at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:391)    at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:318)    at org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:445)    at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:304)    at org.apache.catalina.core.StandardHostValve.throwable(StandardHostValve.java:399)    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:159)    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)    at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:616)    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88)    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:522)    at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1095)    at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:672)    at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:277)    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)    at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)    at java.lang.Thread.run(Thread.java:745)三月 22, 2018 10:21:52 上午 org.apache.catalina.core.StandardHostValve custom嚴重: Exception Processing ErrorPage[errorCode=500, location=/page/errors.jsp]org.apache.jasper.JasperException: javax.servlet.ServletException: redis.clients.jedis.exceptions.JedisDataException: DENIED Redis is running in protected mode because protected mode is enabled, no bind address was specified, no authentication password is requested to clients. In this mode connections are only accepted from the loopback interface. If you want to connect from external computers to Redis you may adopt one of the following solutions: 1) Just disable protected mode sending the command 'CONFIG SET protected-mode no' from the loopback interface by connecting to Redis from the same host the server is running, however MAKE SURE Redis is not publicly accessible from internet if you do so. Use CONFIG REWRITE to make this change permanent. 2) Alternatively you can just disable the protected mode by editing the Redis configuration file, and setting the protected mode option to 'no', and then restarting the server. 3) If you started the server manually just for testing, restart it with the '--protected-mode no' option. 4) Setup a bind address or an authentication password. NOTE: You only need to do one of the above things in order for the server to start accepting connections from the outside.    at org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:555)    at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:461)    at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:396)    at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:340)    at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:292)    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)    at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:720)    at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:468)    at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:391)    at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:318)    at org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:445)    at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:304)    at org.apache.catalina.core.StandardHostValve.throwable(StandardHostValve.java:399)    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:159)    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)    at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:616)    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88)    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:522)    at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1095)    at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:672)    at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:277)    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)    at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)    at java.lang.Thread.run(Thread.java:745)Caused by: javax.servlet.ServletException: redis.clients.jedis.exceptions.JedisDataException: DENIED Redis is running in protected mode because protected mode is enabled, no bind address was specified, no authentication password is requested to clients. In this mode connections are only accepted from the loopback interface. If you want to connect from external computers to Redis you may adopt one of the following solutions: 1) Just disable protected mode sending the command 'CONFIG SET protected-mode no' from the loopback interface by connecting to Redis from the same host the server is running, however MAKE SURE Redis is not publicly accessible from internet if you do so. Use CONFIG REWRITE to make this change permanent. 2) Alternatively you can just disable the protected mode by editing the Redis configuration file, and setting the protected mode option to 'no', and then restarting the server. 3) If you started the server manually just for testing, restart it with the '--protected-mode no' option. 4) Setup a bind address or an authentication password. NOTE: You only need to do one of the above things in order for the server to start accepting connections from the outside.    at org.apache.jsp.page.errors_jsp._jspService(errors_jsp.java:345)    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)    at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)    at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:438)    ... 24 moreCaused by: redis.clients.jedis.exceptions.JedisDataException: DENIED Redis is running in protected mode because protected mode is enabled, no bind address was specified, no authentication password is requested to clients. In this mode connections are only accepted from the loopback interface. If you want to connect from external computers to Redis you may adopt one of the following solutions: 1) Just disable protected mode sending the command 'CONFIG SET protected-mode no' from the loopback interface by connecting to Redis from the same host the server is running, however MAKE SURE Redis is not publicly accessible from internet if you do so. Use CONFIG REWRITE to make this change permanent. 2) Alternatively you can just disable the protected mode by editing the Redis configuration file, and setting the protected mode option to 'no', and then restarting the server. 3) If you started the server manually just for testing, restart it with the '--protected-mode no' option. 4) Setup a bind address or an authentication password. NOTE: You only need to do one of the above things in order for the server to start accepting connections from the outside.    at redis.clients.jedis.Protocol.processError(Protocol.java:117)    at redis.clients.jedis.Protocol.process(Protocol.java:142)    at redis.clients.jedis.Protocol.read(Protocol.java:196)    at redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:288)    at redis.clients.jedis.Connection.getBinaryBulkReply(Connection.java:207)    at redis.clients.jedis.BinaryJedis.get(BinaryJedis.java:157)    at com.radiadesign.catalina.session.RedisSessionManager.loadSessionFromRedis(RedisSessionManager.java:397)    at com.radiadesign.catalina.session.RedisSessionManager.findSession(RedisSessionManager.java:330)    at org.apache.catalina.connector.Request.doGetSession(Request.java:2906)    at org.apache.catalina.connector.Request.getSession(Request.java:2298)    at org.apache.catalina.connector.RequestFacade.getSession(RequestFacade.java:895)    at javax.servlet.http.HttpServletRequestWrapper.getSession(HttpServletRequestWrapper.java:231)    at org.apache.catalina.core.ApplicationHttpRequest.getSession(ApplicationHttpRequest.java:570)    at org.apache.catalina.core.ApplicationHttpRequest.getSession(ApplicationHttpRequest.java:515)    at org.apache.jasper.runtime.PageContextImpl.initialize(PageContextImpl.java:137)    at org.apache.jasper.runtime.JspFactoryImpl.internalGetPageContext(JspFactoryImpl.java:109)    at org.apache.jasper.runtime.JspFactoryImpl.getPageContext(JspFactoryImpl.java:60)    at org.apache.jsp.page.errors_jsp._jspService(errors_jsp.java:122)    ... 27 more

問題處理: 根據提示資訊進行處理

DENIED Redis is running in protected mode because protected mode is enabled, no bind address was specified, no authentication password is requested to clients. In this mode connections are only accepted from the loopback interface.

If you want to connect from external computers to Redis you may adopt one of the following solutions:

1) Just disable protected mode sending the command ‘CONFIG SET protected-mode no’ from the loopback interface by connecting to Redis from the same host the server is running, however MAKE SURE Redis is not publicly accessible from internet if you do so. Use CONFIG REWRITE to make this change permanent.

2) Alternatively you can just disable the protected mode by editing the Redis configuration file, and setting the protected mode option to ‘no’, and then restarting the server.

3) If you started the server manually just for testing, restart it with the ‘–protected-mode no’ option.

4) Setup a bind address or an authentication password. NOTE: You only need to do one of the above things in order for the server to start accepting connections from the outside.

聯繫我們

該頁面正文內容均來源於網絡整理,並不代表阿里雲官方的觀點,該頁面所提到的產品和服務也與阿里云無關,如果該頁面內容對您造成了困擾,歡迎寫郵件給我們,收到郵件我們將在5個工作日內處理。

如果您發現本社區中有涉嫌抄襲的內容,歡迎發送郵件至: info-contact@alibabacloud.com 進行舉報並提供相關證據,工作人員會在 5 個工作天內聯絡您,一經查實,本站將立刻刪除涉嫌侵權內容。

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.