I am getting an error from my datamapper mediator. I already did this before but this time I used the conf instead of gov for my data mapper input and ouput schema.
Here my api config
http://pastebin.com/41iweHs7
Here's the error
ERROR - DataMapperMediator Error while reading input stream. No content to map due to end-of-input
at [Source: java.io.ByteArrayInputStream#4942c854; line: 1, column: 1]
There shouldn't be any difference whether it is gov or conf. According to your error, it is due to a parse error in your input schema. Is your input type JSON or XML (your configuration says XML) ? Can you recheck whether it is the same Schema that worked earlier?
Related
I am trying to pull a private GCR image from my CD tool (DroneIO), but the following error is generated.
Error response from daemon: Get https://gcr.io/v2/xxx/xxx/xxxx/xx: unknown: Unable to parse json key.
I am using the json file that is generated when I create the service account
Have you followed the steps described in https://cloud.google.com/container-registry/docs/advanced-authentication#json_key_file? From the error message, it seems the json key may be invalid somehow or maybe there is some wrong with the way you pipe the json key.
Amazon S3 has a large number of reasons why it will return an HTTP 400 Bad Request error. Most relevant is the fact that some of these errors are from the unreliability of the internet, such as a request timeout. Another reason it might be returned is if the bucket or key name is invalid.
I am attempting to upload files to S3 with key names supplied by a customer-controlled key name. I need to be able to distinguish between a transient 400 error such as a timeout and a bad key/bucket name error that will not be transient. A transient error will indicate we should retry that upload, while a non-transient error means we should cease trying to upload that file.
However, I do not know how to distinguish between these two errors! If it matters, I am attempting to use the JetS3t API to perfom these uploads. How can I distinguish between a bad key/bucket name error and anything else with a 400 error code?
Read the response body.
From the page you cited:
The body o[f] the response also contains information about the error.
Parse the response body that accompanies the http error code. An explanation of the error is almost always spelled out in XML in the response body.
Example nonsense request (nothing edited here, this is exactly what I used for a GET request to generate this error):
http://example-bucket.s3.amazonaws.com/?AWSAccessKeyId=AKIAEXAMPLEEXAMPLE&Signature=bogus&Expires=1500000000
Response:
<Error>
<Code>InvalidAccessKeyId</Code>
<Message>
The AWS Access Key Id you provided does not exist in our records.
</Message>
<AWSAccessKeyId>AKIAEXAMPLEEXAMPLE</AWSAccessKeyId>
<RequestId>...</RequestId>
<HostId>...</HostId>
</Error>
You'll find a pretty close correlation between this content and the list of possible errors.
Now, technically, that's a 403 not a 400, it's just the first idea I came up with for an easily handcrafted nonsense request to generate an error, but any S3 error should generate a comparable response.
SBL-EIM-00205: Failed to load the application dictionary.
SBL-SVR-01042: Internal: Communication protocol error while instantiating new task SBL-EIM-00205: Failed to load the application dictionary.
This is a generic message, Siebel throws it all the time there is an issue in the repository. You will have to go through the log file and get the actual error message. Increase the component log level for EIM component to maximum and re-submit the job for the logs.
The structure of the EIM tables have to match the final tables, so it could be a mismatch of schema causes this error.
SBL-SVR-01042 this is generic error when this error is encountered while attempting to instantiate a new instance of a given component and is generic. As to why the error has occurred, one needs to review the accompanying error messages which will help provide context and more detailed information
SBL-EIM-00205: There could be many reason for this error.This is caused due to the incorrect ODBC registry entries. or some issue with Foreign key mapping.
You should increase log level and get more details.
I am consuming the webservice https://www.uat.p20.experian.nl/WS_SDPGateway/sdpgateway.asmx?wsdl.
I am getting an error:
ERROR
ERROR 2015-09-21 23:08:04,789 [[experian_spd_sandbox].HTTP_8044.worker.01] org.mule.exception.DefaultMessagingExceptionStrategy:
Message : COULD_NOT_READ_XML_STREAM. Failed to route event via endpoint: org.mule.module.cxf.CxfOutboundMessageProcessor. Message payload is of type: byte[]
Type : org.mule.api.transport.DispatchException
Code : MULE_ERROR--2
Payload : [B#df32cd7
JavaDoc :
Exception stack is:
Unexpected character '>' (code 62) expected '='
at [row,col {unknown-source}]: [7,21] (com.ctc.wstx.exc.WstxUnexpectedCharException)
com.ctc.wstx.sr.StreamScanner:647 (null)
COULD_NOT_READ_XML_STREAM (org.apache.cxf.interceptor.Fault)
org.apache.cxf.databinding.stax.StaxDataBinding$XMLStreamDataWriter:151 (null)
COULD_NOT_READ_XML_STREAM. Failed to route event via endpoint: org.mule.module.cxf.CxfOutboundMessageProcessor. Message payload is of type: byte[] (org.mule.api.transport.DispatchException)
org.mule.module.cxf.CxfOutboundMessageProcessor:163
My goal is just to fix the communication and ensure the webservice can be consumed properly from Mule.
"Failed to route event via endpoint" sounds more like a network then a parse error.
Can you try to curl the wsdl from the box that is executing the Mule flow?
Found it:
Afterall it was a mistake in the XML message itself. In addition I had to remove the metadata I had added during trouble shooting. So in case you run into the same just go back to basic and first validate the XML message ;-)
Thanks all for getting me there.
I'm using MPGW service which will hit the CICS service and return back the response.
This is my flow. UI --> DP MPGW gateway --> MPGW Service --> CICS service.
In case of "No data Found" response from CICS, I just want to set the error code as 100 and message as "No data found" and pass on to UI. But everytime datapower is return 500 Internal server error to UI.
I'm using errorHandler.xslt to check the fault code from CICS and setting the error code and error message.
Is there something I need to change the dp:response-header('x-dp-response-code')? If so how to do this?
Note: Process Backend error : 'On' in both the MPGW(gateway and service).
Try this:
If a response contains 500 not found error. Do a dp:reject at the response rule.This will take control to error rule. At error rule, configure an xslt and set below values:
<dp:set-variable name="'var://service/error-protocol-response'" value="'100'" />
<dp:set-variable name="'var://service/error-protocol-reason-phrase'" value="'No Data Found'" />
As per https://www.ibm.com/developerworks/community/forums/html/topic?id=77777777-0000-0000-0000-000014432297 you want:
Within an Error Rule:
Within a Response Rule:
That should do the trick for an MPGW I believe.