What was the fix for CVE 2021-31917 ? Is this applicable only for infinispan-server? - infinispan

There is a CVE reported on infinispan
https://nvd.nist.gov/vuln/detail/CVE-2021-31917
It is marked as fixed after 12.0.0.
I need information for which infinispan module this CVE is applicable ?

The module is org.infinispan:infinispan-server-rest

Related

Axis2 Fault : The system is attempting to engage a module that is not available: addressing

I have the addressing module in my modules folder as well. I have the <module ref="addressing"/> uncommented as well. But, it is still giving the error. I searched in another thread on Stack Overflow:
org.apache.axis2.AxisFault: The system is attempting to engage a module that is not available: addressing
But, it did not help.
Disclaimer- The axis2 war was working on JBoss Server but not on WAS server.
Solution- In axis2.xml file, there is a parameter 'EnableChildFirstClassLoading' which was commented, uncommenting it and deploying axis2 war again solved the issue.
Needed to make the above mentioned change on WAS server only.

java.lang.NoClassDefFoundError: Could not initialize class org.apache.pdfbox.pdmodel.font.PDFont

I am using Apache Tika( tika-app 1.17) in wildfly modules.
While I start extracting PDF it always throws the error:
java.lang.NoClassDefFoundError: Could not initialize class
org.apache.pdfbox.pdmodel.font.PDFont
For other file extensions it works fine.
Things I have tried out dependencies in apache-tika module.xml to PDFbox
Explicitly loaded org.apache.pdfbox from standalone.xml
I have also tried with the below structure
app1.war->(WEB-INF)lib-->app.jar->lib-->tika-app-1.17.jar
I have also jboss-deployment-structure.xml where
<dependencies>
<module name="com.company.tika" />
</dependencies>
is mentioned as a module dependency.
In MANIFEST.MF of the jar also, I have dependency to com.company.tika
Nothing seems to work.
Any suggestions or help would be thankful.
Thanks in Advance
Dwai
I could resolve the issue. The problem was the minor version of pdfbox, fontbox and jempbox were not the same. Hence the PDFFont was not initialized, because internally it needs to load the classes of fontbox also and probably there was a mismatch in the version id of the classes
setting SOLR_JAVA_STACK_SIZE='-Xss256M' only and not making any changes to libs solved this issue for me
I had similar problem.
Under linux i just install missing library pdfbox by:
apt-get install libpdfbox-java
and restart solr server
After this modification i need to change solr start parameter in ./bin/solr
from
SOLR_JAVA_STACK_SIZE='-Xss256kb'
to
SOLR_JAVA_STACK_SIZE='-Xss256M'
because i had error
java.lang.StackOverflowErrorjava.lang.RuntimeException: java.lang.StackOverflowError
of course i restart solr server again.
I hope, it help you reolve this problem.

Unable to eliminate Tomcat Cache warnings in catalina.out

Since switching to Tomcat 8, I continually get messages like this in my catalina.out
org.apache.catalina.webresources.Cache.getResource Unable to add the resource at [/intranet/includes/MailFunctions.jsp] to the cache because there was insufficient free space available after evicting expired cache entries - consider increasing the maximum size of the cache
I've found in the docs to add entries like cachingAllowed="false" antiResourceLocking="false" antiJARLocking="true" cacheMaxSize="0" cacheTTL="1" to my META-INF/context.xml file which I've done, but this doesn't seem to eliminate the problem.
Does anyone know how to stop these messages?
Thanks
I had the same issue but found an answer in another post which worked for me
In your $CATALINA_BASE/conf/context.xml add the block below before
</Context>
<Resources cachingAllowed="true" cacheMaxSize="100000" />
This solved it for me.
“inside the tag ” in where, I think :
Tomcat/bin/catalina.bat int this add set JAVA_OPTS=-Xms256m -Xmx512m -Djava.awt.headless=true [-XX:MaxPermSize=128M]
eclipse->windows->preferences..->tomcat->jvm..->jvm add -Xms256m -Xmx512m
eclipse->preference->Java->instal jres->edit add -Xms256M -Xmx640M -XX:PermSize=256m -XX:MaxPermSize=768m
For anyone else unable to find an answer to this problem, the answer seems
to be as simple as adding this to your $SERVER_HOME/conf/context.xml
inside the tag

java.lang.NoClassDefFoundError: Could not initialize class org.apache.activemq.util.IdGenerator

