Apologies but I'm not sure why you are copying the remoting jar, or in fact which jar you refer to, but this should not be necessary. You should only have to copy the jdbc drivers as previously stated.
If you are receiving error messages about the remoting connector, I believe this is because in your config you are referring `remoting:2.0` and to a socket-binding="remoting" which does not exist in your config. I would suggest changing your remoting config to the following:
<subsystem xmlns="urn:jboss:domain:remoting:3.0"> <endpoint/> <http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm"/> </subsystem>
And if you are still receiving errors, your JMX config to:
<subsystem xmlns="urn:jboss:domain:jmx:1.3"> <expose-resolved-model/> <expose-expression-model/> <remoting-connector/> </subsystem>
This is because the internal marshaller used by Infinispan has changed in Infinispan 9.x. A summary of all the changes which cause incompatibilities across Infinispan versions can be found in the upgrading guide.
To help migrate existing Infinispan stores from 8.x to 9.x, we have created the JDBC Migrator tool. In your case, this should also work from 7.x to 9.x as the marshaller used in both 7.x and 8.x are compatible.
Please ensure you have adequate backups of the appropriate DBs before attempting to use the JDBC Migrator tool.
do you know why I can't access the infinispan node running on a remote host but locally it works? with version 7 this works in both situations
Which Infinispan endpoint are you trying to connect to?
This sounds like a firewall issue if you are using different port numbers across the two versions. Have you compared the configs to ensure that the ports for your endpoints etc are the same?
I'm using the same ports from the stock standalone.xml file. Are there any new ports in the 9 version for which rules need to be created?
There are no errors in the startup logs regarding ports.
I'm trying to connect to the standard 11222 port.
The culprit was probably these 2 lines:
added to the standalone.conf
Is there by any chance a workaround for the bug?
I'm now lost about which bug you're talking about
I mentioned only two : the infinispan full gc and not being able to be reached or the 'Direct buffer memory' from the client call to infinispan