Yeah I also searched for a difference between the two configurations! But could 
not find anything. One difference was the Java versions, 5 and 6. But it don't 
work with both of them on the working machine. Another differnce is Win 2000 vs 
Win XP on the testmachine but that don't have to be a problem I think. Another 
thing is that the testmachine is a lot faster, more RAM and 2 cores.

The strange thing is that I copied the entire Tomcat folder from my machine to 
the testmachien (to the same location) and also copied the used databases. But 
then the problems still exists.

I remember now something that could be usefull to. When the error comes up, in 
the message exchange table a UKNOWN_ENDPOINT status is set to the message. But 
after some time (more than half a hour) when I restarted tomcat, some of the 
UKNOWN_ENDPOINT's were processed. Not all. That happend to me some times..

I'm not at work at the moment but I think we used (on both machines because 
they are copies):
ode-axis2.db.mode=EXTERNAL
ode-axis2.db.ext.dataSource=java:comp/env/jdbc/OdeDS

And OdeDS is configured in Tomcat 5.5.23.

At the moment I'm thinking of a timing problem or something. But I find it very 
strange!
I have a database dump (SQL) with 3 processes deployed, but only with one 
process instance. And that process instances failed with the error. Maybe you 
can do something with that?

Thanks!
   Rene

-----Oorspronkelijk bericht-----
Van: [EMAIL PROTECTED] namens Matthieu Riou
Verzonden: vr 14-12-2007 18:14
Aan: [email protected]
Onderwerp: Re: INTERNAL ERROR: No ENTRY for RESPONSE CHANNEL 69
 
Sounds to me like a transaction manager problem, when channels can't be
found it's usually a missing commit somewhere. Since it works on your
machine and not on the others, and also that problems with unfound channels
usually don't happen on normal configuration, I'd lean toward a
configuration problem. Which leads me to the questions: what is the
difference between you configuration and the configuration on your test
machine? Postgres? Are you running in internal, embedded or external mode?

Thanks,
Matthieu

On Dec 14, 2007 8:12 AM, René Bos <[EMAIL PROTECTED]> wrote:

>  Hello!
>
>
>
> I have a problem with two of my processes. I'm running Ode 1.1 with a
> PostgreSQL database. I attached one of the processes so you can see the BPEL
> code. I attached also the error.
>
>
>
> The error appears sometimes when I do the following calls:
>
> Initiate
>
> saveOrAanbieden with completionValue save
>
> saveOrAanbieden with completionValue aanbieden
>
>
>
> Or when I do:
>
> Initiate
>
> saveOrAanbieden with completionValue aanbieden
>
> approveOrDisapprove with completionValue disapprove
>
> saveOrAanbieden with completionValue aanbieden or save
>
>
>
> The strange thing is the problem does not exists on my local workstation,
> but it does on another testing machine!
>
> On the testing machine it sometimes does show up, other times not.
>
>
>
> Can you tell me if something is fixed in this area? Or can you help me by
> checking my process/reproduce it..
>
>
>
> Rene
>

Reply via email to