You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: JMS/README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -354,7 +354,7 @@ To run the samples with TLS you need to provide additional arguments;
354
354
355
355
*A note on the*`Dcom.ibm.mq.cfg.useIBMCipherMappings=false` property
356
356
357
-
This is needed as the samples were tested in an enviroment with the Oracle JRE installed. Depending on whether you have Oracle or IBM JRE installed, you also need to name the cipher suite/spec accordingly. See the table here [TLS CipherSpecs and CipherSuites in IBM MQ classes for JMS](https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.1.0/com.ibm.mq.dev.doc/q113220_.htm)
357
+
This is needed as the samples were tested in an enviroment with the Oracle JRE installed. Depending on whether you have Oracle or IBM JRE installed, you also need to name the cipher suite/spec accordingly. See the table here [TLS CipherSpecs and CipherSuites in IBM MQ classes for JMS](https://www.ibm.com/docs/en/ibm-mq/latest?topic=jms-tls-cipherspecs-ciphersuites-in-mq-classes)
358
358
359
359
## Bindings mode
360
360
@@ -367,7 +367,7 @@ By default these samples will run in client mode. If you do want to run the samp
367
367
to the `env.json` file.
368
368
369
369
## Unit Test
370
-
The samples also contain unit tests in `src/test`. These tests require connection with a Queue Manager and use the default `env.json` present in the repository, hence make sure you have at least one valid endpoint in the `env.json`.
370
+
The samples also contain unit tests in `src/test`. These tests require connection with a Queue Manager and use the default `env.json` present in the repository, hence make sure you have at least one valid endpoint in the `env.json`.Also these tests have not been run on a single CPU machine where the behaviour might be different.
0 commit comments