[JBoss JIRA] Created: (JBPORTAL-2081) NPE when deleting a portal
by Prabhat Jha (JIRA)
NPE when deleting a portal
--------------------------
Key: JBPORTAL-2081
URL: https://jira.jboss.org/jira/browse/JBPORTAL-2081
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal Core
Affects Versions: 2.6.6 Final
Reporter: Prabhat Jha
Assignee: Thomas Heute
Priority: Blocker
Fix For: 2.6.6 Final
I created a new portal. Added a page. So now there are two pages in portal including default. Make this portal default. Everything is fine. Now when I delete this portal, I get NPE. I think problem is because it's the default portal.
avax.servlet.ServletException: java.lang.NullPointerException
org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:276)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
root cause
java.lang.NullPointerException
org.jboss.portal.core.aspects.controller.PageCustomizerInterceptor.injectDashboardNav(PageCustomizerInterceptor.java:310)
org.jboss.portal.core.aspects.controller.PageCustomizerInterceptor.invoke(PageCustomizerInterceptor.java:165)
org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40)
org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
org.jboss.portal.core.aspects.controller.PolicyEnforcementInterceptor.invoke(PolicyEnforcementInterceptor.java:78)
org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40)
org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
org.jboss.portal.core.aspects.controller.node.PortalNodeInterceptor.invoke(PortalNodeInterceptor.java:81)
org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40)
org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
org.jboss.portal.core.aspects.controller.ControlInterceptor.invoke(ControlInterceptor.java:56)
org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40)
org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
org.jboss.portal.core.aspects.controller.NavigationalStateInterceptor.invoke(NavigationalStateInterceptor.java:42)
org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40)
org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
org.jboss.portal.core.controller.ajax.AjaxInterceptor.invoke(AjaxInterceptor.java:56)
org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40)
org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
org.jboss.portal.core.aspects.controller.ResourceAcquisitionInterceptor.invoke(ResourceAcquisitionInterceptor.java:50)
org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40)
org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
org.jboss.portal.common.invocation.Invocation.invoke(Invocation.java:157)
org.jboss.portal.core.controller.ControllerContext.execute(ControllerContext.java:134)
org.jboss.portal.core.model.portal.PortalObjectResponseHandler.processCommandResponse(PortalObjectResponseHandler.java:81)
org.jboss.portal.core.controller.classic.ClassicResponseHandler.processHandlers(ClassicResponseHandler.java:79)
org.jboss.portal.core.controller.classic.ClassicResponseHandler.processCommandResponse(ClassicResponseHandler.java:53)
org.jboss.portal.core.controller.handler.ResponseHandlerSelector.processCommandResponse(ResponseHandlerSelector.java:70)
org.jboss.portal.core.controller.Controller.processCommandResponse(Controller.java:271)
org.jboss.portal.core.controller.Controller.processCommand(Controller.java:259)
org.jboss.portal.core.controller.Controller.handle(Controller.java:217)
org.jboss.portal.server.RequestControllerDispatcher.invoke(RequestControllerDispatcher.java:51)
org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:131)
org.jboss.portal.core.cms.aspect.IdentityBindingInterceptor.invoke(IdentityBindingInterceptor.java:47)
org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
org.jboss.portal.server.aspects.server.ContentTypeInterceptor.invoke(ContentTypeInterceptor.java:68)
org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
org.jboss.portal.core.aspects.server.PortalContextPathInterceptor.invoke(PortalContextPathInterceptor.java:45)
org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
org.jboss.portal.core.aspects.server.LocaleInterceptor.invoke(LocaleInterceptor.java:96)
org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
org.jboss.portal.core.aspects.server.UserInterceptor.invoke(UserInterceptor.java:246)
org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
org.jboss.portal.server.aspects.server.SignOutInterceptor.invoke(SignOutInterceptor.java:98)
org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
org.jboss.portal.core.impl.api.user.UserEventBridgeTriggerInterceptor.invoke(UserEventBridgeTriggerInterceptor.java:65)
org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
org.jboss.portal.core.aspects.server.IdentityCacheInterceptor.invoke(IdentityCacheInterceptor.java:68)
org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
org.jboss.portal.core.aspects.server.TransactionInterceptor.org$jboss$portal$core$aspects$server$TransactionInterceptor$invoke$aop(TransactionInterceptor.java:49)
org.jboss.portal.core.aspects.server.TransactionInterceptor$invoke_N5143606530999904530.invokeNext(TransactionInterceptor$invoke_N5143606530999904530.java)
org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
org.jboss.aspects.tx.TxInterceptor$RequiresNew.invoke(TxInterceptor.java:253)
org.jboss.portal.core.aspects.server.TransactionInterceptor$invoke_N5143606530999904530.invokeNext(TransactionInterceptor$invoke_N5143606530999904530.java)
org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
org.jboss.aspects.tx.TxInterceptor$RequiresNew.invoke(TxInterceptor.java:262)
org.jboss.portal.core.aspects.server.TransactionInterceptor$invoke_N5143606530999904530.invokeNext(TransactionInterceptor$invoke_N5143606530999904530.java)
org.jboss.portal.core.aspects.server.TransactionInterceptor.invoke(TransactionInterceptor.java)
org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
org.jboss.portal.server.aspects.LockInterceptor$InternalLock.invoke(LockInterceptor.java:69)
org.jboss.portal.server.aspects.LockInterceptor.invoke(LockInterceptor.java:130)
org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
org.jboss.portal.common.invocation.Invocation.invoke(Invocation.java:157)
org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:250)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 2 months
[JBoss JIRA] Created: (JBPORTAL-2086) all subpages not displayed after adding them through admin ui
by Prabhat Jha (JIRA)
all subpages not displayed after adding them through admin ui
-------------------------------------------------------------
Key: JBPORTAL-2086
URL: https://jira.jboss.org/jira/browse/JBPORTAL-2086
Project: JBoss Portal
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Portal Core Admin
Affects Versions: 2.6.6 Final
Reporter: Prabhat Jha
Assignee: Thomas Heute
Fix For: 2.7.0 Beta1
I created a new portal. In default page of this new portal, I created subpage called xyz. I created another subpage of xyz called abc . So now it looks like
* Portals * > * prabat portal * > * default page * > * xyz page * > * abc page
But when I go to portal, I only see xyz page under default page. I was expecting it show a drop down with abc page when I put mouse over xyz. It's not critical and can be fixed in 2.7 and later version of 2.6.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 2 months
[JBoss JIRA] Resolved: (JBWEB-38) PDf file serving speed should be increased.static file serving speed by byte range req should be increased
by Remy Maucherat (JIRA)
[ https://jira.jboss.org/jira/browse/JBWEB-38?page=com.atlassian.jira.plugi... ]
Remy Maucherat resolved JBWEB-38.
---------------------------------
Resolution: Won't Fix
See https://issues.apache.org/bugzilla/show_bug.cgi?id=45419
I think the most realistic solution would be to use a filter or valve to add the header.
> PDf file serving speed should be increased.static file serving speed by byte range req should be increased
> -----------------------------------------------------------------------------------------------------------
>
> Key: JBWEB-38
> URL: https://jira.jboss.org/jira/browse/JBWEB-38
> Project: JBoss Web
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Core
> Affects Versions: JBossWeb embedded - AS 4.0.0
> Environment: jboss 3.2.5 , windows/unix
> Reporter: dev per
> Assignee: Remy Maucherat
> Attachments: test.war
>
>
> Our application serves pdf file over the web.This how we do pdf streaming
> 1.browser sends a request for a pdf file
> 2.Our application adds a header Accpet-Ranges which servers like a flag by which browser understands that this server can send response in byte ranges(streaming).
> 3.Jboss sends the header set by our application along with so many other headers to browser. Jboss tries to send some pdf content
> 4. As soon as Browser sees the flag and it sends request to Jboss to send pdf content in ranges of bytes .browser can request for any rangesof bytes withing contnet length of file.One request may have multiple byte range requests
> 4.Jboss sends the requested bytes to browser.
> Though streaming happens when we open Pdf , sometimes intial appearance of pdf in the browser take a longer time.
> To debug this problem we used a http sniffer and tried to open some other pdfs avilable over internet.This what we found by tracking our application and other pdfs in inetrnet
> a.PDfs over the internet opens up faster than our application pdfs over internet.
> b.reason is those server sends only few thousands of bytes and responds to byte range req from browser.
> c.But jboss application server we use tries to send few hunderd thousand bytes before it services the byte range request from browser.this makes the initial pdf appearance slow.
> Note:the req and resp header of inetrepdfs are same as what we set in our application .
> I think modifying tomcat DefaultServlet , to send only some thousand bytes and service byte range requests as soon as they are recieved , will fix the problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 2 months