mmakowski/clisson-client

clisson-client's Issues

Specify component id as a config property

Request: A switch to turn on/off the event logging

My application would like to have the flexibility to turn on/off the event logging based different environment.

Suppose there is no default facility, please take this as the request for it.

It would be best if there is an optional config parameter for the "componentId" for handy purpose

Many Thanks

When clisson.properties is not found, disable the recording

When introducing clisson to existing codebase, it would be useful to only enable it in selected instances of the system without requiring the instances where reporting is disabled to have clisson.properties.

The client should be modified so that if clisson.properties is not found it uses default config that has the recording disabled.

"java.net.BindException: Address already in use: connect" with Clisson Client

I'm getting the exception below when saving events into Clisson Server via Log4J appender

hints: it seems to occurs when the event is saving at a high rate

java.lang.RuntimeException: error when posting to http://localhost:8123/event
    at com.bimbr.clisson.client.SimpleHttpInvoker.post(SimpleHttpInvoker.java:50)
    at com.bimbr.clisson.client.AsyncHttpRecorder$EventSubmission.invoke(AsyncHttpRecorder.java:129)
    at com.bimbr.clisson.client.AsyncHttpRecorder$BufferProcessor.run(AsyncHttpRecorder.java:139)
    at java.lang.Thread.run(Thread.java:619)
Caused by: java.net.BindException: Address already in use: connect
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
    at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
    at java.net.Socket.connect(Socket.java:525)
    at org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:123)
    at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:148)
    at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:150)
    at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:121)
    at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:575)
    at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:425)
    at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)
    at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:754)
    at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:732)
    at com.bimbr.clisson.client.SimpleHttpInvoker.sendRequest(SimpleHttpInvoker.java:60)
    at com.bimbr.clisson.client.SimpleHttpInvoker.post(SimpleHttpInvoker.java:46)
    ... 3 more

Make buffer size configurable

And point to that config property in the exception thrown when the buffer fills up.

Ensure pending events are sent to the server when JVM shuts down

Ensure HTTP connection is closed gracefully when the JVM shuts down

Related to mmakowski/clisson-server#9

Can the clisson.properties supports placeholder from system variables

the server config supports placeholder from system variables
e.g. clisson.db.path=${java.io.tmpdir}/clisson-db

My application is running multiple instance with different runtime parameters; suppose the client can support the same for the componentId, it might be able to save some efforts in setting up the client.
(Now I have to use diff clisson.properties for the application instances)