Hi, i

RE:

1. Does any body have the same problem?

2. have any body found a solution?

3. what was that solution?

1. Yes, possibly - see thread called POST limits

2. not really, more a kind of workaround, which seems to reduce the amount of times the error occurs

3. see thread called POST limits - If you run Lasso I will tell you more but if you don't there aint much point.

Just out of interest what setup do you run - is it Mac? If it is I might be starting to get some ideas of where to look for this problem .... I will let u know

thank u very much,

Yes, I

Just sent an OTSessionWatcher dump to FMPro bug reporting.

It is hard to decipher exactly which request is coming from where cos it's from the development server which has everything piled on the same box using FMRemote. I didn't want to stick this on the live servers for obvious reasons but I may have to because it will be easier to see where it is going wrong.

The data has been parsed by Lasso into WC friendly syntax and passed to FMPro. It seems as though the connection is made between Lasso and WC the connection is released then it all goes wrong inside FMPro

anyways if anyone can talk open transport here is the point at which it goes tits up. (I have cut 99% of the session off) comments in bold are what i think is happening I could of course be completely wrong

Send orderly release request (T_ORDREL_REQ = 109) on stream 230.

Receive orderly release indication (T_ORDREL_IND = 132) on stream 244.

Lasso disconnected

Receive data (6446 bytes) on stream 230.

Last of the data from Lasso is recieved at WC (I cut it cos its 6446 bytes of meaningless test data)

Send disconnect request (T_DISCON_REQ = 105) on stream 230.

Sequence Number = 0

Receive disconnect indication (T_DISCON_IND = 126) on stream 244.

Reason = 54

Sequence Number = 0

Send unbind request (T_UNBIND_REQ = 110) on stream 230.

DOH!

Receive error ack (T_ERROR_ACK = 127)

const T_DATA_IND = 128;

on stream 230.

Primitive Error = 110

TLI Error = 6

Unix Error = 0

Hopefully someone at Filemaker in CA will have a better idea, if their help line in UK is anything to go by though ..... they really have no idea about what us web guys are doing with their product ...... which quite frankly stinks ...

Ironically I tried to send them the whole Open transport session - it was too much data for their sever in a single post and it returned an internal error

thanks scratch.....

Now i

I can solve my problem with FMPro 5.5v2 and WC v3 (I am currently running WC 5.0v6)

Since you are using OSX you are running 5.5 already - Make sure you have WC 5.5v3 otherwise your problem must originate from somewhere else.

RE: Hopefully someone at Filemaker in CA will have a better idea, if their help line in UK is anything to go by though ..... they really have no idea about what us web guys are doing with their product ...... which quite frankly stinks ...

Filemaker UK support have redeemed themselves... they called back and have been very helpful