I am using XMPPFramework to connect to my xmpp server on local network ,it connects but as soon as it sends the auth packet and recieves challenge it disconnects with error : "internal error" code=1 ErrorDomain=libxmlErrorDomain. Basically it is not able to parse the challenge :
2013-03-08 15:56:41.890 iPhoneXMPP[23710:13703] Data to be parsed <challenge xmlns="urn:ietf:params:xml:ns:xmpp-sasl">cmVhbG09ImluZm9zeXMuY29tIixub25jZT0ib05JYmxSU2hLQXUxWnorRUNGbmRJby83Snljdm5DLzNKQWV2SXB5UCIsY2hhcnNldD11dGYtOCxhbGdvcml0aG09bWQ1LXNlc3M=</challenge>
2013-03-08 15:56:41.891 iPhoneXMPP[23710:13703] Parser failed
How can i solve this issue,is it something related to how i have configured my xcode to work with libxml2 ?
There was a extra charcter at the end of each packet,due to which the SAX parser libxml2 was failing.trimming each packet by one character solved the problem.
Related
I use ApiKit to receive queries. Occasionally I get the following line in a log file:
WARN org.mule.module.http.internal.listener.grizzly.ResponseCompletionHandler - HTTP response sending task failed with error: Locally closed
It seems that in this case the integration has not sent a response to the party that called the integration. I thought that there might be a sort of timeout before ApiKit closes the connection to caller but based on timestamps that might not be the case as everything happens within a second.
In this case the payload is sent to Artemis queue before this warning and despite the warning the message is read from Artemis normally and the whole flow works otherwise just fine besides this warning and not sending the response.
So, am I correct when I think that this warning is an indication why the response is not sent? In addition to that what can be done to prevent this situation?
Ok I am using service broker all other sent through service broker work fine. Except one single message is stuck in the transmission queue and will not send. Only error message I see is:
Connection attempt failed with error: '10060(A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)'.
But it's not clear that is related. Again on other messages of same message type sent are working normally.
The issue was Service Broker not working when XML contains special
characters
The issue was that in generating xml to be sent over service broker we had an á (a-acute) in our document. We overcame this issue by switching the message type from VALIDATION =
WELL_FORMED_XML to
VALIDATION = None.
We then modified
activated stored procedure on the receiving queue. Changing the line
#message_body = CAST(message_body as XML),
-- to
#message_body = CAST(CAST(message_body AS VARCHAR(MAX)) AS XML),
This solved the issue.
I believe alternatively we could have sanitized our xml to replace the á (a-acute) with and html char code, but are use case requires us to allow the use of a lot of special characters which would be hard to id up front.
Connection attempt failed with error: '10060(A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)'.
This message was due a connection issue with another service broker instance running on the same server.
The error from PI when I try to send to SAP system is:
transmitting the message to endpoint http://xxx.xx.xx.xx:50400/sap/xi/engine?type=entry using connection jdbc_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Received HTTP response code 404: Not Found
When I am trying the link http://xxx.xx.xx.xx:50400/sap/xi/engine?type=entry I am getting the error HTTP 404.
Can someone tell me what to check?
Thanks
PS Where Can I change the port?
The problem was on the port in the above url (http : //xxx.xx.xx.xx:50400/sap/xi/engine?type=entry). It is 50000 instead of 50400.
The solution must be done in the following path: SAP XI transaction: SXMB_IFR. Then System Landscape Directory->Business Systems->INTEGRATION_SERVER_VPD->INTEGRATION TAB.
Here in the PIPELINE URL exists the wrong url and here you must correct it.
Thanks
I'm trying to get a Labview VI working. However, I'm getting an error on the KE6485 Multi-read sub-VI with the error "Driver Status: (Hex 0xBFFF004A) Error - A service request has not been received for the session". Does anyone have a suggestion on steps I could take to fix this?
We have seen much more SSL error than before when we move to a new server. The total SSL error rate is not high. Many of them are:
error:140943E8:SSL routines:SSL3_READ_BYTES:reason(1000):s3_pkt.c:1256:SSL alert number 0
We finally found these requests are actually successful requests. Why these error was generated is that openssl found these were fatal error. Add more debug info show that:
ssl_callback_info:SSL_CB_READ_ALERT fatal error close notify
But from rfc2246:
7.2.1. Closure alerts
The client and the server must share knowledge that the connection is
ending in order to avoid a truncation attack. Either party may
initiate the exchange of closing messages.
close_notify
This message notifies the recipient that the sender will not send
any more messages on this connection. The session becomes
unresumable if any connection is terminated without proper
close_notify messages with level equal to warning.
We are wondering if there some special clients send "alert 0" as fatal . Or this related some known issue of openssl. We are using openssl-1.0.1e now. Before migration we used openssl-1.0.0-25.
Any suggestions would be appreciated.
Update:
I investigated the access log and found almost all the "fatal alert 0" was sent by Safari on Apple devices(Mac, iPhone, iPad).
Through the code of libsecurity_ssl which the library of SSL engine. I found that this library would send "fatal alert 0" in sometimes that was totally different with other SSL libraries, for example openssl, NSS.
SSLFatalSessionAlert(SSL_AlertCloseNotify, ctx);
http://www.opensource.apple.com/source/libsecurity_ssl/libsecurity_ssl-32463/lib/sslRecord.c
This mostly occurred when Safari meet unexpected abort of the connection. As my server would not sent a "warning alert 0" to close the connection.