Can't get some LCDS ES Test Drive samples to work in Tomcat

Question

I can't get many of the Sample Test Drive examples included
with Livecycle Data Services ES 2.5.1 to work properly with Tomcat
(both version 5.5.25 and 6.0.14). I've tried both on Windows XP SP2
and Mac OSX (10.4), but I get the same errors on both platforms. I
can however get the Sample Test Drive from LCDS to work fine with
the JRun server on Windows (included with the Windows version of
LCDS). I've setup the JRun server in a similar fashion as Tomcat
(see my steps below) and everything works fine. I haven't been as
successful with Tomcat. Can anyone point out where I'm going wrong
with my Tomcat setup?
I am using Java 1.5.0.
Here are the error messages I get when trying out the LCDS
Test Drive examples on Tomcat:
Sample 1 - Accessing data using an HTTP service (after
pressing the "Get Data" button):
[RPC Fault faultString="HTTP request error"
faultCode="Server.Error.Request" faultDetail="Error: [IOErrorEvent
type="ioError" bubbles=false cancelable=false eventPhase=2
text="Error #2032: Stream Error. URL:
http://localhost:8080/samples/testdrive/sample1/catalog.jsp"
URL: catalog.jsp"]
at mx.rpc::AbstractInvoker/
http://www.adobe.com/2006/flex/mx/internal::faultHandler()
at mx.rpc::Responder/fault()
at mx.rpc::AsyncRequest/fault()
at DirectHTTPMessageResponder/errorHandler()
at flash.events::EventDispatcher/dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at flash.net::URLLoader/redirectEvent()
Samples 3, 4 and 5 all produce the following error:
[RPC Fault faultString="flex.samples.DAOException :
java.sql.SQLException: Connection is broken"
faultCode="Server.Processing" faultDetail="null"]
at mx.rpc::AbstractInvoker/
http://www.adobe.com/2006/flex/mx/internal::faultHandler()
at mx.rpc::Responder/fault()
at mx.rpc::AsyncRequest/fault()
at NetConnectionMessageResponder/statusHandler()
at mx.messaging::MessageResponder/status()
Sample 8 - Data Management Service:
[RPC Fault faultString="Unable to invoke a fill operation on
destination 'inventory' due to the following error: class
flex.samples.DAOException:java.sql.SQLException: Connection is
broken." faultCode="Server.Processing" faultDetail="null"]
at mx.data::ConcreteDataService/
http://www.adobe.com/2006/flex/mx/internal::dispatchFaultEvent()
at DataListRequestResponder/fault()
at mx.rpc::AsyncRequest/fault()
at NetConnectionMessageResponder/statusHandler()
at mx.messaging::MessageResponder/status()
Samples 2, 6 and 7 work fine.
Here are the steps I took to setup Tomcat. I've tried this on
both MacOSX and WinXP:
1. Download and extract Tomcat from tomcat.apache.org (I've
tried both version 5.5.25 and 6.0.14)
2. Install Livecycle Data Services ES 2.5.1 and copy
flex.war, flex-admin.war and samples.war to [tomcat-root]/webapps/
3. Prepare tomcat for Livecycle Data Services by following
the instructions here:
http://help.adobe.com/en_US/livecycle/es/lcds_installation.html
3a. Add Java Open Transaction Manager (JOTM) from
http://jotm.objectweb.org/.
Copy the JAR files from [jotm-root]/lib to
[tomcat-root]/common/lib/.
3b. Create a context file for your web application and
register JOTM using the Transaction element, e.g. for the samples
WAR create a [tomcat-root]/conf/Catalina/localhost/samples.xml file
and add the following lines:
<Context docBase="${catalina.home}/webapps/samples"
privileged="true"
antiResourceLocking="false" antiJARLocking="false">
<Transaction
factory="org.objectweb.jotm.UserTransactionFactory"
jotm.timeout="60"/>
</Context>
3c. Increase the maximum memory to at least 512MB. For
Tomcat, this is achieved by specifying the maximum heap size for
the JVM in the JAVA_OPTS variable in [tomcat-root]/bin/catalina.sh:
-Xmx512m
4. Run the tomcat server ([tomcat-root]/bin/startup.sh for
Mac OS or [tomcat-root]\bin\startup.bat for WinXP) which extracts
the 3 .war files into their respective directories in
[tomcat-root]/webapps/
5. Goto the Samples Test Drive in your web browser at
http://localhost:8080/samples/testdrive/

Answer 1

Thanks Leif,
Yes, set it to the location jndi path.
A piece of info is that the 903 oc4j release notes states that global conn pooling doesn't
work. Infering that the j2ee/home/config/data-sources.xml data sources aren't pooled or ??
I just tested so called local connection pooling, where I edited the data-sources.xml that
gets packaged in the ear, to include the min/max params and re-ran my test.
Still, the AM creates a new conn, it's to a new socket, and closes the conn when done. Causing
each conn to not be pooled, rather opened then closed to the DB box. As verified with lsof and
netstat, checking the ephemeral port # on the DB box side, always changes, meaning it's a
new socket and not an old pooled conn socket.
???? What the heck??
Surely if the AM conn check out / return code works properly, OC4J's pooling JDBC driver would
pool and not close the socket??
Has anywone gotten JDBC Datasource connections in BC4J to actually be pooled under OC4J??
Since I couldn't get this to work in my early 902 oc4j testing, and now can't get it to work
still under 903 OC4J, either it's my config or BC4J AM's code or OC4J?
Any thoughts on how to figure out what's not configed correctly or has a bug?
Thanks, curt