Dragon Joke

Android Usenet Reader version 1.15 is available in market

2010-08-14T08:14:00.000-07:00

Please help to rank STAR and comment this app in market.

Please send me email (kentsang77@gmail.com) or leave message here for any inquiry.

Demo Video:
Part 1: http://www.youtube.com/watch?v=R9Iac_rcjDc
Part 2: http://www.youtube.com/watch?v=Owj2T-BI03o

* Changes Log:

Version 1.15 (2010-08-14)
- Can press Volume Up / Volume Down button for next / prev thread
- Can download the latest n full messages in group
- Revise charset list in 'Server Option View'
- Rewrite nntp client, use mime4j instead of old javamail for better performance
- Remove two permissions: READ_PHONE_STATE and WRITE_EXTERNAL_STORAGE

In next version, I will add more support for REAL offline reading. Let you config your synchronization settings of your subscribed group:

(1) sync new headlines only
(2) sync headlines only
(3) sync new full messages only
(4) sync full messages
(5) sync full messages when wifi

Ken

Android Usenet Reader version 1.14 is available in market

2010-07-27T07:06:00.000-07:00

Please help to rank a STAR and comment this app in market.

Please send me email or leave message here for any inquiry.

Version 1.14 (2010-07-27)
- Fix the problem of invalid charset encoding in footprints posting
- Fix the problem of incorrect subject decoding
- Fix the problem of no response when pressing 'Test' in Add Server View
- Fix the problem of cannot 'Mark Thread as Read' in Headline View
- Fix the problem of incorrect encoding of group name (news.newsfan.net)
- Fix the problem of cannot filter non-ascii newsgroup name in Select Newsgroup View
- Fix the problem of 'select never in delete old articles'
- Fix the problem of missing delete attachment in 'Delete old articles'
- Further fix the problem of incorrect orientation in CameraView with Android 2.2
- Fine tune the performance of 'Mark Thread as Read / UnRead'
- Fine tune the performance of 'Delete old articles'
- Fine tune the performance of 'Delete all articles' / 'Reset group' of group
- Fine tune article load speed
- Change the data type of message date to integer instead of text for performance tuning
- Change the resize scale of image uploaded and picture taken
- Add 'More' menu
- Add progress dialog for 'Reset Newsgroup', 'Delete Newsgroup' and 'Regenerate Index'
- Add 'Delete all articles of all groups'

Android Usenet Reader version 1.13 is available in Market

2010-07-04T01:40:00.000-07:00

Android Usenet Reader version 1.13 is available in Market

Please comment and rank a STAR in market.

Demo:
http://www.youtube.com/watch?v=R9Iac_rcjDc&feature=player_embedded

Version 1.13 (2010-07-04)
- Add support for SSL
- Add server option for setting usenet server port
- Add server option for using SSL connection
- Add About dialog
- Fix the problem of incorrect orientation in CameraView with Android 2.2
- Fix the problem of not listing in market for Tattoo phone
- Fine tune the performance of delete old article

Android Usenet Reader version 1.11 is available on market

2010-06-01T22:57:00.001-07:00

Android Usenet Reader version 1.11 is available on market

* Version 1.11 Fix the problem of incorrect image ordering
* List preference by category (add list separators)
* Add preference for not auto fetching headline when enter group
* Add preference for deleting old articles
* Delete preference for 'HTTP Compression'
* Fix the problem of showing negative number in newsgroup view
* Attach image file when new article
* Load latest headlines first like Outlook express does
* Add a view for showing message index bar of current group
* Bulk fetching headlines of all subscribed groups
* Fix the problem of not listing on market with Android 2.2 phone
*
* Version 1.10 Fix the problem of cannot list headlines if there are over 100 messages are deleted (at server) from the top
* Fix the problem of cannot list headlines if latest number of group is less than Max_Fetch
*
* Version 1.9 Fix the problem of Force Close when changing orientation of phone
*
* Version 1.8 Add a reply_to wrote: at the start of content when reply email
*

Comming funtions and features in next release

