Home » Eclipse Projects » Riena » Getting sendig host when using client monitoring
| | | |
| Re: Getting sendig host when using client monitoring [message #24481 is a reply to message #24440] |
Wed, 08 April 2009 08:54   |
 Stefan Liebig
Messages: 124
Registered: July 2009 |
Senior Member |
|
|
Hi Carsten,
I guess this happens when the store tries to deserialize the
collectibles from disk, right?
Does ´patching´ the manifest.mf with "Eclipse-BuddyPolicy" solve the issue?
Tschüß,
Stefan
Carsten Spieker wrote:
> Hi Stefan,
>
> unfortunately your suggestion does not seem to work, or I´m still doing
> something wrong.
>
> What I did:
>
> - Extending LogServiceCollector and overwriting the collect(*)-method.
> - Implementing an Serializable-Object which contains hostname and the
> original LogEventTransferObject
> - calling super.collect(myOwnSerializable)
>
> What goes wrong:
>
> - When SimpleSender asks the SimpleStore for the Collectibles which are to
> transfer, the SimpleStore cannot found the class of my Serializable-object.
> - I tried to set a "Eclipse-RegisterBuddy: org.eclipse.riena.monitor.client"
> entry in my Manifest.MF but unfortunately org.eclipse.riena.monitor.client
> does not set an accordant "Eclipse-BuddyPolicy".
>
> Effect:
>
> - The Receiver does not receive my Serializable-object but only the original
> LogEntryTranferObject and I´m as far as before.
>
> Have I done something wrong here?
>
> Greetz,
> Carsten
>
> "Stefan Liebig" <Stefan.Liebig@compeople.de> schrieb im Newsbeitrag
> news:grfno1$bho$1@build.eclipse.org...
>> Hi Carsten,
>>
>> Carsten Spieker wrote:
>>> Hi,
>>>
>>> is it possible to get the hostname of the sending client in my
>>> IReceiver-implementation?
>> Well, not out of the box! At least not yet ;-)
>>
>>> I am using
>>> org.eclipse.riena.monitor.client.SimpleSender as sender,
>>> org.eclipse.riena.monitor.client.SimpleStore as store and
>>> org.eclipse.riena.monitor.client.LogServiceCollector as collector?
>>>
>>> Or do I have to create my own implementation of one of these to get this
>>> information?
>> You could probably sub-class LogServiceCollector and implement there the
>> collect( T payload) method, such that you create another Serializable
>> containing the hostname and the original payload and pass this to
>> super.collect()
>> However, this seems to me reasonable use case. I would suggest that you
>> create a bugzilla for that and we can continue discussing there.
>>
>> Tschüß,
>> Stefan
>>
>>> Greetz and Thanks!
>>> Carsten
>
>
|
|
| |
| Re: Getting sendig host when using client monitoring [message #24563 is a reply to message #24522] |
Wed, 08 April 2009 11:08 |
Stefan Liebig
Messages: 124
Registered: July 2009 |
Senior Member |
|
|
Hi Carsten,
Yes, I think it is a bug. So a bug report would be fine.
Thanks and Tschüß,
Stefan
Carsten Spieker wrote:
> Hi Stefan,
>
> yes patching the manifest.mf solves it. Can this be treated as a bug, so
> that I can enter a bug report? Or does it make no sense for you to add the
> BuddyPolicy to this bundle in general?
>
> Tschüss,
> Carsten
>
>
> "Stefan Liebig" <Stefan.Liebig@compeople.de> schrieb im Newsbeitrag
> news:grhoom$8k9$1@build.eclipse.org...
>> Hi Carsten,
>>
>> I guess this happens when the store tries to deserialize the collectibles
>> from disk, right?
>> Does ´patching´ the manifest.mf with "Eclipse-BuddyPolicy" solve the
>> issue?
>>
>> Tschüß,
>> Stefan
>>
>> Carsten Spieker wrote:
>>> Hi Stefan,
>>>
>>> unfortunately your suggestion does not seem to work, or I´m still doing
>>> something wrong.
>>>
>>> What I did:
>>>
>>> - Extending LogServiceCollector and overwriting the collect(*)-method.
>>> - Implementing an Serializable-Object which contains hostname and the
>>> original LogEventTransferObject
>>> - calling super.collect(myOwnSerializable)
>>>
>>> What goes wrong:
>>>
>>> - When SimpleSender asks the SimpleStore for the Collectibles which are
>>> to transfer, the SimpleStore cannot found the class of my
>>> Serializable-object.
>>> - I tried to set a "Eclipse-RegisterBuddy:
>>> org.eclipse.riena.monitor.client" entry in my Manifest.MF but
>>> unfortunately org.eclipse.riena.monitor.client does not set an accordant
>>> "Eclipse-BuddyPolicy".
>>>
>>> Effect:
>>>
>>> - The Receiver does not receive my Serializable-object but only the
>>> original LogEntryTranferObject and I´m as far as before.
>>>
>>> Have I done something wrong here?
>>>
>>> Greetz,
>>> Carsten
>>>
>>> "Stefan Liebig" <Stefan.Liebig@compeople.de> schrieb im Newsbeitrag
>>> news:grfno1$bho$1@build.eclipse.org...
>>>> Hi Carsten,
>>>>
>>>> Carsten Spieker wrote:
>>>>> Hi,
>>>>>
>>>>> is it possible to get the hostname of the sending client in my
>>>>> IReceiver-implementation?
>>>> Well, not out of the box! At least not yet ;-)
>>>>
>>>>> I am using
>>>>> org.eclipse.riena.monitor.client.SimpleSender as sender,
>>>>> org.eclipse.riena.monitor.client.SimpleStore as store and
>>>>> org.eclipse.riena.monitor.client.LogServiceCollector as collector?
>>>>>
>>>>> Or do I have to create my own implementation of one of these to get
>>>>> this information?
>>>> You could probably sub-class LogServiceCollector and implement there the
>>>> collect( T payload) method, such that you create another Serializable
>>>> containing the hostname and the original payload and pass this to
>>>> super.collect()
>>>> However, this seems to me reasonable use case. I would suggest that you
>>>> create a bugzilla for that and we can continue discussing there.
>>>>
>>>> Tschüß,
>>>> Stefan
>>>>
>>>>> Greetz and Thanks!
>>>>> Carsten
>
|
|
| |
| Re: Getting sendig host when using client monitoring [message #24645 is a reply to message #24605] |
Tue, 14 April 2009 08:18 |
Stefan Liebig
Messages: 124
Registered: July 2009 |
Senior Member |
|
|
The bug has been resolved and you can read about the solution here:
http://wiki.eclipse.org/Riena_Getting_Started_with_Client_Mo nitoring#Client_information_provider
Tschüß,
Stefan
Carsten Spieker wrote:
> Hi,
>
> bug 271607 added.
>
> Greetz,
> Carsten
>
> "Stefan Liebig" <Stefan.Liebig@compeople.de> schrieb im Newsbeitrag
> news:gri0j7$b42$1@build.eclipse.org...
>> Hi Carsten,
>>
>> Yes, I think it is a bug. So a bug report would be fine.
>>
>> Thanks and Tschüß,
>> Stefan
>>
>> Carsten Spieker wrote:
>>> Hi Stefan,
>>>
>>> yes patching the manifest.mf solves it. Can this be treated as a bug, so
>>> that I can enter a bug report? Or does it make no sense for you to add
>>> the BuddyPolicy to this bundle in general?
>>>
>>> Tschüss,
>>> Carsten
>>>
>>>
>>> "Stefan Liebig" <Stefan.Liebig@compeople.de> schrieb im Newsbeitrag
>>> news:grhoom$8k9$1@build.eclipse.org...
>>>> Hi Carsten,
>>>>
>>>> I guess this happens when the store tries to deserialize the
>>>> collectibles from disk, right?
>>>> Does ´patching´ the manifest.mf with "Eclipse-BuddyPolicy" solve the
>>>> issue?
>>>>
>>>> Tschüß,
>>>> Stefan
>>>>
>>>> Carsten Spieker wrote:
>>>>> Hi Stefan,
>>>>>
>>>>> unfortunately your suggestion does not seem to work, or I´m still doing
>>>>> something wrong.
>>>>>
>>>>> What I did:
>>>>>
>>>>> - Extending LogServiceCollector and overwriting the collect(*)-method.
>>>>> - Implementing an Serializable-Object which contains hostname and the
>>>>> original LogEventTransferObject
>>>>> - calling super.collect(myOwnSerializable)
>>>>>
>>>>> What goes wrong:
>>>>>
>>>>> - When SimpleSender asks the SimpleStore for the Collectibles which are
>>>>> to transfer, the SimpleStore cannot found the class of my
>>>>> Serializable-object.
>>>>> - I tried to set a "Eclipse-RegisterBuddy:
>>>>> org.eclipse.riena.monitor.client" entry in my Manifest.MF but
>>>>> unfortunately org.eclipse.riena.monitor.client does not set an
>>>>> accordant "Eclipse-BuddyPolicy".
>>>>>
>>>>> Effect:
>>>>>
>>>>> - The Receiver does not receive my Serializable-object but only the
>>>>> original LogEntryTranferObject and I´m as far as before.
>>>>>
>>>>> Have I done something wrong here?
>>>>>
>>>>> Greetz,
>>>>> Carsten
>>>>>
>>>>> "Stefan Liebig" <Stefan.Liebig@compeople.de> schrieb im Newsbeitrag
>>>>> news:grfno1$bho$1@build.eclipse.org...
>>>>>> Hi Carsten,
>>>>>>
>>>>>> Carsten Spieker wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> is it possible to get the hostname of the sending client in my
>>>>>>> IReceiver-implementation?
>>>>>> Well, not out of the box! At least not yet ;-)
>>>>>>
>>>>>>> I am using
>>>>>>> org.eclipse.riena.monitor.client.SimpleSender as sender,
>>>>>>> org.eclipse.riena.monitor.client.SimpleStore as store and
>>>>>>> org.eclipse.riena.monitor.client.LogServiceCollector as collector?
>>>>>>>
>>>>>>> Or do I have to create my own implementation of one of these to get
>>>>>>> this information?
>>>>>> You could probably sub-class LogServiceCollector and implement there
>>>>>> the collect( T payload) method, such that you create another
>>>>>> Serializable containing the hostname and the original payload and pass
>>>>>> this to super.collect()
>>>>>> However, this seems to me reasonable use case. I would suggest that
>>>>>> you create a bugzilla for that and we can continue discussing there.
>>>>>>
>>>>>> Tschüß,
>>>>>> Stefan
>>>>>>
>>>>>>> Greetz and Thanks!
>>>>>>> Carsten
>
>
|
|
| | | |
| Re: Getting sendig host when using client monitoring [message #581796 is a reply to message #24440] |
Wed, 08 April 2009 08:54 |
Stefan Liebig
Messages: 124
Registered: July 2009 |
Senior Member |
|
|
Hi Carsten,
I guess this happens when the store tries to deserialize the
collectibles from disk, right?
Does ´patching´ the manifest.mf with "Eclipse-BuddyPolicy" solve the issue?
Tschüß,
Stefan
Carsten Spieker wrote:
> Hi Stefan,
>
> unfortunately your suggestion does not seem to work, or I´m still doing
> something wrong.
>
> What I did:
>
> - Extending LogServiceCollector and overwriting the collect(*)-method.
> - Implementing an Serializable-Object which contains hostname and the
> original LogEventTransferObject
> - calling super.collect(myOwnSerializable)
>
> What goes wrong:
>
> - When SimpleSender asks the SimpleStore for the Collectibles which are to
> transfer, the SimpleStore cannot found the class of my Serializable-object.
> - I tried to set a "Eclipse-RegisterBuddy: org.eclipse.riena.monitor.client"
> entry in my Manifest.MF but unfortunately org.eclipse.riena.monitor.client
> does not set an accordant "Eclipse-BuddyPolicy".
>
> Effect:
>
> - The Receiver does not receive my Serializable-object but only the original
> LogEntryTranferObject and I´m as far as before.
>
> Have I done something wrong here?
>
> Greetz,
> Carsten
>
> "Stefan Liebig" <Stefan.Liebig@compeople.de> schrieb im Newsbeitrag
> news:grfno1$bho$1@build.eclipse.org...
>> Hi Carsten,
>>
>> Carsten Spieker wrote:
>>> Hi,
>>>
>>> is it possible to get the hostname of the sending client in my
>>> IReceiver-implementation?
>> Well, not out of the box! At least not yet ;-)
>>
>>> I am using
>>> org.eclipse.riena.monitor.client.SimpleSender as sender,
>>> org.eclipse.riena.monitor.client.SimpleStore as store and
>>> org.eclipse.riena.monitor.client.LogServiceCollector as collector?
>>>
>>> Or do I have to create my own implementation of one of these to get this
>>> information?
>> You could probably sub-class LogServiceCollector and implement there the
>> collect( T payload) method, such that you create another Serializable
>> containing the hostname and the original payload and pass this to
>> super.collect()
>> However, this seems to me reasonable use case. I would suggest that you
>> create a bugzilla for that and we can continue discussing there.
>>
>> Tschüß,
>> Stefan
>>
>>> Greetz and Thanks!
>>> Carsten
>
>
|
|
| |
| Re: Getting sendig host when using client monitoring [message #581822 is a reply to message #24522] |
Wed, 08 April 2009 11:08 |
Stefan Liebig
Messages: 124
Registered: July 2009 |
Senior Member |
|
|
Hi Carsten,
Yes, I think it is a bug. So a bug report would be fine.
Thanks and Tschüß,
Stefan
Carsten Spieker wrote:
> Hi Stefan,
>
> yes patching the manifest.mf solves it. Can this be treated as a bug, so
> that I can enter a bug report? Or does it make no sense for you to add the
> BuddyPolicy to this bundle in general?
>
> Tschüss,
> Carsten
>
>
> "Stefan Liebig" <Stefan.Liebig@compeople.de> schrieb im Newsbeitrag
> news:grhoom$8k9$1@build.eclipse.org...
>> Hi Carsten,
>>
>> I guess this happens when the store tries to deserialize the collectibles
>> from disk, right?
>> Does ´patching´ the manifest.mf with "Eclipse-BuddyPolicy" solve the
>> issue?
>>
>> Tschüß,
>> Stefan
>>
>> Carsten Spieker wrote:
>>> Hi Stefan,
>>>
>>> unfortunately your suggestion does not seem to work, or I´m still doing
>>> something wrong.
>>>
>>> What I did:
>>>
>>> - Extending LogServiceCollector and overwriting the collect(*)-method.
>>> - Implementing an Serializable-Object which contains hostname and the
>>> original LogEventTransferObject
>>> - calling super.collect(myOwnSerializable)
>>>
>>> What goes wrong:
>>>
>>> - When SimpleSender asks the SimpleStore for the Collectibles which are
>>> to transfer, the SimpleStore cannot found the class of my
>>> Serializable-object.
>>> - I tried to set a "Eclipse-RegisterBuddy:
>>> org.eclipse.riena.monitor.client" entry in my Manifest.MF but
>>> unfortunately org.eclipse.riena.monitor.client does not set an accordant
>>> "Eclipse-BuddyPolicy".
>>>
>>> Effect:
>>>
>>> - The Receiver does not receive my Serializable-object but only the
>>> original LogEntryTranferObject and I´m as far as before.
>>>
>>> Have I done something wrong here?
>>>
>>> Greetz,
>>> Carsten
>>>
>>> "Stefan Liebig" <Stefan.Liebig@compeople.de> schrieb im Newsbeitrag
>>> news:grfno1$bho$1@build.eclipse.org...
>>>> Hi Carsten,
>>>>
>>>> Carsten Spieker wrote:
>>>>> Hi,
>>>>>
>>>>> is it possible to get the hostname of the sending client in my
>>>>> IReceiver-implementation?
>>>> Well, not out of the box! At least not yet ;-)
>>>>
>>>>> I am using
>>>>> org.eclipse.riena.monitor.client.SimpleSender as sender,
>>>>> org.eclipse.riena.monitor.client.SimpleStore as store and
>>>>> org.eclipse.riena.monitor.client.LogServiceCollector as collector?
>>>>>
>>>>> Or do I have to create my own implementation of one of these to get
>>>>> this information?
>>>> You could probably sub-class LogServiceCollector and implement there the
>>>> collect( T payload) method, such that you create another Serializable
>>>> containing the hostname and the original payload and pass this to
>>>> super.collect()
>>>> However, this seems to me reasonable use case. I would suggest that you
>>>> create a bugzilla for that and we can continue discussing there.
>>>>
>>>> Tschüß,
>>>> Stefan
>>>>
>>>>> Greetz and Thanks!
>>>>> Carsten
>
|
|
| |
| Re: Getting sendig host when using client monitoring [message #581856 is a reply to message #24605] |
Tue, 14 April 2009 08:18 |
Stefan Liebig
Messages: 124
Registered: July 2009 |
Senior Member |
|
|
The bug has been resolved and you can read about the solution here:
http://wiki.eclipse.org/Riena_Getting_Started_with_Client_Mo nitoring#Client_information_provider
Tschüß,
Stefan
Carsten Spieker wrote:
> Hi,
>
> bug 271607 added.
>
> Greetz,
> Carsten
>
> "Stefan Liebig" <Stefan.Liebig@compeople.de> schrieb im Newsbeitrag
> news:gri0j7$b42$1@build.eclipse.org...
>> Hi Carsten,
>>
>> Yes, I think it is a bug. So a bug report would be fine.
>>
>> Thanks and Tschüß,
>> Stefan
>>
>> Carsten Spieker wrote:
>>> Hi Stefan,
>>>
>>> yes patching the manifest.mf solves it. Can this be treated as a bug, so
>>> that I can enter a bug report? Or does it make no sense for you to add
>>> the BuddyPolicy to this bundle in general?
>>>
>>> Tschüss,
>>> Carsten
>>>
>>>
>>> "Stefan Liebig" <Stefan.Liebig@compeople.de> schrieb im Newsbeitrag
>>> news:grhoom$8k9$1@build.eclipse.org...
>>>> Hi Carsten,
>>>>
>>>> I guess this happens when the store tries to deserialize the
>>>> collectibles from disk, right?
>>>> Does ´patching´ the manifest.mf with "Eclipse-BuddyPolicy" solve the
>>>> issue?
>>>>
>>>> Tschüß,
>>>> Stefan
>>>>
>>>> Carsten Spieker wrote:
>>>>> Hi Stefan,
>>>>>
>>>>> unfortunately your suggestion does not seem to work, or I´m still doing
>>>>> something wrong.
>>>>>
>>>>> What I did:
>>>>>
>>>>> - Extending LogServiceCollector and overwriting the collect(*)-method.
>>>>> - Implementing an Serializable-Object which contains hostname and the
>>>>> original LogEventTransferObject
>>>>> - calling super.collect(myOwnSerializable)
>>>>>
>>>>> What goes wrong:
>>>>>
>>>>> - When SimpleSender asks the SimpleStore for the Collectibles which are
>>>>> to transfer, the SimpleStore cannot found the class of my
>>>>> Serializable-object.
>>>>> - I tried to set a "Eclipse-RegisterBuddy:
>>>>> org.eclipse.riena.monitor.client" entry in my Manifest.MF but
>>>>> unfortunately org.eclipse.riena.monitor.client does not set an
>>>>> accordant "Eclipse-BuddyPolicy".
>>>>>
>>>>> Effect:
>>>>>
>>>>> - The Receiver does not receive my Serializable-object but only the
>>>>> original LogEntryTranferObject and I´m as far as before.
>>>>>
>>>>> Have I done something wrong here?
>>>>>
>>>>> Greetz,
>>>>> Carsten
>>>>>
>>>>> "Stefan Liebig" <Stefan.Liebig@compeople.de> schrieb im Newsbeitrag
>>>>> news:grfno1$bho$1@build.eclipse.org...
>>>>>> Hi Carsten,
>>>>>>
>>>>>> Carsten Spieker wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> is it possible to get the hostname of the sending client in my
>>>>>>> IReceiver-implementation?
>>>>>> Well, not out of the box! At least not yet ;-)
>>>>>>
>>>>>>> I am using
>>>>>>> org.eclipse.riena.monitor.client.SimpleSender as sender,
>>>>>>> org.eclipse.riena.monitor.client.SimpleStore as store and
>>>>>>> org.eclipse.riena.monitor.client.LogServiceCollector as collector?
>>>>>>>
>>>>>>> Or do I have to create my own implementation of one of these to get
>>>>>>> this information?
>>>>>> You could probably sub-class LogServiceCollector and implement there
>>>>>> the collect( T payload) method, such that you create another
>>>>>> Serializable containing the hostname and the original payload and pass
>>>>>> this to super.collect()
>>>>>> However, this seems to me reasonable use case. I would suggest that
>>>>>> you create a bugzilla for that and we can continue discussing there.
>>>>>>
>>>>>> Tschüß,
>>>>>> Stefan
>>>>>>
>>>>>>> Greetz and Thanks!
>>>>>>> Carsten
>
>
|
|
|
Goto Forum:
Current Time: Wed Oct 09 13:21:57 GMT 2024
Powered by FUDForum. Page generated in 0.04946 seconds |
] 
Search
Help
Register
Login
Home
