date:20180223

[jira] [Commented] (CAMEL-12291) Blueprint error: "name is already instanciated as null and cannot be removed"

2018-02-23 Thread Grzegorz Grzybek (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-12291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16375338#comment-16375338
 ] 

Grzegorz Grzybek commented on CAMEL-12291:
--

The fix for CAMEL-12251 should not help with original problem - it should just 
make it visible in logs ;)

> Blueprint error: "name is already instanciated as null and cannot be removed"
> -
>
> Key: CAMEL-12291
> URL: https://issues.apache.org/jira/browse/CAMEL-12291
> Project: Camel
>  Issue Type: Bug
>  Components: camel-blueprint
>Affects Versions: 2.20.2
> Environment: Mac OSX, {color:#00}Karaf 4.2.5{color}
>Reporter: Alex Soto
>Assignee: Grzegorz Grzybek
>Priority: Major
>
> The error "name is already instanciated (sic) as null and cannot be removed" 
> is thrown when configuring a component in Blueprint using property 
> placeholders.
> I noticed when trying to migrate my project to Camel 2.20.2 (from 2.17.4) 
>  Example:
> {code:java}
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
> xmlns:camel="http://camel.apache.org/schema/blueprint;
> xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;
> xsi:schemaLocation="
>               http://www.osgi.org/xmlns/blueprint/v1.0.0 
>      https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd”>
>  
> persistent-id="audit.log"
>update-strategy="reload” 
>placeholder-prefix="#{" placeholder-suffix="}">
>
>   
>   
>
> 
>  class="org.apache.camel.component.quartz2.QuartzComponent">
> 
> {code}
>   
>  The bean is referenced in a Camel route:
> {code:java}
> 
>      
> {code}
> Throws exception:
> {quote}org.osgi.service.blueprint.container.ComponentDefinitionException: 
> Name audit-log-reaper-quartz is already +instanciated+ as null and cannot be 
> removed.
>  at 
> org.apache.aries.blueprint.container.BlueprintRepository.removeRecipe(BlueprintRepository.java:131)
>  [38:org.apache.aries.blueprint.core:1.8.3]
>  at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.updateUninstantiatedRecipes(BlueprintContainerImpl.java:572)
>  [38:org.apache.aries.blueprint.core:1.8.3]
>  at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.processProcessors(BlueprintContainerImpl.java:559)
>  [38:org.apache.aries.blueprint.core:1.8.3]
>  at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:394)
>  [38:org.apache.aries.blueprint.core:1.8.3]
>  at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:275)
>  [38:org.apache.aries.blueprint.core:1.8.3]
> {quote}
>  
>   
>  Removing the property placeholder fixes the issue:
>   
> {code:java}
>    class="org.apache.camel.component.quartz2.QuartzComponent">
>   
>   
> 
> {code}
>  
>  According to Guillaume Nodet, this seems to have been introduced by this 
> pull request:
> [https://github.com/apache/camel/commit/a4e94f036d02943814c84195d73837cf607c8c20]
> Solution proposed by Guillaume Nodet is to change line 1056 of 
> /camel-blueprint/src/main/java/org/apache/camel/blueprint/handler/CamelNamespaceHandler.java
> to
> {code:java}
>  if (camelContext.getComponent(component, false) == null) {
> {code}
> I tested this change locally and it seems to work, however I don't know if 
> this can cause other problems.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (CAMEL-12289) URISyntaxException in AbstractSpanDecorator

2018-02-23 Thread Radek Mensik (JIRA)

Radek Mensik created CAMEL-12289:


 Summary: URISyntaxException in AbstractSpanDecorator
 Key: CAMEL-12289
 URL: https://issues.apache.org/jira/browse/CAMEL-12289
 Project: Camel
  Issue Type: Bug
  Components: camel-opentracing
Affects Versions: 2.20.2
Reporter: Radek Mensik


Fix provided in CAMEL-12098 does not solve whole problem. As there are still 
curly brackets in URL, it fails  in AbstractDecorator in method pre(...), where 
is again used URI.createSchema().

I checked and URI.create(endpoint.getEndpointUri()) is also in 2 other 
decorators, but there is probably not happening that {} are used in path..

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (CAMEL-12290) CxfEndpoint with JDK9: NoClassDefFoundError: javax/jws/WebService

2018-02-23 Thread Kamil (JIRA)

Kamil created CAMEL-12290:
-

 Summary: CxfEndpoint with JDK9: NoClassDefFoundError: 
javax/jws/WebService
 Key: CAMEL-12290
 URL: https://issues.apache.org/jira/browse/CAMEL-12290
 Project: Camel
  Issue Type: Improvement
  Components: camel-cxf
Affects Versions: 2.20.1
Reporter: Kamil


When I tried to run tests on JDK9 I get:
{code:java}
java.lang.NoClassDefFoundError: javax/jws/WebService
at 
org.apache.camel.component.cxf.CxfEndpointUtils.hasWebServiceAnnotation(CxfEndpointUtils.java:88)
at 
org.apache.camel.component.cxf.CxfEndpoint.createClientFactoryBean(CxfEndpoint.java:394)
at org.apache.camel.component.cxf.CxfEndpoint.createClient(CxfEndpoint.java:635)
at org.apache.camel.component.cxf.CxfProducer.doStart(CxfProducer.java:84)
at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
at 
org.apache.camel.impl.SynchronousDelegateProducer.start(SynchronousDelegateProducer.java:66)
at org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:75)
at 
org.apache.camel.impl.DeferServiceStartupListener.onCamelContextStarted(DeferServiceStartupListener.java:49)
at 
org.apache.camel.impl.DefaultCamelContext.safelyStartRouteServices(DefaultCamelContext.java:3859)
at 
org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRoutes(DefaultCamelContext.java:3638)
at 
org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:3490)
at 
org.apache.camel.impl.DefaultCamelContext.access$000(DefaultCamelContext.java:208)
at 
org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3249)
at 
org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3245)
at 
org.apache.camel.impl.DefaultCamelContext.doWithDefinedClassLoader(DefaultCamelContext.java:3268)
at 
org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:3245)
at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
at 
org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:3168)
at org.apache.camel.spring.SpringCamelContext.start(SpringCamelContext.java:133)
at 
org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:174)
at 
org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172)
at 
org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165)
at 
org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139)
at 
org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:393)
at 
org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:347)
at 
org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:883)
at 
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:546)
at 
org.springframework.boot.SpringApplication.refresh(SpringApplication.java:693)
at 
org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:360)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:303)
at 
org.springframework.boot.test.context.SpringBootContextLoader.loadContext(SpringBootContextLoader.java:120)
at 
org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContextInternal(DefaultCacheAwareContextLoaderDelegate.java:98)
at 
org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContext(DefaultCacheAwareContextLoaderDelegate.java:116)
at 
org.springframework.test.context.support.DefaultTestContext.getApplicationContext(DefaultTestContext.java:83)
at 
org.springframework.test.context.web.ServletTestExecutionListener.setUpRequestContextIfNecessary(ServletTestExecutionListener.java:189)
at 
org.springframework.test.context.web.ServletTestExecutionListener.prepareTestInstance(ServletTestExecutionListener.java:131)
at 
org.springframework.test.context.TestContextManager.prepareTestInstance(TestContextManager.java:230)
at 
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.createTest(SpringJUnit4ClassRunner.java:228)
at 
org.springframework.test.context.junit4.SpringJUnit4ClassRunner$1.runReflectiveCall(SpringJUnit4ClassRunner.java:287)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.methodBlock(SpringJUnit4ClassRunner.java:289)
at 
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:247)
at 
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:94)
at

[jira] [Commented] (CAMEL-12289) URISyntaxException in AbstractSpanDecorator

2018-02-23 Thread Radek Mensik (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-12289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16374511#comment-16374511
 ] 

Radek Mensik commented on CAMEL-12289:
--

I can submit fix with only changes in AbstractSpanDecorator:
{code:java}
Index: 
components/camel-opentracing/src/main/java/org/apache/camel/opentracing/decorators/AbstractSpanDecorator.java
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
<+>UTF-8
===
--- 
components/camel-opentracing/src/main/java/org/apache/camel/opentracing/decorators/AbstractSpanDecorator.java
    (revision 65b5394ff4645cb47e1bdd6060d100bfe4293a09)
+++ 
components/camel-opentracing/src/main/java/org/apache/camel/opentracing/decorators/AbstractSpanDecorator.java
    (date 1519316576424)
@@ -27,6 +27,7 @@
 import org.apache.camel.Exchange;
 import org.apache.camel.opentracing.SpanDecorator;
 import org.apache.camel.util.URISupport;
+import org.apache.camel.util.StringHelper;
 
 /**
  * An abstract base implementation of the {@link SpanDecorator} interface.
@@ -69,11 +70,13 @@
 
 @Override
 public void pre(Span span, Exchange exchange, Endpoint endpoint) {
-    span.setTag(Tags.COMPONENT.getKey(), CAMEL_COMPONENT + 
URI.create(endpoint.getEndpointUri()).getScheme());
+    String endpointUri = endpoint.getEndpointUri();
+    endpointUri = endpointUri.replace("{","(").replace("}",")");
+    span.setTag(Tags.COMPONENT.getKey(), CAMEL_COMPONENT + 
URI.create(endpointUri).getScheme());
 
 // Including the endpoint URI provides access to any options that may 
have been provided, for
 // subsequent analysis
-    span.setTag("camel.uri", 
URISupport.sanitizeUri(endpoint.getEndpointUri()));
+    span.setTag("camel.uri", URISupport.sanitizeUri(endpointUri));
 }
 
 @Override

{code}
This solves my problem with restlet component, but not sure if it is optimal 
solution...

> URISyntaxException in AbstractSpanDecorator
> ---
>
> Key: CAMEL-12289
> URL: https://issues.apache.org/jira/browse/CAMEL-12289
> Project: Camel
>  Issue Type: Bug
>  Components: camel-opentracing
>Affects Versions: 2.20.2
>Reporter: Radek Mensik
>Priority: Major
>
> Fix provided in CAMEL-12098 does not solve whole problem. As there are still 
> curly brackets in URL, it fails  in AbstractDecorator in method pre(...), 
> where is again used URI.createSchema().
> I checked and URI.create(endpoint.getEndpointUri()) is also in 2 other 
> decorators, but there is probably not happening that {} are used in path..
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (CAMEL-12291) Blueprint error: "name is already instanciated as null and cannot be removed"

2018-02-23 Thread Alex Soto (JIRA)

Alex Soto created CAMEL-12291:
-

 Summary: Blueprint error: "name is already instanciated as null 
and cannot be removed"
 Key: CAMEL-12291
 URL: https://issues.apache.org/jira/browse/CAMEL-12291
 Project: Camel
  Issue Type: Bug
  Components: camel-blueprint
Affects Versions: 2.20.2
 Environment: Mac OSX, {color:#00}Karaf 4.2.5{color}
Reporter: Alex Soto
Assignee: Grzegorz Grzybek


The error "name is already instanciated (sic) as null and cannot be removed" is 
thrown when configuring a component in Blueprint using property placeholders.


 I noticed when trying to migrate my project to Camel 2.20.2 (from 2.17.4) 
 Example:
{code:java}

 


   
  
  
   


 


{code}
  
 The bean is referenced in a Camel route:
{code:java}

     
{code}
Throws exception:
{quote}org.osgi.service.blueprint.container.ComponentDefinitionException: Name 
audit-log-reaper-quartz is already +instanciated+ as null and cannot be removed.
 at 
org.apache.aries.blueprint.container.BlueprintRepository.removeRecipe(BlueprintRepository.java:131)
 [38:org.apache.aries.blueprint.core:1.8.3]
 at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.updateUninstantiatedRecipes(BlueprintContainerImpl.java:572)
 [38:org.apache.aries.blueprint.core:1.8.3]
 at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.processProcessors(BlueprintContainerImpl.java:559)
 [38:org.apache.aries.blueprint.core:1.8.3]
 at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:394)
 [38:org.apache.aries.blueprint.core:1.8.3]
 at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:275)
 [38:org.apache.aries.blueprint.core:1.8.3]
{quote}
 
  
 Removing the property placeholder fixes the issue:
  
{code:java}

  
  

{code}
 
According to Guillaume Nodet, this seems to have been introduced by this pull 
request:

[https://github.com/apache/camel/commit/a4e94f036d02943814c84195d73837cf607c8c20]

Solution proposed by Guillaume Nodet is to change line 106 of 
/camel-blueprint/src/main/java/org/apache/camel/blueprint/handler/CamelNamespaceHandler.java

to
{code:java}
 if (camelContext.getComponent(component, false) == null) {
{code}
I tested this change locally and it seems to work, however I don't know if this 
can cause other problems.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CAMEL-12291) Blueprint error: "name is already instanciated as null and cannot be removed"

2018-02-23 Thread Andrea Cosentino (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-12291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16374930#comment-16374930
 ] 

Andrea Cosentino commented on CAMEL-12291:
--

The fix will be in 2.20.3

> Blueprint error: "name is already instanciated as null and cannot be removed"
> -
>
> Key: CAMEL-12291
> URL: https://issues.apache.org/jira/browse/CAMEL-12291
> Project: Camel
>  Issue Type: Bug
>  Components: camel-blueprint
>Affects Versions: 2.20.2
> Environment: Mac OSX, {color:#00}Karaf 4.2.5{color}
>Reporter: Alex Soto
>Assignee: Grzegorz Grzybek
>Priority: Major
>
> The error "name is already instanciated (sic) as null and cannot be removed" 
> is thrown when configuring a component in Blueprint using property 
> placeholders.
>  I noticed when trying to migrate my project to Camel 2.20.2 (from 2.17.4) 
>  Example:
> {code:java}
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
> xmlns:camel="http://camel.apache.org/schema/blueprint;
> xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;
> xsi:schemaLocation="
>               http://www.osgi.org/xmlns/blueprint/v1.0.0 
>      https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd”>
>  
> persistent-id="audit.log"
>update-strategy="reload” 
>placeholder-prefix="#{" placeholder-suffix="}">
>
>   
>   
>
> 
>  class="org.apache.camel.component.quartz2.QuartzComponent">
> 
> {code}
>   
>  The bean is referenced in a Camel route:
> {code:java}
> 
>      
> {code}
> Throws exception:
> {quote}org.osgi.service.blueprint.container.ComponentDefinitionException: 
> Name audit-log-reaper-quartz is already +instanciated+ as null and cannot be 
> removed.
>  at 
> org.apache.aries.blueprint.container.BlueprintRepository.removeRecipe(BlueprintRepository.java:131)
>  [38:org.apache.aries.blueprint.core:1.8.3]
>  at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.updateUninstantiatedRecipes(BlueprintContainerImpl.java:572)
>  [38:org.apache.aries.blueprint.core:1.8.3]
>  at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.processProcessors(BlueprintContainerImpl.java:559)
>  [38:org.apache.aries.blueprint.core:1.8.3]
>  at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:394)
>  [38:org.apache.aries.blueprint.core:1.8.3]
>  at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:275)
>  [38:org.apache.aries.blueprint.core:1.8.3]
> {quote}
>  
>   
>  Removing the property placeholder fixes the issue:
>   
> {code:java}
>    class="org.apache.camel.component.quartz2.QuartzComponent">
>   
>   
> 
> {code}
>  
> According to Guillaume Nodet, this seems to have been introduced by this pull 
> request:
> [https://github.com/apache/camel/commit/a4e94f036d02943814c84195d73837cf607c8c20]
> Solution proposed by Guillaume Nodet is to change line 106 of 
> /camel-blueprint/src/main/java/org/apache/camel/blueprint/handler/CamelNamespaceHandler.java
> to
> {code:java}
>  if (camelContext.getComponent(component, false) == null) {
> {code}
> I tested this change locally and it seems to work, however I don't know if 
> this can cause other problems.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (CAMEL-12291) Blueprint error: "name is already instanciated as null and cannot be removed"

2018-02-23 Thread Andrea Cosentino (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-12291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino resolved CAMEL-12291.
--
Resolution: Duplicate

> Blueprint error: "name is already instanciated as null and cannot be removed"
> -
>
> Key: CAMEL-12291
> URL: https://issues.apache.org/jira/browse/CAMEL-12291
> Project: Camel
>  Issue Type: Bug
>  Components: camel-blueprint
>Affects Versions: 2.20.2
> Environment: Mac OSX, {color:#00}Karaf 4.2.5{color}
>Reporter: Alex Soto
>Assignee: Grzegorz Grzybek
>Priority: Major
>
> The error "name is already instanciated (sic) as null and cannot be removed" 
> is thrown when configuring a component in Blueprint using property 
> placeholders.
>  I noticed when trying to migrate my project to Camel 2.20.2 (from 2.17.4) 
>  Example:
> {code:java}
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
> xmlns:camel="http://camel.apache.org/schema/blueprint;
> xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;
> xsi:schemaLocation="
>               http://www.osgi.org/xmlns/blueprint/v1.0.0 
>      https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd”>
>  
> persistent-id="audit.log"
>update-strategy="reload” 
>placeholder-prefix="#{" placeholder-suffix="}">
>
>   
>   
>
> 
>  class="org.apache.camel.component.quartz2.QuartzComponent">
> 
> {code}
>   
>  The bean is referenced in a Camel route:
> {code:java}
> 
>      
> {code}
> Throws exception:
> {quote}org.osgi.service.blueprint.container.ComponentDefinitionException: 
> Name audit-log-reaper-quartz is already +instanciated+ as null and cannot be 
> removed.
>  at 
> org.apache.aries.blueprint.container.BlueprintRepository.removeRecipe(BlueprintRepository.java:131)
>  [38:org.apache.aries.blueprint.core:1.8.3]
>  at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.updateUninstantiatedRecipes(BlueprintContainerImpl.java:572)
>  [38:org.apache.aries.blueprint.core:1.8.3]
>  at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.processProcessors(BlueprintContainerImpl.java:559)
>  [38:org.apache.aries.blueprint.core:1.8.3]
>  at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:394)
>  [38:org.apache.aries.blueprint.core:1.8.3]
>  at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:275)
>  [38:org.apache.aries.blueprint.core:1.8.3]
> {quote}
>  
>   
>  Removing the property placeholder fixes the issue:
>   
> {code:java}
>    class="org.apache.camel.component.quartz2.QuartzComponent">
>   
>   
> 
> {code}
>  
> According to Guillaume Nodet, this seems to have been introduced by this pull 
> request:
> [https://github.com/apache/camel/commit/a4e94f036d02943814c84195d73837cf607c8c20]
> Solution proposed by Guillaume Nodet is to change line 106 of 
> /camel-blueprint/src/main/java/org/apache/camel/blueprint/handler/CamelNamespaceHandler.java
> to
> {code:java}
>  if (camelContext.getComponent(component, false) == null) {
> {code}
> I tested this change locally and it seems to work, however I don't know if 
> this can cause other problems.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Reopened] (CAMEL-12291) Blueprint error: "name is already instanciated as null and cannot be removed"

2018-02-23 Thread Andrea Cosentino (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-12291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino reopened CAMEL-12291:
--

> Blueprint error: "name is already instanciated as null and cannot be removed"
> -
>
> Key: CAMEL-12291
> URL: https://issues.apache.org/jira/browse/CAMEL-12291
> Project: Camel
>  Issue Type: Bug
>  Components: camel-blueprint
>Affects Versions: 2.20.2
> Environment: Mac OSX, {color:#00}Karaf 4.2.5{color}
>Reporter: Alex Soto
>Assignee: Grzegorz Grzybek
>Priority: Major
>
> The error "name is already instanciated (sic) as null and cannot be removed" 
> is thrown when configuring a component in Blueprint using property 
> placeholders.
>  I noticed when trying to migrate my project to Camel 2.20.2 (from 2.17.4) 
>  Example:
> {code:java}
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
> xmlns:camel="http://camel.apache.org/schema/blueprint;
> xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;
> xsi:schemaLocation="
>               http://www.osgi.org/xmlns/blueprint/v1.0.0 
>      https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd”>
>  
> persistent-id="audit.log"
>update-strategy="reload” 
>placeholder-prefix="#{" placeholder-suffix="}">
>
>   
>   
>
> 
>  class="org.apache.camel.component.quartz2.QuartzComponent">
> 
> {code}
>   
>  The bean is referenced in a Camel route:
> {code:java}
> 
>      
> {code}
> Throws exception:
> {quote}org.osgi.service.blueprint.container.ComponentDefinitionException: 
> Name audit-log-reaper-quartz is already +instanciated+ as null and cannot be 
> removed.
>  at 
> org.apache.aries.blueprint.container.BlueprintRepository.removeRecipe(BlueprintRepository.java:131)
>  [38:org.apache.aries.blueprint.core:1.8.3]
>  at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.updateUninstantiatedRecipes(BlueprintContainerImpl.java:572)
>  [38:org.apache.aries.blueprint.core:1.8.3]
>  at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.processProcessors(BlueprintContainerImpl.java:559)
>  [38:org.apache.aries.blueprint.core:1.8.3]
>  at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:394)
>  [38:org.apache.aries.blueprint.core:1.8.3]
>  at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:275)
>  [38:org.apache.aries.blueprint.core:1.8.3]
> {quote}
>  
>   
>  Removing the property placeholder fixes the issue:
>   
> {code:java}
>    class="org.apache.camel.component.quartz2.QuartzComponent">
>   
>   
> 
> {code}
>  
> According to Guillaume Nodet, this seems to have been introduced by this pull 
> request:
> [https://github.com/apache/camel/commit/a4e94f036d02943814c84195d73837cf607c8c20]
> Solution proposed by Guillaume Nodet is to change line 106 of 
> /camel-blueprint/src/main/java/org/apache/camel/blueprint/handler/CamelNamespaceHandler.java
> to
> {code:java}
>  if (camelContext.getComponent(component, false) == null) {
> {code}
> I tested this change locally and it seems to work, however I don't know if 
> this can cause other problems.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (CAMEL-12291) Blueprint error: "name is already instanciated as null and cannot be removed"

2018-02-23 Thread Alex Soto (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-12291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Soto updated CAMEL-12291:
--
Description: 
The error "name is already instanciated (sic) as null and cannot be removed" is 
thrown when configuring a component in Blueprint using property placeholders.

I noticed when trying to migrate my project to Camel 2.20.2 (from 2.17.4) 
 Example:
{code:java}

 


   
  
  
   


 


{code}
  
 The bean is referenced in a Camel route:
{code:java}

     
{code}
Throws exception:
{quote}org.osgi.service.blueprint.container.ComponentDefinitionException: Name 
audit-log-reaper-quartz is already +instanciated+ as null and cannot be removed.
 at 
org.apache.aries.blueprint.container.BlueprintRepository.removeRecipe(BlueprintRepository.java:131)
 [38:org.apache.aries.blueprint.core:1.8.3]
 at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.updateUninstantiatedRecipes(BlueprintContainerImpl.java:572)
 [38:org.apache.aries.blueprint.core:1.8.3]
 at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.processProcessors(BlueprintContainerImpl.java:559)
 [38:org.apache.aries.blueprint.core:1.8.3]
 at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:394)
 [38:org.apache.aries.blueprint.core:1.8.3]
 at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:275)
 [38:org.apache.aries.blueprint.core:1.8.3]
{quote}
 
  
 Removing the property placeholder fixes the issue:
  
{code:java}

  
  

{code}
 
 According to Guillaume Nodet, this seems to have been introduced by this pull 
request:

[https://github.com/apache/camel/commit/a4e94f036d02943814c84195d73837cf607c8c20]

Solution proposed by Guillaume Nodet is to change line 1056 of 
/camel-blueprint/src/main/java/org/apache/camel/blueprint/handler/CamelNamespaceHandler.java

to
{code:java}
 if (camelContext.getComponent(component, false) == null) {
{code}
I tested this change locally and it seems to work, however I don't know if this 
can cause other problems.

  was:
The error "name is already instanciated (sic) as null and cannot be removed" is 
thrown when configuring a component in Blueprint using property placeholders.


 I noticed when trying to migrate my project to Camel 2.20.2 (from 2.17.4) 
 Example:
{code:java}

 


   
  
  
   


 


{code}
  
 The bean is referenced in a Camel route:
{code:java}

     
{code}
Throws exception:
{quote}org.osgi.service.blueprint.container.ComponentDefinitionException: Name 
audit-log-reaper-quartz is already +instanciated+ as null and cannot be removed.
 at 
org.apache.aries.blueprint.container.BlueprintRepository.removeRecipe(BlueprintRepository.java:131)
 [38:org.apache.aries.blueprint.core:1.8.3]
 at

[jira] [Comment Edited] (CAMEL-12291) Blueprint error: "name is already instanciated as null and cannot be removed"

2018-02-23 Thread Andrea Cosentino (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-12291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16374930#comment-16374930
 ] 

Andrea Cosentino edited comment on CAMEL-12291 at 2/23/18 8:34 PM:
---

The fix for 12251will be in 2.20.3, but it doesn't help 


was (Author: ancosen):
The fix will be in 2.20.3

> Blueprint error: "name is already instanciated as null and cannot be removed"
> -
>
> Key: CAMEL-12291
> URL: https://issues.apache.org/jira/browse/CAMEL-12291
> Project: Camel
>  Issue Type: Bug
>  Components: camel-blueprint
>Affects Versions: 2.20.2
> Environment: Mac OSX, {color:#00}Karaf 4.2.5{color}
>Reporter: Alex Soto
>Assignee: Grzegorz Grzybek
>Priority: Major
>
> The error "name is already instanciated (sic) as null and cannot be removed" 
> is thrown when configuring a component in Blueprint using property 
> placeholders.
> I noticed when trying to migrate my project to Camel 2.20.2 (from 2.17.4) 
>  Example:
> {code:java}
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
> xmlns:camel="http://camel.apache.org/schema/blueprint;
> xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;
> xsi:schemaLocation="
>               http://www.osgi.org/xmlns/blueprint/v1.0.0 
>      https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd”>
>  
> persistent-id="audit.log"
>update-strategy="reload” 
>placeholder-prefix="#{" placeholder-suffix="}">
>
>   
>   
>
> 
>  class="org.apache.camel.component.quartz2.QuartzComponent">
> 
> {code}
>   
>  The bean is referenced in a Camel route:
> {code:java}
> 
>      
> {code}
> Throws exception:
> {quote}org.osgi.service.blueprint.container.ComponentDefinitionException: 
> Name audit-log-reaper-quartz is already +instanciated+ as null and cannot be 
> removed.
>  at 
> org.apache.aries.blueprint.container.BlueprintRepository.removeRecipe(BlueprintRepository.java:131)
>  [38:org.apache.aries.blueprint.core:1.8.3]
>  at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.updateUninstantiatedRecipes(BlueprintContainerImpl.java:572)
>  [38:org.apache.aries.blueprint.core:1.8.3]
>  at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.processProcessors(BlueprintContainerImpl.java:559)
>  [38:org.apache.aries.blueprint.core:1.8.3]
>  at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:394)
>  [38:org.apache.aries.blueprint.core:1.8.3]
>  at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:275)
>  [38:org.apache.aries.blueprint.core:1.8.3]
> {quote}
>  
>   
>  Removing the property placeholder fixes the issue:
>   
> {code:java}
>    class="org.apache.camel.component.quartz2.QuartzComponent">
>   
>   
> 
> {code}
>  
>  According to Guillaume Nodet, this seems to have been introduced by this 
> pull request:
> [https://github.com/apache/camel/commit/a4e94f036d02943814c84195d73837cf607c8c20]
> Solution proposed by Guillaume Nodet is to change line 1056 of 
> /camel-blueprint/src/main/java/org/apache/camel/blueprint/handler/CamelNamespaceHandler.java
> to
> {code:java}
>  if (camelContext.getComponent(component, false) == null) {
> {code}
> I tested this change locally and it seems to work, however I don't know if 
> this can cause other problems.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CAMEL-12286) Milo client broken

2018-02-23 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-12286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16374372#comment-16374372
 ] 

ASF GitHub Bot commented on CAMEL-12286:


GitHub user ctron opened a pull request:

https://github.com/apache/camel/pull/2233

CAMEL-12286: Fix camel-milo client component

This change adapts the client to the changed behavior of
Eclipse Milo 0.2.x. It does an explicit call to connect and also allows
to configure the allowed security policies in order to still support
anonymous access when no keys are used.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ctron/camel feature/fix_issue_12286_1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/camel/pull/2233.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2233


commit e92e8e73b4997026a5c28859569e767da8dcdb15
Author: Jens Reimann 
Date:   2018-02-22T11:55:38Z

CAMEL-12286: Fix camel-milo client component

This change adapts the client to the changed behavior of
Eclipse Milo 0.2.x. It does an explicit call to connect and also allows
to configure the allowed security policies in order to still support
anonymous access when no keys are used.




> Milo client broken
> --
>
> Key: CAMEL-12286
> URL: https://issues.apache.org/jira/browse/CAMEL-12286
> Project: Camel
>  Issue Type: Bug
>  Components: camel-milo
>Affects Versions: 2.21.0
>Reporter: Jens Reimann
>Assignee: Jens Reimann
>Priority: Major
>
> It looks to me as if the camel-milo client is broken in the most recent 
> version of camel (2.21.x). Running a working example from camel 2.20.x (and 
> 2.19.x) with Camel 2.21-SNAPSHOT results in:
> {code:java}
> 2018-02-22 11:56:45.248  INFO 30400 --- [   main] 
> o.e.milo.opcua.sdk.client.OpcUaClient    : Eclipse Milo OPC UA Stack version: 
> 0.2.1
> 2018-02-22 11:56:45.248  INFO 30400 --- [   main] 
> o.e.milo.opcua.sdk.client.OpcUaClient    : Eclipse Milo OPC UA Client SDK 
> version: 0.2.1
> 2018-02-22 11:56:45.407  INFO 30400 --- [   main] 
> o.a.c.c.m.c.i.SubscriptionManager    : Failed to connect
> java.util.concurrent.ExecutionException: UaException: 
> status=Bad_SessionClosed, message=The session was closed by the client.
>     at 
> java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357) 
> ~[na:1.8.0_161]
>     at 
> java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895) 
> ~[na:1.8.0_161]
>     at 
> org.apache.camel.component.milo.client.internal.SubscriptionManager.performConnect(SubscriptionManager.java:450)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.internal.SubscriptionManager.performAndEvalConnect(SubscriptionManager.java:375)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.internal.SubscriptionManager.connect(SubscriptionManager.java:370)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.internal.SubscriptionManager.(SubscriptionManager.java:340)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.MiloClientConnection.init(MiloClientConnection.java:52)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.MiloClientConnection.checkInit(MiloClientConnection.java:69)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.MiloClientConnection.monitorValue(MiloClientConnection.java:86)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.MiloClientConsumer.doStart(MiloClientConsumer.java:57)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) 
> [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.startService(DefaultCamelContext.java:3701)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRouteConsumers(DefaultCamelContext.java:4019)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStartRouteConsumers(DefaultCamelContext.java:3954)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.safelyStartRouteServices(DefaultCamelContext.java:3874)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRoutes(DefaultCamelContext.java:3638)
>

[jira] [Commented] (CAMEL-12286) Milo client broken

2018-02-23 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-12286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16374371#comment-16374371
 ] 

ASF GitHub Bot commented on CAMEL-12286:


ctron opened a new pull request #2233: CAMEL-12286: Fix camel-milo client 
component
URL: https://github.com/apache/camel/pull/2233
 
 
   This change adapts the client to the changed behavior of
   Eclipse Milo 0.2.x. It does an explicit call to connect and also allows
   to configure the allowed security policies in order to still support
   anonymous access when no keys are used.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Milo client broken
> --
>
> Key: CAMEL-12286
> URL: https://issues.apache.org/jira/browse/CAMEL-12286
> Project: Camel
>  Issue Type: Bug
>  Components: camel-milo
>Affects Versions: 2.21.0
>Reporter: Jens Reimann
>Assignee: Jens Reimann
>Priority: Major
>
> It looks to me as if the camel-milo client is broken in the most recent 
> version of camel (2.21.x). Running a working example from camel 2.20.x (and 
> 2.19.x) with Camel 2.21-SNAPSHOT results in:
> {code:java}
> 2018-02-22 11:56:45.248  INFO 30400 --- [   main] 
> o.e.milo.opcua.sdk.client.OpcUaClient    : Eclipse Milo OPC UA Stack version: 
> 0.2.1
> 2018-02-22 11:56:45.248  INFO 30400 --- [   main] 
> o.e.milo.opcua.sdk.client.OpcUaClient    : Eclipse Milo OPC UA Client SDK 
> version: 0.2.1
> 2018-02-22 11:56:45.407  INFO 30400 --- [   main] 
> o.a.c.c.m.c.i.SubscriptionManager    : Failed to connect
> java.util.concurrent.ExecutionException: UaException: 
> status=Bad_SessionClosed, message=The session was closed by the client.
>     at 
> java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357) 
> ~[na:1.8.0_161]
>     at 
> java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895) 
> ~[na:1.8.0_161]
>     at 
> org.apache.camel.component.milo.client.internal.SubscriptionManager.performConnect(SubscriptionManager.java:450)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.internal.SubscriptionManager.performAndEvalConnect(SubscriptionManager.java:375)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.internal.SubscriptionManager.connect(SubscriptionManager.java:370)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.internal.SubscriptionManager.(SubscriptionManager.java:340)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.MiloClientConnection.init(MiloClientConnection.java:52)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.MiloClientConnection.checkInit(MiloClientConnection.java:69)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.MiloClientConnection.monitorValue(MiloClientConnection.java:86)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.MiloClientConsumer.doStart(MiloClientConsumer.java:57)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) 
> [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.startService(DefaultCamelContext.java:3701)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRouteConsumers(DefaultCamelContext.java:4019)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStartRouteConsumers(DefaultCamelContext.java:3954)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.safelyStartRouteServices(DefaultCamelContext.java:3874)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRoutes(DefaultCamelContext.java:3638)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:3490)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.access$000(DefaultCamelContext.java:208)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3249)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3245)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
>

[jira] [Created] (CAMEL-12287) Allow overriding the server reported endpoint

2018-02-23 Thread Jens Reimann (JIRA)

Jens Reimann created CAMEL-12287:


 Summary: Allow overriding the server reported endpoint
 Key: CAMEL-12287
 URL: https://issues.apache.org/jira/browse/CAMEL-12287
 Project: Camel
  Issue Type: Bug
  Components: camel-milo
Affects Versions: 2.20.2, 2.19.0
Reporter: Jens Reimann
 Fix For: 2.21.0


When the client connects to the server it asks the server first for available 
endpoints. The server should report back with a set of endpoints, which again 
contain the hostname to connect to.

If the server reports back with a hostname which the client cannot look up, it 
is currently not possible to connect to the server with camel-milo.

I did prepare a PR which adds a boolean flag to the endpoint, allowing to 
override the host of reported endpoint with the one originally provided. This 
is disabled by default, but can be enabled when necessary.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CAMEL-12286) Milo client broken

2018-02-23 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-12286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16374384#comment-16374384
 ] 

ASF GitHub Bot commented on CAMEL-12286:


oscerd commented on issue #2233: CAMEL-12286: Fix camel-milo client component
URL: https://github.com/apache/camel/pull/2233#issuecomment-368017694
 
 
   This time I was faster than @davsclaus 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Milo client broken
> --
>
> Key: CAMEL-12286
> URL: https://issues.apache.org/jira/browse/CAMEL-12286
> Project: Camel
>  Issue Type: Bug
>  Components: camel-milo
>Affects Versions: 2.21.0
>Reporter: Jens Reimann
>Assignee: Jens Reimann
>Priority: Major
>
> It looks to me as if the camel-milo client is broken in the most recent 
> version of camel (2.21.x). Running a working example from camel 2.20.x (and 
> 2.19.x) with Camel 2.21-SNAPSHOT results in:
> {code:java}
> 2018-02-22 11:56:45.248  INFO 30400 --- [   main] 
> o.e.milo.opcua.sdk.client.OpcUaClient    : Eclipse Milo OPC UA Stack version: 
> 0.2.1
> 2018-02-22 11:56:45.248  INFO 30400 --- [   main] 
> o.e.milo.opcua.sdk.client.OpcUaClient    : Eclipse Milo OPC UA Client SDK 
> version: 0.2.1
> 2018-02-22 11:56:45.407  INFO 30400 --- [   main] 
> o.a.c.c.m.c.i.SubscriptionManager    : Failed to connect
> java.util.concurrent.ExecutionException: UaException: 
> status=Bad_SessionClosed, message=The session was closed by the client.
>     at 
> java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357) 
> ~[na:1.8.0_161]
>     at 
> java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895) 
> ~[na:1.8.0_161]
>     at 
> org.apache.camel.component.milo.client.internal.SubscriptionManager.performConnect(SubscriptionManager.java:450)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.internal.SubscriptionManager.performAndEvalConnect(SubscriptionManager.java:375)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.internal.SubscriptionManager.connect(SubscriptionManager.java:370)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.internal.SubscriptionManager.(SubscriptionManager.java:340)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.MiloClientConnection.init(MiloClientConnection.java:52)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.MiloClientConnection.checkInit(MiloClientConnection.java:69)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.MiloClientConnection.monitorValue(MiloClientConnection.java:86)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.MiloClientConsumer.doStart(MiloClientConsumer.java:57)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) 
> [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.startService(DefaultCamelContext.java:3701)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRouteConsumers(DefaultCamelContext.java:4019)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStartRouteConsumers(DefaultCamelContext.java:3954)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.safelyStartRouteServices(DefaultCamelContext.java:3874)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRoutes(DefaultCamelContext.java:3638)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:3490)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.access$000(DefaultCamelContext.java:208)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3249)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3245)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doWithDefinedClassLoader(DefaultCamelContext.java:3268)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
>

[jira] [Commented] (CAMEL-12286) Milo client broken

2018-02-23 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-12286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16374379#comment-16374379
 ] 

ASF GitHub Bot commented on CAMEL-12286:


oscerd closed pull request #2233: CAMEL-12286: Fix camel-milo client component
URL: https://github.com/apache/camel/pull/2233
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/components/camel-milo/src/main/docs/milo-client-component.adoc 
b/components/camel-milo/src/main/docs/milo-client-component.adoc
index a911e3f306f..eb3e2b5db37 100644
--- a/components/camel-milo/src/main/docs/milo-client-component.adoc
+++ b/components/camel-milo/src/main/docs/milo-client-component.adoc
@@ -95,7 +95,7 @@ with the following path and query parameters:
 | *endpointUri* | *Required* The OPC UA server endpoint |  | String
 |===
 
- Query Parameters (22 parameters):
+ Query Parameters (23 parameters):
 
 [width="100%",cols="2,5,^1,2",options="header"]
 |===
@@ -108,6 +108,7 @@ with the following path and query parameters:
 | *exceptionHandler* (consumer) | To let the consumer use a custom 
ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this 
options is not in use. By default the consumer will deal with exceptions, that 
will be logged at WARN or ERROR level and ignored. |  | ExceptionHandler
 | *exchangePattern* (consumer) | Sets the exchange pattern when the consumer 
creates an exchange. |  | ExchangePattern
 | *synchronous* (advanced) | Sets whether synchronous processing should be 
strictly used, or Camel is allowed to use asynchronous processing (if 
supported). | false | boolean
+| *allowedSecurityPolicies* (client) | A set of allowed security policy URIs. 
Default is to accept all and use the highest. |  | String
 | *applicationName* (client) | The application name | Apache Camel adapter for 
Eclipse Milo | String
 | *applicationUri* (client) | The application URI | 
http://camel.apache.org/EclipseMilo/Client | String
 | *channelLifetime* (client) | Channel lifetime in milliseconds |  | Long
@@ -161,6 +162,15 @@ However Camel allows to wrap the actual value inside 
`RAW(…)`, which makes esc
 
milo-client://user:password@localhost:12345?node=RAW(nsu=http://foo.bar;s=foo/bar)
 
 
+ Security policies
+
+When setting the allowing security policies is it possible to use the well 
known OPC UA URIs (e.g. 
`http://opcfoundation.org/UA/SecurityPolicy#Basic128Rsa15`)
+or to use the Milo enum literals (e.g. `None`). Specifying an unknown security 
policy URI or enum is an error.
+
+The known security policy URIs and enum literals are can be seen here: 
https://github.com/eclipse/milo/blob/master/opc-ua-stack/stack-core/src/main/java/org/eclipse/milo/opcua/stack/core/security/SecurityPolicy.java[SecurityPolicy.java]
 
+
+**Note:** In any case security policies are considered case sensitive.
+
 === See Also
 
 * Configuring Camel
diff --git 
a/components/camel-milo/src/main/java/org/apache/camel/component/milo/client/MiloClientConfiguration.java
 
b/components/camel-milo/src/main/java/org/apache/camel/component/milo/client/MiloClientConfiguration.java
index 8f1e1847961..1a78648a93c 100644
--- 
a/components/camel-milo/src/main/java/org/apache/camel/component/milo/client/MiloClientConfiguration.java
+++ 
b/components/camel-milo/src/main/java/org/apache/camel/component/milo/client/MiloClientConfiguration.java
@@ -18,10 +18,13 @@
 
 import java.net.MalformedURLException;
 import java.net.URL;
+import java.util.HashSet;
+import java.util.Set;
 
 import org.apache.camel.component.milo.KeyStoreLoader;
 import org.apache.camel.spi.UriParam;
 import org.apache.camel.spi.UriParams;
+import org.eclipse.milo.opcua.stack.core.security.SecurityPolicy;
 
 @UriParams
 public class MiloClientConfiguration implements Cloneable {
@@ -79,6 +82,9 @@
 @UriParam(label = "client", secret = true)
 private String keyPassword;
 
+@UriParam(label = "client", javaType = "java.lang.String")
+private Set allowedSecurityPolicies = new HashSet<>();
+
 public MiloClientConfiguration() {
 }
 
@@ -88,6 +94,7 @@ public MiloClientConfiguration(final MiloClientConfiguration 
other) {
 this.applicationName = other.applicationName;
 this.productUri = other.productUri;
 this.requestTimeout = other.requestTimeout;
+this.allowedSecurityPolicies = allowedSecurityPolicies != null ? new 
HashSet<>(other.allowedSecurityPolicies) : null;
 }
 
 public void setEndpointUri(final String endpointUri) {
@@ -263,6 +270,55 @@ public String getKeyPassword() {
 return this.keyPassword;
 }
 
+/**
+ * A set of allowed security policy URIs. Default is to accept all and

[jira] [Commented] (CAMEL-12286) Milo client broken

2018-02-23 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-12286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16374385#comment-16374385
 ] 

ASF GitHub Bot commented on CAMEL-12286:


oscerd commented on issue #2233: CAMEL-12286: Fix camel-milo client component
URL: https://github.com/apache/camel/pull/2233#issuecomment-368017714
 
 
   Thanks!


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Milo client broken
> --
>
> Key: CAMEL-12286
> URL: https://issues.apache.org/jira/browse/CAMEL-12286
> Project: Camel
>  Issue Type: Bug
>  Components: camel-milo
>Affects Versions: 2.21.0
>Reporter: Jens Reimann
>Assignee: Jens Reimann
>Priority: Major
>
> It looks to me as if the camel-milo client is broken in the most recent 
> version of camel (2.21.x). Running a working example from camel 2.20.x (and 
> 2.19.x) with Camel 2.21-SNAPSHOT results in:
> {code:java}
> 2018-02-22 11:56:45.248  INFO 30400 --- [   main] 
> o.e.milo.opcua.sdk.client.OpcUaClient    : Eclipse Milo OPC UA Stack version: 
> 0.2.1
> 2018-02-22 11:56:45.248  INFO 30400 --- [   main] 
> o.e.milo.opcua.sdk.client.OpcUaClient    : Eclipse Milo OPC UA Client SDK 
> version: 0.2.1
> 2018-02-22 11:56:45.407  INFO 30400 --- [   main] 
> o.a.c.c.m.c.i.SubscriptionManager    : Failed to connect
> java.util.concurrent.ExecutionException: UaException: 
> status=Bad_SessionClosed, message=The session was closed by the client.
>     at 
> java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357) 
> ~[na:1.8.0_161]
>     at 
> java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895) 
> ~[na:1.8.0_161]
>     at 
> org.apache.camel.component.milo.client.internal.SubscriptionManager.performConnect(SubscriptionManager.java:450)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.internal.SubscriptionManager.performAndEvalConnect(SubscriptionManager.java:375)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.internal.SubscriptionManager.connect(SubscriptionManager.java:370)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.internal.SubscriptionManager.(SubscriptionManager.java:340)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.MiloClientConnection.init(MiloClientConnection.java:52)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.MiloClientConnection.checkInit(MiloClientConnection.java:69)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.MiloClientConnection.monitorValue(MiloClientConnection.java:86)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.MiloClientConsumer.doStart(MiloClientConsumer.java:57)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) 
> [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.startService(DefaultCamelContext.java:3701)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRouteConsumers(DefaultCamelContext.java:4019)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStartRouteConsumers(DefaultCamelContext.java:3954)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.safelyStartRouteServices(DefaultCamelContext.java:3874)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRoutes(DefaultCamelContext.java:3638)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:3490)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.access$000(DefaultCamelContext.java:208)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3249)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3245)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doWithDefinedClassLoader(DefaultCamelContext.java:3268)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:3245)
>

[jira] [Commented] (CAMEL-12286) Milo client broken

2018-02-23 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-12286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16374380#comment-16374380
 ] 

ASF GitHub Bot commented on CAMEL-12286:


Github user oscerd closed the pull request at:

https://github.com/apache/camel/pull/2233


> Milo client broken
> --
>
> Key: CAMEL-12286
> URL: https://issues.apache.org/jira/browse/CAMEL-12286
> Project: Camel
>  Issue Type: Bug
>  Components: camel-milo
>Affects Versions: 2.21.0
>Reporter: Jens Reimann
>Assignee: Jens Reimann
>Priority: Major
>
> It looks to me as if the camel-milo client is broken in the most recent 
> version of camel (2.21.x). Running a working example from camel 2.20.x (and 
> 2.19.x) with Camel 2.21-SNAPSHOT results in:
> {code:java}
> 2018-02-22 11:56:45.248  INFO 30400 --- [   main] 
> o.e.milo.opcua.sdk.client.OpcUaClient    : Eclipse Milo OPC UA Stack version: 
> 0.2.1
> 2018-02-22 11:56:45.248  INFO 30400 --- [   main] 
> o.e.milo.opcua.sdk.client.OpcUaClient    : Eclipse Milo OPC UA Client SDK 
> version: 0.2.1
> 2018-02-22 11:56:45.407  INFO 30400 --- [   main] 
> o.a.c.c.m.c.i.SubscriptionManager    : Failed to connect
> java.util.concurrent.ExecutionException: UaException: 
> status=Bad_SessionClosed, message=The session was closed by the client.
>     at 
> java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357) 
> ~[na:1.8.0_161]
>     at 
> java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895) 
> ~[na:1.8.0_161]
>     at 
> org.apache.camel.component.milo.client.internal.SubscriptionManager.performConnect(SubscriptionManager.java:450)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.internal.SubscriptionManager.performAndEvalConnect(SubscriptionManager.java:375)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.internal.SubscriptionManager.connect(SubscriptionManager.java:370)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.internal.SubscriptionManager.(SubscriptionManager.java:340)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.MiloClientConnection.init(MiloClientConnection.java:52)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.MiloClientConnection.checkInit(MiloClientConnection.java:69)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.MiloClientConnection.monitorValue(MiloClientConnection.java:86)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.MiloClientConsumer.doStart(MiloClientConsumer.java:57)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) 
> [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.startService(DefaultCamelContext.java:3701)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRouteConsumers(DefaultCamelContext.java:4019)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStartRouteConsumers(DefaultCamelContext.java:3954)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.safelyStartRouteServices(DefaultCamelContext.java:3874)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRoutes(DefaultCamelContext.java:3638)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:3490)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.access$000(DefaultCamelContext.java:208)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3249)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3245)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doWithDefinedClassLoader(DefaultCamelContext.java:3268)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:3245)
>  [camel-core-2.20.2.jar:2.20.2]
>     at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) 
> [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:3168)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.spring.SpringCamelContext.start(SpringCamelContext.java:133) 
>

[jira] [Updated] (CAMEL-12286) Milo client broken

2018-02-23 Thread Andrea Cosentino (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-12286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino updated CAMEL-12286:
-
Fix Version/s: 2.21.0

> Milo client broken
> --
>
> Key: CAMEL-12286
> URL: https://issues.apache.org/jira/browse/CAMEL-12286
> Project: Camel
>  Issue Type: Bug
>  Components: camel-milo
>Affects Versions: 2.21.0
>Reporter: Jens Reimann
>Assignee: Jens Reimann
>Priority: Major
> Fix For: 2.21.0
>
>
> It looks to me as if the camel-milo client is broken in the most recent 
> version of camel (2.21.x). Running a working example from camel 2.20.x (and 
> 2.19.x) with Camel 2.21-SNAPSHOT results in:
> {code:java}
> 2018-02-22 11:56:45.248  INFO 30400 --- [   main] 
> o.e.milo.opcua.sdk.client.OpcUaClient    : Eclipse Milo OPC UA Stack version: 
> 0.2.1
> 2018-02-22 11:56:45.248  INFO 30400 --- [   main] 
> o.e.milo.opcua.sdk.client.OpcUaClient    : Eclipse Milo OPC UA Client SDK 
> version: 0.2.1
> 2018-02-22 11:56:45.407  INFO 30400 --- [   main] 
> o.a.c.c.m.c.i.SubscriptionManager    : Failed to connect
> java.util.concurrent.ExecutionException: UaException: 
> status=Bad_SessionClosed, message=The session was closed by the client.
>     at 
> java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357) 
> ~[na:1.8.0_161]
>     at 
> java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895) 
> ~[na:1.8.0_161]
>     at 
> org.apache.camel.component.milo.client.internal.SubscriptionManager.performConnect(SubscriptionManager.java:450)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.internal.SubscriptionManager.performAndEvalConnect(SubscriptionManager.java:375)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.internal.SubscriptionManager.connect(SubscriptionManager.java:370)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.internal.SubscriptionManager.(SubscriptionManager.java:340)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.MiloClientConnection.init(MiloClientConnection.java:52)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.MiloClientConnection.checkInit(MiloClientConnection.java:69)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.MiloClientConnection.monitorValue(MiloClientConnection.java:86)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.MiloClientConsumer.doStart(MiloClientConsumer.java:57)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) 
> [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.startService(DefaultCamelContext.java:3701)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRouteConsumers(DefaultCamelContext.java:4019)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStartRouteConsumers(DefaultCamelContext.java:3954)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.safelyStartRouteServices(DefaultCamelContext.java:3874)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRoutes(DefaultCamelContext.java:3638)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:3490)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.access$000(DefaultCamelContext.java:208)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3249)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3245)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doWithDefinedClassLoader(DefaultCamelContext.java:3268)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:3245)
>  [camel-core-2.20.2.jar:2.20.2]
>     at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) 
> [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:3168)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.spring.SpringCamelContext.start(SpringCamelContext.java:133) 
> [camel-spring-2.20.2.jar:2.20.2]
>     at 
>

[jira] [Resolved] (CAMEL-12286) Milo client broken

2018-02-23 Thread Andrea Cosentino (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-12286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino resolved CAMEL-12286.
--
Resolution: Fixed

> Milo client broken
> --
>
> Key: CAMEL-12286
> URL: https://issues.apache.org/jira/browse/CAMEL-12286
> Project: Camel
>  Issue Type: Bug
>  Components: camel-milo
>Affects Versions: 2.21.0
>Reporter: Jens Reimann
>Assignee: Jens Reimann
>Priority: Major
> Fix For: 2.21.0
>
>
> It looks to me as if the camel-milo client is broken in the most recent 
> version of camel (2.21.x). Running a working example from camel 2.20.x (and 
> 2.19.x) with Camel 2.21-SNAPSHOT results in:
> {code:java}
> 2018-02-22 11:56:45.248  INFO 30400 --- [   main] 
> o.e.milo.opcua.sdk.client.OpcUaClient    : Eclipse Milo OPC UA Stack version: 
> 0.2.1
> 2018-02-22 11:56:45.248  INFO 30400 --- [   main] 
> o.e.milo.opcua.sdk.client.OpcUaClient    : Eclipse Milo OPC UA Client SDK 
> version: 0.2.1
> 2018-02-22 11:56:45.407  INFO 30400 --- [   main] 
> o.a.c.c.m.c.i.SubscriptionManager    : Failed to connect
> java.util.concurrent.ExecutionException: UaException: 
> status=Bad_SessionClosed, message=The session was closed by the client.
>     at 
> java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357) 
> ~[na:1.8.0_161]
>     at 
> java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895) 
> ~[na:1.8.0_161]
>     at 
> org.apache.camel.component.milo.client.internal.SubscriptionManager.performConnect(SubscriptionManager.java:450)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.internal.SubscriptionManager.performAndEvalConnect(SubscriptionManager.java:375)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.internal.SubscriptionManager.connect(SubscriptionManager.java:370)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.internal.SubscriptionManager.(SubscriptionManager.java:340)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.MiloClientConnection.init(MiloClientConnection.java:52)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.MiloClientConnection.checkInit(MiloClientConnection.java:69)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.MiloClientConnection.monitorValue(MiloClientConnection.java:86)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.MiloClientConsumer.doStart(MiloClientConsumer.java:57)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) 
> [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.startService(DefaultCamelContext.java:3701)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRouteConsumers(DefaultCamelContext.java:4019)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStartRouteConsumers(DefaultCamelContext.java:3954)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.safelyStartRouteServices(DefaultCamelContext.java:3874)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRoutes(DefaultCamelContext.java:3638)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:3490)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.access$000(DefaultCamelContext.java:208)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3249)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3245)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doWithDefinedClassLoader(DefaultCamelContext.java:3268)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:3245)
>  [camel-core-2.20.2.jar:2.20.2]
>     at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) 
> [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:3168)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.spring.SpringCamelContext.start(SpringCamelContext.java:133) 
> [camel-spring-2.20.2.jar:2.20.2]
>     at 
>

[jira] [Created] (CAMEL-12288) Need call method feature

2018-02-23 Thread Amritha Raj Herle (JIRA)

Amritha Raj Herle created CAMEL-12288:
-

 Summary: Need call method feature
 Key: CAMEL-12288
 URL: https://issues.apache.org/jira/browse/CAMEL-12288
 Project: Camel
  Issue Type: New Feature
  Components: camel-milo
Affects Versions: 2.20.2
Reporter: Amritha Raj Herle
 Attachments: image.png

I'm using Apache camel Milo component for one of my project. Where I'm  having 
a use-case scenario in which i need to CALL THE METHOD (for example START, 
STOP) with some input parameter (ex:START("APPLICATIONNAME") ) which returns 
some output parameter. (StatusCode, or ErrorCode)
 
SceenShot of my sample server
!image.png!
 
I have tested the read node functionality with the node id and the namespace. 
The milo-client component will be more better suited if it provide the call 
functionality.
 
Please do look into it.
 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CAMEL-12288) Need call method feature

2018-02-23 Thread Andrea Cosentino (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-12288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16374410#comment-16374410
 ] 

Andrea Cosentino commented on CAMEL-12288:
--

Please use users mailing list first.

> Need call method feature
> 
>
> Key: CAMEL-12288
> URL: https://issues.apache.org/jira/browse/CAMEL-12288
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-milo
>Affects Versions: 2.20.2
>Reporter: Amritha Raj Herle
>Priority: Major
> Attachments: image.png
>
>
> I'm using Apache camel Milo component for one of my project. Where I'm  
> having a use-case scenario in which i need to CALL THE METHOD (for example 
> START, STOP) with some input parameter (ex:START("APPLICATIONNAME") ) which 
> returns some output parameter. (StatusCode, or ErrorCode)
>  
> SceenShot of my sample server
> !image.png!
>  
> I have tested the read node functionality with the node id and the namespace. 
> The milo-client component will be more better suited if it provide the call 
> functionality.
>  
> Please do look into it.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (CAMEL-12288) Need call method feature

2018-02-23 Thread Andrea Cosentino (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-12288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino resolved CAMEL-12288.
--
Resolution: Invalid
  Assignee: Andrea Cosentino

> Need call method feature
> 
>
> Key: CAMEL-12288
> URL: https://issues.apache.org/jira/browse/CAMEL-12288
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-milo
>Affects Versions: 2.20.2
>Reporter: Amritha Raj Herle
>Assignee: Andrea Cosentino
>Priority: Major
> Attachments: image.png
>
>
> I'm using Apache camel Milo component for one of my project. Where I'm  
> having a use-case scenario in which i need to CALL THE METHOD (for example 
> START, STOP) with some input parameter (ex:START("APPLICATIONNAME") ) which 
> returns some output parameter. (StatusCode, or ErrorCode)
>  
> SceenShot of my sample server
> !image.png!
>  
> I have tested the read node functionality with the node id and the namespace. 
> The milo-client component will be more better suited if it provide the call 
> functionality.
>  
> Please do look into it.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (CAMEL-12288) Need call method feature for milo client component

2018-02-23 Thread Amritha Raj Herle (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-12288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amritha Raj Herle updated CAMEL-12288:
--
Summary: Need call method feature for milo client component  (was: Need 
call method feature)

> Need call method feature for milo client component
> --
>
> Key: CAMEL-12288
> URL: https://issues.apache.org/jira/browse/CAMEL-12288
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-milo
>Affects Versions: 2.20.2
>Reporter: Amritha Raj Herle
>Assignee: Andrea Cosentino
>Priority: Major
> Attachments: image.png
>
>
> I'm using Apache camel Milo component for one of my project. Where I'm  
> having a use-case scenario in which i need to CALL THE METHOD (for example 
> START, STOP) with some input parameter (ex:START("APPLICATIONNAME") ) which 
> returns some output parameter. (StatusCode, or ErrorCode)
>  
> SceenShot of my sample server
> !image.png!
>  
> I have tested the read node functionality with the node id and the namespace. 
> The milo-client component will be more better suited if it provide the call 
> functionality.
>  
> Please do look into it.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (CAMEL-12288) Need method call feature for milo client component

2018-02-23 Thread Amritha Raj Herle (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-12288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amritha Raj Herle updated CAMEL-12288:
--
Summary: Need method call feature for milo client component  (was: Need 
call method feature for milo client component)

> Need method call feature for milo client component
> --
>
> Key: CAMEL-12288
> URL: https://issues.apache.org/jira/browse/CAMEL-12288
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-milo
>Affects Versions: 2.20.2
>Reporter: Amritha Raj Herle
>Assignee: Andrea Cosentino
>Priority: Major
> Attachments: image.png
>
>
> I'm using Apache camel Milo component for one of my project. Where I'm  
> having a use-case scenario in which i need to CALL THE METHOD (for example 
> START, STOP) with some input parameter (ex:START("APPLICATIONNAME") ) which 
> returns some output parameter. (StatusCode, or ErrorCode)
>  
> SceenShot of my sample server
> !image.png!
>  
> I have tested the read node functionality with the node id and the namespace. 
> The milo-client component will be more better suited if it provide the call 
> functionality.
>  
> Please do look into it.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (CAMEL-12288) Need method call feature for milo client component

2018-02-23 Thread Amritha Raj Herle (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-12288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amritha Raj Herle updated CAMEL-12288:
--
Description: 
I'm using Apache camel Milo component for one of my project. Where I'm  having 
a use-case scenario in which i need to CALL THE METHOD (for example *START*(), 
*STOP*()) with some input parameter (ex:*START("APPLICATIONNAME")* ) which 
returns some output parameter. (*StatusCode*, or *ErrorCode*). Please note that 
the input and output parameter can be complex data type (Not just int/double... 
).
  
[ SceenShot of my sample server ]
 !image.png!
  
 I have tested the read node functionality with the node id and the namespace. 
The milo-client component will be more better suited if it provide the call 
functionality.
  
 Please do look into it.
  

  was:
I'm using Apache camel Milo component for one of my project. Where I'm  having 
a use-case scenario in which i need to CALL THE METHOD (for example *START*(), 
*STOP*()) with some input parameter (ex:*START("APPLICATIONNAME")* ) which 
returns some output parameter. (*StatusCode*, or *ErrorCode*). Please note that 
the input and output paramente can be complex data type.
  
 SceenShot of my sample server
 !image.png!
  
 I have tested the read node functionality with the node id and the namespace. 
The milo-client component will be more better suited if it provide the call 
functionality.
  
 Please do look into it.
  


> Need method call feature for milo client component
> --
>
> Key: CAMEL-12288
> URL: https://issues.apache.org/jira/browse/CAMEL-12288
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-milo
>Affects Versions: 2.20.2
>Reporter: Amritha Raj Herle
>Assignee: Andrea Cosentino
>Priority: Major
> Attachments: image.png
>
>
> I'm using Apache camel Milo component for one of my project. Where I'm  
> having a use-case scenario in which i need to CALL THE METHOD (for example 
> *START*(), *STOP*()) with some input parameter (ex:*START("APPLICATIONNAME")* 
> ) which returns some output parameter. (*StatusCode*, or *ErrorCode*). Please 
> note that the input and output parameter can be complex data type (Not just 
> int/double... ).
>   
> [ SceenShot of my sample server ]
>  !image.png!
>   
>  I have tested the read node functionality with the node id and the 
> namespace. The milo-client component will be more better suited if it provide 
> the call functionality.
>   
>  Please do look into it.
>   



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CAMEL-12288) Need method call feature for milo client component

2018-02-23 Thread Andrea Cosentino (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-12288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16374413#comment-16374413
 ] 

Andrea Cosentino commented on CAMEL-12288:
--

Ok, so this is a request for a new feature.

> Need method call feature for milo client component
> --
>
> Key: CAMEL-12288
> URL: https://issues.apache.org/jira/browse/CAMEL-12288
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-milo
>Affects Versions: 2.20.2
>Reporter: Amritha Raj Herle
>Assignee: Andrea Cosentino
>Priority: Major
> Attachments: image.png
>
>
> I'm using Apache camel Milo component for one of my project. Where I'm  
> having a use-case scenario in which i need to CALL THE METHOD (for example 
> START, STOP) with some input parameter (ex:START("APPLICATIONNAME") ) which 
> returns some output parameter. (StatusCode, or ErrorCode)
>  
> SceenShot of my sample server
> !image.png!
>  
> I have tested the read node functionality with the node id and the namespace. 
> The milo-client component will be more better suited if it provide the call 
> functionality.
>  
> Please do look into it.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Reopened] (CAMEL-12288) Need method call feature for milo client component

2018-02-23 Thread Andrea Cosentino (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-12288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino reopened CAMEL-12288:
--

> Need method call feature for milo client component
> --
>
> Key: CAMEL-12288
> URL: https://issues.apache.org/jira/browse/CAMEL-12288
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-milo
>Affects Versions: 2.20.2
>Reporter: Amritha Raj Herle
>Assignee: Andrea Cosentino
>Priority: Major
> Attachments: image.png
>
>
> I'm using Apache camel Milo component for one of my project. Where I'm  
> having a use-case scenario in which i need to CALL THE METHOD (for example 
> START, STOP) with some input parameter (ex:START("APPLICATIONNAME") ) which 
> returns some output parameter. (StatusCode, or ErrorCode)
>  
> SceenShot of my sample server
> !image.png!
>  
> I have tested the read node functionality with the node id and the namespace. 
> The milo-client component will be more better suited if it provide the call 
> functionality.
>  
> Please do look into it.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Issue Comment Deleted] (CAMEL-12288) Need method call feature for milo client component

2018-02-23 Thread Andrea Cosentino (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-12288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino updated CAMEL-12288:
-
Comment: was deleted

(was: Please use users mailing list first.)

> Need method call feature for milo client component
> --
>
> Key: CAMEL-12288
> URL: https://issues.apache.org/jira/browse/CAMEL-12288
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-milo
>Affects Versions: 2.20.2
>Reporter: Amritha Raj Herle
>Assignee: Andrea Cosentino
>Priority: Major
> Attachments: image.png
>
>
> I'm using Apache camel Milo component for one of my project. Where I'm  
> having a use-case scenario in which i need to CALL THE METHOD (for example 
> START, STOP) with some input parameter (ex:START("APPLICATIONNAME") ) which 
> returns some output parameter. (StatusCode, or ErrorCode)
>  
> SceenShot of my sample server
> !image.png!
>  
> I have tested the read node functionality with the node id and the namespace. 
> The milo-client component will be more better suited if it provide the call 
> functionality.
>  
> Please do look into it.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (CAMEL-12288) Need method call feature for milo client component

2018-02-23 Thread Amritha Raj Herle (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-12288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amritha Raj Herle updated CAMEL-12288:
--
Description: 
I'm using Apache camel Milo component for one of my project. Where I'm  having 
a use-case scenario in which i need to CALL THE METHOD (for example *START*(), 
*STOP*()) with some input parameter (ex:*START("APPLICATIONNAME")* ) which 
returns some output parameter. (*StatusCode*, or *ErrorCode*). Please note that 
the input and output paramente can be complex data type.
  
 SceenShot of my sample server
 !image.png!
  
 I have tested the read node functionality with the node id and the namespace. 
The milo-client component will be more better suited if it provide the call 
functionality.
  
 Please do look into it.
  

  was:
I'm using Apache camel Milo component for one of my project. Where I'm  having 
a use-case scenario in which i need to CALL THE METHOD (for example START, 
STOP) with some input parameter (ex:START("APPLICATIONNAME") ) which returns 
some output parameter. (StatusCode, or ErrorCode)
 
SceenShot of my sample server
!image.png!
 
I have tested the read node functionality with the node id and the namespace. 
The milo-client component will be more better suited if it provide the call 
functionality.
 
Please do look into it.
 


> Need method call feature for milo client component
> --
>
> Key: CAMEL-12288
> URL: https://issues.apache.org/jira/browse/CAMEL-12288
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-milo
>Affects Versions: 2.20.2
>Reporter: Amritha Raj Herle
>Assignee: Andrea Cosentino
>Priority: Major
> Attachments: image.png
>
>
> I'm using Apache camel Milo component for one of my project. Where I'm  
> having a use-case scenario in which i need to CALL THE METHOD (for example 
> *START*(), *STOP*()) with some input parameter (ex:*START("APPLICATIONNAME")* 
> ) which returns some output parameter. (*StatusCode*, or *ErrorCode*). Please 
> note that the input and output paramente can be complex data type.
>   
>  SceenShot of my sample server
>  !image.png!
>   
>  I have tested the read node functionality with the node id and the 
> namespace. The milo-client component will be more better suited if it provide 
> the call functionality.
>   
>  Please do look into it.
>   



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (CAMEL-12288) Need method call feature for milo client component

2018-02-23 Thread Andrea Cosentino (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-12288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino updated CAMEL-12288:
-
Flags:   (was: Important)

> Need method call feature for milo client component
> --
>
> Key: CAMEL-12288
> URL: https://issues.apache.org/jira/browse/CAMEL-12288
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-milo
>Affects Versions: 2.20.2
>Reporter: Amritha Raj Herle
>Assignee: Andrea Cosentino
>Priority: Major
> Attachments: image.png
>
>
> I'm using Apache camel Milo component for one of my project. Where I'm  
> having a use-case scenario in which i need to CALL THE METHOD (for example 
> *START*(), *STOP*()) with some input parameter (ex:*START("APPLICATIONNAME")* 
> ) which returns some output parameter. (*StatusCode*, or *ErrorCode*). Please 
> note that the input and output parameter can be complex data type (Not just 
> int/double... ).
>   
> [ SceenShot of my sample server ]
>  !image.png!
>   
>  I have tested the read node functionality with the node id and the 
> namespace. The milo-client component will be more better suited if it provide 
> the call functionality.
>   
>  Please do look into it.
>   



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CAMEL-12288) Need method call feature for milo client component

2018-02-23 Thread Amritha Raj Herle (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-12288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16374418#comment-16374418
 ] 

Amritha Raj Herle commented on CAMEL-12288:
---

Actually this is should be given as basic feature. Because In IOT related 
project we always call method and get some work done.

With this feature the milo component will ease our overload of writing code. 

> Need method call feature for milo client component
> --
>
> Key: CAMEL-12288
> URL: https://issues.apache.org/jira/browse/CAMEL-12288
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-milo
>Affects Versions: 2.20.2
>Reporter: Amritha Raj Herle
>Assignee: Andrea Cosentino
>Priority: Major
> Attachments: image.png
>
>
> I'm using Apache camel Milo component for one of my project. Where I'm  
> having a use-case scenario in which i need to CALL THE METHOD (for example 
> *START*(), *STOP*()) with some input parameter (ex:*START("APPLICATIONNAME")* 
> ) which returns some output parameter. (*StatusCode*, or *ErrorCode*). Please 
> note that the input and output parameter can be complex data type (Not just 
> int/double... ).
>   
> [ SceenShot of my sample server ]
>  !image.png!
>   
>  I have tested the read node functionality with the node id and the 
> namespace. The milo-client component will be more better suited if it provide 
> the call functionality.
>   
>  Please do look into it.
>   



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CAMEL-12288) Need method call feature for milo client component

2018-02-23 Thread Andrea Cosentino (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-12288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16374422#comment-16374422
 ] 

Andrea Cosentino commented on CAMEL-12288:
--

It's not there, so it's a new feature to be implemented. [~ctron] can you give 
your feedback on this?

> Need method call feature for milo client component
> --
>
> Key: CAMEL-12288
> URL: https://issues.apache.org/jira/browse/CAMEL-12288
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-milo
>Affects Versions: 2.20.2
>Reporter: Amritha Raj Herle
>Assignee: Andrea Cosentino
>Priority: Major
> Attachments: image.png
>
>
> I'm using Apache camel Milo component for one of my project. Where I'm  
> having a use-case scenario in which i need to CALL THE METHOD (for example 
> *START*(), *STOP*()) with some input parameter (ex:*START("APPLICATIONNAME")* 
> ) which returns some output parameter. (*StatusCode*, or *ErrorCode*). Please 
> note that the input and output parameter can be complex data type (Not just 
> int/double... ).
>   
> [ SceenShot of my sample server ]
>  !image.png!
>   
>  I have tested the read node functionality with the node id and the 
> namespace. The milo-client component will be more better suited if it provide 
> the call functionality.
>   
>  Please do look into it.
>   



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CAMEL-12286) Milo client broken

2018-02-23 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-12286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16374432#comment-16374432
 ] 

ASF GitHub Bot commented on CAMEL-12286:


ctron commented on issue #2233: CAMEL-12286: Fix camel-milo client component
URL: https://github.com/apache/camel/pull/2233#issuecomment-368029151
 
 
   Thanks again for the quick merge!


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Milo client broken
> --
>
> Key: CAMEL-12286
> URL: https://issues.apache.org/jira/browse/CAMEL-12286
> Project: Camel
>  Issue Type: Bug
>  Components: camel-milo
>Affects Versions: 2.21.0
>Reporter: Jens Reimann
>Assignee: Jens Reimann
>Priority: Major
> Fix For: 2.21.0
>
>
> It looks to me as if the camel-milo client is broken in the most recent 
> version of camel (2.21.x). Running a working example from camel 2.20.x (and 
> 2.19.x) with Camel 2.21-SNAPSHOT results in:
> {code:java}
> 2018-02-22 11:56:45.248  INFO 30400 --- [   main] 
> o.e.milo.opcua.sdk.client.OpcUaClient    : Eclipse Milo OPC UA Stack version: 
> 0.2.1
> 2018-02-22 11:56:45.248  INFO 30400 --- [   main] 
> o.e.milo.opcua.sdk.client.OpcUaClient    : Eclipse Milo OPC UA Client SDK 
> version: 0.2.1
> 2018-02-22 11:56:45.407  INFO 30400 --- [   main] 
> o.a.c.c.m.c.i.SubscriptionManager    : Failed to connect
> java.util.concurrent.ExecutionException: UaException: 
> status=Bad_SessionClosed, message=The session was closed by the client.
>     at 
> java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357) 
> ~[na:1.8.0_161]
>     at 
> java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895) 
> ~[na:1.8.0_161]
>     at 
> org.apache.camel.component.milo.client.internal.SubscriptionManager.performConnect(SubscriptionManager.java:450)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.internal.SubscriptionManager.performAndEvalConnect(SubscriptionManager.java:375)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.internal.SubscriptionManager.connect(SubscriptionManager.java:370)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.internal.SubscriptionManager.(SubscriptionManager.java:340)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.MiloClientConnection.init(MiloClientConnection.java:52)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.MiloClientConnection.checkInit(MiloClientConnection.java:69)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.MiloClientConnection.monitorValue(MiloClientConnection.java:86)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.MiloClientConsumer.doStart(MiloClientConsumer.java:57)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) 
> [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.startService(DefaultCamelContext.java:3701)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRouteConsumers(DefaultCamelContext.java:4019)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStartRouteConsumers(DefaultCamelContext.java:3954)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.safelyStartRouteServices(DefaultCamelContext.java:3874)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRoutes(DefaultCamelContext.java:3638)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:3490)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.access$000(DefaultCamelContext.java:208)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3249)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3245)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doWithDefinedClassLoader(DefaultCamelContext.java:3268)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
>

[jira] [Commented] (CAMEL-12286) Milo client broken

2018-02-23 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-12286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16374434#comment-16374434
 ] 

ASF GitHub Bot commented on CAMEL-12286:


oscerd commented on issue #2233: CAMEL-12286: Fix camel-milo client component
URL: https://github.com/apache/camel/pull/2233#issuecomment-368029846
 
 
   Thanks for your help!


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Milo client broken
> --
>
> Key: CAMEL-12286
> URL: https://issues.apache.org/jira/browse/CAMEL-12286
> Project: Camel
>  Issue Type: Bug
>  Components: camel-milo
>Affects Versions: 2.21.0
>Reporter: Jens Reimann
>Assignee: Jens Reimann
>Priority: Major
> Fix For: 2.21.0
>
>
> It looks to me as if the camel-milo client is broken in the most recent 
> version of camel (2.21.x). Running a working example from camel 2.20.x (and 
> 2.19.x) with Camel 2.21-SNAPSHOT results in:
> {code:java}
> 2018-02-22 11:56:45.248  INFO 30400 --- [   main] 
> o.e.milo.opcua.sdk.client.OpcUaClient    : Eclipse Milo OPC UA Stack version: 
> 0.2.1
> 2018-02-22 11:56:45.248  INFO 30400 --- [   main] 
> o.e.milo.opcua.sdk.client.OpcUaClient    : Eclipse Milo OPC UA Client SDK 
> version: 0.2.1
> 2018-02-22 11:56:45.407  INFO 30400 --- [   main] 
> o.a.c.c.m.c.i.SubscriptionManager    : Failed to connect
> java.util.concurrent.ExecutionException: UaException: 
> status=Bad_SessionClosed, message=The session was closed by the client.
>     at 
> java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357) 
> ~[na:1.8.0_161]
>     at 
> java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895) 
> ~[na:1.8.0_161]
>     at 
> org.apache.camel.component.milo.client.internal.SubscriptionManager.performConnect(SubscriptionManager.java:450)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.internal.SubscriptionManager.performAndEvalConnect(SubscriptionManager.java:375)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.internal.SubscriptionManager.connect(SubscriptionManager.java:370)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.internal.SubscriptionManager.(SubscriptionManager.java:340)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.MiloClientConnection.init(MiloClientConnection.java:52)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.MiloClientConnection.checkInit(MiloClientConnection.java:69)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.MiloClientConnection.monitorValue(MiloClientConnection.java:86)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at 
> org.apache.camel.component.milo.client.MiloClientConsumer.doStart(MiloClientConsumer.java:57)
>  [camel-milo-2.21.0-SNAPSHOT.jar:2.21.0-SNAPSHOT]
>     at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) 
> [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.startService(DefaultCamelContext.java:3701)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRouteConsumers(DefaultCamelContext.java:4019)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStartRouteConsumers(DefaultCamelContext.java:3954)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.safelyStartRouteServices(DefaultCamelContext.java:3874)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRoutes(DefaultCamelContext.java:3638)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:3490)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.access$000(DefaultCamelContext.java:208)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3249)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3245)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
> org.apache.camel.impl.DefaultCamelContext.doWithDefinedClassLoader(DefaultCamelContext.java:3268)
>  [camel-core-2.20.2.jar:2.20.2]
>     at 
>

[jira] [Commented] (CAMEL-12291) Blueprint error: "name is already instanciated as null and cannot be removed"

[jira] [Created] (CAMEL-12289) URISyntaxException in AbstractSpanDecorator

[jira] [Created] (CAMEL-12290) CxfEndpoint with JDK9: NoClassDefFoundError: javax/jws/WebService

[jira] [Commented] (CAMEL-12289) URISyntaxException in AbstractSpanDecorator

[jira] [Created] (CAMEL-12291) Blueprint error: "name is already instanciated as null and cannot be removed"

[jira] [Commented] (CAMEL-12291) Blueprint error: "name is already instanciated as null and cannot be removed"

[jira] [Resolved] (CAMEL-12291) Blueprint error: "name is already instanciated as null and cannot be removed"

[jira] [Reopened] (CAMEL-12291) Blueprint error: "name is already instanciated as null and cannot be removed"

[jira] [Updated] (CAMEL-12291) Blueprint error: "name is already instanciated as null and cannot be removed"

[jira] [Comment Edited] (CAMEL-12291) Blueprint error: "name is already instanciated as null and cannot be removed"

[jira] [Commented] (CAMEL-12286) Milo client broken

[jira] [Commented] (CAMEL-12286) Milo client broken

[jira] [Created] (CAMEL-12287) Allow overriding the server reported endpoint

[jira] [Commented] (CAMEL-12286) Milo client broken

[jira] [Commented] (CAMEL-12286) Milo client broken

[jira] [Commented] (CAMEL-12286) Milo client broken

[jira] [Commented] (CAMEL-12286) Milo client broken

[jira] [Updated] (CAMEL-12286) Milo client broken

[jira] [Resolved] (CAMEL-12286) Milo client broken

[jira] [Created] (CAMEL-12288) Need call method feature

[jira] [Commented] (CAMEL-12288) Need call method feature

[jira] [Resolved] (CAMEL-12288) Need call method feature

[jira] [Updated] (CAMEL-12288) Need call method feature for milo client component

[jira] [Updated] (CAMEL-12288) Need method call feature for milo client component

[jira] [Updated] (CAMEL-12288) Need method call feature for milo client component

[jira] [Commented] (CAMEL-12288) Need method call feature for milo client component

[jira] [Reopened] (CAMEL-12288) Need method call feature for milo client component

[jira] [Issue Comment Deleted] (CAMEL-12288) Need method call feature for milo client component

[jira] [Updated] (CAMEL-12288) Need method call feature for milo client component

[jira] [Updated] (CAMEL-12288) Need method call feature for milo client component

[jira] [Commented] (CAMEL-12288) Need method call feature for milo client component

[jira] [Commented] (CAMEL-12288) Need method call feature for milo client component

[jira] [Commented] (CAMEL-12286) Milo client broken

[jira] [Commented] (CAMEL-12286) Milo client broken

34 matches

Site Navigation

Mail list logo

Footer information