at
>> >> >>> >>>>
>> >> >>>
>> >>
>>
>>org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProce
>>ssorBridge.process(AsyncProcessorConverterHelper.java:61)
>> >> >>> >>>>
>>> >>>> at
> >> >>> >>>>
> >> >>>
> >>
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:398)
> >> >>> >>>> at
> >> >>> >
he.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:398)
>>> >>> >>>> at
>>> >>> >>>>
>>> >>>
>>> org.apache.camel.processor.CamelInternalProcessor.process(Ca
)
>> >>> >>>> at
>> >>> >>>>
>> >>>
>> org.apache.camel.component.direct.DirectProducer.process(DirectProducer.java:56)
>> >>> >>>> at
>> >>> >>>>
>> >>>
&
;>>> at
> >>> >>>>
> >>>
> org.apache.camel.impl.ProducerCache$2.doInProducer(ProducerCache.java:1)
> >>> >>>> at
> >>> >>>>
> >>>
> org.apache.camel.impl.
t;>
>>> org.apache.camel.impl.DefaultProducerTemplate.send(DefaultProducerTemplate.java:124)
>>> >>>> at
>>> >>>>
>>> org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:137)
>&g
Thread.java:680)
>> >>>> Caused by:
>> >>>>
>> >
>
>> >>>> org.apache.openjpa.persistence.InvalidStateException: This operation
>> >>>> cannot
>> >>>> be performed while a Transaction is acti
;>> cannot
> >>>> be performed while a Transaction is active.
> >>>> at
> org.apache.openjpa.kernel.BrokerImpl.begin(BrokerImpl.java:1369)
> >>>> at
> >>>>
> org.apache.openjpa.kernel.DelegatingBroker.begin(Delegat
r$ExtendedEntityManagerInvocationHandler.doJoinTransaction(ExtendedEntityManagerCreator.java:399)
>>>> at
>>>> org.springframework.orm.jpa.ExtendedEntityManagerCreator$ExtendedEntityManagerInvocationHandler.invoke(ExtendedEntityManagerCreator.java:351)
>>&g
g.apache.camel.component.jpa.JpaProducer$1.doInTransaction(JpaProducer.java:55)
>>> at
>>> org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:131)
>>> ... 27 more
>>>
>>> which is throwing from the line
>> whether the issue is in Camel, Spring, OpenJPA, ...). Will open a JIRA
>> for
>> it.
>>
>> [1] https://builds.apache.org/job/Camel.trunk.fulltest/1562/
>>
>> Best,
>>
>> Christian
>> -
>>
>> Software Integration Specialist
>>
>> Apache Member
>> V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
>> Apache Incubator PMC Member
>>
>> https://www.linkedin.com/pub/christian-mueller/11/551/642
>>
>>
>> On Thu, Oct 10, 2013 at 12:28 PM, James Carman
>> <
>> james@
>> >wrote:
>>
>>> There are quite a few broken tests. Jetty seems to be hosed. JPA has a
>>> failed test. CDI has issues. It looks like JMS and FTP even decided to
>>> join the party. This has been going on for a while now. This
>>> particular
>>> job hasn't been "green" since 9/29. Should we stop working other issues
>>> and get ourselves whole again?
>>>
>>> https://builds.apache.org/job/Camel.trunk.fulltest/1561/
>>>
--
View this message in context:
http://camel.465427.n5.nabble.com/Build-failures-tp5741273p5741403.html
Sent from the Camel Development mailing list archive at Nabble.com.
on Specialist
>
> Apache Member
> V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
> Apache Incubator PMC Member
>
> https://www.linkedin.com/pub/christian-mueller/11/551/642
>
>
> On Thu, Oct 10, 2013 at 12:28 PM, James Carman
> <
> james
Today, it looks much better [1]. We are trying to fix the unit tests which
are failing from time to time on slower boxes. But this isn't so easy for
all of them...
I had a look at
org.apache.camel.processor.jpa.JpaProducerConcurrentTest.testConcurrentProducers.
A few times I get the following exce
There are quite a few broken tests. Jetty seems to be hosed. JPA has a
failed test. CDI has issues. It looks like JMS and FTP even decided to
join the party. This has been going on for a while now. This particular
job hasn't been "green" since 9/29. Should we stop working other issues
and ge
Hi,
Brett Porter from INFRA did make a comment on the ticket which made it clear
to me why we suffer from the build failures on Windows:
https://issues.apache.org/jira/browse/INFRA-4272
As these dynamic port issues happen again and again by camel-cxf that would
be great if some CXF guru could
he previous two
builds:
https://builds.apache.org/job/Camel.trunk.fulltest.windows/230/console
https://builds.apache.org/job/Camel.trunk.fulltest.windows/229/console
Babak
--
View this message in context:
http://camel.465427.n5.nabble.com/FOLLOW-UP-Recent-Build-failures-on-Windows-tp5437720p5447239
this message in context:
> http://camel.465427.n5.nabble.com/FOLLOW-UP-Recent-Build-failures-on-Windows-tp5437720p5437720.html
> Sent from the Camel Development mailing list archive at Nabble.com.
>
that?
Wish you all the Riders a nice Weekend!
Babak
--
View this message in context:
http://camel.465427.n5.nabble.com/FOLLOW-UP-Recent-Build-failures-on-Windows-tp5437720p5437720.html
Sent from the Camel Development mailing list archive at Nabble.com.
18 matches
Mail list logo
