Home

Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: Groupwise soap event problems

  1. #1

    Groupwise soap event problems

    I understand there was a bug in 7.0.2 and previous concerning registering
    for events. After registration and if there are other trusted applications
    also registered for the same event, but with a different key. If any events
    are deleted the events will be deleted for all keys.

    Has this been fixed in 7.0.3.Is there any bug description out there? Url.

    Another thing, we made a workaround for this bug, by using the since flag
    and keeping the events in their accounts. By default Groupwise will delete
    them after a while. I was wondering, is it possible for an account to get
    "full" of events, so after a while no more events will get added and we wont
    get notified that there is a new event?

    We are seeing on some of our systems that after registering for events (and
    getting notified), certain accounts just dont send us any notification. We
    havent been able to pinpoint yet. If any other developers are seeing the
    same issues have you found out what the cause might be?

    Any help would be appreciated.



  2. #2
    Preston Stephenson NNTP User

    Re: Groupwise soap event problems

    The problem was fixed in 7.0.3.
    I'm not sure what you mean by "Is there any bug description out there?
    Url."

    As a matter of course, you want to clean out events as soon as you can.
    We've seen problems when the events build up in the users' databases.
    Other problems can also happen. You need to look for "GWEvent" in the
    POA log files and look for errors.

    Preston

    >>> On Monday, June 02, 2008 at 8:58 AM, Martin

    Olsen<marty@lightspeedsystems.com>
    wrote:
    > I understand there was a bug in 7.0.2 and previous concerning registering


    > for events. After registration and if there are other trusted applications


    > also registered for the same event, but with a different key. If any

    events
    > are deleted the events will be deleted for all keys.
    >
    > Has this been fixed in 7.0.3.Is there any bug description out there? Url.
    >
    > Another thing, we made a workaround for this bug, by using the since flag


    > and keeping the events in their accounts. By default Groupwise will delete


    > them after a while. I was wondering, is it possible for an account to get


    > "full" of events, so after a while no more events will get added and we

    wont
    >
    > get notified that there is a new event?
    >
    > We are seeing on some of our systems that after registering for events

    (and
    > getting notified), certain accounts just dont send us any notification. We


    > havent been able to pinpoint yet. If any other developers are seeing the
    > same issues have you found out what the cause might be?
    >
    > Any help would be appreciated.


  3. #3

    Re: Groupwise soap event problems

    What I meant was could you point me to some documentation regarding this bug
    to convince our customers to upgrade to sp3.

    "Preston Stephenson" <PStephenson@gw.novell.com> wrote in message
    news:4843E465.07F1.0037.1@gw.novell.com...
    > The problem was fixed in 7.0.3.
    > I'm not sure what you mean by "Is there any bug description out there?
    > Url."
    >
    > As a matter of course, you want to clean out events as soon as you can.
    > We've seen problems when the events build up in the users' databases.
    > Other problems can also happen. You need to look for "GWEvent" in the
    > POA log files and look for errors.
    >
    > Preston
    >
    >>>> On Monday, June 02, 2008 at 8:58 AM, Martin

    > Olsen<marty@lightspeedsystems.com>
    > wrote:
    >> I understand there was a bug in 7.0.2 and previous concerning registering

    >
    >> for events. After registration and if there are other trusted
    >> applications

    >
    >> also registered for the same event, but with a different key. If any

    > events
    >> are deleted the events will be deleted for all keys.
    >>
    >> Has this been fixed in 7.0.3.Is there any bug description out there? Url.
    >>
    >> Another thing, we made a workaround for this bug, by using the since flag

    >
    >> and keeping the events in their accounts. By default Groupwise will
    >> delete

    >
    >> them after a while. I was wondering, is it possible for an account to get

    >
    >> "full" of events, so after a while no more events will get added and we

    > wont
    >>
    >> get notified that there is a new event?
    >>
    >> We are seeing on some of our systems that after registering for events

    > (and
    >> getting notified), certain accounts just dont send us any notification.
    >> We

    >
    >> havent been able to pinpoint yet. If any other developers are seeing the
    >> same issues have you found out what the cause might be?
    >>
    >> Any help would be appreciated.




  4. #4
    Preston Stephenson NNTP User

    Re: Groupwise soap event problems

    The problem is referenced in TID 3368855.
    It references the bug # 308765.
    It states that the fix was put to 7.0.3.
    Is that sufficient?

    Preston

    >>> On Monday, June 02, 2008 at 12:30 PM, Martin

    Olsen<marty@lightspeedsystems.com>
    wrote:
    > What I meant was could you point me to some documentation regarding this

    bug
    > to convince our customers to upgrade to sp3.
    >
    > "Preston Stephenson" <PStephenson@gw.novell.com> wrote in message
    > news:4843E465.07F1.0037.1@gw.novell.com...
    >> The problem was fixed in 7.0.3.
    >> I'm not sure what you mean by "Is there any bug description out there?
    >> Url."
    >>
    >> As a matter of course, you want to clean out events as soon as you can.
    >> We've seen problems when the events build up in the users' databases.
    >> Other problems can also happen. You need to look for "GWEvent" in the
    >> POA log files and look for errors.
    >>
    >> Preston
    >>
    >>>>> On Monday, June 02, 2008 at 8:58 AM, Martin

    >> Olsen<marty@lightspeedsystems.com>
    >> wrote:
    >>> I understand there was a bug in 7.0.2 and previous concerning

    registering
    >>
    >>> for events. After registration and if there are other trusted
    >>> applications

    >>
    >>> also registered for the same event, but with a different key. If any

    >> events
    >>> are deleted the events will be deleted for all keys.
    >>>
    >>> Has this been fixed in 7.0.3.Is there any bug description out there?

    Url.
    >>>
    >>> Another thing, we made a workaround for this bug, by using the since

    flag
    >>
    >>> and keeping the events in their accounts. By default Groupwise will
    >>> delete

    >>
    >>> them after a while. I was wondering, is it possible for an account to

    get
    >>
    >>> "full" of events, so after a while no more events will get added and we

    >> wont
    >>>
    >>> get notified that there is a new event?
    >>>
    >>> We are seeing on some of our systems that after registering for events

    >> (and
    >>> getting notified), certain accounts just dont send us any notification.


    >>> We

    >>
    >>> havent been able to pinpoint yet. If any other developers are seeing

    the
    >>> same issues have you found out what the cause might be?
    >>>
    >>> Any help would be appreciated.


  5. #5

    Re: Groupwise soap event problems

    That works good.
    Thanks.

    "Preston Stephenson" <PStephenson@gw.novell.com> wrote in message
    news:48440618.07F1.0037.1@gw.novell.com...
    > The problem is referenced in TID 3368855.
    > It references the bug # 308765.
    > It states that the fix was put to 7.0.3.
    > Is that sufficient?
    >
    > Preston
    >
    >>>> On Monday, June 02, 2008 at 12:30 PM, Martin

    > Olsen<marty@lightspeedsystems.com>
    > wrote:
    >> What I meant was could you point me to some documentation regarding this

    > bug
    >> to convince our customers to upgrade to sp3.
    >>
    >> "Preston Stephenson" <PStephenson@gw.novell.com> wrote in message
    >> news:4843E465.07F1.0037.1@gw.novell.com...
    >>> The problem was fixed in 7.0.3.
    >>> I'm not sure what you mean by "Is there any bug description out there?
    >>> Url."
    >>>
    >>> As a matter of course, you want to clean out events as soon as you can.
    >>> We've seen problems when the events build up in the users' databases.
    >>> Other problems can also happen. You need to look for "GWEvent" in the
    >>> POA log files and look for errors.
    >>>
    >>> Preston
    >>>
    >>>>>> On Monday, June 02, 2008 at 8:58 AM, Martin
    >>> Olsen<marty@lightspeedsystems.com>
    >>> wrote:
    >>>> I understand there was a bug in 7.0.2 and previous concerning

    > registering
    >>>
    >>>> for events. After registration and if there are other trusted
    >>>> applications
    >>>
    >>>> also registered for the same event, but with a different key. If any
    >>> events
    >>>> are deleted the events will be deleted for all keys.
    >>>>
    >>>> Has this been fixed in 7.0.3.Is there any bug description out there?

    > Url.
    >>>>
    >>>> Another thing, we made a workaround for this bug, by using the since

    > flag
    >>>
    >>>> and keeping the events in their accounts. By default Groupwise will
    >>>> delete
    >>>
    >>>> them after a while. I was wondering, is it possible for an account to

    > get
    >>>
    >>>> "full" of events, so after a while no more events will get added and we
    >>> wont
    >>>>
    >>>> get notified that there is a new event?
    >>>>
    >>>> We are seeing on some of our systems that after registering for events
    >>> (and
    >>>> getting notified), certain accounts just dont send us any notification.

    >
    >>>> We
    >>>
    >>>> havent been able to pinpoint yet. If any other developers are seeing

    > the
    >>>> same issues have you found out what the cause might be?
    >>>>
    >>>> Any help would be appreciated.




  6. #6

    Re: Groupwise soap event problems

    What exactly are the problems that might occur?

    "Preston Stephenson" <PStephenson@gw.novell.com> wrote in message
    news:4843E465.07F1.0037.1@gw.novell.com...

    > We've seen problems when the events build up in the users' databases.
    > Other problems can also happen. You need to look for "GWEvent" in the
    > POA log files and look for errors.
    >
    > Preston
    >
    >>>> On Monday, June 02, 2008 at 8:58 AM, Martin

    > Olsen<marty@lightspeedsystems.com>
    > wrote:
    >> I understand there was a bug in 7.0.2 and previous concerning registering

    >
    >> for events. After registration and if there are other trusted
    >> applications

    >
    >> also registered for the same event, but with a different key. If any

    > events
    >> are deleted the events will be deleted for all keys.
    >>
    >> Has this been fixed in 7.0.3.Is there any bug description out there? Url.
    >>
    >> Another thing, we made a workaround for this bug, by using the since flag

    >
    >> and keeping the events in their accounts. By default Groupwise will
    >> delete

    >
    >> them after a while. I was wondering, is it possible for an account to get

    >
    >> "full" of events, so after a while no more events will get added and we

    > wont
    >>
    >> get notified that there is a new event?
    >>
    >> We are seeing on some of our systems that after registering for events

    > (and
    >> getting notified), certain accounts just dont send us any notification.
    >> We

    >
    >> havent been able to pinpoint yet. If any other developers are seeing the
    >> same issues have you found out what the cause might be?
    >>
    >> Any help would be appreciated.




  7. #7
    Preston Stephenson NNTP User

    Re: Groupwise soap event problems

    The biggest problem was a general slow down. The CPU
    would max out. Also, events would be lost because the
    events could not be written to the users's databases
    because the databases were locked trying to do other
    updates.

    Preston

    >>> On Tuesday, June 03, 2008 at 11:19 AM, Martin

    Olsen<marty@lightspeedsystems.com> wrote:
    > What exactly are the problems that might occur?
    >
    > "Preston Stephenson" <PStephenson@gw.novell.com> wrote in message
    > news:4843E465.07F1.0037.1@gw.novell.com...
    >
    >> We've seen problems when the events build up in the users' databases.
    >> Other problems can also happen. You need to look for "GWEvent" in the
    >> POA log files and look for errors.
    >>
    >> Preston
    >>
    >>>>> On Monday, June 02, 2008 at 8:58 AM, Martin

    >> Olsen<marty@lightspeedsystems.com>
    >> wrote:
    >>> I understand there was a bug in 7.0.2 and previous concerning

    registering
    >>
    >>> for events. After registration and if there are other trusted
    >>> applications

    >>
    >>> also registered for the same event, but with a different key. If any

    >> events
    >>> are deleted the events will be deleted for all keys.
    >>>
    >>> Has this been fixed in 7.0.3.Is there any bug description out there?

    Url.
    >>>
    >>> Another thing, we made a workaround for this bug, by using the since

    flag
    >>
    >>> and keeping the events in their accounts. By default Groupwise will
    >>> delete

    >>
    >>> them after a while. I was wondering, is it possible for an account to

    get
    >>
    >>> "full" of events, so after a while no more events will get added and we

    >> wont
    >>>
    >>> get notified that there is a new event?
    >>>
    >>> We are seeing on some of our systems that after registering for events

    >> (and
    >>> getting notified), certain accounts just dont send us any notification.


    >>> We

    >>
    >>> havent been able to pinpoint yet. If any other developers are seeing

    the
    >>> same issues have you found out what the cause might be?
    >>>
    >>> Any help would be appreciated.


  8. #8

    Re: Groupwise soap event problems

    That's great. This is exactly the behavior we have been seeing.

    "Preston Stephenson" <PStephenson@gw.novell.com> wrote in message
    news:484625F7.07F1.0037.1@gw.novell.com...
    > The biggest problem was a general slow down. The CPU
    > would max out. Also, events would be lost because the
    > events could not be written to the users's databases
    > because the databases were locked trying to do other
    > updates.
    >
    > Preston
    >
    >>>> On Tuesday, June 03, 2008 at 11:19 AM, Martin

    > Olsen<marty@lightspeedsystems.com> wrote:
    >> What exactly are the problems that might occur?
    >>
    >> "Preston Stephenson" <PStephenson@gw.novell.com> wrote in message
    >> news:4843E465.07F1.0037.1@gw.novell.com...
    >>
    >>> We've seen problems when the events build up in the users' databases.
    >>> Other problems can also happen. You need to look for "GWEvent" in the
    >>> POA log files and look for errors.
    >>>
    >>> Preston
    >>>
    >>>>>> On Monday, June 02, 2008 at 8:58 AM, Martin
    >>> Olsen<marty@lightspeedsystems.com>
    >>> wrote:
    >>>> I understand there was a bug in 7.0.2 and previous concerning

    > registering
    >>>
    >>>> for events. After registration and if there are other trusted
    >>>> applications
    >>>
    >>>> also registered for the same event, but with a different key. If any
    >>> events
    >>>> are deleted the events will be deleted for all keys.
    >>>>
    >>>> Has this been fixed in 7.0.3.Is there any bug description out there?

    > Url.
    >>>>
    >>>> Another thing, we made a workaround for this bug, by using the since

    > flag
    >>>
    >>>> and keeping the events in their accounts. By default Groupwise will
    >>>> delete
    >>>
    >>>> them after a while. I was wondering, is it possible for an account to

    > get
    >>>
    >>>> "full" of events, so after a while no more events will get added and we
    >>> wont
    >>>>
    >>>> get notified that there is a new event?
    >>>>
    >>>> We are seeing on some of our systems that after registering for events
    >>> (and
    >>>> getting notified), certain accounts just dont send us any notification.

    >
    >>>> We
    >>>
    >>>> havent been able to pinpoint yet. If any other developers are seeing

    > the
    >>>> same issues have you found out what the cause might be?
    >>>>
    >>>> Any help would be appreciated.




  9. #9

    Re: Groupwise soap event problems

    I don't want to nag on forever about this issue.

    But now that we have taken the steps to delete all events after retrieving
    them in our solution, are there any other steps that would be required on a
    system that has suffered under not deleting events for a couple of weeks.
    Maintenacne?

    Or is the system fixed ones our application deletes the event?

    "Preston Stephenson" <PStephenson@gw.novell.com> wrote in message
    news:484625F7.07F1.0037.1@gw.novell.com...
    > The biggest problem was a general slow down. The CPU
    > would max out. Also, events would be lost because the
    > events could not be written to the users's databases
    > because the databases were locked trying to do other
    > updates.
    >
    > Preston
    >
    >>>> On Tuesday, June 03, 2008 at 11:19 AM, Martin

    > Olsen<marty@lightspeedsystems.com> wrote:
    >> What exactly are the problems that might occur?
    >>
    >> "Preston Stephenson" <PStephenson@gw.novell.com> wrote in message
    >> news:4843E465.07F1.0037.1@gw.novell.com...
    >>
    >>> We've seen problems when the events build up in the users' databases.
    >>> Other problems can also happen. You need to look for "GWEvent" in the
    >>> POA log files and look for errors.
    >>>
    >>> Preston
    >>>
    >>>>>> On Monday, June 02, 2008 at 8:58 AM, Martin
    >>> Olsen<marty@lightspeedsystems.com>
    >>> wrote:
    >>>> I understand there was a bug in 7.0.2 and previous concerning

    > registering
    >>>
    >>>> for events. After registration and if there are other trusted
    >>>> applications
    >>>
    >>>> also registered for the same event, but with a different key. If any
    >>> events
    >>>> are deleted the events will be deleted for all keys.
    >>>>
    >>>> Has this been fixed in 7.0.3.Is there any bug description out there?

    > Url.
    >>>>
    >>>> Another thing, we made a workaround for this bug, by using the since

    > flag
    >>>
    >>>> and keeping the events in their accounts. By default Groupwise will
    >>>> delete
    >>>
    >>>> them after a while. I was wondering, is it possible for an account to

    > get
    >>>
    >>>> "full" of events, so after a while no more events will get added and we
    >>> wont
    >>>>
    >>>> get notified that there is a new event?
    >>>>
    >>>> We are seeing on some of our systems that after registering for events
    >>> (and
    >>>> getting notified), certain accounts just dont send us any notification.

    >
    >>>> We
    >>>
    >>>> havent been able to pinpoint yet. If any other developers are seeing

    > the
    >>>> same issues have you found out what the cause might be?
    >>>>
    >>>> Any help would be appreciated.




  10. #10

    Re: Groupwise soap event problems

    I'm still not receiving any notifications from one of the boxes even after I
    deleted all the events.

    "Martin Olsen" <marty@lightspeedsystems.com> wrote in message
    news:Fch2k.1912$Ps.1241@kovat.provo.novell.com...
    >I don't want to nag on forever about this issue.
    >
    > But now that we have taken the steps to delete all events after retrieving
    > them in our solution, are there any other steps that would be required on
    > a system that has suffered under not deleting events for a couple of
    > weeks. Maintenacne?
    >
    > Or is the system fixed ones our application deletes the event?
    >
    > "Preston Stephenson" <PStephenson@gw.novell.com> wrote in message
    > news:484625F7.07F1.0037.1@gw.novell.com...
    >> The biggest problem was a general slow down. The CPU
    >> would max out. Also, events would be lost because the
    >> events could not be written to the users's databases
    >> because the databases were locked trying to do other
    >> updates.
    >>
    >> Preston
    >>
    >>>>> On Tuesday, June 03, 2008 at 11:19 AM, Martin

    >> Olsen<marty@lightspeedsystems.com> wrote:
    >>> What exactly are the problems that might occur?
    >>>
    >>> "Preston Stephenson" <PStephenson@gw.novell.com> wrote in message
    >>> news:4843E465.07F1.0037.1@gw.novell.com...
    >>>
    >>>> We've seen problems when the events build up in the users' databases.
    >>>> Other problems can also happen. You need to look for "GWEvent" in the
    >>>> POA log files and look for errors.
    >>>>
    >>>> Preston
    >>>>
    >>>>>>> On Monday, June 02, 2008 at 8:58 AM, Martin
    >>>> Olsen<marty@lightspeedsystems.com>
    >>>> wrote:
    >>>>> I understand there was a bug in 7.0.2 and previous concerning

    >> registering
    >>>>
    >>>>> for events. After registration and if there are other trusted
    >>>>> applications
    >>>>
    >>>>> also registered for the same event, but with a different key. If any
    >>>> events
    >>>>> are deleted the events will be deleted for all keys.
    >>>>>
    >>>>> Has this been fixed in 7.0.3.Is there any bug description out there?

    >> Url.
    >>>>>
    >>>>> Another thing, we made a workaround for this bug, by using the since

    >> flag
    >>>>
    >>>>> and keeping the events in their accounts. By default Groupwise will
    >>>>> delete
    >>>>
    >>>>> them after a while. I was wondering, is it possible for an account to

    >> get
    >>>>
    >>>>> "full" of events, so after a while no more events will get added and
    >>>>> we
    >>>> wont
    >>>>>
    >>>>> get notified that there is a new event?
    >>>>>
    >>>>> We are seeing on some of our systems that after registering for events
    >>>> (and
    >>>>> getting notified), certain accounts just dont send us any
    >>>>> notification.

    >>
    >>>>> We
    >>>>
    >>>>> havent been able to pinpoint yet. If any other developers are seeing

    >> the
    >>>>> same issues have you found out what the cause might be?
    >>>>>
    >>>>> Any help would be appreciated.

    >
    >




Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •