AnsweredAssumed Answered

RESTFul Web-service connector not working in 6.9

Question asked by Tushar Sutar on Aug 16, 2016
Latest reply on Aug 30, 2016 by Tushar Sutar

Like • Show 0 Likes0
Comment • 7

This is continuation to previous discussion,

How to consume YAML Web Service using RESTFul Connector

But the other one was for version 6.9.1

Our production is still on 6.9 and we are in planning phase for upgrade. After successful execution of restful connector on 6.9.1 we thought may be we can move it to production with same configuration used in 6.9.1

But with same configuration we are getting error,

Test Capabilities Error
Error code = 2 Failure - Error processing RESTful web service response Cause: Error processing RESTful web service response: java.lang.IllegalStateException: Expected application/json but received text/html; charset=iso-8859-1

Test Capabilities Error

Error code = 2

Failure - Error processing RESTful web service response   
Cause:  Error processing RESTful web service response: java.lang.IllegalStateException: Expected application/json 
but received text/html; charset=iso-8859-1

Just because of above error if I change 'Accept' type to 'text/html' then I am getting further errors for parsing.

Our current configuration on PROD is as below,

Settings -

Capabilities -

capabilities

Any help is much appreciated.

Cory Veilleux

Aug 29, 2016 1:24 PM

Correct Answer

Hi Tushar,

After looking through the logs more and looking through past issues, from the request that's being sent it looks like it's URL-encoding the path to the REST endpoint. So instead of using the path /it/ds/api/role.php, it's using /it%2Fds%2Fapi%2Frole.php. On the 404 page the server is translating that back to the forward-slash version, but in the end it's a different URL than the actual service URL. It's for this reason that the server is responding with a 404.

This is due to a bug that's been fixed in 6.9.0 P01 and 6.9.1 (which is why it works in your development environment), but the bug is present in 6.9.0 GA. I hope that helps - unfortunately you'll have to upgrade production to either 6.9.0 P01 or 6.9.1 in order to resolve this issue.

Thanks,

Cory

See the reply in context

Attachments

mule.AFX-CONN-CyberArkREST.log.7z.zip67.2 KB

No one else had this question

Outcomes

Tushar Sutar Aug 17, 2016 10:18 AM

Any updates on this ?

Actions

Boris Lekumovich

@ Tushar Sutar on Aug 17, 2016 11:01 AM

Based on the error message, I would try to change the accept to:

text/html; charset=iso-8859-1

Actions

Tushar Sutar @ Boris Lekumovich on Aug 19, 2016 8:00 AM

If I change it,

then error is,

Failure - Error processing RESTful web service response
Cause: 
Error processing RESTful web service response: org.mule.api.MuleRuntimeException: 
Failed to process Expression Evaluation "json:status"

And if I go on changing further configuration, I get NumberFormatException.

My concern with this one is, if I am not able to parse response successfully then at least on end system (LDAP), role should be added to account right ?

Actions

Cory Veilleux

@ Tushar Sutar on Aug 17, 2016 11:02 AM

In looking through the log, you're getting a 404 html error page:

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<HTML><HEAD>
<TITLE>404 Not Found</TITLE>
</HEAD><BODY>
<H1>Not Found</H1>
The requested URL /it/ds/api/role.php was not found on this server.<P>
<HR>
<ADDRESS>Apache/1.3.26 Server at it.intra.sears.com Port 2080</ADDRESS>
</BODY></HTML>

Are you sure that the path is correct?

Actions

Tushar Sutar @ Cory Veilleux on Aug 19, 2016 8:11 AM

Cory,

I did notice same error before uploading the file here, but I was not sure if connector is failing to make the connection itself OR it is not.

A connection failure error should have different one ? Isn't it? instead of for accept-type

Same connection (service) can be called from our DEV, UAT, and from my own machine (Above I have posted a pic where I have used Mozilla extension to call the service).

So what would be missing thing here? Do you want me to change something and generate Debug logs again?

Actions

Cory Veilleux

@ Tushar Sutar on Aug 29, 2016 1:24 PM

Hi Tushar,

Thanks,

Cory

Actions

Tushar Sutar @ Cory Veilleux on Aug 30, 2016 3:54 AM

Yes, we are pushing our management for 6.9.1 upgrade.

Actions

7 Replies

Tushar Sutar Aug 17, 2016 10:18 AM
Mark Correct
Correct Answer
Any updates on this ?
Like • Show 0 Likes0
Actions
- Boris Lekumovich @ Tushar Sutar on Aug 17, 2016 11:01 AM
  Mark Correct
  Correct Answer
  Based on the error message, I would try to change the accept to:
  text/html; charset=iso-8859-1
  Like • Show 0 Likes0
  Actions
  - Tushar Sutar @ Boris Lekumovich on Aug 19, 2016 8:00 AM
    Mark Correct
    Correct Answer
    If I change it,
    then error is,
    
    Failure - Error processing RESTful web service response Cause: Error processing RESTful web service response: org.mule.api.MuleRuntimeException: Failed to process Expression Evaluation "json:status"
    
    And if I go on changing further configuration, I get NumberFormatException.
    
    My concern with this one is, if I am not able to parse response successfully then at least on end system (LDAP), role should be added to account right ?
    Like • Show 0 Likes0
    Actions
- Cory Veilleux @ Tushar Sutar on Aug 17, 2016 11:02 AM
  Mark Correct
  Correct Answer
  In looking through the log, you're getting a 404 html error page:
  
  <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
  <HTML><HEAD>
  <TITLE>404 Not Found</TITLE>
  </HEAD><BODY>
  <H1>Not Found</H1>
  The requested URL /it/ds/api/role.php was not found on this server.<P>
  <HR>
  <ADDRESS>Apache/1.3.26 Server at it.intra.sears.com Port 2080</ADDRESS>
  </BODY></HTML>
  
  Are you sure that the path is correct?
  Like • Show 0 Likes0
  Actions
  - Tushar Sutar @ Cory Veilleux on Aug 19, 2016 8:11 AM
    Mark Correct
    Correct Answer
    Cory,
    
    I did notice same error before uploading the file here, but I was not sure if connector is failing to make the connection itself OR it is not.
    
    A connection failure error should have different one ? Isn't it? instead of for accept-type
    
    Same connection (service) can be called from our DEV, UAT, and from my own machine (Above I have posted a pic where I have used Mozilla extension to call the service).
    
    So what would be missing thing here? Do you want me to change something and generate Debug logs again?
    Like • Show 0 Likes0
    Actions
    - Cory Veilleux @ Tushar Sutar on Aug 29, 2016 1:24 PM
      Unmark Correct
      Correct Answer
      Hi Tushar,
      
      After looking through the logs more and looking through past issues, from the request that's being sent it looks like it's URL-encoding the path to the REST endpoint. So instead of using the path /it/ds/api/role.php, it's using /it%2Fds%2Fapi%2Frole.php. On the 404 page the server is translating that back to the forward-slash version, but in the end it's a different URL than the actual service URL. It's for this reason that the server is responding with a 404.
      This is due to a bug that's been fixed in 6.9.0 P01 and 6.9.1 (which is why it works in your development environment), but the bug is present in 6.9.0 GA. I hope that helps - unfortunately you'll have to upgrade production to either 6.9.0 P01 or 6.9.1 in order to resolve this issue.
      
      Thanks,
      Cory
      Like • Show 1 Like1
      Actions
      - Tushar Sutar @ Cory Veilleux on Aug 30, 2016 3:54 AM
        Mark Correct
        Correct Answer
        Yes, we are pushing our management for 6.9.1 upgrade.
        Like • Show 0 Likes0
        Actions

RESTFul Web-service connector not working in 6.9

Attachments

Outcomes

Related Content

Recommended Content