Error connecting from Eclipse to Endevor 18.0 Web Services and Eclipse-Based UI

Products

• Endevor
• Endevor - ECLIPSE Plugin

Issue/Introduction

Tried to connect Eclipse to the host using Endevor 18.0 Web Services and Eclipse-Based UI component, but got the following error:

2019-10-02 11:50:27.167: [CSE2] Connection has failed, please contact system Administrator.

URL: http://www.example.com Config: null

org.apache.axis2.AxisFault: Transport error: 404 Error:

                 at org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:310)

                 at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:194)  

                 at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:404)

                 at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:231)

                 at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:443)

                 at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:406)

                 at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)

                 at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)

                 at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:555)

                 at com.ca.endevor.service.EndevorVersion.getEndevorVersion(EndevorVersion.java:67)

In TOMCAT started task:               

Oct 02, 2019 9:59:58 AM org.apache.coyote.AbstractProcessor parseHost   

INFO: The host ݨ is not valid                                                             

 Note: further occurrences of request parsing errors will be logged at DEBUG level.            

java.lang.IllegalArgumentException                                                         

 at org.apache.tomcat.util.http.parser.Host.parse(Host.java:73)                           

 at org.apache.tomcat.util.http.parser.Host.parse(Host.java:40)                           

 at org.apache.coyote.AbstractProcessor.parseHost(AbstractProcessor.java:277)             

 at org.apache.coyote.http11.Http11Processor.prepareRequest(Http11Processor.java:1203)    

 at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:776)             

 at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)      

 at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:800)

 at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1471)   

 at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)       

 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1160)       

 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)       

 at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)    

 at java.lang.Thread.run(Thread.java:818)                                                  

Environment

Release : 18.0

Component : CA Endevor Software Change Manager

Cause

1 - There are HTTP/HTTPS mismatches. The protocol and port in the URL used by the client to perform requests or connect to Eclipse UI and the port and/or redirected port defined in their server.xml file shows a conflict. SSH (HTTPS) is defined in server.xml which creates a problem. Their apiml.properties file might be interfering as well, even though they have APIML_ENABLED set to N in their ENWSInstallOptions.properties.

2 - The EndevorService directory and the EndevorService.war file cannot be found under the ../tomcat/webapps directory. Their ENWSInstallOptions.properties file shows that ENDEVOR_TOMCAT_INSTANCE and ENDEVOR_SOFTWARE_DIR share a common path in the definition. The ENWSIns.sh installation script first removes the EndevorService.war from the ENDEVOR_TOMCAT_INSTANCE/webapps directory. After that, it copies EndevorService.war from ENDEVOR_SOFTWARE_DIR/tpv/tomcat/webapps to ENDEVOR_TOMCAT_INSTANCE/webapps. The problem is that, in their case, both paths are equal. Hence, the EndevorService.war is removed and cannot found later on. 

Resolution

1 - The SSH sections defined in server.xml have been commented out or removed. The parameters related with API Mediation Layer Discovery Service in the ENWSInstallOptions.properties file have been commented out or removed as they have defined APIML_ENABLED=NO. They did not need the apiml.properties file in the ../webapps/endevor directory because they are not implementing the mediation layer, so they have removed it as well.

2 - The problem was fixed by changing the path of ENDEVOR_SOFTWARE_DIR specified in the ENWSInstallOptions.properties file. Now ENDEVOR_SOFTWARE_DIR and ENDEVOR_TOMCAT_INSTANCE do not share a common path pointing to the same location. The ENWSIns.sh installation script runs successfully placing the EndevorService directory and the EndevorService.war file under the ENDEVOR_TOMCAT_INSTANCE/webapps directory.

*Notice that ENDEVOR_TOMCAT_INSTANCE is the parameter that indicates the path that will be used for the CA Endevor Tomcat instance and that it can point to the same location than TOMCAT_HOME_DIR. On the other side, ENDEVOR_SOFTWARE_DIR is the parameter pointing to the path where CA Endevor SCM has been installed to and should contain the folders software and tpv.