2:32 p.m.
problem accessing a portlet deployed in a cluster
-------------------------------------------------
Key: JBPORTAL-1879
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1879
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal Server
Affects Versions: 2.6.4 Final
Reporter: Prabhat Jha
Assigned To: Thomas Heute
Fix For: 2.6.5 Final
This is something I had noticed in my scalability test but at that time I thought I may
have done something stupid and later, I saw a similar note in support case.
I have two portal servers (ports-01, ports-02) configuration where nullPortletPage.war is
predeployed before servers are started. If I start both servers simultaneously and access
http://localhost:8280/portal/portal/default/NullPortletPage then I get a 404 error with
"The requested resource () is not available". I am able to access the page if I
hit http://localhost:8180/portal/portal/default/NullPortletPage (notice the port) .
What is more interesting is that when I start servers one by one i.e. start second server
when first one has already started, then I can access the NullPortletPage in both servers.
Since there is a work around, let's fix this by 2.6.5 release.
--
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
2:41 p.m.
New subject: [JBoss JIRA] Commented: (JBPORTAL-1879) problem accessing a portlet deployed in a cluster
[ http://jira.jboss.com/jira/browse/JBPORTAL-1879?page=comments#action_1239... ]
Prabhat Jha commented on JBPORTAL-1879:
---------------------------------------
I think this can be tested with any war containing simple portlet.
problem accessing a portlet deployed in a cluster
-------------------------------------------------
Key: JBPORTAL-1879
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1879
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal Server
Affects Versions: 2.6.4 Final
Reporter: Prabhat Jha
Assigned To: Thomas Heute
Fix For: 2.6.5 Final
This is something I had noticed in my scalability test but at that time I thought I may
have done something stupid and later, I saw a similar note in support case.
I have two portal servers (ports-01, ports-02) configuration where nullPortletPage.war is
predeployed before servers are started. If I start both servers simultaneously and access
http://localhost:8280/portal/portal/default/NullPortletPage then I get a 404 error with
"The requested resource () is not available". I am able to access the page if I
hit http://localhost:8180/portal/portal/default/NullPortletPage (notice the port) .
What is more interesting is that when I start servers one by one i.e. start second server
when first one has already started, then I can access the NullPortletPage in both servers.
Since there is a work around, let's fix this by 2.6.5 release.
--
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
5:36 a.m.
New subject: [JBoss JIRA] Updated: (JBPORTAL-1879) problem accessing a portlet deployed in a cluster
[ http://jira.jboss.com/jira/browse/JBPORTAL-1879?page=all ]
Thomas Heute updated JBPORTAL-1879:
-----------------------------------
Fix Version/s: 2.7 Final
(was: 2.6.5 Final)
problem accessing a portlet deployed in a cluster
-------------------------------------------------
Key: JBPORTAL-1879
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1879
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal Server
Affects Versions: 2.6.4 Final
Reporter: Prabhat Jha
Assigned To: Thomas Heute
Fix For: 2.7 Final
This is something I had noticed in my scalability test but at that time I thought I may
have done something stupid and later, I saw a similar note in support case.
I have two portal servers (ports-01, ports-02) configuration where nullPortletPage.war is
predeployed before servers are started. If I start both servers simultaneously and access
http://localhost:8280/portal/portal/default/NullPortletPage then I get a 404 error with
"The requested resource () is not available". I am able to access the page if I
hit http://localhost:8180/portal/portal/default/NullPortletPage (notice the port) .
What is more interesting is that when I start servers one by one i.e. start second server
when first one has already started, then I can access the NullPortletPage in both servers.
Since there is a work around, let's fix this by 2.6.5 release.
--
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
8:22 p.m.
New subject: [JBoss JIRA] Commented: (JBPORTAL-1879) problem accessing a portlet deployed in a cluster
[ http://jira.jboss.com/jira/browse/JBPORTAL-1879?page=comments#action_1241... ]
Prabhat Jha commented on JBPORTAL-1879:
---------------------------------------
I was able to reproduce it again. I took thread dumps from both nodes in a 2-node cluster.
Clients were connected through AJP connector with mod_jk at front. Attached are the thread
dumps. The file named perf12-dump.txt contains two thread dumps taken about minute apart.
problem accessing a portlet deployed in a cluster
-------------------------------------------------
Key: JBPORTAL-1879
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1879
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal Server
Affects Versions: 2.6.4 Final
Reporter: Prabhat Jha
Assigned To: Thomas Heute
Fix For: 2.7 Final
This is something I had noticed in my scalability test but at that time I thought I may
have done something stupid and later, I saw a similar note in support case.
I have two portal servers (ports-01, ports-02) configuration where nullPortletPage.war is
predeployed before servers are started. If I start both servers simultaneously and access
http://localhost:8280/portal/portal/default/NullPortletPage then I get a 404 error with
"The requested resource () is not available". I am able to access the page if I
hit http://localhost:8180/portal/portal/default/NullPortletPage (notice the port) .
What is more interesting is that when I start servers one by one i.e. start second server
when first one has already started, then I can access the NullPortletPage in both servers.
Since there is a work around, let's fix this by 2.6.5 release.
--
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
8:29 p.m.
New subject: [JBoss JIRA] Updated: (JBPORTAL-1879) problem accessing a portlet deployed in a cluster
[ http://jira.jboss.com/jira/browse/JBPORTAL-1879?page=all ]
Prabhat Jha updated JBPORTAL-1879:
----------------------------------
Attachment: cluster-jam.zip
problem accessing a portlet deployed in a cluster
-------------------------------------------------
Key: JBPORTAL-1879
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1879
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal Server
Affects Versions: 2.6.4 Final
Reporter: Prabhat Jha
Assigned To: Thomas Heute
Fix For: 2.7 Final
Attachments: cluster-jam.zip
This is something I had noticed in my scalability test but at that time I thought I may
have done something stupid and later, I saw a similar note in support case.
I have two portal servers (ports-01, ports-02) configuration where nullPortletPage.war is
predeployed before servers are started. If I start both servers simultaneously and access
http://localhost:8280/portal/portal/default/NullPortletPage then I get a 404 error with
"The requested resource () is not available". I am able to access the page if I
hit http://localhost:8180/portal/portal/default/NullPortletPage (notice the port) .
What is more interesting is that when I start servers one by one i.e. start second server
when first one has already started, then I can access the NullPortletPage in both servers.
Since there is a work around, let's fix this by 2.6.5 release.
--
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
8:50 p.m.
New subject: [JBoss JIRA] Commented: (JBPORTAL-1879) problem accessing a portlet deployed in a cluster
[ http://jira.jboss.com/jira/browse/JBPORTAL-1879?page=comments#action_1241... ]
Prabhat Jha commented on JBPORTAL-1879:
---------------------------------------
java.lang.Object.wait(Native Method)
- waiting on <0x0000002aa5210e30> (a
org.jboss.cache.lock.ReadWriteLockWithUpgrade$WriterLock)
at
org.jboss.cache.lock.ReadWriteLockWithUpgrade$WriterLock.attempt(ReadWriteLockWithUpgrade.java:389)
- locked <0x0000002aa5210e30> (a
org.jboss.cache.lock.ReadWriteLockWithUpgrade$WriterLock)
at org.jboss.cache.lock.IdentityLock.acquireWriteLock(IdentityLock.java:199)
at org.jboss.cache.Node.acquireWriteLock(Node.java:529)
at org.jboss.cache.Node.acquire(Node.java:476)
at
org.jboss.cache.interceptors.OptimisticLockingInterceptor.lockNodes(OptimisticLockingInterceptor.java:153)
at
org.jboss.cache.interceptors.OptimisticLockingInterceptor.invoke(OptimisticLockingInterceptor.java:80)
at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
at
org.jboss.cache.interceptors.OptimisticReplicationInterceptor.invoke(OptimisticReplicationInterceptor.java:85)
at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
at
org.jboss.cache.interceptors.TxInterceptor.runPreparePhase(TxInterceptor.java:873)
at
org.jboss.cache.interceptors.TxInterceptor$LocalSynchronizationHandler.beforeCompletion(TxInterceptor.java:1156)
at
org.jboss.cache.interceptors.OrderedSynchronizationHandler.beforeCompletion(OrderedSynchronizationHandler.java:75)
at
com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.beforeCompletion(SynchronizationImple.java:114)
at
com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.beforeCompletion(TwoPhaseCoordinator.java:247)
at
com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:86)
at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:177)
at
com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1389)
at
com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:135)
at
com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:87)
at
org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterceptor.java:369)
at org.jboss.cache.interceptors.TxInterceptor.invoke(TxInterceptor.java:160)
at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
at
org.jboss.cache.interceptors.CacheMgmtInterceptor.invoke(CacheMgmtInterceptor.java:157)
at org.jboss.cache.TreeCache.invokeMethod(TreeCache.java:5877)
at org.jboss.cache.TreeCache.put(TreeCache.java:3847)
at org.jboss.cache.TreeCache.put(TreeCache.java:3521)
at org.hibernate.cache.OptimisticTreeCache.writeLoad(OptimisticTreeCache.java:84)
at org.hibernate.cache.TransactionalCache.put(TransactionalCache.java:55)
at org.hibernate.engine.TwoPhaseLoad.initializeEntity(TwoPhaseLoad.java:156)
at org.hibernate.loader.Loader.initializeEntitiesAndCollections(Loader.java:854)
at org.hibernate.loader.Loader.doQuery(Loader.java:729)
at
org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:236)
at org.hibernate.loader.Loader.loadEntity(Loader.java:1860)
at
org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:48)
at
org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:42)
at
org.hibernate.persister.entity.AbstractEntityPersister.load(AbstractEntityPersister.java:3044)
at
org.hibernate.event.def.DefaultLoadEventListener.loadFromDatasource(DefaultLoadEventListener.java:395)
at
org.hibernate.event.def.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:375)
at
org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:139)
at
org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:195)
at
org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:103)
at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:878)
at org.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:846)
at org.hibernate.type.EntityType.resolveIdentifier(EntityType.java:557)
at org.hibernate.type.EntityType.resolve(EntityType.java:379)
at org.hibernate.engine.TwoPhaseLoad.initializeEntity(TwoPhaseLoad.java:116)
at org.hibernate.loader.Loader.initializeEntitiesAndCollections(Loader.java:854)
at org.hibernate.loader.Loader.doQuery(Loader.java:729)
at
org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:236)
at org.hibernate.loader.Loader.loadEntity(Loader.java:1907)
at
org.hibernate.loader.entity.CollectionElementLoader.loadElement(CollectionElementLoader.java:72)
at
org.hibernate.persister.collection.OneToManyPersister.getElementByIndex(OneToManyPersister.java:360)
at
org.hibernate.collection.AbstractPersistentCollection.readElementByIndex(AbstractPersistentCollection.java:158)
at org.hibernate.collection.PersistentMap.get(PersistentMap.java:146)
at
org.jboss.portal.core.impl.model.portal.PortalObjectImpl.getChild(PortalObjectImpl.java:427)
at
org.jboss.portal.core.model.portal.command.mapping.DefaultPortalObjectPathMapper$1.getChild(DefaultPortalObjectPathMapper.java:91)
at org.jboss.portal.server.servlet.PathParser.map(PathParser.java:65)
at
org.jboss.portal.core.model.portal.command.mapping.DefaultPortalObjectPathMapper.getTarget(DefaultPortalObjectPathMapper.java:109)
at
org.jboss.portal.core.model.portal.PortalObjectCommandFactory.doMapping(PortalObjectCommandFactory.java:77)
at
org.jboss.portal.core.controller.command.mapper.CommandFactoryDelegate.doMapping(CommandFactoryDelegate.java:87)
at
org.jboss.portal.core.controller.command.mapper.DelegatingCommandFactoryService.doMapping(DelegatingCommandFactoryService.java:142)
at
org.jboss.portal.core.model.portal.DefaultPortalCommandFactory.doMapping(DefaultPortalCommandFactory.java:69)
at org.jboss.portal.core.controller.Controller.handle(Controller.java:208)
at
org.jboss.portal.server.RequestControllerDispatcher.invoke(RequestControllerDispatcher.java:51)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:131)
at
org.jboss.portal.core.cms.aspect.IdentityBindingInterceptor.invoke(IdentityBindingInterceptor.java:47)
at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at
org.jboss.portal.server.aspects.server.ContentTypeInterceptor.invoke(ContentTypeInterceptor.java:68)
at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at
org.jboss.portal.core.aspects.server.PortalContextPathInterceptor.invoke(PortalContextPathInterceptor.java:45)
at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at
org.jboss.portal.core.aspects.server.LocaleInterceptor.invoke(LocaleInterceptor.java:96)
at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at
org.jboss.portal.core.aspects.server.UserInterceptor.invoke(UserInterceptor.java:246)
at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at
org.jboss.portal.server.aspects.server.SignOutInterceptor.invoke(SignOutInterceptor.java:98)
at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at
org.jboss.portal.core.impl.api.user.UserEventBridgeTriggerInterceptor.invoke(UserEventBridgeTriggerInterceptor.java:65)
at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at
org.jboss.portal.core.aspects.server.TransactionInterceptor.org$jboss$portal$core$aspects$server$TransactionInterceptor$invoke$aop(TransactionInterceptor.java:49)
at
org.jboss.portal.core.aspects.server.TransactionInterceptor$invoke_N5143606530999904530.invokeNext(TransactionInterceptor$invoke_N5143606530999904530.java)
at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
at org.jboss.aspects.tx.TxInterceptor$RequiresNew.invoke(TxInterceptor.java:262)
at
org.jboss.portal.core.aspects.server.TransactionInterceptor$invoke_N5143606530999904530.invokeNext(TransactionInterceptor$invoke_N5143606530999904530.java)
at
org.jboss.portal.core.aspects.server.TransactionInterceptor.invoke(TransactionInterceptor.java)
at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at
org.jboss.portal.server.aspects.LockInterceptor.invoke(LockInterceptor.java:139)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at org.jboss.portal.common.invocation.Invocation.invoke(Invocation.java:157)
problem accessing a portlet deployed in a cluster
-------------------------------------------------
Key: JBPORTAL-1879
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1879
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal Server
Affects Versions: 2.6.4 Final
Reporter: Prabhat Jha
Assigned To: Thomas Heute
Fix For: 2.7 Final
Attachments: cluster-jam.zip
This is something I had noticed in my scalability test but at that time I thought I may
have done something stupid and later, I saw a similar note in support case.
I have two portal servers (ports-01, ports-02) configuration where nullPortletPage.war is
predeployed before servers are started. If I start both servers simultaneously and access
http://localhost:8280/portal/portal/default/NullPortletPage then I get a 404 error with
"The requested resource () is not available". I am able to access the page if I
hit http://localhost:8180/portal/portal/default/NullPortletPage (notice the port) .
What is more interesting is that when I start servers one by one i.e. start second server
when first one has already started, then I can access the NullPortletPage in both servers.
Since there is a work around, let's fix this by 2.6.5 release.
--
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
3:01 p.m.
New subject: [JBoss JIRA] Commented: (JBPORTAL-1879) problem accessing a portlet deployed in a cluster
[ http://jira.jboss.com/jira/browse/JBPORTAL-1879?page=comments#action_1241... ]
Prabhat Jha commented on JBPORTAL-1879:
---------------------------------------
I believe this only happens when optimistic locking is enabled. Running tests with
pessimistic locking did not show such behavior. Optimistic locking performs relatively
better though.
problem accessing a portlet deployed in a cluster
-------------------------------------------------
Key: JBPORTAL-1879
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1879
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal Server
Affects Versions: 2.6.4 Final
Reporter: Prabhat Jha
Assigned To: Thomas Heute
Fix For: 2.7 Final
Attachments: cluster-jam.zip
This is something I had noticed in my scalability test but at that time I thought I may
have done something stupid and later, I saw a similar note in support case.
I have two portal servers (ports-01, ports-02) configuration where nullPortletPage.war is
predeployed before servers are started. If I start both servers simultaneously and access
http://localhost:8280/portal/portal/default/NullPortletPage then I get a 404 error with
"The requested resource () is not available". I am able to access the page if I
hit http://localhost:8180/portal/portal/default/NullPortletPage (notice the port) .
What is more interesting is that when I start servers one by one i.e. start second server
when first one has already started, then I can access the NullPortletPage in both servers.
Since there is a work around, let's fix this by 2.6.5 release.
--
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
1:43 p.m.
New subject: [JBoss JIRA] Commented: (JBPORTAL-1879) problem accessing a portlet deployed in a cluster
[ http://jira.jboss.com/jira/browse/JBPORTAL-1879?page=comments#action_1241... ]
Prabhat Jha commented on JBPORTAL-1879:
---------------------------------------
Thread started in portal forum
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156792#...
problem accessing a portlet deployed in a cluster
-------------------------------------------------
Key: JBPORTAL-1879
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1879
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal Server
Affects Versions: 2.6.4 Final
Reporter: Prabhat Jha
Assigned To: Thomas Heute
Fix For: 2.7 Final
Attachments: cluster-jam.zip
This is something I had noticed in my scalability test but at that time I thought I may
have done something stupid and later, I saw a similar note in support case.
I have two portal servers (ports-01, ports-02) configuration where nullPortletPage.war is
predeployed before servers are started. If I start both servers simultaneously and access
http://localhost:8280/portal/portal/default/NullPortletPage then I get a 404 error with
"The requested resource () is not available". I am able to access the page if I
hit http://localhost:8180/portal/portal/default/NullPortletPage (notice the port) .
What is more interesting is that when I start servers one by one i.e. start second server
when first one has already started, then I can access the NullPortletPage in both servers.
Since there is a work around, let's fix this by 2.6.5 release.
--
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
1:04 p.m.
New subject: [JBoss JIRA] Commented: (JBPORTAL-1879) problem accessing a portlet deployed in a cluster
[ http://jira.jboss.com/jira/browse/JBPORTAL-1879?page=comments#action_1241... ]
Prabhat Jha commented on JBPORTAL-1879:
---------------------------------------
I just realized that I messed up during creating a zip and both files in zip are from the
same server.
problem accessing a portlet deployed in a cluster
-------------------------------------------------
Key: JBPORTAL-1879
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1879
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal Server
Affects Versions: 2.6.4 Final
Reporter: Prabhat Jha
Assigned To: Thomas Heute
Fix For: 2.7 Final
Attachments: cluster-jam.zip
This is something I had noticed in my scalability test but at that time I thought I may
have done something stupid and later, I saw a similar note in support case.
I have two portal servers (ports-01, ports-02) configuration where nullPortletPage.war is
predeployed before servers are started. If I start both servers simultaneously and access
http://localhost:8280/portal/portal/default/NullPortletPage then I get a 404 error with
"The requested resource () is not available". I am able to access the page if I
hit http://localhost:8180/portal/portal/default/NullPortletPage (notice the port) .
What is more interesting is that when I start servers one by one i.e. start second server
when first one has already started, then I can access the NullPortletPage in both servers.
Since there is a work around, let's fix this by 2.6.5 release.
--
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
1:38 p.m.
New subject: [JBoss JIRA] Commented: (JBPORTAL-1879) problem accessing a portlet deployed in a cluster
[ http://jira.jboss.com/jira/browse/JBPORTAL-1879?page=comments#action_1241... ]
Prabhat Jha commented on JBPORTAL-1879:
---------------------------------------
To take this one step ahead, I let about 5 threads hit server and as expected it hang but
I wanted to see what happens after that. After about 5 minutes, I see following in server
log:
2008-06-10 14:19:29,360 INFO [org.jboss.system.server.Server] JBoss (MX MicroKernel)
[4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)] Started in 40s:241ms
2008-06-10 14:25:14,808 ERROR
[org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/portal-core].[jsp]]
Servlet.service() for servlet jsp threw exception
java.lang.NullPointerException
at org.hibernate.engine.loading.LoadContexts.cleanup(LoadContexts.java:89)
at
org.hibernate.engine.loading.CollectionLoadContext.endLoadingCollections(CollectionLoadContext.java:203)
at org.hibernate.loader.Loader.endCollectionLoad(Loader.java:877)
at org.hibernate.loader.Loader.initializeEntitiesAndCollections(Loader.java:865)
at org.hibernate.loader.Loader.doQuery(Loader.java:729)
at
org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:236)
at org.hibernate.loader.Loader.loadEntity(Loader.java:1860)
at
org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:48)
at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:42)
at
org.hibernate.persister.entity.AbstractEntityPersister.load(AbstractEntityPersister.java:3044)
at
org.hibernate.event.def.DefaultLoadEventListener.loadFromDatasource(DefaultLoadEventListener.java:395)
at
org.hibernate.event.def.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:375)
at
org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:139)
at
org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:195)
at
org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:103)
at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:878)
at org.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:846)
at org.hibernate.type.EntityType.resolveIdentifier(EntityType.java:557)
at org.hibernate.type.EntityType.resolve(EntityType.java:379)
at org.hibernate.engine.TwoPhaseLoad.initializeEntity(TwoPhaseLoad.java:116)
at org.hibernate.loader.Loader.initializeEntitiesAndCollections(Loader.java:854)
at org.hibernate.loader.Loader.doQuery(Loader.java:729)
at
org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:236)
at org.hibernate.loader.Loader.loadCollection(Loader.java:1994)
at
org.hibernate.loader.collection.CollectionLoader.initialize(CollectionLoader.java:36)
at
org.hibernate.persister.collection.AbstractCollectionPersister.initialize(AbstractCollectionPersister.java:565)
at
org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:60)
at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1716)
at
org.hibernate.collection.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:344)
at
org.hibernate.collection.AbstractPersistentCollection.read(AbstractPersistentCollection.java:86)
at org.hibernate.collection.PersistentMap.entrySet(PersistentMap.java:242)
at java.util.AbstractMap.putAll(AbstractMap.java:314)
at java.util.TreeMap.putAll(TreeMap.java:328)
at java.util.TreeMap.<init>(TreeMap.java:156)
at
org.jboss.portal.core.impl.model.portal.PortalObjectImpl$ChildrenCollection$ChildrenIterator.<init>(PortalObjectImpl.java:320)
at
org.jboss.portal.core.impl.model.portal.PortalObjectImpl$ChildrenCollection.iterator(PortalObjectImpl.java:284)
at
org.jboss.portal.core.impl.api.node.PortalNodeImpl$NodeList.buildChildMap(PortalNodeImpl.java:379)
at
org.jboss.portal.core.impl.api.node.PortalNodeImpl$Siblings.createMap(PortalNodeImpl.java:440)
at
org.jboss.portal.core.impl.api.node.PortalNodeImpl$NodeList.getMap(PortalNodeImpl.java:355)
at
org.jboss.portal.core.impl.api.node.PortalNodeImpl$NodeList.getList(PortalNodeImpl.java:339)
at
org.jboss.portal.core.impl.api.node.PortalNodeImpl.getChildren(PortalNodeImpl.java:228)
at org.apache.jsp.WEB_002dINF.jsp.header.tabs_jsp._jspService(tabs_jsp.java:90)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373)
I also see
2008-06-10 14:25:14,827 ERROR [org.jboss.portal.security.PortalPermissionCollection]
Permission check against the repository failed
org.hibernate.HibernateException: Current transaction is not in progress
at
org.hibernate.context.JTASessionContext.currentSession(JTASessionContext.java:67)
at
org.hibernate.impl.SessionFactoryImpl.getCurrentSession(SessionFactoryImpl.java:544)
at
org.jboss.portal.core.impl.model.portal.PersistentPortalObjectContainer.getObjectNode(PersistentPortalObjectContainer.java:252)
at
org.jboss.portal.core.impl.model.portal.AbstractPortalObjectContainer.getPermission(AbstractPortalObjectContainer.java:166)
at
org.jboss.portal.core.model.portal.PortalObjectPermission.implies(PortalObjectPermission.java:227)
at
org.jboss.portal.security.PortalPermissionCollection.implies(PortalPermissionCollection.java:96)
at org.jboss.portal.security.impl.jacc.Permissions.implies(Permissions.java:93)
at
org.jboss.portal.security.impl.jacc.SecurityContext.implies(SecurityContext.java:81)
at
org.jboss.portal.security.impl.jacc.JACCPortalAuthorizationManager.internalCheckPermission(JACCPortalAuthorizationManager.java:272)
at
org.jboss.portal.security.impl.jacc.JACCPortalAuthorizationManager.checkPermission(JACCPortalAuthorizationManager.java:301)
at
org.jboss.portal.security.impl.jacc.JACCPortalAuthorizationManager.checkPermission(JACCPortalAuthorizationManager.java:326)
at
org.jboss.portal.core.aspects.controller.PageCustomizerInterceptor.injectDashboardNav(PageCustomizerInterceptor.java:287)
at
org.jboss.portal.core.aspects.controller.PageCustomizerInterceptor.invoke(PageCustomizerInterceptor.java:164)
at
org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at
org.jboss.portal.core.aspects.controller.PolicyEnforcementInterceptor.invoke(PolicyEnforcementInterceptor.java:78)
at
org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at
org.jboss.portal.core.aspects.controller.node.PortalNodeInterceptor.invoke(PortalNodeInterceptor.java:81)
at
org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at
org.jboss.portal.core.aspects.controller.NavigationalStateInterceptor.invoke(NavigationalStateInterceptor.java:42)
at
org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at
org.jboss.portal.core.controller.ajax.AjaxInterceptor.invoke(AjaxInterceptor.java:56)
at
org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at
org.jboss.portal.core.aspects.controller.ResourceAcquisitionInterceptor.invoke(ResourceAcquisitionInterceptor.java:50)
at
org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at org.jboss.portal.common.invocation.Invocation.invoke(Invocation.java:157)
problem accessing a portlet deployed in a cluster
-------------------------------------------------
Key: JBPORTAL-1879
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1879
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal Server
Affects Versions: 2.6.4 Final
Reporter: Prabhat Jha
Assigned To: Thomas Heute
Fix For: 2.7 Final
Attachments: cluster-jam.zip
This is something I had noticed in my scalability test but at that time I thought I may
have done something stupid and later, I saw a similar note in support case.
I have two portal servers (ports-01, ports-02) configuration where nullPortletPage.war is
predeployed before servers are started. If I start both servers simultaneously and access
http://localhost:8280/portal/portal/default/NullPortletPage then I get a 404 error with
"The requested resource () is not available". I am able to access the page if I
hit http://localhost:8180/portal/portal/default/NullPortletPage (notice the port) .
What is more interesting is that when I start servers one by one i.e. start second server
when first one has already started, then I can access the NullPortletPage in both servers.
Since there is a work around, let's fix this by 2.6.5 release.
--
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
10:41 a.m.
New subject: [JBoss JIRA] Commented: (JBPORTAL-1879) problem accessing a portlet deployed in a cluster
[ http://jira.jboss.com/jira/browse/JBPORTAL-1879?page=comments#action_1241... ]
Prabhat Jha commented on JBPORTAL-1879:
---------------------------------------
Ran with debug on for org.jboss.cache package and I see
2008-06-11 11:22:22,869 DEBUG [org.jboss.cache.interceptors.OptimisticLockingInterceptor]
Caught exception attempting to lock nodes
org.jboss.cache.lock.TimeoutException: failure acquiring lock: fqn=/,
caller=GlobalTransaction:<10.18.1.130:34605>:26, lock=write
owner=GlobalTransaction:<10.18.1.130:34605>:8 (activeReaders=0,
activeWriter=Thread[ajp-10.18.1.130-8009-30,5,jboss], waitingReaders=0, waitingWriters=46,
waitingUpgrader=0)
at org.jboss.cache.Node.acquire(Node.java:500)
at
org.jboss.cache.interceptors.OptimisticLockingInterceptor.lockNodes(OptimisticLockingInterceptor.java:153)
at
org.jboss.cache.interceptors.OptimisticLockingInterceptor.invoke(OptimisticLockingInterceptor.java:80)
at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
at
org.jboss.cache.interceptors.DataGravitatorInterceptor.invoke(DataGravitatorInterceptor.java:137)
at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
at
org.jboss.cache.interceptors.OptimisticReplicationInterceptor.invoke(OptimisticReplicationInterceptor.java:85)
at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68) at
org.jboss.cache.interceptors.OrderedSynchronizationHandler.beforeCompletion(OrderedSynchronizationHandler.java:75)
at
com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.beforeCompletion(SynchronizationImple.java:114)
at
com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.beforeCompletion(TwoPhaseCoordinator.java:247)
at
com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:86)
at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:177)
at
com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1389)
at
com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:135)
at
com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:87)
at
org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterceptor.java:369)
at org.jboss.cache.interceptors.TxInterceptor.invoke(TxInterceptor.java:160)
at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
at
org.jboss.cache.interceptors.CacheMgmtInterceptor.invoke(CacheMgmtInterceptor.java:157)
at org.jboss.cache.TreeCache.invokeMethod(TreeCache.java:5877)
at org.jboss.cache.TreeCache.put(TreeCache.java:3847)
at org.jboss.cache.TreeCache.put(TreeCache.java:3521)
at org.hibernate.cache.OptimisticTreeCache.writeLoad(OptimisticTreeCache.java:84)
at org.hibernate.cache.TransactionalCache.put(TransactionalCache.java:55)
at
org.jboss.cache.interceptors.TxInterceptor.runPreparePhase(TxInterceptor.java:873)
at
org.jboss.cache.interceptors.TxInterceptor$LocalSynchronizationHandler.beforeCompletion(TxInterceptor.java:1156)
at
org.jboss.cache.interceptors.OrderedSynchronizationHandler.beforeCompletion(OrderedSynchronizationHandler.java:75)
at
com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.beforeCompletion(SynchronizationImple.java:114)
at
com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.beforeCompletion(TwoPhaseCoordinator.java:247)
at
com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:86)
at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:177)
at
com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1389)
at
com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:135)
at
com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:87)
at
org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterceptor.java:369)
at org.jboss.cache.interceptors.TxInterceptor.invoke(TxInterceptor.java:160)
at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
at
org.jboss.cache.interceptors.CacheMgmtInterceptor.invoke(CacheMgmtInterceptor.java:157)
at org.jboss.cache.TreeCache.invokeMethod(TreeCache.java:5877)
at org.jboss.cache.TreeCache.put(TreeCache.java:3847)
at org.jboss.cache.TreeCache.put(TreeCache.java:3521)
at org.hibernate.cache.OptimisticTreeCache.writeLoad(OptimisticTreeCache.java:84)
at org.hibernate.cache.TransactionalCache.put(TransactionalCache.java:55)
at org.hibernate.engine.TwoPhaseLoad.initializeEntity(TwoPhaseLoad.java:156)
at org.hibernate.loader.Loader.initializeEntitiesAndCollections(Loader.java:854)
at org.hibernate.loader.Loader.doQuery(Loader.java:729)
at
org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:236)
at org.hibernate.loader.Loader.loadEntity(Loader.java:1860)
at
org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:48)
at
org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:42)
at
org.hibernate.persister.entity.AbstractEntityPersister.load(AbstractEntityPersister.java:3044)
at
org.hibernate.event.def.DefaultLoadEventListener.loadFromDatasource(DefaultLoadEventListener.java:395)
at
org.hibernate.event.def.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:375)
at
org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:139)
at
org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:195)
at
org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:103)
at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:878)
at org.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:846)
at org.hibernate.type.EntityType.resolveIdentifier(EntityType.java:557)
at org.hibernate.type.EntityType.resolve(EntityType.java:379)
at org.hibernate.engine.TwoPhaseLoad.initializeEntity(TwoPhaseLoad.java:116)
at org.hibernate.loader.Loader.initializeEntitiesAndCollections(Loader.java:854)
at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:236)
at org.hibernate.loader.Loader.doList(Loader.java:2220)
at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2104)
at org.hibernate.loader.Loader.list(Loader.java:2099)
at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:378)
at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:338)
at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:172)
at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1121)
at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79)
at org.hibernate.impl.AbstractQueryImpl.uniqueResult(AbstractQueryImpl.java:811)
at
org.jboss.portal.core.impl.model.portal.PersistentPortalObjectContainer.getObjectNodeNoCache(PersistentPortalObjectContainer.java:274)
problem accessing a portlet deployed in a cluster
-------------------------------------------------
Key: JBPORTAL-1879
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1879
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal Server
Affects Versions: 2.6.4 Final
Reporter: Prabhat Jha
Assigned To: Thomas Heute
Fix For: 2.7 Final
Attachments: cluster-jam.zip
This is something I had noticed in my scalability test but at that time I thought I may
have done something stupid and later, I saw a similar note in support case.
I have two portal servers (ports-01, ports-02) configuration where nullPortletPage.war is
predeployed before servers are started. If I start both servers simultaneously and access
http://localhost:8280/portal/portal/default/NullPortletPage then I get a 404 error with
"The requested resource () is not available". I am able to access the page if I
hit http://localhost:8180/portal/portal/default/NullPortletPage (notice the port) .
What is more interesting is that when I start servers one by one i.e. start second server
when first one has already started, then I can access the NullPortletPage in both servers.
Since there is a work around, let's fix this by 2.6.5 release.
--
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
12:04 p.m.
New subject: [JBoss JIRA] Commented: (JBPORTAL-1879) problem accessing a portlet deployed in a cluster
[ http://jira.jboss.com/jira/browse/JBPORTAL-1879?page=comments#action_1241... ]
Prabhat Jha commented on JBPORTAL-1879:
---------------------------------------
More information does not hurt :-) Optimistic locking with cache mode set to REPL_ASYNC
or LOCAL, does not result into this problem. Only when using REPL_SYNC as cache mode, I
see this problem.
problem accessing a portlet deployed in a cluster
-------------------------------------------------
Key: JBPORTAL-1879
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1879
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal Server
Affects Versions: 2.6.4 Final
Reporter: Prabhat Jha
Assigned To: Thomas Heute
Fix For: 2.7 Final
Attachments: cluster-jam.zip
This is something I had noticed in my scalability test but at that time I thought I may
have done something stupid and later, I saw a similar note in support case.
I have two portal servers (ports-01, ports-02) configuration where nullPortletPage.war is
predeployed before servers are started. If I start both servers simultaneously and access
http://localhost:8280/portal/portal/default/NullPortletPage then I get a 404 error with
"The requested resource () is not available". I am able to access the page if I
hit http://localhost:8180/portal/portal/default/NullPortletPage (notice the port) .
What is more interesting is that when I start servers one by one i.e. start second server
when first one has already started, then I can access the NullPortletPage in both servers.
Since there is a work around, let's fix this by 2.6.5 release.
--
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
12:08 p.m.
New subject: [JBoss JIRA] Updated: (JBPORTAL-1879) problem accessing a portlet deployed in a cluster
[ http://jira.jboss.com/jira/browse/JBPORTAL-1879?page=all ]
Prabhat Jha updated JBPORTAL-1879:
----------------------------------
Description:
This is something I had noticed in my scalability test but at that time I thought I may
have done something stupid and later, I saw a similar note in support case.
I have two portal servers (ports-01, ports-02) configuration where nullPortletPage.war is
predeployed before servers are started. If I start both servers simultaneously and access
http://localhost:8280/portal/portal/default/NullPortletPage then I get a 404 error with
"The requested resource () is not available". I am able to access the page if I
hit http://localhost:8180/portal/portal/default/NullPortletPage (notice the port) .
What is more interesting is that when I start servers one by one and access portal page as
server comes online i.e. start second server when first one has already started and page
has been accessed, then I can access the NullPortletPage in both servers. Since there is a
work around, let's fix this by 2.6.5 release.
was:
This is something I had noticed in my scalability test but at that time I thought I may
have done something stupid and later, I saw a similar note in support case.
I have two portal servers (ports-01, ports-02) configuration where nullPortletPage.war is
predeployed before servers are started. If I start both servers simultaneously and access
http://localhost:8280/portal/portal/default/NullPortletPage then I get a 404 error with
"The requested resource () is not available". I am able to access the page if I
hit http://localhost:8180/portal/portal/default/NullPortletPage (notice the port) .
What is more interesting is that when I start servers one by one i.e. start second server
when first one has already started, then I can access the NullPortletPage in both servers.
Since there is a work around, let's fix this by 2.6.5 release.
problem accessing a portlet deployed in a cluster
-------------------------------------------------
Key: JBPORTAL-1879
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1879
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal Server
Affects Versions: 2.6.4 Final
Reporter: Prabhat Jha
Assigned To: Thomas Heute
Fix For: 2.7 Final
Attachments: cluster-jam.zip
This is something I had noticed in my scalability test but at that time I thought I may
have done something stupid and later, I saw a similar note in support case.
I have two portal servers (ports-01, ports-02) configuration where nullPortletPage.war is
predeployed before servers are started. If I start both servers simultaneously and access
http://localhost:8280/portal/portal/default/NullPortletPage then I get a 404 error with
"The requested resource () is not available". I am able to access the page if I
hit http://localhost:8180/portal/portal/default/NullPortletPage (notice the port) .
What is more interesting is that when I start servers one by one and access portal page
as server comes online i.e. start second server when first one has already started and
page has been accessed, then I can access the NullPortletPage in both servers. Since there
is a work around, let's fix this by 2.6.5 release.
--
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
10:12 a.m.
New subject: [JBoss JIRA] Updated: (JBPORTAL-1879) problem accessing a portlet deployed in a cluster
[ http://jira.jboss.com/jira/browse/JBPORTAL-1879?page=all ]
Prabhat Jha updated JBPORTAL-1879:
----------------------------------
Environment:
Hibernate Version: 3.2.4.sp1
JBoss Cache Version: 1.4.1.SP5
JBoss AS: 4.2.2.GA
problem accessing a portlet deployed in a cluster
-------------------------------------------------
Key: JBPORTAL-1879
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1879
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal Server
Affects Versions: 2.6.4 Final
Environment: Hibernate Version: 3.2.4.sp1
JBoss Cache Version: 1.4.1.SP5
JBoss AS: 4.2.2.GA
Reporter: Prabhat Jha
Assigned To: Thomas Heute
Fix For: 2.7 Final
Attachments: cluster-jam.zip
This is something I had noticed in my scalability test but at that time I thought I may
have done something stupid and later, I saw a similar note in support case.
I have two portal servers (ports-01, ports-02) configuration where nullPortletPage.war is
predeployed before servers are started. If I start both servers simultaneously and access
http://localhost:8280/portal/portal/default/NullPortletPage then I get a 404 error with
"The requested resource () is not available". I am able to access the page if I
hit http://localhost:8180/portal/portal/default/NullPortletPage (notice the port) .
What is more interesting is that when I start servers one by one and access portal page
as server comes online i.e. start second server when first one has already started and
page has been accessed, then I can access the NullPortletPage in both servers. Since there
is a work around, let's fix this by 2.6.5 release.
--
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
10:46 a.m.
New subject: [JBoss JIRA] Assigned: (JBPORTAL-1879) problem accessing a portlet deployed in a cluster
[ http://jira.jboss.com/jira/browse/JBPORTAL-1879?page=all ]
Prabhat Jha reassigned JBPORTAL-1879:
-------------------------------------
Assignee: Prabhat Jha (was: Thomas Heute)
problem accessing a portlet deployed in a cluster
-------------------------------------------------
Key: JBPORTAL-1879
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1879
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal Server
Affects Versions: 2.6.4 Final
Environment: Hibernate Version: 3.2.4.sp1
JBoss Cache Version: 1.4.1.SP5
JBoss AS: 4.2.2.GA
Reporter: Prabhat Jha
Assigned To: Prabhat Jha
Fix For: 2.7 Final
Attachments: cluster-jam.zip
This is something I had noticed in my scalability test but at that time I thought I may
have done something stupid and later, I saw a similar note in support case.
I have two portal servers (ports-01, ports-02) configuration where nullPortletPage.war is
predeployed before servers are started. If I start both servers simultaneously and access
http://localhost:8280/portal/portal/default/NullPortletPage then I get a 404 error with
"The requested resource () is not available". I am able to access the page if I
hit http://localhost:8180/portal/portal/default/NullPortletPage (notice the port) .
What is more interesting is that when I start servers one by one and access portal page
as server comes online i.e. start second server when first one has already started and
page has been accessed, then I can access the NullPortletPage in both servers. Since there
is a work around, let's fix this by 2.6.5 release.
--
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
6:23 a.m.
New subject: [JBoss JIRA] Updated: (JBPORTAL-1879) problem accessing a portlet deployed in a cluster
[ http://jira.jboss.com/jira/browse/JBPORTAL-1879?page=all ]
Galder Zamarreno updated JBPORTAL-1879:
---------------------------------------
JBoss Forum Reference:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156792#...
There's a field for this :)
problem accessing a portlet deployed in a cluster
-------------------------------------------------
Key: JBPORTAL-1879
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1879
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal Server
Affects Versions: 2.6.4 Final
Environment: Hibernate Version: 3.2.4.sp1
JBoss Cache Version: 1.4.1.SP5
JBoss AS: 4.2.2.GA
Reporter: Prabhat Jha
Assigned To: Prabhat Jha
Fix For: 2.7 Final
Attachments: cluster-jam.zip
This is something I had noticed in my scalability test but at that time I thought I may
have done something stupid and later, I saw a similar note in support case.
I have two portal servers (ports-01, ports-02) configuration where nullPortletPage.war is
predeployed before servers are started. If I start both servers simultaneously and access
http://localhost:8280/portal/portal/default/NullPortletPage then I get a 404 error with
"The requested resource () is not available". I am able to access the page if I
hit http://localhost:8180/portal/portal/default/NullPortletPage (notice the port) .
What is more interesting is that when I start servers one by one and access portal page
as server comes online i.e. start second server when first one has already started and
page has been accessed, then I can access the NullPortletPage in both servers. Since there
is a work around, let's fix this by 2.6.5 release.
--
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
7:40 p.m.
New subject: [JBoss JIRA] Commented: (JBPORTAL-1879) problem accessing a portlet deployed in a cluster
[ http://jira.jboss.com/jira/browse/JBPORTAL-1879?page=comments#action_1241... ]
Prabhat Jha commented on JBPORTAL-1879:
---------------------------------------
Details at the forum. Resolution is to update cache version. jboss cache version 1.4.1.SP8
(http://repository.jboss.com/jboss/cache/1.4.1.SP8.patch02-brew
problem accessing a portlet deployed in a cluster
-------------------------------------------------
Key: JBPORTAL-1879
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1879
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal Server
Affects Versions: 2.6.4 Final
Environment: Hibernate Version: 3.2.4.sp1
JBoss Cache Version: 1.4.1.SP5
JBoss AS: 4.2.2.GA
Reporter: Prabhat Jha
Assigned To: Prabhat Jha
Fix For: 2.7 Final
Attachments: cluster-jam.zip
This is something I had noticed in my scalability test but at that time I thought I may
have done something stupid and later, I saw a similar note in support case.
I have two portal servers (ports-01, ports-02) configuration where nullPortletPage.war is
predeployed before servers are started. If I start both servers simultaneously and access
http://localhost:8280/portal/portal/default/NullPortletPage then I get a 404 error with
"The requested resource () is not available". I am able to access the page if I
hit http://localhost:8180/portal/portal/default/NullPortletPage (notice the port) .
What is more interesting is that when I start servers one by one and access portal page
as server comes online i.e. start second server when first one has already started and
page has been accessed, then I can access the NullPortletPage in both servers. Since there
is a work around, let's fix this by 2.6.5 release.
--
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
3:55 p.m.
New subject: [JBoss JIRA] Updated: (JBPORTAL-1879) problem accessing a portlet deployed in a cluster
[ http://jira.jboss.com/jira/browse/JBPORTAL-1879?page=all ]
Attachment: jboss-service.xml
problem accessing a portlet deployed in a cluster
-------------------------------------------------
Key: JBPORTAL-1879
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1879
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal Server
Affects Versions: 2.6.4 Final
Environment: Hibernate Version: 3.2.4.sp1
JBoss Cache Version: 1.4.1.SP5
JBoss AS: 4.2.2.GA
Reporter: Prabhat Jha
Assigned To: Prabhat Jha
Fix For: 2.7 Final
Attachments: cluster-jam.zip, jboss-service.xml
This is something I had noticed in my scalability test but at that time I thought I may
have done something stupid and later, I saw a similar note in support case.
I have two portal servers (ports-01, ports-02) configuration where nullPortletPage.war is
predeployed before servers are started. If I start both servers simultaneously and access
http://localhost:8280/portal/portal/default/NullPortletPage then I get a 404 error with
"The requested resource () is not available". I am able to access the page if I
hit http://localhost:8180/portal/portal/default/NullPortletPage (notice the port) .
What is more interesting is that when I start servers one by one and access portal page
as server comes online i.e. start second server when first one has already started and
page has been accessed, then I can access the NullPortletPage in both servers. Since there
is a work around, let's fix this by 2.6.5 release.
--
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
5:02 p.m.
New subject: [JBoss JIRA] Updated: (JBPORTAL-1879) problem accessing a portlet deployed in a cluster
[ http://jira.jboss.com/jira/browse/JBPORTAL-1879?page=all ]
Prabhat Jha updated JBPORTAL-1879:
----------------------------------
Attachment: (was: cluster-jam.zip)
problem accessing a portlet deployed in a cluster
-------------------------------------------------
Key: JBPORTAL-1879
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1879
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal Server
Affects Versions: 2.6.4 Final
Environment: Hibernate Version: 3.2.4.sp1
JBoss Cache Version: 1.4.1.SP5
JBoss AS: 4.2.2.GA
Reporter: Prabhat Jha
Assigned To: Prabhat Jha
Fix For: 2.7 Final
Attachments: jboss-service.xml, perf11-thread-dump-1.log
This is something I had noticed in my scalability test but at that time I thought I may
have done something stupid and later, I saw a similar note in support case.
I have two portal servers (ports-01, ports-02) configuration where nullPortletPage.war is
predeployed before servers are started. If I start both servers simultaneously and access
http://localhost:8280/portal/portal/default/NullPortletPage then I get a 404 error with
"The requested resource () is not available". I am able to access the page if I
hit http://localhost:8180/portal/portal/default/NullPortletPage (notice the port) .
What is more interesting is that when I start servers one by one and access portal page
as server comes online i.e. start second server when first one has already started and
page has been accessed, then I can access the NullPortletPage in both servers. Since there
is a work around, let's fix this by 2.6.5 release.
--
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
5:02 p.m.
New subject: [JBoss JIRA] Updated: (JBPORTAL-1879) problem accessing a portlet deployed in a cluster
[ http://jira.jboss.com/jira/browse/JBPORTAL-1879?page=all ]
Prabhat Jha updated JBPORTAL-1879:
----------------------------------
Attachment: perf11-thread-dump-1.log
Attaching thread dumps from two nodes running eap43_CP01
problem accessing a portlet deployed in a cluster
-------------------------------------------------
Key: JBPORTAL-1879
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1879
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal Server
Affects Versions: 2.6.4 Final
Environment: Hibernate Version: 3.2.4.sp1
JBoss Cache Version: 1.4.1.SP5
JBoss AS: 4.2.2.GA
Reporter: Prabhat Jha
Assigned To: Prabhat Jha
Fix For: 2.7 Final
Attachments: jboss-service.xml, perf11-thread-dump-1.log
This is something I had noticed in my scalability test but at that time I thought I may
have done something stupid and later, I saw a similar note in support case.
I have two portal servers (ports-01, ports-02) configuration where nullPortletPage.war is
predeployed before servers are started. If I start both servers simultaneously and access
http://localhost:8280/portal/portal/default/NullPortletPage then I get a 404 error with
"The requested resource () is not available". I am able to access the page if I
hit http://localhost:8180/portal/portal/default/NullPortletPage (notice the port) .
What is more interesting is that when I start servers one by one and access portal page
as server comes online i.e. start second server when first one has already started and
page has been accessed, then I can access the NullPortletPage in both servers. Since there
is a work around, let's fix this by 2.6.5 release.
--
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
5:04 p.m.
New subject: [JBoss JIRA] Updated: (JBPORTAL-1879) problem accessing a portlet deployed in a cluster
[ http://jira.jboss.com/jira/browse/JBPORTAL-1879?page=all ]
Prabhat Jha updated JBPORTAL-1879:
----------------------------------
Attachment: perf12-thread-dump-1.log
problem accessing a portlet deployed in a cluster
-------------------------------------------------
Key: JBPORTAL-1879
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1879
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal Server
Affects Versions: 2.6.4 Final
Environment: Hibernate Version: 3.2.4.sp1
JBoss Cache Version: 1.4.1.SP5
JBoss AS: 4.2.2.GA
Reporter: Prabhat Jha
Assigned To: Prabhat Jha
Fix For: 2.7 Final
Attachments: jboss-service.xml, perf11-thread-dump-1.log,
perf12-thread-dump-1.log
This is something I had noticed in my scalability test but at that time I thought I may
have done something stupid and later, I saw a similar note in support case.
I have two portal servers (ports-01, ports-02) configuration where nullPortletPage.war is
predeployed before servers are started. If I start both servers simultaneously and access
http://localhost:8280/portal/portal/default/NullPortletPage then I get a 404 error with
"The requested resource () is not available". I am able to access the page if I
hit http://localhost:8180/portal/portal/default/NullPortletPage (notice the port) .
What is more interesting is that when I start servers one by one and access portal page
as server comes online i.e. start second server when first one has already started and
page has been accessed, then I can access the NullPortletPage in both servers. Since there
is a work around, let's fix this by 2.6.5 release.
--
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
2:58 p.m.
New subject: [JBoss JIRA] Commented: (JBPORTAL-1879) problem accessing a portlet deployed in a cluster
[ http://jira.jboss.com/jira/browse/JBPORTAL-1879?page=comments#action_1241... ]
Prabhat Jha commented on JBPORTAL-1879:
---------------------------------------
So, even upgrading jboss cache version does not solve the problem completely. See related
forum thread. We will decide on tomorrow's call what default configuration we should
ship.
problem accessing a portlet deployed in a cluster
-------------------------------------------------
Key: JBPORTAL-1879
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1879
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal Server
Affects Versions: 2.6.4 Final
Environment: Hibernate Version: 3.2.4.sp1
JBoss Cache Version: 1.4.1.SP5
JBoss AS: 4.2.2.GA
Reporter: Prabhat Jha
Assigned To: Prabhat Jha
Fix For: 2.7 Final
Attachments: jboss-service.xml, perf11-thread-dump-1.log,
perf12-thread-dump-1.log
This is something I had noticed in my scalability test but at that time I thought I may
have done something stupid and later, I saw a similar note in support case.
I have two portal servers (ports-01, ports-02) configuration where nullPortletPage.war is
predeployed before servers are started. If I start both servers simultaneously and access
http://localhost:8280/portal/portal/default/NullPortletPage then I get a 404 error with
"The requested resource () is not available". I am able to access the page if I
hit http://localhost:8180/portal/portal/default/NullPortletPage (notice the port) .
What is more interesting is that when I start servers one by one and access portal page
as server comes online i.e. start second server when first one has already started and
page has been accessed, then I can access the NullPortletPage in both servers. Since there
is a work around, let's fix this by 2.6.5 release.
--
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
2:05 p.m.
New subject: [JBoss JIRA] Updated: (JBPORTAL-1879) problem accessing a portlet deployed in a cluster
[ http://jira.jboss.com/jira/browse/JBPORTAL-1879?page=all ]
Thomas Heute updated JBPORTAL-1879:
-----------------------------------
Fix Version/s: 2.7.0 Beta1
(was: 2.7.0 Alpha1)
problem accessing a portlet deployed in a cluster
-------------------------------------------------
Key: JBPORTAL-1879
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1879
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal Server
Affects Versions: 2.6.4 Final
Environment: Hibernate Version: 3.2.4.sp1
JBoss Cache Version: 1.4.1.SP5
JBoss AS: 4.2.2.GA
Reporter: Prabhat Jha
Assigned To: Prabhat Jha
Fix For: 2.7.0 Beta1
Attachments: jboss-service.xml, perf11-thread-dump-1.log,
perf12-thread-dump-1.log
This is something I had noticed in my scalability test but at that time I thought I may
have done something stupid and later, I saw a similar note in support case.
I have two portal servers (ports-01, ports-02) configuration where nullPortletPage.war is
predeployed before servers are started. If I start both servers simultaneously and access
http://localhost:8280/portal/portal/default/NullPortletPage then I get a 404 error with
"The requested resource () is not available". I am able to access the page if I
hit http://localhost:8180/portal/portal/default/NullPortletPage (notice the port) .
What is more interesting is that when I start servers one by one and access portal page
as server comes online i.e. start second server when first one has already started and
page has been accessed, then I can access the NullPortletPage in both servers. Since there
is a work around, let's fix this by 2.6.5 release.
--
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
9:47 a.m.
New subject: [JBoss JIRA] Commented: (JBPORTAL-1879) problem accessing a portlet deployed in a cluster
[ http://jira.jboss.com/jira/browse/JBPORTAL-1879?page=comments#action_1242... ]
Prabhat Jha commented on JBPORTAL-1879:
---------------------------------------
Default configuration is pessimistic locking until JBCLUSTER-206 is resolved.
problem accessing a portlet deployed in a cluster
-------------------------------------------------
Key: JBPORTAL-1879
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1879
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal Server
Affects Versions: 2.6.4 Final
Environment: Hibernate Version: 3.2.4.sp1
JBoss Cache Version: 1.4.1.SP5
JBoss AS: 4.2.2.GA
Reporter: Prabhat Jha
Assigned To: Prabhat Jha
Fix For: 2.7.0 Beta1
Attachments: jboss-service.xml, perf11-thread-dump-1.log,
perf12-thread-dump-1.log
This is something I had noticed in my scalability test but at that time I thought I may
have done something stupid and later, I saw a similar note in support case.
I have two portal servers (ports-01, ports-02) configuration where nullPortletPage.war is
predeployed before servers are started. If I start both servers simultaneously and access
http://localhost:8280/portal/portal/default/NullPortletPage then I get a 404 error with
"The requested resource () is not available". I am able to access the page if I
hit http://localhost:8180/portal/portal/default/NullPortletPage (notice the port) .
What is more interesting is that when I start servers one by one and access portal page
as server comes online i.e. start second server when first one has already started and
page has been accessed, then I can access the NullPortletPage in both servers. Since there
is a work around, let's fix this by 2.6.5 release.
--
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
4:11 p.m.
New subject: [JBoss JIRA] Updated: (JBPORTAL-1879) problem accessing a portlet deployed in a cluster
[
https://jira.jboss.org/jira/browse/JBPORTAL-1879?page=com.atlassian.jira....
]
Thomas Heute updated JBPORTAL-1879:
-----------------------------------
Fix Version/s: 2.7.0 CR1
(was: 2.7.0 Beta1)
problem accessing a portlet deployed in a cluster
-------------------------------------------------
Key: JBPORTAL-1879
URL: https://jira.jboss.org/jira/browse/JBPORTAL-1879
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal Server
Affects Versions: 2.6.4 Final
Environment: Hibernate Version: 3.2.4.sp1
JBoss Cache Version: 1.4.1.SP5
JBoss AS: 4.2.2.GA
Reporter: Prabhat Jha
Assignee: Prabhat Jha
Fix For: 2.7.0 CR1
Attachments: jboss-service.xml, perf11-thread-dump-1.log,
perf12-thread-dump-1.log
This is something I had noticed in my scalability test but at that time I thought I may
have done something stupid and later, I saw a similar note in support case.
I have two portal servers (ports-01, ports-02) configuration where nullPortletPage.war is
predeployed before servers are started. If I start both servers simultaneously and access
http://localhost:8280/portal/portal/default/NullPortletPage then I get a 404 error with
"The requested resource () is not available". I am able to access the page if I
hit http://localhost:8180/portal/portal/default/NullPortletPage (notice the port) .
What is more interesting is that when I start servers one by one and access portal page
as server comes online i.e. start second server when first one has already started and
page has been accessed, then I can access the NullPortletPage in both servers. Since there
is a work around, let's fix this by 2.6.5 release.
--
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
2:46 p.m.
New subject: [JBoss JIRA] Updated: (JBPORTAL-1879) problem accessing a portlet deployed in a cluster
[
https://jira.jboss.org/jira/browse/JBPORTAL-1879?page=com.atlassian.jira....
]
Prabhat Jha updated JBPORTAL-1879:
----------------------------------
Attachment: 5-server-dumps.zip
Attaching thread dumps from all 5 nodes in 5-node cluster. I took three thread dumps on
each sever.
problem accessing a portlet deployed in a cluster
-------------------------------------------------
Key: JBPORTAL-1879
URL: https://jira.jboss.org/jira/browse/JBPORTAL-1879
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal Server
Affects Versions: 2.6.4 Final
Environment: Hibernate Version: 3.2.4.sp1
JBoss Cache Version: 1.4.1.SP5
JBoss AS: 4.2.2.GA
Reporter: Prabhat Jha
Assignee: Prabhat Jha
Fix For: 2.7.0 CR1
Attachments: 5-server-dumps.zip, jboss-service.xml, perf11-thread-dump-1.log,
perf12-thread-dump-1.log
This is something I had noticed in my scalability test but at that time I thought I may
have done something stupid and later, I saw a similar note in support case.
I have two portal servers (ports-01, ports-02) configuration where nullPortletPage.war is
predeployed before servers are started. If I start both servers simultaneously and access
http://localhost:8280/portal/portal/default/NullPortletPage then I get a 404 error with
"The requested resource () is not available". I am able to access the page if I
hit http://localhost:8180/portal/portal/default/NullPortletPage (notice the port) .
What is more interesting is that when I start servers one by one and access portal page
as server comes online i.e. start second server when first one has already started and
page has been accessed, then I can access the NullPortletPage in both servers. Since there
is a work around, let's fix this by 2.6.5 release.
--
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
1:07 p.m.
New subject: [JBoss JIRA] Resolved: (JBPORTAL-1879) problem accessing a portlet deployed in a cluster
[
https://jira.jboss.org/jira/browse/JBPORTAL-1879?page=com.atlassian.jira....
]
Prabhat Jha resolved JBPORTAL-1879.
-----------------------------------
Fix Version/s: 2.6.7 Final
Resolution: Done
problem accessing a portlet deployed in a cluster
-------------------------------------------------
Key: JBPORTAL-1879
URL: https://jira.jboss.org/jira/browse/JBPORTAL-1879
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal Server
Affects Versions: 2.6.4 Final
Environment: Hibernate Version: 3.2.4.sp1
JBoss Cache Version: 1.4.1.SP5
JBoss AS: 4.2.2.GA
Reporter: Prabhat Jha
Assignee: Prabhat Jha
Fix For: 2.7.0 CR1 , 2.6.7 Final
Attachments: 5-server-dumps.zip, jboss-service.xml, perf11-thread-dump-1.log,
perf12-thread-dump-1.log
This is something I had noticed in my scalability test but at that time I thought I may
have done something stupid and later, I saw a similar note in support case.
I have two portal servers (ports-01, ports-02) configuration where nullPortletPage.war is
predeployed before servers are started. If I start both servers simultaneously and access
http://localhost:8280/portal/portal/default/NullPortletPage then I get a 404 error with
"The requested resource () is not available". I am able to access the page if I
hit http://localhost:8180/portal/portal/default/NullPortletPage (notice the port) .
What is more interesting is that when I start servers one by one and access portal page
as server comes online i.e. start second server when first one has already started and
page has been accessed, then I can access the NullPortletPage in both servers. Since there
is a work around, let's fix this by 2.6.5 release.
--
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
6334
days inactive
6544
days old
26 comments
4 participants
participants (4)
-
Anonymous (JIRA) -
Galder Zamarreno (JIRA)
-
Prabhat Jha (JIRA)
-
Thomas Heute (JIRA)