When creating a new instance of MWS I get this error in log:
2020-03-10 11:28:26 Post process IFS Middleware Server 10.3.3.0 2020-03-10 11:28:26 Running ant script F:\IFS\ifs_home\repository\server\install_fndmws.xml, target post for component server [java]: Java Result: 1 Error in Ant-script: server\install_fndmws.xml Reported error is: The following error occurred while executing this line: F:\IFS\ifs_home\repository\server\install_fndmws.xml:262: Failed to configure Middleware Server. Error is: Error when creating IFS Middleware Domain: com.oracle.cie.domain.script.jython.WLSTException: null @org.python.core.Py.JavaError(Py.java:368)
Anyone have some tips for solution? It´s a server that had an MWS before but that is removed and now replaced by a clone.
Best answer by MattiasLindahl
I managed to use the Backup function instead and after finalizing restore of backup I deleted the instance and created a new instance. Now working!
It seems that IFS MWS Nodemanager keeps stopping. Log file now says:
[Tue Mar 10 15:48:17 CET 2020] - INFO: Unable to connect to nodemanager.. [Tue Mar 10 15:48:17 CET 2020] - FINE: Execute native command [sc, query, IFS MWS Nodemanager F_IFS_ifs_home] [Tue Mar 10 15:48:17 CET 2020] - FINE: Command exit code 0 [Tue Mar 10 15:48:17 CET 2020] - FINE: wait for nodemanager 10s.. [Tue Mar 10 15:48:27 CET 2020] - INFO: Connecting to nodemanager.. [Tue Mar 10 15:48:28 CET 2020] - INFO: Unable to connect to nodemanager.. [Tue Mar 10 15:48:28 CET 2020] - FINE: Execute native command [sc, query, IFS MWS Nodemanager F_IFS_ifs_home] [Tue Mar 10 15:48:28 CET 2020] - FINE: Command exit code 0 [Tue Mar 10 15:48:28 CET 2020] - FINE: wait for nodemanager 10s.. [Tue Mar 10 15:48:38 CET 2020] - INFO: Connecting to nodemanager.. [Tue Mar 10 15:48:39 CET 2020] - INFO: Unable to connect to nodemanager.. [Tue Mar 10 15:48:39 CET 2020] - FINE: Execute native command [sc, query, IFS MWS Nodemanager F_IFS_ifs_home] [Tue Mar 10 15:48:39 CET 2020] - FINE: Command exit code 0 [Tue Mar 10 15:48:39 CET 2020] - FINE: wait for nodemanager 10s.. [Tue Mar 10 15:48:49 CET 2020] - INFO: Connecting to nodemanager.. [Tue Mar 10 15:48:50 CET 2020] - INFO: Unable to connect to nodemanager.. [Tue Mar 10 15:48:50 CET 2020] - FINE: Execute native command [sc, query, IFS MWS Nodemanager F_IFS_ifs_home] [Tue Mar 10 15:48:50 CET 2020] - FINE: Command exit code 0 [Tue Mar 10 15:48:50 CET 2020] - FINE: wait for nodemanager 10s..
I managed to use the Backup function instead and after finalizing restore of backup I deleted the instance and created a new instance. Now working!
When creating a new instance of MWS I get this error in log:
2020-03-10 11:28:26 Post process IFS Middleware Server 10.3.3.0 2020-03-10 11:28:26 Running ant script F:\IFS\ifs_home\repository\server\install_fndmws.xml, target post for component server [java]: Java Result: 1 Error in Ant-script: server\install_fndmws.xml Reported error is: The following error occurred while executing this line: F:\IFS\ifs_home\repository\server\install_fndmws.xml:262: Failed to configure Middleware Server. Error is: Error when creating IFS Middleware Domain: com.oracle.cie.domain.script.jython.WLSTException: null @org.python.core.Py.JavaError(Py.java:368)
Anyone have some tips for solution? It´s a server that had an MWS before but that is removed and now replaced by a clone.
Page 1 / 1
The Clone process won’t backup the Java folder from the Source runtime folder. Copy the Java folder manually and retry your reconfiguration.
Also, the clone won’t copy across the documentation folders too but you can always use the link from an existing instance.
Where is the location of this Java folder in Source runtime?
Make sure the Java sub folder is missing in the Target runtime folder, prior to copying it across.
It seems that IFS MWS Nodemanager keeps stopping. Log file now says:
[Tue Mar 10 15:48:17 CET 2020] - INFO: Unable to connect to nodemanager.. [Tue Mar 10 15:48:17 CET 2020] - FINE: Execute native command [sc, query, IFS MWS Nodemanager F_IFS_ifs_home] [Tue Mar 10 15:48:17 CET 2020] - FINE: Command exit code 0 [Tue Mar 10 15:48:17 CET 2020] - FINE: wait for nodemanager 10s.. [Tue Mar 10 15:48:27 CET 2020] - INFO: Connecting to nodemanager.. [Tue Mar 10 15:48:28 CET 2020] - INFO: Unable to connect to nodemanager.. [Tue Mar 10 15:48:28 CET 2020] - FINE: Execute native command [sc, query, IFS MWS Nodemanager F_IFS_ifs_home] [Tue Mar 10 15:48:28 CET 2020] - FINE: Command exit code 0 [Tue Mar 10 15:48:28 CET 2020] - FINE: wait for nodemanager 10s.. [Tue Mar 10 15:48:38 CET 2020] - INFO: Connecting to nodemanager.. [Tue Mar 10 15:48:39 CET 2020] - INFO: Unable to connect to nodemanager.. [Tue Mar 10 15:48:39 CET 2020] - FINE: Execute native command [sc, query, IFS MWS Nodemanager F_IFS_ifs_home] [Tue Mar 10 15:48:39 CET 2020] - FINE: Command exit code 0 [Tue Mar 10 15:48:39 CET 2020] - FINE: wait for nodemanager 10s.. [Tue Mar 10 15:48:49 CET 2020] - INFO: Connecting to nodemanager.. [Tue Mar 10 15:48:50 CET 2020] - INFO: Unable to connect to nodemanager.. [Tue Mar 10 15:48:50 CET 2020] - FINE: Execute native command [sc, query, IFS MWS Nodemanager F_IFS_ifs_home] [Tue Mar 10 15:48:50 CET 2020] - FINE: Command exit code 0 [Tue Mar 10 15:48:50 CET 2020] - FINE: wait for nodemanager 10s..
I managed to use the Backup function instead and after finalizing restore of backup I deleted the instance and created a new instance. Now working!
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
