This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1] 2
1
The Rest - Ask For Help / Re: NetOptions / NET:GETSTATS - information on queued incoming data
« on: March 23, 2020, 12:14:25 AM »
Thank you Bruce.
2
The Rest - Ask For Help / NetOptions / NET:GETSTATS - information on queued incoming data
« on: February 11, 2020, 09:15:06 AM »
Hi Bruce,
Apologies if it's documented somewhere but could you shed some light on two numbers in the typed NET:GETSTATS group :-
qSimpleInData_Bytes and qSimpleInData_Size
Our situation being that we have small packets (maybe 500 bytes at most) streaming in and occasionally a backlog develops then clears. We'd picked on qSimpleInData_Bytes to monitor for more serious problems. It seems to work in 16684 increments (16k + some control information?). Would 10 of these small packets result in 166840, 100 result in 1668400 etc - or is it more complex? I'm trying to get a handle on "how much data is actually queued-up" - these are apps dealing with FX market rates and of course the customer needs everything to be "instantaneous"!
Hope this makes some sense.
Thanks, Simon
Apologies if it's documented somewhere but could you shed some light on two numbers in the typed NET:GETSTATS group :-
qSimpleInData_Bytes and qSimpleInData_Size
Our situation being that we have small packets (maybe 500 bytes at most) streaming in and occasionally a backlog develops then clears. We'd picked on qSimpleInData_Bytes to monitor for more serious problems. It seems to work in 16684 increments (16k + some control information?). Would 10 of these small packets result in 166840, 100 result in 1668400 etc - or is it more complex? I'm trying to get a handle on "how much data is actually queued-up" - these are apps dealing with FX market rates and of course the customer needs everything to be "instantaneous"!
Hope this makes some sense.
Thanks, Simon
3
E-Mail - Ask For Help / Re: Office 365 are retiring 3DES
« on: February 04, 2019, 11:17:16 PM »
Thanks Bruce.
4
E-Mail - Ask For Help / Office 365 are retiring 3DES
« on: February 03, 2019, 04:04:40 AM »
Hi all,
"Office 365 will retire 3DES starting February 28, 2019."
I know nothing about ciphers! Sounds frightening - will this effect us sending emails using TLS 1.2? NetTalk 9.18
Thanks,
Simon
"Office 365 will retire 3DES starting February 28, 2019."
I know nothing about ciphers! Sounds frightening - will this effect us sending emails using TLS 1.2? NetTalk 9.18
Thanks,
Simon
5
The Rest - Ask For Help / Re: Incoming data backing-up in NetTalk
« on: October 26, 2017, 10:56:58 AM »
Thanks Bruce,
That's making sense. Think I can definitely rule out your prize1 (another window on top) here. Need to explore your prize2 (inject NotifyEvents) but not sure that will help - almost convinced the problem is of my own making - I was pushed to "ask CapeSoft" and do appreciate your prompt response.
Simon
That's making sense. Think I can definitely rule out your prize1 (another window on top) here. Need to explore your prize2 (inject NotifyEvents) but not sure that will help - almost convinced the problem is of my own making - I was pushed to "ask CapeSoft" and do appreciate your prompt response.
Simon
6
The Rest - Ask For Help / Incoming data backing-up in NetTalk
« on: October 26, 2017, 01:14:10 AM »
Hi,
Using NetSimple client to receive a stream of FIX (Financial Information Exchange) messages. Traffic can be high but the application has always worked well.
We are now seeing regular incidents where traffic is backing-up (presumably inside clanet.dll). Memory usage climbs along with NetTalk's "qSimpleInData_Bytes" statistic.
My understanding is this should mean "my" thread isn't taking packets from NetTalk, yet "old" data continues to trickle through - it's not like I'm taking nothing.
Right now, it's not making sense. I'm assuming the fault lies with me - any bright ideas on what I should be looking for or ways to diagnose this? Of course I'm unable to replicate it and it's happening on critical production machines - the usual story!
Thanks,
Simon
Using NetSimple client to receive a stream of FIX (Financial Information Exchange) messages. Traffic can be high but the application has always worked well.
We are now seeing regular incidents where traffic is backing-up (presumably inside clanet.dll). Memory usage climbs along with NetTalk's "qSimpleInData_Bytes" statistic.
My understanding is this should mean "my" thread isn't taking packets from NetTalk, yet "old" data continues to trickle through - it's not like I'm taking nothing.
Right now, it's not making sense. I'm assuming the fault lies with me - any bright ideas on what I should be looking for or ways to diagnose this? Of course I'm unable to replicate it and it's happening on critical production machines - the usual story!
Thanks,
Simon
7
Web Server - Ask For Help / Re: WebService json error response looks wrong
« on: December 12, 2016, 02:30:50 AM »
Thank you sir.
8
Web Server - Ask For Help / Re: WebService json error response looks wrong
« on: December 09, 2016, 05:28:00 AM »
I think the main problem is this generated code:-
BuildResultFields Routine
! Start of "Start of BuildResultFields Routine"
! [Priority 5000]
! End of "Start of BuildResultFields Routine"
if p_web.RequestJSON
If Records(p_web.ServiceErrorQueue)
jsonResults.append(p_web.ServiceErrorQueue)
That last line should probably be :-
jsonResults.append(p_web.ServiceErrorQueue, 'ServiceErrors')
And if I put this in the available embed :-
json.SetTagCase(jf:CaseAsIs)
Things look better to me :-
{
"GetSubscriberDetails_response" : {
"queue" : [
{
"ErrorNumber" : 9005,
"ErrorPosition" : "GetSubscriberDetails",
"ErrorRecordId" : "Password",
"ErrorDescription" : "Authentication Failed",
"ErrorRecommendation" : ""
}
]
}
}
BuildResultFields Routine
! Start of "Start of BuildResultFields Routine"
! [Priority 5000]
! End of "Start of BuildResultFields Routine"
if p_web.RequestJSON
If Records(p_web.ServiceErrorQueue)
jsonResults.append(p_web.ServiceErrorQueue)
That last line should probably be :-
jsonResults.append(p_web.ServiceErrorQueue, 'ServiceErrors')
And if I put this in the available embed :-
json.SetTagCase(jf:CaseAsIs)
Things look better to me :-
{
"GetSubscriberDetails_response" : {
"queue" : [
{
"ErrorNumber" : 9005,
"ErrorPosition" : "GetSubscriberDetails",
"ErrorRecordId" : "Password",
"ErrorDescription" : "Authentication Failed",
"ErrorRecommendation" : ""
}
]
}
}
9
Web Server - Ask For Help / Re: WebService json error response looks wrong
« on: December 08, 2016, 07:30:30 AM »
Hi,
I'm not really sure what you're asking, sorry!
I was driving at that "queue" when I expected "ServiceErrors", and "ERRORNUMBER" where I expected "ErrorNumber" ...
Thanks
I'm not really sure what you're asking, sorry!
I was driving at that "queue" when I expected "ServiceErrors", and "ERRORNUMBER" where I expected "ErrorNumber" ...
Thanks
10
Web Server - Ask For Help / WebService json error response looks wrong
« on: December 08, 2016, 06:37:20 AM »
Hi,
I'm on 9.13 and working on a webservice. xml error response looks like this:-
<?xml version="1.0" encoding="utf-8"?>
<GetSubscriberDetails_response xmlns="Subscriptions">
<ServiceErrors>
<Error>
<ErrorNumber>9005</ErrorNumber>
<ErrorPosition>GetSubscriberDetails</ErrorPosition>
<ErrorRecordId>Password</ErrorRecordId>
<ErrorDescription>Authentication Failed</ErrorDescription>
<ErrorRecommendation/>
</Error>
</ServiceErrors>
</GetSubscriberDetails_response>
json like this :-
{
"GetSubscriberDetails_response" : {
"queue" : [
{
"ERRORNUMBER" : 9005,
"ERRORPOSITION" : "GetSubscriberDetails",
"ERRORRECORDID" : "Password",
"ERRORDESCRIPTION" : "Authentication Failed",
"ERRORRECOMMENDATION" : ""
}
]
}
}
What have I got wrong!?
Thanks.
I'm on 9.13 and working on a webservice. xml error response looks like this:-
<?xml version="1.0" encoding="utf-8"?>
<GetSubscriberDetails_response xmlns="Subscriptions">
<ServiceErrors>
<Error>
<ErrorNumber>9005</ErrorNumber>
<ErrorPosition>GetSubscriberDetails</ErrorPosition>
<ErrorRecordId>Password</ErrorRecordId>
<ErrorDescription>Authentication Failed</ErrorDescription>
<ErrorRecommendation/>
</Error>
</ServiceErrors>
</GetSubscriberDetails_response>
json like this :-
{
"GetSubscriberDetails_response" : {
"queue" : [
{
"ERRORNUMBER" : 9005,
"ERRORPOSITION" : "GetSubscriberDetails",
"ERRORRECORDID" : "Password",
"ERRORDESCRIPTION" : "Authentication Failed",
"ERRORRECOMMENDATION" : ""
}
]
}
}
What have I got wrong!?
Thanks.
11
Web Server - Ask For Help / Re: Can't get the HTML editor to show
« on: September 26, 2016, 12:30:53 AM »
editted clarion10\accessory\libsrc\win\NetWeb\web\scripts\netweb,js :-
;var NetTalkVersion=9.14
to :-
;var NetTalkVersion=9.13
Seems happy now...
;var NetTalkVersion=9.14
to :-
;var NetTalkVersion=9.13
Seems happy now...
12
Web Server - Ask For Help / Re: Can't get the HTML editor to show
« on: September 25, 2016, 11:47:20 PM »
Thanks, 9.13 seems to have done the trick. I'm seeing no errors or warnings in firebug.
BUT now I have the attached error on all pages
BUT now I have the attached error on all pages
13
Web Server - Ask For Help / Re: Can't get the HTML editor to show
« on: September 25, 2016, 02:38:15 AM »
NetTalk 9.11
14
Web Server - Ask For Help / Can't get the HTML editor to show
« on: September 25, 2016, 02:34:35 AM »
Hi,
Trying to use HTML editor - by checking "Allow xHTML" for a Text field on a popup memory form but it refuses to show. I've looked at the web36 example (which works) and can't see what's different. Both editors are included in the WebServer Scripts settings, Redactor is set as default.
Perhaps there's a clue in what happens when "Allow xHTML" is checked - the Tab on the form kind-of breaks. Attached images show the effect.
Any help much appreciated!
Simon
Trying to use HTML editor - by checking "Allow xHTML" for a Text field on a popup memory form but it refuses to show. I've looked at the web36 example (which works) and can't see what's different. Both editors are included in the WebServer Scripts settings, Redactor is set as default.
Perhaps there's a clue in what happens when "Allow xHTML" is checked - the Tab on the form kind-of breaks. Attached images show the effect.
Any help much appreciated!
Simon
15
The Rest - Ask For Help / Re: To Bruce. timestamps in incoming NetSimple packets?
« on: April 05, 2015, 02:17:49 AM »
Thanks Bruce,
That all makes sense.
> Presumably, since this is NetSimple you are managing the case where the incoming message is split across 2 incoming packets?
Yes, that wasn't the problem. Turned out to be some errant code crippling the thread and stalling the receipt of packets from NetTalk.
Simon
That all makes sense.
> Presumably, since this is NetSimple you are managing the case where the incoming message is split across 2 incoming packets?
Yes, that wasn't the problem. Turned out to be some errant code crippling the thread and stalling the receipt of packets from NetTalk.
Simon
Pages: [1] 2