Welcome to apibusinesshub-integration-recipes Discussions!

[aadinigam]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[vishal11ingale]

Hello Mayur,

Your blog and resources on Apache Camel Redis component as SAP Cloud Platform Integration Adapter are really helpful. I have followed all the steps as described. I was able to create .esa file and deploy it in SAP CPI tenant.

However, I am facing the issue to use it in iflow. Redis iflow is not getting deployed as I am getting the error as shown below. It would be great help if you can guide to resolve it as early as possible. Thank you in advance for your help.

Error Details

[CONTENT][CONTENT_DEPLOY][InstanceError] : {"message":"ERROR","childMessageInstances":[{"message":"EXCEPTION","parameters":["java.util.concurrent.TimeoutException"]},{"message":"UNRESOLVED","parameters":["(&(component=spring-redis)(objectClass=org.apache.camel.spi.ComponentResolver))"]}]}

[mayurmohan]

Error seems adapter is not available for iflow in runtime. show me your iflow design and configuration for redis

[vishal11ingale]

Hello Mayur, please find the iflow design below and configuration for redis channel. It's same which you have already provided in your blog and github.

Please help on resolving this issue.

[vishal11ingale]

Error seems adapter is not available for iflow in runtime. show me your iflow design and configuration for redis

Hello Mayur, please find the iflow design below and configuration for redis channel. It's same which you have already provided in your blog and github.

Awaiting for your reply.

[vishal11ingale]

Hello Mayur, It is in Cloud foundry. Yes I have deployed integration adaptor and it is visible under the manage integration content. Also I can see this adaptor in the adaptor list. However when I try to deploy the iflow provided in the blog/GitHub on the tenant, it gives this error. Could you please help me with this? Thanks and Regards, Vishal Ingale.

…

On Tue, Feb 8, 2022, 4:38 PM Mayur Belur Mohan ***@***.***> wrote: is it neo or cf? have you deployed integration adapter ? error seems adapter is not available for iflow in runtime — Reply to this email directly, view it on GitHub <#27 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXUVQ5C7FLFQPDMXPR2PILTU2D2S7ANCNFSM4VSVMTSA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: <SAP/apibusinesshub-integration-recipes/repo-discussions/27/comments/2132479 @github.com>

[sunil-solace]

@mayurmohan I get a similar error as posted by @vishal11ingale
I've a customer adapter built and deployed successfully in the CF and an Integration flow as well. Below is the error that I get for the iFlow deployment. Will appreciate a help in this regard. Thanks!

[CONTENT][CONTENT_DEPLOY][ErrorUnresolvedDependency] : {"message":"ERROR","childMessageInstances":[{"message":"EXCEPTION","parameters":["java.util.concurrent.TimeoutException"]},{"message":"UNRESOLVED","parameters":["(&(component=sap-sol)(objectClass=org.apache.camel.spi.ComponentResolver))"]}]}

[sunil-solace]

This problem start when we include a new dependency into the custom adapter and configure felix maven bundle plugin to Import package. If that's not imported we see another issue while deploying the adapter itself.

[sunil-solace]

After making Embed-Dependency exclusions to felix maven bundle plugin, the next error I get is
[CONTENT][CONTENT_DEPLOY][InstanceError] : {"message":"CAMEL_CONTEXT_NOT_STARTED"}

[mayurmohan]

please try this

1. take Karaf runtime
2. provision apache camel 2.17,4
3. Start your karaf console and check Camel is provisioned properly
4. deploy your jar ( not ESA) there and check camel component coming up or not?
   if this works in this environment , without any issues. it will work in our runtime as well.

[sunil-solace]

