Problem with two process communicating via sockets

[sai_kumar]

Hi all,
I am working on application where two process should communicate via sockets, with one process ( process A running as back gound process ) creates a socket and listens and other process ( Process B) will connect to that socket and communicate.
I am facing crash when RSocketServ::Connect() is called in both process's. The code is

Process A :
{
RSocketServ socketServ;
RSocket listener,blanksocket;
TSockAddr iAddr(KInetAddrAny);
iAddr.SetPort(80);

socketServ.Connect(); // crash with exit type 2,0
listener.Open(socketServ, KAfInet,KSockStream, KProtocolInetTcp);

listener.Bind (iAddr);

listener.Listen (1);

TRequestStatus aStatus;
listener.Accept (blanksocket,aStatus);
User::WaitForRequest(aStatus);
}



Process B:
{
RSocketServ socketclientServ;
RSocket clientsocket;
TRequestStatus Status;

TSockAddr iAddr(KInetAddrAny);
iAddr.SetPort(80);


socketclientServ.Connect(); // crash with exit type 2,0

// Open a TCP socket
clientsocket.Open( socketclientServ,KAfInet,KSockStream, KProtocolInetTcp ) ;

// Initiate socket connection
clientsocket.Connect( iAddr, Status );
}

Am i missing some thing which has to be done before RSocketServ::Connect? Is there any specific port no. for two process on the same system to communicate.

[jsm_s60]

Are you testing on emulator ?

or

Are you testing on device ? If yes which device ?

[sai_kumar]

I am working on Device (OMAP board)

[wizard_hu_]

I am working on Device (OMAP board)

That is nice. However getting the panic code would be even nicer. Normally you could get it as described on http://wiki.forum.nokia.com/index.ph...ded_panic_code
ExitType is one thing but RProcess has ExitCategory and ExitReason too, try getting them somehow.

And the problem itself is that you probably can not RSocket::Connect to KInetAddrAny (0.0.0.0), KInetAddrLoop may be a better pick (127.0.0.1) - note that Symbian is not Unix, socket-based IPC is not common, and you may face some side effects too (RSocket::Connect may decide to launch an IAP regardless of the fact that you are connecting to localhost).

[sai_kumar]

Thank you wizard_hu_ for your repply.

I was working with tshell image it doesn't worked (panic when RSocketServ::Connect() is called), but with S60 image it works( RSocketServ::Connect() is success and returned KErrNone) but it panicked when listener.Accept (blanksocket,aStatus); is called ( Exit type 2,0 Esock client ).Can you please help me why Accept is panicking ?

What is the reason for panic when RSocketServ::Connect() is called in tshell image and no panic in s60 image?

[wizard_hu_]

Oh, I confused RSocketServ::Connect with RSocket::Connect, sorry about that. If RSocketServ::Connect fails, you probably do not have Socket Server running.
Unfortunately "Esock client" panic category is not documented in the SDK Help, but there is one called "eSock", which says "client" a lot

Category: eSock panic
Panic of client from Sockets Server due to server error

From the TESockCliPanic enumeration.

0 Failed to create Sockets Server

I guess it may be correct, and the 2 in your message is TExitType, which is an enumeration of EExitKill,EExitTerminate,EExitPanic,EExitPending