Recent changes to bugs

#12 EventParser.parse throws OOM when end > is missing

2014-06-20T09:37:15.796000Z

Group: v1.0_(example) --> 2.0.5

EventParser.parse throws OOM when end > is missing

2014-06-20T09:34:31.427000Z

Ticket 12 has been modified: EventParser.parse throws OOM when end > is missing
Edited By: Just van den Broecke (justb)
milestone updated: u'v1.0(example)' => u'2.0.5'

EventParser.parse throws OOM when end > is missing

2014-06-20T09:34:31.427000Z

From Carsten:
Date: 18-06-14 12:15

We have stumbled over a bug in EventParser.parse that causes an OOM exception when the > char is missing.

The following code should check for -1 returned from read() and break/throw accordingly.

// Then find end-tag ('>'), appending all chars to preparsed string.
do {
        nextChar = (char) aReader.read();
        preparsedString.append(nextChar);
 } while (nextChar != '>');

This can/will happen if there is a difference between the char encoding used by the server (tomcat) hosting pushlet and the encoding of any strings contained in the events sent from a client.

Chat demo can't send special char

2012-04-27T07:45:17Z

when send special char..access error..

PushletClient.joinListen returns before session ID is saved

2009-06-05T21:56:31Z

Since the handling of E_JOIN_LISTEN_ACK is processed in a different thread than the one that starts the DataEventListener, it is possible that a call to PushletClient.joinListen will return before the E_JOIN_LISTEN_ACK branch executes to save the session ID. This can cause throwOnInvalidSession if the user calls PushletClient.subscribe immediately after PushletClient.joinListen.

Flow of events that cause the problem:
- Client calls PushletClient.joinListen
- DataEventListener thread is started via startDataEventListener
- DataEventListener sends E_JOIN_LISTEN to pushlet
- DataEventListener notifies thread that started it, joinListen returns
- Client calls PushletClient.subscribe, throwOnInvalidSession is triggered and ID is still null
- Shortly after the E_JOIN_LISTEN_ACK is received and ID is saved

The work around I am using is this:
- Add a boolean field to PushletClient named 'startFromJoinListen'
- Move the 'this.notify()' code in DataEventListener.run() to a method called 'signalReady()'
- If Pushlet.joinListen is called then set startFromJoinListen to true
- In DataEventListener, if (!startFromJoinListen) { signalReady(); } immediately after the call to openURL. However if startFromJoinListen is true then don't call signalReady() until E_JOIN_LISTEN_ACK is received.
This will ensure that there is a session ID saved before further calls can be made. I can submit a patch if you like.

Poll mode blocks when no event present

2008-04-09T15:39:53Z

In poll mode, when the event-queue is empty, the thread is blocked waiting for an event. This is not the expected behaviour of poll mode.

The problem seems to be located in Subscriber.fetchEvent() line 236: deQueueAll() is called with a zero value. Then dequeueAll(), call the wait method with this previous value, blocking the thread forever.

A quick (and dirt) workarround is to initialize queueReadTimeoutMillis with 1 for example.

I attached a file with the blocked thread stack trace.

Browsers receaving all events when listening on different su

2008-02-19T11:27:50Z

I have two web browsers listening on different subjects

"/CTE/7" and "/CTE/9".

i have a java servlet publishing events on each subjects depending on which browser it originated. for some reason both browsers are getting all requests.

Stock demo doest not run in WebSphere

2007-12-07T03:02:23Z

Stock demo doest not run in WebSphere6.
Data was send and printwriter was flushed but client didn't received data.

Refreshing Stocks demo running in IE with F5 problem

2007-07-20T21:26:58Z

Refreshing Stocks demo running in IE with F5 causes updates to stop arriving for about 15 seconds. Reconnect should take musch less time than that.

Problem with Umlauts in IE

2007-05-26T11:05:30Z

Hi,

I've detected a problem if the event that is pushed contains some german umlauts (not sure if the same occurs with some french characters, too).
It works with Firefox but does not work in IE. Finally I found the solution for the problem.
In the class nl.justobjects.pushlet.core.XMLAdapter the contentType for strictXML is set as "text/xml" but to have it work with umlauts you must change this to "text/xml; charset=UTF-8" (line 38).
After this change it works.

Btw: Great work, I love pushlets ;-)