Compiere Web Store 機能しません
loginボタンを押下して、ユーザーとパスワード入力すると以下のエラーになります。
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
java.lang.IllegalArgumentException: Client_ID=0 org.compiere.model.MBPartner.initTemplate(MBPartner.java:371) org.compiere.model.MBPartner.<init>(MBPartner.java:275) org.compiere.model.MBPartner.<init>(MBPartner.java:249) org.compiere.util.WebUser.load(WebUser.java:259) org.compiere.util.WebUser.<init>(WebUser.java:116) org.compiere.util.WebUser.get(WebUser.java:78) org.compiere.util.WebLogin.action(WebLogin.java:219) org.compiere.wstore.LoginServlet.doPost(LoginServlet.java:186) javax.servlet.http.HttpServlet.service(HttpServlet.java:717) javax.servlet.http.HttpServlet.service(HttpServlet.java:810) org.compiere.wstore.StoreFilter.doFilter(StoreFilter.java:108) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
note The full stack trace of the root cause is available in the Apache Tomcat/5.5.9 logs. Apache Tomcat/5.5.9
loginボタンを押下して、ユーザーとパスワード入力すると以下のエラーになります。
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
java.lang.IllegalArgumentException: Client_ID=0 org.compiere.model.MBPartner.initTemplate(MBPartner.java:371) org.compiere.model.MBPartner.<init>(MBPartner.java:275) org.compiere.model.MBPartner.<init>(MBPartner.java:249) org.compiere.util.WebUser.load(WebUser.java:259) org.compiere.util.WebUser.<init>(WebUser.java:116) org.compiere.util.WebUser.get(WebUser.java:78) org.compiere.util.WebLogin.action(WebLogin.java:219) org.compiere.wstore.LoginServlet.doPost(LoginServlet.java:186) javax.servlet.http.HttpServlet.service(HttpServlet.java:717) javax.servlet.http.HttpServlet.service(HttpServlet.java:810) org.compiere.wstore.StoreFilter.doFilter(StoreFilter.java:108) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
note The full stack trace of the root cause is available in the Apache Tomcat/5.5.9 logs. Apache Tomcat/5.5.9