beepcore-java-users Mailing List for Java BEEP Core (Page 8)

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Hey guys,

Hope you all have a great christmas, and enjoy the holiday!

Cheers
Sean

Hi,
=20
I have been testing beep by flooding the session with messages and get =
SEVERE errors. I use a message listener that just sends a string back. =
On the sending peer's side I register the NullReplyListener. I do not =
wait until I have recieved reply before I sending the next message. =
After a few messages have been sent then I get a error
          SEVERE: Incorrect message number: was 16; expection 1
Is it correct to assume that I can send miltiple messages on a single =
channel without waiting for a reply between every message?
=20
If I don't send any reply back then the error does not occur.
=20
I have attatched a demo program to illistrate the problem.
=20
Thanks,
Sean de Kock
=20
Files:
    bombClient.java (package: org.beepcore.beep.example) - client
    bombServer.java (package: org.beepcore.beep.example) - server
    TestBombProfile.java (package: org.beepcore.beep.profile.test) - =
profile

Hi, a quick question about listeners..
It seems that if TCPSessionCreator.listen() is called
by two processes on the same machine, with the same
port, no exception is thrown.
Ofcourse only the first caller receives the initiator
request.
Is this the expected behaviour of Beep?
thanks,
Manjuka

http://greetings.yahoo.com.au - Yahoo! Greetings
- Send your seasons greetings online this year!

This was fixed for the 0.9.07 release:

http://sourceforge.net/tracker/index.php?func=detail&aid=589436&group_id=24004&atid=380281

--KMK

On Mon, 2002-12-16 at 03:41, Andrew Keedle wrote:
> I'm using beepcore-0.9.06, which I know is not the latest, but I've
> come across a problem with my server. If I telnet to the Server port I
> get the greeting message ok, but if I drop the telnet connection then
> whatever connects after that doesn't get the greeting message. Any
> clues?
-- 
Kevin Kress <kk...@my...>

I'm using beepcore-0.9.06, which I know is not the latest, but I've come
across a problem with my server. If I telnet to the Server port I get the
greeting message ok, but if I drop the telnet connection then whatever
connects after that doesn't get the greeting message. Any clues?

> Huston wrote:
> >>I have a few questions about the use of the TLSProfile:
> >>*    Firstly what is the advantages of JSSE over PTLS and vica versa?
> >
> >
> > The reason for the PTLS TLSProfile was because of a bug in theJSSE
library
> > that wouldn't allow client authentication when starting TLS (instead of
> > SSL).
>
> I don't believe this true any more.  I don't seem to be having this
> problem with the JSSE stuff that comes with JDK 1.4.

Great! Thanks for the info.

--Huston

Hi Huston,

I have made a tempory solution to the problem, I wrote a method in =
TuningProfile that returns the latest session object (stored as a =
static). I know that it is not a good solution but it works for now. So =
far the XML-RPC over BEEP is just about finished. I am wanting to make =
it open-source but I have to clear it with my boss first, as the company =
has payed me to do the developement. I am away this next week but I will =
speak to him when I return.

Thanks
Sean de Kock

Huston wrote:
>>I have a few questions about the use of the TLSProfile:
>>*    Firstly what is the advantages of JSSE over PTLS and vica versa?
> 
> 
> The reason for the PTLS TLSProfile was because of a bug in theJSSE library
> that wouldn't allow client authentication when starting TLS (instead of
> SSL).

I don't believe this true any more.  I don't seem to be having this 
problem with the JSSE stuff that comes with JDK 1.4.

-andy

Easy enough to add, I'll add it to the list unless you would like to submit
a patch :-)

--Huston

----- Original Message -----
From: "David Blacka" <dav...@ve...>
To: <bee...@li...>
Sent: Monday, December 09, 2002 2:25 PM
Subject: [Beepcore-java-users] serverName session property?

Is it possible to get the serverName session property from the Session,
assuming that the peer used the serverName attribute to start a channel at
some point?

This is sort of a trick question, because looking through the code I see
that in Session.java, the serverName attribute is pulled out of the <start>
element, but nothing is actually done with the information.

--
David Blacka    <da...@ve...>
Sr. Engineer    Verisign Applied Research

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Beepcore-java-users mailing list
Bee...@li...
https://lists.sourceforge.net/lists/listinfo/beepcore-java-users