I've built my custom Adapter with Camel version 2.24.* will that not work in Camel 2.17 Karaf runtime?
I see the following error:
2023-03-19 20:06:24,392 | INFO | l for user karaf | BlueprintContainerImpl | 15 - org.apache.aries.blueprint.core - 1.6.1 | Bundle sapsolexample.xml/0.0.0 is waiting for dependencies [(&(component=sap-sol)(objectClass=org.apache.camel.spi.ComponentResolver))] 2023-03-19 20:11:24,170 | INFO | rint Extender: 1 | BlueprintCamelContext | 70 - org.apache.camel.camel-core - 2.17.7 | Apache Camel 2.17.7 (CamelContext: camel-1) is shutting down 2023-03-19 20:11:24,182 | INFO | rint Extender: 1 | BlueprintCamelContext | 70 - org.apache.camel.camel-core - 2.17.7 | Apache Camel 2.17.7 (CamelContext: camel-1) uptime 2023-03-19 20:11:24,186 | INFO | rint Extender: 1 | BlueprintCamelContext | 70 - org.apache.camel.camel-core - 2.17.7 | Apache Camel 2.17.7 (CamelContext: camel-1) is shutdown in 0.016 seconds 2023-03-19 20:11:24,188 | ERROR | rint Extender: 1 | BlueprintContainerImpl | 15 - org.apache.aries.blueprint.core - 1.6.1 | Unable to start blueprint container for bundle sapsolexample.xml/0.0.0 due to unresolved dependencies [(&(component=sap-sol)(objectClass=org.apache.camel.spi.ComponentResolver))] java.util.concurrent.TimeoutException at org.apache.aries.blueprint.container.BlueprintContainerImpl$1.run(BlueprintContainerImpl.java:371)[15:org.apache.aries.blueprint.core:1.6.1] at org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:48)[15:org.apache.aries.blueprint.core:1.6.1] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_311] at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_311] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)[:1.8.0_311] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)[:1.8.0_311] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)[:1.8.0_311] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)[:1.8.0_311] at java.lang.Thread.run(Thread.java:748)[:1.8.0_311]

However, after installing the jar as a bundle in ~/deploy folder, I see the following bundle:headers :
`
karaf@root()> bundle:headers 113

SapBtpSolConnector.SapBtpSolConnector (113)

Embed-Dependency = *;scope=provided
Embed-Transitive = true
Build-Jdk-Spec = 1.8
Created-By = Apache Maven Bundle Plugin 5.1.8
Manifest-Version = 1.0
Bnd-LastModified = 1679270505811
Embedded-Artifacts = sol-jcsmp-10.17.0.jar;g="com.solacesystems";a="sol-jcsmp";v="10.17.0",commons-logging-1.2.jar;g="commons-logging";a="commons-logging";v="1.2",org.osgi.annotation-6.0.0.jar;g="org.osgi";a="org.osgi.annotation";v="6.0.0",org.apache.servicemix.bundles.jzlib-1.0.7_2.jar;g="org.apache.servicemix.bundles";a="org.apache.servicemix.bundles.jzlib";v="1.0.7_2"
Tool = Bnd-6.3.1.202206071316

Bundle-ManifestVersion = 2
Bundle-SymbolicName = SapBtpSolConnector
Bundle-Version = 1.0.0
Bundle-Name = SapBtpSolConnector.SapBtpSolConnector
Bundle-ClassPath = .,sol-jcsmp-10.17.0.jar,commons-logging-1.2.jar,org.osgi.annotation-6.0.0.jar,org.apache.servicemix.bundles.jzlib-1.0.7_2.jar

Require-Capability =
osgi.ee;filter:=(&(osgi.ee=JavaSE)(version=1.8))

Export-Package =
sapbtpsolconnector;uses:="org.apache.camel,org.apache.camel.impl,org.apache.camel.spi";version=1.0.0
Import-Package =
org.apache.avalon.framework.logger;resolution:=optional,
org.apache.camel;resolution:=optional;version="[2.24,3)",
org.apache.camel.impl;resolution:=optional;version="[2.24,3)",
org.apache.camel.spi;resolution:=optional;version="[2.24,3)",
org.apache.log;resolution:=optional,
org.apache.log4j;resolution:=optional,
org.ietf.jgss;resolution:=optional,
org.slf4j;resolution:=optional;version="[1.6,2)",
org.xml.sax;resolution:=optional,
org.xml.sax.ext;resolution:=optional,
org.xml.sax.helpers;resolution:=optional
`

[mayurmohan]

I've built my custom Adapter with Camel version 2.24.* will that not work in Camel 2.17 Karaf runtime?

provision karaf with 2.24.2 only in that case.

