Lucee server io.undertow.request: UT005023

ghz 8months ago ⋅ 67 views

I am trying to run Contentbox 6.0.4 via lucee server 5.4.5 version, but unfortunately i get the following error

[INFO ] runwar.context: 2024-04-07 08:34:21 coldbox.system.web.Controller + LogBox created
[INFO ] runwar.context: 2024-04-07 08:34:23 coldbox.system.web.Controller + ColdBox services created
[INFO ] runwar.context: 2024-04-07 08:34:26 coldbox.system.web.Controller + Controller CacheBox created
[INFO ] runwar.context: 2024-04-07 08:34:26 coldbox.system.web.Controller + Controller WireBox created
[INFO ] runwar.context: 2024-04-07 08:36:09 coldbox.system.web.services.LoaderService + Application's WireBox configured
[INFO ] runwar.context: 2024-04-07 08:36:32 coldbox.system.web.services.LoaderService + ColdBox Global Classes registered
[INFO ] runwar.context: 2024-04-07 08:37:21 coldbox.system.cache.providers.CacheBoxColdBoxProvider Reaping scheduled task started for (default) every (5) minutes
[INFO ] runwar.context: 2024-04-07 08:37:26 coldbox.system.cache.providers.CacheBoxColdBoxProvider CacheBox Cache: default has been initialized successfully for operation
[INFO ] runwar.context: 2024-04-07 08:37:31 coldbox.system.cache.providers.CacheBoxColdBoxProvider Reaping scheduled task started for (SESSIONS) every (5) minutes
[INFO ] runwar.context: 2024-04-07 08:37:31 coldbox.system.cache.providers.CacheBoxColdBoxProvider CacheBox Cache: SESSIONS has been initialized successfully for operation
[ERROR] io.undertow.request: UT005023: Exception handling request to /cbadmin
java.lang.ThreadDeath: null
    at java.lang.Thread.stop(Unknown Source) [?:?]
    at lucee.commons.io.SystemUtil._stop(SystemUtil.java:1343) ~[?:?]
    at lucee.commons.io.SystemUtil.stop(SystemUtil.java:1334) ~[?:?]
    at lucee.commons.io.StopThread.run(SystemUtil.java:1765) ~[?:?]
[INFO ] runwar.server:

Is there any solution to that (possibly commandbox 5.8 upgrade to a more recent version)?

Regards

Answers

The error you are encountering (java.lang.ThreadDeath) seems to be related to a Java runtime issue, specifically related to the Thread.stop() method. This method is deprecated and unsafe to use because it abruptly terminates the thread.

However, it appears that the Thread.stop() method is being called within the Lucee application, which suggests there might be a bug or compatibility issue with the Lucee version you are using and possibly the Java version.

Here are some steps you can take to troubleshoot and potentially resolve the issue:

  1. Update Lucee and Java: Ensure that you are using the latest version of Lucee and Java. Newer versions may have bug fixes and improvements that address this issue.

  2. Check Compatibility: Verify that the version of Lucee you are using is compatible with the version of Java you have installed. Sometimes, certain versions of Lucee may not work correctly with specific Java versions.

  3. Review Application Code: If you have access to the application code, review it to see if there are any custom threads being used and if the stop() method is being called explicitly. If so, consider refactoring the code to avoid using stop().

  4. Check for Updates: Ensure that your Contentbox application is up to date. Sometimes, newer versions of the application may include fixes for compatibility issues with Lucee and Java.

  5. Debugging: Use debugging tools to pinpoint the exact location in the code where the exception is being thrown. This can provide valuable insight into the root cause of the issue.

  6. Community Support: Seek help from the Lucee and Contentbox communities. They may have encountered similar issues and can provide guidance or solutions.

If updating Lucee and Java does not resolve the issue, you may need to dig deeper into the application code or seek assistance from the community or developers familiar with Contentbox and Lucee.

#lucee