status_code 200 request_uri /user/join01.do exception_type class org.springframework.dao.RecoverableDataAccessException servlet_name action message ### Error querying database. Cause: com.mysql.cj.jdbc.exceptions.CommunicationsException: The last packet successfully received from the server was 44,453,403 milliseconds ago. The last packet sent successfully to the server was 44,453,403 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem. ### The error may exist in file [/www/apache-tomcat-8.5.78/webapps/narmoonja/WEB-INF/classes/egovframework/sqlmap/mappers/commonMapper.xml] ### The error may involve defaultParameterMap ### The error occurred while setting parameters ### SQL: SELECT REGIST_GRADE_SEQ as registGradeSeq, REGIST_USER_DIVISION as registUserDivision, REGIST_STANDARD_MODUEL_ID as registStandardModuelId, REGIST_STANDARD_SEND_YN as registStandardSendYn, SEND_DENY_PHONE as sendDenyPhone, SEND_FORBIDDEN_WORD as sendForbiddenWord, COMMON_KAKAO_CHAT_URL as commonKakaoChatUrl, COMMON_TELEGRAM_CHAT_URL as commonTelegramChatUrl, LOGO_WEB_IMG_URL as logoWebImgUrl, BANNER_WEB_HEIGHT_SIZE as bannerWebHeightSize, BANNER_WEB_IMG_URL_1 as bannerWebImgUrl1, BANNER_WEB_IMG_URL_2 as bannerWebImgUrl2, BANNER_WEB_IMG_URL_3 as bannerWebImgUrl3, LOGO_MOBILE_IMG_URL as logoMobileImgUrl, BANNER_MOBILE_HEIGHT_SIZE as bannerMobileHeightSize, BANNER_MOBILE_IMG_URL_1 as bannerMobileImgUrl1, BANNER_MOBILE_IMG_URL_2 as bannerMobileImgUrl2, BANNER_MOBILE_IMG_URL_3 as bannerMobileImgUrl3, SITE_NM as siteNm, COMPANY_NM as companyNm, OWNER as owner, BIZ_NO as bizNo, MALL_NO as mallNo, ZIP_CODE as zipCode, ADDRESS as address, ADDRESS_2 as address2, PHONE as phone, TEL as tel, FAX as fax, EMAIL as email, CS_1 as cs1, CS_2 as cs2, CS_3 as cs3, CS_4 as cs4, POLICY_NM as policyNm, COPY_RIGHT_YEAR as copyRightYear, COPY_RIGHT_NM as copyRightNm, WORK_NO as workNo, SITE_URL as siteUrl, CASH_FRANCHISE_ID as cashFranchiseId, CASH_FRANCHISE_NM as cashFranchiseNm, CASH_FRANCHISE_OWNER as cashFranchiseOwner, CASH_FRANCHISE_ADDRESS as cashFranchiseAddress, CASH_FRANCHISE_TEL as cashFranchiseTel, BANK_NM as bankNm, BANK_DEPOSITOR as bankDepositor, BANK_ACCOUNT_NO as bankAccountNo, USE_TERM as useTerm, PRIVACY_POLICY as privacyPolicy, AD_SPAM_POLICY as adSpamPolicy, NAVER_SEARCH_PHRASE as naverSearchPhrase, SITE_TOP_TITLE as siteTopTitle, SHARE_IMAGE_URL as shareImageUrl, LOG_SCHEDULER_ON as logSchedulerOn FROM SITE_SETTING WHERE SITE_SEQ = 1 ### Cause: com.mysql.cj.jdbc.exceptions.CommunicationsException: The last packet successfully received from the server was 44,453,403 milliseconds ago. The last packet sent successfully to the server was 44,453,403 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem. ; SQL []; The last packet successfully received from the server was 44,453,403 milliseconds ago. The last packet sent successfully to the server was 44,453,403 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.; nested exception is com.mysql.cj.jdbc.exceptions.CommunicationsException: The last packet successfully received from the server was 44,453,403 milliseconds ago. The last packet sent successfully to the server was 44,453,403 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem. exception org.springframework.dao.RecoverableDataAccessException: ### Error querying database. Cause: com.mysql.cj.jdbc.exceptions.CommunicationsException: The last packet successfully received from the server was 44,453,403 milliseconds ago. The last packet sent successfully to the server was 44,453,403 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem. ### The error may exist in file [/www/apache-tomcat-8.5.78/webapps/narmoonja/WEB-INF/classes/egovframework/sqlmap/mappers/commonMapper.xml] ### The error may involve defaultParameterMap ### The error occurred while setting parameters ### SQL: SELECT REGIST_GRADE_SEQ as registGradeSeq, REGIST_USER_DIVISION as registUserDivision, REGIST_STANDARD_MODUEL_ID as registStandardModuelId, REGIST_STANDARD_SEND_YN as registStandardSendYn, SEND_DENY_PHONE as sendDenyPhone, SEND_FORBIDDEN_WORD as sendForbiddenWord, COMMON_KAKAO_CHAT_URL as commonKakaoChatUrl, COMMON_TELEGRAM_CHAT_URL as commonTelegramChatUrl, LOGO_WEB_IMG_URL as logoWebImgUrl, BANNER_WEB_HEIGHT_SIZE as bannerWebHeightSize, BANNER_WEB_IMG_URL_1 as bannerWebImgUrl1, BANNER_WEB_IMG_URL_2 as bannerWebImgUrl2, BANNER_WEB_IMG_URL_3 as bannerWebImgUrl3, LOGO_MOBILE_IMG_URL as logoMobileImgUrl, BANNER_MOBILE_HEIGHT_SIZE as bannerMobileHeightSize, BANNER_MOBILE_IMG_URL_1 as bannerMobileImgUrl1, BANNER_MOBILE_IMG_URL_2 as bannerMobileImgUrl2, BANNER_MOBILE_IMG_URL_3 as bannerMobileImgUrl3, SITE_NM as siteNm, COMPANY_NM as companyNm, OWNER as owner, BIZ_NO as bizNo, MALL_NO as mallNo, ZIP_CODE as zipCode, ADDRESS as address, ADDRESS_2 as address2, PHONE as phone, TEL as tel, FAX as fax, EMAIL as email, CS_1 as cs1, CS_2 as cs2, CS_3 as cs3, CS_4 as cs4, POLICY_NM as policyNm, COPY_RIGHT_YEAR as copyRightYear, COPY_RIGHT_NM as copyRightNm, WORK_NO as workNo, SITE_URL as siteUrl, CASH_FRANCHISE_ID as cashFranchiseId, CASH_FRANCHISE_NM as cashFranchiseNm, CASH_FRANCHISE_OWNER as cashFranchiseOwner, CASH_FRANCHISE_ADDRESS as cashFranchiseAddress, CASH_FRANCHISE_TEL as cashFranchiseTel, BANK_NM as bankNm, BANK_DEPOSITOR as bankDepositor, BANK_ACCOUNT_NO as bankAccountNo, USE_TERM as useTerm, PRIVACY_POLICY as privacyPolicy, AD_SPAM_POLICY as adSpamPolicy, NAVER_SEARCH_PHRASE as naverSearchPhrase, SITE_TOP_TITLE as siteTopTitle, SHARE_IMAGE_URL as shareImageUrl, LOG_SCHEDULER_ON as logSchedulerOn FROM SITE_SETTING WHERE SITE_SEQ = 1 ### Cause: com.mysql.cj.jdbc.exceptions.CommunicationsException: The last packet successfully received from the server was 44,453,403 milliseconds ago. The last packet sent successfully to the server was 44,453,403 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem. ; SQL []; The last packet successfully received from the server was 44,453,403 milliseconds ago. The last packet sent successfully to the server was 44,453,403 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.; nested exception is com.mysql.cj.jdbc.exceptions.CommunicationsException: The last packet successfully received from the server was 44,453,403 milliseconds ago. The last packet sent successfully to the server was 44,453,403 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.