[resolved] Problem deploying services on Karaf (not start)

One Star

[resolved] Problem deploying services on Karaf (not start)

Hi,
We're working with Talend 5.2.2 developing REST services and deploying them on Apache Karaf. We use JRE 1.6. We've three environments: development (DEV), preproduction (PRE) and production (PRO). In DEV we've do it with success and all work fine.
We work and develop in DEV, then tested and checked services are uploaded to other environments modifying some parameters (SQL conexions and tRESTRequest Endpoint), where only it's installed Runtime ESBSE with Karaf, but not the Studio.
An image to explain it:

So, what is our problem?
In DEV we've checked that karaf start correctly our services and other default bundles, however, in PRE any bundle is started.
Any idea? security restrictions? any port closed or blocked by firewall?? we've checked the ports used by karaf (admin:list) and all are opened by our admin; also we've test some commands as : testb:start-all, osgi:start ID, tesb:start-locator, tesb:start-sam, tesb:start-sts and any bundle start.



Thanks
Cheers

Accepted Solutions
One Star

Re: [resolved] Problem deploying services on Karaf (not start)

Hi,
We have just resolved it. We have reinstalled whole our software, but the issue persists, so we used testb:start-all command on Karaf's console and system bundles have started.
Thanks for your time Sabrina.
Cheers

All Replies
Moderator

Re: [resolved] Problem deploying services on Karaf (not start)

Hi,
Regardless the state, is the service cannot be used normally in your pre-production? Is there any error log info which is located in <talend runtime installation path>\container\log\tesb.log?
Best regards
Sabrina
--
Don't forget to give kudos when a reply is helpful and click Accept the solution when you think you're good with it.
One Star

Re: [resolved] Problem deploying services on Karaf (not start)

Hi Sabrina,
Thanks by your reply.
Tesb.log is Ok, only appears one error, but it's the same that we can see in DEVELOPMENT environment, and there services work ok:
You can download the complete log from https://app.box.com/s/b5rp70fba0n9ko2gbbd5
12:40:29,287 | ERROR | rint Extender: 1 | container.BlueprintContainerImpl 364 | 9 - org.apache.aries.blueprint - 0.3.2 | Unable to start blueprint container for bundle org.apache.karaf.shell.ssh
org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to intialize bean sshServerFactory
at org.apache.aries.blueprint.container.BeanRecipe.runBeanProcInit(BeanRecipe.java:640)
at org.apache.aries.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:726)
at org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:64)
at org.apache.aries.blueprint.container.BlueprintRepository.createInstances(BlueprintRepository.java:219)
at org.apache.aries.blueprint.container.BlueprintRepository.createAll(BlueprintRepository.java:147)
at org.apache.aries.blueprint.container.BlueprintContainerImpl.instantiateEagerComponents(BlueprintContainerImpl.java:631)
at org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:337)
at org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:230)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NoSuchMethodError: org.apache.mina.core.service.IoAcceptor.bind(Ljava/net/SocketAddressSmiley WinkV
at org.apache.sshd.SshServer.start(SshServer.java:374)
at org.apache.karaf.shell.ssh.SshServerFactory.start(SshServerFactory.java:48)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.aries.blueprint.utils.ReflectionUtils.invoke(ReflectionUtils.java:225)
at org.apache.aries.blueprint.container.BeanRecipe.invoke(BeanRecipe.java:838)
at org.apache.aries.blueprint.container.BeanRecipe.runBeanProcInit(BeanRecipe.java:638)
... 15 more

Thanks,
Cheers.
Moderator

Re: [resolved] Problem deploying services on Karaf (not start)

Hi,
We work and develop in DEV, then tested and checked services are uploaded to other environments modifying some parameters (SQL conexions and tRESTRequest Endpoint), where only it's installed Runtime ESBSE with Karaf, but not the Studio.

Did you use Talend ESB Enterprise Subscription version (Talend 5.2.2)? If so, it suggest you open a ticket on Talend Support Portal so that we can schedule a webex with you(Remote assistance).
Best regards
Sabrina
--
Don't forget to give kudos when a reply is helpful and click Accept the solution when you think you're good with it.
One Star

Re: [resolved] Problem deploying services on Karaf (not start)

Hi Sabrina,
We've Talend Integration Subscription 5.2.1, but we're using Talend ESB 5.2.2 to develop and deploy our WS. We've opened a ticket with our issue, but your suggestion (webex) would be great!! do you know if we can do it with our subscription?
Thanks
Cheers
One Star

Re: [resolved] Problem deploying services on Karaf (not start)

Hi,
We have just resolved it. We have reinstalled whole our software, but the issue persists, so we used testb:start-all command on Karaf's console and system bundles have started.
Thanks for your time Sabrina.
Cheers
Moderator

Re: [resolved] Problem deploying services on Karaf (not start)

Hi,
Thanks for your feedback. Don't hesitate to post your issue on forum.
Best regards
Sabrina
--
Don't forget to give kudos when a reply is helpful and click Accept the solution when you think you're good with it.