> I have a few questions about the use of the TLSProfile:
> *    Firstly what is the advantages of JSSE over PTLS and vica versa?

The reason for the PTLS TLSProfile was because of a bug in theJSSE library
that wouldn't allow client authentication when starting TLS (instead of
SSL).

> *    Do I need to use the startChannel method inherited from the
tunningProfile or can I just > use the session object?

Can you provide more information? I don't understand the question.

> *    I have a situation where a session is established, and then the
listener starts the TLS
> (without authentication). I assume that by setting up a
handshakeCompleteListener I can find
> out when the TLS is started. If the client now tries to send a message
then an error occurs:
>         SEVERE: javax.net.ssl.SSLException: Recieved fatal alert:
unexpected_message
> It looks like this is caused due to the session object needs updating. By
sending a message
> from the listener (started TLS) and then using the session object from the
message
> (message.getChannel().gatSession()) I can avoid the problem. Is there
another way of
> getting the current session object?

Not currently but this could be fixed without too much trouble.

> *    How do I go about setting the TLS up for authentication where can I
create a
> private-public key pair, etc.

It depends on which TLSProfile you use. Both of them are configured with the
init() method but they have different configuration options. JSSE uses the
Keystore and PTLS uses PEM files.

> I am in the process of implementing XML-RPC over beep, if anyone is
intrested in this let
> me know.

Very cool, will it be an open source release?

--Huston

Sean,

The complete method is used by the listener so it doesn't pass the new
Session back to anyone, which seems to be ok in most cases but I can see
where this could be a problem. I'll give it some thought and see what I can
come up with. As for the initiator the new Session is returned from the
startTLS call.

--Huston

----- Original Message -----
From: <136...@su...>
To: <hu...@us...>; "beepcore-java-users"
<bee...@li...>
Sent: Thursday, December 12, 2002 3:50 AM
Subject: [Beepcore-java-users] tuning

Hi,

I have looked further into the session object and I found that I was
mistaken, new session objects are not created when a message is recieved. I
do however still have a problem only this time I am less sure of what it is.
When the tuning takes place the complete() method calls reset() (in
TCPSession) which resets the session the new session object is never passed
back. Is this correct, or should the object be passed back? If it is correct
this way how should the peer (non TLS-initiator) get new channels and
control the session?

Thanks,
Sean de Kock

-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_______________________________________________
Beepcore-java-users mailing list
Bee...@li...
https://lists.sourceforge.net/lists/listinfo/beepcore-java-users

Hi,
=20
I have looked further into the session object and I found that I was =
mistaken, new session objects are not created when a message is =
recieved. I do however still have a problem only this time I am less =
sure of what it is. When the tuning takes place the complete() method =
calls reset() (in TCPSession) which resets the session the new session =
object is never passed back. Is this correct, or should the object be =
passed back? If it is correct this way how should the peer (non =
TLS-initiator) get new channels and control the session?
=20
Thanks,
Sean de Kock

Hi,
=20
I have been looking into the way that the session object acts on the =
peer that is recieving a message. I have noticed that when using tuning =
everytime a message has been recieved a new session (TCPSession) object =
is created. This is done by calling the reset method. This is a pain if =
you want to operate as peer-to-peer. Everytime a message is recieved =
then you lose the session object, and with it the control of the =
session. As yet I have not found any where to get the latest session =
object. Am I missing something, is there maybe a different way to =
control the session when using tuning?
=20
My situation:
I start a beep session, the listener starts TLS (JSSE) and the sends =
data the initiator (did not start TLS) gets the session from a message =
recieved, and can send data. When the data is recieved on the listener's =
side a new session object is created and the old one is useless.
=20
Is there a reason for creating a new object and not just modifying the =
old one?
=20
Thanks,
Sean de Kock

On Wed, Dec 11, 2002 at 01:33:14PM +0200, De Kock SJ <136...@su...> wrote:
> Hi,
>  
> I have a few questions about the use of the TLSProfile:
> *    Firstly what is the advantages of JSSE over PTLS and vica versa?

Probably the greatest one would be interoperability with other BEEP 
implementations.  Also I suspect you have more visibility into the
TLS stuff withing the BEEP context/framework as it may set tuning
information based on the TLS negotiation rather than the JSSE which
is external.

