The request failed because the PowerHouse Web Server ConnectionTimeout has expired

Fri Aug 15 12:50:33 CDT 2014

Yes. By process of elimination I determined it's this one table. It has same protection as the others.

From: Bob Deskin [mailto:bob.deskin at unicomglobal.com]
Sent: August-15-14 10:15 AM
To: Thomson, Martyn; powerh-l at lists.sowder.com
Subject: RE: The request failed because the PowerHouse Web Server ConnectionTimeout has expired

I've never heard of that error being issued other than in a timeout situation, either because the PH Web Server is taking too long or the timeout is set low and lower than the PHCGI timeout. Could be something internal that was never encountered.

However, if this only happens if there's data in a specific table then I have to be suspicious of that table. Is it possible that the ownership of that table is such that PH Web can't get at it?

Bob Deskin
PowerHouse Consultant
UNICOM Global
bob.deskin at unicomglobal.com<mailto:bob.deskin at unicomglobal.com>
(973) 526-3856

This message (including any attachments) contains confidential information that is PRIVILEGED, CONFIDENTIAL and/or ATTORNEY WORK PRODUCT and is intended only for the individual(s) named herein. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this email is strictly prohibited. If you have received this message in error, please notify the UNICOM Systems, Inc. Postmaster (postmaster at unicomsi.com<mailto:postmaster at unicomsi.com>) of the error immediately, do not read or use the email and any attachments in any manner, destroy all copies, and delete it from your system if the communication was sent via email. UNICOM Systems, Inc. (818) 838-0606 Fax: (818) 838-0776

From: Thomson, Martyn [mailto:Martyn.Thomson at hpadvancedsolutions.com]
Sent: Friday, August 15, 2014 1:00 PM
To: Bob Deskin; powerh-l at lists.sowder.com<mailto:powerh-l at lists.sowder.com>
Subject: RE: The request failed because the PowerHouse Web Server ConnectionTimeout has expired

Hi Bob.
Times out immediately. When the data is good its returned within 5 secs. The message is misleading. Its not a timeout issue.

From: Bob Deskin [mailto:bob.deskin at unicomglobal.com]
Sent: August-15-14 9:47 AM
To: Thomson, Martyn; powerh-l at lists.sowder.com<mailto:powerh-l at lists.sowder.com>
Subject: RE: The request failed because the PowerHouse Web Server ConnectionTimeout has expired

How long does it take for the message to be returned?

The PH Web Server Timeout is set in the Administrator PHWebServer Properties dialog. It is the amount of time that the Dispatcher waits for the PH Web Server to complete a task. If the task takes too long, the Dispatcher assumes that the PH Web Server has run into problems and shuts it down. The default timeout is 5 minutes. If you've lowered the value, maybe it's too low for the process you're trying to do.

Bob

Bob Deskin
PowerHouse Consultant
UNICOM Global
bob.deskin at unicomglobal.com<mailto:bob.deskin at unicomglobal.com>
(973) 526-3856

This message (including any attachments) contains confidential information that is PRIVILEGED, CONFIDENTIAL and/or ATTORNEY WORK PRODUCT and is intended only for the individual(s) named herein. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this email is strictly prohibited. If you have received this message in error, please notify the UNICOM Systems, Inc. Postmaster (postmaster at unicomsi.com<mailto:postmaster at unicomsi.com>) of the error immediately, do not read or use the email and any attachments in any manner, destroy all copies, and delete it from your system if the communication was sent via email. UNICOM Systems, Inc. (818) 838-0606 Fax: (818) 838-0776

From: powerh-l-bounces+bob.deskin=unicomglobal.com at lists.sowder.com<mailto:powerh-l-bounces+bob.deskin=unicomglobal.com at lists.sowder.com> [mailto:powerh-l-bounces+bob.deskin=unicomglobal.com at lists.sowder.com] On Behalf Of Thomson, Martyn
Sent: Friday, August 15, 2014 12:37 PM
To: powerh-l at lists.sowder.com<mailto:powerh-l at lists.sowder.com>
Subject: The request failed because the PowerHouse Web Server ConnectionTimeout has expired

Hey Listers!
I have a PH Web screen (8.40G) using a union view of several tables/views that somehow trips up the PH Web server. Here is the generalised view definition:

create view LINKAGE_UNION_VIEW
    (FLD1,
     FLD2,
     EFFECTIVE_YYMM,
     TERMINATE_YYMM,
     DB_PERCENT,
     CURRENT_FLAG) as
    select C2.FLD1, C2.FLD2, C2.EFFECTIVE_YYMM, C2.TERMINATE_YYMM,
        C2.DB_PERCENT, C2.CURRENT_FLAG
        from CURRENT_VIEW C2
    union distinct
    select C3.FLD1, C3.FLD2, C3.EFFECTIVE_YYMM, C3.TERMINATE_YYMM,
        C3.DB_PERCENT, C3.CURRENT_FLAG
        from TERMINATED_VIEW C3
    union distinct
    select C4.FLD1, C4.FLD2, C4.EFFECTIVE_YYMM, C4.TERMINATE_YYMM,
        C4.DB_PERCENT, 'C'
        from LINKAGE_1_TABLE C4
        where (C4.TERMINATE_YYMM <= '000000')
    union distinct
    select C5.FLD1, C5.FLD2, C5.EFFECTIVE_YYMM, C5.TERMINATE_YYMM,
        C5.DB_PERCENT, 'T'
        from LINKAGE_1_TABLE C5
        where (C5.TERMINATE_YYMM > '000000')
    union distinct
    select C6.FLD1, C6.FLD2, C6.EFFECTIVE_YYMM, C6.TERMINATE_YYMM,
        C6.DB_PERCENT, 'C'
        from LINKAGE_2_TABLE C6
        where (C6.TERMINATE_YYMM <= '000000')
    union distinct
    select C7.FLD1, C7.FLD2, C7.EFFECTIVE_YYMM, C7.TERMINATE_YYMM,
        C7.DB_REPORTING_PERCENT, 'T'
        from LINKAGE_2_TABLE C7
        where (C7.TERMINATE_YYMM > '000000')
    order by 2 asc, 6 asc, 1 asc;

Data is retrieved by providing a value for FLD2.
CURRENT_VIEW and TERMINATED_VIEW  are both views of a third table, differentiated on TERMINATE_YYMM.
The corresponding attributes of each table/view are the same and use the same domain definitions.
Whenever there's data originating from table LINKAGE_1_TABLE  it always gives the connection timeout error.

Things I've tried:

1.      The error has nothing to do with amount of data returned. So long as there's none from LINKAGE_1_TABLE the view works for one or hundreds of rows;

2.      changed order of tables in view definition. No effect;

3.      For a FLD2 value with no LINKAGE_2_TABLE data, moved data from table  LINKAGE_1_TABLE to LINKAGE_2_TABLE. Still get error;

4.      For a FLD2 value with no LINKAGE_1_TABLE data, moved data from table  LINKAGE_2_TABLE to LINKAGE_1_TABLE. No error;

5.      3 and 4 imply data is corrupted. Used DUMP/REC to look at LINKAGE_1_TABLE in Hex. Nothing unusual about it;

6.      This is the only PH Web screen we have using data from LINKAGE_1_TABLE;

7.      The protection on LINKAGE_1_TABLE is no different than the other tables;

8.      Same view used in QUICK, QUIZ or SQL has no problem retrieving data. Only PowerHouse Web server coughs.

Anyone seen this before? Is it because each of 3 tables is defined twice in the view?
Losing hair here! Any suggestions much appreciated.

Using PH 8.4G, OpenVMS 8.3, Oracle Rdb SQL V7.2
Regards,
Martyn Thomson
Senior Technical Analyst, Development Services
Information Technology Services
HP Advanced Solutions Inc.
phone: 250.405.4555 | fax: 250.405.4422
email:martyn.thomson at hpadvancedsolutions.com<mailto:martyn.thomson at hpadvancedsolutions.com>
web:  www.hpadvancedsolutions.com<http://www.hpadvancedsolutions.com/>

This e-mail message has been scanned and cleared by Postini / Google Message Security and the UNICOM Global security systems. This message is for the named person's use only. If you receive this message in error, please delete it and notify the sender.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sowder.com/pipermail/powerh-l/attachments/20140815/2eb92baf/attachment-0001.htm>