I am trying to use ActiveMQ 5.10.0 with SoapUI 4.6 and Hermes 1.14. I get the error below when I try and add a queue. I presume Hermes can't find the type IdGenerator in any of the loaded jars. Which are:
activemq-client-5.10.0.jar
geronimo-j2ee-management_1.1_spec-1.0.1.jar
geronimo-jms_1.1_spec-1.1.1.jar
Does anyone know where this class is defined? I looked for activemq-util.jar in the binary distribution but I did not find such a file.
Error:
java.lang.NoClassDefFoundError: Could not initialize class org.apache.activemq.util.IdGenerator
at org.apache.activemq.ActiveMQConnectionFactory.getClientIdGenerator(ActiveMQConnectionFactory.java:969)
at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:363)
at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:331)
at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:303)
at org.apache.activemq.ActiveMQConnectionFactory.createQueueConnection(ActiveMQConnectionFactory.java:260)
at hermes.impl.jms.ConnectionManagerSupport.createConnection(ConnectionManagerSupport.java:147)
at hermes.impl.jms.ConnectionManagerSupport.createConnection(ConnectionManagerSupport.java:92)
at hermes.impl.jms.ConnectionSharedManager.reconnect(ConnectionSharedManager.java:81)
at hermes.impl.jms.ConnectionSharedManager.connect(ConnectionSharedManager.java:91)
at hermes.impl.jms.ConnectionSharedManager.getConnection(ConnectionSharedManager.java:104)
at hermes.impl.jms.ConnectionSharedManager.getObject(ConnectionSharedManager.java:142)
at hermes.impl.jms.ThreadLocalSessionManager.connect(ThreadLocalSessionManager.java:190)
at hermes.impl.jms.ThreadLocalSessionManager.getSession(ThreadLocalSessionManager.java:570)
at hermes.impl.jms.AbstractSessionManager.getDestination(AbstractSessionManager.java:460)
at hermes.impl.DefaultHermesImpl.getDestination(DefaultHermesImpl.java:367)
at hermes.browser.tasks.BrowseDestinationTask.invoke(BrowseDestinationTask.java:141)
at hermes.browser.tasks.TaskSupport.run(TaskSupport.java:175)
at hermes.browser.tasks.ThreadPool.run(ThreadPool.java:170)
at java.lang.Thread.run(Unknown Source)
This is very old but in case anyone else is trying to get this spun up... don't use the built in HermesJMS that comes with SoapUI. Apparently there's a bug in it that doesn't play nice with ActiveMQ v5.8 and following [I tried 5.11 & 5.13 and had the issue. The cheating fix is to install the standalone [I had to get it from sourceforge].
The sourceforge jar is installed with [assuming version 1.14]: java -jar hermes-installer-1.14.jar
Once installed you can tie this version to soapui or launch it with the bat/sh file. I still had issues with ActiveMQ version 5.13 but version 5.11 worked for me.
The IdGenerator class is located in the activemq-client jar. Here is the result of a search in the source tree:
/activemq-client/src/main/java/org/apache/activemq/util/IdGenerator.java
There's been no recent changes so I'd guess that the error is misleading and that it's actually some other missing dependency that's being loaded when the class is created. Is there more information in the log or a 'caused by exception' ?
For whom it may interest. This is kind of common issue I come accross from time to time. I call it jar version incompatibility. I was getting exception in title and other funny exceptions when using latest (but not actively developed) hermes 1.14 and currently latest Apache Active MQ 5.14. I've found out after a long struggle that it is fixed by using an older version of Active MQ - like 5.3.

Dependency not resolved while creating OSGI bundle having selenium web driver

I am trying to create an OSGI bundle having selenium firefox web driver. I used the same dependency in maven project and it all worked fine. But when i am creating bundle, compilation gives no issues. But on installing bundle, there are some internal dependencies which can not be resolved. There is a property in maven bundle plugin
embed-transitivy. I set it to true which solves almost all the internal dependencies of firefox-webdriver. Still some could not be resolved.
Error:
net.sf.cglib.asm.util -- Cannot be resolved
org.apache.avalon.framework.logger -- Cannot be resolved
org.apache.log -- Cannot be resolved
org.apache.log4j from log4j.over.slf4j (4)
org.apache.tools.ant -- Cannot be resolved
org.apache.tools.ant.types -- Cannot be resolved
org.codehaus.aspectwerkz.hook -- Cannot be resolved
sun.misc -- Cannot be resolved
Moreover, when I am searching for net.sf.cglib.asm.util in cglib-nodep.2.1_3.jar there is no such class. Internally firefox-driver using cglib-nodep.2.1_3.jar. I guess there is some problem with the version 2.1_3. I dont know How OSGI resolves this version name.
Can somebody please figure out what could be an issue. and where do I find the class net.sf.cglib.asm.util ?
PS: I am using 2.25.0 version of firefox-driver which internally depends upon cglib and fetches 2.1_3 version of it.
There is a different problem all together I think. You might like to have a look at this.
http://code.google.com/p/google-guice/issues/detail?id=208
There is the same problem you have faced. So read that. It might help.
Sounds like you are facing the problem described here http://spring.io/blog/2009/01/19/exposing-the-boot-classpath-in-osgi/ and here http://blog.meschberger.ch/2008/10/osgi-bundles-require-classes-from.html