ServiceAdapter:BehaviorOnDisconnect Cancel The title field is required!

1. Roger Blanchard

   

   381 posts
   Registered:
   29 Jun 2018
   08 Apr 2019

   Link to this post

   Can the BehaviorOnDisconnect be changed after we are onnected to the Appserver?
   
   For most of our forms we want to use the RetryQuit for a hew use cases we want to ignore and handle ourselves.
   
   FrameworkSettings:ServiceAdapter:BehaviorOnDisconnect = OptionsOnDisconnectEnum:Ignore.
2. Mike Fechner

   

   319 posts
   Registered:
   14 Sep 2016
   09 Apr 2019 in reply to Roger Blanchard

   Link to this post

   Can the BehaviorOnDisconnect be changed after we are onnected to the Appserver?.

   
   
   From looking at the code, I'd say yes. 
   
   Didn't this work as expected? 
3. Roger Blanchard

   

   381 posts
   Registered:
   29 Jun 2018
   09 Apr 2019 in reply to Mike Fechner

   Link to this post

   It appeared to work just fine on my development PC. I then built the project and loaded on a tablet which is running WebClient. The person doing the QA said the question was still coming up. Before I dug into it I wanted to make sure this would work as I thought it would.
   
    I will dig into it a bit more.
   
   Thanks for the response.
   
4. Roger Blanchard

   

   381 posts
   Registered:
   29 Jun 2018
   12 Apr 2019 in reply to Mike Fechner

   Link to this post

   Hey Mike,
   
   I did look into this and when using the Ignore option it does appear that the Retry/Quit question is not displayed. However, we get the following error over and over. We actually have to kill the app.
   
   
   
   [19/04/12@08:03:57.314-0400] P-005532 T-004448 1 4GL APPL           An Consultingwerk.Framework.Exceptions.AppServerConnectionException has occurred:
   [19/04/12@08:03:57.314-0400] P-005532 T-004448 1 4GL APPL           Unable to connect to the AppServer partition named Default.
   [19/04/12@08:03:57.314-0400] P-005532 T-004448 1 4GL APPL           Connection failure for host OspreyPOS.WebClient.Server port 8940 transport HTTP. (9407)
   [19/04/12@08:03:57.314-0400] P-005532 T-004448 1 4GL APPL           appServerConnect adecomm/as-utils.w at line 388  (adecomm/as-utils.r)
   [19/04/12@08:03:57.314-0400] P-005532 T-004448 1 4GL APPL           ConnectService Consultingwerk.Framework.AppServerServiceManager at line 530  (Consultingwerk/Framework/AppServerServiceManager.r)
   [19/04/12@08:03:57.314-0400] P-005532 T-004448 1 4GL APPL           ConnectService Consultingwerk.OERA.ServiceAdapter at line 681  (Consultingwerk/OERA/ServiceAdapter.r)
   [19/04/12@08:03:57.314-0400] P-005532 T-004448 1 4GL APPL           ConnectService Consultingwerk.OERA.ServiceAdapter at line 631  (Consultingwerk/OERA/ServiceAdapter.r)
   [19/04/12@08:03:57.314-0400] P-005532 T-004448 1 4GL APPL           InvokeTask Consultingwerk.OERA.ServiceAdapter at line 2682  (Consultingwerk/OERA/ServiceAdapter.r)
   [19/04/12@08:03:57.314-0400] P-005532 T-004448 1 4GL APPL           TimerTickHandler Consultingwerk.SmartComponents.Implementation.KeepAliveService at line 694  (Consultingwerk/SmartComponents/Implementation/KeepAliveService.r)
   [19/04/12@08:03:57.314-0400] P-005532 T-004448 1 4GL APPL           ospreymobile.p at line 360  (ospreymobile.r)
   [19/04/12@08:03:57.314-0400] P-005532 T-004448 1 4GL APPL          
   [19/04/12@08:03:57.314-0400] P-005532 T-004448 1 4GL APPL             appServerConnect adecomm/as-utils.w at line 388  (adecomm/as-utils.r)
   [19/04/12@08:03:57.314-0400] P-005532 T-004448 1 4GL APPL             ConnectService Consultingwerk.Framework.AppServerServiceManager at line 530  (Consultingwerk/Framework/AppServerServiceManager.r)
   [19/04/12@08:03:57.314-0400] P-005532 T-004448 1 4GL APPL             ConnectService Consultingwerk.OERA.ServiceAdapter at line 681  (Consultingwerk/OERA/ServiceAdapter.r)
   [19/04/12@08:03:57.314-0400] P-005532 T-004448 1 4GL APPL             ConnectService Consultingwerk.OERA.ServiceAdapter at line 631  (Consultingwerk/OERA/ServiceAdapter.r)
   [19/04/12@08:03:57.314-0400] P-005532 T-004448 1 4GL APPL             InvokeTask Consultingwerk.OERA.ServiceAdapter at line 2682  (Consultingwerk/OERA/ServiceAdapter.r)
   [19/04/12@08:03:57.314-0400] P-005532 T-004448 1 4GL APPL             TimerTickHandler Consultingwerk.SmartComponents.Implementation.KeepAliveService at line 694  (Consultingwerk/SmartComponents/Implementation/KeepAliveService.r)
   [19/04/12@08:03:57.314-0400] P-005532 T-004448 1 4GL APPL             ospreymobile.p at line 360  (ospreymobile.r)
5. Roger Blanchard

   

   381 posts
   Registered:
   29 Jun 2018
   12 Apr 2019 in reply to Mike Fechner

   Link to this post

   Should the KeepAlive service follow the Ignore option as well? That appears to be where these errors are coming from.
   
   I am going to remove this service as I am not sure this would be too useful in our POS module where we want to run disconnected if the server is not available.
6. Mike Fechner

   

   319 posts
   Registered:
   14 Sep 2016
   12 Apr 2019 in reply to Roger Blanchard

   Link to this post

   Are you sure, that you're using "our" version of the adecomm/as-utils.w?
7. Roger Blanchard

   

   381 posts
   Registered:
   29 Jun 2018
   12 Apr 2019 in reply to Mike Fechner

   Link to this post

   Yep, I thought of that first. I popped up a message in your flavor to make sure that was being found before the PSC flavor. Right now I have the KeepAlive service removed and I do not have the issue. 
   
   I have a bigger issue with PSC that I opened a call for. If you try and connect to PASOE and cant it throws an error within 4 seconds. If you are on a wireless network that 4 seconds turns into 86 seconds!!