Require-Capability =
osgi.ee;filter:=(&(osgi.ee=JavaSE)(version=1.8))

this means you should have this runtime available, ensure karaf using this runtime.

[sunil-solace]

Thanks @mayurmohan for the all the pointers so far! I'm now able to run my Custom Integration Adapter (JAR file) in Karaf v4.2.16. The adapter is built using Camel v2.24.2 and installed the same version of Camel even in the Karaf runtime. So my local setup is all functional, however when the same project's ESA file is deployed, the IFlows are still failing with this error [CONTENT][CONTENT_DEPLOY][RuntimeError] : {"message":"CAMEL_CONTEXT_NOT_STARTED"}. The Integration Adapter deployment is successful though.

Here's the IFlow blueprint beans file:

<blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0" xmlns:Generator="com.sap.it.gnb.ifl.common.gen.pluggability.api.GeneratorHandler" xmlns:bsn="http://sapcd.com/bsnagt" xmlns:camel="http://camel.apache.org/schema/blueprint" xmlns:cxf="http://camel.apache.org/schema/blueprint/cxf" xmlns:cxfcore="http://cxf.apache.org/blueprint/core" xmlns:exsl="http://exslt.org/common" xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0" xmlns:hci-ph="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.0.0" xmlns:http-conf="http://cxf.apache.org/transports/http/configuration" xmlns:idocsoap="urn:sap-com:document:sap:idoc:soap:messages" xmlns:jaxws="http://cxf.apache.org/blueprint/jaxws" xmlns:ns="https://bsnschemas.netweaver.neo.com/bsnflow" xmlns:orange="http://xi.com/orange" xmlns:sap-cxf-generic-request="http://camel.apache.org/cxf/jaxws/dispatch" xmlns:sap-cxf-generic-request-reply="http://camel.apache.org/cxf/jaxws/provider" xmlns:sec="http://cxf.apache.org/configuration/security" xmlns:str="http://exslt.org/strings" xmlns:wsa="http://cxf.apache.org/ws/addressing" xmlns:wsrm-mgr="http://cxf.apache.org/ws/rm/manager" xmlns:wsrm-policy="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0 http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd http://camel.apache.org/schema/blueprint http://camel.apache.org/schema/blueprint/camel-blueprint.xsd http://camel.apache.org/schema/blueprint/cxf http://camel.apache.org/schema/blueprint/cxf/camel-cxf.xsd http://cxf.apache.org/blueprint/core http://cxf.apache.org/schemas/blueprint/core.xsd http://cxf.apache.org/transports/http/configuration http://cxf.apache.org/schemas/configuration/http-conf.xsd http://cxf.apache.org/ws/rm/manager http://cxf.apache.org/schemas/configuration/wsrm-manager.xsd http://schemas.xmlsoap.org/ws/2005/02/rm/policy http://schemas.xmlsoap.org/ws/2005/02/rm/wsrm-policy.xsd http://cxf.apache.org/configuration/security http://cxf.apache.org/schemas/configuration/security.xsd http://cxf.apache.org/policy http://cxf.apache.org/schemas/policy.xsd http://cxf.apache.org/blueprint/jaxws http://cxf.apache.org/schemas/blueprint/jaxws.xsd"> <reference id="cxfTracingFeatureFactory" interface="com.sap.it.op.agent.trace.cxf.CxfTracingFeatureFactory"/> <bean class="com.sap.esb.monitoring.cxf.runtime.feature.RuntimeFeature" id="cxf.feature.RuntimeFeature"/> <reference id="customClassResolver" interface="org.apache.camel.spi.ClassResolver"/> <reference id="MessageProcessingLogSink" interface="com.sap.it.op.agent.api.MessageProcessingLogSink"/> <reference id="IntegrationOperationsErrorEventPublisher" interface="com.sap.it.op.ed.IntegrationOperationsErrorEventPublisher"/> <bean class="com.sap.it.op.agent.collector.camel.MplInterceptor" id="itOpAgentMplInterceptor"/> <bean class="com.sap.it.op.agent.collector.camel.MplEventNotifier" id="itOpAgentMplEventNotifier"> <property name="messageProcessingLogSink"> <ref component-id="MessageProcessingLogSink"/> </property> </bean> <bean class="com.sap.it.op.agent.collector.camel.CustomShutdownStrategy" id="CustomShutdownStrategy"> <property name="timeout" value="60"/> <property name="suppressLoggingOnTimeout" value="true"/> <property name="shutdownNowOnTimeout" value="true"/> </bean> <reference id="secureStore" interface="com.sap.it.nm.security.SecureStore"/> <bean class="com.sap.esb.secure.parameter.impl.SecureParameterAccessFactoryImpl" id="secureParameterAccessFactory"> <property name="secureParameterStorage" ref="secureStore"/> </bean> <reference id="clusterLockManager" interface="com.sap.it.nm.concurrent.ClusterLockManager"/> <reference id="authenticationHeaderProvider" interface="com.sap.it.nm.security.AuthenticationHeaderProvider"/> <bean class="java.util.HashMap" id="userdefinedNamespaces"/> <camel:camelContext id="testBasicSolConFlow" streamCache="true"> <camel:properties> <camel:property key="CamelLogDebugBodyMaxChars" value="-1"/> <camel:property key="CamelMaximumEndpointCacheSize" value="50"/> </camel:properties> <camel:streamCaching id="testBasicSolConFlow_cacheConfig" spoolChiper="AES/CTR/NoPadding" spoolDirectory="${karaf.base}/camel/camel-tmp-#camelId#-#uuid#" spoolThreshold="5242880" spoolUsedHeapMemoryThreshold="50"/> <camel:route id="Process_1"> <camel:from id="MessageFlow_4_999775175409310" uri="sap-sol:queue:testQueue?thisPd=xxxxx&amp;msgVpn=yyyyy&amp;host=hhhhhhhh&amp;username=uuuuuu"/> <camel:to uri="sap-pp-util://sender"/> <camel:removeHeaders excludePattern="(?i)CamelRedeliveryMaxCounter" pattern="*"/> <camel:setProperty id="EndEvent_2_999775182274645" propertyName="SAP_MarkMessageAsFailed"> <camel:constant>false</camel:constant> </camel:setProperty> </camel:route> </camel:camelContext> </blueprint>

[mayurmohan]

please create a camel route to test your component and test it and make sure its works in karaf itself first.

[sunil-solace]

@mayurmohan sorry if you've misunderstood my above comment, I was successfully able to test with Solace Adapter route in my local, but the above blue print bean I gave is from the iFlow Jar file which I created for the Custom Adapter in SAP Integration iFlow.

[mayurmohan]

this error is [CONTENT][CONTENT_DEPLOY][RuntimeError] : {"message":"CAMEL_CONTEXT_NOT_STARTED"} very generic. complete stack trace required from system logs

[sunil-solace]

Mayur, that error is what I get from SAP's Integration Flow deployment.

Where in my local, its all running fine, as below:

[mayurmohan]

as i said more exception stack trace required to debug this. camel context may not start if dependency is missing or some other error.

[sunil-solace]

But as you said, if it works in my local Karaf runtime, it should work here as well. It fails in the SAP environment, and the above logs in the screenshot is what I have, is there a way to pull detailed logs? I'm pretty sure the dependencies are all in place as I am able to run locally.

[mayurmohan]

<camelContext xmlns="http://camel.apache.org/schema/blueprint">
	<route id="timerToLog">
		<from uri="timer:foo?repeatCount=1&amp;period=5000" />
		<setBody>
			<constant>TestingCPI</constant>
		</setBody>
		<to uri="kafka:test?brokers=pkc-lq8gm.westeurope.azure.confluent.cloud:9092&amp;serializerClass=org.apache.kafka.common.serialization.StringSerializer&amp;topic=cpi
		&amp;securityProtocol=SASL_SSL&amp;sslEndpointAlgorithm=HTTPS&amp;saslJaasConfig=org.apache.kafka.common.security.plain.PlainLoginModule%20required%20username%3D%22%22%20password%3D%22fgarZFlvfGblmPpqgBiZG9lkqzbB1tfzUf%22"/>

	</route>
</camelContext>

[mayurmohan]

