Slava Imeshev

For production mode it makes sense to set initalSize = maxSize. Also, size of the pool should be equal at least maximum number of simultaneous requests (there is a config parameter in tomcat's server.xml connector stanza, maxProcessors.

HTH

1) You may try to upgrade to the latest SP or version of the server - this problem may be fixed already.
2) Contact BEA support (please check this: http://www.viewtier.com/newsgroups/thread.jspa?threadID=4&tstart=0)
3) Write a shell script that tries to shutdown weblogic gracefully using SHUTDOWN, waits for some time and then issues kill.

Glad to help.

J2EE RI is just a set of jars. Just unzip/untar them at location you like.

Sessions that never time out is not a good idea - your application will die because of OutOfMemory sooner or later. Why would you want to have it?

You should a) set up both beans to use TXDataSources b) set up pools to use XA driver instead of plain JDBC drivers.

Generally it does not unless you ship jar with DAO seprately from EJBs.

Though you may obtain heap information using JVMPI, I don't think raw heap dump would be of any help. You may want to look at run-time J2EE monitoring tools from Borland or Quest - they may provide more readable information.

Also it makes a lot of sense to run load tests of your application under profiler in QA environment. Please check this as well: http://jroller.com/page/imeshev/20040204

I'd rather call a black-box magic. I don't think that describing the lower level details of this process would feet into format of this forum. Do you have any specific questions/problems?

Re: #1

In case of SLSB EJBObject serves as a facade to a pool of SLSB instances. Binding between EJBObject and an instance exists only for duration of a method call. So, yes, next call to a method will/may go to any arbitrary SLSB instance. That's what spec says and that's what weblogic does for you.

In case of SFSB EJBObject is bound to an instance for duration of a session and will become invlaid if runtime exception is thrown.

I'd check out this book: Java Servlet Programming, 2nd Edition by Jason Hunter It' provides detailed information on building and deploying servlets.

Also, here is the weblogic documentation on servlets:Programming WebLogic HTTP Servlets

I'd try to change change test/myejb to ejb/myejb.

You can access download page here (you'll need to register).

As for exactly version 6.0 - it's been EOL-ed.

You could get your configuration from the source control (likely not the case) or recreate the DS manually.

I'm not sure that it would work at all: you result set field #4 is a computed value. I doubt a server would be able to parse back this computation:

select ptscno,ptbcrno,ptprno,trunc(to_date(ptprdt,'dd-mm-yyyy'))