[prev in list] [next in list] [prev in thread] [next in thread] 

List:       bricolage-devel
Subject:    Re: SOAP TimeOut again...
From:       Pedro_Custódio <pecus () co ! sapo ! pt>
Date:       2007-01-17 17:22:27
Message-ID: 67FCE319-C05C-42E8-AC57-C993EB7F397B () co ! sapo ! pt
[Download RAW message or body]

Well,

i guess they somehow have messed up with the database. I've re- 
initialized the bric db, and everything is back online.
By the looks of it, the fault happened when they exported the  
elements and configs from the devel environment and brought them to  
production, but I still have to take a closer look at this..
:(

Thanks anyway for the help.
Pedro

On Jan 16, 2007, at 6:16 PM, David E. Wheeler wrote:

> On Jan 16, 2007, at 9:47 AM, Pedro Custódio wrote:
>
>> we get into timeout trouble land:
>>
>> 	TRANSPORT ERROR: 500 Server closed connection without sending any  
>> data back
>> 	Check the Apache error log for more information.
>>
>>
>> worst part? Nothing on the error log... just a kick entry on the  
>> access log:
>>
>> 	...
>> 	127.0.0.1 - - [16/Jan/2007:17:45:17 +0000] "POST /soap HTTP/1.1"  
>> 200 491 "-" "SOAP::Lite/Perl/0.69" "-" "_default_:80"
>>
>> Any clues?
>> Could if be an installations issue?
>> At this point any suggestion is more than welcome...
>
> That is odd. I have no idea…does it happen if you constrain the  
> call to list_ids() so that it returns fewer stories?
>
> Best,
>
> David


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic