The spec doesn't permit you to do any of the following
in an ejb:
1) Start a new thread
2) Accept a serversocket
3) Have static data that is not final
Perhaps you can explain what you are trying to do?
Thanks again for the reply!!!!!!!!!
Anyhow, here is the background on our project.
We are trying to create a serversocket listening on the JBoss VM. The serversocket will listen for connections from our legacy database that only make socket connections. The legacy database will make 2 to 10 socket connections to the JBoss VM serversocket. The serversocket will create 2 to 10 sockets which will be pooled on a stateless session bean.
Basically, we need to run a serversocket in the JBoss VM.
Our plans were to run it in a separate thread.
Its seems like JBoss 2.4.4, allowed us to start the thread in the session bean itself. Is this a mistake in JBoss implementation of the EJB 1.1 specs?
Also is there a better way to do create a serversocket in JBoss?
You have a database that opens connections on your app?
That sounds the wrong way around?
You will need some kind of client that takes the
requests and calls the session bean.
The client could run in the same VM as the session bean
as a service with an MBean dependency on the ejb
to ensure correct startup sequence. Because it is an
Service MBean you can have lifecycle events like
start() and stop().
Once again THANKS!!!!!!!!!!
Actually the database we use is just many flat files. We don't have a "real" database. We run a program to read the files then open a connection to past along the data.
Thank yo very much for your help!!!!