Unable to access PAM's UI
Article ID: 106223
Updated On:
Products
CA Process Automation Base
Issue/Introduction
Process Automation is installed on a server where another application is installed (like Service Desk). When SDM's services start first, PAM's UI is not shown, but if PAM's service starts first, SDM's UI is not shown.
This behavior means that some ports are being shared by both applications, so the first that starts will take it an won't let the other to work successfully.
This behavior means that some ports are being shared by both applications, so the first that starts will take it an won't let the other to work successfully.
Environment
Release: ITPASA99000-4.3-Process Automation-Add On License for-CA Server Automation
Component:
Component:
Resolution
This can be solved reinstalling/reconfigured both applications and set different ports, but there is one PAM port that is not configurable during the installation. In order to identify if this is the port that causes the issue, the following steps can be follow:
1.- Stop both applications, on this case SDM and PAM.
2.- Start just SDM until it's fully up and running.
3.- Now, start PAM services.
4.- Right after it, open Task Manager and check the processes list looking for "java.exe", which is associate to PAM.
5.- When Java.exe is fully loaded (it will consume something near to 2 GB of RAM, but it depends on the environment) it should start a second "Java.exe", which is associated to the login. If you wait for 10 minutes after PAM services were started and this second "Java.exe" never started, the logs inside of the following folder can be reviewed: "..CA\PAM\activemq\data".
In the logs, the following error messages can be seen:
2018-07-11 09:29:42,689 | INFO | Listening for connections at: tcp://server_name:61618 | org.apache.activemq.transport.TransportServerThreadSupport | main
2018-07-11 09:29:42,689 | INFO | Connector tcp://server_name:61618 Started | org.apache.activemq.broker.TransportConnector | main
2018-07-11 09:30:04,369 | WARN | Transport Connection to: tcp://server_name:58406 failed: java.io.EOFException | org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ Transport: tcp:///server_name:[email protected]
2018-07-11 09:57:57,698 | WARN | Transport Connection to: tcp://172.17.103.76:49348 failed: java.io.EOFException | org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ Transport: tcp:///server_name:[email protected]
2018-07-11 10:19:02,882 | WARN | Transport Connection to: tcp://172.17.103.76:49416 failed: java.net.SocketException: Connection reset | org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ Transport: tcp:///server_name:[email protected]
The avobe messages means that port 61618, which is the default for ActiveMQ, is being used by another application and could be causing this issue. In order to resolve this, the next steps can be followed:
1.- Keep SDM up and running.
2.- Stop PAM service.
3.- Navigate to ..CA\PAM\server\c2o\.config and open "OasisConfig.properties".
4.- Search for line 181 and 182, which will have the following information:
#Defines the tcp port of the activeMQ.
org.apache.activemq.tcp.port=61618
pam.mq.tcp.url=tcp://server_name:61618
5.- Change the value of the port used by ActiveMQ to an available port, for example:
#Defines the tcp port of the activeMQ.
org.apache.activemq.tcp.port=61630
pam.mq.tcp.url=tcp://server_name:61630
6.- Start PAM again and verify if now the second "Java.exe" starts and if the login page is shown.
1.- Stop both applications, on this case SDM and PAM.
2.- Start just SDM until it's fully up and running.
3.- Now, start PAM services.
4.- Right after it, open Task Manager and check the processes list looking for "java.exe", which is associate to PAM.
5.- When Java.exe is fully loaded (it will consume something near to 2 GB of RAM, but it depends on the environment) it should start a second "Java.exe", which is associated to the login. If you wait for 10 minutes after PAM services were started and this second "Java.exe" never started, the logs inside of the following folder can be reviewed: "..CA\PAM\activemq\data".
In the logs, the following error messages can be seen:
2018-07-11 09:29:42,689 | INFO | Listening for connections at: tcp://server_name:61618 | org.apache.activemq.transport.TransportServerThreadSupport | main
2018-07-11 09:29:42,689 | INFO | Connector tcp://server_name:61618 Started | org.apache.activemq.broker.TransportConnector | main
2018-07-11 09:30:04,369 | WARN | Transport Connection to: tcp://server_name:58406 failed: java.io.EOFException | org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ Transport: tcp:///server_name:[email protected]
2018-07-11 09:57:57,698 | WARN | Transport Connection to: tcp://172.17.103.76:49348 failed: java.io.EOFException | org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ Transport: tcp:///server_name:[email protected]
2018-07-11 10:19:02,882 | WARN | Transport Connection to: tcp://172.17.103.76:49416 failed: java.net.SocketException: Connection reset | org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ Transport: tcp:///server_name:[email protected]
The avobe messages means that port 61618, which is the default for ActiveMQ, is being used by another application and could be causing this issue. In order to resolve this, the next steps can be followed:
1.- Keep SDM up and running.
2.- Stop PAM service.
3.- Navigate to ..CA\PAM\server\c2o\.config and open "OasisConfig.properties".
4.- Search for line 181 and 182, which will have the following information:
#Defines the tcp port of the activeMQ.
org.apache.activemq.tcp.port=61618
pam.mq.tcp.url=tcp://server_name:61618
5.- Change the value of the port used by ActiveMQ to an available port, for example:
#Defines the tcp port of the activeMQ.
org.apache.activemq.tcp.port=61630
pam.mq.tcp.url=tcp://server_name:61630
6.- Start PAM again and verify if now the second "Java.exe" starts and if the login page is shown.
Feedback
Yes
No
Powered by
