[ 
https://issues.apache.org/jira/browse/OFBIZ-12171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17282963#comment-17282963
 ] 

Jacques Le Roux commented on OFBIZ-12171:
-----------------------------------------

Hi MIchael,
I just tested, applying PR 270+53, got some issues (note: I'm on Windows 7)

The integration tests (cleanAll eclipse loadAll testIntegration) failed:
java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: Could 
not initialize class 
org.apache.commons.dbcp2.managed.PoolableManagedConnectionFactory

Got these errors running OFBiz just after:

2021-02-11 10:05:23,386 |delegator-startup-1 |ExecutionPool                 |E| 
null
java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: 
org/apache/logging/log4j/util/ReflectionUtil

of course
2021-02-11 10:05:23,392 |delegator-startup-1 |ExecutionPool                 |E| 
null
java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: Could 
not initialize class 
org.apache.commons.dbcp2.managed.PoolableManagedConnectionFactory

Feb 11, 2021 10:05:24 AM org.apache.catalina.core.StandardContext filterStart
SEVERE: Exception starting filter [SameSiteFilter]
java.lang.NoClassDefFoundError: Could not initialize class 
org.apache.ofbiz.webapp.control.SameSiteFilter
[...]
SEVERE: Context [/ebay] startup failed due to previous errors
Feb 11, 2021 10:05:24 AM org.apache.catalina.loader.WebappClassLoaderBase 
clearReferencesThreads
WARNING: The web application [ebay] appears to have started a thread named 
[Log4j2-TF-10-Scheduled-3] but has failed to stop it. This is very likely to 
create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
[...]
SEVERE: One or more Filters failed to start. Full details will be found in the 
appropriate container log file
[...]
SEVERE: Context [/marketing] startup failed due to previous errors
[...]
SEVERE: Context [/exampleext] startup failed due to previous errors
[...]
SEVERE: Context [/rest] startup failed due to previous errors
Etc.


> Handling the JCenter shutdown
> -----------------------------
>
>                 Key: OFBIZ-12171
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-12171
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: ALL APPLICATIONS, ALL COMPONENTS, ALL PLUGINS
>    Affects Versions: Release Branch 18.12, Trunk, 17.12.05
>            Reporter: Michael Brohl
>            Assignee: Michael Brohl
>            Priority: Major
>
> Citing Taher's message at [2]:
> Hello Everyone, 
>  
> I received emails and checked resources [1] that seem to confirm JCenter from 
> JFrog is going down and that the last day of operation for the repository is 
> going to be May 1st 2021. 
>  
> This is a big deal as many running instances will crash unless updated, so 
> not only do future versions of OFBiz need to adapt, but also existing 
> installations. 
>  
> I'm not sure how to best handle this? Especially for production instances out 
> there on older versions of OFBiz. Maybe one solution is to host the existing 
> libraries in some temporary location or try to migrate them to MavenCentral 
> ... Whatever is the solution I think we should make a fast move. 
>  
> [1] 
> [https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter]
>  
> [https://www.infoq.com/news/2021/02/jfrog-jcenter-bintray-closure]
> [2] 
> [https://lists.apache.org/thread.html/rf8e883ca8b90d51ad9d6d48c46f8f1fcc1cb82cce802daeeab0b910a%40%3Cdev.ofbiz.apache.org%3E]
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to