* Can upload taken pciture with GRS data when posting article
* Bulk fetching full messages in thread

Android Usenet Reader (AUR) version 1.7 is available in market.

2010-03-24T09:57:00.001-07:00

1. Please kindly help to test it.
2. Please leave comment in market.
3. Please rank a star for this app in market
4. Report bug at http://dragonjoke.blogspot.com/2010/03/android-usenet-reader-v15-is-available.html

Youtube demo:

Part 1:
http://www.youtube.com/watch?v=R9Iac_rcjDc

Part 2:
http://www.youtube.com/watch?v=Owj2T-BI03o

Please report bug here:
http://dragonjoke.blogspot.com/2010/03/android-usenet-reader-v15-is-available.html

Changes log:

Version 1.6 Hot fix for the problem of missing article in thread list
Version 1.7 Try to fix the problem of AUR is not listing in Tattoo
Fix the problem of cannot post article with manual-added server

Android Usenet Reader v1.5 is available in market

2010-03-23T10:18:00.000-07:00

Android Usenet Reader v1.5 is available in market

Version 1.5
- Do not append "Re: " at the start of the reply title if the title already is start with "Re:"
- Fix the problem of incorrect "Prev / Next Thread Index" in Article
- Fix the problem of cannot list headline with group name have Upper Case chars (matrix.person.raycity-DIGITALZONE)
- Add a Max number of headline list in "Setting" for loadling top n headline in list (temporary solution to slow load speed if cached large number of article (say > 30000))
- Change the password edit text as password dot text
- Fix the problem of non-HK country phone cannot list / view message

Android Usenet Reader v1.4

2010-03-19T09:12:00.000-07:00

Usenet Android Reader v1.4 changes log:

1. fine tune database indexing, browsing thread is very slow if total number of messages is greater than 20000. v1.4 improved it a lot.
2. fix the problem of big5-scs problem (Unknow message show in article body) in android 1.6 or below.
3. reset (or delete) server option when delete all messages of a usenet server.
4. add thread browsing in tree-like view. Press 'menu' in article and press 'Thread'. Support jumping to particular message in thread.
5. set the cursor to first position in content text field when replying a message

Android Usenet Reader in android market

2010-03-10T17:03:00.000-08:00

uploaded to market! Please use keyword 'Usenet' to search.

Or use QR code:

Please comment and report bug here.

Android Usenet Reader Server List 最後召集

2010-03-09T17:21:00.001-08:00

以下 Server 會加入 Android Usenet Reader 的預設 Server 清單中.
預設清單裡的 server 可以無限 subscribe newsgroup
非預設清單內的 server 只可以 subscribe 一個 newsgroup
原意是想優惠本地 Server subscriber.

如有其他本地 server 不在此列.
請到這裡留言加入:

news.3home.net
news.checknews.net
news.hkpcug.org
news.hkux.net
news.idsam.com
news.iplus.hk
news.newsgroup.la
my.newsgroup.la
free.newsgroup.la
news.nntp.hk
news.sporthk.net
news.twonil.com.hk
news.usenet.hk
news.xddddd.com
newsgroup.cc
palmfaq.org
wonderfuland.net
wonderspace.net

Android Usenet Reader

2010-03-03T06:37:00.000-08:00

Please leave me message if you have comment of my android apps.

Yes! It's not yet in market. Just a beta test...

http://android.newsgroupstats.hk

Standalone JAX-WS is not ready for production

2008-07-18T12:07:00.000-07:00

Further to the bug 'light weight http server connections leaks when calling invalid wsdl' 6712353, another problem we encountered is that the standalone jax-ws server doesn't work well when serving concurrent web service calls.

I tried to perform a stress test by making concurrent web service calls, the standalone web service server will keep throwing javax.xml.stream.XMLStreamException.

Is it a bug? Not sure. I will post it to java forum.

If it's a bug. I think it may due to Sun's light weight http server.

I did a very simple experiment:

1. Create a simple web method:


// Calculator.java
package simplews;

import javax.jws.WebMethod;
import javax.jws.WebService;
import javax.xml.ws.Endpoint;

@WebService
public class Calculator {

    @WebMethod
    public int add(int a, int b) {
        return a + b;
    }
}

2. Generate web service class by using apt:

D:\>c:\Program Files\java\jdk1.6.0_06\bin"\apt -d . src\simplews\Calculator.java
warning: Annotation types without processors: [javax.xml.bind.annotation.XmlRootElement, javax.xml.bind.annotation.XmlAccessorType, javax.xml.bind.annotation.XmlType, javax.xml.bind.annotation.XmlElement]
1 warning

3. Create my endpoint:


//Main.java
package simplews;

import java.util.concurrent.ArrayBlockingQueue;
import java.util.concurrent.ThreadPoolExecutor;
import java.util.concurrent.TimeUnit;
import javax.xml.ws.Endpoint;

public class Main {
    private static ArrayBlockingQueue m_arrayBlockingQueue = null;
    private static ThreadPoolExecutor m_executor = null;

    public static void main(String[] args) {
        // create and publish an endpoint
        m_arrayBlockingQueue = new ArrayBlockingQueue(10000);
        m_executor = new ThreadPoolExecutor(5, 50, 15L, TimeUnit.SECONDS, m_arrayBlockingQueue);
        Calculator calculator = new Calculator();
        Endpoint endpoint = Endpoint.publish("http://localhost:8080/calculator", calculator);
    }
}

4. Create my web service client:


//Main.java
public class Main {

    private static int totalThread = 20;
    private static int countPerThread = 1000;
    private static long sleeptime = 1L;

    /**
     * @param args the command line arguments
     */
    public static void main(String[] args) {
        // TODO code application logic here
        try {
            totalThread = Integer.parseInt(args[0]);
        } catch (Exception e) {
        }
        try {
            countPerThread = Integer.parseInt(args[1]);
        } catch (Exception e) {
        }
        try {
            sleeptime = Long.parseLong(args[2]);
        } catch (Exception e) {
        }
        for (int i = 0; i < totalThread; i++) {
            Runnable runnable = new Runnable() {
                int count = countPerThread;
                public void run() {
                    while (--count > 0) {
                        try { // Call Web Service Operation
                            simplews.CalculatorService service = new simplews.CalculatorService();
                            simplews.Calculator port = service.getCalculatorPort();
                            // TODO initialize WS operation arguments here
                            int arg0 = 5;
                            int arg1 = 6;
                            // TODO process result here
                            int result = port.add(arg0, arg1);
                            System.out.println(Thread.currentThread().toString() + " | Result = " + result);
                            Thread.sleep(sleeptime);
                        } catch (Exception ex) {
                            // TODO handle custom exceptions here
                            ex.printStackTrace();
                        }
                    }
                }
            };
            Thread thread = new Thread(runnable);
            thread.start();

            try {
                Thread.sleep(sleeptime);
            } catch (Exception e) {
            }
        }
    }
}

What I am doing here is to create certain number of threads and keep calling remote web method.

5. Start server

6. Start clients with 10 threads, 100 web service calls per thread and sleep = 1 millis.

Server side will keep throwing:


com.sun.xml.internal.ws.streaming.XMLStreamReaderException: XML reader error: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,2]
Message: The markup in the document preceding the root element must be well-formed.
        at com.sun.xml.internal.ws.streaming.XMLStreamReaderUtil.wrapException(XMLStreamReaderUtil.java:242)
        at com.sun.xml.internal.ws.streaming.XMLStreamReaderUtil.next(XMLStreamReaderUtil.java:70)
        at com.sun.xml.internal.ws.streaming.XMLStreamReaderUtil.nextContent(XMLStreamReaderUtil.java:85)
        at com.sun.xml.internal.ws.streaming.XMLStreamReaderUtil.nextElementContent(XMLStreamReaderUtil.java:75)
        at com.sun.xml.internal.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:167)
        at com.sun.xml.internal.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:149)
        at com.sun.xml.internal.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:121)
        at com.sun.xml.internal.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:280)
        at com.sun.xml.internal.ws.transport.http.HttpAdapter.decodePacket(HttpAdapter.java:207)
        at com.sun.xml.internal.ws.transport.http.HttpAdapter.access$500(HttpAdapter.java:74)
        at com.sun.xml.internal.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:363)
        at com.sun.xml.internal.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:175)
        at com.sun.xml.internal.ws.transport.http.server.WSHttpHandler.handleExchange(WSHttpHandler.java:100)
        at com.sun.xml.internal.ws.transport.http.server.WSHttpHandler.handle(WSHttpHandler.java:77)
        at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:65)
        at sun.net.httpserver.AuthFilter.doFilter(AuthFilter.java:65)
        at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:68)
        at sun.net.httpserver.ServerImpl$Exchange$LinkHandler.handle(ServerImpl.java:552)
        at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:65)
        at sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:524)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
        at java.lang.Thread.run(Thread.java:619)
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,2]
Message: The markup in the document preceding the root element must be well-formed.
        at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(XMLStreamReaderImpl.java:588)
        at com.sun.xml.internal.ws.util.xml.XMLStreamReaderFilter.next(XMLStreamReaderFilter.java:78)
        at com.sun.xml.internal.ws.streaming.XMLStreamReaderUtil.next(XMLStreamReaderUtil.java:51)
        ... 21 more

At the same time, number of loopback connections (by Selector) at server
side will be increased by one per exception! Those loopback connections cannot be released unless restarting application.

The application will halt when the number of leaked connection rearch
server limit (max filedispatcher).

Bug 6712353 is dispatched and pending for fix, I am not sure when the fix can be released.

So, if you plan to use standalone jax-ws, make sure the bug is fixed otherwise you are in trouble. Currently one of our application in production is suffered and we have to detect number of leaked connections and trigger an auto-restart of the application in order to free those leaked connections.

I attached my test code here (NetBeans Project):

http://kentsang77.googlepages.com/SimpleWS.rar
http://kentsang77.googlepages.com/SimpleWSClient.rar

jdk version:

java version "1.6.0_06"
Java(TM) SE Runtime Environment (build 1.6.0_06-b02)
Java HotSpot(TM) 64-Bit Server VM (build 10.0-b22, mixed mode)

VirtualBox

2008-07-01T12:03:00.000-07:00

Recently, I start to play virtualization with my new toy, Intel Q9450 box. While searching information from the net, I found VirtualBox.

Wow! It really an ultra light-weight virtualization software. I start to install some guest OS. ~~FreeBSD~~, Centos and Ubuntu. Some experience I want to share:

1. It seems that VirtualBox(1.6.2) doesn't support 64bits guest OS. Even my VirtualBox is 64bits.
2. Adding lan bridge to your guest OS require manually group your lan interface to bridge.
3. Cloning guest OS require VirtualBox's cloning command line tool:

VBoxManage clonevdi centos5.2.vdi centos5.2-2.vid

This command is okay if you save your Virtual Disk File in default location (C:\Documents and Settings\yourid\.VirtualBox\VDI).

If you have save your virtual disk file in another place, you have to specify the full path (both input file name and output file name). E.g.

VBoxManage clonevdi d:\vbox\centos5.2.vdi d:\vbox\centos5.2-2.vid

Otherwise you will got an error saying that Could not access hard disk image.

JAX-WS loopback connections leak

2008-06-05T06:13:00.000-07:00

I have a core java application with standalone jax-ws enabled. It's running very well at the beginning until I found there is a big bug in jdk build-in light weight http server.

The server will create several loop back connections when the server startup. Whenever there is an invalid wsdl call, the standalone server will create a couple more of loop back connections.

Please refer to my video illustrating the problem:

flash link: http://dragonken.googlepages.com/nio-loopback2.swf

I have report the issue (with the testing source code attached) to sun and post the problem to jax-ws forum:

http://forums.java.net/jive/thread.jspa?threadID=41517&tstart=0