The action class cannot be hot-deployed after an exception is thrown in the SAStruts action processing.

 
[Symptom]
The action class cannot be hot-deployed after an exception is thrown in the SAStruts action processing.
A system error also occurs due to the LinkageError below when the above symptom occurs.

-----
java.lang.LinkageError: loader constraint violation: loader (instance of com/caucho/loader/EnvironmentClassLoader) previously initiated loading for a different type with name "jp/sample/master/entity/Table1"
at java.lang.ClassLoader.defineClass1(Native Method) [na:1.6.0_18]
-----

[Condition]
This event occurs when a log output is performed in the following classes which performs error processing thrown from within Action processing.

* ApplicationRuntimeExceptionHandler
* SystemRuntimeExceptionHandler
The above error processing classes are specified in the status-config.xml.

[Cause]
It occurs because the Action class is referred by the logger which is a non-target class and loaded into the normal class loader.

[Workaround]
Please turn off the log output for the Action class in the logger setting file.
Not to output an error in the action class, for example, please add the following setting.

-------------------------
<logger name="jp.sample.action">
<level value="off" />
</logger>

-- Target ------------------------------------------------------------------------
iWP/Web System Construction Platform/WebPlatform/AppFramework
-----------------------------------------------------------------------------------


FAQID:464
Was this article helpful?
0 out of 0 found this helpful
Powered by Zendesk