I am currently facing the issue that I cannot start the JMS Connection Aliases in the 2 affected IS (wM 9.5 SP1).
Both IS have the same Fix Level.
On other ISes (both 7.1.x and 9.5 SP1) I have the identically named JMS Connection Aliases running using identically named certificates.
Only difference is that the path names to those certificates not working contain a “-” (a dash) in the name.
But this dash works for normal Broker Connection as well as for the underlying JNDI-Alias as well as for the complete Broker SSL configuration (incl. generation of the naming directories). PE_NONTRANSACTIONAL_ALIAS is also working with this path name.
JNDI-Provider is WmJMSNaming, JMS-Provider is Broker.
OS is Solaris Sparc V10 for both wM Versions.
Should it be the case, that this dash in the path name causes these problems?
Please help to identify and workaround.