Solace | Java-based Multi-User Dungeon Server | Game Engine library

Trying to use the full format command would require an eval(), which is normally considered not only bad practice, but also a serious security issue, especially when the input argument is completely set by the user.

Since the fields are known, I see little point in providing the whole format line, and it is better to parse the format string looking for keywords, then use keyword lookup to create the output.

That is telling you that the [customerId] field does not exist on that event. If the [message] field is JSON then you should add a json filter to parse it. That will create the [customerId] field, which you can then use as the document_id.

Most probably something is wrong with your JDK installation, as per The Java Developer’s Guide to SSL Certificates article:

Truststore

The truststore is a file that contains the root certificates for Certificate Authorities (CA) that issue certificates such as GoDaddy, Verisign, Network Solutions, and others.

The truststore comes bundled with the JDK/JRE and is located in $JAVA_HOME/lib/security/cacerts.

The truststore is used whenever our Java code establishes a connection over SSL.

According to the error you're getting this /var/tmp/jre1.8.0_281/lib/security/cacerts is a folder while it must be the file.

So I would recommend double-checking the integrity of your JRE installation and eventually perform a clean install as it seems to be broken somehow

You might also be interested in Building a JMS Testing Plan - Apache JMeter article

Answer to question could be found here! https://solace.community/discussion/646/solace-integration-with-kafka-over-tcps-failing

👍

It looks like the two scripts (the one for JQuery and the one for Ripples) are not present on the home page of the site in question.

It looks like you added them to your /home page here, but that page is not set as your actual home page. You may be aware of that, but thought it was worth mentioning. Because I work with Squarespace a lot, I knew to look for that, but others here on StackOverflow would not know to go to /home to see what you're referring to. Keep that in mind.

In any case, to fix the issue, move your JavaScript code (from the first snippet in your question above) to Footer code injection instead of Header code injection. It must be in Footer code injection because, otherwise, it executes before your .ripples element is present, and so therefore the code does nothing.

So, move it to Footer code injection so that, when it runs, the element with class="ripples" is present.

Since EJB 3.x continues to support all the EJB 2.x APIs, it may not be difficult to upgrade your application. In ejb-jar.xml, you would just need to update the top of the file from 2.x to 3.x and everything else remains the same. Where things get tricky is if you have extensive configuration in ibm-ejb-jar-bnd.xmi and/or ibm-ejb-jar-ext.xmi, as those both need to be converted to the newer XML equivalents. The advantage to upgrading is that EJB 3.x tends to need much less XML configuration and you can take advantage of injection, which is used in the Solace example.

However, if you would like to stick with EJB 2.x, then much of the existing Solace example is still applicable, you just need to convert the annotations to XML, add in the missing EJBLocalHome interface, and then perform JNDI lookups instead of injection. So, assuming you start with this Solace EJB 3.x example, then you need to convert @MessageDriven to message-driven, @Stateless to session, @EJB to ejb-local-ref and @Resoruce to resource-ref and resource-env-ref. And finally, perform JNDI lookups of those references in place of injection.

Since modifying an existing EJB 2.x application can be tricky if you are not using the original tooling, I've provided the following key pieces of configuration for what the Solace EJB 3.x example would look like for EJB 2.x:

First, everything in server.xml would remain the same.

Second, the ejb-jar.xml for the two beans in the Solace example would look something like this:

You are calling System.exit() on the listener container thread

You can get a 100% portable standalone JMS application with essentially no extra work on your part if the JMS providers you're switching between also provide a JNDI implementation. The JMS specification doesn't require JNDI but it establishes the convention that JNDI be used to locate administered objects like connections factories and destinations so it is very common for JMS providers to also provide a JNDI implementation as well.

In short your application can simply use the JMS and JNDI APIs. JMS and JNDI implementation details can be isolated to a jndi.properties file placed on the application's classpath. Switching between providers would be as simple as changing this properties file and changing the jars on the classpath.

If the JMS providers you're switching between don't provide JNDI implementations then you'll have to use implementation-specific code to create your connection factories and destinations. This will, of course, hurt portability, but you should be able to create your own API to isolate these details to classes which you can switch out for yourself.

I think a histplot would be a better way to visualize this problem if "ultimately, what i want to show is how the total sales of each title differs across platforms" This shows the frequency of games with standard deviations (grouped by game) in 0.1 bins. You can pass ddof=0 to not return NaN values, but that will change the standard devation of all values.