[JBoss JIRA] Created: (JBPORTAL-1814) 'Page layout' in admin portal works only for users called "admin"
by Tobias Roth (JIRA)
'Page layout' in admin portal works only for users called "admin"
-----------------------------------------------------------------
Key: JBPORTAL-1814
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1814
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal Core Admin
Reporter: Tobias Roth
In 'page layout' of the admin tool, portlet instances are only listed for the original admin user (i.e. callded 'admin', in role 'admin'). For other admin users, this list stays empty.
How to reproduce:
1) build JBoss_Portal_Branch_2_6, deploy the portal, identity and admin
2) log in as admin
3) create a new role called newadminrole
4) create a new user called newadmin, add him _only_ to the newadminrole (no other roles)
5) give access to the admin portal to newadmin
6) give access to the adminportlet instance to newadmin
7) log out, log in as newadmin
8) go to the 'page layout' page of the default page
9) verify that no portlet instances are listed
Some notes:
- if you log in as admin, the portlet instances are listed
- if you install cms or google widgets, lists of files appear for those
Unless I forgot to set some specific permissions, this suspiciously looks like a bug.
See JBPORTAL-1646 and JBPORTAL-1740 for similar, but not identic bugs.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 5 months
[JBoss JIRA] Created: (JBWEB-77) Servlet throws NPE the first time it is hit.
by Phillip Thurmond (JIRA)
Servlet throws NPE the first time it is hit.
--------------------------------------------
Key: JBWEB-77
URL: http://jira.jboss.com/jira/browse/JBWEB-77
Project: JBoss Web
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Phillip Thurmond
Assigned To: Mladen Turk
Priority: Blocker
The first time a servlet is hit, it throws a NPE. After the exception is thrown, the servlet works correctly. Here is the stack trace. Example war attached.
java.lang.NullPointerException
at org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:471)
at org.apache.catalina.connector.CoyoteOutputStream.print(CoyoteOutputStream.java:113)
at test.TestServlet.doGet(TestServlet.java:67)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:228)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:216)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:624)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:445)
at java.lang.Thread.run(Thread.java:595)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 5 months
[JBoss JIRA] Created: (JBCACHE-1225) TreeCache._enqueueMethodCall doesn't handle buddy backup FQNs
by Brian Stansberry (JIRA)
TreeCache._enqueueMethodCall doesn't handle buddy backup FQNs
-------------------------------------------------------------
Key: JBCACHE-1225
URL: http://jira.jboss.com/jira/browse/JBCACHE-1225
Project: JBoss Cache
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Clustering
Affects Versions: 1.4.1.SP7
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: 1.4.1.SP8
public void _enqueueMethodCall(String subtree, MethodCall call)
throws Throwable
{
JBCMethodCall jbcCall = (JBCMethodCall) call;
Region region = regionManager_.getRegion(subtree);
if (region == null)
throw new IllegalStateException("No region found for " + subtree);
RegionManager.getRegion will return null if the FQN is for a buddy backup region.
Solution is to do as TreeCacheMarshaller.getRegion() does -- check for buddy region fqn's and strip out the buddy-backup portion before calling regionManager.getRegion.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 5 months