[MAGNOLIA-1560] Public instance throws error on initial bootstrap Created: 25/May/07  Updated: 06/Nov/07  Resolved: 06/Nov/07

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 3.1 M2
Fix Version/s: 3.5 RC1

Type: Bug Priority: Major
Reporter: zam6ak Assignee: Magnolia International
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

JBoss 4.0.5
3.1-SNAPSHOT (r9555)


Attachments: Text File MAGNOLIA-1560-stacktrace.txt     XML File config.server.activation.xml    
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
Date of First Response:

 Description   

Out of box installation using magnoliaPublic...

This may have something to do with DMS module not being updated to new activation configuration ....
The end result is that DMS module fails to register on public instance..

See attached file for stacktrace.



 Comments   
Comment by zam6ak [ 25/May/07 ]

I was able to place empty subscribers XML and rebootstrap public instance without problems.

  • Place attached file into WEB-INF/bootstrap/public/config

I dont know if this is a desired solution, but if the /server/activation is not to exist on public instance then something has to be done in the code....

Regards
Amir

Comment by zam6ak [ 25/May/07 ]

Attaching empty subsribers XML for /server/activation config for public instance

Comment by Magnolia International [ 26/May/07 ]

> This may have something to do with DMS module not being updated to new activation configuration ....
Definitely.

Can we please avoid reports of failures on stuff that's work-in-progress? See MAGNOLIA-1448 and the tasks related to the changes in the activation configuration (which afaik has been commited today...)
That kind of info is more than welcomed on the dev list though.

As a side note, can we avoir huge stacktraces in the body of reports?

Thanks.

Comment by Magnolia International [ 18/Oct/07 ]

What's the status of this ?

Comment by Philipp Bracher [ 19/Oct/07 ]

should be solved since /server/activation is registerd in the exchange module now (no difference between author & public)

Comment by Philipp Bracher [ 06/Nov/07 ]

is probably outdated

Generated at Mon Feb 12 03:28:05 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.