Discussions
Categories
- 17.9K All Categories
- 3.4K Industry Applications
- 3.3K Intelligent Advisor
- 63 Insurance
- 536.4K On-Premises Infrastructure
- 138.3K Analytics Software
- 38.6K Application Development Software
- 5.8K Cloud Platform
- 109.5K Database Software
- 17.5K Enterprise Manager
- 8.8K Hardware
- 71.1K Infrastructure Software
- 105.3K Integration
- 41.6K Security Software
Error using JMS consume

955208
Member Posts: 12
Please solve the problem below.
I have created a jms queue. In a second composite, I have created a jms adapter to consume these messages and a write file service to write these messages to a file.
In this composite i have used mediator and used xsl file to get the messages from jms queue and write to a file.
Now the problem is when I invoke a message a new file gets created but only with empty tags with no values in it.
Please suggest.
I have created a jms queue. In a second composite, I have created a jms adapter to consume these messages and a write file service to write these messages to a file.
In this composite i have used mediator and used xsl file to get the messages from jms queue and write to a file.
Now the problem is when I invoke a message a new file gets created but only with empty tags with no values in it.
Please suggest.
Answers
-
Reddy,i have used mediator and used xsl file to get the messages from jms queue and write to a file.Do check the mapping properly and do a test also to see the transformed elements ....
http://docs.oracle.com/cd/E16764_01/integration.1111/e10224/bp_xslt_mpr.htm#BABGAIFG
There can be following reasons:
1. Message in JMS Queue is not getting dequeued.
2. JMS adapter is not properly configured or mapped to proper JMS queue.
3. Mediator XSL map is not proper..
4. File adapter message schema is improper
You can check Composite instance in Oracle EM and can track where the payload is going from ( JMS Adapter----- Mediator----- File adapter).
Regards,
Abhinav Gupta -
Empty file is getting create that means you are subscribing to the message.
Now the problem should be in the XSL mapped.
The subscribing message should be based on the same schema on which you have defined your xsd. -
There are more chances that it could be related to Schema. Can you please share your input and output schemas. I suspect there is a problem with the namespace.
Thanks & Regards,
Vikas Manchanda
This discussion has been closed.