Hi Patrick, What Version of Vysper are you running? I'd suggest you run current TRUNK, because BOSH has been heavily refactored since the last release.
Could you please also try to run the Adium debug console? Maybe this gives more insight in what is acutally happening on Adium's side. http://trac.adium.im/wiki/CurrentAdiumDebug I'm also having troubles connecting with BOSH/Adium, but with different results. Please open a JIRA. Thanks, Bernd On Mon, Oct 8, 2012 at 4:04 AM, Patrick Twohig <[email protected]> wrote: > Sorry. I should have pasted the logs. I'm using Adium as a test client. > Perhaps it's just a bad BOSH client? > > 176988 [1961786982@qtp-1067398966-2] INFO > org.apache.vysper.xmpp.extension.xep0124.BoshBackedSessionContext - BOSH > session 45ccc2475fa541948fb501121227b984 closed > > 233358 [InactivityChecker] ERROR > org.apache.vysper.xmpp.extension.xep0124.InactivityChecker - BOSH session > 7a15f10de7fa4b9fb810ccb25fcb1885 reached maximum inactivity period, closing > session... > > 233358 [InactivityChecker] INFO > org.apache.vysper.xmpp.extension.xep0124.BoshBackedSessionContext - BOSH > session 7a15f10de7fa4b9fb810ccb25fcb1885 closed > > 280386 [InactivityChecker] ERROR > org.apache.vysper.xmpp.extension.xep0124.InactivityChecker - BOSH session > e7ef1f80d8ee43cd930d0fe518017dbc reached maximum inactivity period, closing > session... > > 280387 [InactivityChecker] INFO > org.apache.vysper.xmpp.extension.xep0124.BoshBackedSessionContext - BOSH > session e7ef1f80d8ee43cd930d0fe518017dbc closed > > 357423 [1118499567@qtp-1067398966-4] INFO > org.apache.vysper.xmpp.extension.xep0124.BoshBackedSessionContext - BOSH > session 63f296fdc3844711b78f9335934f299a closed > > 499068 [InactivityChecker] ERROR > org.apache.vysper.xmpp.extension.xep0124.InactivityChecker - BOSH session > 6546e780e088425693cea8c7fdb42647 reached maximum inactivity period, closing > session... > > 499068 [InactivityChecker] INFO > org.apache.vysper.xmpp.extension.xep0124.BoshBackedSessionContext - BOSH > session 6546e780e088425693cea8c7fdb42647 closed > > 546074 [InactivityChecker] ERROR > org.apache.vysper.xmpp.extension.xep0124.InactivityChecker - BOSH session > aecd1969f2d84d11b309d7fcf4d1bfb1 reached maximum inactivity period, closing > session... > > 546074 [InactivityChecker] INFO > org.apache.vysper.xmpp.extension.xep0124.BoshBackedSessionContext - BOSH > session aecd1969f2d84d11b309d7fcf4d1bfb1 closed > > 563079 [InactivityChecker] ERROR > org.apache.vysper.xmpp.extension.xep0124.InactivityChecker - BOSH session > b3731c8aa1fc42b2b4ebbade1e28ac4c reached maximum inactivity period, closing > session... > > 563079 [InactivityChecker] INFO > org.apache.vysper.xmpp.extension.xep0124.BoshBackedSessionContext - BOSH > session b3731c8aa1fc42b2b4ebbade1e28ac4c closed > > 635155 [InactivityChecker] ERROR > org.apache.vysper.xmpp.extension.xep0124.InactivityChecker - BOSH session > 188d0a08cd46488d99f2eb33ec639de2 reached maximum inactivity period, closing > session... > > 635155 [InactivityChecker] INFO > org.apache.vysper.xmpp.extension.xep0124.BoshBackedSessionContext - BOSH > session 188d0a08cd46488d99f2eb33ec639de2 closed > > 673084 [pool-3-thread-8] INFO > org.apache.vysper.xmpp.state.resourcebinding.ResourceRegistry - added > resource no. 1 to entity user2@localhost <- 70519eab796540fb877b5e9e71272de1 > > 673084 [pool-3-thread-8] INFO > org.apache.vysper.xmpp.state.resourcebinding.ResourceRegistry - added > resource no. 1 to session e6eb0be116234b289d3035790435a321 <- > 70519eab796540fb877b5e9e71272de1 > > 679514 [pool-6-thread-3] INFO > org.apache.vysper.xmpp.modules.core.im.handler.PresenceAvailabilityHandler > - user2@localhost/70519eab796540fb877b5e9e71272de1 has become available > > On Sun, Oct 7, 2012 at 7:00 PM, Patrick Twohig <[email protected]> wrote: > >> Hi, >> >> I have been able to successfully get Vysper up and running embedded it >> into an existing web application. However, it seems like it takes a very >> long time to connect via BOSH, and longer to actually exchange messages. >> Specifically it seems to be on a 60s interval. I was curious where may be >> a good place to start looking. This problem doesn't happn with regular >> XMPP, so I'm fairly certain this is a problem with the BOSH servlet. Any >> help would be greatly appreciated. >> >> Thanks, >> Patrick. >>
