Install WLS as Windows Service got ‘input line too long’ error

Following doc: https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_afrLoop=85729941264881&_afrWindowMode=0&_adf.ctrl-state=u0k53lbwd_130#aref_section23

Setup Node manager as NT Service is easy, just run that cmd under WL_HOME\server\bin\installNodeMgrSvc.cmd.

Service created successfully, no errors, start/stop smoothly.

The problem popped up when doing Admin server and Managed server.

Error: the input line is too long.

This is typical JAVA CLASSPATH exceed DOS/WIN environment size limit issue.

The number of characters that can be entered into a single command is limited to 8191. (this is including spaces).

In detail, The error occurs when setting EXTRA_JAVA_PROPERTIES in call %USERDOMAIN_HOME%\bin\setDomainEnv.cmd

Try to ignore those lines:
set EXTRA_JAVA_PROPERTIES=-Doracle.apm.home=%APM_ORACLE_HOME% -DAPM_HELP_FILENAME=oesohwconfig.xml %EXTRA_JAVA_PROPERTIES%
set EXTRA_JAVA_PROPERTIES= -DXL.HomeDir=%OIM_ORACLE_HOME%\server -Dscheduler.disabled=false -Djava.security.auth.login.config=%OIM_ORACLE_HOME%\server\config\authwl.conf -Dorg.owasp.esapi.resources=%OIM_ORACLE_HOME%\server\apps\oim.ear\APP-INF\classes -DeditionOverride=ee %EXTRA_JAVA_PROPERTIES%
set EXTRA_JAVA_PROPERTIES= -Doracle.oaam.home=%OAAM_ORACLE_HOME% -Djava.awt.headless=true %EXTRA_JAVA_PROPERTIES%
set EXTRA_JAVA_PROPERTIES= -Doracle.oaam.home=%OAAM_ORACLE_HOME% %EXTRA_JAVA_PROPERTIES%
set EXTRA_JAVA_PROPERTIES= -Doracle.oaam.home=%OAAM_ORACLE_HOME% %EXTRA_JAVA_PROPERTIES%
set EXTRA_JAVA_PROPERTIES= -Doam.oes.new=true -DOAM_POLICY_FILE=%DOMAIN_HOME%\config\fmwconfig\oam-policy.xml -DOAM_CONFIG_FILE=%DOMAIN_HOME%\config\fmwconfig\oam-config.xml -DOAM_ORACLE_HOME=%OAM_ORACLE_HOME% -Doracle.security.am.SERVER_INSTNCE_NAME=%SERVER_NAME% -Does.jars.home=%OAM_ORACLE_HOME%\server\lib\oes-d8 -Does.integration.path=%OAM_ORACLE_HOME%\server\lib\oeslib\oes-integration.jar -Does.enabled=true -Djavax.xml.soap.SOAPConnectionFactory=weblogic.wsee.saaj.SOAPConnectionFactoryImpl -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Djavax.xml.soap.SOAPFactory=oracle.j2ee.ws.saaj.soap.SOAPFactoryImpl %EXTRA_JAVA_PROPERTIES%
set EXTRA_JAVA_PROPERTIES=%EXTRA_JAVA_PROPERTIES% -Dem.oracle.home=C:\app\oracle\Middleware_IAM\oracle_common -Djava.awt.headless=true
set EXTRA_JAVA_PROPERTIES=%EXTRA_JAVA_PROPERTIES% -Dbpm.enabled=true
set EXTRA_JAVA_PROPERTIES=%EXTRA_JAVA_PROPERTIES% -Dsoa.archives.dir=%SOA_ORACLE_HOME%\soa -Dsoa.oracle.home=%SOA_ORACLE_HOME% -Dsoa.instance.home=%DOMAIN_HOME% -Dtangosol.coherence.clusteraddress=227.7.7.9 -Dtangosol.coherence.clusterport=9778 -Dtangosol.coherence.log=jdk -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Dweblogic.transaction.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true -Djavax.net.ssl.trustStore=%WL_HOME%\server\lib\DemoTrust.jks
set EXTRA_JAVA_PROPERTIES=%EXTRA_JAVA_PROPERTIES% -Dums.oracle.home=%UMS_ORACLE_HOME%
set EXTRA_JAVA_PROPERTIES=-Dcommon.components.home=%COMMON_COMPONENTS_HOME% -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=%DOMAIN_HOME% -Djrockit.optfile=%COMMON_COMPONENTS_HOME%\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=%ORACLE_DOMAIN_CONFIG_DIR%\servers\%SERVER_NAME% -Doracle.domain.config.dir=%ORACLE_DOMAIN_CONFIG_DIR% -Digf.arisidbeans.carmlloc=%ORACLE_DOMAIN_CONFIG_DIR%\carml -Digf.arisidstack.home=%ORACLE_DOMAIN_CONFIG_DIR%\arisidprovider -Doracle.security.jps.config=%DOMAIN_HOME%\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=%DOMAIN_HOME%\servers\%SERVER_NAME%\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=%ALT_TYPES_DIR% -Djava.protocol.handler.pkgs=%PROTOCOL_HANDLERS% %WLS_JDBC_REMOTE_ENABLED% %EXTRA_JAVA_PROPERTIES%
set JAVA_PROPERTIES=%JAVA_PROPERTIES% %EXTRA_JAVA_PROPERTIES%

When service created and start, got an error ‘ Unable to initialize the Java virtual machine!’

This EXTRA_JAVA_PROPERTIES seems is critical for JAVA process. Giving up.

I think for now I have to keep IAM desktop never always in login status.

A helpful trick, beasvc -remove command doesn’t work. Had to run sc delete instead.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s