ApplinX 10.1 windows x64

Hi,

When i install Applinx 10.1 with its designer in windows machine, server is not getting started after stopping it for first time.
Tried with multiple re installations and reboot of machine.

Getting hanged or it is in same position for indefinite time.

Below is the start up console, it is not proceeding after last line.

Any insight will be really helpful.

Thanks & Regards,
Abraar Ahamed Shaik

09-Jan-2019 07:57:52.084 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
09-Jan-2019 07:57:52.084 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=C:\SoftwareAG\ApplinX\conf\logging.properties
09-Jan-2019 07:57:52.084 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xmx1024m
09-Jan-2019 07:57:52.100 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcom.sabratec.useicon=true
09-Jan-2019 07:57:52.100 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcom.sabratec.gxhome=C:\SoftwareAG\ApplinX
09-Jan-2019 07:57:52.100 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.library.path=C:\SoftwareAG\ApplinX
09-Jan-2019 07:57:52.100 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xrs
09-Jan-2019 07:57:52.100 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=C:\SoftwareAG\ApplinX
09-Jan-2019 07:57:52.100 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcom.sabratec.useicon=true
09-Jan-2019 07:57:52.100 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=C:\SoftwareAG\ApplinX\tomcat
09-Jan-2019 07:57:52.100 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: [C:\SoftwareAG\ApplinX]
09-Jan-2019 07:57:52.319 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler [“http-nio-2380”]
09-Jan-2019 07:57:52.538 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
09-Jan-2019 07:57:52.538 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler [“ajp-nio-2309”]
09-Jan-2019 07:57:52.538 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
09-Jan-2019 07:57:52.538 INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 1052 ms
09-Jan-2019 07:57:52.569 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina]
09-Jan-2019 07:57:52.584 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.5.15
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/C:/SoftwareAG/ApplinX/webapps/…/wsstack/WEB-INF/lib/slf4j-jdk14-1.7.7.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/C:/SoftwareAG/ApplinX/webapps/…/wsstack/WEB-INF/lib/slf4j-log4j12-1.7.7.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.JDK14LoggerFactory]
09-Jan-2019 07:58:09.647 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler [“http-nio-2380”]
09-Jan-2019 07:58:09.663 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler [“ajp-nio-2309”]
09-Jan-2019 07:58:09.710 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 17160 ms

Hi,

I’m sorry for the late response, I somehow missed your post.
Is it still relevant?
We don’t have enough information here to get to the bottom of this, the immediate “suspects” would be the license file or occupied ports.
If these are ok, I suggest to open a support call along with all relevant information and it will be addressed.

Regards,
Gadi