曝光臺(tái) 注意防騙 網(wǎng)曝天貓店富美金盛家居專營(yíng)店坑蒙拐騙欺詐消費(fèi)者

The following screenshot shows the configuration:
« Flight Ops Doc
Manager » Administration Guide
􀃖
Java 1.5 shall be ticked. Java 4 or 6 shall be unticked.
Be Careful : The version of java shall be less than 1.5.0_16.
5.3.5
Flight Ops Doc Manager server error client JWS cannot load
5.3.5.1
Symptom
After reinstalling Flight Ops Doc Manager server, when a client tries to load Flight Ops Doc Manager client, it fails without loading the new version of Flight Ops Doc Manager jnlp file.
5.3.5.2
Cause
Sun java web start does not identify that the version between client and server is different. Then the local copy of the JWS file is used.
« Flight Ops Doc
Manager »
Administration Guide
Reference: UG0601141
Issue: 7.1
PAGE 26/32
© AIRBUS S.A.S 2009. All rights reserved. Confidential and proprietary document. This document and all information contained herein is the sole property of AIRBUS S.A.S. No intellectual
property rights are granted by the delivery of this document or the disclosure of its content. This document shall not be reproduced or disclosed to a third party without the express written
consent of AIRBUS S.A.S. This document and its content shall not be used for any purpose other than that for which it is supplied
5.3.5.3
Solution/ Fix
Open Java Web Start console. Go into the advanced tab of the preference menu and clean the application directory.
(note: Java Web Start is placed in your start menu and also in: %JAVA_HOME%\jre\javaws\javaws.exe)
5.3.6
Infinite process on server
5.3.6.1
Symptom
Infinite process (for example on import DB manual process). The application seems to be working but the progress bar is freezed.
Look into the Flight Ops Doc Manager server trace file (FOSP-trace.txt) for the line:
java.lang.StackOverflowError
5.3.6.2
Cause
The server uses not enough memory for stack.
5.3.6.3
Solution/ Fix
Before, stop the Flight Ops Doc Manager server.
« Flight Ops Doc
Manager »
Administration Guide
Reference: UG0601141
Issue: 7.1
PAGE 27/32
© AIRBUS S.A.S 2009. All rights reserved. Confidential and proprietary document. This document and all information contained herein is the sole property of AIRBUS S.A.S. No intellectual
property rights are granted by the delivery of this document or the disclosure of its content. This document shall not be reproduced or disclosed to a third party without the express written
consent of AIRBUS S.A.S. This document and its content shall not be used for any purpose other than that for which it is supplied
You must increase the stacksize of server launcher (launchFospServer.bat). For instance replace the Xss parameter by “-Xss8M”.
Launch the Flight Ops Doc Manager server.
5.3.7
Aircraft model not unique
5.3.7.1
Symptom
During certain operation such as load a BatchUpdateException may occur.
The following trace can be seen in the trace file:
Caused by: org.hibernate.NonUniqueResultException: query did not return a unique result: 2
at org.hibernate.impl.AbstractQueryImpl.uniqueElement(AbstractQueryImpl.java:844)
at org.hibernate.impl.AbstractQueryImpl.uniqueResult(AbstractQueryImpl.java:835)
at com.airbus.ops.fosp.server.persistence.fleet.FleetHb8Dao.getAircraftModelByName(FleetHb8Dao.java:303)
5.3.7.2
Cause
Database table containing aircraft_model is corrupted.
5.3.7.3
Solution/ Fix
Log out all users of application. Stop application (client and server).
Open database using a tool such as DBVizualiser identify the aircraft_model present twice.
For instance, in table FOSP_AIRCRAFT_MODEL:
ACM_ID
ACM_MODEL
57057
380-841
92092
380-841
One of the ACM_MODEL shall be deleted. You must keep the first one.
First of all link aircrafts to the first model. In our case:
update FOSP_AIRCRAFT set AC_ACM_ID=’57057’ where AC_ACM_ID=’92092’
Then you may delete additional ACM_MODEL
delete from FOSP_AIRCRAFT_MODEL where ACM_ID='92092'
5.3.8
Impossible to freeze a manual
5.3.8.1
Symptom
5.3.8.1.1
Standalone mode
Infinite process for the Freeze process. The application seems to be working but the progress bar on client side is frozen for a long time.
Look into the Flight Ops Doc Manager server trace file (FOSP-trace.txt) for one of the following lines:
« Flight Ops Doc
Manager »
Administration Guide
Reference: UG0601141
Issue: 7.1
PAGE 28/32
© AIRBUS S.A.S 2009. All rights reserved. Confidential and proprietary document. This document and all information contained herein is the sole property of AIRBUS S.A.S. No intellectual
　
中國(guó)航空網(wǎng) www.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：“Flight Ops Doc Manager”Administration Guide(9)