You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@mina.apache.org by aruna reddy <re...@gmail.com> on 2011/09/14 09:15:55 UTC
vysper issue with BOSH connection
Hi,
When I use the TCP connection to Vysper 0.7 server the request and
response is like below
Received packet : <iq id="Mo71Q-2"
to="raj1@infor.com/9cb2f36e2d1841b28dfc51aee35a1da8"
type="result"><query xmlns="jabber:iq:roster"><item
jid="raj2@infor.com" name="raj2@infor.com" subscription="none"
ask="subscribe"></item></query></iq>
Received packet : <presence id="Mo71Q-3"
to="raj1@infor.com/9cb2f36e2d1841b28dfc51aee35a1da8"
from="raj1@infor.com/9cb2f36e2d1841b28dfc51aee35a1da8"></presence>
Waiting for packet id.Mo71Q-4
Received packet : <iq id="93c23199827545678835b21d31d5b114"
to="raj1@infor.com/9cb2f36e2d1841b28dfc51aee35a1da8" type="set"><query
xmlns="jabber:iq:roster"><item jid="raj2@infor.com"
name="raj2@infor.com" subscription="none"
ask="subscribe"></item></query></iq>
Received packet : <iq id="Mo71Q-4"
to="raj1@infor.com/9cb2f36e2d1841b28dfc51aee35a1da8"
type="result"><query xmlns="jabber:iq:roster"><item
jid="raj2@infor.com" name="raj2@infor.com" subscription="none"
ask="subscribe"></item></query></iq>
When I use the Bosh connection to Vysper 0.7 server the request and
response is like below
Received packet : <iq id="084vQ-2"
to="raj1@infor.com/f35d3c9eaff84f34ba5ac0b851ae75b5"
type="result"><query xmlns="jabber:iq:roster"><item
jid="raj2@infor.com" name="raj2@infor.com" subscription="none"
ask="subscribe"></item></query></iq>
Waiting for packet id.084vQ-4
Received packet : <presence id="084vQ-3"
to="raj1@infor.com/f35d3c9eaff84f34ba5ac0b851ae75b5"
from="raj1@infor.com/f35d3c9eaff84f34ba5ac0b851ae75b5"></presence>
Received packet : <iq id="1367aac10bcd476aa2a151a566e3dc28"
to="raj1@infor.com/f35d3c9eaff84f34ba5ac0b851ae75b5" type="set"><query
xmlns="jabber:iq:roster"><item jid="raj2@infor.com"
name="raj2@infor.com" subscription="none"
ask="subscribe"></item></query></iq>
No response from the server.:
at com.infor.test.BoshTest.createEntry(BoshTest.java:130)
at com.infor.test.BoshTest.main(BoshTest.java:75)
Though I increased the time out huge I don’t see the response from
server when I used the bosh connection, tested it with other xmpp
(openfire) server, client works fine.
Regards,
Aruna
RE: java.net.BindingException: Address already in use
Posted by Davis Ford <df...@axeda.com>.
Thanks for the suggestion Jason. That did not fix it, unfortunately. I also changed the test teardown to shut down the SshServer immediately .stop(true) -- still experiencing the same issue.
I'm using mina-core 2.0.4
The test connects with the first JSch client, and when it tries to connect the second JSch client is when the bind failure occurs. I suppose I'll have to go grab a Linux VM and try to debug it there.
-----Original Message-----
From: Jason Weinstein [mailto:jason.weinstein@oracle.com]
Sent: Tuesday, September 20, 2011 2:31 PM
To: users@mina.apache.org
Subject: Re: java.net.BindingException: Address already in use
Just a quick thought, but you may want to try setReuseAddress(true)
Re: java.net.BindingException: Address already in use
Posted by Jason Weinstein <ja...@oracle.com>.
Just a quick thought, but you may want to try setReuseAddress(true)
On 9/20/2011 11:06 AM, Davis Ford wrote:
> Hi all, I have a JUnit test that does the following:
>
> setup: find an unused port:
> try {
> // find an unused port to test on
> ServerSocket s = new ServerSocket(0);
> port = s.getLocalPort();
> s.close();
> System.err.println("--- TEST SETUP SPAWNED A NEW PORT ON "+port);
> } catch(Exception ex) {
> fail("Test setup fails trying to reserve an unused port "+ex.getMessage());
> }
>
> ...next start an sshd server with SFTP subsystem.
>
> Then a @Test method that uses JSch as a client to connect and upload a file and validate the file is there, etc.
>
> This all works fine and well, but I have another test case that does the same, except it creates two JSch clients -- just to validate that I can connect multiple clients simultaneously to the same server.
>
> My dev. laptop is on Win7, but the CI server is Linux. The test passes on Windows fine. I can even Thread.sleep() after the server is created and connect to the server multiple times using FileZillla.
>
> On Linux, it fails with a BindingException -- any idea why this might be? It isn't immediately clear to me what the difference would be on win/linux platform.
>
> java.net.BindException: Address already in use
> at sun.nio.ch.Net.bind(Native Method)
> at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:119)
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
> at org.apache.mina.transport.socket.nio.NioSocketAcceptor.open(NioSocketAcceptor.java:201)
> at org.apache.mina.transport.socket.nio.NioSocketAcceptor.open(NioSocketAcceptor.java:51)
> at org.apache.mina.core.polling.AbstractPollingIoAcceptor.registerHandles(AbstractPollingIoAcceptor.java:543)
> at org.apache.mina.core.polling.AbstractPollingIoAcceptor.access$300(AbstractPollingIoAcceptor.java:67)
> at org.apache.mina.core.polling.AbstractPollingIoAcceptor$Acceptor.run(AbstractPollingIoAcceptor.java:418)
> at org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:64)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:619)
>
> at org.junit.Assert.fail(Assert.java:91)
> at com.example.module.fileupload.server.SftpServerImplTest.testTwoSessionAndUploadTwoFiles(SftpServerImplTest.java:207)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
> at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
> at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
> at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
> at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
>
java.net.BindingException: Address already in use
Posted by Davis Ford <df...@axeda.com>.
Hi all, I have a JUnit test that does the following:
setup: find an unused port:
try {
// find an unused port to test on
ServerSocket s = new ServerSocket(0);
port = s.getLocalPort();
s.close();
System.err.println("--- TEST SETUP SPAWNED A NEW PORT ON "+port);
} catch(Exception ex) {
fail("Test setup fails trying to reserve an unused port "+ex.getMessage());
}
...next start an sshd server with SFTP subsystem.
Then a @Test method that uses JSch as a client to connect and upload a file and validate the file is there, etc.
This all works fine and well, but I have another test case that does the same, except it creates two JSch clients -- just to validate that I can connect multiple clients simultaneously to the same server.
My dev. laptop is on Win7, but the CI server is Linux. The test passes on Windows fine. I can even Thread.sleep() after the server is created and connect to the server multiple times using FileZillla.
On Linux, it fails with a BindingException -- any idea why this might be? It isn't immediately clear to me what the difference would be on win/linux platform.
java.net.BindException: Address already in use
at sun.nio.ch.Net.bind(Native Method)
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:119)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
at org.apache.mina.transport.socket.nio.NioSocketAcceptor.open(NioSocketAcceptor.java:201)
at org.apache.mina.transport.socket.nio.NioSocketAcceptor.open(NioSocketAcceptor.java:51)
at org.apache.mina.core.polling.AbstractPollingIoAcceptor.registerHandles(AbstractPollingIoAcceptor.java:543)
at org.apache.mina.core.polling.AbstractPollingIoAcceptor.access$300(AbstractPollingIoAcceptor.java:67)
at org.apache.mina.core.polling.AbstractPollingIoAcceptor$Acceptor.run(AbstractPollingIoAcceptor.java:418)
at org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:64)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
at org.junit.Assert.fail(Assert.java:91)
at com.example.module.fileupload.server.SftpServerImplTest.testTwoSessionAndUploadTwoFiles(SftpServerImplTest.java:207)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
Re: vysper issue with BOSH connection
Posted by aruna reddy <re...@gmail.com>.
Hi,
The problem seems to be with the client API
http://kenai.com/projects/jbosh , it could not send the update
acknowledgement id, hence for the new response id is attached with old
or first created acknowledgement id, on the server side Vesper
performers check on dispatching the response to client by getting the
response based on acknowledge id, if response is older than “1000”
milliseconds then it raises the terminate response, so in this cases
Vysper server raises the terminate response because the fetched
response for acknowledgement id was older. On correction on client to
send the acknowledge id equal to response id or less than one then it
processing was proper, I am still test on it.
Summary:
The response form Vysper seems to be solved based on client correction
to send latest acknowledge id .
Suggestion:
Why can’t Vysper upcoming release get response on response id instead
of acknowledge id, so client glitch does not affect the process of
Vysper.
Regards,
Aruna
On Fri, Sep 16, 2011 at 9:51 AM, aruna reddy <re...@gmail.com> wrote:
> Hi,
>
> I have attached the two logs vysper_server log and stanza log
>
>
> On Thu, Sep 15, 2011 at 11:40 PM, Bernd Fondermann
> <be...@googlemail.com> wrote:
>> On Wed, Sep 14, 2011 at 09:15, aruna reddy <re...@gmail.com> wrote:
>>> Hi,
>>>
>>> When I use the TCP connection to Vysper 0.7 server the request and
>>> response is like below
>>>
>>>
>>>
>>> Received packet : <iq id="Mo71Q-2"
>>> to="raj1@infor.com/9cb2f36e2d1841b28dfc51aee35a1da8"
>>> type="result"><query xmlns="jabber:iq:roster"><item
>>> jid="raj2@infor.com" name="raj2@infor.com" subscription="none"
>>> ask="subscribe"></item></query></iq>
>>>
>>> Received packet : <presence id="Mo71Q-3"
>>> to="raj1@infor.com/9cb2f36e2d1841b28dfc51aee35a1da8"
>>> from="raj1@infor.com/9cb2f36e2d1841b28dfc51aee35a1da8"></presence>
>>>
>>> Waiting for packet id.Mo71Q-4
>>>
>>> Received packet : <iq id="93c23199827545678835b21d31d5b114"
>>> to="raj1@infor.com/9cb2f36e2d1841b28dfc51aee35a1da8" type="set"><query
>>> xmlns="jabber:iq:roster"><item jid="raj2@infor.com"
>>> name="raj2@infor.com" subscription="none"
>>> ask="subscribe"></item></query></iq>
>>>
>>> Received packet : <iq id="Mo71Q-4"
>>> to="raj1@infor.com/9cb2f36e2d1841b28dfc51aee35a1da8"
>>> type="result"><query xmlns="jabber:iq:roster"><item
>>> jid="raj2@infor.com" name="raj2@infor.com" subscription="none"
>>> ask="subscribe"></item></query></iq>
>>>
>>>
>>>
>>> When I use the Bosh connection to Vysper 0.7 server the request and
>>> response is like below
>>>
>>>
>>>
>>> Received packet : <iq id="084vQ-2"
>>> to="raj1@infor.com/f35d3c9eaff84f34ba5ac0b851ae75b5"
>>> type="result"><query xmlns="jabber:iq:roster"><item
>>> jid="raj2@infor.com" name="raj2@infor.com" subscription="none"
>>> ask="subscribe"></item></query></iq>
>>>
>>> Waiting for packet id.084vQ-4
>>>
>>> Received packet : <presence id="084vQ-3"
>>> to="raj1@infor.com/f35d3c9eaff84f34ba5ac0b851ae75b5"
>>> from="raj1@infor.com/f35d3c9eaff84f34ba5ac0b851ae75b5"></presence>
>>>
>>> Received packet : <iq id="1367aac10bcd476aa2a151a566e3dc28"
>>> to="raj1@infor.com/f35d3c9eaff84f34ba5ac0b851ae75b5" type="set"><query
>>> xmlns="jabber:iq:roster"><item jid="raj2@infor.com"
>>> name="raj2@infor.com" subscription="none"
>>> ask="subscribe"></item></query></iq>
>>>
>>> No response from the server.:
>>>
>>> at com.infor.test.BoshTest.createEntry(BoshTest.java:130)
>>>
>>> at com.infor.test.BoshTest.main(BoshTest.java:75)
>>>
>>>
>>>
>>> Though I increased the time out huge I don’t see the response from
>>> server when I used the bosh connection, tested it with other xmpp
>>> (openfire) server, client works fine.
>>
>> Do you see anything in the server log?
>>
>> Bernd
>>
>
Re: vysper issue with BOSH connection
Posted by aruna reddy <re...@gmail.com>.
Hi,
I have attached the two logs vysper_server log and stanza log
On Thu, Sep 15, 2011 at 11:40 PM, Bernd Fondermann
<be...@googlemail.com> wrote:
> On Wed, Sep 14, 2011 at 09:15, aruna reddy <re...@gmail.com> wrote:
>> Hi,
>>
>> When I use the TCP connection to Vysper 0.7 server the request and
>> response is like below
>>
>>
>>
>> Received packet : <iq id="Mo71Q-2"
>> to="raj1@infor.com/9cb2f36e2d1841b28dfc51aee35a1da8"
>> type="result"><query xmlns="jabber:iq:roster"><item
>> jid="raj2@infor.com" name="raj2@infor.com" subscription="none"
>> ask="subscribe"></item></query></iq>
>>
>> Received packet : <presence id="Mo71Q-3"
>> to="raj1@infor.com/9cb2f36e2d1841b28dfc51aee35a1da8"
>> from="raj1@infor.com/9cb2f36e2d1841b28dfc51aee35a1da8"></presence>
>>
>> Waiting for packet id.Mo71Q-4
>>
>> Received packet : <iq id="93c23199827545678835b21d31d5b114"
>> to="raj1@infor.com/9cb2f36e2d1841b28dfc51aee35a1da8" type="set"><query
>> xmlns="jabber:iq:roster"><item jid="raj2@infor.com"
>> name="raj2@infor.com" subscription="none"
>> ask="subscribe"></item></query></iq>
>>
>> Received packet : <iq id="Mo71Q-4"
>> to="raj1@infor.com/9cb2f36e2d1841b28dfc51aee35a1da8"
>> type="result"><query xmlns="jabber:iq:roster"><item
>> jid="raj2@infor.com" name="raj2@infor.com" subscription="none"
>> ask="subscribe"></item></query></iq>
>>
>>
>>
>> When I use the Bosh connection to Vysper 0.7 server the request and
>> response is like below
>>
>>
>>
>> Received packet : <iq id="084vQ-2"
>> to="raj1@infor.com/f35d3c9eaff84f34ba5ac0b851ae75b5"
>> type="result"><query xmlns="jabber:iq:roster"><item
>> jid="raj2@infor.com" name="raj2@infor.com" subscription="none"
>> ask="subscribe"></item></query></iq>
>>
>> Waiting for packet id.084vQ-4
>>
>> Received packet : <presence id="084vQ-3"
>> to="raj1@infor.com/f35d3c9eaff84f34ba5ac0b851ae75b5"
>> from="raj1@infor.com/f35d3c9eaff84f34ba5ac0b851ae75b5"></presence>
>>
>> Received packet : <iq id="1367aac10bcd476aa2a151a566e3dc28"
>> to="raj1@infor.com/f35d3c9eaff84f34ba5ac0b851ae75b5" type="set"><query
>> xmlns="jabber:iq:roster"><item jid="raj2@infor.com"
>> name="raj2@infor.com" subscription="none"
>> ask="subscribe"></item></query></iq>
>>
>> No response from the server.:
>>
>> at com.infor.test.BoshTest.createEntry(BoshTest.java:130)
>>
>> at com.infor.test.BoshTest.main(BoshTest.java:75)
>>
>>
>>
>> Though I increased the time out huge I don’t see the response from
>> server when I used the bosh connection, tested it with other xmpp
>> (openfire) server, client works fine.
>
> Do you see anything in the server log?
>
> Bernd
>
Re: vysper issue with BOSH connection
Posted by Bernd Fondermann <be...@googlemail.com>.
On Wed, Sep 14, 2011 at 09:15, aruna reddy <re...@gmail.com> wrote:
> Hi,
>
> When I use the TCP connection to Vysper 0.7 server the request and
> response is like below
>
>
>
> Received packet : <iq id="Mo71Q-2"
> to="raj1@infor.com/9cb2f36e2d1841b28dfc51aee35a1da8"
> type="result"><query xmlns="jabber:iq:roster"><item
> jid="raj2@infor.com" name="raj2@infor.com" subscription="none"
> ask="subscribe"></item></query></iq>
>
> Received packet : <presence id="Mo71Q-3"
> to="raj1@infor.com/9cb2f36e2d1841b28dfc51aee35a1da8"
> from="raj1@infor.com/9cb2f36e2d1841b28dfc51aee35a1da8"></presence>
>
> Waiting for packet id.Mo71Q-4
>
> Received packet : <iq id="93c23199827545678835b21d31d5b114"
> to="raj1@infor.com/9cb2f36e2d1841b28dfc51aee35a1da8" type="set"><query
> xmlns="jabber:iq:roster"><item jid="raj2@infor.com"
> name="raj2@infor.com" subscription="none"
> ask="subscribe"></item></query></iq>
>
> Received packet : <iq id="Mo71Q-4"
> to="raj1@infor.com/9cb2f36e2d1841b28dfc51aee35a1da8"
> type="result"><query xmlns="jabber:iq:roster"><item
> jid="raj2@infor.com" name="raj2@infor.com" subscription="none"
> ask="subscribe"></item></query></iq>
>
>
>
> When I use the Bosh connection to Vysper 0.7 server the request and
> response is like below
>
>
>
> Received packet : <iq id="084vQ-2"
> to="raj1@infor.com/f35d3c9eaff84f34ba5ac0b851ae75b5"
> type="result"><query xmlns="jabber:iq:roster"><item
> jid="raj2@infor.com" name="raj2@infor.com" subscription="none"
> ask="subscribe"></item></query></iq>
>
> Waiting for packet id.084vQ-4
>
> Received packet : <presence id="084vQ-3"
> to="raj1@infor.com/f35d3c9eaff84f34ba5ac0b851ae75b5"
> from="raj1@infor.com/f35d3c9eaff84f34ba5ac0b851ae75b5"></presence>
>
> Received packet : <iq id="1367aac10bcd476aa2a151a566e3dc28"
> to="raj1@infor.com/f35d3c9eaff84f34ba5ac0b851ae75b5" type="set"><query
> xmlns="jabber:iq:roster"><item jid="raj2@infor.com"
> name="raj2@infor.com" subscription="none"
> ask="subscribe"></item></query></iq>
>
> No response from the server.:
>
> at com.infor.test.BoshTest.createEntry(BoshTest.java:130)
>
> at com.infor.test.BoshTest.main(BoshTest.java:75)
>
>
>
> Though I increased the time out huge I don’t see the response from
> server when I used the bosh connection, tested it with other xmpp
> (openfire) server, client works fine.
Do you see anything in the server log?
Bernd