HTTP Status 500 -


type Exception report

message

description The server encountered an internal error () that prevented it from fulfilling this request.

exception

bcf.base.SystemException: bcf.ecmascript.ScriptException: script cookies.htm not found. [mgback-1711685541931]
	bcf.web.ecmascript.ActionScriptServlet.callActionScript(ActionScriptServlet.java:411)
	bcf.web.ui.PageHandlerServlet.callActionScript(PageHandlerServlet.java:254)
	bcf.web.ecmascript.ActionScriptServlet$ActionScriptAction.execute(ActionScriptServlet.java:231)
	bcf.web.ControllerServlet.doRequest(ControllerServlet.java:58)
	bcf.web.ecmascript.ActionScriptServlet.doGet(ActionScriptServlet.java:291)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
	bcfx.app.AppLanguageFilter.doFilter(AppLanguageFilter.java:192)
	bcf.web.SessionSynchronizationFilter.doFilter(SessionSynchronizationFilter.java:88)
	bcf.web.sm.SMCallerIdentityFilter.doFilter(SMCallerIdentityFilter.java:689)

root cause

bcf.ecmascript.ScriptException: script cookies.htm not found. [mgback-1711685541931]
	bcf.web.ecmascript.ActionScriptEngine.callFunction(ActionScriptEngine.java:609)
	bcf.web.ecmascript.ActionScriptEngine.callRequestFunction(ActionScriptEngine.java:695)
	bcf.web.ecmascript.ActionScriptServlet.callActionScript(ActionScriptServlet.java:405)
	bcf.web.ui.PageHandlerServlet.callActionScript(PageHandlerServlet.java:254)
	bcf.web.ecmascript.ActionScriptServlet$ActionScriptAction.execute(ActionScriptServlet.java:231)
	bcf.web.ControllerServlet.doRequest(ControllerServlet.java:58)
	bcf.web.ecmascript.ActionScriptServlet.doGet(ActionScriptServlet.java:291)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
	bcfx.app.AppLanguageFilter.doFilter(AppLanguageFilter.java:192)
	bcf.web.SessionSynchronizationFilter.doFilter(SessionSynchronizationFilter.java:88)
	bcf.web.sm.SMCallerIdentityFilter.doFilter(SMCallerIdentityFilter.java:689)

note The full stack trace of the root cause is available in the JBossWeb/2.0.0.GA_CP logs.


JBossWeb/2.0.0.GA_CP