You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@roller.apache.org by Anil Gangolli <an...@busybuddha.org> on 2005/12/01 16:39:56 UTC
Re: Roller on Jboss 4.0 Problem
Bjorn:
This looks roughly like you are getting an implementation of the
Digester that is from a classloader outside the webapp (possibly in some
common, or system level) and it can't find the class within the webapp
(which is there in rollerweb.jar within the WEB-INF/lib.) You might be
able to work around this with various classloader semantic tweaks for
the web app, but I am not sure. If you're working from sources, you
might try the suggestion below.
roller-dev:
I think we can be more resilient to this by supplying the actual Class
class object rather than the String class name when setting up
addCreateObject() in the Digester. This means loading them ourselves.
Anyone see issues with this?
--a.
Anil Gangolli wrote:
>
> Can you also tell us what version of Roller you are using? and
> whether you built from sources or used the distribution?
>
> --a.
>
> Björn Ingimundarson wrote:
>
>> Hello,
>>
>> I am currently setting up Roller Weblogger on JBoss 4.0 and have
>> followed the instructions found at
>> http://rollerweblogger.org/wiki/Wiki.jsp?page=InstallationGuideJBoss4.
>>
>> The installation went ok and I can see my blog and post comments and
>> all that good stuff.
>> There are however 2 issues that are bothering me when trying to
>> log-in and post/modify entries.
>>
>> 1. I can not see the Menu on the main page due to the following
>> exception:
>>
>> 13:26:19,800 ERROR
>> [org.roller.presentation.tags.menu.RollerMenuModel.<init>(RollerMenuModel.java:106)]
>> Unexpected exception
>> java.lang.ClassNotFoundException: No ClassLoaders found for:
>> org.roller.presentation.tags.menu.MenuImpl
>> at
>> org.apache.commons.digester.Digester.createSAXException(Digester.java:2540)
>>
>> at
>> org.apache.commons.digester.Digester.createSAXException(Digester.java:2566)
>>
>> at
>> org.apache.commons.digester.Digester.startElement(Digester.java:1276)
>> at
>> org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
>> at
>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown
>> Source)
>> at
>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
>> Source)
>> at
>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
>> Source)
>> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>> at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>> at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>> at org.apache.commons.digester.Digester.parse(Digester.java:1567)
>> at
>> org.roller.presentation.tags.menu.RollerMenuModel.<init>(RollerMenuModel.java:72)
>>
>> at
>> org.roller.presentation.tags.menu.MenuTag.prepareContext(MenuTag.java:63)
>>
>> at
>> org.roller.presentation.tags.VelocityTag.doEndTag(VelocityTag.java:84)
>> at org.roller.presentation.tags.HybridTag.doEndTag(HybridTag.java:64)
>>
>> 2. I can not access anything after I'm logged in
>> I get an error message after I am logged in: You are not authorized
>> to access that resource.
>>
>> However I seem to be logged in. From my jboss.security.log I see
>>
>> 13:57:27,699 TRACE
>> [org.jboss.security.auth.spi.DatabaseServerLoginModule]
>> DatabaseServerLoginModule, dsJndiName=java:/jdbc/RollerDB
>> 13:57:27,699 TRACE
>> [org.jboss.security.auth.spi.DatabaseServerLoginModule]
>> principalsQuery=SELECT passphrase FROM rolleruser WHERE username=?
>> 13:57:27,699 TRACE
>> [org.jboss.security.auth.spi.DatabaseServerLoginModule]
>> rolesQuery=SELECT rolename, 'Roles' FROM userrole WHERE username=?
>> 13:57:27,699 TRACE
>> [org.jboss.security.auth.spi.DatabaseServerLoginModule] login
>> 13:57:27,699 TRACE
>> [org.jboss.security.auth.spi.DatabaseServerLoginModule] User 'bjossi'
>> authenticated, loginOk=true
>> 13:57:27,699 TRACE
>> [org.jboss.security.auth.spi.DatabaseServerLoginModule] commit,
>> loginOk=true
>> 13:57:27,870 TRACE
>> [org.jboss.security.auth.spi.DatabaseServerLoginModule] Assign user
>> to role editor
>> 13:57:27,870 TRACE
>> [org.jboss.security.plugins.JaasSecurityManager.roller-policy]
>> updateCache, subject=Subject:
>> Principal: bjossi
>> Principal: Roles(members:editor)
>>
>> So I am a logged in user in role 'editor'.
>>
>> Anyone out there with a successful JBoss Roller Weblogger Setup.
>>
>> Anyone,, anyone.. :)
>>
>> Best Regards,
>> Bjorn Ingimundarson
>>
>>
>
>
re: logging issue on JBoss 4.0.3
Posted by Anil Gangolli <an...@busybuddha.org>.
Bjorn:
Thanks for noticing the resource-ref issue. There may be more related
issues. I'll talk about that in my next e-mail.
Unless you really do want the latest (and possibly unstable code), you
should probably be pulling the tagged 2.0 sources or the distribution.
It's pretty clear that 2.1 is not quite stable yet.
This is really a completely new thread, so I cut out all of the older
stuff pertaining to the JBoss 4.0.0 problems below which were resolved
by your upgrade.
Noticed something about the logs below. TRACE level is only in log4j
1.2.12. Roller is using 1.2.11. We didn't move to 1.2.12 due to some
issues reported with it, but it may be fine to use it.
Something looks like its expecting TRACE and 1.2.12. Either it is
harmless or you end up with a misconfigured log4j. If the rest of
logging seems to be working right it may be ok. You may also have too
many log4j implementations in the classloader hierarchy; if you have
1.2.12 in a level that is "visible" to the webapp, you may be able to
remove the log4j jar from the Roller WEB-INF/lib; or replace the one in
the webapp with 1.2.12; or fix your other configs not to mention TRACE.
--a.
Björn Ingimundarson wrote:
> After successfully deploying Roller 1.2 on JBoss 4.0.3 I decided it
> was time to upgrade my Roller version so I fetched the latest source
> from SVN and built it. I updated my database launched JBoss with my
> upgraded Roller (2.1 the database says).
>
> The first time I started JBoss with the new Roller I got an exception
> reporting that it was unable to map the rollerdb datasource.
> jdbc/rollerdb was defined in my jboss-web.xml but no longer defined in
> web.xml. Why was this removed from web.xml. When I added this back to
> web.xml like it was before the server started up properly except for
> one stack trace on INFO level.
>
> 00:21:31,143 INFO
> [org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
> log4j:ERROR Could not create level [TRACE]. Reported error follows.
> 00:21:31,143 INFO
> [org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
> java.lang.ClassCastException
> 00:21:31,143 INFO
> [org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
> at
> org.apache.log4j.xml.DOMConfigurator.parseLevel(DOMConfigurator.java:521)
> 00:21:31,143 INFO
> [org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
> at
> org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:437)
>
> 00:21:31,153 INFO
> [org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
> at
> org.apache.log4j.xml.DOMConfigurator.parseCategory(DOMConfigurator.java:344)
>
> 00:21:31,153 INFO
> [org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
> at
> org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:790)
> 00:21:31,153 INFO
> [org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
> at
> org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:675)
>
> 00:21:31,163 INFO
> [org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
> at
> org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:625)
>
> 00:21:31,163 INFO
> [org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
> at
> org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:611)
>
> 00:21:31,173 INFO
> [org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
> at
> org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:468)
>
> 00:21:31,173 INFO
> [org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
> at org.apache.log4j.LogManager.<clinit>(LogManager.java:122)
> 00:21:31,183 INFO
> [org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
> at org.apache.log4j.Category.getInstance(Category.java:519)
> 00:21:31,183 INFO
> [org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
> at
> org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)
>
> 00:21:31,193 INFO
> [org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
> at
> org.apache.velocity.runtime.log.LogManager.createLogSystem(LogManager.java:127)
>
> 00:21:31,193 INFO
> [org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
> at
> org.apache.velocity.runtime.RuntimeInstance.initializeLogger(RuntimeInstance.java:553)
>
> 00:21:31,203 INFO
> [org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
> at
> org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.java:226)
>
> 00:21:31,203 INFO
> [org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
> at
> org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.java:461)
>
> 00:21:31,203 INFO
> [org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
> at
> org.apache.velocity.runtime.RuntimeSingleton.init(RuntimeSingleton.java:208)
>
> 00:21:31,213 INFO
> [org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
> at org.apache.velocity.app.Velocity.init(Velocity.java:106)
> 00:21:31,243 INFO
> [org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
> at
> org.apache.velocity.servlet.VelocityServlet.initVelocity(VelocityServlet.java:193)
>
> 00:21:31,243 INFO
> [org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
> at
> org.apache.velocity.servlet.VelocityServlet.init(VelocityServlet.java:162)
>
> 00:21:31,243 INFO
> [org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
> at
> org.roller.presentation.velocity.BasePageServlet.init(BasePageServlet.java:49)
>
>
> Roller however seems to run without a hitch despite of this.
>
> And oh man Roller 2 is cool :)
>
> Best Regards,
> Bjorn Ingimundarson
>
>
> Anil Gangolli wrote:
>
Re: regarding the removal of web-security.xml from metadata/xdoclet
Posted by Matt Raible <mr...@gmail.com>.
On 12/3/05, Anil Gangolli <an...@busybuddha.org> wrote:
>
> As Björn Ingimundarson recently noticed, we somehow lost the resource
> refs portion of the web.xml.
>
> It's because they happened to have been hiding in the web-security.xml
> fragment in metadata/xdoclet, and that was removed with the recent Acegi
> changes. I believe we need the resource refs in general, even though
> things might work for Tomcat. There's an odd comment that was there
> calling it a "Tomcat resource ref", but there's nothing specific about
> it; it's part of the Servlet 2.3 and 2.4 specs, and I think Tomcat may
> be one of the more lenient containers with respect to missing these.
> Not sure about that, but I'd like to put them back. Objections?
Sorry about that - I forgot to checkin
metadata/web-resource-env-refs.xml, should be fixed now.
>
> On a related but different note, I'm a bit concerned that the
> security-constraint clauses that were there might also be required for
> some containers to know to setup for HttpServletRequest.isUserInRole()
> properly (which appears to still be used in the codebase). Does the
> way Acegi is injected entirely obviate the need for them for all
> containers? Matt maybe you can comment on this question.
Yes, the SecurityContextHolderAwareRequestFilter makes it possible for
request.isUserInRole("rolename") to work. I've successfully
integrated it into AppFuse, and a couple of productions sites - and
haven't had any issues. I haven't seen any issues on my site so far -
but it is a single-user site for the most part.
Matt
>
> --a.
>
>
regarding the removal of web-security.xml from metadata/xdoclet
Posted by Anil Gangolli <an...@busybuddha.org>.
As Björn Ingimundarson recently noticed, we somehow lost the resource
refs portion of the web.xml.
It's because they happened to have been hiding in the web-security.xml
fragment in metadata/xdoclet, and that was removed with the recent Acegi
changes. I believe we need the resource refs in general, even though
things might work for Tomcat. There's an odd comment that was there
calling it a "Tomcat resource ref", but there's nothing specific about
it; it's part of the Servlet 2.3 and 2.4 specs, and I think Tomcat may
be one of the more lenient containers with respect to missing these.
Not sure about that, but I'd like to put them back. Objections?
On a related but different note, I'm a bit concerned that the
security-constraint clauses that were there might also be required for
some containers to know to setup for HttpServletRequest.isUserInRole()
properly (which appears to still be used in the codebase). Does the
way Acegi is injected entirely obviate the need for them for all
containers? Matt maybe you can comment on this question.
--a.
Re: Roller on Jboss 4.0 Problem
Posted by Björn Ingimundarson <bj...@hexsoftware.net>.
After successfully deploying Roller 1.2 on JBoss 4.0.3 I decided it was
time to upgrade my Roller version so I fetched the latest source from
SVN and built it. I updated my database launched JBoss with my upgraded
Roller (2.1 the database says).
The first time I started JBoss with the new Roller I got an exception
reporting that it was unable to map the rollerdb datasource.
jdbc/rollerdb was defined in my jboss-web.xml but no longer defined in
web.xml. Why was this removed from web.xml. When I added this back to
web.xml like it was before the server started up properly except for one
stack trace on INFO level.
00:21:31,143 INFO
[org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
log4j:ERROR Could not create level [TRACE]. Reported error follows.
00:21:31,143 INFO
[org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
java.lang.ClassCastException
00:21:31,143 INFO
[org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
at
org.apache.log4j.xml.DOMConfigurator.parseLevel(DOMConfigurator.java:521)
00:21:31,143 INFO
[org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
at
org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:437)
00:21:31,153 INFO
[org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
at
org.apache.log4j.xml.DOMConfigurator.parseCategory(DOMConfigurator.java:344)
00:21:31,153 INFO
[org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
at org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:790)
00:21:31,153 INFO
[org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
at
org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:675)
00:21:31,163 INFO
[org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
at
org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:625)
00:21:31,163 INFO
[org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
at
org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:611)
00:21:31,173 INFO
[org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
at
org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:468)
00:21:31,173 INFO
[org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
at org.apache.log4j.LogManager.<clinit>(LogManager.java:122)
00:21:31,183 INFO
[org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
at org.apache.log4j.Category.getInstance(Category.java:519)
00:21:31,183 INFO
[org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
at
org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)
00:21:31,193 INFO
[org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
at
org.apache.velocity.runtime.log.LogManager.createLogSystem(LogManager.java:127)
00:21:31,193 INFO
[org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
at
org.apache.velocity.runtime.RuntimeInstance.initializeLogger(RuntimeInstance.java:553)
00:21:31,203 INFO
[org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
at
org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.java:226)
00:21:31,203 INFO
[org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
at
org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.java:461)
00:21:31,203 INFO
[org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
at
org.apache.velocity.runtime.RuntimeSingleton.init(RuntimeSingleton.java:208)
00:21:31,213 INFO
[org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
at org.apache.velocity.app.Velocity.init(Velocity.java:106)
00:21:31,243 INFO
[org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
at
org.apache.velocity.servlet.VelocityServlet.initVelocity(VelocityServlet.java:193)
00:21:31,243 INFO
[org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
at
org.apache.velocity.servlet.VelocityServlet.init(VelocityServlet.java:162)
00:21:31,243 INFO
[org.apache.velocity.runtime.log.SimpleLog4JLogSystem.init(SimpleLog4JLogSystem.java:63)]
at
org.roller.presentation.velocity.BasePageServlet.init(BasePageServlet.java:49)
Roller however seems to run without a hitch despite of this.
And oh man Roller 2 is cool :)
Best Regards,
Bjorn Ingimundarson
Anil Gangolli wrote:
>
> Thanks. I'll add a note to the wiki.
>
> Björn Ingimundarson wrote:
>
>> Seems like this was all just a JBoss issue.
>>
>> I spotted this issue when searching for a fix on Google
>> http://jira.atlassian.com/browse/JRA-8279
>>
>> I upgraded to the latest version of JBoss and now everything works
>> like a charm :)
>>
>> This seems to also have fixed my user role problem. So it looks like
>> the userrole went down the drain when RollerMenuModel failed (due to
>> the class loader problem).
>>
>> Best regards,
>> Bjorn Ingimundarson
>>
>> Anil Gangolli wrote:
>>
>>> Bjorn:
>>>
>>> This looks roughly like you are getting an implementation of the
>>> Digester that is from a classloader outside the webapp (possibly in
>>> some common, or system level) and it can't find the class within the
>>> webapp (which is there in rollerweb.jar within the WEB-INF/lib.)
>>> You might be able to work around this with various classloader
>>> semantic tweaks for the web app, but I am not sure. If you're
>>> working from sources, you might try the suggestion below.
>>>
>>> roller-dev:
>>>
>>> I think we can be more resilient to this by supplying the actual
>>> Class class object rather than the String class name when setting up
>>> addCreateObject() in the Digester. This means loading them
>>> ourselves. Anyone see issues with this?
>>>
>>> --a.
>>>
>>> Anil Gangolli wrote:
>>>
>>>>
>>>> Can you also tell us what version of Roller you are using? and
>>>> whether you built from sources or used the distribution?
>>>>
>>>> --a.
>>>>
>>>> Björn Ingimundarson wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> I am currently setting up Roller Weblogger on JBoss 4.0 and have
>>>>> followed the instructions found at
>>>>> http://rollerweblogger.org/wiki/Wiki.jsp?page=InstallationGuideJBoss4.
>>>>>
>>>>>
>>>>> The installation went ok and I can see my blog and post comments
>>>>> and all that good stuff.
>>>>> There are however 2 issues that are bothering me when trying to
>>>>> log-in and post/modify entries.
>>>>>
>>>>> 1. I can not see the Menu on the main page due to the following
>>>>> exception:
>>>>>
>>>>> 13:26:19,800 ERROR
>>>>> [org.roller.presentation.tags.menu.RollerMenuModel.<init>(RollerMenuModel.java:106)]
>>>>> Unexpected exception
>>>>> java.lang.ClassNotFoundException: No ClassLoaders found for:
>>>>> org.roller.presentation.tags.menu.MenuImpl
>>>>> at
>>>>> org.apache.commons.digester.Digester.createSAXException(Digester.java:2540)
>>>>>
>>>>> at
>>>>> org.apache.commons.digester.Digester.createSAXException(Digester.java:2566)
>>>>>
>>>>> at
>>>>> org.apache.commons.digester.Digester.startElement(Digester.java:1276)
>>>>> at
>>>>> org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown
>>>>> Source)
>>>>> at
>>>>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown
>>>>> Source)
>>>>> at
>>>>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
>>>>> Source)
>>>>> at
>>>>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
>>>>> Source)
>>>>> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
>>>>> Source)
>>>>> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
>>>>> Source)
>>>>> at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>>>>> at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
>>>>> Source)
>>>>> at org.apache.commons.digester.Digester.parse(Digester.java:1567)
>>>>> at
>>>>> org.roller.presentation.tags.menu.RollerMenuModel.<init>(RollerMenuModel.java:72)
>>>>>
>>>>> at
>>>>> org.roller.presentation.tags.menu.MenuTag.prepareContext(MenuTag.java:63)
>>>>>
>>>>> at
>>>>> org.roller.presentation.tags.VelocityTag.doEndTag(VelocityTag.java:84)
>>>>>
>>>>> at
>>>>> org.roller.presentation.tags.HybridTag.doEndTag(HybridTag.java:64)
>>>>>
>>>>> 2. I can not access anything after I'm logged in
>>>>> I get an error message after I am logged in: You are not
>>>>> authorized to access that resource.
>>>>>
>>>>> However I seem to be logged in. From my jboss.security.log I see
>>>>>
>>>>> 13:57:27,699 TRACE
>>>>> [org.jboss.security.auth.spi.DatabaseServerLoginModule]
>>>>> DatabaseServerLoginModule, dsJndiName=java:/jdbc/RollerDB
>>>>> 13:57:27,699 TRACE
>>>>> [org.jboss.security.auth.spi.DatabaseServerLoginModule]
>>>>> principalsQuery=SELECT passphrase FROM rolleruser WHERE username=?
>>>>> 13:57:27,699 TRACE
>>>>> [org.jboss.security.auth.spi.DatabaseServerLoginModule]
>>>>> rolesQuery=SELECT rolename, 'Roles' FROM userrole WHERE username=?
>>>>> 13:57:27,699 TRACE
>>>>> [org.jboss.security.auth.spi.DatabaseServerLoginModule] login
>>>>> 13:57:27,699 TRACE
>>>>> [org.jboss.security.auth.spi.DatabaseServerLoginModule] User
>>>>> 'bjossi' authenticated, loginOk=true
>>>>> 13:57:27,699 TRACE
>>>>> [org.jboss.security.auth.spi.DatabaseServerLoginModule] commit,
>>>>> loginOk=true
>>>>> 13:57:27,870 TRACE
>>>>> [org.jboss.security.auth.spi.DatabaseServerLoginModule] Assign
>>>>> user to role editor
>>>>> 13:57:27,870 TRACE
>>>>> [org.jboss.security.plugins.JaasSecurityManager.roller-policy]
>>>>> updateCache, subject=Subject:
>>>>> Principal: bjossi
>>>>> Principal: Roles(members:editor)
>>>>>
>>>>> So I am a logged in user in role 'editor'.
>>>>>
>>>>> Anyone out there with a successful JBoss Roller Weblogger Setup.
>>>>>
>>>>> Anyone,, anyone.. :)
>>>>>
>>>>> Best Regards,
>>>>> Bjorn Ingimundarson
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
--
Bjorn Ingimundarson
Senior Developer
Hex Software
Tel/Mobile: +354 824 4680
E-mail: bjossi@hexsoftware.net
Web page: http://www.hexia.net
Re: Roller on Jboss 4.0 Problem
Posted by Anil Gangolli <an...@busybuddha.org>.
Thanks. I'll add a note to the wiki.
Björn Ingimundarson wrote:
> Seems like this was all just a JBoss issue.
>
> I spotted this issue when searching for a fix on Google
> http://jira.atlassian.com/browse/JRA-8279
>
> I upgraded to the latest version of JBoss and now everything works
> like a charm :)
>
> This seems to also have fixed my user role problem. So it looks like
> the userrole went down the drain when RollerMenuModel failed (due to
> the class loader problem).
>
> Best regards,
> Bjorn Ingimundarson
>
> Anil Gangolli wrote:
>
>> Bjorn:
>>
>> This looks roughly like you are getting an implementation of the
>> Digester that is from a classloader outside the webapp (possibly in
>> some common, or system level) and it can't find the class within the
>> webapp (which is there in rollerweb.jar within the WEB-INF/lib.) You
>> might be able to work around this with various classloader semantic
>> tweaks for the web app, but I am not sure. If you're working from
>> sources, you might try the suggestion below.
>>
>> roller-dev:
>>
>> I think we can be more resilient to this by supplying the actual
>> Class class object rather than the String class name when setting up
>> addCreateObject() in the Digester. This means loading them
>> ourselves. Anyone see issues with this?
>>
>> --a.
>>
>> Anil Gangolli wrote:
>>
>>>
>>> Can you also tell us what version of Roller you are using? and
>>> whether you built from sources or used the distribution?
>>>
>>> --a.
>>>
>>> Björn Ingimundarson wrote:
>>>
>>>> Hello,
>>>>
>>>> I am currently setting up Roller Weblogger on JBoss 4.0 and have
>>>> followed the instructions found at
>>>> http://rollerweblogger.org/wiki/Wiki.jsp?page=InstallationGuideJBoss4.
>>>>
>>>> The installation went ok and I can see my blog and post comments
>>>> and all that good stuff.
>>>> There are however 2 issues that are bothering me when trying to
>>>> log-in and post/modify entries.
>>>>
>>>> 1. I can not see the Menu on the main page due to the following
>>>> exception:
>>>>
>>>> 13:26:19,800 ERROR
>>>> [org.roller.presentation.tags.menu.RollerMenuModel.<init>(RollerMenuModel.java:106)]
>>>> Unexpected exception
>>>> java.lang.ClassNotFoundException: No ClassLoaders found for:
>>>> org.roller.presentation.tags.menu.MenuImpl
>>>> at
>>>> org.apache.commons.digester.Digester.createSAXException(Digester.java:2540)
>>>>
>>>> at
>>>> org.apache.commons.digester.Digester.createSAXException(Digester.java:2566)
>>>>
>>>> at
>>>> org.apache.commons.digester.Digester.startElement(Digester.java:1276)
>>>> at
>>>> org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown
>>>> Source)
>>>> at
>>>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown
>>>> Source)
>>>> at
>>>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
>>>> Source)
>>>> at
>>>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
>>>> Source)
>>>> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
>>>> Source)
>>>> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
>>>> Source)
>>>> at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>>>> at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
>>>> Source)
>>>> at org.apache.commons.digester.Digester.parse(Digester.java:1567)
>>>> at
>>>> org.roller.presentation.tags.menu.RollerMenuModel.<init>(RollerMenuModel.java:72)
>>>>
>>>> at
>>>> org.roller.presentation.tags.menu.MenuTag.prepareContext(MenuTag.java:63)
>>>>
>>>> at
>>>> org.roller.presentation.tags.VelocityTag.doEndTag(VelocityTag.java:84)
>>>> at
>>>> org.roller.presentation.tags.HybridTag.doEndTag(HybridTag.java:64)
>>>>
>>>> 2. I can not access anything after I'm logged in
>>>> I get an error message after I am logged in: You are not
>>>> authorized to access that resource.
>>>>
>>>> However I seem to be logged in. From my jboss.security.log I see
>>>>
>>>> 13:57:27,699 TRACE
>>>> [org.jboss.security.auth.spi.DatabaseServerLoginModule]
>>>> DatabaseServerLoginModule, dsJndiName=java:/jdbc/RollerDB
>>>> 13:57:27,699 TRACE
>>>> [org.jboss.security.auth.spi.DatabaseServerLoginModule]
>>>> principalsQuery=SELECT passphrase FROM rolleruser WHERE username=?
>>>> 13:57:27,699 TRACE
>>>> [org.jboss.security.auth.spi.DatabaseServerLoginModule]
>>>> rolesQuery=SELECT rolename, 'Roles' FROM userrole WHERE username=?
>>>> 13:57:27,699 TRACE
>>>> [org.jboss.security.auth.spi.DatabaseServerLoginModule] login
>>>> 13:57:27,699 TRACE
>>>> [org.jboss.security.auth.spi.DatabaseServerLoginModule] User
>>>> 'bjossi' authenticated, loginOk=true
>>>> 13:57:27,699 TRACE
>>>> [org.jboss.security.auth.spi.DatabaseServerLoginModule] commit,
>>>> loginOk=true
>>>> 13:57:27,870 TRACE
>>>> [org.jboss.security.auth.spi.DatabaseServerLoginModule] Assign user
>>>> to role editor
>>>> 13:57:27,870 TRACE
>>>> [org.jboss.security.plugins.JaasSecurityManager.roller-policy]
>>>> updateCache, subject=Subject:
>>>> Principal: bjossi
>>>> Principal: Roles(members:editor)
>>>>
>>>> So I am a logged in user in role 'editor'.
>>>>
>>>> Anyone out there with a successful JBoss Roller Weblogger Setup.
>>>>
>>>> Anyone,, anyone.. :)
>>>>
>>>> Best Regards,
>>>> Bjorn Ingimundarson
>>>>
>>>>
>>>
>>>
>>
>>
>
>
Re: Roller on Jboss 4.0 Problem
Posted by Björn Ingimundarson <bj...@hexsoftware.net>.
Seems like this was all just a JBoss issue.
I spotted this issue when searching for a fix on Google
http://jira.atlassian.com/browse/JRA-8279
I upgraded to the latest version of JBoss and now everything works like
a charm :)
This seems to also have fixed my user role problem. So it looks like the
userrole went down the drain when RollerMenuModel failed (due to the
class loader problem).
Best regards,
Bjorn Ingimundarson
Anil Gangolli wrote:
> Bjorn:
>
> This looks roughly like you are getting an implementation of the
> Digester that is from a classloader outside the webapp (possibly in
> some common, or system level) and it can't find the class within the
> webapp (which is there in rollerweb.jar within the WEB-INF/lib.) You
> might be able to work around this with various classloader semantic
> tweaks for the web app, but I am not sure. If you're working from
> sources, you might try the suggestion below.
>
> roller-dev:
>
> I think we can be more resilient to this by supplying the actual Class
> class object rather than the String class name when setting up
> addCreateObject() in the Digester. This means loading them
> ourselves. Anyone see issues with this?
>
> --a.
>
> Anil Gangolli wrote:
>
>>
>> Can you also tell us what version of Roller you are using? and
>> whether you built from sources or used the distribution?
>>
>> --a.
>>
>> Björn Ingimundarson wrote:
>>
>>> Hello,
>>>
>>> I am currently setting up Roller Weblogger on JBoss 4.0 and have
>>> followed the instructions found at
>>> http://rollerweblogger.org/wiki/Wiki.jsp?page=InstallationGuideJBoss4.
>>>
>>> The installation went ok and I can see my blog and post comments and
>>> all that good stuff.
>>> There are however 2 issues that are bothering me when trying to
>>> log-in and post/modify entries.
>>>
>>> 1. I can not see the Menu on the main page due to the following
>>> exception:
>>>
>>> 13:26:19,800 ERROR
>>> [org.roller.presentation.tags.menu.RollerMenuModel.<init>(RollerMenuModel.java:106)]
>>> Unexpected exception
>>> java.lang.ClassNotFoundException: No ClassLoaders found for:
>>> org.roller.presentation.tags.menu.MenuImpl
>>> at
>>> org.apache.commons.digester.Digester.createSAXException(Digester.java:2540)
>>>
>>> at
>>> org.apache.commons.digester.Digester.createSAXException(Digester.java:2566)
>>>
>>> at
>>> org.apache.commons.digester.Digester.startElement(Digester.java:1276)
>>> at
>>> org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown
>>> Source)
>>> at
>>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown
>>> Source)
>>> at
>>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
>>> Source)
>>> at
>>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
>>> Source)
>>> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
>>> Source)
>>> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
>>> Source)
>>> at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>>> at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>>> at org.apache.commons.digester.Digester.parse(Digester.java:1567)
>>> at
>>> org.roller.presentation.tags.menu.RollerMenuModel.<init>(RollerMenuModel.java:72)
>>>
>>> at
>>> org.roller.presentation.tags.menu.MenuTag.prepareContext(MenuTag.java:63)
>>>
>>> at
>>> org.roller.presentation.tags.VelocityTag.doEndTag(VelocityTag.java:84)
>>> at
>>> org.roller.presentation.tags.HybridTag.doEndTag(HybridTag.java:64)
>>>
>>> 2. I can not access anything after I'm logged in
>>> I get an error message after I am logged in: You are not
>>> authorized to access that resource.
>>>
>>> However I seem to be logged in. From my jboss.security.log I see
>>>
>>> 13:57:27,699 TRACE
>>> [org.jboss.security.auth.spi.DatabaseServerLoginModule]
>>> DatabaseServerLoginModule, dsJndiName=java:/jdbc/RollerDB
>>> 13:57:27,699 TRACE
>>> [org.jboss.security.auth.spi.DatabaseServerLoginModule]
>>> principalsQuery=SELECT passphrase FROM rolleruser WHERE username=?
>>> 13:57:27,699 TRACE
>>> [org.jboss.security.auth.spi.DatabaseServerLoginModule]
>>> rolesQuery=SELECT rolename, 'Roles' FROM userrole WHERE username=?
>>> 13:57:27,699 TRACE
>>> [org.jboss.security.auth.spi.DatabaseServerLoginModule] login
>>> 13:57:27,699 TRACE
>>> [org.jboss.security.auth.spi.DatabaseServerLoginModule] User
>>> 'bjossi' authenticated, loginOk=true
>>> 13:57:27,699 TRACE
>>> [org.jboss.security.auth.spi.DatabaseServerLoginModule] commit,
>>> loginOk=true
>>> 13:57:27,870 TRACE
>>> [org.jboss.security.auth.spi.DatabaseServerLoginModule] Assign user
>>> to role editor
>>> 13:57:27,870 TRACE
>>> [org.jboss.security.plugins.JaasSecurityManager.roller-policy]
>>> updateCache, subject=Subject:
>>> Principal: bjossi
>>> Principal: Roles(members:editor)
>>>
>>> So I am a logged in user in role 'editor'.
>>>
>>> Anyone out there with a successful JBoss Roller Weblogger Setup.
>>>
>>> Anyone,, anyone.. :)
>>>
>>> Best Regards,
>>> Bjorn Ingimundarson
>>>
>>>
>>
>>
>
>
--
Bjorn Ingimundarson
Senior Developer
Hex Software
Tel/Mobile: +354 824 4680
E-mail: bjossi@hexsoftware.net
Web page: http://www.hexia.net