ensure you put try catch in CamelComponent main interface and Camel Producer side implementation to grab actual exception and also put some dummy log to see weather Camel Producer side getting instantiated properly.

[mayurmohan]

Ideally URI should not be used to fetch some endpoint parameters like Queue, its for host:port purposes.

none the less please queue fetching logic out of URI and remove the URI part if possible,

[sunil-solace]

Removed the URI and passing everything as Parameters now. Added more logs but still something fails even before it could be logged. From the system logs I could see this log very often, you have any idea what this is about. Looks like being logged by a SAP agent monitoring the Camel processes.

22:30:45#+0000#ERROR#com.sap.it.op.agent.collector.camel.MplEventNotifier#anonymous#pool-31-thread-1#com.sap.it.op.agent.collector.camel#na#na#na#na#Retry counting repository for sftp polling scenarios could not be stopped: while trying to invoke the method com.sap.it.op.agent.collector.camel.retry.impl.RetryCounterRepository.stop() of a null object loaded from field com.sap.it.op.agent.collector.camel.retry.impl.RetryHandler.retryTrackingRepository of an object loaded from local variable 'this'#-#10.0.201.51#1

Because I've tested this Camel Component thoroughly using UTs and deploying to Karaf, I feel there's some error happening at the SAP side converting the UI input into blueprint and validation of fields.
Both Producers and Consumers are getting initialized in Karaf.

[mayurmohan]

this is not issue with SAP side. in the logs where exactly its failing? in the component interface or end point or came consumer/camel producer side?

[sunil-solace]

The problem is we don't see any error in the log nor the detailed INFO level logger, Mayur. It is therefore difficult to understand where the problem is. Even as I said before, I'm able to run the JAR successfully in my local Karaf.

Can you confirm which version of Camel in installed in the env and remember that this adapter is built using Camel v2.24.2, will it cause any incompatibility with the version of Camel run in the SAP's Karaf runtime?

[mayurmohan]

