Improve JMS connector to replace JMS transport in MI
Current Limitation
There is a new HTTP connector as a replacement for the endpoints. Similarly the the old JMS connector should be revamped with new JMS standards to become an alternative for the JMS transport.
[1] - https://github.com/wso2-extensions/esb-connector-jms
Suggested Improvement
Revamp the old JMS connector. https://github.com/wso2-extensions/esb-connector-jms
Version
No response
Hello @arunans23, I have analysed the issue you are currently pointing out. I'll work on it if you can give me a chance to do it, and I highly appreciate it.
Thank you for assigning me to this task.
Hello there @arunans23,
I'd love to help out with this improvement. Could you please confirm which repository you'd recommend contributing to for revamping the JMS connector?
Should the work be done directly in wso2-extensions/esb-connector-jms, or is there another repo you'd suggest for implementing the updated connector?
Happy to get started once that's clarified! 🚀
@Sanjaya-Samudra. Yeah. these changes should be done in the https://github.com/wso2-extensions/esb-connector-jms. The existing implementation is very old. We need to revamp it so that we can use it as a connector to send messages to JMS brokers like activemq.
Sample http connector : https://github.com/wso2-extensions/mi-connector-http Create a new connector : https://mi.docs.wso2.com/en/latest/develop/customizations/creating-new-connector/
@Sanjaya-Samudra. Yeah. these changes should be done in the https://github.com/wso2-extensions/esb-connector-jms. The existing implementation is very old. We need to revamp it so that we can use it as a connector to send messages to JMS brokers like activemq.
Sample http connector : https://github.com/wso2-extensions/mi-connector-http Create a new connector : https://mi.docs.wso2.com/en/latest/develop/customizations/creating-new-connector/
Okay, I'll give a closer look and let you know.
Thank you very much.
I have looked on to this and tried to setup the requirments for our project and it all went well.
Build of the wso2-extensions/esb-connector-jms project is also successful and got the target folder with zip file of JMS connector. But don't know what actually need to do with it.
Downloaded MI in my local Machine and ActiveMQ also and run the server it works fine.
Don't know how to add zip file to MI, cause MI works fine in the console with [2025-10-17 13:22:10,549] INFO {StartupFinalizer} - WSO2 Micro Integrator started in 28.73 seconds message but coudn't load the UI of it in my web browser. Can you please help me with it? like, need to know how to load the Management Console and if there any updates have to be taken in order to do this.
And the other thing I want to know is the path I have taken is correct or not? Cause I can't launch the https://localhost:9443/carbon
Pls guide me, Appreciate your support, Sanjaya.