From bashiro at myway.com  Thu Feb  7 15:50:53 2013
From: bashiro at myway.com (Bashiro)
Date: Thu, 07 Feb 2013 18:50:53 -0500
Subject: [jdom-interest] CREATING TREE IN GUI.
Message-ID: <20130207185053.9384@web005.roc2.bluetie.com>


Hello,

I have been working with JDom for a while and  I have the following question:

I use JDom to create and read XML files. I then populate it in jjTree using  jTree and node models.
Is there a way to create a Tree in GUI without first loading the XML files in a tree/node models ?

Bashiro
Drammen-Norway


From mohammed.lethrech at gmail.com  Wed Feb 13 14:17:50 2013
From: mohammed.lethrech at gmail.com (mohammed lethrech)
Date: Wed, 13 Feb 2013 22:17:50 +0000 (UTC)
Subject: [jdom-interest] Connectons-nous sur LinkedIn
Message-ID: <1486474672.10181638.1360793870133.JavaMail.app@ela4-app2311.prod>

LinkedIn
------------



J'aimerais vous inviter ? rejoindre mon r?seau professionnel en ligne, sur le site LinkedIn.

mohammed

mohammed lethrech
ingenieur etudes et developpement chez DGI
Maroc

Veuillez confirmer que vous connaissez mohammed lethrech?:
https://www.linkedin.com/e/ooumsv-hd51ja5j-6q/isd/11062900987/Tmtk5LPF/?hs=false&tok=0MYOXylfFp4lE1

--
Vous recevez des invitations ? vous connecter par e-mail. Cliquez ici si vous ne souhaitez plus recevoir ces e-mails?:
http://www.linkedin.com/e/ooumsv-hd51ja5j-6q/7oDAlhpn_lk3BOJqUdfprhVLquvgbY0_0jL/goo/jdom-interest%40jdom%2Eorg/20061/I3662986257_1/?hs=false&tok=31rBePLZxp4lE1

(c) 2012 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA.


  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.jdom.org/pipermail/jdom-interest/attachments/20130213/5bde2a05/attachment.html>

From kroy9532 at yahoo.com  Mon Feb 25 19:57:21 2013
From: kroy9532 at yahoo.com (Krishnendu Roy Chowdhury)
Date: Mon, 25 Feb 2013 19:57:21 -0800 (PST)
Subject: [jdom-interest] SIGSEGV (segmentation fault) error occurred
	during init a JDOM element
In-Reply-To: <512C0F19.8090300@tuis.net>
Message-ID: <1361851041.73229.YahooMailClassic@web162801.mail.bf1.yahoo.com>

Hi Rolf,

Thank you for your quick update. Initially I also thought that It's related to perm gen space related error. But in the logs I didn't find ?java.lang.OutOfMemoryError: PermGen space? error and Problematic frame was J (Crash in Compiled Code) in the logs.? 

Is the problem is related to JVM or have memory restrictions to reserve more memory to perm gen?

Krish.

--- On Tue, 2/26/13, Rolf Lear <jdom at tuis.net> wrote:

From: Rolf Lear <jdom at tuis.net>
Subject: Re: [jdom-interest] SIGSEGV (segmentation fault) error occurred during init a JDOM element
To: "Krishnendu Roy Chowdhury" <kroy9532 at yahoo.com>
Cc: "JDOM Group" <jdom-interest at jdom.org>
Date: Tuesday, February 26, 2013, 6:55 AM


  

    
  
  
    Hi Krish.

      

      This problem is almost certainly not related directly to JDOM.
      PermGen space is typically very small, and only used for two
      common purposes:

      ?- storing class definitions

      ?- storing String constants

      

      ?For your interest, the most common causes of PermGen Exhaustion
      that I know of are:

      

      - using Tomcat and loading/unloading servlets - each 'classloader'
      has it's own space in PermGen, and since each servlet has it's own
      classloader the PermGen fills up fast because so many classes are
      duplicated in different places in PermGen

      - Using lots of String.intern() calls - String.intern() uses a
      String constant reference from PermGen (or creates one if there
      was not one already). If you have many calls to String.intern() it
      can fill up PermGen very fast. JDOM does not do String.intern()

      

      Rolf

      

      On 25/02/2013 1:30 AM, Krishnendu Roy Chowdhury wrote:

    
    
      
        
          
            
              HI!
                    

                    

                    I have faced a problem related to segmentation fault
                    in Linux box. I got following error -

                    

                  
              <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

                    J org.jdom.Element.<init>(Ljava/lang/String;)V

                    ...

                    siginfo:si_signo=SIGSEGV: si_errno=0, si_code=2
                    (SEGV_ACCERR), si_addr=0x00002aab2ac30000
              ....................................
              error
                    ?occurred during error reporting (printing native
                    stack), id 0xb

                    <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

                    

                    

                    It is also shows in the log that 100% use of PermGen
                    space. Why this segmentation fault occurred? Is it
                    related to JDK or JDOM?

                    

                    In my understanding, problem is related to JDK and
                    occurred due to 100% use of PermGen space. But I am
                    not sure as Problematic frame is J. 

                    

                    Another interesting point is "error occurred during
                    error reporting (printing native stack), id 0xb".

                    

                    I am using JDK6up20 and Linux environment. Please
                    find attached logs for details.
              ?
              Please
                    help me.?
              

                  Regards,

                  Krish
          
        
      
      

      
      

      _______________________________________________
To control your jdom-interest membership:
http://www.jdom.org/mailman/options/jdom-interest/youraddr at yourhost.com
    
    

  

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.jdom.org/pipermail/jdom-interest/attachments/20130225/86cf2f2c/attachment.html>

From jdom at tuis.net  Mon Feb 25 20:07:51 2013
From: jdom at tuis.net (Rolf Lear)
Date: Mon, 25 Feb 2013 23:07:51 -0500
Subject: [jdom-interest] SIGSEGV (segmentation fault) error occurred
 during init a JDOM element
Message-ID: <vs81tr9o49ib5rjb10qi24jb.1361851671381@email.android.com>

Tecnically *all* SIG* issues are jvm related (unless you use jni...). It should not be possible for JDOM to generate a signal issue.

Is it reliably reproducable, or was it a one-off?

Rolf


Krishnendu Roy Chowdhury <kroy9532 at yahoo.com> wrote:

>Hi Rolf,
>
>Thank you for your quick update. Initially I also thought that It's related to perm gen space related error. But in the logs I didn't find ?java.lang.OutOfMemoryError: PermGen space? error and Problematic frame was J (Crash in Compiled Code) in the logs.? 
>
>Is the problem is related to JVM or have memory restrictions to reserve more memory to perm gen?
>
>Krish.
>
>--- On Tue, 2/26/13, Rolf Lear <jdom at tuis.net> wrote:
>
>
>From: Rolf Lear <jdom at tuis.net>
>Subject: Re: [jdom-interest] SIGSEGV (segmentation fault) error occurred during init a JDOM element
>To: "Krishnendu Roy Chowdhury" <kroy9532 at yahoo.com>
>Cc: "JDOM Group" <jdom-interest at jdom.org>
>Date: Tuesday, February 26, 2013, 6:55 AM
>
>Hi Krish.
>
>This problem is almost certainly not related directly to JDOM. PermGen space is typically very small, and only used for two common purposes:
>?- storing class definitions
>?- storing String constants
>
>?For your interest, the most common causes of PermGen Exhaustion that I know of are:
>
>- using Tomcat and loading/unloading servlets - each 'classloader' has it's own space in PermGen, and since each servlet has it's own classloader the PermGen fills up fast because so many classes are duplicated in different places in PermGen
>- Using lots of String.intern() calls - String.intern() uses a String constant reference from PermGen (or creates one if there was not one already). If you have many calls to String.intern() it can fill up PermGen very fast. JDOM does not do String.intern()
>
>Rolf
>
>On 25/02/2013 1:30 AM, Krishnendu Roy Chowdhury wrote:
>
>HI! 
>
>I have faced a problem related to segmentation fault in Linux box. I got following error -
>
><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
>J org.jdom.Element.<init>(Ljava/lang/String;)V
>...
>siginfo:si_signo=SIGSEGV: si_errno=0, si_code=2 (SEGV_ACCERR), si_addr=0x00002aab2ac30000
>
>....................................
>
>error ?occurred during error reporting (printing native stack), id 0xb
><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 
>
>It is also shows in the log that 100% use of PermGen space. Why this segmentation fault occurred? Is it related to JDK or JDOM?
>
>In my understanding, problem is related to JDK and occurred due to 100% use of PermGen space. But I am not sure as Problematic frame is J. 
>
>Another interesting point is "error occurred during error reporting (printing native stack), id 0xb".
>
>I am using JDK6up20 and Linux environment. Please find attached logs for details.
>
>?
>
>Please help me.?
>
>
>Regards,
>Krish 
>
>_______________________________________________ To control your jdom-interest membership: http://www.jdom.org/mailman/options/jdom-interest/youraddr at yourhost.com 
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.jdom.org/pipermail/jdom-interest/attachments/20130225/7f02baa0/attachment.html>