[vwnc] [7.6] Opentalk bug

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

[vwnc] [7.6] Opentalk bug

Emiliano Pérez-3
Hi List,
    sorry if this issue has been already addressed but i cant find it
anywere on the list. The thing is that I´ve been "porting" some work
from 7.4.1 to 7.6. This work involves using opentalk and a subsystem
that uses some remotes objects in the #pause and #resume actions. In
7.4.1 worked fine but in 7.6 when i save the image the resume action
throws a waitWrite... exception. When i debugged the problem I found a
comment refering to an "AR #" bug report, so i figure that this is a
well known bug and has already been fixed.

What I wanted to know is which version of opentalk should i use for a
7.6 image from now on, since i been looking in the public repo and found
too many versions, but none especifically for 7.6 nor addressing
especifically that bug.

At the moment i dont have the AR number but i can specify it later if
necesary.

Thanks in advance.

Regards,
     Emiliano.
_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: [vwnc] [7.6] Opentalk bug

Emiliano Pérez-3
Hi list, the report number is "AR 42265". Anyone knows how to fix this?
I`ve seen somewere else that there is an opentalk patch adressing this problem but i don´t know if its free to use, and how to include this in my 7.6 image with opentalk since it is a .st file. Filing in each time i load opentalk does not seem a good idea.

2008/7/22 Emiliano Pérez <[hidden email]>:
Hi List,
  sorry if this issue has been already addressed but i cant find it anywere on the list. The thing is that I´ve been "porting" some work from 7.4.1 to 7.6. This work involves using opentalk and a subsystem that uses some remotes objects in the #pause and #resume actions. In 7.4.1 worked fine but in 7.6 when i save the image the resume action throws a waitWrite... exception. When i debugged the problem I found a comment refering to an "AR #" bug report, so i figure that this is a well known bug and has already been fixed.

What I wanted to know is which version of opentalk should i use for a 7.6 image from now on, since i been looking in the public repo and found too many versions, but none especifically for 7.6 nor addressing especifically that bug.

At the moment i dont have the AR number but i can specify it later if necesary.

Thanks in advance.

Regards,
   Emiliano.


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: [vwnc] [7.6] Opentalk bug

Alan Knight-2
That's a bug that was fixed quite some time ago.

I'm suspicious that in your case your subsystem is being shut down or paused only after the opentalk system has already done so. Try checking the prerequisites on your system, or in the debugger look and see what the state of the opentalk subsystem is. The Tools-StartupOrderingTool parcel might be helpful.

At 09:18 AM 7/25/2008, Emiliano Pérez wrote:
Hi list, the report number is "AR 42265". Anyone knows how to fix this?
I`ve seen somewere else that there is an opentalk patch adressing this problem but i don´t know if its free to use, and how to include this in my 7.6 image with opentalk since it is a .st file. Filing in each time i load opentalk does not seem a good idea.

2008/7/22 Emiliano Pérez <[hidden email] >:
Hi List,
  sorry if this issue has been already addressed but i cant find it anywere on the list. The thing is that I´ve been "porting" some work from 7.4.1 to 7.6. This work involves using opentalk and a subsystem that uses some remotes objects in the #pause and #resume actions. In 7.4.1 worked fine but in 7.6 when i save the image the resume action throws a waitWrite... exception. When i debugged the problem I found a comment refering to an "AR #" bug report, so i figure that this is a well known bug and has already been fixed.

What I wanted to know is which version of opentalk should i use for a 7.6 image from now on, since i been looking in the public repo and found too many versions, but none especifically for 7.6 nor addressing especifically that bug.

At the moment i dont have the AR number but i can specify it later if necesary.

Thanks in advance.

Regards,
   Emiliano.


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

--
Alan Knight [|], Engineering Manager, Cincom Smalltalk

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: [vwnc] [7.6] Opentalk bug

Emiliano Pérez-3
In reply to this post by Emiliano Pérez-3
Alan,
    Thanks a lot for your help. I see now that I was wrong about the
bug, the weird thing is that I never came across this problem in 7.4.1.
The prerequisite for my subsystem is implemented like this:

prerequisiteSystems
    ^Array with: Opentalk.OpentalkSystem.

This means that the Opentalk system closes after mine and opens first,
am I rigth? I´ve been debugging for a while now but its difficult
because the image tends to crash if you halt the subsystem sequence.
I´ve chequed my subsystem with the tool you mention, it apears just
below opentalk´s.

Debugging the error I came to find that the Opentalk.TCPTransport
instances stop when i save/close the image but they don´t start again
when the image is resumed, even though my broker does, and this is the
main cause for my problem. Don´t know why this happens, but it has to be
somethng my application does wrong (maybe an object release?).

Regards,
     Emiliano.

Alan Knight escribió:

> That's a bug that was fixed quite some time ago.
>
> I'm suspicious that in your case your subsystem is being shut down or
> paused only after the opentalk system has already done so. Try
> checking the prerequisites on your system, or in the debugger look and
> see what the state of the opentalk subsystem is. The
> Tools-StartupOrderingTool parcel might be helpful.
>
> At 09:18 AM 7/25/2008, Emiliano Pérez wrote:
>> Hi list, the report number is "AR 42265". Anyone knows how to fix this?
>> I`ve seen somewere else that there is an opentalk patch adressing
>> this problem but i don´t know if its free to use, and how to include
>> this in my 7.6 image with opentalk since it is a .st file. Filing in
>> each time i load opentalk does not seem a good idea.
>>
>> 2008/7/22 Emiliano Pérez <[hidden email]
>> <mailto:[hidden email]> >:
>>
>>     Hi List,
>>       sorry if this issue has been already addressed but i cant find
>>     it anywere on the list. The thing is that I´ve been "porting"
>>     some work from 7.4.1 to 7.6. This work involves using opentalk
>>     and a subsystem that uses some remotes objects in the #pause and
>>     #resume actions. In 7.4.1 worked fine but in 7.6 when i save the
>>     image the resume action throws a waitWrite... exception. When i
>>     debugged the problem I found a comment refering to an "AR #" bug
>>     report, so i figure that this is a well known bug and has already
>>     been fixed.
>>
>>     What I wanted to know is which version of opentalk should i use
>>     for a 7.6 image from now on, since i been looking in the public
>>     repo and found too many versions, but none especifically for 7.6
>>     nor addressing especifically that bug.
>>
>>     At the moment i dont have the AR number but i can specify it
>>     later if necesary.
>>
>>     Thanks in advance.
>>
>>     Regards,
>>        Emiliano.
>>
>>
>> _______________________________________________
>> vwnc mailing list
>> [hidden email]
>> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
>
> --
> Alan Knight [|], Engineering Manager, Cincom Smalltalk
> [hidden email]
> [hidden email]
> http://www.cincom.com/smalltalk

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc