You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@esme.apache.org by Richard Hirsch <hi...@gmail.com> on 2010/02/25 19:12:15 UTC
"Mailto" Action Showstopper
Right now, we have a showstopper when a user uses a "mailto" action.
For some reason, it kills the server.
Could somebody (@vassil?) take a look at this. We've "killed "our Stax
server twice now and since that server is being used by various
partners / testers. It is a real problem.
There is already a JIRA item covering this issue:
http://issues.apache.org/jira/browse/ESME-162
I've looked at the problem but didn't see anything....
Thanks.
D.
Re: "Mailto" Action Showstopper
Posted by Richard Hirsch <hi...@gmail.com>.
Thanks.
D.
On Sun, Feb 28, 2010 at 3:56 PM, Vassil Dichev <vd...@apache.org> wrote:
> The mailto action is fixed and should work now. I'm wondering whether
> the definition of EOL has changed in the Lift parser helpers, but I
> don't have time to check the history right now.
>
>
> On Fri, Feb 26, 2010 at 9:15 AM, Richard Hirsch <hi...@gmail.com> wrote:
>> On Fri, Feb 26, 2010 at 6:08 AM, Vassil Dichev <vd...@apache.org> wrote:
>>> Unfortunately I couldn't find why exactly the mailto action
>>> configuration breaks.
>>>
>>> What I have found is that when trying to define the mailto action, the
>>> CPU gets stuck in the parser, which is weird, because as Dick said, it
>>
>> . Where does it get stuck? I'd look at the SVN change history to find
>> out what has changed.
>>
>>> used to work. It is reproducible both locally and on the Stax instance
>>> (which I probably crashed one more time).
>>
>> Can you delete or deactivate the mailto action. I don't have access to
>> the DB from work.
>>>
>>> Does anyone remember when they have last configured a "mailto" action
>>> successfully?
>>
>> A while ago
>>
>>>
>>>
>>> On Thu, Feb 25, 2010 at 8:46 PM, Richard Hirsch <hi...@gmail.com> wrote:
>>>> It has happened twice on the Stax environment. Just add a mailto
>>>> action, trigger it and the CPU shoots up and the server freezes. I
>>>> don't remember seeing anything in the logs.
>>>>
>>>> What is stange is that it used to work.
>>>>
>>>> D.
>>>>
>>>> On Thu, Feb 25, 2010 at 7:40 PM, Vassil Dichev <vd...@apache.org> wrote:
>>>>> Oops, any error messages/stack traces? Is it reproducible locally?
>>>>>
>>>>>
>>>>> On Thu, Feb 25, 2010 at 8:12 PM, Richard Hirsch <hi...@gmail.com> wrote:
>>>>>>
>>>>>> Right now, we have a showstopper when a user uses a "mailto" action.
>>>>>> For some reason, it kills the server.
>>>>>>
>>>>>> Could somebody (@vassil?) take a look at this. We've "killed "our Stax
>>>>>> server twice now and since that server is being used by various
>>>>>> partners / testers. It is a real problem.
>>>>>>
>>>>>> There is already a JIRA item covering this issue:
>>>>>> http://issues.apache.org/jira/browse/ESME-162
>>>>>>
>>>>>> I've looked at the problem but didn't see anything....
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> D.
>>>>>
>>>>
>>>
>>
>
Re: "Mailto" Action Showstopper
Posted by Vassil Dichev <vd...@apache.org>.
The mailto action is fixed and should work now. I'm wondering whether
the definition of EOL has changed in the Lift parser helpers, but I
don't have time to check the history right now.
On Fri, Feb 26, 2010 at 9:15 AM, Richard Hirsch <hi...@gmail.com> wrote:
> On Fri, Feb 26, 2010 at 6:08 AM, Vassil Dichev <vd...@apache.org> wrote:
>> Unfortunately I couldn't find why exactly the mailto action
>> configuration breaks.
>>
>> What I have found is that when trying to define the mailto action, the
>> CPU gets stuck in the parser, which is weird, because as Dick said, it
>
> . Where does it get stuck? I'd look at the SVN change history to find
> out what has changed.
>
>> used to work. It is reproducible both locally and on the Stax instance
>> (which I probably crashed one more time).
>
> Can you delete or deactivate the mailto action. I don't have access to
> the DB from work.
>>
>> Does anyone remember when they have last configured a "mailto" action
>> successfully?
>
> A while ago
>
>>
>>
>> On Thu, Feb 25, 2010 at 8:46 PM, Richard Hirsch <hi...@gmail.com> wrote:
>>> It has happened twice on the Stax environment. Just add a mailto
>>> action, trigger it and the CPU shoots up and the server freezes. I
>>> don't remember seeing anything in the logs.
>>>
>>> What is stange is that it used to work.
>>>
>>> D.
>>>
>>> On Thu, Feb 25, 2010 at 7:40 PM, Vassil Dichev <vd...@apache.org> wrote:
>>>> Oops, any error messages/stack traces? Is it reproducible locally?
>>>>
>>>>
>>>> On Thu, Feb 25, 2010 at 8:12 PM, Richard Hirsch <hi...@gmail.com> wrote:
>>>>>
>>>>> Right now, we have a showstopper when a user uses a "mailto" action.
>>>>> For some reason, it kills the server.
>>>>>
>>>>> Could somebody (@vassil?) take a look at this. We've "killed "our Stax
>>>>> server twice now and since that server is being used by various
>>>>> partners / testers. It is a real problem.
>>>>>
>>>>> There is already a JIRA item covering this issue:
>>>>> http://issues.apache.org/jira/browse/ESME-162
>>>>>
>>>>> I've looked at the problem but didn't see anything....
>>>>>
>>>>> Thanks.
>>>>>
>>>>> D.
>>>>
>>>
>>
>
Re: "Mailto" Action Showstopper
Posted by Richard Hirsch <hi...@gmail.com>.
On Fri, Feb 26, 2010 at 6:08 AM, Vassil Dichev <vd...@apache.org> wrote:
> Unfortunately I couldn't find why exactly the mailto action
> configuration breaks.
>
> What I have found is that when trying to define the mailto action, the
> CPU gets stuck in the parser, which is weird, because as Dick said, it
. Where does it get stuck? I'd look at the SVN change history to find
out what has changed.
> used to work. It is reproducible both locally and on the Stax instance
> (which I probably crashed one more time).
Can you delete or deactivate the mailto action. I don't have access to
the DB from work.
>
> Does anyone remember when they have last configured a "mailto" action
> successfully?
A while ago
>
>
> On Thu, Feb 25, 2010 at 8:46 PM, Richard Hirsch <hi...@gmail.com> wrote:
>> It has happened twice on the Stax environment. Just add a mailto
>> action, trigger it and the CPU shoots up and the server freezes. I
>> don't remember seeing anything in the logs.
>>
>> What is stange is that it used to work.
>>
>> D.
>>
>> On Thu, Feb 25, 2010 at 7:40 PM, Vassil Dichev <vd...@apache.org> wrote:
>>> Oops, any error messages/stack traces? Is it reproducible locally?
>>>
>>>
>>> On Thu, Feb 25, 2010 at 8:12 PM, Richard Hirsch <hi...@gmail.com> wrote:
>>>>
>>>> Right now, we have a showstopper when a user uses a "mailto" action.
>>>> For some reason, it kills the server.
>>>>
>>>> Could somebody (@vassil?) take a look at this. We've "killed "our Stax
>>>> server twice now and since that server is being used by various
>>>> partners / testers. It is a real problem.
>>>>
>>>> There is already a JIRA item covering this issue:
>>>> http://issues.apache.org/jira/browse/ESME-162
>>>>
>>>> I've looked at the problem but didn't see anything....
>>>>
>>>> Thanks.
>>>>
>>>> D.
>>>
>>
>
Re: "Mailto" Action Showstopper
Posted by Vassil Dichev <vd...@apache.org>.
Unfortunately I couldn't find why exactly the mailto action
configuration breaks.
What I have found is that when trying to define the mailto action, the
CPU gets stuck in the parser, which is weird, because as Dick said, it
used to work. It is reproducible both locally and on the Stax instance
(which I probably crashed one more time).
Does anyone remember when they have last configured a "mailto" action
successfully?
On Thu, Feb 25, 2010 at 8:46 PM, Richard Hirsch <hi...@gmail.com> wrote:
> It has happened twice on the Stax environment. Just add a mailto
> action, trigger it and the CPU shoots up and the server freezes. I
> don't remember seeing anything in the logs.
>
> What is stange is that it used to work.
>
> D.
>
> On Thu, Feb 25, 2010 at 7:40 PM, Vassil Dichev <vd...@apache.org> wrote:
>> Oops, any error messages/stack traces? Is it reproducible locally?
>>
>>
>> On Thu, Feb 25, 2010 at 8:12 PM, Richard Hirsch <hi...@gmail.com> wrote:
>>>
>>> Right now, we have a showstopper when a user uses a "mailto" action.
>>> For some reason, it kills the server.
>>>
>>> Could somebody (@vassil?) take a look at this. We've "killed "our Stax
>>> server twice now and since that server is being used by various
>>> partners / testers. It is a real problem.
>>>
>>> There is already a JIRA item covering this issue:
>>> http://issues.apache.org/jira/browse/ESME-162
>>>
>>> I've looked at the problem but didn't see anything....
>>>
>>> Thanks.
>>>
>>> D.
>>
>
Re: "Mailto" Action Showstopper
Posted by Richard Hirsch <hi...@gmail.com>.
It has happened twice on the Stax environment. Just add a mailto
action, trigger it and the CPU shoots up and the server freezes. I
don't remember seeing anything in the logs.
What is stange is that it used to work.
D.
On Thu, Feb 25, 2010 at 7:40 PM, Vassil Dichev <vd...@apache.org> wrote:
> Oops, any error messages/stack traces? Is it reproducible locally?
>
>
> On Thu, Feb 25, 2010 at 8:12 PM, Richard Hirsch <hi...@gmail.com> wrote:
>>
>> Right now, we have a showstopper when a user uses a "mailto" action.
>> For some reason, it kills the server.
>>
>> Could somebody (@vassil?) take a look at this. We've "killed "our Stax
>> server twice now and since that server is being used by various
>> partners / testers. It is a real problem.
>>
>> There is already a JIRA item covering this issue:
>> http://issues.apache.org/jira/browse/ESME-162
>>
>> I've looked at the problem but didn't see anything....
>>
>> Thanks.
>>
>> D.
>
Re: "Mailto" Action Showstopper
Posted by Vassil Dichev <vd...@apache.org>.
Oops, any error messages/stack traces? Is it reproducible locally?
On Thu, Feb 25, 2010 at 8:12 PM, Richard Hirsch <hi...@gmail.com> wrote:
>
> Right now, we have a showstopper when a user uses a "mailto" action.
> For some reason, it kills the server.
>
> Could somebody (@vassil?) take a look at this. We've "killed "our Stax
> server twice now and since that server is being used by various
> partners / testers. It is a real problem.
>
> There is already a JIRA item covering this issue:
> http://issues.apache.org/jira/browse/ESME-162
>
> I've looked at the problem but didn't see anything....
>
> Thanks.
>
> D.