.NET Standalone Adapter with Client

[wattsw]

I have created two adapters one that is Piped mode launched by the DotNetServer_N2. The other is a stadalone socket adapter following the guidance provided in the pdf and on the posted thread with the similar subject on standalone adapter. I have created a client that works fine with the Piped mode adapter but it gets a timeout error with the socket mode. I created an adapter.xml file that has the same port definitions as defined in the server code. I have provided the following listings:

1. The output from the LS server log file (Included here)
2. The standalone application code that creates the server and adapter. (as attachment)
3. The client side application. (as attachment)

It would be greatly appreciated if anyone could provide any insight as to the timeout or provide a complete server/client standalone example.

Thanks you in adavance for you support.

Output from Log File

12-Nov-06 12:40:44,709 |INFO |LightstreamerLogger.license |main |This is a trial version.
12-Nov-06 12:40:47,463 |INFO |LightstreamerLogger.init |main |Lightstreamer Server starting in Vivace edition
12-Nov-06 12:40:47,523 |INFO |LightstreamerLogger.init |main |Started HTML Adaptor for JMX on port 6666
12-Nov-06 12:40:47,674 |INFO |LightstreamerLogger.init |main |Started JMXMP Connector for JMX on port 9999
12-Nov-06 12:40:47,904 |INFO |.remote.transport.SocketTransport|main |Connecting...
12-Nov-06 12:42:37,161 |INFO |.remote.transport.SocketTransport|main |Connected
12-Nov-06 12:42:37,181 |INFO |.remote.transport.SocketTransport|main |Connecting...
12-Nov-06 12:42:37,181 |INFO |emote.request_reply.RequestSender|NMSTESTMETA Request Sender |Request sender 'NMSTESTMETA' starting...
12-Nov-06 12:42:37,191 |INFO |mote.request_reply.NotifyReceiver|NMSTESTMETA Reply Receiver |Reply receiver 'NMSTESTMETA' starting...
12-Nov-06 12:42:37,221 |INFO |.remote.transport.SocketTransport|main |Connected
12-Nov-06 12:42:37,241 |INFO |mote.request_reply.NotifyReceiver|NMSTESTDATA Notify Receiver|Notify receiver 'NMSTESTDATA' starting...
12-Nov-06 12:42:37,241 |INFO |emote.request_reply.RequestSender|NMSTESTDATA Request Sender |Request sender 'NMSTESTDATA' starting...
12-Nov-06 12:42:37,271 |INFO |mote.request_reply.NotifyReceiver|NMSTESTDATA Reply Receiver |Reply receiver 'NMSTESTDATA' starting...
12-Nov-06 12:42:37,281 |INFO |mote.transport.LocalPipeTransport|main |Spawning external command 'cmd.exe' on path './bin/'...
12-Nov-06 12:42:38,393 |INFO |emote.request_reply.RequestSender|TestMetadata Request Sender|Request sender 'NmsTestMetadata' starting...
12-Nov-06 12:42:38,393 |INFO |mote.transport.LocalPipeTransport|main |Spawning external command 'cmd.exe' on path './bin/'...
12-Nov-06 12:42:38,403 |INFO |mote.request_reply.NotifyReceiver|TestMetadata Reply Receiver|Reply receiver 'NmsTestMetadata' starting...
12-Nov-06 12:42:39,444 |INFO |mote.request_reply.NotifyReceiver|estListData Notify Receiver|Notify receiver 'NmsTestListData' starting...
12-Nov-06 12:42:39,454 |INFO |emote.request_reply.RequestSender|TestListData Request Sender|Request sender 'NmsTestListData' starting...
12-Nov-06 12:42:39,454 |INFO |mote.request_reply.NotifyReceiver|TestListData Reply Receiver|Reply receiver 'NmsTestListData' starting...
12-Nov-06 12:42:39,564 |INFO |LightstreamerLogger.init |main |Lightstreamer Server 3.3.4 build 1289 starting...
12-Nov-06 12:42:39,675 |INFO |LightstreamerLogger.init |main |Lightstreamer Server listening to *:8080 ...
12-Nov-06 12:43:05,031 |INFO |LightstreamerLogger.connections |SERVER POOLED THREAD 1 |Accepted HTTP connection from 127.0.0.1:1118
12-Nov-06 12:43:05,372 |INFO |LightstreamerLogger.requests |SERVER POOLED THREAD 2 |Serving request: /lightstreamer/create_session.txt?LS_adapter=NMSTEST2 from 127.0.0.1:1118
12-Nov-06 12:43:05,452 |INFO |LightstreamerLogger.requests |SERVER POOLED THREAD 2 |Starting new session: S1798301506N1 from 127.0.0.1:1118
12-Nov-06 12:43:07,505 |INFO |LightstreamerLogger.connections |SERVER POOLED THREAD 3 |Accepted HTTP connection from 127.0.0.1:1123
12-Nov-06 12:43:07,515 |INFO |LightstreamerLogger.requests |SERVER POOLED THREAD 4 |Serving request: /lightstreamer/control.txt?LS_op=add&LS_schema1=equipName+status& LS_mode1=MERGE&LS_session=S1798301506N1&LS_Snapsho t1=true&LS_window=1&LS_start1=1&LS_id1=item1+item2 +item3&LS_end1=30 from 127.0.0.1:1123
12-Nov-06 12:43:07,575 |INFO |LightstreamerLogger.requests |SERVER POOLED THREAD 4 |Controlling session: S1798301506N1 from 127.0.0.1:1123
12-Nov-06 12:43:07,705 |INFO |LightstreamerLogger.connections |SERVER POOLED THREAD 5 |Reused HTTP connection from 127.0.0.1:1123
12-Nov-06 12:43:16,327 |INFO |LightstreamerLogger.connections |SERVER POOLED THREAD 6 |Closed HTTP connection from 127.0.0.1:1123
12-Nov-06 12:43:16,768 |INFO |LightstreamerLogger.connections |PUMP POOLED THREAD 1 |Closed HTTP connection from 127.0.0.1:1118
12-Nov-06 12:43:40,041 |INFO |LightstreamerLogger.connections |SERVER POOLED THREAD 8 |Accepted HTTP connection from 127.0.0.1:1124
12-Nov-06 12:43:40,392 |INFO |LightstreamerLogger.requests |SERVER POOLED THREAD 9 |Serving request: /lightstreamer/create_session.txt?LS_adapter=NMSTEST from 127.0.0.1:1124
12-Nov-06 12:45:20,396 |ERROR|LightstreamerLogger.requests |SERVER POOLED THREAD 9 |Unexpected error
com.lightstreamer.adapters.remote.RemotingExceptio n: Request 10000010eddb15869 timed out
at com.lightstreamer.adapters.remote.request_reply.Re questSender.sendRequest(RequestSender.java:180)
at com.lightstreamer.adapters.remote.request_reply.Re questSender.sendRequest(RequestSender.java:141)
at com.lightstreamer.adapters.remote.metadata.RemoteM etadataProvider.requestNotifyUser(RemoteMetadataPr ovider.java:158)
at com.lightstreamer.adapters.remote.metadata.RemoteM etadataProvider.notifyUser(RemoteMetadataProvider. java:345)
at com.lightstreamer.d.j.a(j.java)
at com.lightstreamer.d.h.<init>(h.java)
at com.lightstreamer.f.p.a(p.java)
at com.lightstreamer.f.p.a(p.java)
at com.lightstreamer.f.k.a(k.java)
at com.lightstreamer.g.f.a(f.java)
at com.lightstreamer.g.f.a(f.java)
at com.lightstreamer.g.j.a(j.java)
at com.lightstreamer.g.j.b(j.java)
at com.lightstreamer.c.g.a(g.java)
at com.lightstreamer.c.g.a(g.java)
at com.lightstreamer.c.q.a(q.java)
at com.lightstreamer.h.nb.run(nb.java)
at com.lightstreamer.h.wb.a(wb.java)
at com.lightstreamer.h.xb.run(xb.java)
12-Nov-06 12:45:20,396 |INFO |LightstreamerLogger.connections |SERVER POOLED THREAD 9 |Failed request from 127.0.0.1:1124
12-Nov-06 12:45:20,396 |ERROR|LightstreamerLogger.connections |SERVER POOLED THREAD 9 |Failure in request processing
com.lightstreamer.f.hb: com.lightstreamer.adapters.remote.RemotingExceptio n: Request 10000010eddb15869 timed out
at com.lightstreamer.f.k.a(k.java)
at com.lightstreamer.g.f.a(f.java)
at com.lightstreamer.g.f.a(f.java)
at com.lightstreamer.g.j.a(j.java)
at com.lightstreamer.g.j.b(j.java)
at com.lightstreamer.c.g.a(g.java)
at com.lightstreamer.c.g.a(g.java)
at com.lightstreamer.c.q.a(q.java)
at com.lightstreamer.h.nb.run(nb.java)
at com.lightstreamer.h.wb.a(wb.java)
at com.lightstreamer.h.xb.run(xb.java)
12-Nov-06 12:45:20,396 |INFO |LightstreamerLogger.connections |SERVER POOLED THREAD 10 |Closed HTTP connection from 127.0.0.1:1124

[DarioCrivelli]

For some reason, the Remote Server which runs the Remote Metadata Adapter, after correctly connecting with the Proxy Adapter, seems either not to receive the commands, or not to respond.
Unfortunately, the Remote Server does not log its read-write activity, so a sniffing is needed in order to discriminate the two cases.

I tried to replicate the problem, but the two (piped and networked) adapter pairs work in my installation. May you please also show your adapters.xml configuration files for the two adapter pairs (i.e. NMSTEST and NMSTEST2) and the command lines for the two Remote Servers (i.e. for the Metadata Adapter and Data Adapter of NMSTEST)?

By the way, launching the Remote Server for the Remote Metadata Adapter but configuring it with the class for the Remote Data Adapter would reproduce the exception.

[wattsw]

I found the problem. When I was naming the metadata and data servers I was naming them the same as the adapter name in the adapter.xml. When I named them to something unique, it works. I believe this thread can be closed.

Thanks