I\'ve just finished re-installing my OS, and as always install and test standard tools which I use, and now I get this error like never before when I tried to start Jboss 5
jboss-5.0.0.GA-JDK6/server/default/conf/bootstrap$ diff bindings.xml.old bindings.xml
In this file you have to change two things. One:
Old
<bean name="StandardBindings" class="java.util.HashSet"
< elementClass="org.jboss.services.binding.ServiceBindingMetadata">
<constructor>
<parameter>
<set>
—New
<bean name="StandardBindings" class="java.util.HashSet">
<constructor>
<parameter class="java.util.Collection">
<set elementClass="org.jboss.services.binding.ServiceBindingMetadata">
Second: And then your http port number in the below bean definition
<bean class="org.jboss.services.binding.ServiceBindingMetadata">
<property name="serviceName">jboss.web:service=WebServer</property>
<property name="port">7070</property>
Looks like a bug that occurs with certain specific combinations of JRE and OS versions (see https://jira.jboss.org/jira/browse/JBAS-6981). Basically, the JBoss config is relying on reflection to return constructors in a certain order, and in some cases this order is different, causing the exception. Did you change your JRE version when you reinstalled, say from 1.6.0_17 to _18?
Anyway, the workaround is described in the JIRA issue, and also here. You need to change the content of conf/bootstrap/profile.xml. Look for the definition of the AttachmentStore, and change the constructor line so that it starts like this (i.e. add the class XML attribute to the parameter tag):
<constructor><parameter class="java.io.File"><inject …
The original version doesn't have the class="java.io.File" attribute.
Pretty sloppy of the JBoss folks, but there you go.