Forms crashes after copying over fmx

Question

Group,
While testing changes, I notice that when I copy over the currently open form's fmx that when I close the form the following exception is raised and forms crashes. Is there any work around? (other then not copying overwriting files in use)
Thanks.
Env details
Forms Version 10.1.2.0.2
Redhat 3
latest IE
--pat
FRM-92101: there was a failure in the forms server during startup. This could happen due to invalid configuration.
Please look into the web-server log for details.
details...
Loading http://triton.xxxx:7778/forms/java/frmall_jinit.jar from JAR cache
proxyHost=null
proxyPort=0
connectMode=HTTP, native.
Forms Applet version is : 10.1.2.0
oracle.forms.net.ConnectionException: Forms session <26> aborted: unable to communicate with runtime process.
at oracle.forms.net.ConnectionException.createConnectionException(Unknown Source)
at oracle.forms.net.HTTPNStream.getResponse(Unknown Source)
at oracle.forms.net.HTTPNStream.doFlush(Unknown Source)
at oracle.forms.net.HTTPNStream.flush(Unknown Source)
at java.io.DataOutputStream.flush(Unknown Source)
at oracle.forms.net.StreamMessageWriter.run(Unknown Source)

Answer 1

Mr Helmet :-)
This is actually expected behavior (See MetaLink Note 286762.1). There is a way to work around this in a development environment, but you really DO NOT want to do it in a production environment (See MetaLink Note Note 151618.1).
To increase scalability of Forms, each individual user does not have all the Forms loaded for them. So, only those things that are necesary for a user to run a session are loaded. For the first sessions, it is everything. For subsequent users, it is only things necessary that are different from the first sessions.
This allows you to run LOTS more users with FAR fewer resources.
If this is a Development system, the workaround is to disable this performance feature & load everything into memory for every user. You do this by setting the FORMS_MMAP environment variable to FALSE (0 for Forms 6i and earlier). Use the version number for Forms versions 9 & earlier (i.e. FORMS90_MMAP).
I hope this explains things for you & why this is expected.
If you think about it, why would you want currently connected users to be running while putting new Forms in place. Think about how the logic could be messed up if they started running parts of the application that were put out there while other parts were still in memory.
Another way you could do this in a production environment would be to have multiple directories for different versions of your application. Then, when the new files are ready to be promoted, you change the FORMS_PATH to point to that new location. The connected users will still be reading the old forms & the new users would be using the new ones.
I hope this helps.
Cordially,
Steve