I am facing issue while creating a HIVE based datasource in Cognos Analytics 11.2.1.
I have followed the below steps while creating the HIVE Datasource:
1.Selected "JDBC" as connection type.
2.Selected "HIVE" as "TYPE" in connection string.
Provided "jdbc:hive2://ipaddress:10000/default" as "JDBC URL".
Kept default driver class name(i.e."org.apache.hive.jdbc.HiveDriver")
However on testing the datasource, I am getting the below error:
XQE-GEN-0002 An unexpected exception occurred: org.apache.curator.RetryPolicy
Can you please help me in resolving the issue.
Thanks,
Tushar
Related
I updated our signalr packages from 2.4.0 and added RunAzureSignalR instead of RunSignalR. Added this code in de Startup.cs
app.Map("/signalr", map =>
{
var hubConfiguration = new HubConfiguration
{
EnableDetailedErrors = true
};
map.RunAzureSignalR(typeof(Startup).FullName, hubConfiguration, options =>
{
options.ConnectionString = AppApiSettings.SignalRServiceConnectionString;
});
});
But when I try to send a message to the hub I get an exception The connection is not active, data cannot be sent to the service.. Can't find any reason this would happen or why the service would not run.
When I use RunSignalR (self hosted) everything runs great.
Any help would be greatly appreciated.
It turns out Azure Service only support TLS1.2 for security concerns.
Please add following code to your Startup:
ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;
The hint for this solution was found on a github ticket: https://github.com/Azure/azure-signalr/issues/279
"No server available" indicates that your app server has trouble connecting to Azure service. You can enable tracing from the app server side with the following to see if any error throws.
GlobalHost.TraceManager.Switch.Level = SourceLevels.Information;
A sample here: https://github.com/Azure/azure-signalr/blob/dev/samples/AspNet.ChatSample/AspNet.ChatSample.SelfHostServer/Startup.cs#L19
If you are local debugging the server side, you can also uncheck "Just My Code" and break when any CLR exception throws:
System.Security.Authentication.AuthenticationException: "A call to SSPI failed, see inner exception."
- (inner) "The function requested is not supported"
System.ObjectDisposedException: 'Safe handle has been closed'
System.Net.WebException: 'The request was aborted: Could not create SSL/TLS secure channel.'
System.Net.WebSockets.WebSocketException: 'Unable to connect to the remote server'
- (inner) WebException: The request was aborted: Could not create SSL/TLS secure channel.
I recently had the same issue and again the accepted answer didn't help me. My project was a .NET 4.8 MVC application (so TLS version shouldn't be an issue) and following an update of the projects Nuget packages the issue arose.
I knew it was the Nuget updates that had broken my application but I didn't want to go through each one to figure out where the issue was.
Thanks to #cognophile for pointing me in the right direction. For me though I only needed to downgrade the following three Nuget packages to version 5.0.17 to fix the issue. Anything 6.x with these packages caused the issue again.
Microsoft.AspNetCore.Connections.Abstractions
Microsoft.AspNetCore.Http.Connections.Client
Microsoft.AspNetCore.Http.Connections.Common
I've recently had the same issue whereby the negotiation worked with map.RunSignalR(...) but not map.RunAzureSignalR(...) and tried the accepted answer here without resolution. For anyone still experiencing this issue having tried the accepted answer like myself, I found the below to work for a .NET Framework 4.6.1 project.
Navigating to the negotiation link (e.g. .../signalr/negotiate?clientProtocol=2.1&connectionData=...&callback=jQuery...&_=...) in the browser would give a
HTTP 500: Azure SignalR Service is not connected yet, please try again later
Having enabled the exception debugging suggestions from #Youp Hulsebos and the SignalR GitHub (source), I was able to find the following exceptions being thrown from the SignalR registration call in Startup.Configure(...):
Microsoft.Azure.SignalR.Common.ServiceConnectionNotActiveException: 'The connection is not active, data cannot be sent to the service.'
LoaderException - Method 'get_Features' in type 'Microsoft.AspNetCore.Http.Connections.Client.HttpConnection' from assembly 'Microsoft.AspNetCore.Http.Connections.Client, Version=1.0.0.0, Culture=neutral' does not have an implementation.":"Microsoft.AspNetCore.Http.Connections.Client.HttpConnection"
Having found the second of these exceptions and applying some Google-fu, I found this GitHub issue discussing the LoaderException from Microsoft.Azure.SignalR.WebSocketConnectionContext discussing this as the result of upgrading Microsoft.AspNetCore.Http.Connections.Client from 5.0.12.0 to 6.0.0.0.
Having tried downgrading the package to 5.0.12.0, I still encountered the same issue. Having checked the linked issue ([dotnet/aspnetcore#38699]), I downgraded the following packages to 5.0.11.0 and this resolved the issue:
Microsoft.AspNetCore.Connections.Abstractions
Microsoft.AspNetCore.Http.Connections.Client
Microsoft.AspNetCore.Http.Connections.Common
Microsoft.AspNetCore.Http.Features
I try to write my own neo4j-guide as described at neo4j.
Neither my own example nor the included restaurant_recommendation.html seems to work. If I call in chrome http://localhost:8080/play/html/restaurant_recommendation.html I get a clean page.
If I call :play http://localhost:8080/play/html/restaurant_recommendation.html I get
Remote guide error
TypeError: Failed to fetch
Any suggestion what's wrong or how to analyze it?
The problem was the cors. So I installed a chrome-plugin CORS_TOGGLE which solves the problem for me.
I have a problem with transferring a response from Neo4j to Golang using neoism.
The Neo4j response has nested structure and is assembled with Neo4j plugin in the following way.
I can see that the response is correct in the Neo4j panel. The problem appears when I'm trying to get the response with Golang.
The following error is received: "Unsupported property type: class pkgName.Dev$NestedReport"
The problem isn't reproduced in case if only one top-level element is present in the results.
What is the best way to resolve the issue?
The problem was related to the wrong testing.
We're running with Grails 2.5.3 against a MySQL DB and recently introduced a second datasource definition. We're getting the following exceptions in a non-transactional service which is calling into multiple transactional services. The exception occurs when it tries to start the second transaction:
» 3 Aug 2016 16:49:44.119 PooledConnection has already been closed.. Stacktrace follows:
» 3 Aug 2016 16:49:44.119 java.sql.SQLException: PooledConnection has already been closed.
It seems like Grails is closing the connection to the second datasource after the first transaction ends and is trying to reuse that connection. I'm wondering if anyone has seen this and/or worked around it.
We had faced the same issue but not for two different datasources. Our application was using Hibernate and iBatis and while the hibernate part was integrated within grails and worked fine, the iBatis code gave the mentioned issue when a second continuous transaction was called.
To solve this we created another datasource in resources.groovy and using the iBatis code with this new datasource. you can refer to Grails Pooled Connection Exception for the configuration details of our solution.
I am trying to use 2.0.0-M1 version of grails plugin for neo4j but when i try to save any entity,it is giving me error :
The instance was updated by another user while you were editing. Stacktrace follows: org.grails.datastore.mapping.core.OptimisticLockingException: The instance was updated by another user while you were editing at org.grails.datastore.gorm.neo4j.NodePendingUpdate.run(NodePendingUpdate.java:83)
and if i try to use 2.0.0-M2 version,i got error :
groovy.lang.MissingMethodException: No signature of method: groovy.util.ConfigObject.startsWith() is applicable for argument types: (java.lang.String) values: [jdbc:neo4j:instance:]
Also tell me if 2.0.0-M2 is supporting rest or not.
Please reply fast.
Configuration has changed significantly from M1 to M2. Internally the plugin now uses the Neo4j JDBC driver. I didn't yet found enough time to update the docs, in the meantime refer to https://github.com/sarmbruster/neo4jsample/blob/neo4j_2.0/grails-app/conf/DataSource.groovy for a valid sample config.
The error you're mentioning seems to be caused by a incorrect configuration.
M2 is capable of working with remote database, just set datasource.url="jdbc:neo4j://localhost:7474/", see https://github.com/sarmbruster/neo4jsample/blob/neo4j_2.0/grails-app/conf/DataSource.groovy#L13