When I run the diagnostics on the Rule Execution Server console of the Business Rules service, I see a warning saying "No XU MBean found". Is this expected?
I found that this warning is expected if no rulesets have been executed yet. Once a ruleset has been executed (and hence the the XU or the Execution unit has been called at least once), this warning disappears.
Related
I'm running an SAP PI/PO scenario and having a problem with finding the response message (the error one).
Scenario:
PROXY (class) -> SAP PI/PO 7.5 -> SOAP (wsdl)
The error when executing the scenario is:
Transmitting the message using connection
SOAP_http://sap.com/xi/XI/System failed, due to:
com.sap.engine.interfaces.messaging.api.exception.MessagingException:
Error encountered while executing mapping:
com.sap.aii.af.service.mapping.MappingException:
com.sap.aii.utilxi.misc.api.ResourceException: Could not determine
mapping steps for message 3b14b3f8-0860-11ed-a034-000001795062
The problem is that I cannot find the message (3b14b3f8-0860-11ed-a034-000001795062) in SAP PI monitor. It's the response message (who is causing the error), as the request message I did find in the monitor and it's correct.
Where I can find it? Why is not showing?
From what I read, this problem happens with several reasons, I just want to find this message.
The webservice works correctly, I test it in SOAP UI.
To find the response message (which contains the error), we have to first activate the Integrated Configuration log (it's not active by default).
To activate the log, we have to follow these steps (more info: https://blogs.sap.com/2012/11/06/message-staging-and-logging-options-in-advanced-adapter-engine-of-pi-73x/)
Go to "Advanced Settings" in the target Integrated Configuration.
Change the "Use global configuration" radio button to "Use scenario-specific configuration" in both, "Staging" and "Loging".
Change all "Staging" lists to "Store".
Change all "Logging" lists to "Log".
Save and activate.
Now, in the SAP PO monitor (Message monitor), by clicking the "Related Messages" option, we can see the response message error.
In this case, the error was:
<sap:Error xmlns:sap='http://sap.com/xi/XI/Message/30'
SOAP:mustUnderstand='1'>sap:CategoryXIAdapter</sap:Category><sap:Code
area='SOAP'>FAULT</sap:Code>sap:P1http://schemas.microsoft.com/ws/2005/05/addressing/none</sap:P1>sap:P2ActionNotSupported</sap:P2>sap:AdditionalTextThe
message with Action '' cannot be processed at the receiver, due to a
ContractFilter mismatch at the EndpointDispatcher. This may be because
of either a contract mismatch (mismatched Actions between sender and
receiver) or a binding/security mismatch between the sender and the
receiver. Check that sender and receiver have the same contract and
the same binding (including security requirements, e.g. Message,
Transport, None).</sap:AdditionalText><sap:ApplicationFaultMessage
namespace='http://schemas.microsoft.com/ws/2005/05/addressing/none'>ActionNotSupported</sap:ApplicationFaultMessage></sap:Error>
In which the Action was empty.
I am executing a workflow in informatica which is supposed to inset values in a target file.
Some of the records are getting inserted but i get an error after a few insertions saying:
[Informatica][ODBC PWX Driver] PWX-00267 DBAPI error for file……… Write error on record 119775 Requested 370 SQLSTATE [08S01]
Is this because of file constraints of how the record can be or due to some other reasons?
I'm not sure if this is exactly the case, but looking for the error code 08S01 I've found this site that lists Data Provider Error Codes. Under SQLCODE 370 (assuming this is what your error message indicates) I've found:
Message: There are insufficient resources on the target system to
complete the command. Contact your server administrator.
Reason: The resource limits reached reply message indicates that the
server could not be completed due to insufficient server resources
(e.g. memory, lock, buffer).
Action: Verify the connection and command parameters, and then
re-attempt the connection and command request. Review a client network
trace to determine if the server returned a SQL communications area
reply data (SQLCARD) with an optional reason code or other optional
diagnostic information.
In the new Azure portal I see under "Metrics" section for an EventHub that there were many "Internal Server Error" events on a specific day. Is it possible to find out more about what could have caused it and description about those errors?
As the metrics for Event Hubs state about InternalServerErrors and OtherErrors:
InternalServerErrors: Total number of internal server error exceptions sent back to the sender or receiver while performing run-time operations. This type of error is due to either service-side or network problems.
OtherErrors: These types of errors are due to faults at the sender or receiver side, such as providing bad parameters, not enough credentials, or trying to perform an operation on a nonexistent entity.
I would recommend you log into azure portal, choose your Event hub, click "MONITORING > Diagnostics logs", then turn on diagnostics for collecting logs. For more details, you could refer to Event Hubs diagnostic logs.
I have downloaded wso2 esb 5.0.0 into local but when I started it's starting with log level DEBUG. I would like t change the log level to ERROR by default when ever server started.
Looks like log level in registry will override log level in property files so is there a way to edit log level in registry or any other configuration file
All WSO2 products uses a log4j based logging mechanism. Through log4j.properties file, <ESB_HOME>/repository/conf directory, this can be controlled.
WSO2 recommends to not to modify log4j.properties directly but rather through management console. The settings in the management console override the settings in log4j.properties.
For the respective loggers, check the log level and set it appropriately.
TRACE - Designates finer-grained informational events than the DEBUG.
DEBUG - Designates fine-grained informational events that are most useful to debug an application.
INFO - Designates informational messages that highlight the progress
of the application at coarse-grained level.
WARN - Designates potentially harmful situations.
ERROR - Designates error events that might still allow the application to continue running.
FATAL - Designates very severe error events that will presumably lead
the application to abort.
For the following loggers, change the log levels to ERROR.
log4j.category.org.apache.synapse=ERROR
log4j.category.org.apache.synapse.transport=ERROR
log4j.category.org.apache.axis2=ERROR
log4j.category.org.apache.axis2.transport=ERROR
log4j.logger.org.wso2=ERROR
log4j.logger.org.wso2.carbon=ERROR
log4j.appender.CARBON_LOGFILE.threshold=ERROR
log4j.appender.CARBON_MEMORY.threshold=ERROR
log4j.appender.CARBON_SYS_LOG.threshold=ERROR
log4j.appender.AUDIT_LOGFILE.threshold=ERROR
note: Even Important info statements like server startup will not be printed due to this change.
Refer the post for insights into tracking messages across different WSO2 components: http://muralitechblog.com/wso2-esb-how-to-track-messages/
https://docs.wso2.com/display/ESB490/Setting+Up+Logging
When running the Diagnostics for the Rule Execution Server for the Business Rules instance on Bluemix, I see the following warning:
Decision Runner Resource Provider
Warning
Diagnostic failed
Run the installation wizard to create database tables
this question is already answered in the IBM developer forum.
Excerpt from the link :
This warning is expected for the Business Rules service on Bluemix, and can be safely ignored. You will see it if your instance uses the version Decision Server 8.7.0.1. (See the About section in the Rule Execution Server console).
Hope it helps.