機一次cpu100%的線上故障
阿新 • • 發佈:2017-09-15
ognl ont 機器 exce quest stack code crm com
某天發現線上crm機器cpu100%了,估計是哪裏寫了個死循環,用jstack看了下
at java.util.HashMap.hash(HashMap.java:351)
at java.util.HashMap.getEntry(HashMap.java:443)
at java.util.HashMap.containsKey(HashMap.java:434)
at ognl.OgnlContext.get(OgnlContext.java:491)
at com.opensymphony.xwork2.ActionContext.get(ActionContext.java:341)
at org.apache.struts2.ServletActionContext.getRequest(ServletActionContext.java:112)
at com.upg.ucars.framework.base.SessionTool.getAttribute(SessionTool.java:81)
at com.upg.ucars.framework.interceptor.AsyncInterceptor.actionIsLocked(AsyncInterceptor.java:71)
at com.upg.ucars.framework.interceptor.AsyncInterceptor.intercept(AsyncInterceptor.java:38)
at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:246)
at com.upg.ucars.framework.interceptor.AuthorizationInterceptor.intercept(AuthorizationInterceptor.java:83)
at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:246)
at com.opensymphony.xwork2.interceptor.ConversionErrorInterceptor.intercept(ConversionErrorInterceptor.java:138)
at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:246)
at com.opensymphony.xwork2.interceptor.ParametersInterceptor.doIntercept(ParametersInterceptor.java:249)
at com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:98)
at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:246)
at com.opensymphony.xwork2.interceptor.ParametersInterceptor.doIntercept(ParametersInterceptor.java:249)
at com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:98)
at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:246)
at com.opensymphony.xwork2.interceptor.StaticParametersInterceptor.intercept(StaticParametersInterceptor.java:191)
at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:246)
at org.apache.struts2.interceptor.FileUploadInterceptor.intercept(FileUploadInterceptor.java:252)
at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:246)
at com.opensymphony.xwork2.interceptor.ChainingInterceptor.intercept(ChainingInterceptor.java:145)
at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:246)
at com.opensymphony.xwork2.interceptor.I18nInterceptor.intercept(I18nInterceptor.java:139)
at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:246)
at org.apache.struts2.interceptor.ServletConfigInterceptor.intercept(ServletConfigInterceptor.java:164)
定位到 at com.upg.ucars.framework.interceptor.AsyncInterceptor.actionIsLocked(AsyncInterceptor.java:71)這一句
相關的代碼如下:
public String intercept(ActionInvocation arg0) throws Exception {
try{
if(SessionTool.getLocale()==null){
SessionTool.setDefaultLocale();
}
String actionName=arg0.getProxy().getActionName().toUpperCase();
if("LOGIN".equals(actionName)){
unlockAction();
}
boolean lock=true;
if(isUncontrolled(arg0))
return arg0.invoke();
else{
while(lock){
lock=actionIsLocked();
if(!lock){
lockAction();
String target=arg0.invoke();
unlockAction();
return target;
}
}
}
}catch(Exception e){
unlockAction();
throw e;
}
return "";
}
因為這裏有個while循環,估計就是在這裏死循環了
/**
* 判斷action是否已加鎖
* @return
*/
private boolean actionIsLocked(){
String flag=(String)SessionTool.getAttribute(SessionKeyConst.ASYNC_ACTION_LOCK);
if(flag==null)
return false;
return flag.equals("true");
}
/**
* 為action加鎖
*/
private void lockAction(){
SessionTool.setAttribute(SessionKeyConst.ASYNC_ACTION_LOCK, "true");
}
/**
* 為action解鎖
*/
private void unlockAction(){
SessionTool.setAttribute(SessionKeyConst.ASYNC_ACTION_LOCK, "false");
}
}
/**
* (獲取session中存儲的數據對象)
* @param key 數據對象在session中的唯一標識
* @return 存儲在session中的數據對象
* @date
*/
public static Object getAttribute(String key){
Object ret=null;
try{
HttpServletRequest request=ServletActionContext.getRequest();
if(request!=null){
ret=request.getSession().getAttribute(key);
}
}catch(NullPointerException e){
return ret;
}
return ret;
}
這裏的加鎖和解鎖就是在session裏把SessionKeyConst.ASYNC_ACTION_LOCK這個屬性設成true和false,但HttpSession這個類對於同一個用戶的並發操作是非線程安全的,有可能一個在解鎖同時另一個在加鎖,一個線程在加鎖後變成他true,此時另一個線程剛好調用actionIsLocked返回true則就進入死循環了。去線上一看,果然有同一個用戶
機一次cpu100%的線上故障