2023-03-22T08:07:59.991+0000 [APP/PROC/WEB/0] STDOUT
{ "written_at":"2023-03-22T08:07:59.991Z","written_ts":1089274763696546,"tenant_id":"-","component_id":"49d95e70-5cf4-4cda-b48d-d0f8d82082a6",
"component_name":"itw-cpisuite-us-01-0-33","bundle.name":"org.apache.camel.camel-blueprint",
"bundle.id":"784","organization_name":"cpi_prod_us10_org","component_type":"application","space_name":
"prov_us10_cpi003","bundle.version":"2.24.2.sap-31","component_instance":"0","organization_id":"65ef7a72-5a67-48d6-a1c6-1d291900feff",
"correlation_id":"-","space_id":"e5ffb667-6ed3-416f-9469-5c61f31416c2","container_id":"10.0.73.74","type":"log",
"logger":"org.apache.camel.blueprint.BlueprintCamelContext","thread":"Blueprint Event Dispatcher: 1","level":"ERROR",
"categories":[],"msg":"Error occurred during starting CamelContext: testFlow123",
"stacktrace":["org.apache.camel.FailedToCreateRouteException:
Failed to create route Process_1: Route(Process_1)[[From[sap-sol:foo?thisPd=5qjmfr60j92faqtpna...
because of while trying to invoke the method java.lang.String.startsWith(java.lang.String) of a null object loaded from local variable
'name'","\tat org.apache.camel.impl.RouteService.warmUp(RouteService.java:147)",
"\tat org.apache.camel.impl.DefaultCamelContext.doWarmUpRoutes(DefaultCamelContext.java:3954)",
"\tat org.apache.camel.impl.DefaultCamelContext.safelyStartRouteServices(DefaultCamelContext.java:3861)",
"\tat org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRoutes(DefaultCamelContext.java:3647)","\tat
org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:3488)",
"\tat org.apache.camel.impl.DefaultCamelContext$4.call(DefaultCamelContext.java:3247)",
"\tat org.apache.camel.impl.DefaultCamelContext$4.call(DefaultCamelContext.java:3243)",
"\tat org.apache.camel.impl.DefaultCamelContext.doWithDefinedClassLoader(DefaultCamelContext.java:3266)",
"\tat org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:3243)",
"\tat org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:78)",
"\tat org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:3159)",
"\tat org.apache.camel.blueprint.BlueprintCamelContext.start(BlueprintCamelContext.java:255)",
"\tat org.apache.camel.blueprint.BlueprintCamelContext.maybeStart(BlueprintCamelContext.java:297)",
"\tat org.apache.camel.blueprint.BlueprintCamelContext.blueprintEvent(BlueprintCamelContext.java:188)",
"\tat org.apache.aries.blueprint.container.BlueprintEventDispatcher$3.call(BlueprintEventDispatcher.java:197)",
"\tat org.apache.aries.blueprint.container.BlueprintEventDispatcher$3.call(BlueprintEventDispatcher.java:195)",
"\tat java.util.concurrent.FutureTask.run(FutureTask.java:266)",
"\tat java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)",
"\tat java.util.concurrent.FutureTask.run(FutureTask.java:266)",
"\tat java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)",
"\tat java.util.concurrent.FutureTask.run(FutureTask.java:266)",
"\tat java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:182)",
"\tat java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:295)",
"\tat java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)",
"\tat java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)",
"\tat java.lang.Thread.run(Thread.java:838)","Caused by: java.lang.NullPointerException: while trying to invoke the method java.lang.String.startsWith(java.lang.String) of a null object loaded from local variable 'name'",
"\tat com.solacesystems.jcsmp.impl.QueueImpl.createWithInit(QueueImpl.java:111)",
"\tat com.solacesystems.jcsmp.impl.QueueImpl.userCreateWithInit(QueueImpl.java:101)",
"\tat com.solacesystems.jcsmp.impl.QueueImpl.userCreateWithInit(QueueImpl.java:97)",
"\tat com.solacesystems.jcsmp.JCSMPFactory.createQueue(JCSMPFactory.java:787)",
"\tat sapbtpsolconnector.SapBtpSolConnectorConsumer.subscribeToQueue(SapBtpSolConnectorConsumer.java:80)",
"\tat sapbtpsolconnector.SapBtpSolConnectorConsumer.(SapBtpSolConnectorConsumer.java:63)",
"\tat sapbtpsolconnector.SapBtpSolConnectorEndpoint.createConsumer(SapBtpSolConnectorEndpoint.java:56)",
"\tat org.apache.camel.impl.EventDrivenConsumerRoute.addServices(EventDrivenConsumerRoute.java:69)",
"\tat org.apache.camel.impl.DefaultRoute.onStartingServices(DefaultRoute.java:107)",
"\tat org.apache.camel.impl.RouteService.doWarmUp(RouteService.java:172)",
"\tat org.apache.camel.impl.RouteService.warmUp(RouteService.java:145)","\t... 25 more"] }

[sunil-solace]

Also it could be wrt to the SDK vendor being used in SAP runtime, it could be that you're using a custom JDK version?

[mayurmohan]

you can find answer herre https://answers.sap.com/questions/13161342/what-jdk-version-does-cpi-run-on.html
SAP JVM 8 JDK which is based on OPENJDK (https://sap.github.io/SapMachine/)

[sunil-solace]

I see, what's the long term solution you propose for the missing missing module java.security.jgss in the SAP JDK version used in CPI?

Also I see that the latest ADK v2.1.1 is launching Camel 3.x dependencies, which means the CPI should also support JDK 11 now, right? Is the JDK 11 support already available or will be available soon?
<dependency> <groupId>com.sap.cloud.adk</groupId> <artifactId>com.sap.cloud.adk.build.archive</artifactId> <version>2.1.1</version> </dependency>

[mayurmohan]

please raise ticket for the component LOD-HCI-PI-ASDK to get the answer on the same

[mayurmohan]

you can create your own OSGI JAR like openmdx-dalvik embedding the module java.security.jgss and use it in the adapter.

[mayurmohan]

this is the complete exception stack. after full analysis i see a blocker in this implementation. we dont support JAVA 11 in our runtime, your Secure SMF TCPS needs it seems. so we cant connect using TCPS with java runtime 8 to your solace cloud VMR using sol-jcsmp 10.17.0.