[BEEPbuilders] [beepcore] Caught NPE on SessionEvent.toString() when receivingsession close event

Daan Hoogland daan.hoogland at luminis.nl
Mon Jun 20 13:45:13 PDT 2005


Dann Martens wrote:

> Hi,
>
> In order for this to happen, either the original founding fathers of
> the beepcore project need to overcome any personal reservations
> regarding passing the torch, or someone should take the initiative to
> branch the project and give it a new home as well.

Or we could use this list to share considderations and patches.

> The new Java 5.0 features are compelling enough to consider a branch
> (built-in SASL, ...). In addition, lessons should be learned from the
> success/failure of the project up to now; some soul searching is in order.

Hereby,... Are there any more people on this list actually using it in a
project?

> BEEP provides functionality at different levels, in a package deal.
> The original authors have tried to spin it around already several
> times in their attempts to huckster the technology, to no avail. I can
> sum up many uses for BEEP, but none of them seem to require the entire
> package at the same time.
>
> Clearly, BEEP appeals in many ways to a lot of us, but without any
> means to commit your effort spent to improve the current
> implementation, we would be wasting our time...
>
> Cya,
> Dann   
> Daan Hoogland wrote:
>
>> H,
>>
>> nice to hear someone does something with this.
>>
>> I saw something maybe related with a tls profile. I tested the stability
>> by removing the ip connection from under the c/s connection. It was the
>> client that couldn't recover. Ididn't look into it to much as the
>> connection is generally very stable. Also I thought it was JSSE related,
>> but your scenario rings a bell somehow. I'm working with the latest
>> version as well:-(
>>
>> Maybe if you get to do a fix you could post it here? The project could
>> get alive the old fashioned way again:-)
>>
>> Christian Möller wrote:
>>
>>  
>>
>>> Hi,
>>>
>>> currently I'm writing a prototype BEEP client and server testing the
>>> protocol, some implementations of it - and my knowledge.
>>>
>>> In the course of my investigation I've written an ugly behaving client
>>> not sending any channel or session close requests; he only shuts down
>>> the TCP connection when finished. My
>>> org.beepcore.beep.core.event.SessionListener tries to log the event he
>>> receives with a call of sessionClosed(final SessionEvent event) - and
>>> fails like this:
>>>
>>> java.lang.NullPointerException
>>>     at
>>> org.beepcore.beep.transport.tcp.TCPSession.toString(TCPSession.java:230)
>>>
>>>     at java.lang.String.valueOf(String.java:2131)
>>>     at java.lang.StringBuffer.append(StringBuffer.java:370)
>>>     at java.util.EventObject.toString(EventObject.java:54)
>>>     ...
>>>
>>> No heavy bug, but it shouldn't be much work to fix it. I'm working with
>>> version 0.9.08.
>>>
>>> Thanks and regards.
>>>
>>> Christian
>>> _______________________________________________
>>> BEEPbuilders mailing list
>>> BEEPbuilders at lists.beepcore.org
>>> http://drakken.dbc.mtview.ca.us/mailman/listinfo/beepbuilders
>>>
>>>
>>>   
>>
>>
>>
>>  
>>
>


-- 
<insert your favorite astute quote here />
-----------------------------
Daan Hoogland
software architect
-----------------------------
daan.hoogland at luminis.nl
0620442544
www.luminis.nl
-----------------------------
<or here />



More information about the BEEPbuilders mailing list