Unable to connect to the Vantage Web Client (MTC-M)
search cancel

Unable to connect to the Vantage Web Client (MTC-M)

book

Article ID: 245073

calendar_today

Updated On:

Products

Vantage Storage Resource Manager

Issue/Introduction

When attempting to connect to the new 14.01 release of the Vantage Web Client (MTC-M), we receive messages such as "Unable to Connect" and "Problem Loading Page", etc.  When this has happened intermittently in the past, we were able to temporarily resolve the problem by bouncing the SAMSWEB started task, but now we're not able to connect at all.

Also, messages such as the following were seen in the SAMSWEB STC: 

INFO: Error parsing HTTP request header                                        
 Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.
java.lang.IllegalArgumentException: Invalid character found in the request target ¨/<script>alert(53416)</script> (. The valid characters are defined in RFC 7230 and RFC 3986
...
...

INFO: Error parsing HTTP request header                                        
 Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.
java.lang.IllegalArgumentException: Invalid character found in method name ¨id0x0a...(. HTTP method names must be tokens
.at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:419) 

...
...

INFO: Error parsing HTTP request header                                        
 Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.
java.lang.IllegalArgumentException: Invalid character found in the HTTP protococol ¨5.2-dev/ (  
.at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:570)

 

 

Environment

Release : 14.1

Component : Vantage Storage Resource Manager

Cause

An incorrect URL was being used to connect to the MTC-M (web client).

Resolution

The URL used to connect to the Web Client (MTC-M) specified an incorrect address.  The Web Client STC was installed on 'LPAR 1', but it was later accessed via another LPAR (i.e., 'LPAR 4'), and an attempt was made to connect to MTC-M specifying a URL associated with 'LPAR 4' instead of 'LPAR 1'.  For example: 

Bad URL:  http://xxx.yy.zz.4:8080/VantageGMI/

Good URL:  http://xxx.yy.zz.1:8080/VantageGMI/

Note that in this case the 'Vantage Summary Report' (which gets generated during the full install process for MTC-M) showed the incorrect URL:  http://xxx.yy.zz.4:8080/VantageGMI/  (since this part of the install process was run from 'LPAR 4' instead of 'LPAR 1').