> *    Do I need to use the startChannel method inherited from the tunningProfile or can I just use the session object?
> *    I have a situation where a session is established, and then the listener starts the TLS (without authentication). I assume that by setting up a handshakeCompleteListener I can find out when the TLS is started. If the client now tries to send a message then an error occurs:
>          SEVERE: javax.net.ssl.SSLException: Recieved fatal alert: unexpected_message
> It looks like this is caused due to the session object needs updating. By sending a message from the listener (started TLS) and then using the session object from the message (message.getChannel().gatSession()) I can avoid the problem. Is there another way of getting the current session object?
> *    How do I go about setting the TLS up for authentication where can I create a private-public key pair, etc.
>  
> I am in the process of implementing XML-RPC over beep, if anyone is intrested in this let me know.

Did you take a look at the SOAP over BEEP proposal that Marshall did?  Would
this do what you need?  I don't know if it's been implemented anywhere though.

-bill

>  
> Thanks
> Sean
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:
> With Great Power, Comes Great Responsibility 
> Learn to use your power at OSDN's High Performance Computing Channel
> http://hpc.devchannel.org/
> _______________________________________________
> Beepcore-java-users mailing list
> Bee...@li...
> https://lists.sourceforge.net/lists/listinfo/beepcore-java-users

Hi,
=20
I am not sure if I understand how the session object get updated (or is =
a new object created). I have a situation where the one peer closes the =
session and the other peer is waiting for SESSION_STATE_CLOSED but never =
gets it. By putting debug statements in the session source I see that =
the state is changed! Is this correct? If so how can I get hold of the =
new session object?
=20
Regards,
Sean

Hi,
=20
I have a few questions about the use of the TLSProfile:
*    Firstly what is the advantages of JSSE over PTLS and vica versa?
*    Do I need to use the startChannel method inherited from the =
tunningProfile or can I just use the session object?
*    I have a situation where a session is established, and then the =
listener starts the TLS (without authentication). I assume that by =
setting up a handshakeCompleteListener I can find out when the TLS is =
started. If the client now tries to send a message then an error occurs:
         SEVERE: javax.net.ssl.SSLException: Recieved fatal alert: =
unexpected_message
It looks like this is caused due to the session object needs updating. =
By sending a message from the listener (started TLS) and then using the =
session object from the message (message.getChannel().gatSession()) I =
can avoid the problem. Is there another way of getting the current =
session object?
*    How do I go about setting the TLS up for authentication where can I =
create a private-public key pair, etc.
=20
I am in the process of implementing XML-RPC over beep, if anyone is =
intrested in this let me know.
=20
Thanks
Sean

Is it possible to get the serverName session property from the Session,=20
assuming that the peer used the serverName attribute to start a channel a=
t=20
some point?

This is sort of a trick question, because looking through the code I see=20
that in Session.java, the serverName attribute is pulled out of the <star=
t>=20
element, but nothing is actually done with the information.

--=20
David Blacka    <da...@ve...>=20
Sr. Engineer    Verisign Applied Research

Here are the details:

C:\WINNT>java -version
java version "1.4.1_01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-b01)
Java HotSpot(TM) Client VM (build 1.4.1_01-b01, mixed mode)

Try this for reproducing:

1. Change EchoProfile as follows and build beepcore.jar.
    public void startChannel(Channel channel, String encoding, String data)
            throws StartChannelException
    {
        log.debug("EchoCCL StartChannel Callback");
        // exception - begin
        try {
        	channel.setReceiveBufferSize(8096);
        } catch (BEEPException e) {
        	e.printStackTrace();
        }
        // exception - end
        channel.setMessageListener(this);
    }
2. Run Beepd and Bing in that order. (I usually have beepcore.jar in
   CLASSPATH)

Regards,
-- 
Harsh Daharwal
IOS Networks Inc.
http://www.iosnetworks.com

Huston said:
>> I'm trying to set a Channel's receive buffer size using
>> Channel::setReceiveBufferSize(8096); in startChannel() method
>> of my profile which implements StartChannelListener. The attempt
>> results in following exception:
>>
>> java.net.SocketException: Software caused connection abort: recv
>> failed at java.net.SocketInputStream.socketRead0(Native Method)
>> at java.net.SocketInputStream.read(SocketInputStream.java:129)
>> at org.beepcore.beep.transport.tcp.TCPSession.processNextFrame
>> (TCPSession.java:434)
>> at org.beepcore.beep.transport.tcp.TCPSession.access$000
>> (TCPSession.java:55)
>> at org.beepcore.beep.transport.tcp.TCPSession$1.run
>> (TCPSession.java:230)
>>
>>
>> Are there any pre-conditions for using this method.
>> I'm using 9.07 version of framework.
>
> No, which jvm are you using? This looks like a bug, I'll see what I can
> find after I get your reply.
>
> --Huston

