Server-Push

I read somewhere that Flex Data Services provides Server-Push
functionality. That is, the server starts a conversation with the
client. It's obvious that, In order to such thing ocurr, there has
to be a persistent connection between server and client.
I've being reading about Data Management Service to learn how
to implement this Server-Push and all I see is about a method
called Fill() that is thriggered from the client and syncronizes
it's data with the server. But it's not server-push
Does it really exist?

Hi,
When you create a DataService and fill your collection. The
collection becomes managed. You don't have to call fill again if
there is any change in the data. Server pushs updates to clients
when the client's dataservice is using rtmp channel. It is a live
connection between the server and the client. For example,
you fill(collection, "hqsql", from products where price <
100). If one of the product's price increases, server push a
message to your collection to remove it. If a product's product's
price decrease, it will be added to the collection. The push is
happened based on your fill method.
William Chan

Similar Messages

  • Using the new Data/Services generation with server push

    Have moved my Flex/BlazeDS app (which uses Blaze AMFChannel for request/response messages and StreamingAMFChannel for server push messaging) from Flex Builder 3 to Flash Builder 4. The new Data/Services works fine to generate service classes and value objects for the request/response messages, question is can it provide any help setting up a messaging consumer and value objects for the pushed data?
    rick holland

    I am so sorry - I meant AirPort Express - not extreme - but it's moot since I missed the point of your post - you want two outputs - and one to not be digital.
    For what it's worth - I still think the express might be your best bet.
    http://www.apple.com/airportexpress/airtunes.html
    It has combined digital/analog out - you plug in one and it switches the output depending on which connection is inserted. I would expect a very short wait until everything accepts digital input - expecially for people who want good sound quality. If you have to go digital to analog outside of the receiver/amp (where it really belongs) - why not let it be the express sitting right next to where you want the second "receiver" to be...

  • Server Push redirecting to a pre-existing JSP

    Question:
    Has anyone tried to create a Server Push servlet that can be used to serve up pre-existing JSPs?
    Is it even possible for a servlet to serve a pre-existing JSP or does the web page code have to be embedded within the servlet?

    Hi, do you mean you want to redirect to another JSP?
    you could use the "sendRedirect" method in the HttpServletResponse object.
    for example:
    public MyServlet perform(...HttpServletRequest request, HttpServletResponse response)
         throws IOException, ServletException {
      String redirectTo = "http://www.companyname.com/index.jsp";
      response.sendRedirect(redirectTo);
    }something like that....

  • Server Push in JSP

    Hi AnyOne!
              I have a jsp, and a database . If a column in my table gets updated I
              want all of my clients who are connected to it , to see the refreshed value
              without click any refresh/Reload button on the browser. A kind of
              Server-Push.
              That is, If one client makes changes, then all of the other clients on the
              web should get intimated.
              How can I achieve this ?
              thanks
              vikas
              

    Vikas,
              There was a article about the same in java world a while back.
              http://www.javaworld.com/javaworld/jw-03-2000/jw-03-pushlet.html
              But I believe this is bad design. I don't think using opened HTTP Connections
              to do a real time operation is not a good Idea. What if you are serving couple
              of hundred clients?
              Kumar.
              Vikas Jolly wrote:
              > Hi AnyOne!
              >
              > I have a jsp, and a database . If a column in my table gets updated I
              > want all of my clients who are connected to it , to see the refreshed value
              > without click any refresh/Reload button on the browser. A kind of
              > Server-Push.
              > That is, If one client makes changes, then all of the other clients on the
              > web should get intimated.
              >
              > How can I achieve this ?
              >
              > thanks
              > vikas
              

  • Implementing Server Push using LCDS 2.6

    Hi All,
    We have created an application where we are using polling to get certain constant updates. Now this polling is client polling wherein the client polls the server at regular intervals to get the fresh data for certain actions.
    Now we wish to take this to another level and implement Server Data Push so that the client does not keep polling unnecessarily and the server notifies the client as and when the data gets updated with the server. For this we have the DataService Transaction class that needs to be implemented.
    But there are a couple of questions that are in my mind regarding this technology. It would be great if someone could answer them.
    My questions are:
    1) Does the LCDS server know which client to push data to in case of multiple clients looking at the same data scenario. e.g. Two clients A and B are looking at the same data. A performs an action and that action needs some time to get completed at the server. Now in case we use Server Data Push, will the LCDS be intelligent enough to send the message on completion of the requested activity to only A and not B.
    2) In order to push data to the client, the server will invoke some method which will return the desired data to te client. How do we keep the parameters registered with the server that this method would need while getting invoked. SInce, the call to the method will not be client initiated, how does the server know what parameters to be passed to the method in order to invoke it. How will this work in a multi-user looking at the same data/screen scenario.
    The answers to these questions will really help us. In case anyone is well versed with this technology, please pitch in to give your inputs.
    Many Thanks.
    Regards,
    Shally

    Hi,
    As also, suggested by you, we were thinking of using an RTMP channel only for this since its a two way socket that establishes a communication channel between the client and the server and then helps keep messages moving to and fro.
    We have successfully implemented RTMP channel and achieved the following functionalities.
    1) A client initiated change which gets propagated to the server and then to all the clients.
    2) Server push to all the clients.
    Now our last step is to implement data push to a particular client. As told by you, we will use the client id but we have some doubts and questions regarding this since we do not have the code examples or anything that could help us in implementing the same.
    I would therefore request you to kindly lead us on the following fronts:
    1) Is the client id the one that is part of the request- response thread, I saw a client id being printed in the logs when a request is made and the response comes.
    2) What code needs to be written on the server side to extract this client id once a call is made so that it can keep this client id with itself to push a message later on.
    3) What methods or API are available to be used to push this message to a particular client? Do we need to call the fill method of a particular client using the client id parameter and inform the client that its requested job has been done.
    For (3) is the Messaging(Publish and Subscribe model) the right way to go??
    It would be great if you could provide us some code snippets just to give us an idea from where we can take it up ourselves.
    Looking forward to hear from you.
    Many Thanks,
    Shally
    Message was edited by: testing34

  • Implementing Server Push

    How can i implement a server push in my jsp pages?
    any sample code would be appreciated.
    The server pushes the data to the jsp when the
    database changes because of an update.
    Thanks

    Http is a stateless protocol and cannot maintain a connection to the server. I am working on a project now that has the same type of requirement and we are using pushlet technology. You should have a look at the following
    www.pushlets.com
    Hope this helps
    SD

  • Server Push Intermittent message loss

    We are using LCDS 2.6 and using the RTMP port for the server push. However, at times the notifications in between the server to clients goes missing. It works pretty good at times and after some time, it does not shows notification.
    We are using DataTransactionServices for pushing the data from LCDS to the Flex clients.

    Hello,
    We are still facing the intermittent issue with LCDS. Following steps has been done:
    1. We tried different values in DataDestination property like autoSyncEnbaled , cache items and some other properties, but it did not work.
    2. We analysed LCDS logs in log file and found that :
       a. Java Code is pushing updated state to LCDS and message is also routing to client.
       b. At client side UI is receiving old data from LCDS.
    Do you have any idea, why is this happening?
    Gaurav Shukla
    Senior Technical Architect -ADCOE
    HCL Technologies Ltd.
    SEZ, Plot No. 3A, Sector 126, Noida 201301, U.P. (India)
    Mob: +91-9899 89 9189
    www.hcltech.com<http://www.hcltech.com>
    www.hcl.com<http://www.hcl.com>
    cid:[email protected]

  • Server push / Client pull

    Hi,
    Please let me know about Server push and Client pull . When this has to be needed. please explain.
    Thanks in advance.

    google ...

  • Server Push   pushing data to clients

    Need some ideas.
    I have been hunting around for info on a simple/clean method
    to push data out to clients. Client could be a Java application or maybe an applet. Solution must easily go through firewalls
    In either case I want the client to startup, register with the server
    and start receiving data. Without further user intervention.
    Whatever, scheme is used must be able to deal with network
    disconnects.
    I have looked at Pushlets, the article was 2 years old and I don't see
    any recent postings on Pushlets. So maybe that is not the way to go.
    I guess my other choice is JMS. SonicMQ?
    Server Push using Netscape?
    Or are there other options.
    Many thanks for your feedback.
    KD

    Have you considered J2ME.
    J2ME and WAP Push can be complementary. but for WAP Push to work the devices or the browsers in the devices have to be WAP 1.2 complaint.
    more details can be found at http://devforum.openwave.com
    hope this helps.
    williams

  • Server Push in Servlets

    Hi AnyOne!
              I have a servlet, and a database . If a column in my table gets updated I
              want all of my clients who are connected to it , to see the refreshed value
              without click any refresh/Reload button on the browser. A kind of
              Server-Push.
              That is, If one client makes changes, then all of the other clients on the
              web should get intimated.
              How can I achieve this ?
              thanks
              vikas
              

    I read the OP's message and imediately thought oh, cool, MVC candidate :-)          If I wanna talk about MVC I would prefer Sun's Design Patterns group.
              Kumar.
              [email protected] wrote:
              > "Mettu Kumar" <[email protected]> wrote in message
              > news:[email protected]...
              > > Ryan,
              > >
              > > I was not commenting on MVC pattern. I am talking about the problems
              > > pushlets implementation could potentially cause.
              >
              > Mettu, we completly crossed paths my friend. I read the OP's message and
              > imediately thought oh, cool, MVC candidate :-) Silly me! I understand what
              > you are talking about now :-)
              >
              > > 1. If you are serving 10,000 clients, probably a given instance your
              > server will
              > > be serving 100 or 1000 of the them. but with pushlets you have 10, 000
              > > conenctions open siumultaneously and your server is serving all the client
              > 100%
              > > of the time.
              >
              > No, you're right that isn't good.
              >
              > > Do you think this would scale? Imagine the number of threads on server.
              > > 2. This could potentially bring down the web server you are using.
              > >
              >
              > It would scale right up to the time the server came crashing down :-) Yes,
              > if the server kept a single connection, thread of execution, open to every
              > client while the client was running that would be not so hot indeed,
              > especially if your clients increased exponentially. This is precisely why I
              > like the callback method on each client, kind of a pain to implement though.
              >
              > >
              > > Kumar.
              > >
              > > [email protected] wrote:
              > >
              > > > I wasn't referring to the article on pushlets you mentioned when I said
              > the
              > > > idea of MVC was a valid one, nor have I read the article as I respond
              > but
              > > > heres the idea I was describing which is based on the concept of MVC.
              > It
              > > > provides perfectly for the scenario the OP described IMO. I think, at
              > least
              > > > based on what I've seen, that the notion of MVC in the J2EE sector is
              > used
              > > > mostly as a means to seperate business logic from presentation logic.
              > It
              > > > doesn't allow for any mechanisms to notify the ``views" when data
              > ``model"
              > > > changes. This is no big deal I guess for most applications but it does
              > > > break the MVC paradigm IMO. To aleiviate this problem we incorporate an
              > > > observer pattern to notify each subscribing view when the model changes.
              > > > There really isn't any difference in my mind between push and pull where
              > > > pull is a standard RFC 2616 request and push is a simple callback to the
              > > > object registered with the controller (servlet, jsp). If the server can
              > > > handle a thousand or so concurrent requests why couldn't it handle a
              > > > thousand concurrent callbacks. You could probably improve this by
              > > > multi-threading the controller. Just some thoughts I would like to hear
              > > > yours :-)
              > > >
              > > > ~Ryan
              > > >
              > > > "Mettu Kumar" <[email protected]> wrote in message
              > > > news:[email protected]...
              > > > > Ryan,
              > > > >
              > > > > Did you ever try to use to Pushlets serving thousands of clients?
              > > > > Why did you think its a good design? If you feel its a good design,
              > let
              > > > us
              > > > > know whats good about it.
              > > > >
              > > > > Kumar.
              > > > >
              > > > > [email protected] wrote:
              > > > >
              > > > > > "Mettu Kumar" <[email protected]> wrote in message
              > > > > > news:[email protected]...
              > > > > > > Vikas,
              > > > > > >
              > > > > > > There was a article about the same in java world a while back.
              > > > > > > http://www.javaworld.com/javaworld/jw-03-2000/jw-03-pushlet.html
              > > > > > >
              > > > > > > But I believe this is bad design. I don't think using opened HTTP
              > > > > > Connections
              > > > > > > to do a real time operation is not a good Idea. What if you are
              > > > serving
              > > > > > couple
              > > > > > > of hundred clients?
              > > > > > >
              > > > > > > Kumar.
              > > > > > >
              > > > > >
              > > > > > It's a perfectly valid design. OP, check out MVC and the observer
              > > > design
              > > > > > pattern I think you'll find what you're looking for there.
              > > > > >
              > > > > > ~Ryan
              > > > > >
              > > > > > > Vikas Jolly wrote:
              > > > > > >
              > > > > > > > Hi AnyOne!
              > > > > > > >
              > > > > > > > I have a servlet, and a database . If a column in my table gets
              > > > updated
              > > > > > I
              > > > > > > > want all of my clients who are connected to it , to see the
              > > > refreshed
              > > > > > value
              > > > > > > > without click any refresh/Reload button on the browser. A kind
              > of
              > > > > > > > Server-Push.
              > > > > > > > That is, If one client makes changes, then all of the other
              > clients
              > > > on
              > > > > > the
              > > > > > > > web should get intimated.
              > > > > > > >
              > > > > > > > How can I achieve this ?
              > > > > > > >
              > > > > > > > thanks
              > > > > > > > vikas
              > > > > > >
              > > > >
              > > > >
              > >
              

  • Server push with Javamail: idle() blocks

    Hi,
    today I tried to implement server push functionality in my mail application via Javamail.
    I did this by calling the following method everytime Javamail creates a new Folder instance for me:
    private void activateServerPush(Folder f) {
         if (f instanceof IMAPFolder) {
              final IMAPFolder ifo = (IMAPFolder) f;
              ifo.addMessageCountListener(new MessageCountListener() {
                   @Override
                   public void messagesAdded(MessageCountEvent arg0) {
                        DebugPrinter.print(this, "messagesAdded event called");
                        clear(false, true); // Clear cache
                        onMessageCountChanged();
                   @Override
                   public void messagesRemoved(MessageCountEvent arg0) {
                        DebugPrinter.print(this, "messagesRemoved event called");
                        clear(false, true); // Clear cache
                        onMessageCountChanged();
              MyThread thread = new MyThread() {
                   @Override
                   public void run() {
                        while (true) {
                             DebugPrinter.print(this, "Before idle");
                             try {
                                  ifo.idle();
                                  DebugPrinter.print(this, "After idle");
                             } catch (MessagingException e) {
                                  // TODO Auto-generated catch block
                                  e.printStackTrace();
                             DebugPrinter.print(this, "After idle try");
              // Start thread
              ServletThread.EXECUTOR_SERVICE.submit(thread);
    }Now, when I run the code above, I only get "Before idle" as output.
    The rest won't be printed so it seems like idle() is blocking.
    Also, the event listener messagesAdded(...) are not called. I tried this by sending an email to myself but nothing happens.
    What's wrong?

    Hi Bill and thanks for your reply.
    How does the idle command (line) look line in the debug output?
    I simply did a full text search for the word "idle" (ignore case) of everything that got printed to console and only found this:
    DEBUG: mail.imap.minidletime: 10
    * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS AUTH=PLAIN AUTH=LOGIN
    A2 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS] Logged in
    Also, I noticed that the line "Before idle" (See source code in my initial posting here) gets printed but AFTER that line I can't find anything else that could refer to the idle command.
    When I leave Apple Mail (my default native email client on my computer) open, the email that I sent gets correctly (instantly) pushed.

  • How to use server push technology

    I need to write a Chatroom by using Server-push technology. Who would like to offer some information about this technology for me? Thanks!!

    Define "server-push" technology.client-pull is where the client pulls, via a specific request, information from the server.
    Server-push is where the server pushes information to a client when that information becomes available. The client does not initiate the exchange.

  • Which tech can replace applet to implement server push model

    We have implemented server push real-time datas to client with Applet+JSObject. but there is a thing we can not do well. When some users have intalled jre not same with our default, the applet run fail. So we are finding another tech to implement server push model.
    Any suggestions!
    client polling to emulate server push is cancelled.
    Thanks very much!

    linuxhippy wrote:
    well you can do it with polling - i have implemented such a system and it works very well.how many clients do your system support ?
    polling period ?
    what third-party libs ?

  • 10.4 Server - software update server - push to clients

    Hello all, after some advice.
    Weve recently built up a 10.4.7 Server running among other services, Software Update. We've been successfull in pushing out managed pref's to clients to retarget their update server etc, updates are working so thats fine..
    heres the issue. most of our mac clients arent admins, they are regular users, thus every time an update needs to install - it will prompt for an admin user's credentials, which we cant have happening.
    Is there a way, to configure either the update server or the clients, to receive updates and install them silently for instance? with no user intervention?
    One way im considering, its a bit messy though, is using apple remote desktop to issue a UNIX command to all selected Mac's, telling them to launch 'softwareupdate -i -r' and execute as root (afaik, you need to be root to execute softwareupdate manually or something) But this seems flaky in testing so far.
    Thanks for any help.
    Eliot.

    Excellent thanks for the suggestions guys... Ive been playing with the cron suggestion to begin with, it seems to work, as in it will download and install recommended updates. Although with the particular update I was trying to install, it didnt seem to follow through correctly.
    it was the latest firmware update for the INTEL iMac's, according to software update via the terminal, it had downloaded and installed the update, and then required a reboot. ok, but after reboot, it hadnt kicked into the firmware install mode. I actually had to download this update via the gui software update in order for it to function correctly, ie reboot, install firmware, reboot again. which is odd?? could be a problem for future updates like this, when using an automated cron task for updates? Or am I just missing something, hehe?
    Otherwise yeah, the ARD option sounds interesting, we're about to purchase ARD3, definately worth a look.

  • Someone please help me repair my Lion Server Push Notify

    This is the errors I receive when turning of and back on iChat Server and iCal Server. If someone could help me figure out what is going on I would appriciate it.
    Push no longer works on desktop clients or iOS devices.
    Jan 18 07:46:23 golivepro jabberd/sm[18488]: version: jabberd sm 2.2.14-373.2
    Jan 18 07:46:23 golivepro jabberd/c2s[18490]: [golivepro.com] configured; realm=golivepro.com, registration disabled
    Jan 18 07:46:23 golivepro jabberd/c2s[18490]: attempting connection to router at 127.0.0.1, port=5347
    Jan 18 07:46:23 golivepro jabberd/c2s[18490]: [5] [router] write error: Broken pipe (32)
    Jan 18 07:46:23 golivepro jabberd/c2s[18490]: connection to router closed
    Jan 18 07:46:23 golivepro jabberd/c2s[18490]: attempting reconnect (3 left)
    Jan 18 07:46:23 golivepro jabberd/router[18489]: [127.0.0.1, port=5347] listening for incoming connections
    Jan 18 07:46:23 golivepro jabberd/sm[18488]: [golivepro.com] configured
    Jan 18 07:46:23 golivepro jabberd/sm[18488]: attempting connection to router at 127.0.0.1, port=5347
    Jan 18 07:46:23 golivepro jabberd/router[18489]: [127.0.0.1, port=52330] connect
    Jan 18 07:46:23 golivepro jabberd/router[18489]: [127.0.0.1, port=52330] authenticated as jabberd
    Jan 18 07:46:23 golivepro jabberd/s2s[18491]: attempting connection to router at 127.0.0.1, port=5347
    Jan 18 07:46:23 golivepro jabberd/router[18489]: [127.0.0.1, port=52331] connect
    Jan 18 07:46:23 golivepro jabberd/router[18489]: [127.0.0.1, port=52331] authenticated as jabberd
    Jan 18 07:46:24 golivepro jabberd/sm[18488]: connection to router established
    Jan 18 07:46:24 golivepro jabberd/router[18489]: [sm] online (bound to 127.0.0.1, port 52330)
    Jan 18 07:46:24 golivepro jabberd/router[18489]: [golivepro.com] online (bound to 127.0.0.1, port 52330)
    Jan 18 07:46:24 golivepro jabberd/sm[18488]: sm ready for sessions
    Jan 18 07:46:24 golivepro jabberd/s2s[18491]: connection to router established
    Jan 18 07:46:24 golivepro jabberd/router[18489]: [s2s] set as default route
    Jan 18 07:46:24 golivepro jabberd/router[18489]: [s2s] online (bound to 127.0.0.1, port 52331)
    Jan 18 07:46:24 golivepro jabberd/s2s[18491]: ready for connections
    Jan 18 07:46:24 golivepro Rooms[18497]: Starting up...
    Jan 18 07:46:24 golivepro Rooms[18497]: Loading persistent rooms from disk...
    Jan 18 07:46:24 golivepro Rooms[18497]: Finished loading rooms from disk
    Jan 18 07:46:24 golivepro Rooms[18497]: Connecting to XMPP server at 'golivepro.com' as 'rooms.golivepro.com'...
    Jan 18 07:46:24 golivepro jabberd_notification/c2s[2715]: [8] [::ffff:10.0.1.160, port=52338] connect
    Jan 18 07:46:24 golivepro jabberd_notification/c2s[2715]: SASL callback for non-existing host: golivepro.com
    Jan 18 07:46:24 golivepro jabberd_notification/c2s[2715]: [8] [::ffff:10.0.1.160, port=52338] disconnect jid=unbound, packets: 0
    Jan 18 07:46:24 golivepro push_notify[98]: notification server connect failed, will retry in 300 seconds
    Jan 18 07:46:25 golivepro jabberd/router[18489]: [127.0.0.1, port=52340] connect
    Jan 18 07:46:25 golivepro jabberd/router[18489]: [127.0.0.1, port=52340] authenticated as proxy65.golivepro.com
    Jan 18 07:46:25 golivepro jabberd/router[18489]: [proxy65.golivepro.com] online (bound to 127.0.0.1, port 52340)
    Jan 18 07:46:25 golivepro jabberd/c2s[18490]: attempting connection to router at 127.0.0.1, port=5347
    Jan 18 07:46:25 golivepro jabberd/router[18489]: [127.0.0.1, port=52341] connect
    Jan 18 07:46:25 golivepro jabberd/router[18489]: [127.0.0.1, port=52341] authenticated as jabberd
    Jan 18 07:46:25 golivepro jabberd/c2s[18490]: connection to router established
    Jan 18 07:46:25 golivepro jabberd/router[18489]: [c2s] online (bound to 127.0.0.1, port 52341)
    Jan 18 07:46:25 golivepro jabberd/c2s[18490]: [::, port=5222] listening for connections
    Jan 18 07:46:25 golivepro jabberd/c2s[18490]: [::, port=5223] listening for SSL connections
    Jan 18 07:46:25 golivepro jabberd/c2s[18490]: ready for connections
    Jan 18 07:46:27 golivepro jabberd/router[18489]: [127.0.0.1, port=52342] connect
    Jan 18 07:46:28 golivepro jabberd/router[18489]: [127.0.0.1, port=52342] authenticated as rooms.golivepro.com
    Jan 18 07:46:28 golivepro jabberd/router[18489]: [rooms.golivepro.com] online (bound to 127.0.0.1, port 52342)
    Jan 18 07:46:28 golivepro Rooms[18497]: Successfully connected to XMPP server, ready for activity
    Jan 18 07:47:38 golivepro org.calendarserver.calendarserver[18600]: Reading configuration from file: /etc/caldavd/caldavd.plist
    Jan 18 07:47:38 golivepro org.calendarserver.calendarserver[18600]: Neither EnableCalDAV nor EnableCardDAV are set to True.
    Jan 18 07:47:38 golivepro com.apple.launchd[1] (org.calendarserver.calendarserver[18600]): Exited with code: 1
    Jan 18 07:47:38 golivepro com.apple.launchd[1] (org.calendarserver.calendarserver): Throttling respawn: Will start in 56 seconds
    Jan 18 07:49:34 golivepro servermgrd[16543]: Got error -9845 for SSLHandshake  remote address is fe80::c62c:3ff:fe07:a9e3%en0:2765
    Jan 18 07:49:34 golivepro servermgrd[16543]: Exception in SessionController threadListen: Socket: Connect failed
    Jan 18 07:50:53 golivepro xscertd-helper[17108]: idle timer triggered, exiting
    Jan 18 07:51:24 golivepro jabberd_notification/c2s[2715]: [8] [::ffff:10.0.1.160, port=52543] connect
    Jan 18 07:51:24 golivepro jabberd_notification/c2s[2715]: SASL callback for non-existing host: golivepro.com
    Jan 18 07:51:24 golivepro jabberd_notification/c2s[2715]: [8] [::ffff:10.0.1.160, port=52543] disconnect jid=unbound, packets: 0
    Jan 18 07:51:24 golivepro push_notify[98]: notification server connect failed, will retry in 300 seconds
    Jan 18 07:51:57 golivepro push_notify[98]: discarding message; not connected to notification server
    Jan 18 07:56:24 golivepro jabberd_notification/c2s[2715]: [8] [::ffff:10.0.1.160, port=52725] connect
    Jan 18 07:56:24 golivepro jabberd_notification/c2s[2715]: SASL callback for non-existing host: golivepro.com
    Jan 18 07:56:24 golivepro jabberd_notification/c2s[2715]: [8] [::ffff:10.0.1.160, port=52725] disconnect jid=unbound, packets: 0
    Jan 18 07:56:24 golivepro push_notify[98]: notification server connect failed, will retry in 300 seconds

    This is the errors I receive when turning of and back on iChat Server and iCal Server. If someone could help me figure out what is going on I would appriciate it.
    Push no longer works on desktop clients or iOS devices.
    Jan 18 07:46:23 golivepro jabberd/sm[18488]: version: jabberd sm 2.2.14-373.2
    Jan 18 07:46:23 golivepro jabberd/c2s[18490]: [golivepro.com] configured; realm=golivepro.com, registration disabled
    Jan 18 07:46:23 golivepro jabberd/c2s[18490]: attempting connection to router at 127.0.0.1, port=5347
    Jan 18 07:46:23 golivepro jabberd/c2s[18490]: [5] [router] write error: Broken pipe (32)
    Jan 18 07:46:23 golivepro jabberd/c2s[18490]: connection to router closed
    Jan 18 07:46:23 golivepro jabberd/c2s[18490]: attempting reconnect (3 left)
    Jan 18 07:46:23 golivepro jabberd/router[18489]: [127.0.0.1, port=5347] listening for incoming connections
    Jan 18 07:46:23 golivepro jabberd/sm[18488]: [golivepro.com] configured
    Jan 18 07:46:23 golivepro jabberd/sm[18488]: attempting connection to router at 127.0.0.1, port=5347
    Jan 18 07:46:23 golivepro jabberd/router[18489]: [127.0.0.1, port=52330] connect
    Jan 18 07:46:23 golivepro jabberd/router[18489]: [127.0.0.1, port=52330] authenticated as jabberd
    Jan 18 07:46:23 golivepro jabberd/s2s[18491]: attempting connection to router at 127.0.0.1, port=5347
    Jan 18 07:46:23 golivepro jabberd/router[18489]: [127.0.0.1, port=52331] connect
    Jan 18 07:46:23 golivepro jabberd/router[18489]: [127.0.0.1, port=52331] authenticated as jabberd
    Jan 18 07:46:24 golivepro jabberd/sm[18488]: connection to router established
    Jan 18 07:46:24 golivepro jabberd/router[18489]: [sm] online (bound to 127.0.0.1, port 52330)
    Jan 18 07:46:24 golivepro jabberd/router[18489]: [golivepro.com] online (bound to 127.0.0.1, port 52330)
    Jan 18 07:46:24 golivepro jabberd/sm[18488]: sm ready for sessions
    Jan 18 07:46:24 golivepro jabberd/s2s[18491]: connection to router established
    Jan 18 07:46:24 golivepro jabberd/router[18489]: [s2s] set as default route
    Jan 18 07:46:24 golivepro jabberd/router[18489]: [s2s] online (bound to 127.0.0.1, port 52331)
    Jan 18 07:46:24 golivepro jabberd/s2s[18491]: ready for connections
    Jan 18 07:46:24 golivepro Rooms[18497]: Starting up...
    Jan 18 07:46:24 golivepro Rooms[18497]: Loading persistent rooms from disk...
    Jan 18 07:46:24 golivepro Rooms[18497]: Finished loading rooms from disk
    Jan 18 07:46:24 golivepro Rooms[18497]: Connecting to XMPP server at 'golivepro.com' as 'rooms.golivepro.com'...
    Jan 18 07:46:24 golivepro jabberd_notification/c2s[2715]: [8] [::ffff:10.0.1.160, port=52338] connect
    Jan 18 07:46:24 golivepro jabberd_notification/c2s[2715]: SASL callback for non-existing host: golivepro.com
    Jan 18 07:46:24 golivepro jabberd_notification/c2s[2715]: [8] [::ffff:10.0.1.160, port=52338] disconnect jid=unbound, packets: 0
    Jan 18 07:46:24 golivepro push_notify[98]: notification server connect failed, will retry in 300 seconds
    Jan 18 07:46:25 golivepro jabberd/router[18489]: [127.0.0.1, port=52340] connect
    Jan 18 07:46:25 golivepro jabberd/router[18489]: [127.0.0.1, port=52340] authenticated as proxy65.golivepro.com
    Jan 18 07:46:25 golivepro jabberd/router[18489]: [proxy65.golivepro.com] online (bound to 127.0.0.1, port 52340)
    Jan 18 07:46:25 golivepro jabberd/c2s[18490]: attempting connection to router at 127.0.0.1, port=5347
    Jan 18 07:46:25 golivepro jabberd/router[18489]: [127.0.0.1, port=52341] connect
    Jan 18 07:46:25 golivepro jabberd/router[18489]: [127.0.0.1, port=52341] authenticated as jabberd
    Jan 18 07:46:25 golivepro jabberd/c2s[18490]: connection to router established
    Jan 18 07:46:25 golivepro jabberd/router[18489]: [c2s] online (bound to 127.0.0.1, port 52341)
    Jan 18 07:46:25 golivepro jabberd/c2s[18490]: [::, port=5222] listening for connections
    Jan 18 07:46:25 golivepro jabberd/c2s[18490]: [::, port=5223] listening for SSL connections
    Jan 18 07:46:25 golivepro jabberd/c2s[18490]: ready for connections
    Jan 18 07:46:27 golivepro jabberd/router[18489]: [127.0.0.1, port=52342] connect
    Jan 18 07:46:28 golivepro jabberd/router[18489]: [127.0.0.1, port=52342] authenticated as rooms.golivepro.com
    Jan 18 07:46:28 golivepro jabberd/router[18489]: [rooms.golivepro.com] online (bound to 127.0.0.1, port 52342)
    Jan 18 07:46:28 golivepro Rooms[18497]: Successfully connected to XMPP server, ready for activity
    Jan 18 07:47:38 golivepro org.calendarserver.calendarserver[18600]: Reading configuration from file: /etc/caldavd/caldavd.plist
    Jan 18 07:47:38 golivepro org.calendarserver.calendarserver[18600]: Neither EnableCalDAV nor EnableCardDAV are set to True.
    Jan 18 07:47:38 golivepro com.apple.launchd[1] (org.calendarserver.calendarserver[18600]): Exited with code: 1
    Jan 18 07:47:38 golivepro com.apple.launchd[1] (org.calendarserver.calendarserver): Throttling respawn: Will start in 56 seconds
    Jan 18 07:49:34 golivepro servermgrd[16543]: Got error -9845 for SSLHandshake  remote address is fe80::c62c:3ff:fe07:a9e3%en0:2765
    Jan 18 07:49:34 golivepro servermgrd[16543]: Exception in SessionController threadListen: Socket: Connect failed
    Jan 18 07:50:53 golivepro xscertd-helper[17108]: idle timer triggered, exiting
    Jan 18 07:51:24 golivepro jabberd_notification/c2s[2715]: [8] [::ffff:10.0.1.160, port=52543] connect
    Jan 18 07:51:24 golivepro jabberd_notification/c2s[2715]: SASL callback for non-existing host: golivepro.com
    Jan 18 07:51:24 golivepro jabberd_notification/c2s[2715]: [8] [::ffff:10.0.1.160, port=52543] disconnect jid=unbound, packets: 0
    Jan 18 07:51:24 golivepro push_notify[98]: notification server connect failed, will retry in 300 seconds
    Jan 18 07:51:57 golivepro push_notify[98]: discarding message; not connected to notification server
    Jan 18 07:56:24 golivepro jabberd_notification/c2s[2715]: [8] [::ffff:10.0.1.160, port=52725] connect
    Jan 18 07:56:24 golivepro jabberd_notification/c2s[2715]: SASL callback for non-existing host: golivepro.com
    Jan 18 07:56:24 golivepro jabberd_notification/c2s[2715]: [8] [::ffff:10.0.1.160, port=52725] disconnect jid=unbound, packets: 0
    Jan 18 07:56:24 golivepro push_notify[98]: notification server connect failed, will retry in 300 seconds

Maybe you are looking for