Re: A method with return type size_t returns negative value

2011-11-15 Thread Jing Lv
; } JNIEXPORT -size_t +SSIZE_T handleWrite(jlong fd, const void *buf, jint len) { BOOL result = 0; DWORD written = 0; HANDLE h = (HANDLE)fd; if (h != INVALID_HANDLE_VALUE) { I will put it on the bug system. On 2011/11/9 16:57, Jing Lv wrote: Hello Alan, (Sorry that haven't

Re: A method with return type size_t returns negative value

2011-11-09 Thread Jing Lv
Hello Alan, (Sorry that haven't check this for months) I check with the bug 7030624 but see no progress now. What's the current status? Shall we go on with a simple patch to fix the problem? On 2011/7/21 21:32, Alan Bateman wrote: Jing LV wrote: Ping, anyone notice this? :) My plan

Re: 7015589: (spec) BufferedWriter.close leaves stream open if close of underlying Writer fails

2011-09-22 Thread Jing Lv
Hi Alan, I see the status of 7015589 has changed to fix delivered, so is this fix in the repository(java8?) already? On 2011/8/9 19:43, Alan Bateman wrote: A few months back there was a bug report [1] pointing out that it's possible to continue writing to a BufferedWriter after

Timer thread termination may not be detected and cause non-clean VM shutdown

2011-09-13 Thread Jing LV
something to terminate the Timer. Any suggestions/comments? Thanks. -- Best Regards, Jimmy, Jing LV

Re: BufferedOutputStream does not throw exception after it's closed

2011-07-25 Thread Jing LV
. 于 2011-4-26 0:48, Mandy Chung 写道: Hi Jing, On 04/25/11 09:12, Jing LV wrote: Hi Alan, I have many trouble to find 7015589 - I thought it was on bugs.sun.com but search never return a correct result. I guess it was the problem of the system. However up to now I can find nothing. I aslo try

Re: A method with return type size_t returns negative value

2011-07-05 Thread Jing LV
some to be discussed)? Thanks! 于 2011-5-5 14:22, Jing LV 写道: 于 2011-4-26 16:43, Alan Bateman 写道: Jing LV wrote: Hello, Thanks for raising the defect. I see there is no patch now, so I create one (as the defect mentioned jint may be good, I use jint here). I have no Sun Online

Re: lang-management modification - it may break customer application?

2011-06-29 Thread Jing LV
the serviceability-dev mailing list as java.lang.management is a serviceability feature. On 6/30/11 12:32 PM, Jing LV wrote: Hello, I see there is some modifiction in the java.lang.management.ManagementFactory, e.g, newPlatformMXBeanProxy. The LogManager.LOGGING_MXBEAN_NAME in Java7 has been

Re: A method with return type size_t returns negative value

2011-05-05 Thread Jing LV
于 2011-4-26 16:43, Alan Bateman 写道: Jing LV wrote: Hello, Thanks for raising the defect. I see there is no patch now, so I create one (as the defect mentioned jint may be good, I use jint here). I have no Sun Online Account Id, would someone take a look? The function prototypes

Re: A method with return type size_t returns negative value

2011-04-26 Thread Jing LV
, JNI_TRUE); } 于 2011-3-24 20:34, Alan Bateman 写道: Jing LV wrote: : Thanks Alan. Would you please tell me the bug number? The bug now tracking this is: 7030624: size_t usages in src/windows/native/java/io/io_util_md.c need to be re-visited -Alan. -- Best Regards, Jimmy, Jing LV

Re: BufferedOutputStream does not throw exception after it's closed

