[JBPAPP6-1793] rpms: after a yum update from 6.0.0 to 6.0.1 a reindex of the jar files is needed - JBoss Issue Tracker

XML

Word

Printable

Steps to Reproduce:

Hide

yum install eap6 (make sure you get 6.0.0)

run and use it...

yum update eap6 to get to 6.0.1

Solution: make sure EAP is not running, then execute:

find /usr/share/jbossas/modules/ -type f -name *.jar.index -exec rm -vf {} \;

which will remove all index files therefor forcing a new indexing at the next EAP start

As far as I know "yum update" can run a post-update script specific to the package being updated. We should remove the old index files from there.

Show
yum install eap6 (make sure you get 6.0.0) run and use it... yum update eap6 to get to 6.0.1 Solution: make sure EAP is not running, then execute: find /usr/share/jbossas/modules/ -type f -name *.jar.index -exec rm -vf {} \; which will remove all index files therefor forcing a new indexing at the next EAP start As far as I know "yum update" can run a post-update script specific to the package being updated. We should remove the old index files from there.
Workaround:

Workaround Exists
Workaround Description:

Hide

run:

find /usr/share/jbossas/modules/ -type f -name *.jar.index -exec rm -vf {} \;

Show
run: find /usr/share/jbossas/modules/ -type f -name *.jar.index -exec rm -vf {} \;
Docs QE Status:
NEW

Updated an EAP 6.0.0 installed with yum as rpm's to 6.0.1 causes "Failed to load application components!" when trying to access the console