Hi!
Is there any specific reason why username and password is not passed to jms_config in jndi lookup was chosen? I am trying to integrate this plugin with the Tibco EMS and it seems like Tibco's Connection Manager expects username/password passed for Connection creation even if java.naming.security.principal and java.naming.security.credentials were presented during the lookup.
If jms_config block is reconfigured like below everything works just fine:
elsif @jndi_name
@jms_config = {
:require_jars => @require_jars,
:jndi_name => @jndi_name,
:jndi_context => @jndi_context,
:username => @username, # tibco ems expects username and password on Connection creation
:password => @password
}
Is it possible to pass username and password to jms_config even if jndi lookup was chosen?
Hi!
Is there any specific reason why username and password is not passed to jms_config in jndi lookup was chosen? I am trying to integrate this plugin with the Tibco EMS and it seems like Tibco's Connection Manager expects username/password passed for Connection creation even if java.naming.security.principal and java.naming.security.credentials were presented during the lookup.
If jms_config block is reconfigured like below everything works just fine:
Is it possible to pass username and password to jms_config even if jndi lookup was chosen?