[MAGNOLIA-1138] Magnolia 3.0 RC3 does not install properly on JBoss Application Server 4.0.4 Created: 13/Oct/06 Updated: 23/Jan/13 Resolved: 16/Nov/06 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 3.0 RC3 |
| Fix Version/s: | 3.0 Final |
| Type: | Bug | Priority: | Critical |
| Reporter: | Gregory Pierce | Assignee: | Boris Kraft |
| Resolution: | Workaround exists | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Description |
|
I installed the product on JAS by first dropping the war files into the deploy directory and I could see that JBoss was deploying the application. Everything was fine until I went to log into the authoring environment at which time I received the error below. I then stopped the application server, unzipped the wars and redeployed everything restarted the application server and received the same error when trying to log in (note I don't see a users.properties or defaultUsers.properties file anywhere): 18:33:28,922 ERROR [UsersRolesLoginModule] Failed to load users/passwords/role files |
| Comments |
| Comment by Gregory Pierce [ 13/Oct/06 ] |
|
After working through the Wiki to look for a resolution for something else I found the resolution to this bug. Would it be possible to put in the readme that comes with Magnolia a note telling people to go to the wiki if they are installing on JBoss Application Server? In addition it is unclear whether or not the .war file really needs to be unzipped to run in the application server or not. Could this be made explicit in the documentation for 3.0? |