Hello Gupta,  Can you change the SSLEnabled to TRUE in Lab environment as well and check if it works fine? In this way we can identify if SSLEnabled flag is causing the issue here.  Also, can you please let us know if you have started the ASAM service with sm_sitemod. If yes, can you share the below commands outputs from $BASEDIR/ASAM/smarts/bin directory: ./sm_service show --cmdline ./sm_server --version  Regards, Natya.
Hi All,  I'm getting the below error when ASAM Adapter is trying to initiate a JMS connection with NFM17.9. We are using SSL Mode enabled.  1) EMS Instance password is given in MD5Hash 2) JMS Password is given in clear text 3) Ports, IP Addresses are verified 4) Placed the SamOSS.jar and compared the sizes, md5sum etc. 5) copied the Truststore file and also tried with keystore file as well 6) By running the tcpdump on NFM and it is clear that request is going there...  But still getting the below error.. Any help on this would be really great...  ASAM_MESSAGE-*-SEVERE-.[Connector] Exception Type:javax.naming.NameNotFoundException external/5620SamJMSServer -- service jboss.naming.context.java.jboss.exported.external.5620SamJMSServer org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:104) org.jboss.as.naming.NamingContext.lookup(NamingContext.java:197) org.jboss.as.naming.NamingContext.lookup(NamingContext.java:174) org.jboss.naming.remote.protocol.v1.Protocol$1.handleServerMessage(Protocol.java:127) org.jboss.naming.remote.protocol.v1.RemoteNamingServerV1$MessageReciever$1.run(RemoteNamingServerV1.java:73) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) java.lang.Thread.run(Thread.java:748)  Regards, LSR Gupta
ASAM Adapter v 3.2.0.12 to NFM/NSP 17.9 integration issue