There's a bean with this annotation
@Size(min = 1, max = 10)
@NotNull
private java.lang.String name;
looks like causing
2022-05-18T11:56:27,906 | WARN | qtp534549026-548 |
RestOpenApiProcessor | mel.openapi.RestOpenApiProcessor 78
| 257 -
it to improve this. Can you please share a test
case to reproduce it (I tried and it works fine for me) ?
Thanks,
Regards
JB
On Mon, May 16, 2022 at 11:56 AM Martin Lichtin
wrote:
I was wondering of any side-effects once this message appears
BlueprintCamelStateService 137 | 134
I was wondering of any side-effects once this message appears
BlueprintCamelStateService 137 | 134 -
org.apache.camel.karaf.camel-blueprint - 3.14.3 | Karaf
BundleStateService not accessible. Bundle state won't reflect Camel
context state
not instantly seeing an issue, just curious about
Is there potentially a race condition when calling addRoutes while
camelContext status is 'Initializing'?
I noticed the routes are not actually added in such a case, but no error
or warning appears, they're just silently ignored.
Creating the CamelContext with blueprint, then adding the
Would you have an idea what could provoke this? It happens infrequently
2022-05-08T22:14:54,999 | ERROR | rint Event Dispatcher: 1 |
BlueprintCamelContext | .blueprint.BlueprintCamelContext 190
| 188 - org.apache.camel.karaf.camel-blueprint - 3.14.3 | Error occurred
during
Camel 3.14.2 features, xml-specs-api loading jaxb-runtime/2.3.1_1
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.jaxb-runtime/2.3.1_1
but better would be to load jaxb-runtime version 2.3.2_1 as this version
contains the "com.sun.istack" classes that 2.3.1_1 is missing.
Any reason the version for org.apache.cxf packages is so restricted?
e.g. in the camel-cxf-transport MANIFEST:
Import-Package: ., org.apache.cxf.transport;version="[3.4,3.4]"
means exactly version 3.4.0 is required.
Is there a way to avoid such exceptions on a timer:// route stop?
java.util.concurrent.RejectedExecutionException: null
at
org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$SimpleTask.run(RedeliveryErrorHandler.java:429)
~[?:?]
at
Hi,
the migration says
"Support for multiple CamelContexts has been removed and only 1 CamelContext per
deployment is supported."
The term "deployment" seem loose.
My concern here is that in OSGi each bundle has its own CamelContext (e.g. via
blueprint configuration), how will that work?
-
https://camel.apache.org/components/2.x/http4-component.html
The documentation lists two Uri parameters, "proxyAuthHost" and "proxyHost"
(and again two for 'Port').
Is there a difference, or are both offering the same functionality to configure
the proxy host.
- Martin
PS: Noticed
�
���
�
On 19.08.2020 16:01, Alex Soto wrote:
Thanks Alex,
Also looking for a way to configure this in a Blueprint XML file.
Best regards,
Alex soto
On Aug 18, 2020, at 11:13 AM, Alex Dettinger wrote:
Hi Alex,
It seems the timeout is tuned after the context creation.
juil. 2020 à 11:43, Martin Lichtin a écrit :
Hi JB
I would, if that was the issue.
However in all the CamelContexts I'm only using regular beans, not calling an
OSGi service.
Ideally there should be a way to tell Camel to not look into the OSGi registry
when resolving bean names. But seems
juin 2020 à 09:29, Martin Lichtin a écrit :
Thanks.
Unfortunately the cache does not seem to kick in.
Also it's supposed to be turned on by default (xsd: "Caches the bean lookup, to
avoid lookup up bean on every usage. Default value: true".
The bean is called from a REST CamelContext
)
In Camel 3.x there is a new scope option instead
On Thu, Jun 25, 2020 at 5:09 PM Martin Lichtin
wrote:
Is there a way to tell Camel to not search OSGi services when looking up a bean?
It seems by default it's continuously looking up the service references, would
like to turn this off
It's Camel 2.24.3
On 25.06.2020 17:10, Andrea Cosentino wrote:
What is the camel version for this?
Il giorno gio 25 giu 2020 alle ore 17:09 Martin Lichtin
ha scritto:
Is there a way to tell Camel to not search OSGi services when looking up a
bean?
It seems by default it's continuously
Is there a way to tell Camel to not search OSGi services when looking up a bean?
It seems by default it's continuously looking up the service references, would
like to turn this off.
Stack Trace Sample Count Percentage(%)
java.util.TreeMap.getEntryUsingComparator(Object) 17 3.753
elho Soares
On Thu, Jul 12, 2018 at 4:55 PM Martin Lichtin
wrote:
Anyone know how I can configure so the generated
swagger.json does not set host: "0.0.0.0"?
With this 0.0.0.0 I cannot, for example, import the Swagger directly into
Postman and make calls to the API.
https://swagger
Anyone know how I can configure so the generated swagger.json does
not set host: "0.0.0.0"?
With this 0.0.0.0 I cannot, for example, import the Swagger directly into
Postman and make calls to the API.
https://swagger.io/docs/specification/2-0/api-host-and-base-path/ says the
"host" can be
Using the File2 component (2.19.5), I'm provoking a situation with the "move"
folder no longer being writable.
This causes the following exception to occur and logged during the "commit"
phase.
And then, with every consumer poll, the same file is being imported again and
again!
Not a good
m/apache/camel/blob/camel-2.19.x/camel-core/src/main/docs/direct-component.adoc>
which you may need to set to true on your own in 2.19.5.
On Thu, Apr 26, 2018 at 6:24 PM, Martin Lichtin <lich...@yahoo.com.invalid>
wrote:
After upgrading from 2.18 to 2.19.5, I'm often seeing this excepti
After upgrading from 2.18 to 2.19.5, I'm often seeing this exception at startup.
It looks like the auto-started route is not immediately ready?
Using a producer template, it can happen that
"DirectConsumerNotAvailableException" is thrown.
At next try (e.g. a second later) it works.
How can this
Started using the File component (2.19.5) and seeing exchange properties with
prefixed names that don't seem to make sense:
"CompletePathAndFilename"-CamelFileLockFileAcquired=true,
"CompletePathAndFilename"-CamelFileLockFileName="CompletePathAndFilename".camelLock,
where
To make REST use my own ObjectMapper, I try below but it doesn't work.
Anyone have an example that does?
http://camel.apache.org/schema/blueprint;>
Thanks for a hint.
On 01.11.2017 22:21, Martin Lichtin wrote:
I'm runn
I'm running into a jackson.databind.JsonMappingException: Infinite recursion
(StackOverflowError)
with a REST route that uses bindingMode="json" to marshal/unmarshal. It loops
like:
...
at
the
Camel* headers, the params from the Url query string, etc...
On 25.09.2017 15:26, Claus Ibsen wrote:
Remove the Content-Length header when you change the body
On Mon, Sep 25, 2017 at 2:47 PM, Martin Lichtin
<lich...@yahoo.com.invalid> wrote:
Using an to handle an exception, I want t
Using an to handle an exception, I want to mark the situation as
'handled' and set the body with information from the exception. Eg:
java.lang.Exception
false
500
${exception.stacktrace}
Problem is: the body
. with
null
On 16.09.2017 18:34, Martin Lichtin wrote:
Camel Rest DSL
Want to ask how can one pass the body of a PUT request to a method positional
argument.
Eg, with bindingMode=json will the magic ${body} work?
with the method in Java as
update(String id
Camel Rest DSL
Want to ask how can one pass the body of a PUT request to a method positional
argument.
Eg, with bindingMode=json will the magic ${body} work?
with the method in Java as
update(String id, MyOrder myOrder)
Searched the docs (including Camel
Trying to upgrade from 2.17.7 to 2.18.4 I'm running into the following problem:
org.osgi.service.blueprint.container.ComponentDefinitionException:
org.apache.aries.proxy.FinalModifierException: The methods protected final void
Upgrading from 2.16.x to 2.17.7 I see many
Runtime endpoint registry is in extended mode gathering usage statistics of all
incoming and outgoing endpoints (cache limit: 1000)
messages.I'm not setting the statisticslevel, and the default level should not
be extended?
);
}
})
On 13.05.2017 09:35, Claus Ibsen wrote:
You can add onWhen where you can do a predicate to decide that per message
On Sat, May 13, 2017 at 9:00 AM, Martin Lichtin
<lich...@yahoo.com.invalid> wrote:
One can define a route exception handling to catch and continue:
rd.onException(Exception
One can define a route exception handling to catch and continue:
rd.onException(Exception.class).continued(true).process(myExceptionHandler)
However, how can one decide on a per-message basis (ie. in myExceptionHandler)
whether to continue with the route or not?
Thanks
- Martin
markRollbackOnly() - I’ve never used rollback()) are in routes where something
besides an exception determines whether or not I want to rollback the
transaction.
For what it’s worth ...
On Mar 31, 2017, at 6:18 AM, Martin Lichtin<lich...@yahoo.com.INVALID> wrote:
Hi
Wanted to ask, what
Hi
Wanted to ask, what would be a reason to explicitly call rollback() in an
onException().
For example, would this make sense?
.onException(Exception.class).rollback().end()
I'm under the expression above line could just be left out, as Camel anyway
lets
the exception up and that will
Hi All
Having an issue with Camel context shutdown taking much longer than expected.
The trace below shows it quite well.
There's 2 seconds "graceful" shutdown, but then it takes 2x10 seconds to
"really" shutdown.
Any ideas why that could be? Also, how can I reduce the 10 seconds termination
You would need to build your custom
> shutdown, and that can be a bit more complex if some routes have inter
> related dependencies, so you cannot shutdown X before Y etc.
>
> On Thu, Jul 14, 2016 at 12:01 PM, Martin Lichtin
>
> lichtin@.com
> wrote:
>> Is there
Is there a way to shutdown some routes in a context concurrently?
The default shutdown strategy seems to handle one route after the other.
To speed things up, I'm looking for a way to shutdown a set of routes at once.
hat version of Camel do you use. And what is the real stacktrace printed
>
> And what is the *actual* url you call. As that plain string should be
> parsable.
>
>
>
> On Thu, Mar 24, 2016 at 10:39 AM, Martin Lichtin
>
> lichtin@.com
> wrote:
>> When usi
When using a producer template to send messages to a JMS queue, such as
producerTemplate.sendBodyAndHeaders("jms:queue:myQ", body, headers);
we see how this internally always creates an exception:
java.lang.Throwable.(String) line: 267
java.lang.Exception.(String) line: 52
PM, Martin Lichtin
lich...@yahoo.com.invalid wrote:
Trying a new command.
karaf camel:context-inflight myCamelContext
Error executing command: Object name cannot be null
Trying a new command.
karaf camel:context-inflight myCamelContext
Error executing command: Object name cannot be null
In the end, the solution was to replace
to uri=bean:myBean /
with
bean ref=myBean /
This way, the bean is still referencend and can be called while the other
context is shutting down.
- Martin
Martin Lichtin-2 wrote
This didn't make a difference.
However, something else I noticed
if blueprint shutdown in reverse
order and therefore the bean before camel etc.
On Tue, May 26, 2015 at 9:56 PM, Martin Lichtin
lich...@yahoo.com.invalid wrote:
Using Blueprint in an OSGi bundle:
bean id=myBean init-method=init destroy-method=destroy
class=myPkg.MyBean
/bean
camelContext
at 12:41 PM, Martin Lichtin
lich...@yahoo.com.invalid wrote:
Is anyone else seeing this issue on shutting down a simple timer-based route
such as
route id=myRoute
from uri=timer://myTimer?fixedRate=trueamp;period 00
/
to uri=bean:myBean /
/route
Is anyone else seeing this issue on shutting down a simple timer-based route
such as
route id=myRoute
from
uri=timer://myTimer?fixedRate=trueamp;period=2000 /
to uri=bean:myBean /
/route
On shutting down, it reports
2015-05-22 01:20:14,970 |
:41 PM, Martin Lichtin
lich...@yahoo.com.invalid wrote:
Is anyone else seeing this issue on shutting down a simple timer-based route
such as
route id=myRoute
from uri=timer://myTimer?fixedRate=trueamp;period 00
/
to uri=bean:myBean /
/route
/1.2
ahead of installing the 'camel' feature, then I can later install 'cxf'.
James Carman wrote
You need to update jre.properties to make sure you have the right version
coming from the jre. What jdk?
On Monday, April 6, 2015, Martin Lichtin lt;
lichtin@.com
gt; wrote:
In a Karaf
)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On April 3, 2015 at 11:26:55 PM, Martin Lichtin (
lichtin@.com
) wrote:
Using Camel 2.15.1 and CXF 3.0.4 in a Karaf container, I'm wondering how
one can control the Spring version.
Camel feature camel-spring loads
In a Karaf 3.0.3 container one cannot install feature 'camel' followed
by installing 'cxf'.
karaf@root() feature:repo-add
mvn:org.apache.camel.karaf/apache-camel/2.15.1/xml/features
Adding feature url
mvn:org.apache.camel.karaf/apache-camel/2.15.1/xml/features
karaf@root() feature:install
.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On April 3, 2015 at 11:26:55 PM, Martin Lichtin (
lichtin@.com
) wrote:
Using Camel 2.15.1 and CXF 3.0.4 in a Karaf container, I'm
Using Camel 2.15.1 and CXF 3.0.4 in a Karaf container, I'm wondering how
one can control the Spring version.
Camel feature camel-spring loads Spring with
feature version=[3.2,4)spring/feature
which will result in loading 3.2.11.RELEASE.
Is there a way to use Spring 4?
- Martin
51 matches
Mail list logo
