[JDEV] Problems with a Jabber client written in Java (It works on NT but not on Linux)

Al Sutton al at alsutton.com
Wed May 30 01:07:51 CDT 2001


Re: [JDEV] Problems with a Jabber client written in Java (It works on NT but not on Linux)Aubrey,

I posted before, but you may have missed it. I have a working client written in Java that runs on Windows (9x, NT, 2000), Linux, and Solaris. I used my own libraries which you can download from http://www.alsutton.com/kvmjab/.

Regards,

Al
  ----- Original Message ----- 
  From: Jackson, Aubrey 
  To: jdev at jabber.org 
  Sent: Tuesday, May 29, 2001 8:39 PM
  Subject: Re: [JDEV] Problems with a Jabber client written in Java (It works on NT but not on Linux)


  David, 

  Thank you for your response. I am using the Sun JDK 1.2.2. It seems to be something going on at the socket layer. I am able send the client initializing info to the server but I don't get a response back from the server. Do you know if any one has written and run a Java Jabber client on Linux??

  Aubrey 

  Date: Tue, 29 May 2001 10:51:34 -0600 
  From: David Waite <dwaite at jabber.com> 
  To: jdev at jabber.org 
  Subject: Re: [JDEV] Problems with a Jabber client written in Java (It works on NT 
   butnot on Linux) 
  Reply-To: jdev at jabber.org 



  --------------979D3A411159C0D2161D6EB7 
  Content-Type: text/plain; charset=us-ascii 
  Content-Transfer-Encoding: 7bit 

  The only thing which comes to mind right off the bat is that Redhat 
  installed kaffe, and it is being used instead of Sun's JDK. I have never 
  done testing with JabberBeans on kaffe. 

  -David Waite 

  "Jackson, Aubrey" wrote: 

  > 
  > 
  > Hello to the group, 
  > 
  >         I have a problem with a Java client that I have written and 
  > was wondering if anyone else had run across a similar situation. As 
  > mentioned in the subject line the client is written in Java. It uses 
  > the JabberBeans framework (0.9.0-pre4) APIs as the basis for 
  > communication with a Jabber server. The client works fine when run on 
  > the WindowsNT 4.0 operating system. However, when run on Red Hat Linux 
  > 6.2 the client is never connected to the server. The client sends the 
  > correct username and password to the appropriate server but never 
  > receives a connection notification from the server. No packets from 
  > the server are ever received by my client after my client sends the 
  > authentication packet. Has anyone else seen this type of problem? 
  > 
  > Thank you 
  > Aubrey 

  --------------979D3A411159C0D2161D6EB7 
  Content-Type: text/html; charset=us-ascii 
  Content-Transfer-Encoding: 7bit 

  <!doctype html public "-//w3c//dtd html 4.0 transitional//en"> 
  <html> 
  The only thing which comes to mind right off the bat is that Redhat installed 
  kaffe, and it is being used instead of Sun's JDK. I have never done testing 
  with JabberBeans on kaffe. 
  <p>-David Waite 
  <p>"Jackson, Aubrey" wrote: 
  <blockquote TYPE=CITE>&nbsp; 
  <p><font face="Arial"><font size=-1>Hello to the group,</font></font> 
  <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <font face="Arial"><font size=-1>I 
  have a problem with a Java client that I have written and was wondering 
  if anyone else had run across a similar situation. As mentioned in the 
  subject line the client is written in Java. It uses the JabberBeans framework 
  (0.9.0-pre4) APIs as the basis for communication with a Jabber server. 
  The client works fine when run on the WindowsNT 4.0 operating system. However, 
  when run on Red Hat Linux 6.2 the client is never connected to the server. 
  The client sends the correct username and password to the appropriate server 
  but never receives a connection notification from the server. No packets 
  from the server are ever received by my client after my client sends the 
  authentication packet. Has anyone else seen this type of problem?</font></font> 
  <p><font face="Arial"><font size=-1>Thank you</font></font> 
  <br><font face="Arial"><font size=-1>Aubrey</font></font></blockquote> 
  </html> 

  --------------979D3A411159C0D2161D6EB7-- 




  --__--__-- 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.jabber.org/jdev/attachments/20010530/eda69dbc/attachment-0002.htm>


More information about the JDev mailing list