bayeux | Historic Tale Construction Kit - opensource | Game Engine library

It looks like you have a couple relatively large values, while most are small. This causes 'skewing' of your color scale in a way that looks less interesting. Instead of graphing number of users, consider mapping based on a quantile .

Here is an implementation of grouping into quantiles using cut2() from Hmisc. In this case, values are cut into 5 groups.

In general, CometD recommends to deploy in Jetty and to use the latest release (at this time 4.0.4).

Your web.xml has incorrect values for the transports init-param.

JettyWebSocketTransport is a CometD transport that uses Jetty-specific API in its implementation; as such, it only works when your application is deployed in Jetty.

I recommend that you remove the transports init-param and let CometD pick the proper defaults, which will work in both Jetty and Tomcat.

For the record, the default WebSocket transport is org.cometd.websocket.server.WebSocketTransport which is based on the standard JSR 356 APIs that are implemented by both Jetty and Tomcat.

Your client is correct, although there also you may want to use the standard WebSocket transport, org.cometd.websocket.client.WebSocketTransport.

I tried the command to generate a project from the archetypes and works fine for me. Perhaps you have a hint in the error: URI does not specify a valid host name: http:/cometd.org - see how there is only 1 slash, not the required 2 slashes.

In summary:

• Move to CometD 4.0.x
• Move to Jetty if you can
• Remove the transports configuration and use the defaults.
• Re-run the archetypes with the right URL: https://cometd.org.

Solution for: - CometD 4.0.2 - Spring 4.3.9.RELEASE - Spring Security 4.1.0.RELEASE

In my project we faced similar problem while switching from "long pooling" to "websocket" connection. For clarification - one difference - we were using "user context" only during "handshake".

With usage of "long pooling" Cookie with JSESSIONID was interpreted correctly by Spring and we were working in "user context". After switching to "websocket" it looked like "user context" was lost just before running message receiving code.

We could not find proper solution - following code is in my opinion just a hack. But it worked for us.

It seems you are using this Kafka library, which has nothing to do with Salesforce, but you give it a string of your Kafka broker addresses, as shown in the examples there.

Note: That library doesn't look actively maintained and Kafka is not an http protocol so putting http://server:9092 doesn't make sense...

You might want to checkout confluent-kafka-dotnet instead.

I believe that the authorization key is incorrect. It is not your password that is expected but an OAuth access token or session id that you receive after you log into salesforce. See the different OAuth flows, if you are testing you can use the username password flow.

The following method u can use to get the session id when needed

Here is a regex that should do what you want:

You don't need to do anything.

The information carried by the advice field is handled by the implementation, so your application (or any application) should not perform any action based on the information of the advice field.

For applications, the advice field is just informative.

You have specified incorrect channel path in:

Your web.xml declared the web application to be Servlet 3.1.

ServletOutputStream.setWriteListener(WriteListener) is a method that has been added to Servlet 3.1.

The error you get: