SetDaemon(true) problem, named pipe communication

Question

hi all!
i have a "strange" problem, when running a thread in a daemon mode.
Thread parsing = new Thread(){
               public void run(){
                    initParser();
                    String[] __log_data;
                    String line;
                    while(true){
                         _action = 0;
                         try{
                              line = _comm_in.receive();
                              __log_data = vpncDataParser(line);
                              if(_action != 0 )
                                   _comm_out.send(createSOAPQuery(__log_data));
                         }catch(ProbeException pe){
                              pe.toString();
                         }catch(NullPointerException npe){
                              npe.toString();
          parsing.setDaemon(false);
          parsing.start();as you see in the code above, i set daemonizing to false...and everything works. but as soon as i set it to true the program exits without exception triggered.
i use a socket to read data ( _comm_in.receive() ), i used a named pipe before that and hadn't had problems with daemonizing. but there was an another problem - the program exited after a couple of lines read.
any ideas will be appreciated.
cheers
dian

Answer 1

I wish I did, unfortunately I'm not much of a named pipe guru. I noticed something though, you're calling initParser() in the parsing Thread. I don't see that method in your anonymous inner class so I assume it's in the enclosing class (rather than omitted here for brievity). Similarly commin and commout appear to be from the enclosing class. Since those are in the enclosing class, a number of parsing threads could be messing with them at the same time.
Is it possible that any of these are getting messed up by another thread while your anonymous inner class is running? For example, if it was doing something like:
Thread parsing = new Thread(){
               public void run(){
          parsing.setDaemon(false);
          parsing.start();
          _comm_in = null;    // This would break itI assume it's not that straight-forward, but a more complicated variation of it perhaps? Is it possible for two parsing threads to be running at once? If so, is the second one calling initParser() messing up the first?
Other than that, if its some weird named-pipe goings on then I'm useless to you :).
- Jemiah