Server LogSpring Web Socket Config
I developed Chat application and deployed in linux server and I have Deskrom Desk Support application to send chat messages, Chat Server is started with out any error. I am using Web Sockets Stomp protocol.
After I sent message from Desk application the messages are saving in Chat application but in the middle I am getting the above attached Broken Pipe exception.
Please help me to fix the problem.
Related
Is it possible to create an app that provides a REST API and a TCP/IP socket connection interface. I'm new to web related programming but I do have a REST API demo program working and I have created socket servers in the past. I need to create an app that can receive messages via a REST API and forward the message to a machine that is connected via the socket connection. I am working in C# with Visual Studio 2022.
Thank you.
I have a chat app having web service installed on tomcat server, ejabberd as XMPP server. Right now i am using strophe.js on client side to directly communicate with ejabberd server for chatting purpose.
Is this correct chat app design ? or shall I send chat through tomcat server so that xmpp server is not accessible directly from client side ? Can anyon suggest a better design ?
You should connect your clients directly to ejabberd (or through a proxy like NGinx). ejabberd is designed to receive lot of traffic directly and using Tomcat as proxy will not be scalable and is not recommended.
I am creating chat application that will connect to facebook chat via XMPP. I installed eJabberd server, and, I am looking for a way to to hook to messages that comes from the client in order to add the access token and the api key/secret to the message before I am sending it to facebook, and I can't figure out how to do it, is it via one of the pre defined ejabber modules, or I need to develop one?
** I can connect with pidgin to facebook xmpp using the eJabberd server I installed.
Thanks.
I've implemented pub/sub framework using ASP.NET, WCF Service with net.tcp binding. I hosted wcf service on IIS7.5. My code was developed under VS2010, Windows7.
My demo application is working fine but I just want to handle the error exception when my wcf service callback to client.
So far, my WCF Service or ASP.NET did not throw any error to screen at all.
here is my step of testing:
started service
opened 2 IE (e.g. UserA and UserB)
both User subscribed to WCF Service
closed UserB (closed IE of B)
tried to send msg from UserA to UserB
UserA could send msg to B but no error was appeared
I expected that it should be some error appear to my face but no...
please suggest me how to handle this case?
Thank you
The connection/client lives in IIS on that machine, not your browser. Closing IE will not necessarily close the client instance, meaning the callback will still succeed. If you want to tie the instance to IE, you need to use something like Silverlight to host the callback functionality. Then you should be able to see the behavior you are looking for.
I'm maintaining web server software on which users can deploy web applications. Web applications run as separate processes: the web server launches a web application process, forwards the HTTP request to the web application, and forwards the web application's response back to the HTTP client. The communication between the web server and the web application happens through sockets.
Some users (= web application developers) report that they occasionally get mysterious EIO errors when they write to the socket that connects their web application to the web server (at least, they think it's writing to the socket that causes the error). Some others report that they get this error as well when writing something to STDERR (which is redirected to a log file). Restarting the web server and the web application "fixes" this problem for a short period of time.
What does EIO mean? I know the manual says "Input/output error" but this description is as vague as it can get. Under what circumstances can it occur and how is it different from ECONNREFUSED/EPIPE/ENOTCONN/etc?
Well, apparently EIO can occur when trying to write to a disconnected console device.