We are now deploying our application to production. But an issue of Rate Controlled show up? How can we solve this one? Any steps might solve this issue.The issue is connecting to *** using a adapter that uses a java.
We are getting the error from ipad device.
<Warning>: DEBUG: Submitting credentials to Worklight
<Warning>: DEBUG: Checking for authRequired attribute in responseJSON
<Warning>: DEBUG: authRequired attribute is present in responseJSON true
<Warning>: DEBUG: authrequired === true? true
<Warning>: DEBUG: authRequired is true, calling onShowLogin
<Warning>: DEBUG: do login [object Object]
<Error>: HID: The 'Rate Controlled' connection 'appme' access to protected services is denied.
<Warning>: void SendDelegateMessage(NSInvocation *): delegate (webView:runJavaScriptAlertPanelWithMessage:initiatedByFrame:) failed to return after waiting 10 seconds. main run loop mode: kCFRunLoopDefaultMode
<Warning>: ERROR: Failed to submit credentials to worklight
We are fetching credentials to ***. The adapter use jars and java classes to access the credentials.
Does not appear to be MobileFirst Platform-related.
Read through these threads, as it looks like you have some native code written by you here that is involved:
https://discussions.apple.com/thread/6074570
http://forums.coronalabs.com/topic/47830-hid-the-passive-connection-appname-access-to-protected-services-is-denied/
From these threads it seems that the real issue not the "HID ... access denied", but something else in your code that affects the network requests.
Note that you are also printing "[object object]"...
If this is working in the development environment but not in your production environment, then indeed you need to verify your network for anything potential who may cause delays or block requests.
Related
I have an ASP.NET Core application using a SignalR hub. When running via a console application (development mode), no keep-alive requests are sent by the server to the client. Consequently, the connection is re-established every 30 seconds or so.
However, when running the same application via Service Fabric, keep-alive requests are sent and everything works as expected.
Here are the server logs when running under the console app:
dbug: Microsoft.AspNetCore.Http.Connections.Internal.HttpConnectionManager[1]
New connection T2NKQg0jyrm7QAPz4p0ZWA created.
dbug: Microsoft.AspNetCore.Http.Connections.Internal.HttpConnectionDispatcher[4]
Establishing new connection.
dbug: Microsoft.AspNetCore.SignalR.HubConnectionHandler[5]
OnConnectedAsync started.
dbug: Microsoft.AspNetCore.Http.Connections.Internal.Transports.WebSocketsTransport[1]
Socket opened using Sub-Protocol: '(null)'.
trce: Microsoft.AspNetCore.Http.Connections.Internal.Transports.WebSocketsTransport[9]
Message received. Type: Text, size: 32, EndOfMessage: True.
dbug: Microsoft.AspNetCore.SignalR.Internal.DefaultHubProtocolResolver[2]
Found protocol implementation for requested protocol: json.
dbug: Microsoft.AspNetCore.SignalR.HubConnectionContext[1]
Completed connection handshake. Using HubProtocol 'json'.
trce: Microsoft.AspNetCore.Http.Connections.Internal.Transports.WebSocketsTransport[11]
Sending payload: 3 bytes.
trce: Microsoft.AspNetCore.Http.Connections.Internal.Transports.WebSocketsTransport[9]
Message received. Type: Text, size: 11, EndOfMessage: True.
trce: Microsoft.AspNetCore.Http.Connections.Internal.Transports.WebSocketsTransport[9]
Message received. Type: Text, size: 11, EndOfMessage: True.
dbug: Microsoft.AspNetCore.Http.Connections.Internal.Transports.WebSocketsTransport[4]
Waiting for the application to finish sending data.
dbug: Microsoft.AspNetCore.Http.Connections.Internal.Transports.WebSocketsTransport[2]
Socket closed.
trce: Microsoft.AspNetCore.Http.Connections.Internal.HttpConnectionContext[1]
Disposing connection T2NKQg0jyrm7QAPz4p0ZWA.
trce: Microsoft.AspNetCore.Http.Connections.Internal.HttpConnectionContext[2]
Waiting for application to complete.
dbug: Microsoft.AspNetCore.SignalR.HubConnectionHandler[6]
OnConnectedAsync ending.
trce: Microsoft.AspNetCore.Http.Connections.Internal.HttpConnectionContext[3]
Application complete.
dbug: Microsoft.AspNetCore.Http.Connections.Internal.HttpConnectionManager[2]
Removing connection T2NKQg0jyrm7QAPz4p0ZWA from the list of connections.
dbug: Microsoft.AspNetCore.Http.Connections.Internal.HttpConnectionManager[1]
New connection JW_1AnoGvhvNJ6MdWGb5RA created.
dbug: Microsoft.AspNetCore.Http.Connections.Internal.HttpConnectionDispatcher[4]
Establishing new connection.
dbug: Microsoft.AspNetCore.SignalR.HubConnectionHandler[5]
OnConnectedAsync started.
dbug: Microsoft.AspNetCore.Http.Connections.Internal.Transports.WebSocketsTransport[1]
Socket opened using Sub-Protocol: '(null)'.
trce: Microsoft.AspNetCore.Http.Connections.Internal.Transports.WebSocketsTransport[9]
Message received. Type: Text, size: 32, EndOfMessage: True.
dbug: Microsoft.AspNetCore.SignalR.Internal.DefaultHubProtocolResolver[2]
Found protocol implementation for requested protocol: json.
dbug: Microsoft.AspNetCore.SignalR.HubConnectionContext[1]
Completed connection handshake. Using HubProtocol 'json'.
trce: Microsoft.AspNetCore.Http.Connections.Internal.Transports.WebSocketsTransport[11]
Sending payload: 3 bytes.
trce: Microsoft.AspNetCore.Http.Connections.Internal.Transports.WebSocketsTransport[9]
Message received. Type: Text, size: 11, EndOfMessage: True.
And the client logs:
Microsoft.AspNetCore.Http.Connections.Client.HttpConnection: Debug: Transport 'WebSockets' started.
Microsoft.AspNetCore.Http.Connections.Client.HttpConnection: Information: HttpConnection Started.
Microsoft.AspNetCore.SignalR.Client.HubConnection: Information: Using HubProtocol 'json v1'.
Microsoft.AspNetCore.SignalR.Client.HubConnection: Debug: Sending Hub Handshake.
Microsoft.AspNetCore.Http.Connections.Client.Internal.WebSocketsTransport: Debug: Received message from application. Payload size: 32.
Microsoft.AspNetCore.Http.Connections.Client.Internal.WebSocketsTransport: Debug: Message received. Type: Text, size: 3, EndOfMessage: True.
Microsoft.AspNetCore.SignalR.Client.HubConnection: Debug: Handshake with server complete.
Microsoft.AspNetCore.SignalR.Client.HubConnection: Debug: Receive loop starting.
Microsoft.AspNetCore.SignalR.Client.HubConnection: Debug: Sending PingMessage message.
Microsoft.AspNetCore.Http.Connections.Client.Internal.WebSocketsTransport: Debug: Received message from application. Payload size: 11.
Microsoft.AspNetCore.SignalR.Client.HubConnection: Debug: Sending PingMessage message completed.
Microsoft.AspNetCore.SignalR.Client.HubConnection: Information: HubConnection started.
Microsoft.AspNetCore.SignalR.Client.HubConnection: Trace: The HubConnection is attempting to transition from the Connecting state to the Connected state.
Microsoft.AspNetCore.SignalR.Client.HubConnection: Trace: Releasing Connection Lock in StartAsyncInner (/_/src/SignalR/clients/csharp/Client.Core/src/HubConnection.cs:280).
The thread 0x8184 has exited with code 0 (0x0).
Microsoft.AspNetCore.SignalR.Client.HubConnection: Trace: Acquired the Connection Lock in order to ping the server.
Microsoft.AspNetCore.SignalR.Client.HubConnection: Debug: Sending PingMessage message.
Microsoft.AspNetCore.SignalR.Client.HubConnection: Debug: Sending PingMessage message completed.
Microsoft.AspNetCore.SignalR.Client.HubConnection: Trace: Releasing Connection Lock in RunTimerActions (/_/src/SignalR/clients/csharp/Client.Core/src/HubConnection.cs:1881).
Microsoft.AspNetCore.Http.Connections.Client.Internal.WebSocketsTransport: Debug: Received message from application. Payload size: 11.
Microsoft.AspNetCore.SignalR.Client.HubConnection: Trace: Waiting on Connection Lock in HandleConnectionClose (/_/src/SignalR/clients/csharp/Client.Core/src/HubConnection.cs:1279).
Microsoft.AspNetCore.Http.Connections.Client.HttpConnection: Debug: Disposing HttpConnection.
Microsoft.AspNetCore.Http.Connections.Client.Internal.WebSocketsTransport: Information: Transport is stopping.
Microsoft.AspNetCore.Http.Connections.Client.Internal.WebSocketsTransport: Debug: Send loop stopped.
Microsoft.AspNetCore.Http.Connections.Client.Internal.WebSocketsTransport: Debug: Transport stopped.
Microsoft.AspNetCore.Http.Connections.Client.HttpConnection: Information: HttpConnection Disposed.
Microsoft.AspNetCore.SignalR.Client.HubConnection: Debug: Canceling all outstanding invocations.
Microsoft.AspNetCore.Http.Connections.Client.Internal.WebSocketsTransport: Debug: Receive loop canceled.
Microsoft.AspNetCore.Http.Connections.Client.Internal.WebSocketsTransport: Debug: Receive loop stopped.
Microsoft.AspNetCore.SignalR.Client.HubConnection: Trace: The HubConnection is attempting to transition from the Connected state to the Reconnecting state.
Microsoft.AspNetCore.SignalR.Client.HubConnection: Error: HubConnection reconnecting due to an error.
I won't include them here, but the logs when running under Service Fabric show that the server is correctly sending keep-alives to the client ("Sent a ping message to the client").
It might seem obvious that there is some difference in configuration between my console and Service Fabric hosts, but I've gone through it carefully and cannot see anything that would explain this. In fact, the SignalR integration differed only in that the development host configured detailed errors to be enabled, but even if I remove that the behavior remains the same.
Short of running my own build of ASP.NET Core (something I'm perhaps lazily attempting to avoid only because it was looking far from trivial to build), is there anything I might be missing that would explain this situation?
I have an Phoenix/Elixir App that works fine with https locally, however when I try to change it to use the production certificates the server does not respond and no error messages are shown.
In my dev.exs this was made with the hostname localhost
In prod.exs here are the keys. These were made with my production URL
I have tried to change the localhost to production url on local by adding host into the https portion in the config
https: [port: 443,
host: "produrl.com"
keyfile: "priv/keys/domain.key",
certfile: "priv/keys/domain.crt"],
This throws an error
sudo MIX_ENV=prod mix phoenix.server
[info] Running LiteChartBe.Endpoint with Cowboy using http://localhost:80
[info] Application lite_chart_be exited: LiteChartBe.start(:normal, []) returned an error: shutdown: failed to start child: LiteChartBe.Endpoint
** (EXIT) shutdown: failed to start child: Phoenix.Endpoint.Server
** (EXIT) shutdown: failed to start child: {:ranch_listener_sup, LiteChartBe.Endpoint.HTTPS}
** (EXIT) shutdown: failed to start child: :ranch_acceptors_sup
** (EXIT) :badarg
{"Kernel pid terminated",application_controller,"{application_start_failure,lite_chart_be,{{shutdown,{failed_to_start_child,'Elixir.LiteChartBe.Endpoint',{shutdown,{failed_to_start_child,'Elixir.Phoenix.Endpoint.Server',{shutdown,{failed_to_start_child,{ranch_listener_sup,'Elixir.LiteChartBe.Endpoint.HTTPS'},{shutdown,{failed_to_start_child,ranch_acceptors_sup,badarg}}}}}}}},{'Elixir.LiteChartBe',start,[normal,[]]}}}"}
Kernel pid terminated (application_controller) ({application_start_failure,lite_chart_be,{{shutdown,{failed_to_start_child,'Elixir.LiteChartBe.Endpoint',{shutdown,{failed_to_start_child,'Elixir.Phoeni
If I simply forward localhost to produrl in my local hosts file, no errors are thrown and nothing connects to the server using https.
The error states that you provided a wrong argument for the configuration of your Endpoint (** (EXIT) :badarg). I suppose that is beacause you are missing a comma behind your host url.
This does probably not solve your problem, but that is supposedly the reason for the error message shown after your change.
I am using poltergeist to execute tests, recently this has stopped working. The first spec that tries using it fails with this error:
phantomjs[37617] <Error>: Set a breakpoint at CGSLogError to catch errors as they are logged.
phantomjs[37617] <Error>: On-demand launch of the Window Server is allowed for root user only.
phantomjs[37617] <Warning>: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver.active" (268435459)
phantomjs[37617] <Error>: On-demand launch of the Window Server is allowed for root user only.
phantomjs[37617] <Warning>: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver.active" (268435459)
phantomjs[37617] <Error>: This user is not allowed access to the window system right now.
phantomjs[37617] <Warning>: CGSConnectionByID: 0 is not a valid connection ID.
phantomjs[37617] <Warning>: Invalid Connection ID 0
phantomjs[37617:3258922] Could not rendezvous with font server (error 268435459)
phantomjs[37617:3258922] XType: unable to make a connection to the font daemon!
phantomjs[37617:3258922] registering /System/Library/Fonts/*, /System/Library/Fonts/Base/*, and /Library/Fonts/* locally
Reinstalling phantomjs, as well as poltergeist had no effect.
Googling this brings me far away from my known rubyverse.
I am guessing this is a permissions issue, but have no clue where to start looking.
I'd greatly appreciate a pointing in the right direction.
I am getting following while connecting to red5 demo apps :
NetConnection.Connect.Closed
[WARN] [ConnectionChecker-1] org.red5.server.net.rtmp.RTMPConnManager - Connection GN0PSGBZE63TF has exceeded the max inactivity threshold of 60000 ms
[INFO] [NioProcessor-5] org.red5.server.net.rtmp.RTMPMinaConnection - Connection is closed:
[WARN] [NioProcessor-5] org.red5.server.net.rtmp.RTMPMinaIoHandler - Connection was not found for GN0PSGBZE63TF
[ERROR] [RTMPConnectionExecutor-3] org.red5.server.service.ServiceInvoker - Method getApplicationList with parameters [] not found in org.red5.server.Context#4989fa8
[WARN] [RTMPConnectionExecutor-3] org.red5.server.service.ServiceInvoker - Service not found: installer
[WARN] [ConnectionChecker-1] org.red5.server.net.rtmp.RTMPConnManager - Connection Q6TFXYIXBD4T4 has exceeded the max inactivity threshold of 60000 ms
[INFO] [NioProcessor-9] org.red5.server.net.rtmp.RTMPMinaConnection - Connection is closed:
[WARN] [NioProcessor-9] org.red5.server.net.rtmp.RTMPMinaIoHandler - Connection was not found for Q6TFXYIXBD4T4
[root#vps red5]# ^C
A few things are happening here:
Your client connection is timing out
The method you attempted to call doesn't exist
The installer service isn't installed or running
Obviously I dont know what happened before the first line "NetConnection.Connect.Closed" so I can't assume much about that missing section. To fix 1-3, you probably just need to add the installer app to your install. Grab all the stuff in this location and put it in your red5/webapps/installer directory: https://github.com/Red5/red5-server/tree/master/src/main/server/webapps/installer
I have build the app in worklight 6.1 version and which we have tested in our local environment with no issue at all. I have wrote the adapter procedure and which is not secure till now having simple procedure method where we won't required any security.
Now after deploying the app on production environment , I am not able to call worklight procedure at all. Some logs are getting displaying on Xcode console given below
2014-01-06 11:23:36.294 PROJECT[340:60b] DeviceAuthManager:getWorklightUniqueDeviceId --> returning UUID from the keychain
2014-01-06 11:23:36.666 PROJECT[340:60b] Adding request to wl_antiXSRFRealm challenge handler's waiting list
2014-01-06 11:23:36.668 PROJECT[340:60b] Adding request to wl_deviceNoProvisioningRealm challenge handler's waiting list
and logs which are getting displaying on server side(IBM http server) given below
/PROJECT/apps/services/api/PROJECT/ipad/0/query HTTP/1.1" 401 165
IPADDRESS - - [05/Jan/2014:23:54:36 -0600] "POST /PROJECT/apps/services/api/PROJECT/ipad/0/query HTTP/1.1" 401 166
IPADDRESS - - [05/Jan/2014:23:54:36 -0600] "POST /PROJECT/apps/services/api/PROJECT/ipad/0/query HTTP/1.1" 401 166
Just let me know what could be the reason for this whether i forgot something when deploying on the production.
And also let me know whether adapter must be secure or we can keep without any security on server side.
After Deploying the adapter on production , am calling the adapter using method given below
function Authentication(user,pass) {
console.log('Hi Authentication');
busyInd.show();
var invocationData = {
adapter : 'CORE_ADAPTER',
procedure : 'Authentication',
parameters : [ user,pass ]
};
WL.Client.invokeProcedure(invocationData,{
onSuccess : AuthSuccess,
onFailure : function AuthFailure(response){ busyInd.hide();console.log("reponse failure "+response);},
});
}
As per the Srik Comment given below At the time of app launch I am getting
2014-01-06 17:24:31.710 PROJECT[53760:c07] DEBUG: addDeviceIDHeader deviceIDSuccessCallback
2014-01-06 17:24:31.711 PROJECT[53760:c07] DEBUG: connectOnStartup finalizeInit
2014-01-06 17:24:31.712 PROJECT[53760:c07] DEBUG: before: app init onSuccess
2014-01-06 17:24:31.712 PROJECT[53760:c07] DEBUG: after: app init onSuccess
2014-01-06 17:24:31.712 PROJECT[53760:c07] DEBUG: added onPause event handler
2014-01-06 17:24:31.712 PROJECT[53760:c07] DEBUG: wlclient init success
and ConnectOnStartup is true in initOption.js file, After successfully init only app is calling adapter.
I have checked this with wireshark worklight is adding one more slash at that time like this
http://localhost:10080/HDFC_SECURITIES_MEAP//apps/services/
This is resolved now after removing slash at the end of url in worlight.plist file. This is the testing with ios5 , ios6, ios7` and all build are working with no issue even not a single time we are getting exception. And .plist is completely editable.