Logstash-Plug in-JMS Weblogic 12.2.1

Hi, I have installed Weblogic 12.2.1 and the latest Logstash 7.5.2 version as well as the jms plugin v3.1.2. I am struggling with the jms plug in and I have already set the .conf and .yml, but it doesn't work!
In the Destination field the documentation and the examples suggest no JNDI name, just the queue or topic name!!!

Any suggestions would be greatly appreciated!!!

The input of the jms.conf :
input {
jms { pub_sub => false
include_header => false
include_properties => false
include_body => true
use_jms_timestamp => false
yaml_file => "/home/chris/Downloads/logstash-7.5.2/config/jms.yml"
yaml_section => "weblogic"
destination => "DemoQ"

The yml :

:jndi_name: jms/DemoCF
java.naming.factory.initial: weblogic.jndi.WLInitialContextFactory
java.naming.provider.url: t3://localhost:7001
java.naming.factory.url.pkgs: javax.naming:javax.jms
java.naming.security.principal: weblogic
java.naming.security.credentials: *****!
- /home/chris/Downloads/wlogic/fmw_12.
- /home/chris/Downloads/wlogic/fmw_12.
- /home/chris/Downloads/wlogic/fmw_12.

and the ouput of the Logstash :

[2020-01-31T14:50:10,284][WARN ][logstash.inputs.jms ][main] JMS Consumer Died {:exception=>"Java::WeblogicJmsCommon::JMSException", :exception_message=>"[JMSExceptions:045101]The destination name passed to the createTopic or createQueue "DemoQ" is invalid. If the destination name does not contain a "/" character, then it must be the name of a distributed destination that is available in the cluster to which the client is attached. If it does contain a "/" character, then the string before the "/" must be the name of a JMS server or a ".". The string after the "/" is the name of a the desired destination. If the "./" version of the string is used then any destination with the given name on the local WebLogic Server instance

After days I figured this out! In the field of destination use:
jmsmodulename!destinationname (from docs of Oracle ) ,
for a clustered environment!!
Neither "/" nor "./"

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.