is Yellowfin 9.10.0.1 compatible with Tomcat 10.x?

Is Yellowfin compatible with Jboss? if my app wants to get rid of Tomcat?

Hello Phani,

Thanks for getting back to us with your inquiry. Yellowfin does work on multiple Java application servers; however, Yellowfin can only fully support Tomcat, as that's what we ship and test against. At this point in time, there might be no future plans to fully support application servers other than Tomcat.

Please let us know if you have any more questions; we will be happy to help.

Thanks & Regards,

Priya.

Hello Phani,

I hope you are doing well.

I just wanted to check in and see how it's all going. Is there anything else you need from me to help with this? If you can get back to me that would be great.

Thanks & Regards,

Priya.

Hello Priya,

I get below error in tomcat, connexotomcat-stderr.2024-02-01, with 9.0.10.1 YFN

LF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [file:/C:/connexoservice/partners/tomcat/webapps/facts/WEB-INF/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [file:/C:/connexoservice/partners/tomcat/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
java.net.SocketException: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext)
at javax.net.ssl.DefaultSSLSocketFactory.throwException(SSLSocketFactory.java:248)
at javax.net.ssl.DefaultSSLSocketFactory.createSocket(SSLSocketFactory.java:255)
at sun.net.http://www.protocol.https.HttpsClient.createSocket(HttpsClient.java:433)
at sun.net.NetworkClient.doConnect(NetworkClient.java:162)
at sun.net.http://www.http.HttpClient.openServer(HttpClient.java:463)
at sun.net.http://www.http.HttpClient.openServer(HttpClient.java:558)
at sun.net.http://www.protocol.https.HttpsClient.<init>(HttpsClient.java:292)
at sun.net.http://www.protocol.https.HttpsClient.New(HttpsClient.java:395)
at sun.net.http://www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:191)
at sun.net.http://www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1162)
at sun.net.http://www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1056)
at sun.net.http://www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:177)
at sun.net.http://www.protocol.http.HttpURLConnection.getOutputStream0(HttpURLConnection.java:1340)
at sun.net.http://www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1315)
at sun.net.http://www.protocol.https.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java:264)
at com.hof.util.LicenceControl$_A.run(LicenceControl.java:1788)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext)
at java.security.Provider$Service.newInstance(Provider.java:1711)
at sun.security.jca.GetInstance.getInstance(GetInstance.java:236)
at sun.security.jca.GetInstance.getInstance(GetInstance.java:164)
at javax.net.ssl.SSLContext.getInstance(SSLContext.java:156)
at javax.net.ssl.SSLContext.getDefault(SSLContext.java:96)
at javax.net.ssl.SSLSocketFactory.getDefault(SSLSocketFactory.java:122)
at javax.net.ssl.HttpsURLConnection.getDefaultSSLSocketFactory(HttpsURLConnection.java:332)
at javax.net.ssl.HttpsURLConnection.<init>(HttpsURLConnection.java:289)
at sun.net.http://www.protocol.https.HttpsURLConnectionImpl.<init>(HttpsURLConnectionImpl.java:99)
at sun.net.http://www.protocol.https.Handler.openConnection(Handler.java:62)
at sun.net.http://www.protocol.https.Handler.openConnection(Handler.java:57)
at java.net.URL.openConnection(URL.java:1001)
at com.hof.util.LicenceControl$_A.run(LicenceControl.java:1763)
... 1 more
Caused by: java.io.IOException: keystore password was incorrect
at sun.security.pkcs12.PKCS12KeyStore.engineLoad(PKCS12KeyStore.java:2068)
at java.security.KeyStore.load(KeyStore.java:1445)
at sun.security.ssl.SSLContextImpl$DefaultManagersHolder.getKeyManagers(SSLContextImpl.java:1124)
at sun.security.ssl.SSLContextImpl$DefaultManagersHolder.<clinit>(SSLContextImpl.java:1021)
at sun.security.ssl.SSLContextImpl$DefaultSSLContext.<init>(SSLContextImpl.java:1186)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at java.security.Provider$Service.newInstance(Provider.java:1689)
... 13 more
Caused by: java.security.UnrecoverableKeyException: failed to decrypt safe contents entry: javax.crypto.BadPaddingException: Given final block not properly padded. Such issues can arise if a bad key is used during decryption.
... 23 more

Hello Phani,

I hope you are doing well.

I have a few things that need to be checked on a live basis, I am happy to jump on a call to discuss. I am happy to jump on a call to see the issue.
I am usually available between 2:00 pm-11:00 pm IST, Please let me know your available time so I can check this in the screen share session!

Thanks & Regards,
Priya.

Hello Phani,

I just want to touch base to see if you had a chance to read through my response. If you can get back to me that would be great.

Thanks,

Priya.

Hello Phani,

Greetings for the Day.

This is a follow-up reminder that 3 days have passed without any activity in this ticket. When there's no activity, it usually means either that you have identified the solution for the reported issue or that the matter is no longer relevant and after 5 days (1 day from now) without any activity, we assume that the ticket can be closed.

If this is not the case, please do reply and let us know how we can be of further assistance, we would be happy to assist.

Thanks,

Priya.

Hello Phani,

Greetings for the Day.

This email is to notify you that we believe that you have identified the solution for the reported issue or that this ticket can be resolved for now.

Because of age and inactivity, I am going to go ahead and mark this ticket as Completed for now. However, if you ever want to revisit this or have anything else I can help you with, please let us know, and we will be more than happy to do so.

Thanks & Regards,

Priya.