-
1. Re: http://jira.jboss.com/jira/browse/JBPORTAL-459 You shoul
theute Dec 19, 2006 4:00 AM (in response to bsmithjj)On top of the documentation you have the Wiki. Here is a page related to what you are looking for:
http://wiki.jboss.org/wiki/Wiki.jsp?page=PortalSecurityImplementation -
2. Re: http://jira.jboss.com/jira/browse/JBPORTAL-459 You shoul
bsmithjj Dec 19, 2006 8:02 AM (in response to bsmithjj)The link to the wiki is not good enough. Here is a link to the 2.2 docs on the JACC security http://docs.jboss.com/jbportal/v2.2/reference-guide/en/html_single/#security in JBoss Portal. We are evaluating a few open source portals. We're concerned that there is a lot of change going on in the security layer of JBoss Portal. We built a portal using JBoss Portal last year and simply used JAAS and integrated our own permissions systems. This year, in preparation for a new project, we've been reviewing 2.4 we see that simply adding in our own login module isn't going to cut it - mainly due to the JACC Security policy stuff. We don't have a problem with JACC, we're mainly wondering if the JACC implementation is stable, going away, going to change, etc.... The fact that it's not in the documentation leads us to believe that maybe the security layer is in the process of being changed.
Please provide some indication of the direction of the Security layer - are the API's fixed for 2.4 and all 2.X releases of the Portal? Where's the real documentation for these API's? We are existing JBoss customers, we obviously wouldn't be interested in adding on or buying support for the JBoss Portal if we can't get decent written documentation on the API's and a guarantee of consistency on the portal.
Thanks. -
3. Re: http://jira.jboss.com/jira/browse/JBPORTAL-459 You shoul
theute Dec 19, 2006 9:01 AM (in response to bsmithjj)We are still using JAAS for authentication, the changes are quite minor in term of public API between 2.2 and 2.4 then 2.4 and 2.6. But it is more flexible (2.6 lets you store user preferences in a place other than Database (LDAP for example)), the identity part has just been finished and documentation for it is on the way (It will reach the Wiki first probably)
authentication and authorization documentation seems to be lacking in 2.4, but i see that you went ahead and open a JIRA task, this is a good thing but please do not change the priority as said in the READ ME when you submit a Jira task. -
4. Re: http://jira.jboss.com/jira/browse/JBPORTAL-459 You shoul
bsmithjj Dec 19, 2006 11:07 AM (in response to bsmithjj)so what you're saying is ....
1. Yes - the security API's are in flux
2. When 2.6 is released, instead of updating the documentation, you will prefer to update your wiki
I am not sure why I would a.) use 2.4 release of portal and b.) be interested in support for it - as we know, 2.4.X is the current 'stable' release of the portal. Sounds like I need to 'wait and see' how 2.6 shapes up with respect to the security API's / implementation. -
5. Re: http://jira.jboss.com/jira/browse/JBPORTAL-459 You shoul
theute Dec 19, 2006 12:19 PM (in response to bsmithjj)Sorry if i was unclear by saying that it will reach the Wiki first. What i meant is that the documentation for the security will reach the Wiki very soon. It will of course be incorporated to the official documentation for 2.6 at the release date.
It allows people to start playing with 2.6 while having some documentation available (in the wiki) -
6. JBoss Portal Security - You're losing your way...
bsmithjj Dec 24, 2006 1:20 PM (in response to bsmithjj)As I look into this more, look at the source code for 2.6, the wiki link you supplied, etc. I really am beginning to think that in some ways, you're losing your way with the security layer of JBoss Portal. All I want to do is customize the login for the dang thing for my environment. Instead, I find suggestions of JACC, and the promise of a large amount of volatility in the part of the portal related to authentication/authorization either with JAAS or JACC (and let's not forget that there's really no good documentation for customizing security now in any of the releases - download one and see if you can figure out from the docs how to get started with customizing security)
The wiki link you supplied earlier suggests that you are attempting to create a first class framework for authorization as part of developing point releases of JBoss Portal; furthermore, it suggests that you expect to have to create several versions of the security framework in the path to whatever you're trying to reach - the first version will be based on JACC...what's the next version going to be based on?
Are corporate customers really clamoring for such a massive overhaul in the security layer in a point release of the portal? We're customers - all we want is the portal/portlet functionality and the ability to customize security similar to what was available in 2.0.X versions of the portal. We like the page model, themes, the overall ease of developing/deploying portlets, etc. We also like how easy it has been in the past to customize security. We like the 2.6 DR1 release a lot - what we don't like is the fact that the security integration point is a moving target. -
7. Re: http://jira.jboss.com/jira/browse/JBPORTAL-459 You shoul
julien1 Dec 25, 2006 5:33 PM (in response to bsmithjj)JBoss Portal relies on the JACC framework for authorization. It is true that this has been removed from the documentation as it is an implementation detail.
Since 2.4 we have developed an abstraction on top of JACC which hides the usage of that layer (because the layer API simply sucks, specifically the configuration part).
We can work on providing documentation on the security abstraction we have however with the garantee that this framework will not change for the 2.x versions (i.e 2.4, 2.6 maybe 2.8) (JBoss Portal 3.x will work in non Java EE environement, i.e servlet container that does not provide this API implementation). -
8. Re: http://jira.jboss.com/jira/browse/JBPORTAL-459 You shoul
julien1 Dec 25, 2006 7:16 PM (in response to bsmithjj)I have started to rework the security documentation in the 2.6 trunk docs (http://anonsvn.jboss.org/repos/portal/docs/trunk/referenceGuide/en/modules/security.xml). It describe both authentication and authorization part with simple examples.
I regret that I don't have much time to spend on that item, however it provides accurate documentation on what exist since 2.4 and will remain until the end of life of the 2.x branch. It gives also a couple of examples.
I know that the subject is tough but it would be great is someone can extend the documentation as it is an important subject for the whole community. -
9. Re: http://jira.jboss.com/jira/browse/JBPORTAL-459 You shoul
bsmithjj Dec 26, 2006 12:14 PM (in response to bsmithjj)Julien,
Thanks for the update on the security API's, the documentation, and the guarantee to freeze the portal API's in this layer for the 2.X series. I will take a look at these and see if I can make progress with your documentation and example.
Thanks again,
Brad Smith -
10. Re: JBoss Portal Security - You're losing your way...
bsmithjj May 14, 2007 9:58 AM (in response to bsmithjj)"bsmithjj" wrote:
As I look into this more, look at the source code for 2.6, the wiki link you supplied, etc. I really am beginning to think that in some ways, you're losing your way with the security layer of JBoss Portal...
I've noticed in the so-called 'candidate releases (CR),' 1 and 2, that the dashboard link doesn't work. This kind of a release practice seems to be typical for the JBoss portal; I mean the practice of releasing alpha-quality software as a CR release. I've assumed that when JBoss labels a technology as CR release, it is suggesting that the technology is basically working and a.) you believe only minor bugs remain in the product, and b.) you'ld like the early adopters to help find bugs by trying to use the product in development. Furthermore, since CR is typically the label JBoss applies to a technology prior to releasing it as stable (GA), all the features that comprise the release of the technology really should be completely working as designed (modulo minor bugs).
However, since the dashboard just doesn't work in two CR releases, I have to conclude the dashboard is just not done and thus is really an alpha level feature. Also, I see a barage of new stuff appearing, like the usage of jBPM (which seriously slows down a clean portal install and startup times after installation). Google gadget integration (who really needs that?)? etc...
I wouldn't care so much about this, however, we are in the process of migrating a relatively large portal application from BEA Weblogic Portal 8 to JBoss portal and the flakiness of the JBoss releases causes a fair amount of consternation. Also, I must admit that I am bit spoiled by the high quality of coding and documentation of the Seam framework - switching from Seam to JBoss portal to do any work is horrible.
Thanks,
Brad Smith -
11. Re: http://jira.jboss.com/jira/browse/JBPORTAL-459 You shoul
theute May 14, 2007 10:11 AM (in response to bsmithjj)Dashboard link works, any other question ?
You can desactivate Google Gadget (just remove the corresponding war) we have lot of fans, thanks.
You can remove the CMS, remove the corresponding sar.
I'm glad to see that you diodn't change :) -
12. Re: http://jira.jboss.com/jira/browse/JBPORTAL-459 You shoul
bsmithjj May 14, 2007 10:23 AM (in response to bsmithjj)oh yes - I forgot the stack trace
09:18:40,432 ERROR STDERR - org.jboss.portal.core.controller.ResourceAccessDeniedException: Not Authorized has denied access 09:18:40,432 ERROR STDERR - at org.jboss.portal.core.model.portal.command.PortalObjectCommand.enforceSecurity(PortalObjectCommand.java:90) 09:18:40,432 ERROR STDERR - at org.jboss.portal.core.model.portal.command.render.RenderPageCommand.enforceSecurity(RenderPageCommand.java:120) 09:18:40,432 ERROR STDERR - at org.jboss.portal.core.aspects.controller.PolicyEnforcementInterceptor.invoke(PolicyEnforcementInterceptor.java:68) 09:18:40,432 ERROR STDERR - at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:38) 09:18:40,432 ERROR STDERR - at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) 09:18:40,432 ERROR STDERR - at org.jboss.portal.core.aspects.controller.node.PortalNodeInterceptor.invoke(PortalNodeInterceptor.java:81) 09:18:40,448 ERROR STDERR - at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:38) 09:18:40,448 ERROR STDERR - at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) 09:18:40,448 ERROR STDERR - at org.jboss.portal.core.aspects.controller.NavigationalStateInterceptor.invoke(NavigationalStateInterceptor.java:42) 09:18:40,448 ERROR STDERR - at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:38) 09:18:40,448 ERROR STDERR - at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) 09:18:40,448 ERROR STDERR - at org.jboss.portal.core.controller.ajax.AjaxInterceptor.invoke(AjaxInterceptor.java:51) 09:18:40,448 ERROR STDERR - at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:38) 09:18:40,448 ERROR STDERR - at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) 09:18:40,463 ERROR STDERR - at org.jboss.portal.common.invocation.Invocation.invoke(Invocation.java:157) 09:18:40,463 ERROR STDERR - at org.jboss.portal.core.controller.ControllerContext.execute(ControllerContext.java:121) 09:18:40,463 ERROR STDERR - at org.jboss.portal.core.model.portal.PortalObjectResponseHandler.processCommandResponse(PortalObjectResponseHandler.java:63) 09:18:40,463 ERROR STDERR - at org.jboss.portal.core.controller.classic.ClassicResponseHandler.processHandlers(ClassicResponseHandler.java:96) 09:18:40,463 ERROR STDERR - at org.jboss.portal.core.controller.classic.ClassicResponseHandler.processCommandResponse(ClassicResponseHandler.java:70) 09:18:40,463 ERROR STDERR - at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 09:18:40,463 ERROR STDERR - at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 09:18:40,463 ERROR STDERR - at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 09:18:40,479 ERROR STDERR - at java.lang.reflect.Method.invoke(Method.java:585) 09:18:40,479 ERROR STDERR - at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) 09:18:40,479 ERROR STDERR - at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) 09:18:40,479 ERROR STDERR - at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) 09:18:40,479 ERROR STDERR - at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) 09:18:40,479 ERROR STDERR - at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) 09:18:40,479 ERROR STDERR - at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) 09:18:40,479 ERROR STDERR - at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) 09:18:40,494 ERROR STDERR - at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) 09:18:40,494 ERROR STDERR - at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) 09:18:40,494 ERROR STDERR - at $Proxy122.processCommandResponse(Unknown Source) 09:18:40,494 ERROR STDERR - at org.jboss.portal.core.controller.handler.ResponseHandlerSelector.processCommandResponse(ResponseHandlerSelector.java:72) 09:18:40,494 ERROR STDERR - at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 09:18:40,494 ERROR STDERR - at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 09:18:40,494 ERROR STDERR - at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 09:18:40,510 ERROR STDERR - at java.lang.reflect.Method.invoke(Method.java:585) 09:18:40,510 ERROR STDERR - at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) 09:18:40,510 ERROR STDERR - at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) 09:18:40,510 ERROR STDERR - at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) 09:18:40,526 ERROR STDERR - at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) 09:18:40,526 ERROR STDERR - at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) 09:18:40,526 ERROR STDERR - at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) 09:18:40,526 ERROR STDERR - at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) 09:18:40,526 ERROR STDERR - at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) 09:18:40,526 ERROR STDERR - at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) 09:18:40,526 ERROR STDERR - at $Proxy133.processCommandResponse(Unknown Source) 09:18:40,541 ERROR STDERR - at org.jboss.portal.core.controller.Controller.processCommandResponse(Controller.java:264) 09:18:40,541 ERROR STDERR - at org.jboss.portal.core.controller.Controller.processCommand(Controller.java:252) 09:18:40,541 ERROR STDERR - at org.jboss.portal.core.controller.Controller.handle(Controller.java:213) 09:18:40,541 ERROR STDERR - at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 09:18:40,541 ERROR STDERR - at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 09:18:40,541 ERROR STDERR - at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 09:18:40,541 ERROR STDERR - at java.lang.reflect.Method.invoke(Method.java:585) 09:18:40,541 ERROR STDERR - at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) 09:18:40,557 ERROR STDERR - at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) 09:18:40,557 ERROR STDERR - at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) 09:18:40,557 ERROR STDERR - at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) 09:18:40,557 ERROR STDERR - at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) 09:18:40,557 ERROR STDERR - at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) 09:18:40,557 ERROR STDERR - at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) 09:18:40,557 ERROR STDERR - at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) 09:18:40,557 ERROR STDERR - at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) 09:18:40,573 ERROR STDERR - at $Proxy134.handle(Unknown Source) 09:18:40,573 ERROR STDERR - at org.jboss.portal.server.RequestControllerDispatcher.invoke(RequestControllerDispatcher.java:51) 09:18:40,573 ERROR STDERR - at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:131) 09:18:40,573 ERROR STDERR - at org.jboss.portal.core.cms.aspect.IdentityBindingInterceptor.invoke(IdentityBindingInterceptor.java:47) 09:18:40,573 ERROR STDERR - at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38) 09:18:40,573 ERROR STDERR - at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) 09:18:40,573 ERROR STDERR - at org.jboss.portal.server.aspects.server.ContentTypeInterceptor.invoke(ContentTypeInterceptor.java:68) 09:18:40,588 ERROR STDERR - at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38) 09:18:40,588 ERROR STDERR - at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) 09:18:40,588 ERROR STDERR - at org.jboss.portal.core.aspects.server.LocaleInterceptor.invoke(LocaleInterceptor.java:93) 09:18:40,588 ERROR STDERR - at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38) 09:18:40,588 ERROR STDERR - at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) 09:18:40,588 ERROR STDERR - at org.jboss.portal.core.aspects.server.UserInterceptor.invoke(UserInterceptor.java:245) 09:18:40,588 ERROR STDERR - at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38) 09:18:40,604 ERROR STDERR - at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) 09:18:40,619 ERROR STDERR - at org.jboss.portal.server.aspects.server.SessionInvalidatorInterceptor.invoke(SessionInvalidatorInterceptor.java:84) 09:18:40,619 ERROR STDERR - at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38) 09:18:40,619 ERROR STDERR - at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) 09:18:40,619 ERROR STDERR - at org.jboss.portal.core.impl.api.user.UserEventInterceptor.invoke(UserEventInterceptor.java:63) 09:18:40,619 ERROR STDERR - at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38) 09:18:40,619 ERROR STDERR - at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) 09:18:40,619 ERROR STDERR - at org.jboss.portal.core.aspects.server.TransactionInterceptor.org$jboss$portal$core$aspects$server$TransactionInterceptor$invoke$aop(TransactionInterceptor.java:49) 09:18:40,619 ERROR STDERR - at org.jboss.portal.core.aspects.server.TransactionInterceptor$invoke_N5143606530999904530.invokeNext(TransactionInterceptor$invoke_N5143606530999904530.java) 09:18:40,619 ERROR STDERR - at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) 09:18:40,635 ERROR STDERR - at org.jboss.aspects.tx.TxInterceptor$RequiresNew.invoke(TxInterceptor.java:253) 09:18:40,635 ERROR STDERR - at org.jboss.portal.core.aspects.server.TransactionInterceptor$invoke_N5143606530999904530.invokeNext(TransactionInterceptor$invoke_N5143606530999904530.java) 09:18:40,635 ERROR STDERR - at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) 09:18:40,635 ERROR STDERR - at org.jboss.aspects.tx.TxInterceptor$RequiresNew.invoke(TxInterceptor.java:262) 09:18:40,635 ERROR STDERR - at org.jboss.portal.core.aspects.server.TransactionInterceptor$invoke_N5143606530999904530.invokeNext(TransactionInterceptor$invoke_N5143606530999904530.java) 09:18:40,635 ERROR STDERR - at org.jboss.portal.core.aspects.server.TransactionInterceptor.invoke(TransactionInterceptor.java) 09:18:40,635 ERROR STDERR - at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38) 09:18:40,635 ERROR STDERR - at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) 09:18:40,651 ERROR STDERR - at org.jboss.portal.server.aspects.LockInterceptor$InternalLock.invoke(LockInterceptor.java:70) 09:18:40,651 ERROR STDERR - at org.jboss.portal.server.aspects.LockInterceptor.invoke(LockInterceptor.java:131) 09:18:40,651 ERROR STDERR - at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) 09:18:40,651 ERROR STDERR - at org.jboss.portal.common.invocation.Invocation.invoke(Invocation.java:157) 09:18:40,651 ERROR STDERR - at org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:380) 09:18:40,651 ERROR STDERR - at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) 09:18:40,651 ERROR STDERR - at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) 09:18:40,666 ERROR STDERR - at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) 09:18:40,666 ERROR STDERR - at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) 09:18:40,666 ERROR STDERR - at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) 09:18:40,666 ERROR STDERR - at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) 09:18:40,666 ERROR STDERR - at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) 09:18:40,666 ERROR STDERR - at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) 09:18:40,666 ERROR STDERR - at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) 09:18:40,666 ERROR STDERR - at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524) 09:18:40,682 ERROR STDERR - at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) 09:18:40,682 ERROR STDERR - at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) 09:18:40,682 ERROR STDERR - at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) 09:18:40,682 ERROR STDERR - at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) 09:18:40,682 ERROR STDERR - at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) 09:18:40,682 ERROR STDERR - at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) 09:18:40,682 ERROR STDERR - at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) 09:18:40,682 ERROR STDERR - at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) 09:18:40,698 ERROR STDERR - at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) 09:18:40,698 ERROR STDERR - at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) 09:18:40,698 ERROR STDERR - at java.lang.Thread.run(Thread.java:595)
Also, I see you haven't changed much either in the style of your reply (can't say I'm glad about it though)! ;-) -
13. Re: http://jira.jboss.com/jira/browse/JBPORTAL-459 You shoul
theute May 14, 2007 10:31 AM (in response to bsmithjj)Right i don't change your attitude always make me keep this style.
Anyway, some information on this stacktrace ? What is the scenario around this ? I am willing to resolve this if you met a bug, just give me some background, so far nobody reported an error like this. -
14. Re: http://jira.jboss.com/jira/browse/JBPORTAL-459 You shoul
bsmithjj May 14, 2007 10:43 AM (in response to bsmithjj)My environment:
Windows
JBoss 4.0.5 with EJB3
MySQL 5.0.37 with Connector 5.0.4
JDK 1.5
I downloaded JBoss Portal 2.6-CR2, placed it in the deploy directory, started the server up, logged in as admin, clicked the Admin link (that worked), then clicked the dashboard link and got a blank white page with the stack trace I posted earlier. According to another developer here, this was the same for CR1 as well.
Thanks