Search:

Hi Antonio,

please have a look here.

Our recommendation is to specify all VM Arguments, in order to avoid any issue you may have with class loading.

Thanks and Regards,
Gianluca

Hi Antonio,

a similar procedure should be doable on IntelliJ IDEA as well and a detailed post on this is coming soon, stay tuned!

Thanks and Regards,
Gianluca

Hi nttam,

after having looked at the log and exchanged some private messages, we finally found out that the issue was due to a conversion of raw data sent by the middleware. In fact, raw data...

Hi mttam,

the image is not clear. Please stop the server instance and remove the current Lightstreamer.log, just to start from clean scenario.
Please also update the lightstreamer_log_conf.xml...

Ok nttam,

could you please provide us with a log excerpt from which such it is possible to analyze such issue?

Thanks
Gianluca

Hi nttam,

just to clarify the current scenario: the middleware sends "data" to the adapter and, from there, are forwarded to the clients, is it correct? So, on the client side such data appear in...

Hi nttam,

could you please provide us with some examples of error in terms of sent and received data?

Thanks
Gianluca

Hi nttam,

provided that you left the <classloader> value to its default value ("common") in the adapters.xml files relative to the involved Adapter Sets, you have to put common classes and...

Hi nttam,

I'm sorry but it is not clear to me what you mean by "not independently adapters". If you have already prepared the adapter folder (where also the appropriate adapters.xml is expected to...

Follow these instructions for developing and running an Adapter Set using Eclipse:


Create a new Java Project

Add the ls-bootstrap.jar and ls-adapter-interface.jar files taken from...