Databases
StackOverflow2013
Postsdbo
POGlassfish 3.1.1 start-local-instance fails with JAXBException
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POGlassfish 3.1.1 start-local-instance fails with JAXBException
    primarykey
    data
    text
    <p>I am setting up a GlassFish cluster following the guide at <a href="http://javadude.wordpress.com/2011/04/25/glassfish-3-1-clustering-tutorial/" rel="nofollow">http://javadude.wordpress.com/2011/04/25/glassfish-3-1-clustering-tutorial/</a>. I started from fresh installs of GlassFish 3.1.1. I also have the same architecture as in the guide: two nodes with one instance each. The DAS is on node1.</p> <p>I've tried starting from scratch several times and am able to create the cluster, nodes and instances without issue. I also have the DAS communicating with node2 via SSH. However, each time when I get to the point where I attempt to start instance2 it fails:</p> <pre><code>$ ./asadmin start-local-instance --node node1 --sync normal instance2 Previous synchronization failed at Feb 23, 2012 2:41:53 PM Will perform full synchronization. Removing all cached state for instance instance2. CLI802 Synchronization failed for directory config, caused by: javax.xml.bind.JAXBException - with linked exception: [java.lang.ClassNotFoundException: com.sun.xml.bind.v2.ContextFactory] Command start-local-instance failed. </code></pre> <p>I spent the day Googling and searching GlassFish's Jira, but couldn't find a solution to this issue. I'd very much appreciate any ideas you have on how to solve this problem.</p> <p>My operating system is CentOS 5.7 and my Java version is 1.6.0_20</p> <p>Unfortunately my instance directory is empty, I'm assuming because it never started. So there is no log file. I set AS_DEBUG=true but it gives no stack trace. The last debug lines before the error are</p> <pre><code>Removing all cached state for instance instance2. Removing: /usr/local/glassfish3_1_1/glassfish/nodes/blade-50/instance2/config Removing: /usr/local/glassfish3_1_1/glassfish/nodes/blade-50/instance2/applications Removing: /usr/local/glassfish3_1_1/glassfish/nodes/blade-50/instance2/generated Removing: /usr/local/glassfish3_1_1/glassfish/nodes/blade-50/instance2/lib Removing: /usr/local/glassfish3_1_1/glassfish/nodes/blade-50/instance2/docroot Got exception: javax.xml.bind.JAXBException </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USTakaitra
    1. USTakaitra
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COWhat do the log files say? can you post in the error?
      singulars
      1. POGlassfish 3.1.1 start-local-instance fails with JAXBException
      1. USdann.dev
    2. COAlso, not sure if it has anything to do with it (haven't set up a cluster before) but the biggest problem I have with glassfish is it trying to us the same port's somewhere
      singulars
      1. POGlassfish 3.1.1 start-local-instance fails with JAXBException
      1. USdann.dev
    3. COHow do you know it's a port issue. Can you post the error?
      singulars
      1. POGlassfish 3.1.1 start-local-instance fails with JAXBException
      1. USPreston
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload