how to hold temporary data to use later.....

[sungkwon.eom]

Hello, this is the scenario what I want to handle..


1) load files from a directory
2)collect first line from each files  (Using this data DB will be
updated later)
3)compress files to a single tar.gz file.
4)upload the compressed file to FTP site.
5)update DB table over the compressed and FTP uploded files using temporary
data from (2).


In here, how can I hold the first line of each files and how to pass the
line data to DB route?
Of course if compress & FTP uploading is fail,  DB update should not occur.

Thanks, in advance.



--
View this message in context: 
http://camel.465427.n5.nabble.com/how-to-hold-temporary-data-to-use-later-tp5781121.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Apache Camel bean parameter binding issue with Spring DSL

[Claus Ibsen]

Hi

Thanks I logged a ticket
https://issues.apache.org/jira/browse/CAMEL-9870

On Thu, Apr 14, 2016 at 10:00 PM, Mario Balaban  wrote:
> I am using version 2.16.1. The example is something like this:
>
>  
>
> and the the java bean method is:
>
> public void addNote(String invoice, String note){
> ...}
>
> In this case the binding expression assigns the result of Invoice.toString
> method to the first argument and null to the second even if there is a
> header with name "note" that does contain a non null value.
>
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/Apache-Camel-bean-parameter-binding-issue-with-Spring-DSL-tp5772200p5781114.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel scheduler is not concurrent

[cookie]

Thank you very much... that looks like the answer I am looking for.



--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-scheduler-is-not-concurrent-tp5781066p5781120.html
Sent from the Camel - Users mailing list archive at Nabble.com.

RE: camel-spring-boot + @UseAdviceWith

[David Bennison]

Fortunately I am not too far into my project so I've branched and ripped out 
Camel Spring Boot (which is a shame). I lost a few days with this issue and it 
makes me wonder what other problems may be lurking. They really should have 
done what Chris Love suggested on CAMEL-7963 and highlighted in the Docs the 
annotations that don't work, preferably with any known workarounds.

BTW once I ripped out Camel Spring Boot the @UseAdviceWith worked.

From: Jeff Segal 
Sent: 14 April 2016 18:18
To: users@camel.apache.org
Subject: Re: camel-spring-boot + @UseAdviceWith

Exactly - I had the same suspicion with regard to Camel-7963 but was hoping
to be proven wrong here. I have not gotten any further unfortunately. I'm
planning on trying a few work-arounds but it's unclear what the typical
setup ought to be. I would think that others would be in the same boat if
they want to apply integration tests to their routes while using
camel-spring-boot.

Jeff

On Thu, Apr 14, 2016 at 5:16 AM, David Bennison  wrote:

> Our problem looks similar to this one with @MockEndpoints raised back in
> 2015 against Camel 2.16.0.
>
> http://grokbase.com/t/camel/users/15bgwdeftt/spring-boot-test-mocks
>
> The reason given by Joakim Bjørnstad appears to explain what we are
> experiencing.
>
> The last comment on https://issues.apache.org/jira/browse/CAMEL-7963 is:-
>
> "I still need to add support for Spring test annotations like
> @MockEndpoints"
>
> So perhaps they never got done. I had problems with @MockEndpoints as
> well. I am also experiencing strangeness with NotifyBuilder but that could
> be unrelated.
> 
> From: Jeff Segal 
> Sent: 12 April 2016 16:46
> To: users@camel.apache.org
> Subject: camel-spring-boot + @UseAdviceWith
>
> All,
>
> I'm currently creating a camel-spring-boot project and would like to add
> some tests using @UseAdviceWith but am hitting a few issues. I couldn't
> find an example that fit that use case exactly, so I've played around with
> different things to no avail.
>
> Specifically, I found that when I use @ContextConfiguration to specify my
> main Spring app config, my use of
> @BootstrapWith(CamelTestContextBootstrapper.class) is honored (i.e. I can
> step through it in a debugger during startup) and I can see @UseAdviceWith
> being used in CamelSpringTestContextLoader.handleCamelContextStartup().
> However, when I @Autowire my CamelContext into my test class, Spring
> startup fails because it can't find my CamelContext Spring bean (even when
> I explicitly include a @Configuration that extends CamelConfiguration,
> which explicitly creates a CamelContext @Bean). I need a reference to my
> CamelContext so that I can start it once I'm done setting up my routeWith
> advice.
>
> One last thing: when I use @SpringApplicationConfiguration instead of
> @ContextConfiguration, Spring is able to find the CamelContext bean but it
> ignores my @BootstrapWith(CamelTestContextBootstrapper.class) &
> @UseAdviceWith and thus just starts up the CamelContext automatically
> rather than waiting for me to start it manually (after my routeWith
> advice).
>
> Any pointers on what I might be doing wrong would be great. In summary:
>
> Honoring @UseAdviceWith but no CamelContext Spring bean:
>
> @ContextConfiguration(classes = {ApplicationConfig.class})
> @RunWith(CamelSpringJUnit4ClassRunner.class)
> @BootstrapWith(CamelTestContextBootstrapper.class)
> @UseAdviceWith
> @Slf4j
> public class MyTest {
>
> @Autowired
> CamelContext camelContext;
>
> @Test
> public void test() throws InterruptedException {
> log.info("Starting test...");
> Thread.sleep(1000 * 60);
> }
>
> }
>
> Have a CamelContext Spring bean but NOT honoring @UseAdviceWith:
>
> @SpringApplicationConfiguration(classes = {ApplicationConfig.class})
> @RunWith(CamelSpringJUnit4ClassRunner.class)
> @BootstrapWith(CamelTestContextBootstrapper.class)
> @UseAdviceWith
> @Slf4j
> public class MyTest {
>
> @Autowired
> CamelContext camelContext;
>
> @Test
> public void test() throws InterruptedException {
> log.info("Starting test...");
> Thread.sleep(1000 * 60);
> }
>
> }
>
> Thanks!
> Jeff
> This email is confidential and may be privileged. If you are not the
> intended recipient, please notify the sender immediately and delete the
> email from your computer. You should not copy the email, use it for any
> purpose or disclose its contents to any other person. Please note that any
> views or opinions presented in this email may be personal to the author and
> do not necessarily represent the views or opinions of MetaPack. It is the
> responsibility of the recipient to check this email for the presence of
> viruses. MetaPack accepts no liability for any damage caused by any virus
> transmitted by this email. MetaPack Registered Office: 4th Floor, 200
> Gray’s Inn Road London WC1X 8XZ. Registered in England No. 03870530. 

Re: Apache Camel bean parameter binding issue with Spring DSL

[Mario Balaban]

I am using version 2.16.1. The example is something like this: 

 

and the the java bean method is: 

public void addNote(String invoice, String note){
...}

In this case the binding expression assigns the result of Invoice.toString
method to the first argument and null to the second even if there is a
header with name "note" that does contain a non null value.




--
View this message in context: 
http://camel.465427.n5.nabble.com/Apache-Camel-bean-parameter-binding-issue-with-Spring-DSL-tp5772200p5781114.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Camel Shutdown does not shutdown ActiveMQ

[mattmadhavan]

Hello,
When I try to shutdown a Spring boot/Camel application for some reason the
activemq connections are not shutdown. I am shutting down as follows.



But as can be seen from Eclipse the application does not shutdown.

 

Any ides please?

Thanks
Matt



-
Thanks
Matt G. Madhavan
--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-Shutdown-does-not-shutdown-ActiveMQ-tp5781115.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camel-spring-boot + @UseAdviceWith

[Jeff Segal]

Exactly - I had the same suspicion with regard to Camel-7963 but was hoping
to be proven wrong here. I have not gotten any further unfortunately. I'm
planning on trying a few work-arounds but it's unclear what the typical
setup ought to be. I would think that others would be in the same boat if
they want to apply integration tests to their routes while using
camel-spring-boot.

Jeff

On Thu, Apr 14, 2016 at 5:16 AM, David Bennison  wrote:

> Our problem looks similar to this one with @MockEndpoints raised back in
> 2015 against Camel 2.16.0.
>
> http://grokbase.com/t/camel/users/15bgwdeftt/spring-boot-test-mocks
>
> The reason given by Joakim Bjørnstad appears to explain what we are
> experiencing.
>
> The last comment on https://issues.apache.org/jira/browse/CAMEL-7963 is:-
>
> "I still need to add support for Spring test annotations like
> @MockEndpoints"
>
> So perhaps they never got done. I had problems with @MockEndpoints as
> well. I am also experiencing strangeness with NotifyBuilder but that could
> be unrelated.
> 
> From: Jeff Segal 
> Sent: 12 April 2016 16:46
> To: users@camel.apache.org
> Subject: camel-spring-boot + @UseAdviceWith
>
> All,
>
> I'm currently creating a camel-spring-boot project and would like to add
> some tests using @UseAdviceWith but am hitting a few issues. I couldn't
> find an example that fit that use case exactly, so I've played around with
> different things to no avail.
>
> Specifically, I found that when I use @ContextConfiguration to specify my
> main Spring app config, my use of
> @BootstrapWith(CamelTestContextBootstrapper.class) is honored (i.e. I can
> step through it in a debugger during startup) and I can see @UseAdviceWith
> being used in CamelSpringTestContextLoader.handleCamelContextStartup().
> However, when I @Autowire my CamelContext into my test class, Spring
> startup fails because it can't find my CamelContext Spring bean (even when
> I explicitly include a @Configuration that extends CamelConfiguration,
> which explicitly creates a CamelContext @Bean). I need a reference to my
> CamelContext so that I can start it once I'm done setting up my routeWith
> advice.
>
> One last thing: when I use @SpringApplicationConfiguration instead of
> @ContextConfiguration, Spring is able to find the CamelContext bean but it
> ignores my @BootstrapWith(CamelTestContextBootstrapper.class) &
> @UseAdviceWith and thus just starts up the CamelContext automatically
> rather than waiting for me to start it manually (after my routeWith
> advice).
>
> Any pointers on what I might be doing wrong would be great. In summary:
>
> Honoring @UseAdviceWith but no CamelContext Spring bean:
>
> @ContextConfiguration(classes = {ApplicationConfig.class})
> @RunWith(CamelSpringJUnit4ClassRunner.class)
> @BootstrapWith(CamelTestContextBootstrapper.class)
> @UseAdviceWith
> @Slf4j
> public class MyTest {
>
> @Autowired
> CamelContext camelContext;
>
> @Test
> public void test() throws InterruptedException {
> log.info("Starting test...");
> Thread.sleep(1000 * 60);
> }
>
> }
>
> Have a CamelContext Spring bean but NOT honoring @UseAdviceWith:
>
> @SpringApplicationConfiguration(classes = {ApplicationConfig.class})
> @RunWith(CamelSpringJUnit4ClassRunner.class)
> @BootstrapWith(CamelTestContextBootstrapper.class)
> @UseAdviceWith
> @Slf4j
> public class MyTest {
>
> @Autowired
> CamelContext camelContext;
>
> @Test
> public void test() throws InterruptedException {
> log.info("Starting test...");
> Thread.sleep(1000 * 60);
> }
>
> }
>
> Thanks!
> Jeff
> This email is confidential and may be privileged. If you are not the
> intended recipient, please notify the sender immediately and delete the
> email from your computer. You should not copy the email, use it for any
> purpose or disclose its contents to any other person. Please note that any
> views or opinions presented in this email may be personal to the author and
> do not necessarily represent the views or opinions of MetaPack. It is the
> responsibility of the recipient to check this email for the presence of
> viruses. MetaPack accepts no liability for any damage caused by any virus
> transmitted by this email. MetaPack Registered Office: 4th Floor, 200
> Gray’s Inn Road London WC1X 8XZ. Registered in England No. 03870530. VAT No
> 945 7723 86.
>

Re: Camel HTTP4 Component and Curl Post Request behaving differently

[Debraj Manna]

The issue got resolved when I started sending the query parameters under
header Exchange.HTTP_QUERY and removed it from the main url. Earlier my url
was like


https4://example.com/oms-api/?Action=UpdateOrderInformation&ServiceName=OMS&Signature=25566099c0b6b6c5123bbfede4c91590512050668f957e2a43ef982a0dcf1c00&Timestamp=2016-04-14T12%3A44%3A17+0530&Version=1.0
".


Now in the working case my url is like

https4://example.com/oms-api/


and the query parameters are send as :
headers.put(Exchange.HTTP_QUERY, "
Action=UpdateOrderInformation&ServiceName=OMS&Signature=25566099c0b6b6c5123bbfede4c91590512050668f957e2a43ef982a0dcf1c00&Timestamp=2016-04-14T12%3A44%3A17+0530&Version=1.0

")

Can someone please let me know is it always recommended to send query
parameters under Exchange.HTTP_QUERY? I am asking this because sending the
query parameters with the main url is not failing always.


On Thu, Apr 14, 2016 at 2:08 PM, Debraj Manna 
wrote:

> Hi,
>
> I am facing a weird problem with Camel Http 4 component. Let me try to
> explain.
>
> I am making a post request (added the header Exchange.HTTP_METHOD:
> HttpMethods.POST) via camel http 4 component. It is returning me
>
> {
> "ErrorResponse": {
> "Head": {
> "RequestAction": "UpdateOrderInformation",
> "ErrorType": "Sender",
> "ErrorCode": "7",
> "ErrorMessage": "E007: Login failed. Signature mismatch"
> },
> "Body": ""
> }
> }
>
> Authentication was performed using authUserName & authPassword.
>
> But when I am sending the same url via curl as shown below:-
>
> curl -v -H "Accept: application/json" -H "Content-Type: application/json"
> -X POST -d '{"Request": {"Orders":[{"id_sales_order":
> 397,"address_billing": {"first_name":"John","last_name": "Doe","phone":
> "1234567","phone2": "1234","address1": "Sesamestreet 123","city":
> "Berlin","postcode": "12345","country": "Germany"}}]}}' "
> https://debraj:deb...@example.com/oms-api/?Action=UpdateOrderInformation&ServiceName=OMS&Signature=25566099c0b6b6c5123bbfede4c91590512050668f957e2a43ef982a0dcf1c00&Timestamp=2016-04-14T12%3A44%3A17+0530&Version=1.0
> "
>
> {
>   "SuccessResponse": {
> "Head": {
>   "RequestId": "",
>   "RequestAction": "UpdateOrderInformation",
>   "ResponseType": "",
>   "Timestamp": "2015-07-02T12:26:03+0200"
> },
> "Body": []
> }
>
> I have enabled debug http log. Below is the output:-
>
> 2016-04-14T12:44:18.375+0530 | DEBUG | qtp1202042637-19 |
> RequestAddCookies|  -  -  |
> {{camel.breadcrumbId,ID-debraj1247-34494-1460618050527-0-5}{camel.contextId,camel-1}{camel.exchangeId,ID-debraj1247-34494-1460618050527-0-6}{camel.messageId,ID-debraj1247-34494-1460618050527-0-5}{camel.routeId,route8}{reqId,fc652d13-8d81-4993-be88-89e93d93d7ef}{tId,5710da8e-abff--b609-852c9d1118df}}
> | CookieSpec selected: default
> 2016-04-14T12:44:18.385+0530 | DEBUG | qtp1202042637-19 |
> RequestAuthCache |  -  -  |
> {{camel.breadcrumbId,ID-debraj1247-34494-1460618050527-0-5}{camel.contextId,camel-1}{camel.exchangeId,ID-debraj1247-34494-1460618050527-0-6}{camel.messageId,ID-debraj1247-34494-1460618050527-0-5}{camel.routeId,route8}{reqId,fc652d13-8d81-4993-be88-89e93d93d7ef}{tId,5710da8e-abff--b609-852c9d1118df}}
> | Auth cache not set in the context
> 2016-04-14T12:44:18.386+0530 | DEBUG | qtp1202042637-19 |
> olingHttpClientConnectionManager |  -  -  |
> {{camel.breadcrumbId,ID-debraj1247-34494-1460618050527-0-5}{camel.contextId,camel-1}{camel.exchangeId,ID-debraj1247-34494-1460618050527-0-6}{camel.messageId,ID-debraj1247-34494-1460618050527-0-5}{camel.routeId,route8}{reqId,fc652d13-8d81-4993-be88-89e93d93d7ef}{tId,5710da8e-abff--b609-852c9d1118df}}
> | Connection request: [route: {s}->https://example.com:443][total kept
> alive: 0; route allocated: 0 of 20; total allocated: 0 of 200]
> 2016-04-14T12:44:18.404+0530 | DEBUG | qtp1202042637-19 |
> olingHttpClientConnectionManager |  -  -  |
> {{camel.breadcrumbId,ID-debraj1247-34494-1460618050527-0-5}{camel.contextId,camel-1}{camel.exchangeId,ID-debraj1247-34494-1460618050527-0-6}{camel.messageId,ID-debraj1247-34494-1460618050527-0-5}{camel.routeId,route8}{reqId,fc652d13-8d81-4993-be88-89e93d93d7ef}{tId,5710da8e-abff--b609-852c9d1118df}}
> | Connection leased: [id: 0][route: 

Log raw requests and responses received via a Jetty endpoint

[Roman Vottner]

We run a couple of Jetty servers through Camel and are curious if Camel 
provides any built-in facilities to log the raw HTTP request and also the 
response. We’d like an output similar to the one of an Apache HTTP Client (log 
messages for org.apache.http.wire) where an output may look like this:

2016-04-14 14:57:27 - [DEBUG] - http-outgoing-1 >> "POST /api/v1/someEndpoint 
HTTP/1.1[\r][\n]" [o.a.h.wire] [Console] 
2016-04-14 14:57:27 - [DEBUG] - http-outgoing-1 >> "Content-Type: 
application/json[\r][\n]" [o.a.h.wire] [Console] 
2016-04-14 14:57:27 - [DEBUG] - http-outgoing-1 >> "Content-Length: 
1030[\r][\n]" [o.a.h.wire] [Console] 
2016-04-14 14:57:27 - [DEBUG] - http-outgoing-1 >> "Host: 
localhost:8393[\r][\n]" [o.a.h.wire] [Console] 
2016-04-14 14:57:27 - [DEBUG] - http-outgoing-1 >> "Connection: 
Keep-Alive[\r][\n]" [o.a.h.wire] [Console] 
2016-04-14 14:57:27 - [DEBUG] - http-outgoing-1 >> "User-Agent: 
Apache-HttpClient/4.4 (Java 1.5 minimum; Java/1.8.0_66)[\r][\n]" [o.a.h.wire] 
[Console] 
2016-04-14 14:57:27 - [DEBUG] - http-outgoing-1 >> "Accept-Encoding: 
gzip,deflate[\r][\n]" [o.a.h.wire] [Console] 
2016-04-14 14:57:27 - [DEBUG] - http-outgoing-1 >> "Authorization: ...[\r][\n]" 
[o.a.h.wire] [Console] 
2016-04-14 14:57:27 - [DEBUG] - http-outgoing-1 >> "[\r][\n]" [o.a.h.wire] 
[Console] 
2016-04-14 14:57:27 - [DEBUG] - http-outgoing-1 >> "{"message“:“..."}" 
[o.a.h.wire] [Console] 
2016-04-14 14:57:27 - [DEBUG] - http-outgoing-1 << "HTTP/1.1 200 OK[\r][\n]" 
[o.a.h.wire] [Console] 
2016-04-14 14:57:27 - [DEBUG] - http-outgoing-1 << "Content-Type: 
application/json; charset=utf-8[\r][\n]" [o.a.h.wire] [Console] 
2016-04-14 14:57:27 - [DEBUG] - http-outgoing-1 << "Transfer-Encoding: 
chunked[\r][\n]" [o.a.h.wire] [Console] 
2016-04-14 14:57:27 - [DEBUG] - http-outgoing-1 << "[\r][\n]" [o.a.h.wire] 
[Console] 
2016-04-14 14:57:27 - [DEBUG] - http-outgoing-1 << "34[\r][\n]" [o.a.h.wire] 
[Console] 
2016-04-14 14:57:27 - [DEBUG] - http-outgoing-1 << "{"messageId“:“..."}" 
[o.a.h.wire] [Console] 
2016-04-14 14:57:27 - [DEBUG] - http-outgoing-1 << "[\r][\n]" [o.a.h.wire] 
[Console] 
2016-04-14 14:57:27 - [DEBUG] - http-outgoing-1 << "0[\r][\n]" [o.a.h.wire] 
[Console] 
2016-04-14 14:57:27 - [DEBUG] - http-outgoing-1 << "[\r][\n]" [o.a.h.wire] 
[Console] 

We use SLF4J/Logback for logging and stumbled over the logback-access library 
(http://logback.qos.ch/access.html#teeFilter) which seem to provide the 
functionality we are looking for already though I am not really able to get the 
TeeFilter (ServletFilter) for a JettyComponent(9) to work. We do not have any 
web.xml configs or the like as we use Camels Rest DSL over Jetty. 

Our configuration does look like this:

Spring Config:
--

@Configuration
public class ServicesSpringConfig extends CamelConfiguration {

  @Override
  protected void setupCamelContext(CamelContext camelContext) throws Exception {
...
camelContext.addComponent("jetty", jettyHttpComponent());
  }

  @private JettyHttpComponent jettyHttpComponent() throws URISyntaxException {
JettyHttpComponent jetty = new JettyHttpComponent9();
jetty.setSslContextParameters(sslContextParameters());
jetty.setErrorHandler(new SuppressJettyInfoErrorHandler());
return jetty;
  }

  @Bean(name = "jettyRawRequestResponseLogger")
  public TeeFilter jettyRawRequestResponseLogger() {
return new TeeFilter();
  }
}

Rest DSL:
-

restConfiguration()
.component("jetty")
.scheme("https")
.host("0.0.0.0")
.port("{{rest.port}}")
.contextPath("/api/v1")
.endpointProperty("matchOnUriPrefix", "true")
.endpointProperty("sendServerVersion", "false")
// we do want to make use of the streaming API which sends out the response 
in small chunks
// instead of all at once. This, however, will replace the Content-Length 
header field with
// a Transfer-Encoding: chunked header field. A chunk length of 0 indicates 
the end of the
// stream
.endpointProperty("chunked", "true")
.endpointProperty("headerFilterStrategy", „#customHeaderFilter")
.endpointProperty("filterRef", "#jettyRawRequestResponseLogger“);

How do I have to add the TeeFilter servlet filter to the Jetty component in 
order to log in- and outgoing messages as filterRef does not work in my case? 

Thanks for any help you can provide

Re: Unicode characters not recognizing when reading file

[patelp7]

I tried and it just doesnt work for me. As soon as I modify the body, either
try to replace all /r/n with /n or convert the body to string or use the
transform tag, the character is corrupted. I have attached the file if
that's helpful.

  sample_data_export.csv
  



--
View this message in context: 
http://camel.465427.n5.nabble.com/Unicode-characters-not-recognizing-when-reading-file-tp5781028p5781109.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel scheduler is not concurrent

[Claus Ibsen]

So if you want to use concurrent tasks on the same Camel route you
need to configure that on the scheduler.

I created an unit test to show how
https://github.com/apache/camel/commit/244868166b2df472a7bfe34e8bfaea6e453e6217

On Thu, Apr 14, 2016 at 2:44 PM, Claus Ibsen  wrote:
> Its used when you use the same thread pool but for multiple routes.
> Then each route can have their own tasks if you set
> concurrentTasks=Number of routes.
>
> See the unit test TwoSchedulerConcurrentTasksTest
>
> Then both routes use the same scheduler with the name foo, and its
> configured to have 2 concurrent tasks, so there is a task for each
> route.
>
> On Thu, Apr 14, 2016 at 9:55 AM, cookie  wrote:
>> Hi.
>>
>>According to the camel scheduler documentation it is possible to
>> configure its threadpool to support more than one thread at a time.
>> According to the following  commit
>> 
>> the option for it is "concurrentTasks=".
>>
>> However when I apply this option and use the debugger I see that the
>> configured number of threads are created but the scheduler always uses one
>> thread only, i.e. if I set a breakpoint in the corresponding bean method and
>> thus make the thread wait until after the next polling interval has reached,
>> I expect another thread to get activated and call the bean method but this
>> does not happen. Actually the additional threads NEVER get invoked, they are
>> just created.
>>
>> So one of my questions is: what is the intention behind concurrent tasks in
>> the scheduler?
>>
>> Also, is it possible to achieve the desired behavior using camel scheduler
>> or any other component?
>>
>> Thank you in advance
>>
>>
>>
>>
>>
>> --
>> View this message in context: 
>> http://camel.465427.n5.nabble.com/Camel-scheduler-is-not-concurrent-tp5781066.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
>
> --
> Claus Ibsen
> -
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel scheduler is not concurrent

[Claus Ibsen]

Its used when you use the same thread pool but for multiple routes.
Then each route can have their own tasks if you set
concurrentTasks=Number of routes.

See the unit test TwoSchedulerConcurrentTasksTest

Then both routes use the same scheduler with the name foo, and its
configured to have 2 concurrent tasks, so there is a task for each
route.

On Thu, Apr 14, 2016 at 9:55 AM, cookie  wrote:
> Hi.
>
>According to the camel scheduler documentation it is possible to
> configure its threadpool to support more than one thread at a time.
> According to the following  commit
> 
> the option for it is "concurrentTasks=".
>
> However when I apply this option and use the debugger I see that the
> configured number of threads are created but the scheduler always uses one
> thread only, i.e. if I set a breakpoint in the corresponding bean method and
> thus make the thread wait until after the next polling interval has reached,
> I expect another thread to get activated and call the bean method but this
> does not happen. Actually the additional threads NEVER get invoked, they are
> just created.
>
> So one of my questions is: what is the intention behind concurrent tasks in
> the scheduler?
>
> Also, is it possible to achieve the desired behavior using camel scheduler
> or any other component?
>
> Thank you in advance
>
>
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/Camel-scheduler-is-not-concurrent-tp5781066.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: PDF/A files using Camel FOP component

[Charles Moulliard]

This question has been asked within another forum:
https://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-users/201205.mbox/%3c4fc74204.4040...@takoma.fr%3E

On Thu, Apr 14, 2016 at 12:34 PM, Bilgin Ibryam  wrote:

> It might be better to ask this in the FOP list and find out why fonts
> might be missing and how to pass them. Then we can figure it out how
> to do it with Camel in/out of OSGI.
>
> On 14 April 2016 at 11:05, Laurentiu Trica 
> wrote:
> > Hi,
> >
> > No, I don't think it's related to your change, but it's an issue I have
> to
> > overcome.
> > I don't know how I'd pass the fonts in a non OSGI environment...
> >
> > I'm only working with Camel in OSGI, does anyone have any ideas on how to
> > make this work?
> >
> > Thanks,
> > Laurentiu
> >
> > On Thu, Apr 14, 2016 at 1:02 PM, Bilgin Ibryam 
> wrote:
> >
> >> Is that related my change in the component? How would you pass the
> >> fonts in a non-osgi environment?
> >>
> >> On 14 April 2016 at 08:03, Laurentiu Trica  >
> >> wrote:
> >> > Hi Bilgin,
> >> >
> >> > Thank you, sorry for the late response.
> >> > I tried your update and it seems to work, but now I get this error:
> >> >
> >> > javax.xml.transform.TransformerException:
> >> > org.apache.fop.pdf.PDFConformanceException: For PDF/A-1b, all fonts,
> even
> >> > the base 14 fonts, have to be embedded! Offending font: /Helvetica
> >> > at
> >> >
> >>
> com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:749)[:1.7.0_95]
> >> > at
> >> >
> >>
> com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:353)[:1.7.0_95]
> >> > at
> >> >
> >>
> de.edigrid.util.fop.FopProducer.transform(FopProducer.java:89)[520:org.apache.camel.camel-fop:2.13.2]
> >> > at
> >> >
> >>
> de.edigrid.util.fop.FopProducer.process(FopProducer.java:64)[520:org.apache.camel.camel-fop:2.13.2]
> >> > at
> >> >
> >>
> org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)[84:org.apache.camel.camel-core:2.14.1]
> >> > at
> >> >
> >>
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:120)[84:org.apache.camel.camel-core:2.14.1]
> >> > at
> >> >
> >>
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:72)[84:org.apache.camel.camel-core:2.14.1]
> >> > at
> >> >
> >>
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:416)[84:org.apache.camel.camel-core:2.14.1]
> >> > at
> >> >
> >>
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191)[84:org.apache.camel.camel-core:2.14.1]
> >> > at
> >> >
> >>
> org.apache.camel.processor.Pipeline.process(Pipeline.java:118)[84:org.apache.camel.camel-core:2.14.1]
> >> > at
> >> >
> >>
> org.apache.camel.processor.Pipeline.process(Pipeline.java:80)[84:org.apache.camel.camel-core:2.14.1]
> >> > at
> >> >
> >>
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191)[84:org.apache.camel.camel-core:2.14.1]
> >> > at
> >> >
> >>
> org.apache.camel.component.file.GenericFileConsumer.processExchange(GenericFileConsumer.java:433)[84:org.apache.camel.camel-core:2.14.1]
> >> > at
> >> >
> >>
> org.apache.camel.component.file.GenericFileConsumer.processBatch(GenericFileConsumer.java:211)[84:org.apache.camel.camel-core:2.14.1]
> >> > at
> >> >
> >>
> org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:175)[84:org.apache.camel.camel-core:2.14.1]
> >> > at
> >> >
> >>
> org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:187)[84:org.apache.camel.camel-core:2.14.1]
> >> > at
> >> >
> >>
> org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:114)[84:org.apache.camel.camel-core:2.14.1]
> >> > at
> >> >
> >>
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)[:1.7.0_95]
> >> > at
> >> >
> >>
> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)[:1.7.0_95]
> >> > at
> >> >
> >>
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)[:1.7.0_95]
> >> > at
> >> >
> >>
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)[:1.7.0_95]
> >> > at
> >> >
> >>
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[:1.7.0_95]
> >> > at
> >> >
> >>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.7.0_95]
> >> > at java.lang.Thread.run(Thread.java:745)[:1.7.0_95]
> >> > Caused by: org.apache.fop.pdf.PDFConformanceException: For PDF/A-1b,
> all
> >> > fonts, even the base 14 fonts, have to be embedded! Offending font:
> >> > /Helvetica
> >> > at
> >> >
> >>
> org.apache.fop.pdf.PDFFont.validate(PDFFont.java:169)[515:org.apache.servicemix.bundles.fop:1.1.0.1]
> >> > at
> >> >
> >>
> org.apache.fop.pdf.PDFFont.output(PDF

Re: PDF/A files using Camel FOP component

[Bilgin Ibryam]

It might be better to ask this in the FOP list and find out why fonts
might be missing and how to pass them. Then we can figure it out how
to do it with Camel in/out of OSGI.

On 14 April 2016 at 11:05, Laurentiu Trica  wrote:
> Hi,
>
> No, I don't think it's related to your change, but it's an issue I have to
> overcome.
> I don't know how I'd pass the fonts in a non OSGI environment...
>
> I'm only working with Camel in OSGI, does anyone have any ideas on how to
> make this work?
>
> Thanks,
> Laurentiu
>
> On Thu, Apr 14, 2016 at 1:02 PM, Bilgin Ibryam  wrote:
>
>> Is that related my change in the component? How would you pass the
>> fonts in a non-osgi environment?
>>
>> On 14 April 2016 at 08:03, Laurentiu Trica 
>> wrote:
>> > Hi Bilgin,
>> >
>> > Thank you, sorry for the late response.
>> > I tried your update and it seems to work, but now I get this error:
>> >
>> > javax.xml.transform.TransformerException:
>> > org.apache.fop.pdf.PDFConformanceException: For PDF/A-1b, all fonts, even
>> > the base 14 fonts, have to be embedded! Offending font: /Helvetica
>> > at
>> >
>> com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:749)[:1.7.0_95]
>> > at
>> >
>> com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:353)[:1.7.0_95]
>> > at
>> >
>> de.edigrid.util.fop.FopProducer.transform(FopProducer.java:89)[520:org.apache.camel.camel-fop:2.13.2]
>> > at
>> >
>> de.edigrid.util.fop.FopProducer.process(FopProducer.java:64)[520:org.apache.camel.camel-fop:2.13.2]
>> > at
>> >
>> org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)[84:org.apache.camel.camel-core:2.14.1]
>> > at
>> >
>> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:120)[84:org.apache.camel.camel-core:2.14.1]
>> > at
>> >
>> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:72)[84:org.apache.camel.camel-core:2.14.1]
>> > at
>> >
>> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:416)[84:org.apache.camel.camel-core:2.14.1]
>> > at
>> >
>> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191)[84:org.apache.camel.camel-core:2.14.1]
>> > at
>> >
>> org.apache.camel.processor.Pipeline.process(Pipeline.java:118)[84:org.apache.camel.camel-core:2.14.1]
>> > at
>> >
>> org.apache.camel.processor.Pipeline.process(Pipeline.java:80)[84:org.apache.camel.camel-core:2.14.1]
>> > at
>> >
>> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191)[84:org.apache.camel.camel-core:2.14.1]
>> > at
>> >
>> org.apache.camel.component.file.GenericFileConsumer.processExchange(GenericFileConsumer.java:433)[84:org.apache.camel.camel-core:2.14.1]
>> > at
>> >
>> org.apache.camel.component.file.GenericFileConsumer.processBatch(GenericFileConsumer.java:211)[84:org.apache.camel.camel-core:2.14.1]
>> > at
>> >
>> org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:175)[84:org.apache.camel.camel-core:2.14.1]
>> > at
>> >
>> org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:187)[84:org.apache.camel.camel-core:2.14.1]
>> > at
>> >
>> org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:114)[84:org.apache.camel.camel-core:2.14.1]
>> > at
>> >
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)[:1.7.0_95]
>> > at
>> >
>> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)[:1.7.0_95]
>> > at
>> >
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)[:1.7.0_95]
>> > at
>> >
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)[:1.7.0_95]
>> > at
>> >
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[:1.7.0_95]
>> > at
>> >
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.7.0_95]
>> > at java.lang.Thread.run(Thread.java:745)[:1.7.0_95]
>> > Caused by: org.apache.fop.pdf.PDFConformanceException: For PDF/A-1b, all
>> > fonts, even the base 14 fonts, have to be embedded! Offending font:
>> > /Helvetica
>> > at
>> >
>> org.apache.fop.pdf.PDFFont.validate(PDFFont.java:169)[515:org.apache.servicemix.bundles.fop:1.1.0.1]
>> > at
>> >
>> org.apache.fop.pdf.PDFFont.output(PDFFont.java:178)[515:org.apache.servicemix.bundles.fop:1.1.0.1]
>> > at
>> >
>> org.apache.fop.pdf.PDFDocument.outputIndirectObject(PDFDocument.java:951)[515:org.apache.servicemix.bundles.fop:1.1.0.1]
>> > at
>> >
>> org.apache.fop.pdf.PDFDocument.streamIndirectObject(PDFDocument.java:918)[515:org.apache.servicemix.bundles.fop:1.1.0.1]
>> > at
>> >
>> org.apache.fop.pdf.PDFDocument.output(PDFDocument.java:912)[515:org.apache.servicemix.bundles.fop:1.1.0.1]
>> > at
>> >
>> org.apache.fop.pdf.PDFDocu

Re: PDF/A files using Camel FOP component

[Laurentiu Trica]

Hi,

No, I don't think it's related to your change, but it's an issue I have to
overcome.
I don't know how I'd pass the fonts in a non OSGI environment...

I'm only working with Camel in OSGI, does anyone have any ideas on how to
make this work?

Thanks,
Laurentiu

On Thu, Apr 14, 2016 at 1:02 PM, Bilgin Ibryam  wrote:

> Is that related my change in the component? How would you pass the
> fonts in a non-osgi environment?
>
> On 14 April 2016 at 08:03, Laurentiu Trica 
> wrote:
> > Hi Bilgin,
> >
> > Thank you, sorry for the late response.
> > I tried your update and it seems to work, but now I get this error:
> >
> > javax.xml.transform.TransformerException:
> > org.apache.fop.pdf.PDFConformanceException: For PDF/A-1b, all fonts, even
> > the base 14 fonts, have to be embedded! Offending font: /Helvetica
> > at
> >
> com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:749)[:1.7.0_95]
> > at
> >
> com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:353)[:1.7.0_95]
> > at
> >
> de.edigrid.util.fop.FopProducer.transform(FopProducer.java:89)[520:org.apache.camel.camel-fop:2.13.2]
> > at
> >
> de.edigrid.util.fop.FopProducer.process(FopProducer.java:64)[520:org.apache.camel.camel-fop:2.13.2]
> > at
> >
> org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)[84:org.apache.camel.camel-core:2.14.1]
> > at
> >
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:120)[84:org.apache.camel.camel-core:2.14.1]
> > at
> >
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:72)[84:org.apache.camel.camel-core:2.14.1]
> > at
> >
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:416)[84:org.apache.camel.camel-core:2.14.1]
> > at
> >
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191)[84:org.apache.camel.camel-core:2.14.1]
> > at
> >
> org.apache.camel.processor.Pipeline.process(Pipeline.java:118)[84:org.apache.camel.camel-core:2.14.1]
> > at
> >
> org.apache.camel.processor.Pipeline.process(Pipeline.java:80)[84:org.apache.camel.camel-core:2.14.1]
> > at
> >
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191)[84:org.apache.camel.camel-core:2.14.1]
> > at
> >
> org.apache.camel.component.file.GenericFileConsumer.processExchange(GenericFileConsumer.java:433)[84:org.apache.camel.camel-core:2.14.1]
> > at
> >
> org.apache.camel.component.file.GenericFileConsumer.processBatch(GenericFileConsumer.java:211)[84:org.apache.camel.camel-core:2.14.1]
> > at
> >
> org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:175)[84:org.apache.camel.camel-core:2.14.1]
> > at
> >
> org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:187)[84:org.apache.camel.camel-core:2.14.1]
> > at
> >
> org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:114)[84:org.apache.camel.camel-core:2.14.1]
> > at
> >
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)[:1.7.0_95]
> > at
> >
> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)[:1.7.0_95]
> > at
> >
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)[:1.7.0_95]
> > at
> >
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)[:1.7.0_95]
> > at
> >
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[:1.7.0_95]
> > at
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.7.0_95]
> > at java.lang.Thread.run(Thread.java:745)[:1.7.0_95]
> > Caused by: org.apache.fop.pdf.PDFConformanceException: For PDF/A-1b, all
> > fonts, even the base 14 fonts, have to be embedded! Offending font:
> > /Helvetica
> > at
> >
> org.apache.fop.pdf.PDFFont.validate(PDFFont.java:169)[515:org.apache.servicemix.bundles.fop:1.1.0.1]
> > at
> >
> org.apache.fop.pdf.PDFFont.output(PDFFont.java:178)[515:org.apache.servicemix.bundles.fop:1.1.0.1]
> > at
> >
> org.apache.fop.pdf.PDFDocument.outputIndirectObject(PDFDocument.java:951)[515:org.apache.servicemix.bundles.fop:1.1.0.1]
> > at
> >
> org.apache.fop.pdf.PDFDocument.streamIndirectObject(PDFDocument.java:918)[515:org.apache.servicemix.bundles.fop:1.1.0.1]
> > at
> >
> org.apache.fop.pdf.PDFDocument.output(PDFDocument.java:912)[515:org.apache.servicemix.bundles.fop:1.1.0.1]
> > at
> >
> org.apache.fop.pdf.PDFDocument.outputTrailer(PDFDocument.java:995)[515:org.apache.servicemix.bundles.fop:1.1.0.1]
> > at
> >
> org.apache.fop.render.pdf.PDFDocumentHandler.endDocument(PDFDocumentHandler.java:172)[515:org.apache.servicemix.bundles.fop:1.1.0.1]
> > at
> >
> org.apache.fop.render.intermediate.util.IFDocumentHandlerProxy.endDocument(IFDocumentHandlerProxy.java:192)

Re: PDF/A files using Camel FOP component

[Bilgin Ibryam]

Is that related my change in the component? How would you pass the
fonts in a non-osgi environment?

On 14 April 2016 at 08:03, Laurentiu Trica  wrote:
> Hi Bilgin,
>
> Thank you, sorry for the late response.
> I tried your update and it seems to work, but now I get this error:
>
> javax.xml.transform.TransformerException:
> org.apache.fop.pdf.PDFConformanceException: For PDF/A-1b, all fonts, even
> the base 14 fonts, have to be embedded! Offending font: /Helvetica
> at
> com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:749)[:1.7.0_95]
> at
> com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:353)[:1.7.0_95]
> at
> de.edigrid.util.fop.FopProducer.transform(FopProducer.java:89)[520:org.apache.camel.camel-fop:2.13.2]
> at
> de.edigrid.util.fop.FopProducer.process(FopProducer.java:64)[520:org.apache.camel.camel-fop:2.13.2]
> at
> org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)[84:org.apache.camel.camel-core:2.14.1]
> at
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:120)[84:org.apache.camel.camel-core:2.14.1]
> at
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:72)[84:org.apache.camel.camel-core:2.14.1]
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:416)[84:org.apache.camel.camel-core:2.14.1]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191)[84:org.apache.camel.camel-core:2.14.1]
> at
> org.apache.camel.processor.Pipeline.process(Pipeline.java:118)[84:org.apache.camel.camel-core:2.14.1]
> at
> org.apache.camel.processor.Pipeline.process(Pipeline.java:80)[84:org.apache.camel.camel-core:2.14.1]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191)[84:org.apache.camel.camel-core:2.14.1]
> at
> org.apache.camel.component.file.GenericFileConsumer.processExchange(GenericFileConsumer.java:433)[84:org.apache.camel.camel-core:2.14.1]
> at
> org.apache.camel.component.file.GenericFileConsumer.processBatch(GenericFileConsumer.java:211)[84:org.apache.camel.camel-core:2.14.1]
> at
> org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:175)[84:org.apache.camel.camel-core:2.14.1]
> at
> org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:187)[84:org.apache.camel.camel-core:2.14.1]
> at
> org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:114)[84:org.apache.camel.camel-core:2.14.1]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)[:1.7.0_95]
> at
> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)[:1.7.0_95]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)[:1.7.0_95]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)[:1.7.0_95]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[:1.7.0_95]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.7.0_95]
> at java.lang.Thread.run(Thread.java:745)[:1.7.0_95]
> Caused by: org.apache.fop.pdf.PDFConformanceException: For PDF/A-1b, all
> fonts, even the base 14 fonts, have to be embedded! Offending font:
> /Helvetica
> at
> org.apache.fop.pdf.PDFFont.validate(PDFFont.java:169)[515:org.apache.servicemix.bundles.fop:1.1.0.1]
> at
> org.apache.fop.pdf.PDFFont.output(PDFFont.java:178)[515:org.apache.servicemix.bundles.fop:1.1.0.1]
> at
> org.apache.fop.pdf.PDFDocument.outputIndirectObject(PDFDocument.java:951)[515:org.apache.servicemix.bundles.fop:1.1.0.1]
> at
> org.apache.fop.pdf.PDFDocument.streamIndirectObject(PDFDocument.java:918)[515:org.apache.servicemix.bundles.fop:1.1.0.1]
> at
> org.apache.fop.pdf.PDFDocument.output(PDFDocument.java:912)[515:org.apache.servicemix.bundles.fop:1.1.0.1]
> at
> org.apache.fop.pdf.PDFDocument.outputTrailer(PDFDocument.java:995)[515:org.apache.servicemix.bundles.fop:1.1.0.1]
> at
> org.apache.fop.render.pdf.PDFDocumentHandler.endDocument(PDFDocumentHandler.java:172)[515:org.apache.servicemix.bundles.fop:1.1.0.1]
> at
> org.apache.fop.render.intermediate.util.IFDocumentHandlerProxy.endDocument(IFDocumentHandlerProxy.java:192)[515:org.apache.servicemix.bundles.fop:1.1.0.1]
> at
> org.apache.fop.render.intermediate.IFRenderer.stopRenderer(IFRenderer.java:296)[515:org.apache.servicemix.bundles.fop:1.1.0.1]
> at
> org.apache.fop.area.RenderPagesModel.endDocument(RenderPagesModel.java:265)[515:org.apache.servicemix.bundles.fop:1.1.0.1]
> at
> org.apache.fop.area.AreaTreeHandler.endDocument(AreaTreeHandler.java:342)[515:org.apache.servicemix.bundles.fop:1.1.0.1]
> at
> org.apache.fop.fo.FOTreeBuilder.endDocument(FOTreeBuilder.java:168)[515:org.apache.servicemix.

RE: camel-spring-boot + @UseAdviceWith

[David Bennison]

Our problem looks similar to this one with @MockEndpoints raised back in 2015 
against Camel 2.16.0.

http://grokbase.com/t/camel/users/15bgwdeftt/spring-boot-test-mocks

The reason given by Joakim Bjørnstad appears to explain what we are 
experiencing.

The last comment on https://issues.apache.org/jira/browse/CAMEL-7963 is:-

"I still need to add support for Spring test annotations like @MockEndpoints"

So perhaps they never got done. I had problems with @MockEndpoints as well. I 
am also experiencing strangeness with NotifyBuilder but that could be unrelated.

From: Jeff Segal 
Sent: 12 April 2016 16:46
To: users@camel.apache.org
Subject: camel-spring-boot + @UseAdviceWith

All,

I'm currently creating a camel-spring-boot project and would like to add
some tests using @UseAdviceWith but am hitting a few issues. I couldn't
find an example that fit that use case exactly, so I've played around with
different things to no avail.

Specifically, I found that when I use @ContextConfiguration to specify my
main Spring app config, my use of
@BootstrapWith(CamelTestContextBootstrapper.class) is honored (i.e. I can
step through it in a debugger during startup) and I can see @UseAdviceWith
being used in CamelSpringTestContextLoader.handleCamelContextStartup().
However, when I @Autowire my CamelContext into my test class, Spring
startup fails because it can't find my CamelContext Spring bean (even when
I explicitly include a @Configuration that extends CamelConfiguration,
which explicitly creates a CamelContext @Bean). I need a reference to my
CamelContext so that I can start it once I'm done setting up my routeWith
advice.

One last thing: when I use @SpringApplicationConfiguration instead of
@ContextConfiguration, Spring is able to find the CamelContext bean but it
ignores my @BootstrapWith(CamelTestContextBootstrapper.class) &
@UseAdviceWith and thus just starts up the CamelContext automatically
rather than waiting for me to start it manually (after my routeWith
advice).

Any pointers on what I might be doing wrong would be great. In summary:

Honoring @UseAdviceWith but no CamelContext Spring bean:

@ContextConfiguration(classes = {ApplicationConfig.class})
@RunWith(CamelSpringJUnit4ClassRunner.class)
@BootstrapWith(CamelTestContextBootstrapper.class)
@UseAdviceWith
@Slf4j
public class MyTest {

@Autowired
CamelContext camelContext;

@Test
public void test() throws InterruptedException {
log.info("Starting test...");
Thread.sleep(1000 * 60);
}

}

Have a CamelContext Spring bean but NOT honoring @UseAdviceWith:

@SpringApplicationConfiguration(classes = {ApplicationConfig.class})
@RunWith(CamelSpringJUnit4ClassRunner.class)
@BootstrapWith(CamelTestContextBootstrapper.class)
@UseAdviceWith
@Slf4j
public class MyTest {

@Autowired
CamelContext camelContext;

@Test
public void test() throws InterruptedException {
log.info("Starting test...");
Thread.sleep(1000 * 60);
}

}

Thanks!
Jeff
This email is confidential and may be privileged. If you are not the intended 
recipient, please notify the sender immediately and delete the email from your 
computer. You should not copy the email, use it for any purpose or disclose its 
contents to any other person. Please note that any views or opinions presented 
in this email may be personal to the author and do not necessarily represent 
the views or opinions of MetaPack. It is the responsibility of the recipient to 
check this email for the presence of viruses. MetaPack accepts no liability for 
any damage caused by any virus transmitted by this email. MetaPack Registered 
Office: 4th Floor, 200 Gray’s Inn Road London WC1X 8XZ. Registered in England 
No. 03870530. VAT No 945 7723 86.

Re: Apache Camel bean parameter binding issue with Spring DSL

[Claus Ibsen]

On Thu, Apr 14, 2016 at 10:23 AM, Mario Balaban  wrote:
> Hello, I also have been passing a couple of hours trying to debug a missing
> parenthesis from a bean binding expression. It would be nice if the parser
> threw an exception in case of missing close parenthesis. Thanks!
>

What Camel version did you use?
And can you show the example?




>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/Apache-Camel-bean-parameter-binding-issue-with-Spring-DSL-tp5772200p5781069.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Apache Camel bean parameter binding issue with Spring DSL

[Mario Balaban]

Hello, I also have been passing a couple of hours trying to debug a missing
parenthesis from a bean binding expression. It would be nice if the parser
threw an exception in case of missing close parenthesis. Thanks!



--
View this message in context: 
http://camel.465427.n5.nabble.com/Apache-Camel-bean-parameter-binding-issue-with-Spring-DSL-tp5772200p5781069.html
Sent from the Camel - Users mailing list archive at Nabble.com.

scalability with A MQ Xpaas component in openshift

[Meissa Sakho]

Hi all,
I'm using the A MQ Xpass component that is shipped with openshift 3.1

I've defined a multiple A-MQ pod with a broker running on each pod to
achieve scalability.
On the client side, I need to instruct to the consumer and provider the way
to access the service.
I'm not very sure about the protocole to use to send and receive messages.
here is the source code (extract) of my camel route:



@ContextName("myCdiCamelContext")

public class MyRoutes extends RouteBuilder {



@Inject

*@ServiceName("failover://broker-amq-tcp?randomize=false")*

@Alias("jms")

ActiveMQComponent activeMQComponent;



@Inject

@Uri("jms:queue:TEST.FOO")

Endpoint jmsEndpoint;



@Inject

@Uri("direct:hello")

Endpoint helloEndpoint;



@Inject

@Uri("direct:bye")

Endpoint byeEndpoint;



@Inject

@Uri("log:output")

Endpoint finalEndpoint;



@Inject

private DOICLogger myLogger;



@Override

public void configure() throws Exception {







restConfiguration().component("jetty").host("0.0.0.0").port(8080);




rest("rest/say").get("/hello/{name}").route().id("1").to(helloEndpoint);

rest("rest/say").get("/bye/{name}").route().id("2").to(byeEndpoint);



from(helloEndpoint).id("3").transform().simple("Hello ${header.name
}").to(jmsEndpoint);

from(byeEndpoint).id("4").transform().simple("Bye ${header.name
}").to(jmsEndpoint);





from(jmsEndpoint).id("5").to(finalEndpoint);

}

}





When I deploy my route on openshift, I'm having the exception below:

org.apache.camel.ExchangeTimedOutException: The OUT message was not
received within: 2 millis due reply message with correlationID:
Camel-ID-app-amq-3-4r37y-34752-1460564678101-0-15 not received on
destination: temp-queue://ID:app-amq-3-4r37y-40118-1460564679395-1:2:1.
Exchange[Message: Hello Bonjour]

at
org.apache.camel.component.jms.reply.ReplyManagerSupport.processReply(ReplyManagerSupport.java:152)

at
org.apache.camel.component.jms.reply.TemporaryQueueReplyHandler.onTimeout(TemporaryQueueReplyHandler.java:61)

at
org.apache.camel.component.jms.reply.CorrelationTimeoutMap.onEviction(CorrelationTimeoutMap.java:54)



Do you have any idea about what's wrong here.

thanks in advance,

Meissa

Thanks,

Meissa

Camel HTTP4 Component and Curl Post Request behaving differently

[Debraj Manna]

Hi,

I am facing a weird problem with Camel Http 4 component. Let me try to
explain.

I am making a post request (added the header Exchange.HTTP_METHOD:
HttpMethods.POST) via camel http 4 component. It is returning me

{
"ErrorResponse": {
"Head": {
"RequestAction": "UpdateOrderInformation",
"ErrorType": "Sender",
"ErrorCode": "7",
"ErrorMessage": "E007: Login failed. Signature mismatch"
},
"Body": ""
}
}

Authentication was performed using authUserName & authPassword.

But when I am sending the same url via curl as shown below:-

curl -v -H "Accept: application/json" -H "Content-Type: application/json"
-X POST -d '{"Request": {"Orders":[{"id_sales_order":
397,"address_billing": {"first_name":"John","last_name": "Doe","phone":
"1234567","phone2": "1234","address1": "Sesamestreet 123","city":
"Berlin","postcode": "12345","country": "Germany"}}]}}' "
https://debraj:deb...@example.com/oms-api/?Action=UpdateOrderInformation&ServiceName=OMS&Signature=25566099c0b6b6c5123bbfede4c91590512050668f957e2a43ef982a0dcf1c00&Timestamp=2016-04-14T12%3A44%3A17+0530&Version=1.0
"

{
  "SuccessResponse": {
"Head": {
  "RequestId": "",
  "RequestAction": "UpdateOrderInformation",
  "ResponseType": "",
  "Timestamp": "2015-07-02T12:26:03+0200"
},
"Body": []
}

I have enabled debug http log. Below is the output:-

2016-04-14T12:44:18.375+0530 | DEBUG | qtp1202042637-19 |
RequestAddCookies|  -  -  |
{{camel.breadcrumbId,ID-debraj1247-34494-1460618050527-0-5}{camel.contextId,camel-1}{camel.exchangeId,ID-debraj1247-34494-1460618050527-0-6}{camel.messageId,ID-debraj1247-34494-1460618050527-0-5}{camel.routeId,route8}{reqId,fc652d13-8d81-4993-be88-89e93d93d7ef}{tId,5710da8e-abff--b609-852c9d1118df}}
| CookieSpec selected: default
2016-04-14T12:44:18.385+0530 | DEBUG | qtp1202042637-19 |
RequestAuthCache |  -  -  |
{{camel.breadcrumbId,ID-debraj1247-34494-1460618050527-0-5}{camel.contextId,camel-1}{camel.exchangeId,ID-debraj1247-34494-1460618050527-0-6}{camel.messageId,ID-debraj1247-34494-1460618050527-0-5}{camel.routeId,route8}{reqId,fc652d13-8d81-4993-be88-89e93d93d7ef}{tId,5710da8e-abff--b609-852c9d1118df}}
| Auth cache not set in the context
2016-04-14T12:44:18.386+0530 | DEBUG | qtp1202042637-19 |
olingHttpClientConnectionManager |  -  -  |
{{camel.breadcrumbId,ID-debraj1247-34494-1460618050527-0-5}{camel.contextId,camel-1}{camel.exchangeId,ID-debraj1247-34494-1460618050527-0-6}{camel.messageId,ID-debraj1247-34494-1460618050527-0-5}{camel.routeId,route8}{reqId,fc652d13-8d81-4993-be88-89e93d93d7ef}{tId,5710da8e-abff--b609-852c9d1118df}}
| Connection request: [route: {s}->https://example.com:443][total kept
alive: 0; route allocated: 0 of 20; total allocated: 0 of 200]
2016-04-14T12:44:18.404+0530 | DEBUG | qtp1202042637-19 |
olingHttpClientConnectionManager |  -  -  |
{{camel.breadcrumbId,ID-debraj1247-34494-1460618050527-0-5}{camel.contextId,camel-1}{camel.exchangeId,ID-debraj1247-34494-1460618050527-0-6}{camel.messageId,ID-debraj1247-34494-1460618050527-0-5}{camel.routeId,route8}{reqId,fc652d13-8d81-4993-be88-89e93d93d7ef}{tId,5710da8e-abff--b609-852c9d1118df}}
| Connection leased: [id: 0][route: {s}->https://example.com:443][total
kept alive: 0; route allocated: 1 of 20; total allocated: 1 of 200]
2016-04-14T12:44:18.406+0530 | DEBUG | qtp1202042637-19 |
MainClientExec   |  -  -  |
{{camel.breadcrumbId,ID-debraj1247-34494-1460618050527-0-5}{camel.contextId,camel-1}{camel.exchangeId,ID-debraj1247-34494-1460618050527-0-6}{camel.messageId,ID-debraj1247-34494-1460618050527-0-5}{camel.routeId,route8}{reqId,fc652d13-8d81-4993-be88-89e93d93d7ef}{tId,5710da8e-abff--b609-852c9d1118df}}
| Opening connection {s}->https://example.com:443
2016-04-14T12:44:18.470+0530 | DEBUG | qtp1202042637-19 |
aultHttpClientConnectionOperator |  -  -  |
{{camel.breadcrumbId,ID-debraj1247-34494-1460618050527-0-5}{camel.contextId,camel-1}{camel.exchangeId,ID-debraj1247-34494-1460618050527-0-6}{camel.messageId,ID-debraj1247-34494-1460618050527-0-5}{camel.routeId,route8}{reqId,fc652d13-8d81-4993-be88-89e93d93d7ef}{tId,5710da8e-abff--b609-852c9d1118df}}
| Connecting to example.com/54.169.255.232:443
2016-04-14T12:44:18.471+0530 | DEBUG | qtp1202042637-19 |
SSLConnectionSocketFactory   |  -  -  |
{{camel.breadcrumbId,ID-debraj1247-34494-1460618050527-0-5}{camel.contextId,camel-1}{camel.exchangeId,ID-debraj1247-34494-1460618050527-0-6}{camel.messageId,ID-debraj1247-34494-1460618050527-0-5}{camel.routeId,route8}{reqId,fc652d13-8d81-4993-be88-89e93d93d7ef}{tId,5710da8e-abff--b609-852c9d1118df}}
| Connecting socket to example.com/54.169.255.232:443 with timeout 0
2016-04-14T12:44:18.572+0530 | DEBUG | qtp1202042637-19 |
SSLConnectionSocketFactory   |  -  -  |
{{camel.breadcrumbId,ID-debraj1247-34494-1460618050527-0-5}{camel.contextId,camel-1}{camel.exchangeId,ID-debraj1247-3449

Re: Clarification on how Converters work with CDI

[Antonin Stefanutti]

> On 13 Apr 2016, at 14:08, Anton  wrote:
> 
> On Wed, Apr 13, 2016 at 1:58 PM, John D. Ament 
> wrote:
> 
>> The JPA component doesn't do any type conversion (based on code
>> inspection).  It assumes the object coming in is the right type.  Good
>> catch on adding the converter to the body.
>> 
> 
> Thanks John
> 
> I think it would be good to have some consistency in regards to whether
> components do conversion or not.
> 
> What is the best way to know if a component supports implicit type
> conversion?

I’d said the documentation ATM. The JPA component doc mentions type conversion 
for the producer but not for the consumer. That being said, I agree it’d be 
better to have a way to have type conversion consistently applied.

Antonin

Camel scheduler is not concurrent

[cookie]

Hi.

   According to the camel scheduler documentation it is possible to
configure its threadpool to support more than one thread at a time.
According to the following  commit

  
the option for it is "concurrentTasks=".

However when I apply this option and use the debugger I see that the
configured number of threads are created but the scheduler always uses one
thread only, i.e. if I set a breakpoint in the corresponding bean method and
thus make the thread wait until after the next polling interval has reached,
I expect another thread to get activated and call the bean method but this
does not happen. Actually the additional threads NEVER get invoked, they are
just created. 

So one of my questions is: what is the intention behind concurrent tasks in
the scheduler?

Also, is it possible to achieve the desired behavior using camel scheduler
or any other component?

Thank you in advance  





--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-scheduler-is-not-concurrent-tp5781066.html
Sent from the Camel - Users mailing list archive at Nabble.com.

RE: camel-spring-boot + @UseAdviceWith

[David Bennison]

Hi,

Have you got any further with this? I am suffering from the same problem.


From: Jeff Segal 
Sent: 12 April 2016 16:46
To: users@camel.apache.org
Subject: camel-spring-boot + @UseAdviceWith

All,

I'm currently creating a camel-spring-boot project and would like to add
some tests using @UseAdviceWith but am hitting a few issues. I couldn't
find an example that fit that use case exactly, so I've played around with
different things to no avail.

Specifically, I found that when I use @ContextConfiguration to specify my
main Spring app config, my use of
@BootstrapWith(CamelTestContextBootstrapper.class) is honored (i.e. I can
step through it in a debugger during startup) and I can see @UseAdviceWith
being used in CamelSpringTestContextLoader.handleCamelContextStartup().
However, when I @Autowire my CamelContext into my test class, Spring
startup fails because it can't find my CamelContext Spring bean (even when
I explicitly include a @Configuration that extends CamelConfiguration,
which explicitly creates a CamelContext @Bean). I need a reference to my
CamelContext so that I can start it once I'm done setting up my routeWith
advice.

One last thing: when I use @SpringApplicationConfiguration instead of
@ContextConfiguration, Spring is able to find the CamelContext bean but it
ignores my @BootstrapWith(CamelTestContextBootstrapper.class) &
@UseAdviceWith and thus just starts up the CamelContext automatically
rather than waiting for me to start it manually (after my routeWith
advice).

Any pointers on what I might be doing wrong would be great. In summary:

Honoring @UseAdviceWith but no CamelContext Spring bean:

@ContextConfiguration(classes = {ApplicationConfig.class})
@RunWith(CamelSpringJUnit4ClassRunner.class)
@BootstrapWith(CamelTestContextBootstrapper.class)
@UseAdviceWith
@Slf4j
public class MyTest {

@Autowired
CamelContext camelContext;

@Test
public void test() throws InterruptedException {
log.info("Starting test...");
Thread.sleep(1000 * 60);
}

}

Have a CamelContext Spring bean but NOT honoring @UseAdviceWith:

@SpringApplicationConfiguration(classes = {ApplicationConfig.class})
@RunWith(CamelSpringJUnit4ClassRunner.class)
@BootstrapWith(CamelTestContextBootstrapper.class)
@UseAdviceWith
@Slf4j
public class MyTest {

@Autowired
CamelContext camelContext;

@Test
public void test() throws InterruptedException {
log.info("Starting test...");
Thread.sleep(1000 * 60);
}

}

Thanks!
Jeff
This email is confidential and may be privileged. If you are not the intended 
recipient, please notify the sender immediately and delete the email from your 
computer. You should not copy the email, use it for any purpose or disclose its 
contents to any other person. Please note that any views or opinions presented 
in this email may be personal to the author and do not necessarily represent 
the views or opinions of MetaPack. It is the responsibility of the recipient to 
check this email for the presence of viruses. MetaPack accepts no liability for 
any damage caused by any virus transmitted by this email. MetaPack Registered 
Office: 4th Floor, 200 Gray’s Inn Road London WC1X 8XZ. Registered in England 
No. 03870530. VAT No 945 7723 86.

Re: PDF/A files using Camel FOP component

[Laurentiu Trica]

Hi Bilgin,

Thank you, sorry for the late response.
I tried your update and it seems to work, but now I get this error:

javax.xml.transform.TransformerException:
org.apache.fop.pdf.PDFConformanceException: For PDF/A-1b, all fonts, even
the base 14 fonts, have to be embedded! Offending font: /Helvetica
at
com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:749)[:1.7.0_95]
at
com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:353)[:1.7.0_95]
at
de.edigrid.util.fop.FopProducer.transform(FopProducer.java:89)[520:org.apache.camel.camel-fop:2.13.2]
at
de.edigrid.util.fop.FopProducer.process(FopProducer.java:64)[520:org.apache.camel.camel-fop:2.13.2]
at
org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)[84:org.apache.camel.camel-core:2.14.1]
at
org.apache.camel.processor.SendProcessor.process(SendProcessor.java:120)[84:org.apache.camel.camel-core:2.14.1]
at
org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:72)[84:org.apache.camel.camel-core:2.14.1]
at
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:416)[84:org.apache.camel.camel-core:2.14.1]
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191)[84:org.apache.camel.camel-core:2.14.1]
at
org.apache.camel.processor.Pipeline.process(Pipeline.java:118)[84:org.apache.camel.camel-core:2.14.1]
at
org.apache.camel.processor.Pipeline.process(Pipeline.java:80)[84:org.apache.camel.camel-core:2.14.1]
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191)[84:org.apache.camel.camel-core:2.14.1]
at
org.apache.camel.component.file.GenericFileConsumer.processExchange(GenericFileConsumer.java:433)[84:org.apache.camel.camel-core:2.14.1]
at
org.apache.camel.component.file.GenericFileConsumer.processBatch(GenericFileConsumer.java:211)[84:org.apache.camel.camel-core:2.14.1]
at
org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:175)[84:org.apache.camel.camel-core:2.14.1]
at
org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:187)[84:org.apache.camel.camel-core:2.14.1]
at
org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:114)[84:org.apache.camel.camel-core:2.14.1]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)[:1.7.0_95]
at
java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)[:1.7.0_95]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)[:1.7.0_95]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)[:1.7.0_95]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[:1.7.0_95]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.7.0_95]
at java.lang.Thread.run(Thread.java:745)[:1.7.0_95]
Caused by: org.apache.fop.pdf.PDFConformanceException: For PDF/A-1b, all
fonts, even the base 14 fonts, have to be embedded! Offending font:
/Helvetica
at
org.apache.fop.pdf.PDFFont.validate(PDFFont.java:169)[515:org.apache.servicemix.bundles.fop:1.1.0.1]
at
org.apache.fop.pdf.PDFFont.output(PDFFont.java:178)[515:org.apache.servicemix.bundles.fop:1.1.0.1]
at
org.apache.fop.pdf.PDFDocument.outputIndirectObject(PDFDocument.java:951)[515:org.apache.servicemix.bundles.fop:1.1.0.1]
at
org.apache.fop.pdf.PDFDocument.streamIndirectObject(PDFDocument.java:918)[515:org.apache.servicemix.bundles.fop:1.1.0.1]
at
org.apache.fop.pdf.PDFDocument.output(PDFDocument.java:912)[515:org.apache.servicemix.bundles.fop:1.1.0.1]
at
org.apache.fop.pdf.PDFDocument.outputTrailer(PDFDocument.java:995)[515:org.apache.servicemix.bundles.fop:1.1.0.1]
at
org.apache.fop.render.pdf.PDFDocumentHandler.endDocument(PDFDocumentHandler.java:172)[515:org.apache.servicemix.bundles.fop:1.1.0.1]
at
org.apache.fop.render.intermediate.util.IFDocumentHandlerProxy.endDocument(IFDocumentHandlerProxy.java:192)[515:org.apache.servicemix.bundles.fop:1.1.0.1]
at
org.apache.fop.render.intermediate.IFRenderer.stopRenderer(IFRenderer.java:296)[515:org.apache.servicemix.bundles.fop:1.1.0.1]
at
org.apache.fop.area.RenderPagesModel.endDocument(RenderPagesModel.java:265)[515:org.apache.servicemix.bundles.fop:1.1.0.1]
at
org.apache.fop.area.AreaTreeHandler.endDocument(AreaTreeHandler.java:342)[515:org.apache.servicemix.bundles.fop:1.1.0.1]
at
org.apache.fop.fo.FOTreeBuilder.endDocument(FOTreeBuilder.java:168)[515:org.apache.servicemix.bundles.fop:1.1.0.1]
at
com.sun.org.apache.xml.internal.serializer.ToXMLSAXHandler.endDocument(ToXMLSAXHandler.java:185)[:1.7.0_95]
at org.apache.xerces.parsers.AbstractSAXParser.endDocument(Unknown
Source)[:]
at org.apache.xerces.impl.XMLDocumentScannerImpl.endEntity(Unknown
Source)[:]
at org.apache.xerces.impl.