Skip to main content
Announcements
Introducing Qlik Answers: A plug-and-play, Generative AI powered RAG solution. READ ALL ABOUT IT!
cancel
Showing results for 
Search instead for 
Did you mean: 
oandgtc
Contributor
Contributor

Talend ESB 5.6 deployed Web Service Starting Problem in Runtime

Folks
I'm new to Talend ESB but I have created a SOAP web service that does some simple data serving. It has two operations and they work perfectly in Studio (one at a time) and I can query the wsdl using SOAP UI as expected. When I export the service (to a kar file) and deploy using the Karaf deploy folder it shows in list as Active and Created but the bundle will not start. I have a zookeeper message as follows
"Got user-level KeeperException when processing sessionid:0x14f4a23e08f0001 type:delete cxid:0xf zxid:0xfffffffffffffffe txntype:unknown reqpath:n/a Error Path:/cxf-locator/{http:%2F%2Fwww.talend.org%2Fservice%2F}licenses/http:%2F%2Flocalhost:8040%2Fservices%2Flicenses/timetolive Error:KeeperErrorCode = NoNode for /cxf-locator/{http:%2F%2Fwww.talend.org%2Fservice%2F}licenses/http:%2F%2Flocalhost:8040%2Fservices%2Flicenses/timetolive"
But nothing else that I can see.
Could someone please tell me what the requirements are for the Runtime for deployed apps to run ? - I have the same issue when I deploy the demo services (CRM and so on)
I'm running 5.6.6.2 TOS_ESB on Mac OSX but I have tried the same jobs on Linux without success also.

Labels (2)
3 Replies
Anonymous
Not applicable

On the machine running the Karaf (otherwise change localhost to the ip address) have you tested this url (http://localhost:8040/services/)? It will show you which services are actually running. I suspect that your service endpoints have changed to suit the Karaf environment. By default it will add "services" to your endpoint and change the port to 8040.
oandgtc
Contributor
Contributor
Author

Thanks rhall_2.0, spot on.
How do I can the Karaf behaviour so that the endpoint specified in the Talend Service is honoured ? 
Thank you
Anonymous
Not applicable

You can check the logs in Karaf with log:display or log:display-exception. When deploying webservices in Karaf it will use the Jetty instance running. You should always use relative paths foe endpoints in your jobs when deploying to Karaf and if you need to change the bind port, change the jetty.xml in /etc inside the runtime, if you dont like the /services path for CXF edit org.apache.cxf.osgi.cfg in /etc.