This is definitely something in how the mid-tier handles web services
against the join form. I was hoping that I couldn't be the only one that
has experienced this and was hoping someone might chime in with a golden
egg. ;-)
Terry
On 2015-01-06 12:17, laurent matheo wrote:
> ** Hi :)
>
>
Hi :)
I guess you could log and compare and check where the time is consumed when
using the WS.
If API + SQL calls are the same, then it’s « elsewhere ».
> Le 6 janv. 2015 à 18:15, Terry Bootsma a écrit :
>
> **
> For further information:
>
> Remedy User Tool against the join form: < 1 seco
Okso, have you turned on API/SQL/Filter logging into a single file and
isolated the transaction to determine where the time is going?
On Tue, Jan 6, 2015 at 10:15 AM, Terry Bootsma
wrote:
> **
>
> For further information:
>
> Remedy User Tool against the join form: < 1 second
>
> MidTier di
Terry,
Do you experience similar delay when pulling the same 2000 records directly
from the user/web tool, or only when done through web services?
Are the fields used in the qualification of the join indexed properly?
On Tue, Jan 6, 2015 at 10:12 AM, Terry Bootsma
wrote:
> **
>
> Hello everyone
For further information:
Remedy User Tool against the join form: < 1 second
MidTier direct access against the join form: < 5 seconds
So, it is not a join-form or indexing issue.
Terry
On 2015-01-06 12:12, tboot...@objectpath.com wrote:
> Hello everyone:
>
> I was wondering if anyon
Hello everyone:
I was wondering if anyone else has experienced this.
Environment:
Red Hat Linux 6.4
Mid Tier 8.1.01 SP1 20140514135 Hotfix
Apache Tomcat 6.0
Remedy Server 8.1.01 201401281910
Oracle Database
When consuming web services that are based on "join" forms in Remedy, we
have exp
6 matches
Mail list logo