> Unfortunately I haven't
> gotten around to doing the OutputStream version but maybe it is time I
> addressed this and the FileOutputDataStream...

I've implemented a version of OutputDataStreamAdapter which is probably
inefficient, bugridden and lacking in documentatin but it's a start ;-)

It assumes you will set the MimeHeaders via the OutputDataStream before
creating an OutputDataStreamAdapter from it. I've sucessfully used it to
pass a Vector of strings and integers. My example code which is the run
method of my profile reply thread ....

      Vector result = new Vector();
      MimeHeaders mh = new MimeHeaders();
      OutputDataStream ods = new OutputDataStream(mh);
      objStream = new ObjectOutputStream(new
OutputDataStreamAdapter(ods));
      result.add(new Integer(123));
      result.add(new String("hello"));
      objStream.writeObject(result);
      objStream.close();      
      message.sendRPY(ods);

If I tidy this up a bit is it worthy of inclusion into beepcore?

=========cut OutputDataStreamAdapter.java below ================

/*
 * OutputDataStreamAdapter.java
 *
 * Created on 04 December 2002, 10:49
 * @author  and...@pr...
 *
 */

package org.beepcore.beep.core;

import java.io.IOException;
import org.beepcore.beep.util.BufferSegment;
import org.beepcore.beep.core.OutputDataStream;
import org.beepcore.beep.core.BEEPException;

public class OutputDataStreamAdapter 
  extends java.io.OutputStream
  {
  static final int DEFAULT_BUFFER_SIZE = 1024;

  private OutputDataStream ods;    
  private int dataSize;
  private byte[] dataBuffer;
  private int dataCount;

  /** Creates a new instance of OutputDataStreamAdapter */
  public OutputDataStreamAdapter(OutputDataStream ods)
    {
    this(ods, DEFAULT_BUFFER_SIZE);  
    }

  public OutputDataStreamAdapter(OutputDataStream ods, int bufferSize)
    {
    this.ods = ods;
    dataSize = bufferSize;
    dataCount = 0;
    dataBuffer = new byte[dataSize];  
    }

  /** Writes the specified byte to this output stream. The general
   * contract for <code>write</code> is that one byte is written
   * to the output stream. The byte to be written is the eight
   * low-order bits of the argument <code>b</code>. The 24
   * high-order bits of <code>b</code> are ignored.
   * <p>
   * Subclasses of <code>OutputStream</code> must provide an
   * implementation for this method.
   *
   * @param      b   the <code>byte</code>.
   * @exception  IOException  if an I/O error occurs. In particular,
   *             an <code>IOException</code> may be thrown if the
   *             output stream has been closed.
   *
   */

  public void write(int b) 
    throws IOException
    {
    if (dataCount > dataSize)
      {
      // whoops!!!  
      }

    if (dataCount == dataSize)
      {
      this.flush();
      }

    dataBuffer[dataCount++] = (byte)b;      
    }

  public void flush()
    throws IOException
    {
    if (dataCount > 0)
      { 
      BufferSegment bs = new BufferSegment(dataBuffer, 0, dataCount);
      ods.add(bs);
      dataBuffer = new byte[dataSize];
      dataCount = 0;
      }
    }

  public void close()
    throws IOException
    {
    this.flush();  
    ods.setComplete();
    dataBuffer = null;
    }

  }

> In the mean time there is an InputDataStreamAdapter 

I'll have a look at that, it sounds like it makes one end of the job
easier ...

> Unfortunately I haven't
> gotten around to doing the OutputStream version but maybe it is time I
> addressed this and the FileOutputDataStream...

I might be tempted to look at InputDataStreamAdapter to gauge the
complexity of writing OutputDataStreamAdapter ....

