Develop Reference

downgrade java version on archlinux

I have just updated java on my archlinux server and now it mess up my tomcat projects.
I want to downgrade java from 11.0.17.u1 to 11.0.13.u8
I looked at my var/cache/pacman/pkg folder and it seems like my old package are still there
jre11-openjdk-11.0.13.u8-1-x86_64.pkg.tar.zst
jre11-openjdk-headless-11.0.13.u8-1-x86_64.pkg.tar.zst
I am trying to run this command to force the installation of this java version :
sudo pacman -U jre11-openjdk-11.0.13.u8-1-x86_64.pkg.tar.zst
But it does not let me and I get this message :
loading packages...
warning: downgrading package jre11-openjdk (11.0.17.u1-1 => 11.0.13.u8-1)
resolving dependencies...
warning: cannot resolve "jre11-openjdk-headless=11.0.13.u8-1", a dependency of "jre11-openjdk"
:: The following package cannot be upgraded due to unresolvable dependencies:
jre11-openjdk
What can I do to force the downgrade?
Further infos:
This is the error I am getting since I updated the JVM
09-Jan-2023 15:46:44.910 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesObjectStreamClassCaches Failed to clear soft references from ObjectStreamClass$Caches for web application [docs]
java.lang.ClassCastException: class java.io.ObjectStreamClass$Caches$1 cannot be cast to class java.util.Map (java.io.ObjectStreamClass$Caches$1 and java.util.Map are in module java.base of loader 'bootstrap')
The tomcat servers I have not restarted yet (which are still running under the old jvm are doing just fine.
I found this topic here :
ClassCastException when stopping Tomcat 10 inside Eclipse
The solution that is brought is to upgrade the tomcat version. I am in an emergency situation where I don't have the time to update all my tomcat servers right now.

Tomcat versione 8.5.69 and sameSiteCookies=lax doesnt work with saml/onelogin

I have a web application that run on tomcat 8.5.34 and use the single sign on login with saml/onelogin api.
Here the specifications:
Amazon corretto Jdk 1.8.0_252
Apache tomcat 8.5.34
OS Windows 10
java-saml-2.4.0.jar and java-saml-core-2.4.0.jar
Everithing was fine until we upgrade the tomcat version to 8.5.69, from that version the redirect to our application stopped to work.
Here every attempt to fix the issue:
Upgrade the java-saml api --> fail
Upgrade the tomcat version till the last 9 release --> fail
Change the attribute classname in the tag CookieProcessor to the org.apache.tomcat.util.http.LegacyCookieProcessor --> fail
After all we found two solutions:
Downgrade the tomcat version (that is not possible in production server, we are migrating to tomcat 9)
Change the attribute sameSiteCookies in this configuration in context.xml <CookieProcessor sameSiteCookies="lax"/> from lax to unset, but this configuration involve my application in a security problem named CSRF attacks so i cant pass VAPT tests.
Now i am in a bottleneck, any suggestions?
Thanks to the all community.

Activiti Explorer - Request resource is not available

I have big problem to run activiti-explorer when i try access: http://localhost:8080/activiti-explorer/ tomcat shows me HTTP Status 404 - The requested resource is not available. I'm really don't have any idea why that dosen't work. Can you help me?
This what have I done on my PC:
I'm using 5.19.0 version of activiti-explorer
7.0.63 tomcat
JDK 1.8.0.77 (i think there is no point to downgrade java to previous versions (<=1.7) becouse my main application using this version)
I'm sure I have correctly configured environment variables (JAVA_HOME,JRE_HOME,PATH,CATALINA_HOME)
I configured data base connection (db.properties, context.xml) in activiti-explorer.war and i moved this file to tomcat/webapps
I don't have any errors about activiti during tomcat start

Check if activiti explorer is deployed to tomcat in manager.
http://{host}:{port}/manager/html
More info in https://tomcat.apache.org/tomcat-7.0-doc/manager-howto.html

Check the catalina.out log. There will be something in there that leads you to the solution.

Check Admin Console (cmd that runs behind) after hitting the link. most recent exception occurred will be displayed there.

Unable to start server in Eclipse Gallileo IDE with WAS7

Server not starting in Eclipse Gallileo IDE with WAS7.
I run the server from outside of Eclipse but I want to start it from within the eclipse
Below are the details of my Workspace configurations :
Eclipse Java EE IDE for Web Developers.
WAS 7.0
An alert is coming saying "Cannot connect to VM socket closed".
I got the following exception in console :
JVMSHRC154E Escape character g not valid for cache name
<JIT: FullSpeedDebug: ignoring countString>
<JIT: FullSpeedDebug: ignoring countString>
JVMJ9VM015W Initialization error for library j9shr24(13): JVMJ9VM009E J9VMDllMain failed

Per the JVMSHRC154E, it appears that somehow -Xshareclasses:name=...%g... is being added to your server JVM command line. I do not know why there would be a difference between Eclipse and the command-line (perhaps a product issue that should be reported to IBM), but you could try working around the issue by adding -Xshareclasses:nonfatal to your server's generic JVM arguments.

IBM has released development tools for WebSphere Application Server (WAS).
You can download it from eclipse market place.
There are tools for the WAS7 and up. (IBM Information page)
You probably need WAS 7 Tools - marketplace page.
The short instruction is:
In the eclipse click Help->Eclipse Market Place->Search WebSphere Application Server Tools.

Inside eclipse installation folder go to \plugins.....\cdcla\eclipse\launch\simple.
Open the file websphere70.properties.
You will see the following content and remove the
"_%g"
part and save it
shareclasses=webspherev70_%g,groupAccess,nonfatal

http.proxyHost system property is set to null

Please help me to find out the reason of the following behaviour.
I have two applications running in Tomcat container: my application and Hudson (v2.2.0). Tomcat is started with -Dhttp.proxyHost=proxy -Dhttp.proxyPost=8080 options so that my application uses proxy to access external WebServices.
I have detected the following very strange behaviour of Hudson running a maven build: At some point of time (just before maven is launched), the http.proxyHost system property is set to null. Perhaps I am following the wrong trace, by my application (which is deployed to the same Tomcat) crashes as it cannot open the connection and I think this two are relative.
I have installed the custom ProxySelector to report when the proxy is reset. It looks like http.proxyHost is reset just before maven starts the dependency resolving:
15.12 10:13:35 DEBUG [org.CustomProxySelector] Using proxy DIRECT for URL http://repo.internal/nexus/content/groups/development/org/parent/1.0.0-SNAPSHOT/maven-metadata.xml.sha1. Proxy settings: http.proxyHost=null, ftp.proxyHost=proxy
java.lang.Exception
at org.CustomProxySelector.select(CustomProxySelector.java:42)
at org.CustomProxySelector.select(CustomProxySelector.java:38)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:906)
at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:836)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1172)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:379)
at org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:115)
at org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116)
at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88)
at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61)
at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$GetTask.verifyChecksum(WagonRepositoryConnector.java:708)
at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$GetTask.run(WagonRepositoryConnector.java:625)
at org.sonatype.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:64)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
15.12 10:13:35 INFO [hudson.maven.MavenModuleSetBuild] using maven 3 3.0.3
15.12 10:16:10 INFO [hudson.model.Run] common-ops #87 main build action completed: SUCCESS
I might be wrong in what is actually happening: Maven should run in separate JVM, but how CustomProxySelector which I install to JVM static variable in my project, is visible from Maven JVM? If "parent" JVM and "forked" JVM share the same root classloader then perhaps they share the system properties as well. That means, if Maven build (even temporary) sets http.proxyHost to null and my process opens URL as this time, it will fail.
My question is: If above behaviour is a bug in Hudson / Maven? What can be a workaround (except trivial running 2 Tomcat servers).