I got the following error message when using HttpClient in DolphinDB:
url must be a string scalar
Does anyone know what to do with this error message? Thanks!
The plugin version needs to match the DolphinDB server version. Right now the plugin version is 130 so you need to get server version 1.30
Related
I have a script created to automate the process of generating Let's Encrypt certificates for my websites.
The Script always worked fine, but starting yesterday I am receiving the issue below when I try to run:
New-ACMERegistration -Contacts mailto:user#email.com -AcceptTos
Error:
System.UriFormatException: Invalid URI: The URI scheme is not valid.
at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
at ACMESharp.AcmeClient.GetDirectory(Boolean saveRelative) in
C:\projects\acmesharp\ACMESharp\ACMESharp\AcmeClient.cs:line 145
at ACMESharp.POSH.NewRegistration.ProcessRecord() in
C:\projects\acmesharp\ACMESharp\ACMESharp.POSH\NewRegistration.cs:line 63
at System.Management.Automation.CommandProcessor.ProcessRecord()
I have the latest version of th PowerShell module installed (https://www.powershellgallery.com/packages/ACMESharp/0.9.1.326).
Has anybody stumbled on a similar issue?
An error is thrown because the BaseUri: https://acme-v01.api.letsencrypt.org/directory returns a JSON Error. ACME Protocol Version 1 has been deprecated. You will need to use a client that uses ACME Protocol Version 2.
Consider replacing ACMESharp with ACME-PS.
From time to time I get the following warning in the logfile of my Wicket application:
04.10.2012 14:52:08,525 WARN [org.apache.wicket.core.request.mapper.AbstractBookmarkableMapper]
Unknown listener interface 'd allow_url_include=On '
What does that mean and how do I fix it? I tried Google, but I could only find results for the PHP configuration allow_url_include.
I'm using Wicket 6.0.0
Most likely an automated tool tries to exploit some PHP application. Wicket can't handle this request and prints the warning. Look in the access log what HTTP requests hit your server at this timestamp to see which request caused this warning.
It's safe to ignore this warning in this case.
My WSO2-ESB throws following error message when I execute WSO2 sample 100 (a WS-Security sample), http://wso2.org/project/esb/java/4.0.3/docs/samples/qos_mediation_samples.html):
ERROR - Axis2Sender Unexpected error during sending message out org.apache.axis2.AxisFault: Error in encryption
At org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:117)
....
org.apache.xml.security.encryption.XMLEncryptionException: Illegal key size or default parameters
And my WSO2-AS throws:
ERROR {org.apache.axis2.engine.AxisEngine} - Missing wsse:Security header in request org.apache.axis2.AxisFault: Missing wsse:Security header in request
What is "Illegal key size or default parameters" means? How to fix this error?
BTW, I am using JDK 1.6 which has included the JCE API and local_policy.jar, US_export_policy.jar, et al. So, I guess it isn't a JCE problem. (http://wso2.org/node/2520/print)
You may have to patch local_policy.jar and US_export_policy.jar which are relevant to your jdk version.
Please refer http://blog.rampartfaq.com/2009/08/faq-001-javasecurityinvalidkeyexception.html
--
Thilini
Type in cmd: java -version, check whether this version is equal to the version displayed at the startup of wso2.
If these versions were not equal, modify your path and put %JAVA_HOME%\bin before %SystemRoot%\system32.
I'm working on an EJB3 MDB that listen to a MQ queue in a distant server.
All is working fine (MDB triggered when a message is put into the listenned queue) except the treatment done by the MDB. For information, i use WMQ resource adapter to map the queue.
Into the method 'onMessage' of the MDB, i try to cast the given message into the class 'com.ibm.jms.JMSBytesMessage', but i get a strange error message.
The code is the following one (simple for the example):
public void onMessage(Message theMessage) {
((JMSBytesMessage) theMessage).readBytes(myBytes);
}
And the exception message:
Exception while reading input request: com.ibm.jms.JMSBytesMessage incompatible with com.ibm.jms.JMSBytesMessage
Ok, the message received should be (and is) type 'com.ibm.jms.JMSBytesMessage', so why the application doesn't work ? Should it be possible that my JBoss server already use another version of the library 'com.ibm.mqjms.jar' (including the JMSBytesMessage class) and cause this kind of error ?
ps: i've deployed the application on a JBoss server version 4.2.3 under linux system.
I've already make the application work on my local machine with same version of JBoss server but under window system (same configuration, same libraries, etc.)
Does someone have an idea about the reason of such error ?
Thanks in advance for any help.
Regards,
EDIT: SOLUTION: cast with javax.jms.BytesMessage instead of com.ibm.jms.JMSBytesMessage
Might as well reproduce my comment as answer:
Don't cast to the MQ-specific com.ibm.jms.JMSBytesMessage, cast to the JMS-standard javax.jms.BytesMessage. Coupling your code to the implementation-specific types is counter to what JMS tries to achieve.
SSL_Connect API is failing with return value 5 errno=2.
can any one help me in how to trace the same? can any one let me know what could cause this issue?
OS: Windows 2003 Std Sp2 32 bit
You can use following APIs to check the error further as it will store the error as a string in buf.
value = ERR_get_error();
ERR_error_string_n(value,buf,sizeof buf);
Furthermore, I also received this error when I added "SET_MODE_AUTO_RETRY" to CTX object and created an SSL object. I removed it and made changes to retry on my own in case of some error after some delay.
Another check you can do is what port value are you using? If it is not 443 then please try with 443; it may help.
I am also new to this so just sharing what I tried in order to resolve these issues.