> We're using beepcore-java for our client/server communication on a
> "trial" project, so far so good, we've got a listener based on beepd and
> our own profiles.
>
> One thing that makes itself clear farly quickly is how much nicer it
> would be if beep's InputDataStream and OutputDataStream were derived
> from java's own Stream classes (or perhaps implemented their interfaces)
>
> In particular it would make it easier to send/receive XML documents or
> serialize entire java objects through beep channels without
> "stringizing" them first.
>
> Have I missed a trick that makes this possible already? Has anyone
> thought the same thoughts? How difficuly would it be to implement?

You have a good point. In a previous version we tried doing what you
suggested but ran into a couple of snags but I think the problem is better
understood now and maybe we should revisit this decision. In the mean time
there is an InputDataStreamAdapter (I know it is a really bad name, I keep
hoping someone will suggest something better) that you can get from a
InputDataStream that inherits from InputStream. Unfortunately I haven't
gotten around to doing the OutputStream version but maybe it is time I
addressed this and the FileOutputDataStream...

--Huston

Someone asked a question the other day about sending a large file 
in a single message using one of the stream classes.  While this does not 
answer the question directly I thought I'd throw out an idea.  If
you arrange things correctly you can easily send sequenced blocks of the
file in ANS frames.  An ftp style GET is easily implemented, and a 
PUT requires an extra message exchange with a put message prompting a get 
from the other end.

-bill

Hi, 

We're using beepcore-java for our client/server communication on a
"trial" project, so far so good, we've got a listener based on beepd and
our own profiles.

One thing that makes itself clear farly quickly is how much nicer it
would be if beep's InputDataStream and OutputDataStream were derived
from java's own Stream classes (or perhaps implemented their interfaces)

In particular it would make it easier to send/receive XML documents or
serialize entire java objects through beep channels without
"stringizing" them first.

Have I missed a trick that makes this possible already? Has anyone
thought the same thoughts? How difficuly would it be to implement?

Thanks ....

> What is the best way to pass files across (possibly very big files) a beep
session?

In previous versions of the library there was a FileDataStream that would do
this for you, I need to add one back to the library. In the mean time you
can create one of your own using the OutputDataStream directly. If you do
write one and would like to contribute it to the project that would be
great!

> I have been thinking about writing a very simple users guide for beepcore.
As I am currently working through it I know which were the areas where I
battled. Would anyone be keen to assist in proof reading it and possibly
helping with explanations of certain asspects of beepcore? Any further
comments on my idea are welcome.

Any documentation you would like to write would be appreciated. Let me know
when you are ready and I'll review it.

--Huston

Willie,

At Invisible Worlds there was a project to modify the jetty servlet
container to support BEEP. It worked fine and was an easy way to get some
servlets talking BEEP. The servlet interfaces were really designed with http
in mind so they are more client-server than peer-to-peer, but that is
sufficient for many applications.

--Huston

----- Original Message -----
From: Willie Vu
To: bee...@li...
Sent: Monday, December 02, 2002 11:34 PM
Subject: [Beepcore-java-users] BEEP servlet?

Playing the server role, a BEEP peer behaves like a servlet.  I wonder if
implementing BEEP as a servlet is a good idea.  Any comment?

Also, I read the www.beepcore.org FAQ about an Apache module.  What features
will this module provide?

--
Willie Vu
mailto:ctw...@us...

2001	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov (3)	Dec
2002	Jan (24)	Feb (3)	Mar (18)	Apr (2)	May (11)	Jun (6)	Jul (11)	Aug (37)	Sep (22)	Oct (11)	Nov (11)	Dec (29)
2003	Jan (8)	Feb (4)	Mar (19)	Apr (13)	May (16)	Jun (15)	Jul (2)	Aug (1)	Sep (1)	Oct (7)	Nov (13)	Dec
2004	Jan (1)	Feb (4)	Mar (2)	Apr	May (3)	Jun (2)	Jul (8)	Aug	Sep (7)	Oct (15)	Nov (8)	Dec
2005	Jan	Feb	Mar	Apr (1)	May (1)	Jun	Jul (6)	Aug	Sep (3)	Oct	Nov	Dec (5)
2006	Jan	Feb	Mar	Apr	May	Jun (1)	Jul (4)	Aug	Sep	Oct (4)	Nov	Dec
2007	Jan	Feb	Mar	Apr	May	Jun (1)	Jul	Aug	Sep	Oct	Nov	Dec

beepcore-java-users Mailing List for Java BEEP Core (Page 8)

beepcore-java-users — Discussion list for developers using beepcore-java library