by Jens Helbig
ITM 6.30.07 and using the ORACLE SUN JRE 1.8 it could happen, that the JAVA Webstart (JWS) is failing with an exception like:
JNLParseException[ Could not parse launch file. Error at line 36.]
at com.sun.javaws.jnl.XMLFormat.parse(Unknown Source)
at com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source)
Caused by: org.xml.sax.SAXParseException; lineNumber: 36; columnNumber: 40; The string "--" is not permitted within comments.
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(Unknown Source)
org.xml.sax.SAXParseException; lineNumber: 36; columnNumber: 40; The string "--" is not permitted within comments.
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(Unknown Source)
To make the JWS working again you need to modify the tep.jnlpt and tep.jnlp on the TEPS server.
Windows:
- modify the c:\IBM\ITM\Config\tep.jnlpt (set the changes permanently)
- modify the c:\IBM\ITM\CNB\tep.jnlp (set the changes temporary if a TEPS reconfiguration is not possible but will lost at the
next TEPS reconfiguration)
UNIX:
- modify the /opt/IBM/ITM/config/tep.jnlpt (set the changes permanently)
- modify the /opt/IBM/ITM/ (set the changes temporary if a TEPS reconfiguration is not possible but will lost at the
next TEPS reconfiguration)
FROM:
- now clear the Java cache of your JWS and restart the JWS. The JWS should come up now and working as expected.
! The modification of the
https://www-304.ibm.com/support/entdocview.wss?uid=swg1IV92369
! The wrong "------" i have seen mostly on Windows 6.30.7 envirornments, so it seems only related to a tep.jnlp(t) on Windows Tivoli Enterprise Servers !