I am trying to resubmit a report using quickfixj ,on first submission the report is submitted successfully but when i try to re submit the same report, i get error saying: Serious Error :Message sequence number 1 expecting 326 while resubmitting ,In the event logs I could find session is created called,to admin and from admin called.After that onlogout is called giving the above error with msgtype =2
Is this an error on client side or the server side?pls suggest.I have also tried using resetmessagesequence=Y and resetonlogout=Y in the config file on default level .But I get the same errors on resubmitting the report .Please advise
Related
We're installing FSL and have run into a problem with the FSL Mobile App when we go to consume products.
The error message is "Product2.Material_Code__c like '%search term entered%' or Product2.Product_Image__c like '%search term entered%'
ERROR at ROw:1:Column:368 field 'Product_Image__c' can not be filtered in a query call.
In the error message above %search term entered% is whatever we search on not part of the error message.
Product_Image__c is a pre-existing rich text area custom field on the Product2 table.
Does anyone know how this field got into the SOQL and how we can take it out or otherwise resolve this error.
Sshot of error messageError message on product search.
Regards
Anushka
I am trying to handle a FIX Reject (MsgType 35=3), but I am unclear on how to retrieve the message that is referred to by the FIX Reject message.
The FIX Reject refers to the rejected message by MsgSeqNum, in the RefSeqNum field (tag 45). However I don't know how to get the rejected message by its sequence number. I think it should be possible because the FIX engine can resend messages in a sequence number range (in response to a resend request), so if the engine can do it so should I.
The question: how do I get the message that is referenced by the reject message in the RefSeqNum field?
Do you want to programmatically handle this failure? Generally the lower level rejects should never happen in the production environment. I have always dealt with them while testing and manual inspection of messages to identify the actual message and the tag having the problem.
In any case you can programmatically get the message by:
First looking up the session using Session Session.lookupSession(SessionID sessionId)
Get the MessageStore associated with the Session using MessageStore Session.getStore()
Obtain the actual message using MemoryStore.get(int startSequence, int endSequence, Collection<String> messsages)
You can find API documentation for QuickFIX/J here, or visit the documentation folder.
Note that in step 3 you will have to pass the same sequence number as the start and the end sequence number.
I'm working on update operation and trying to update with invalid id which is greater than 10 digit.
Ex. PUT /api/addresses/76412345678
For the above api I receive 400 status code with no error message from the api. It is difficult to know what it the error with just 400 status code.
Please confirm on how to handle this error? Will the api community be handling this error from their end?
I am attempting to get user comments on a network update. Some updates fail with the error "The update mapping to user's update-key cannot be processed."
I'm getting the updates from people/~/network/updates. Then I'm using the updateKey returned to query people/~/network/updates/key={updateKey}/update-comments.
One of the updates giving me this error is a company update so I tried companies/{company_id}/updates/key={update_key}/update-comments but It gave the same error.
What exactly does it mean by the key can't be processed and what do I need to do to get the comments?
I am fetching data from server into my iPhone app.
For fetching data from server, I am using HTTP Post method and for parsing data obtained I am using SBJSON Parser.
When the first time my app launches, the data is not fetched.
It shows the following failure log in Console. The app does not crash but just that data is not fetched.
<html>Your request timed out.
Please retry the request. </html>
2011-04-21 08:39:06.339 Hive[1594:207] -JSONValue failed. Error trace is: (
"Error Domain=org.brautaset.JSON.ErrorDomain Code=3 \"Unrecognised leading character\" UserInfo=0x4cabe90 {NSLocalizedDescription=Unrecognised leading character}"
)
The app fetches data properly from the second time onwards. It only gives this error when the app runs the first time.
What could be wrong?
Without analysis of the server and its resources it is difficult to determine why the server is taking too long to respond.
One thing to think about is how much time occurs between the last time you make the JSON attempt and the next time you make your "first attempt". Maybe then see if you an recreate it using a web browser.
Is the server a production quality server? If not, it may be "spinning up" to answer the first request which takes too long for the first response.
Personally, I wrote a generic JSON feed class that has a failure retry option. If it receives nothing or invalid JSON, it will retry x times at y seconds intervals based on what you pass it. It takes a little more work initially but it will payoff for two reasons.
1) It can be reused over and over and an update, like using ASIHTTRequest like Terente's good suggestion can be made in a single file.
2) While you may not expect a response to fail, server slowness or network issues can occur causing a flawed response.
You could use ASIHTTRequest and if you get an time out try to make an new request to the server.