problem in loading adapters in the new Lightstreamer 6.0

engcoder

hi,

i downloaded the new version Lightstreamer 6.0 and attach my adapter that worked fine in the previous version.
when i start the lightstreamer it gives the Exception :
java.lang.ClassNotFoundException: com.lightstreamer.adapters.remote.metadata.NetworkedMetadataProvider

this is my adapter.xml file


<?xml version="1.0"?>


<adapters_conf id="DataPool">


   <metadata_provider>
        <adapter_class>com.lightstreamer.adapters.remote.metadata.NetworkedMetadataProvider</adapter_class>
        <param name="request_reply_port">6663</param>
    </metadata_provider>
	
 
    <data_provider name="DataPool">
        <adapter_class>com.lightstreamer.adapters.remote.data.NetworkedDataProvider</adapter_class>
        <param name="request_reply_port">6661</param>
        <param name="notify_port">6662</param>
    </data_provider>
	


 <data_provider name="Intraday1">


<adapter_class>com.lightstreamer.adapters.remote.data.NetworkedDataProvider</adapter_class>


        
        <param name="request_reply_port">5661</param>


        <param name="notify_port">5662</param>




    </data_provider>




<data_provider name="Intraday2">


<adapter_class>com.lightstreamer.adapters.remote.data.NetworkedDataProvider</adapter_class>


        
        <param name="request_reply_port">7661</param>


        <param name="notify_port">7662</param>




    </data_provider>


</adapters_conf>

Gianluca Finocchiaro

Hi engcoder,

starting from Lightstreamer server v6.0, in the adapters.xml configuration file you need to replace the old class names com.lightstreamer.adapters.remote.metadata.NetworkedMetadataProviderand com.lightstreamer.adapters.remote.data.NetworkedDataProvider with one of the two brand new reserved names: PROXY_FOR_REMOTE_ADAPTERor ROBUST_PROXY_FOR_REMOTE_ADAPTER (depending on your needs).

So, with regard to your example, the metadata_provider section will be modified as follows:

<metadata_provider>
  <adapter_class>[B]PROXY_FOR_REMOTE_ADAPTER[/B]</adapter_class>
  [B]<classloader>log-enabled</classloader>[/B]
  <param name="request_reply_port">6663</param>
</metadata_provider>

and all the data_provider sections become:

<data_provider name="DataPool">
  <adapter_class>[B]PROXY_FOR_REMOTE_ADAPTER[/B]</adapter_class>
  [B]<classloader>log-enabled</classloader>[/B]
  <param name="request_reply_port">6661</param>
  <param name="notify_port">6662</param>
 </data_provider>

You can get more information here:

Adapter Remote Infrastructre changelog
Updated .NET Adapter demos and related full source code available on GitHub
The generic template, available under
DOCS-SDKs/adapter_generic_infrastructure/doc/adapter_conf_template/adapters.xml
or
DOCS-SDKs/adapter_generic_infrastructure/doc/adapter_robust_conf_template/adapters.xml,
of the Lightstreamer distribution.

Hope this helps.

Regards,
Gianluca

engcoder

hi,

i do the replace but another error appears : Error while loading the Adapters: {}. com.lightstreamer.init.b: Common ClassLoader not supported for a Proxy Adapter

Gianluca Finocchiaro

Hi engconder,

thanks for reporting the issue. As you can read from the adapters.xml template available under DOCS-SDKs/adapter_generic_infrastructure/doc/adapter_conf_template or DOCS-SDKs/adapter_generic_infrastructure/doc/adapter_robust_conf_template of the Lightstreamer distribution, for Proxy Adapters it is also mandatory to specify the classloader both in the metadata_providerand in the data_provider configurations. In such case, as stated in the comment, it is advisable to use the special "log-enabled" option, as follows:

<metadata_provider>
  <adapter_class>PROXY_FOR_REMOTE_ADAPTER</adapter_class>
  [B]<classloader>log-enabled</classloader>[/B]
  <param name="request_reply_port">6663</param>
</metadata_provider>

<data_provider name="DataPool">
  <adapter_class>PROXY_FOR_REMOTE_ADAPTER</adapter_class>
  [B]<classloader>log-enabled</classloader>[/B]
  <param name="request_reply_port">6661</param>
  <param name="notify_port">6662</param>
</data_provider>>

Such configurations are required because of newly introduced Classloader separation in Lightstreamer 6.0: you can get more on this here.

For the sake of completeness, I have also modified the previous reply, inserting the same tag as above.

Get back to us for any further issue.

Regards,
Gianluca

engcoder

it works that the LS load the adapters confg. from xml succefully and open all the ports but when running the first adapter application (i have 3 adapters as shown previous at xml file) , the LS gives the following Exception

<ERROR> Exception caught while trying to initialize the Remote Server
com.lightstreamer.adapters.proxy.RemotingException: Timeout while waiting for an
answer to request 10000014b30b1c427
at com.lightstreamer.adapters.proxy.request_reply.RequestSender.dequeueT
imeoutChecks(RequestSender.java:291) ~[ls-proxy-adapters.jar:na]

Gianluca Finocchiaro

Hi,

how long does it take to make the first request after the initial connection by the remote Adapter? Consider that default timeout is 10 seconds, as you can read from the adapters.xml template:

 <!-- Optional.
        Timeout for sent requests. A negative value stands for an unlimited timeout.
        Timed out requests are considered as failed and later answers are ignored.
        Default: 10000 ms (10 seconds). -->
<!--
<param name="timeout">10000</param>
-->

Could you please check the remote Adapter flow?

Regards,
Gianluca

engcoder

thanks for reply,
the adapters is loaded when i changed Y to N
but the LS gives Exception after connecting to the ports :

<ERROR> Exception caught while trying to initialize the Remote Servercom.lightstreamer.adapters.proxy.RemotingException: Timeout while waiting for an
answer to request 10000014ccb4c5f0a

Gianluca Finocchiaro

Discussion goes on here