On Sat, Jan 26, 2013 at 3:43 AM, Claus Ibsen <claus.ib...@gmail.com> wrote:
> On Fri, Jan 25, 2013 at 9:55 PM, Chris Wolf <cwolf.a...@gmail.com> wrote:
>> I ask because when I use jpa: in producer mode, I get this error:
>> Caused by: oracle.net.ns.NetException: Listener refused the connection
>> with the following error:
>> ORA-12519, TNS:no appropriate service handler found
>>
>> Strangely, using jpa: in consumer mode, this does not happen. In the
>> tnslsnr.log, I observe 120 connections being opened when
>> running the route with jpa: in producer mode. If I instead use a
>> custom Processor and do my own JPA persistence code,
>> the issue does not occur.
>>
>> Thanks for any advice,
>>
>
> To answer your subject of this mail thread.
>
> No camel-jpa does not have its own connection pooling etc.
> You need to configure this outside Camel, eg as you would normally do with
> JPA.
>
Thanks, I created a standalone JPA program and reproduced the issue
"ORA-12519" and, by tailing TNS listener log, saw that the number of
connections was exhausted, thus the cause of ORA-12519.
Very strange since I don't have any connection pool configured...
well, I demonstrated it's not a Camel issue, so I posted on the
OpenJPA list. Thanks for getting back to me.
-Chris
