I tried every possible way to connect WSRR from IBM Message Broker (MB). But I am getting this exception every time.
Code:
<?xml version="1.0" encoding="UTF-8"?><LookupResults><ServiceRegistry>Failure to retrieve Service from WSRR!</ServiceRegistry><Exception><RecoverableException><File>F:\build\S000_P\src\DataFlowEngine\ImbDataFlowNode.cpp</File><Line>1129</Line><Function>ImbDataFlowNode::createExceptionList</Function><Type>SRRetrieveITServiceNode</Type><Name>WSRR_Connectivity#FCMComposite_1_8</Name><Label>WSRR_Connectivity.Endpoint Lookup One</Label><Catalog>BIPmsgs</Catalog><Severity>3</Severity><Number>2230</Number><Text>Node throwing exception</Text><RecoverableException><File>F:\build\S000_P\src\DataFlowEngine\PluginInterface\com_ibm_broker_plugin_CMbService.cpp</File><Line>1860</Line><Function>ImbJavaExceptionUtils::throwableToNativeException</Function><Type></Type><Name></Name><Label></Label><Catalog>BIPmsgs</Catalog><Severity>3</Severity><Number>4367</Number><Text>Unhandled exception in plugin method.</Text><Insert><Type>5</Type><Text>evaluate</Text></Insert><Insert><Type>5</Type><Text>Endpoint Lo[/code]
The Java based SRRetrieveITServiceNode has thrown an exception and this has been wrapped in the parent BIP2230 exception when it was thrown across the JNI boundary between the SRRetrieveITServiceNode and the rest of the flow.
Unfortunately your pasted XML has truncated the rest of the exception stack but I would expect that the innermost exception in the stack will tell you the root cause of the problem.
IBM suggests the following solution:-
Resolving the problem
Ensure the certificate in broker truststore is of X.509 format and that broker is pointing to a .jks truststore
Related
I have a Blazor Server app in which I log requests/other stuff using ILogger (Serilog under the hood).
The problem is that when an unhandled exception occurs, the circuit breaks and that error is logged only to the browser console. I want to be able to log the exception in a global manner so that I can later check the logs (Seq) and address the issue.
I already looked here https://github.com/dotnet/aspnetcore/issues/13452 but cannot wrap my head around a solution.
I don't think the question requires a code example.
I have a Indy Server (TIdHTTPWebBrokerBridge) which serve a WebModule (TWebModule), the WebModule contains these 3 components:
HTTPSoapDispatcher1: THTTPSoapDispatcher;
HTTPSoapPascalInvoker1: THTTPSoapPascalInvoker;
WSDLHTMLPublish1: TWSDLHTMLPublish;
It's really a classical Delphi SOAP Server Application as generated by the template, and I added a generated SOAP Proxy from WSDL, and it works fine.
I like to log the error handled by the web server code. For example if the SOAP message is not correctly formatted. I tried to branch the following Events:
HTTPSoapPascalInvoker1.OnExceptionEvent
TIdHTTPWebBrokerBridge1.OnException
TIdHTTPWebBrokerBridge1.OnCommandError
But I can't get any of them to be triggered, even worst if I put a breakpoint inside them, it shows a cross which mean that this code may never be executed.
So, my question is how can I get a maximum of information about error generated by the webserver outside of my code ?
Thanks in advance,
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 am generating dynamic links from the application using Branch IO. It generates link properly but sometime theres error generating link like
The request timed out.
CFNetwork handshake failed
Is this issue from branch side?
Found error in my network. Due to firewall issue, some of the packets were dropped.
Tried from other network i was able to get rid of the above issue.
I have a web-application deployed in Websphere AS 8.0(Host A) using spring-jms client accessing queues in WMQ 7.0 in remote machine(Host B). I have configured WMQ ConnectionFactory and WMQ Queues in JNDI using JMS Provider under Resources link with WMQ as Messaging Provider as per the instructions in WAS 8 administration guide. I have also tested it using Test Connection button. It works fine. I have configured JNDI template and QueueConnectionFactory and Queue(Destination), DestinationResolver and JMSTemplate as per Spring JMS configuration.
However when I try to run my server and access WMQ through JNDI it throws the following exception:
exception message JMSCC0085: A destination was not specified.; nested exception is **com.ibm.msg.client.jms.DetailedInvalidDestinationException**: JMSCC0085: A destination was not specified. with params [B#775e20e, 1c02f7440b8438e5]
org.springframework.jms.InvalidDestinationException:JMSCC0085:**A destination was not specified**.; nested exception is com.ibm.msg.client.jms.DetailedInvalidDestinationException:**JMSCC0085:A destination was not specified.**
at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:469)
at org.springframework.jms.core.JmsTemplate.send(JmsTemplate.java:534)
at org.springframework.jms.core.JmsTemplate.send(JmsTemplate.java:526)
I tried to print my default destination name and it printed as queue://QM_MGR/Q1, where QM_MGR is name of queue manager and Q1 is name of queue in WMQ.
Please note that I have not configured any JNDI in WMQ, have not configured any InitialContextFactory and Provider URL in JNDI template and resource-ref in web.xml.
I had tried all the above and failed. So I had removed the above mentioned configurations.
Can any one help me by pointing out why I am getting this exception, what I am missing or detail out the steps to avoid this exception?. Thanks in advance.
Although you have defined the connection factory and destinations in your JNDI, you have to define the MQ counterparts. For example an MQ queue manager by name QM_MGR must be created along with a SVRCONN channel and a listener running at a port, say 1414. Also a queue with name Q1 must be created on that queue manager.
Please check if you have done the above.
I have fixed this issue. It was the JNDI namespace that caused the error. Thanks all.