Problems with Web Admin
This section describes problems that relate to the Web Admin application used with DirX Identity and how to solve them.
No Connection to Java-based Identity Server
Indication:
You cannot connect with Web Admin to the Java-based Server even if the Java-based Server is running.
Reason:
There is no thread left in the integrated Tomcat (part of Java-based Server).
Solution:
Increase the number of threads for the integrated Tomcat:
-
Log in with DirX Identity Manager to the Connectivity view group.
-
Open Configuration → DirX Identity Servers → Java Servers → Your_Server.
-
Select the Limits tab.
-
Increase the maximum number of threads for Tomcat.
-
Restart the Java-based Server.
-
Check that Web Admin works now.
-
If not, repeat the procedure.
Node for C++-based Identity Server is not Displayed
Indication:
The node for the C++-based Server is not displayed.
Reason:
The connector server connection to the C++-based Server is not working.
Solution 1:
Enable the connector server connection:
-
Edit the file install_path/server/conf/dxmmsssvr.ini.
-
Set the switch cconnserver to 1.
-
The resulting section is:
; optional: start SOAP SPML connector service (requires a configured port)
cconnserver=1 -
Restart the C++-based Server.
Solution 2:
-
Check that the port 5315 (or the configured port) is blocked by a firewall.
-
Open the firewall if this is the case.
Solution 3:
Test the connection:
-
Enter the address "http://localhost:5315/" in any web browser.
-
The returned SOAP answer should be:
<SOAP-ENV:Envelope>
<SOAP-ENV:Body id="_0">
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Client</faultcode>
<faultstring>Server custom error</faultstring> <SOAP-ENV:Code/> <SOAP-ENV:Detail> Error receiving the JMX request data, msg: gSOAP error while receiving data, socket = 796, errcode = 14 </SOAP-ENV:Detail> </SOAP-ENV:Fault> </SOAP-ENV:Body> </SOAP-ENV:Envelope> -
If this is not the answer, check the C++-based Server log files for error messages.