EJB Container doesn't survive first bean access

[bovi]

I'm new to EJB, and I've created an entity bean for an Oracle database.

When I run the container and my test client, the connection works fine. Then, when I run the test client again, I get a javax.naming.NameNotFoundException; it doesn't seem to be able to find the container anymore after the first run, even though the container is still running.

Also, if I use the debugger, I never get the connection at all. The debug run choice adds a -classic parameter to the VM for some reason, how can I override this? What are the other options? The release running doesn't have any parameters.

I am using JBuilder 5 Enterprise trial, in case that makes a difference. What could I be doing wrong?

 

[bovi]

Never mind, I found out that it's just JBuilder's internal appserver that is useless. The dedicated appserver works fine (most of the time).

On a side note, this board looks nearly dead...