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/03/03 08:35:57 UTC
Strange Exception on Streams Page
We have a strange exception on the stax environment.
I've created a JIRA item for the problem:
https://issues.apache.org/jira/browse/ESME-169
Obviously, it is based on some characteristic of a particular message.
Unfortunately, I don't know which message. It appears to be coming
from a RSS twitter feed.
D.
Re: Strange Exception on Streams Page
Posted by Vassil Dichev <vd...@apache.org>.
Yes, sorry. I've closed it and put a short explanation.
On Fri, Mar 19, 2010 at 1:33 PM, Richard Hirsch <hi...@gmail.com> wrote:
> Vassil: Was this problem described in this Jira item :
> http://issues.apache.org/jira/browse/ESME-169
>
> Can we close it?
>
> D.
>
> On Wed, Mar 3, 2010 at 7:27 PM, Vassil Dichev <vd...@apache.org> wrote:
>
>> Duh, upon more careful investigation of the message it turns out that
>> the replacement string is not quoted. This means the message text must
>> contain "$1", which would normally be interpreted as the first
>> matching group.
>>
>> I've just committed the fix.
>>
>>
>> On Wed, Mar 3, 2010 at 10:25 AM, Richard Hirsch <hi...@gmail.com>
>> wrote:
>> > On Wed, Mar 3, 2010 at 9:18 AM, Vassil Dichev <vd...@apache.org>
>> wrote:
>> >>> There is already a jira item for this problem:
>> >>> http://issues.apache.org/jira/browse/ESME-152
>> >>>
>> >>> Maybe, it is the same problem.....
>> >>
>> >> Hm, there's not much detail in the issue description.
>> >>
>> >> I checked empty messages- even empty tags generate an open and closing
>> >> tag in Scala:
>> >>
>> >> http://www.simplyscala.com/interp?code=<body/>
>> >>
>> >> This means the message is not even empty, so probably some error
>> >> caused this inconsistent state.
>> >>
>> >> I'm not sure if the auto-OpenID login is related, but these should not
>> >> be possible anymore. The "Unknown" users in the DB are left over from
>> >> the time when the autologin patch was still active. Should we purge
>> >> the DB from these users? Most of the time they don't even have the
>> >> proper validated data.
>> >
>> > No problem. If the user is an old user, then it might not be cause.
>> >
>> > I'll take a look at the individual messages later and delete them 1:1
>> > to find the guilty party.
>> >
>> >>
>> >
>>
>
Re: Strange Exception on Streams Page
Posted by Richard Hirsch <hi...@gmail.com>.
Vassil: Was this problem described in this Jira item :
http://issues.apache.org/jira/browse/ESME-169
Can we close it?
D.
On Wed, Mar 3, 2010 at 7:27 PM, Vassil Dichev <vd...@apache.org> wrote:
> Duh, upon more careful investigation of the message it turns out that
> the replacement string is not quoted. This means the message text must
> contain "$1", which would normally be interpreted as the first
> matching group.
>
> I've just committed the fix.
>
>
> On Wed, Mar 3, 2010 at 10:25 AM, Richard Hirsch <hi...@gmail.com>
> wrote:
> > On Wed, Mar 3, 2010 at 9:18 AM, Vassil Dichev <vd...@apache.org>
> wrote:
> >>> There is already a jira item for this problem:
> >>> http://issues.apache.org/jira/browse/ESME-152
> >>>
> >>> Maybe, it is the same problem.....
> >>
> >> Hm, there's not much detail in the issue description.
> >>
> >> I checked empty messages- even empty tags generate an open and closing
> >> tag in Scala:
> >>
> >> http://www.simplyscala.com/interp?code=<body/>
> >>
> >> This means the message is not even empty, so probably some error
> >> caused this inconsistent state.
> >>
> >> I'm not sure if the auto-OpenID login is related, but these should not
> >> be possible anymore. The "Unknown" users in the DB are left over from
> >> the time when the autologin patch was still active. Should we purge
> >> the DB from these users? Most of the time they don't even have the
> >> proper validated data.
> >
> > No problem. If the user is an old user, then it might not be cause.
> >
> > I'll take a look at the individual messages later and delete them 1:1
> > to find the guilty party.
> >
> >>
> >
>
Re: Strange Exception on Streams Page
Posted by Vassil Dichev <vd...@apache.org>.
Duh, upon more careful investigation of the message it turns out that
the replacement string is not quoted. This means the message text must
contain "$1", which would normally be interpreted as the first
matching group.
I've just committed the fix.
On Wed, Mar 3, 2010 at 10:25 AM, Richard Hirsch <hi...@gmail.com> wrote:
> On Wed, Mar 3, 2010 at 9:18 AM, Vassil Dichev <vd...@apache.org> wrote:
>>> There is already a jira item for this problem:
>>> http://issues.apache.org/jira/browse/ESME-152
>>>
>>> Maybe, it is the same problem.....
>>
>> Hm, there's not much detail in the issue description.
>>
>> I checked empty messages- even empty tags generate an open and closing
>> tag in Scala:
>>
>> http://www.simplyscala.com/interp?code=<body/>
>>
>> This means the message is not even empty, so probably some error
>> caused this inconsistent state.
>>
>> I'm not sure if the auto-OpenID login is related, but these should not
>> be possible anymore. The "Unknown" users in the DB are left over from
>> the time when the autologin patch was still active. Should we purge
>> the DB from these users? Most of the time they don't even have the
>> proper validated data.
>
> No problem. If the user is an old user, then it might not be cause.
>
> I'll take a look at the individual messages later and delete them 1:1
> to find the guilty party.
>
>>
>
Re: Strange Exception on Streams Page
Posted by Richard Hirsch <hi...@gmail.com>.
On Wed, Mar 3, 2010 at 9:18 AM, Vassil Dichev <vd...@apache.org> wrote:
>> There is already a jira item for this problem:
>> http://issues.apache.org/jira/browse/ESME-152
>>
>> Maybe, it is the same problem.....
>
> Hm, there's not much detail in the issue description.
>
> I checked empty messages- even empty tags generate an open and closing
> tag in Scala:
>
> http://www.simplyscala.com/interp?code=<body/>
>
> This means the message is not even empty, so probably some error
> caused this inconsistent state.
>
> I'm not sure if the auto-OpenID login is related, but these should not
> be possible anymore. The "Unknown" users in the DB are left over from
> the time when the autologin patch was still active. Should we purge
> the DB from these users? Most of the time they don't even have the
> proper validated data.
No problem. If the user is an old user, then it might not be cause.
I'll take a look at the individual messages later and delete them 1:1
to find the guilty party.
>
Re: Strange Exception on Streams Page
Posted by Vassil Dichev <vd...@apache.org>.
> There is already a jira item for this problem:
> http://issues.apache.org/jira/browse/ESME-152
>
> Maybe, it is the same problem.....
Hm, there's not much detail in the issue description.
I checked empty messages- even empty tags generate an open and closing
tag in Scala:
http://www.simplyscala.com/interp?code=<body/>
This means the message is not even empty, so probably some error
caused this inconsistent state.
I'm not sure if the auto-OpenID login is related, but these should not
be possible anymore. The "Unknown" users in the DB are left over from
the time when the autologin patch was still active. Should we purge
the DB from these users? Most of the time they don't even have the
proper validated data.
Re: Strange Exception on Streams Page
Posted by Richard Hirsch <hi...@gmail.com>.
Displaying this new user also doesn't work:
http://esmecloudserverapache.dickhirsch.staxapps.net/user/https%3A%2F%2Fme.yahoo.co.jp%2Fa%2Flonvldtve_oheols4cy4fzjc1jq-%23bef9c
Maybe, it is related to the long username for users being created via openid
On Wed, Mar 3, 2010 at 9:06 AM, Richard Hirsch <hi...@gmail.com> wrote:
> On Wed, Mar 3, 2010 at 9:03 AM, Vassil Dichev <vd...@apache.org> wrote:
>> Check the users page- there is a user generated by an OpenID login,
>> which seems to have an empty message. The login URL starts with
>> https://me.yahoo.co.jp
>>
>> I'm not sure if there's an empty message because of an earlier
>> exception when posting or because the user deliberately posted an
>> empty message. At least it's not possible to post an empty message
>> through the Web UI.
>>
>> Or maybe the key is in some special Asian characters used... At any
>> rate, I'll try to make this more robust so that the error doesn't
>> occur.
>
>
> There is already a jira item for this problem:
> http://issues.apache.org/jira/browse/ESME-152
>
> Maybe, it is the same problem.....
>
>
>>
>>
>> On Wed, Mar 3, 2010 at 9:52 AM, Vassil Dichev <vd...@apache.org> wrote:
>>> Actually the problem is here:
>>>
>>> private[model] object text extends MappedText(this){
>>> override lazy val asJsExp =
>>> JE.Str(is.replaceFirst("(?<=<body>).*(?=</body>)",
>>> digestedXHTML.mkString))
>>> }
>>>
>>> But this would mean that a message has no body... or maybe an empty
>>> body? Let me check this.
>>>
>>>
>>> On Wed, Mar 3, 2010 at 9:35 AM, Richard Hirsch <hi...@gmail.com> wrote:
>>>> We have a strange exception on the stax environment.
>>>>
>>>> I've created a JIRA item for the problem:
>>>> https://issues.apache.org/jira/browse/ESME-169
>>>>
>>>> Obviously, it is based on some characteristic of a particular message.
>>>> Unfortunately, I don't know which message. It appears to be coming
>>>> from a RSS twitter feed.
>>>>
>>>> D.
>>>>
>>>
>>
>
Re: Strange Exception on Streams Page
Posted by Richard Hirsch <hi...@gmail.com>.
On Wed, Mar 3, 2010 at 9:03 AM, Vassil Dichev <vd...@apache.org> wrote:
> Check the users page- there is a user generated by an OpenID login,
> which seems to have an empty message. The login URL starts with
> https://me.yahoo.co.jp
>
> I'm not sure if there's an empty message because of an earlier
> exception when posting or because the user deliberately posted an
> empty message. At least it's not possible to post an empty message
> through the Web UI.
>
> Or maybe the key is in some special Asian characters used... At any
> rate, I'll try to make this more robust so that the error doesn't
> occur.
There is already a jira item for this problem:
http://issues.apache.org/jira/browse/ESME-152
Maybe, it is the same problem.....
>
>
> On Wed, Mar 3, 2010 at 9:52 AM, Vassil Dichev <vd...@apache.org> wrote:
>> Actually the problem is here:
>>
>> private[model] object text extends MappedText(this){
>> override lazy val asJsExp =
>> JE.Str(is.replaceFirst("(?<=<body>).*(?=</body>)",
>> digestedXHTML.mkString))
>> }
>>
>> But this would mean that a message has no body... or maybe an empty
>> body? Let me check this.
>>
>>
>> On Wed, Mar 3, 2010 at 9:35 AM, Richard Hirsch <hi...@gmail.com> wrote:
>>> We have a strange exception on the stax environment.
>>>
>>> I've created a JIRA item for the problem:
>>> https://issues.apache.org/jira/browse/ESME-169
>>>
>>> Obviously, it is based on some characteristic of a particular message.
>>> Unfortunately, I don't know which message. It appears to be coming
>>> from a RSS twitter feed.
>>>
>>> D.
>>>
>>
>
Re: Strange Exception on Streams Page
Posted by Vassil Dichev <vd...@apache.org>.
Check the users page- there is a user generated by an OpenID login,
which seems to have an empty message. The login URL starts with
https://me.yahoo.co.jp
I'm not sure if there's an empty message because of an earlier
exception when posting or because the user deliberately posted an
empty message. At least it's not possible to post an empty message
through the Web UI.
Or maybe the key is in some special Asian characters used... At any
rate, I'll try to make this more robust so that the error doesn't
occur.
On Wed, Mar 3, 2010 at 9:52 AM, Vassil Dichev <vd...@apache.org> wrote:
> Actually the problem is here:
>
> private[model] object text extends MappedText(this){
> override lazy val asJsExp =
> JE.Str(is.replaceFirst("(?<=<body>).*(?=</body>)",
> digestedXHTML.mkString))
> }
>
> But this would mean that a message has no body... or maybe an empty
> body? Let me check this.
>
>
> On Wed, Mar 3, 2010 at 9:35 AM, Richard Hirsch <hi...@gmail.com> wrote:
>> We have a strange exception on the stax environment.
>>
>> I've created a JIRA item for the problem:
>> https://issues.apache.org/jira/browse/ESME-169
>>
>> Obviously, it is based on some characteristic of a particular message.
>> Unfortunately, I don't know which message. It appears to be coming
>> from a RSS twitter feed.
>>
>> D.
>>
>
Re: Strange Exception on Streams Page
Posted by Richard Hirsch <hi...@gmail.com>.
Thanks.
The problem has happened a few times and I just erased a few messages
in DB to fix it - I thought it was a fluke.
It is important to get to the root cause of it.
D.
On Wed, Mar 3, 2010 at 8:52 AM, Vassil Dichev <vd...@apache.org> wrote:
> Actually the problem is here:
>
> private[model] object text extends MappedText(this){
> override lazy val asJsExp =
> JE.Str(is.replaceFirst("(?<=<body>).*(?=</body>)",
> digestedXHTML.mkString))
> }
>
> But this would mean that a message has no body... or maybe an empty
> body? Let me check this.
>
>
> On Wed, Mar 3, 2010 at 9:35 AM, Richard Hirsch <hi...@gmail.com> wrote:
>> We have a strange exception on the stax environment.
>>
>> I've created a JIRA item for the problem:
>> https://issues.apache.org/jira/browse/ESME-169
>>
>> Obviously, it is based on some characteristic of a particular message.
>> Unfortunately, I don't know which message. It appears to be coming
>> from a RSS twitter feed.
>>
>> D.
>>
>
Re: Strange Exception on Streams Page
Posted by Vassil Dichev <vd...@apache.org>.
Actually the problem is here:
private[model] object text extends MappedText(this){
override lazy val asJsExp =
JE.Str(is.replaceFirst("(?<=<body>).*(?=</body>)",
digestedXHTML.mkString))
}
But this would mean that a message has no body... or maybe an empty
body? Let me check this.
On Wed, Mar 3, 2010 at 9:35 AM, Richard Hirsch <hi...@gmail.com> wrote:
> We have a strange exception on the stax environment.
>
> I've created a JIRA item for the problem:
> https://issues.apache.org/jira/browse/ESME-169
>
> Obviously, it is based on some characteristic of a particular message.
> Unfortunately, I don't know which message. It appears to be coming
> from a RSS twitter feed.
>
> D.
>