Verified Answers


If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Suggested Answer
  • Replies reply
    1
  • Answers answer
    1
  • Subscribers subscribers
    12
  • Views views
    70
  • Users 0 members are here
Related
Options

PPM Wokbench App - Socket closed exception

Madhu Mishra

This particular user is having issues launching workbench from open workbench App. After clicking on startup.bat , the below error appears.We have validated the java version ,its same as other users. User has PATH variable updated with this path as well C:\Program Files\Java\jdk-1.8\bin. Can I get some guidance here please.

Workbench starting up.
** Your URL: rmi://<url>:<port>/KintanaServer
Using locale: en_US
connecting to rmi://<url>:<port>/KintanaServer
2024-08-13 14:43:03 ERROR  com.kintana.core.client.ValidationManager.preloadCriticalValidations(ValidationManager.java:116) -ValidationManager.java:116 -  com.kintana.rmi.RemoteException: Connection reset; nested exception is
        java.net.SocketException: Connection reset
com.kintana.rmi.RemoteException: Connection reset; nested exception is
        java.net.SocketException: Connection reset
        at com.kintana.rmi.ObjectBrokerConnection.close(Unknown Source)
        at com.kintana.rmi.ObjectBrokerConnection.run(Unknown Source)
2024-08-13 14:43:03 ERROR  com.kintana.core.util.DPCacheManager.preloadCriticalDPComponents(DPCacheManager.java:255) -DPCacheManager.java:255 -  com.kintana.rmi.UnexpectedException: Socket closed; nested exception is
        java.net.SocketException: Socket closed
com.kintana.rmi.UnexpectedException: Socket closed; nested exception is
        java.net.SocketException: Socket closed
        at com.kintana.core.server.BasePluginImpl_Stub.preloadCriticalDPComponents(BasePluginImpl_Stub.java:3435)
        at com.kintana.core.util.DPCacheManager.preloadCriticalDPComponents(DPCacheManager.java:239)
        at com.kintana.core.client.SessionManager.corePostLogon(SessionManager.java:475)
        at com.kintana.core.client.SessionManager.logon(SessionManager.java:551)
        at com.kintana.core.client.LogonManager.logon(LogonManager.java:108)
        at com.kintana.core.gui.LogonApplet$LogonListener$1.run(LogonApplet.java:1005) 

Fatal Error: Failed loading validation profiles: com.kintana.rmi.UnexpectedException: Socket closed; nested exception is
        java.net.SocketException: Socket closed
GUID=D0997ABA-4F93-2B7A-BF77-F95476F010D7
Generated Time=2024/08/13-05:13:03.239 GMT-04:00
        at com.kintana.core.util.VPCacheManager.preloadValidationProfiles(VPCacheManager.java:61)
        at com.kintana.core.client.SessionManager.corePostLogon(SessionManager.java:476)
        at com.kintana.core.client.SessionManager.logon(SessionManager.java:551)
        at com.kintana.core.client.LogonManager.logon(LogonManager.java:108)
        at com.kintana.core.gui.LogonApplet$LogonListener$1.run(LogonApplet.java:1005)

  • Suggested Answer

    0  

    Hi Madhu,

    "Socket closed" likely means that the network connection has been interrupted, most likely on the client (i.e. User) side. The most likely culprit could an antivirus/firewall on the user's computer forcibly closing the connection.

    Most importantly, it looks like you're still using RMI for workbench connectivity; this is considered outdated and very likely not to be handled properly by firewalls - you should consider switching workbench connectivity to HTTP(S) instead of RMI(S) if that's not already the case.

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.