Displaying keyword search results 11 - 20
Created by voodoo on March 23, 2011 15:32:55 Last update: March 23, 2011 15:36:00
I got "Unknown SSL protocol error" when using curl to get the default page from iis 7 (of course, IE simply displayed "Internet Explorer cannot display the webpage"). The problem was that I used the default iis 7 certificate, which didn't have a name - and that caused SSL to fail. I created a new certificate with a name and that fixed the problem.
# curl -v -k --dump-header - https://192.168.80.15...Other possible reasons: 3 Common Causes of Unknown SSL Protocol Errors with cURL
Created by Dr. Xi on March 02, 2011 11:39:18 Last update: March 09, 2011 12:19:30
Some peculiarities about Java PrintWriter: PrintWriter never throws any exceptions. From JavaDoc : Methods in this class never throw I/O exceptions, although some of its constructors may. The client may inquire as to whether any errors have occurred by invoking checkError(). When error occurs, you'll never know anything more than that it occured, because checkError returns boolean. When a character is out of the range of the character encoding of the PrintWriter, it prints a question mark (?). But this is not an error. Test code:
import java.io.*; public class TestPrintWri...Latin1 test result:
java TestPrintWriter iso-8859-1 | od -bc 000000...UTF-8 test result:
java TestPrintWriter utf-8 | od -bc 0000000 141...Also, the constructor throws a FileNotFoundException when you try to write to a...
Created by voodoo on February 25, 2011 14:00:41 Last update: February 25, 2011 14:03:46
Suddenly my Windows XP failed to boot with this error message on a blank screen:
missing or corrupt <windows root>\system32\hal.dllI took out the hard drive, put it in a USB enclosure and attached it to another PC. Then I ran CHKDSK and it fixed some file system errors. But I did find that hal.dll was intact, so hal.dll was not missing or corrupt . It turned out that the file that was really missing was C:\boot.ini . It is a hidden file, so you have to use attrib boot.ini to see it. The file is missing if attrib boot.ini returns nothing (run in the root folder C:\). In my case I reconstructed the boot.ini file:
[boot loader] timeout=30 default=multi(0)dis...and changed the attributes back...
Created by antoniosanct on January 19, 2011 10:48:09 Last update: January 19, 2011 10:48:09
Same problem using Eclipse 3.6 (WTP 3.2.1) & Windows XP SP3, launching the default server. This fix solves the problem. Thanks a lot!
Created by Dr. Xi on September 17, 2010 21:29:47 Last update: September 17, 2010 21:31:43
With JBoss (Tomcat?), the servlet container always appends the default charset ISO-8859-1 to the Content-Type header of a JSP response. For example, if you are using JSP to render PDF and put the following declaration at the top of the JSP:
<%@ page contentType="application/pdf"%>These would be the headers in the HTTP response (notice that charset=ISO-8859-1 was appended to Content-Type ):
HTTP/1.1 200 OK Server: Apache-Coyote/1.1 X-...And the output would be truncated a few bytes before non-ASCII characters were encountered, without any error messages ! Maybe you don't intend to output binary files with JSP, but still your response would be truncated without warning if the page happens to contain any non-ASCII characters (when the charset is the default charset=ISO-8859-1 ). However, if you...
Created by Fang on September 08, 2010 20:47:40 Last update: September 08, 2010 20:47:40
For JSP pages in standard syntax, the page encoding is determined from the following sources: The page encoding value of a JSP property group whose URL pattern matches the page. The pageEncoding attribute of the page directive of the page. It is a translation-time error to name different encodings in the pageEncoding attribute of the page directive of a JSP page and in a JSP property group. The CHARSET value of the contentType attribute of the page directive, i.e. , CHARSET does not specify a character set , but a character encoding (such as UTF-8). If none of these is provided, ISO-8859-1 is used as the default page encoding.
Created by magnum on August 19, 2010 22:42:26 Last update: August 19, 2010 22:43:59
Lyx wasn't able to open DVI files with the error message MIME type application/x-dvi not supported. I looked at Lyx preferences and it's using xdg-open to open the file. The following query shows that the default application for the DVI mime type is Evince. So I updated that to xdvi , which I do have.
$ xdg-mime query default application/x-dvi ...But it didn't work! I checked that the file ~/.local/share/applications/defaults.list did get updated. I even logged out and logged back in! I had to update the system wide configuration file /usr/share/applications/defaults.list to make it work:
Created by nogeek on July 30, 2010 23:00:06 Last update: July 30, 2010 23:01:24
It happened on Windows XP with JBoss 5.1.0.GA. This is the stack trace:
2010-07-30 16:39:52,177 ERROR [org.jboss.kernel.pl...According to " (SOLVED) JBAS-7674 solution for JBoss 5.1?? (Windows lock on jnp-service.url) ", the problem seemed to be solved for JBoss 6. In the meanwhile for JBoss 5, disabling Windows Indexing Service seemed to solve the problem. Quote from aforementioned link: It seemed that a file was being locked for some reason, and that file was obviously necessary for JBoss to start. Some further investigation (ok, I admit, I just tried to delete all of JBoss with the faith that it would fail on the locked file), it turns out that file was some file called jnp-service.url in the data directory of the default server. After downloading...
Created by Fang on July 17, 2010 03:16:53 Last update: July 17, 2010 03:18:25
This error happens when the ordering of elements in web.xml is not correct. For example, in a <servlet> declaration, <servlet-name> should come before <servlet-class> . If you switch the order of <servlet-name> and <servlet-class> , you'll get this error. This was my stack trace in JBoss when I declared <load-on-startup> before <init-param> for a servlet:
DEPLOYMENTS IN ERROR: Deployment "vfszip:/C:/...
Created by Dr. Xi on February 13, 2010 22:52:18 Last update: February 13, 2010 22:52:18
This runtime error happens when the Sun EL implementation is not available. Look for the class com.sun.el.ExpressionFactoryImpl in your deployment package, you probably won't find it, or you'll find a version that can't be loaded in your deployment environment. If you are using Maven to build, you can add the following repository and dependency in pom.xml :
<!-- Project dependencies --> <dependencies...