Connection failure after deploying to 10.1.3 app server

Question

I am working on a three-tier application that uses session EJB facades and TopLink for persistence. I configured a datasource in the embedded OC4J server preferences in JDeveloper (10.1.3) and can successfully deploy my persistence code to the embedded server and access it from a test client.
I recently installed Oracle App Server 10g 10.1.3 to be used for integration testing. In JDeveloper, I configured a new application server connection and EJB Jar deployment profile to allow me to deploy my persistence code to the new server. When I deploy my code to the server and attempt to use one of the session EJB persistence methods, I get the following exception message:
Internal Exception: java.sql.SQLException: javax.resource.spi.ApplicationServerInternalException: Unable to create a connection. Connection factory has been stopped.Error Code: 0
In the Oracle Enterprise Manager, my application is running and the datasource and connection pool test successfully.
If I restart OC4J from Oracle Enterprise Manager, my application works correctly, at least until I have to deploy new code to the server, at which time the above error reappears. My question: Should OC4J have to be restarted each time new code is deployed? I am not making any changes to the datasource or connection pool configurations. Thanks.

Answer 1

Thanks Jaap.
I was told recently by someone at Oracle that Forms/Reports is supported on 10.1.3.x and eventually on 11g (not yet released), and I was also told 10.1.3 doesn't require two servers, but I'm having trouble finding much to support either claim.
Reason I'm asking is that we're currently using the client/server Forms/Reports and need to decide on a migration path and l don't know if it's wise to continue with the 10.1.2 App Server knowing it's going to be de-supported in a few short years and I don't want to go with 10.1.3 if it requires additional servers (we're small). We're looking at APEX as a possible alternative...
Tim