2011-04-25 Thread Jing LV
于 2011-2-17 17:01, Alan Bateman 写道: Jing LV wrote: : Thanks Remi. I've report this issue on the openjdk bugzilla. Any other comments on this? Can someone help to raise this issue on Sun bug system? Thanks in advance. It's 7015589, sorry I should have been clearer in my mail of Jan 28 [1

Re: A method with return type size_t returns negative value

2011-03-24 Thread Jing LV
于 2011-3-23 18:23, Alan Bateman 写道: Jing LV wrote: Hello, I found a problem in windows/native/java/io/io_util_md.c, method handleRead(). The return type of the method is size_t, which is defined as unsigned int. However we see the method would return negative values while it meets some error

A method with return type size_t returns negative value

2011-03-23 Thread Jing LV
developer may have misunderstand it. I suggest modify it to ssize_t (or SSIZE_T as it is on windows). Any comments? -- Best Regards, Jimmy, Jing LV

Support for Turkish locale

2011-03-01 Thread Jing LV
question is, is Turkish Locale officially supported by OpenJDK? And is there some solutions already for such issues? If no, I can provide the fix. -- Best Regards, Jimmy, Jing LV

Crash in ntdll.dll due to JdbcOdbcConnection

2011-03-01 Thread Jing LV
Hello, I've found a bug, and find it already raised as Oracle Bug 7002634: Crash in ntdll.dll RtlEnterCriticalSection due to race condition in JdbcOdbcConnection. However it's been deferred. I believe I can provide a fix for this, would someone help me? Thanks! -- Best Regards, Jimmy, Jing LV

Re: BufferedOutputStream does not throw exception after it's closed

2011-02-17 Thread Jing LV
于 2011-1-25 23:28, Rémi Forax 写道: On 01/25/2011 04:15 PM, Jing LV wrote: Hello, Hi, you should report it as a bug even if I think that too many programs rely on that semantics so the spec should be updated instead of the implementation. Find a similar problem with the one in the last mail

Re: A HashMap bug with a Proxy value?

2011-02-17 Thread Jing LV
Hello, is there any other comments on this issue? Can someone help raise a bug on Sun's bug system? Thanks. ? 2011-1-19 17:06, Jing LV ??: Hi, Thanks for information. I've raised a new bug on openjdk bug system (https://bugs.openjdk.java.net/show_bug.cgi?id=100165) with testcase

Re: BufferedWriter.write does not throw exception if it is already closed.

2011-01-27 Thread Jing LV
于 2011-1-26 0:19, Alan Bateman 写道: Jing LV wrote: Hello, I find a problem in java.io.BufferedWriter. It is stated in the java spec of its close() method: ... Once the stream has been closed, further write() or flush() invocations will cause an IOException to be thrown. However

BufferedWriter.write does not throw exception if it is already closed.

2011-01-25 Thread Jing LV
Hello, I find a problem in java.io.BufferedWriter. It is stated in the java spec of its close() method: ... Once the stream has been closed, further write() or flush() invocations will cause an IOException to be thrown. However if a BufferedWriter is created with a delegated writer, then it seems

BufferedOutputStream does not throw exception after it's closed

2011-01-25 Thread Jing LV
Hello, Find a similar problem with the one in the last mail(BufferedWriter), this time is BufferedOutputStream, and it has a delegated output stream and behave the same with BufferedWriter, I believe the two problems are just the same - it needs to check the open status before store the contents

Re: A HashMap bug with a Proxy value?

2011-01-19 Thread Jing LV
Hi, Thanks for information. I've raised a new bug on openjdk bug system (https://bugs.openjdk.java.net/show_bug.cgi?id=100165) with testcase and patch. ? 2011-1-14 1:46, Jason Mehrens ??: I wonder the design for Proxy and InvocationHandler can be enhanced by creating a default

A HashMap bug with a Proxy value?

2011-01-12 Thread Jing LV
if any comments. Thanks a lot. Best wishes! Jing LV

Re: A HashMap bug with a Proxy value?

2011-01-12 Thread Jing LV
Hi, Chris, David and Alan, thanks for comments. Yes I was talking about the java.lang.reflect.Proxy, and proxy.equals(proxy) will return false if equals() (in InvocationHandler) is not well overriden. There is some solution on this problem (on spec. etc. ). However but for common developers