In a esb route, a messagingEndpoint reads a large file and sends it to an AMQ queue. But it fails if the file is larger than 50Mb, wich is not very large itself.
The error is : "Uncategorized exception occured during JMS processing; nested exception is javax.jms.JMSException: Socket closed", I think it's a timeout that occurs after approximatly 30 seconds.
What parameters or other way can we use to handle large files in Talend ESB and ActiveMQ (seeded with Talend ESB) ?
Solved! Go to Solution.
Have you looked at this documentation?
You may want to use a cMessagingEndpoint and use the Apache Camel JMS component from scratch. See this:
Yes I've read this doc but it is for Artemis, not standard ActiveMQ seeded with Talend ESB.
I'll try the basic jms endpoint but not convinced it will change anything as the Talend component does more or less the same.
we're using cMessaingEndpoint for convenience use but you can achieve the same with Talend component if you put the camel options in the "advanced settings'".
Anyway, I'm trying this
That is true in most scenarios, but I've just found it easier to use the Apache Camel components' full URIs. As I said, it just gives you complete control and allows you to focus on one set of documentation instead of cross-referencing when the functionality is implemented in Talend without using the Advanced Settings.
I can't find the full JMS URI syntax , it failed retrived the cMQconnectionFactory I add as parameter, while I can see it in the java code. I tried the java object Talend creates and also the name of the object it adds in the Camel context but it fails with "No bean could be found in the registry for: myfactory of type: javax.jms.ConnectionFactory"
With cJMS component, I tried this parameter , adding a cExchangePattern INOUT before as the doc says the parameter only works this way, but it does not seem to have any effect, the timeout does not occur later. In the java code I can see :
I also tried Transacted mode in factory and in producer with "&transactionTimeout=120" , no effect either.
You're better off using Connection Pooling for JMS in the runtime (Karaf) and you can emulate this using the Spring tab in the Studio.