Re: [VOTE] Release Geronimo 2.1.8 RC2

[Yi Xiao]

Rat check's result shows just some test resources miss license-head.
so my+1

On Wed, Dec 21, 2011 at 11:30 PM, Forrest Xia  wrote:

> Tag tck all passed!
>
> Here is my +1
>
>
> On Wed, Dec 21, 2011 at 2:05 PM, Forrest Xia  wrote:
>
>> Hi folks,
>>
>> A release candidate for Geronimo 2.1.8 has been created and staged.
>>
>> The tag has been created here:
>> https://svn.apache.org/repos/asf/geronimo/server/tags/geronimo-2.1.8/
>>
>> The staging repo is here:
>> https://repository.apache.org/content/repositories/orgapachegeronimo-377/
>>
>> The main artifacts up for vote are the source release archives:
>>
>> https://repository.apache.org/content/repositories/orgapachegeronimo-377/org/apache/geronimo/geronimo/2.1.8/geronimo-2.1.8-source-release.tar.gz
>>
>> https://repository.apache.org/content/repositories/orgapachegeronimo-377/org/apache/geronimo/geronimo/2.1.8/geronimo-2.1.8-source-release.zip
>>
>>
>> A tck execution against 2.1.8 tag is ongoing, and will be finished around
>> 16 hours later. I will update the status here.
>>
>> The vote will be open for 72 hours.
>>
>> [  ] +1 about time to push this out the door
>> [  ]  0 no opinion
>> [  ] -1 not this one  (please explain why)
>>
>>
>> --
>> Thanks!
>>
>> Regards, Forrest
>>
>>
>
>
> --
> Thanks!
>
> Regards, Forrest
>
>


-- 
Best regards!


 John Xiao

Re: Geronimo 3 and karaf 3

[David Jencks]

I pushed a karaf snapshot maybe that will help?  I don't see this problem 
locally.

thanks
david jencks

On Dec 21, 2011, at 8:18 AM, Forrest Xia wrote:

> Trunk build failed with this error when building a new module Geronimo 
> Framework, Feature :: DS and Metatype
> 
>  [INFO] Internal error in the plugin manager executing goal 
> 'org.apache.karaf.tooling:karaf-maven-plugin:3.0.0-SNAPSHOT:features-generate-descriptor':
>  Unable to find the mojo 'features-generate-descriptor' (or one of its 
> required components) in the plugin 
> 'org.apache.karaf.tooling:karaf-maven-plugin'
>  Component descriptor cannot be found in the component repository: 
> org.sonatype.aether.RepositorySystem.
> 
> 
> On Tue, Dec 20, 2011 at 2:06 PM, David Jencks  wrote:
> BTW, to get the regions/isolation stuff working I think we are going to need 
> to replace our use of BundleListener/SynchronousBundleListener with the 
> (updated-for-4.3) aries RecursiveBundleTracker.  I think we'll need also 
> change from ConfigurationActivator to an extender pattern.  I'd guess the 
> ConfigurationActivator functionality could be moved to DependencyManager 
> rather than having an additional tracker.
> 
> thanks
> david jencks
> 
> On Dec 20, 2011, at 10:13 AM, David Jencks wrote:
> 
>> OK, I just committed this stuff, with reference to GERONIMO-6240.
>> 
>> Some more hints
>> 
>> I can build all the way through with 
>> MAVEN_OPTS="-XX:MaxPermSize=2048m -Xms2048m -Xmx4096m"
>> 
>> I can start karaf after setting
>> 
>> export JAVA_MAX_MEM=2048m
>> export JAVA_MAX_PERM_MEM=512m
>> 
>> The car packaging is set up to stop and wait if it gets stuck.  In an 
>> earlier version of this you'd get the karaf console and you could use karaf 
>> commands to investigate what was going on.  For some reason this isn't 
>> working now.  If you get into this situation, you need to kill the maven 
>> java process some way.  Usually setting a breakpoint at DependencyManager 
>> line 571 will show you a bundle that has a resolution problem that you can 
>> then fix.
>> 
>> The problem with the console deploy-type commands I think relates to using 
>> the karaf RMIRegistry.  I'm going to modify it so it includes the port as a 
>> service property, then we can look for the osgi service and get its port 
>> instead of the port gbean attribute.
>> 
>> thanks
>> david jencks
>> 
>> On Dec 19, 2011, at 9:10 PM, David Jencks wrote:
>> 
>>> more not-yet-working inline
>>> 
>>> On Dec 19, 2011, at 5:08 PM, David Jencks wrote:
>>> 
 I've been spending a lot of time working to rebase geronimo on karaf 3 so 
 we can have a maintainable future and get stuff like osgi 4.3, up to date 
 aries components, and the experimental region support now in karaf.
 
 After a lot of work I have everything except clustering building and after 
 turning off a couple problematic modules the tomcat-javaee6 server starts 
 and the web admin console appears to work at least a little bit.   I'd 
 like a little vacation this year and would like to commit this work first 
 so that others can help with the loose ends if they like.  I'll probably 
 be around to answer questions in any case.
 
 The modules that don't start are:
 
 activemq-broker-blueprint.  The ${X + Y} stuff is not getting evaluated at 
 all.  I don't know if this is an xbean-blueprint problem or an aries 
 blueprint problem or a side effect of running in geronimo.
 As a result activemq-ra and tomcat-console-activemq can't be started.
 
 client-deployer.  I think this is a pretty simple gbean name problem but I 
 haven't looked into it.
 
 
 Here are some of the changes:
 
 -- assemble the server using a combination of karaf assembly from features 
 and kars and geronimo assembly from geronimo plugins.  We now use the same 
 base karaf assembly stuff as the normal default full karaf assembly 
 (except I might have left out the spring feature repository).
 
 -- basic geronimo components such as the kernel, configuration manager, 
 dependency manager, deployer, and service config builder are set up as 
 osgi declarative services so they start without any geronimo 
 configuration.  They are generally configured through config admin as 
 appropriate.  Most of these also have gbean wrappers so they can be 
 accessed through gbean references.
 
 -- "geronimo" is started from a DS component, EmbeddedDaemon.
 
 -- I think I'm using the karaf remote jmx security rather than ours.  The 
 capabilities are similar but not identical.
 
 Some other things that are not working yet:
 
 -- The (gogo) geronimo console commands that work through "remote" gbean 
 proxies don't work AFAIK.  Probably one way to fix this would be to expose 
 some more of the DS components using gbean wrappers, but I haven't looked 
 into this yet.
 
 -- the app cl

Re: Geronimo 3 and karaf 3

[Forrest Xia]

Trunk build failed with this error when building a new module *Geronimo
Framework, Feature :: DS and Metatype*

 [INFO] Internal error in the plugin manager executing goal
'org.apache.karaf.tooling:karaf-maven-plugin:3.0.0-SNAPSHOT:features-generate-descriptor':
Unable to find the mojo 'features-generate-descriptor' (or one of its
required components) in the plugin
'org.apache.karaf.tooling:karaf-maven-plugin'
 Component descriptor cannot be found in the component repository:
org.sonatype.aether.RepositorySystem.


On Tue, Dec 20, 2011 at 2:06 PM, David Jencks wrote:

> BTW, to get the regions/isolation stuff working I think we are going to
> need to replace our use of BundleListener/SynchronousBundleListener with
> the (updated-for-4.3) aries RecursiveBundleTracker.  I think we'll need
> also change from ConfigurationActivator to an extender pattern.  I'd guess
> the ConfigurationActivator functionality could be moved to
> DependencyManager rather than having an additional tracker.
>
> thanks
> david jencks
>
> On Dec 20, 2011, at 10:13 AM, David Jencks wrote:
>
> OK, I just committed this stuff, with reference to 
> GERONIMO-6240
> .
>
> Some more hints
>
> I can build all the way through with
> MAVEN_OPTS="-XX:MaxPermSize=2048m -Xms2048m -Xmx4096m"
>
> I can start karaf after setting
>
> export JAVA_MAX_MEM=2048m
> export JAVA_MAX_PERM_MEM=512m
>
> The car packaging is set up to stop and wait if it gets stuck.  In an
> earlier version of this you'd get the karaf console and you could use karaf
> commands to investigate what was going on.  For some reason this isn't
> working now.  If you get into this situation, you need to kill the maven
> java process some way.  Usually setting a breakpoint at DependencyManager
> line 571 will show you a bundle that has a resolution problem that you can
> then fix.
>
> The problem with the console deploy-type commands I think relates to using
> the karaf RMIRegistry.  I'm going to modify it so it includes the port as a
> service property, then we can look for the osgi service and get its port
> instead of the port gbean attribute.
>
> thanks
> david jencks
>
> On Dec 19, 2011, at 9:10 PM, David Jencks wrote:
>
> more not-yet-working inline
>
> On Dec 19, 2011, at 5:08 PM, David Jencks wrote:
>
> I've been spending a lot of time working to rebase geronimo on karaf 3 so
> we can have a maintainable future and get stuff like osgi 4.3, up to date
> aries components, and the experimental region support now in karaf.
>
>
> After a lot of work I have everything except clustering building and after
> turning off a couple problematic modules the tomcat-javaee6 server starts
> and the web admin console appears to work at least a little bit.   I'd like
> a little vacation this year and would like to commit this work first so
> that others can help with the loose ends if they like.  I'll probably be
> around to answer questions in any case.
>
>
> The modules that don't start are:
>
>
> activemq-broker-blueprint.  The ${X + Y} stuff is not getting evaluated at
> all.  I don't know if this is an xbean-blueprint problem or an aries
> blueprint problem or a side effect of running in geronimo.
>
> As a result activemq-ra and tomcat-console-activemq can't be started.
>
>
> client-deployer.  I think this is a pretty simple gbean name problem but I
> haven't looked into it.
>
>
>
> Here are some of the changes:
>
>
> -- assemble the server using a combination of karaf assembly from features
> and kars and geronimo assembly from geronimo plugins.  We now use the same
> base karaf assembly stuff as the normal default full karaf assembly (except
> I might have left out the spring feature repository).
>
>
> -- basic geronimo components such as the kernel, configuration manager,
> dependency manager, deployer, and service config builder are set up as osgi
> declarative services so they start without any geronimo configuration.
>  They are generally configured through config admin as appropriate.  Most
> of these also have gbean wrappers so they can be accessed through gbean
> references.
>
>
> -- "geronimo" is started from a DS component, EmbeddedDaemon.
>
>
> -- I think I'm using the karaf remote jmx security rather than ours.  The
> capabilities are similar but not identical.
>
>
> Some other things that are not working yet:
>
>
> -- The (gogo) geronimo console commands that work through "remote" gbean
> proxies don't work AFAIK.  Probably one way to fix this would be to expose
> some more of the DS components using gbean wrappers, but I haven't looked
> into this yet.
>
>
> -- the app client (as well as the client-deployer) is not working yet at
> all.  We may be able to use command line args to tell the EmbeddedDaemon
> it's an app client, or possibly not.  We may be able to use a karaf
> instance to supply different ConfigAdmin settings to e.g. the local
> attribute manager to convince it it's an app client.  Similarly the
> separa

[jira] [Created] (GERONIMO-6241) LocalAttributeManagerReadWriteTest of geronimo-system failed in 2.1 branch

[Forrest Xia (Created) (JIRA)]

LocalAttributeManagerReadWriteTest of geronimo-system failed in 2.1 branch
--

 Key: GERONIMO-6241
 URL: https://issues.apache.org/jira/browse/GERONIMO-6241
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: kernel
Affects Versions: 2.1.8
Reporter: Forrest Xia


Build framework/modules/geronimo-system with unit test, you will see a unit 
test failure:

---
Test set: 
org.apache.geronimo.system.configuration.LocalAttributeManagerReadWriteTest
---
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.256 sec <<< 
FAILURE!
testReadWrite(org.apache.geronimo.system.configuration.LocalAttributeManagerReadWriteTest)
  Time elapsed: 0.253 sec  <<< ERROR!
java.lang.Exception: 
{http://geronimo.apache.org/xml/ns/attributes-1.2}attribute: Number of children 
do not match up: 2 3
at 
org.apache.geronimo.testsupport.DOMUtils.compareNodes(DOMUtils.java:109)
at 
org.apache.geronimo.testsupport.DOMUtils.compareNodes(DOMUtils.java:114)
at 
org.apache.geronimo.testsupport.DOMUtils.compareNodes(DOMUtils.java:114)
at 
org.apache.geronimo.testsupport.DOMUtils.compareNodes(DOMUtils.java:114)
at 
org.apache.geronimo.testsupport.DOMUtils.compareNodes(DOMUtils.java:62)
at 
org.apache.geronimo.system.configuration.LocalAttributeManagerReadWriteTest.testReadWrite(LocalAttributeManagerReadWriteTest.java:276)


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [VOTE] Release Geronimo 2.1.8 RC2

[Forrest Xia]

Tag tck all passed!

Here is my +1

On Wed, Dec 21, 2011 at 2:05 PM, Forrest Xia  wrote:

> Hi folks,
>
> A release candidate for Geronimo 2.1.8 has been created and staged.
>
> The tag has been created here:
> https://svn.apache.org/repos/asf/geronimo/server/tags/geronimo-2.1.8/
>
> The staging repo is here:
> https://repository.apache.org/content/repositories/orgapachegeronimo-377/
>
> The main artifacts up for vote are the source release archives:
>
> https://repository.apache.org/content/repositories/orgapachegeronimo-377/org/apache/geronimo/geronimo/2.1.8/geronimo-2.1.8-source-release.tar.gz
>
> https://repository.apache.org/content/repositories/orgapachegeronimo-377/org/apache/geronimo/geronimo/2.1.8/geronimo-2.1.8-source-release.zip
>
>
> A tck execution against 2.1.8 tag is ongoing, and will be finished around
> 16 hours later. I will update the status here.
>
> The vote will be open for 72 hours.
>
> [  ] +1 about time to push this out the door
> [  ]  0 no opinion
> [  ] -1 not this one  (please explain why)
>
>
> --
> Thanks!
>
> Regards, Forrest
>
>


-- 
Thanks!

Regards, Forrest

Re: [Vote] Release Geronimo Samples & Daytrader 3.0-beta-1 RC4

[Forrest Xia]

Not see the news in the geronimo home page, when it will be there?

On Tue, Dec 13, 2011 at 7:38 PM, viola lu  wrote:

> Hi devs,
>
> The vote to release Geronimo Samples&Daytrader 3.0-beta-1 RC4 passes with
> 5 "+1" votes and no 0 or -1 votes. Voting +1 were
>
> Forrest Xia
>
> Rex Wang
>
> Kevan Miller
>
> Shawn Jiang
>
> Viola Lu
>
> Janet Han
>
> 4 of above "+1" were from PMC members.
>
> Thanks all for your time of review and vote.
>
> On Sat, Dec 10, 2011 at 2:13 AM, Kevan Miller wrote:
>
>> Looks good to me. Here's my +1
>>
>> --kevan
>> On Nov 25, 2011, at 6:02 AM, viola lu wrote:
>>
>> > Hi Devs,
>> >
>> >
>> > A forth release candidate for Geronimo Sample & Daytrader  3.0-beta-1
>> has been created and staged coz of previous failure release candidate.
>> >
>> > The tags have been created here:
>> >
>> >
>> https://svn.apache.org/repos/asf/geronimo/samples/tags/samples-parent-3.0-beta-1
>> >
>> https://svn.apache.org/repos/asf/geronimo/daytrader/tags/daytrader-3.0-beta-1/
>> >
>> > The staging repos is here:
>> >
>> >
>> https://repository.apache.org/content/repositories/orgapachegeronimo-210/(Daytrader)
>> >
>> https://repository.apache.org/content/repositories/orgapachegeronimo-247(Sample)
>> >
>> >
>> > The main artifacts up for vote are the source release archives:
>> >
>> https://repository.apache.org/content/repositories/orgapachegeronimo-247/org/apache/geronimo/samples/samples-parent/3.0-beta-1/samples-parent-3.0-beta-1-source-release.tar.gz
>> >
>> https://repository.apache.org/content/repositories/orgapachegeronimo-247/org/apache/geronimo/samples/samples-parent/3.0-beta-1/samples-parent-3.0-beta-1-source-release.zip
>> >
>> >
>> https://repository.apache.org/content/repositories/orgapachegeronimo-210/org/apache/geronimo/daytrader/daytrader-parent/3.0-beta-1/daytrader-parent-3.0-beta-1-source-release.tar.gz
>> >
>> https://repository.apache.org/content/repositories/orgapachegeronimo-210/org/apache/geronimo/daytrader/daytrader-parent/3.0-beta-1/daytrader-parent-3.0-beta-1-source-release.zip
>> >
>> > Here is sample update
>> >
>> >   •  Append Java EE 6 and OSGi samples
>> >
>> > Remove empty java file
>> >
>> https://svn.apache.org/repos/asf/geronimo/samples/tags/samples-parent-3.0-beta-1/samples/javaee6/singletonejb-javaee6/singletonejb-javaee6-war/src/main/java/org/apache/geronimo/samples/javaee6/singletonejb/sessionBeans/
>> >
>> > Remove useless dependency files
>> >
>> https://svn.apache.org/repos/asf/geronimo/samples/tags/samples-parent-3.0-beta-1/samples/javaee5/DataCDInfo/DataCDInfo-JTA-jetty/src/main/
>> >
>> >
>> > The vote will be open for the 72-hour minimum.
>> >
>> > [  ] +1 about time to push this out the door
>> > [  ]  0 no opinion
>> > [  ] -1 not this one  (please explain why)
>> >
>> > --
>> > viola
>> >
>> > Apache Geronimo
>> >
>>
>>
>
>
> --
> viola
>
> Apache Geronimo
>
>


-- 
Thanks!

Regards, Forrest

[jira] [Commented] (GERONIMO-6185) SchemaFactory.newInstance() fails on IBM JDK

[Forrest Xia (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-6185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13173964#comment-13173964
 ] 

Forrest Xia commented on GERONIMO-6185:
---

Hi Jarek, any more potential issues you may expect?

Since you gave the workaround, can we think this jira is resolved?

Thanks!
Forrest

> SchemaFactory.newInstance() fails on IBM JDK
> 
>
> Key: GERONIMO-6185
> URL: https://issues.apache.org/jira/browse/GERONIMO-6185
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: web
>Affects Versions: 3.0
>Reporter: Jarek Gawor
>
> On IBM JDK call to 
> SchemaFactory.newInstance(XMLConstants.W3C_XML_SCHEMA_NS_URI) will fail with 
> the following exception if the TCCL is set to some other classloader besides 
> the system classloader (e.g. in calling this function in a web or wab 
> application):
> java.lang.IllegalArgumentException: Provider 
> org.apache.xerces.jaxp.validation.XMLSchemaFactory not found
>   at javax.xml.validation.SchemaFactory.newInstance(Unknown Source)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (GERONIMO-6228) Jar resource and getRealPath cache should not be cleaned while uninstalling embedded WAB in EBA

[Ivan (Closed) (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-6228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan closed GERONIMO-6228.
--


> Jar resource and getRealPath cache should not be cleaned while uninstalling 
> embedded WAB in EBA
> ---
>
> Key: GERONIMO-6228
> URL: https://issues.apache.org/jira/browse/GERONIMO-6228
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Tomcat
>Affects Versions: 3.0-beta-1
>Reporter: Ivan
>Assignee: Ivan
> Fix For: 3.0, 3.0-beta-2
>
>
> Jar resource and getRealPath cache should not be cleaned while uninstalling 
> embedded WAB in EBA, those cache directories should be cleaned up while 
> uninstalling the EBA.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (GERONIMO-6228) Jar resource and getRealPath cache should not be cleaned while uninstalling embedded WAB in EBA

[Ivan (Resolved) (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-6228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan resolved GERONIMO-6228.


   Resolution: Fixed
Fix Version/s: 3.0
 Assignee: Ivan

> Jar resource and getRealPath cache should not be cleaned while uninstalling 
> embedded WAB in EBA
> ---
>
> Key: GERONIMO-6228
> URL: https://issues.apache.org/jira/browse/GERONIMO-6228
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Tomcat
>Affects Versions: 3.0-beta-1
>Reporter: Ivan
>Assignee: Ivan
> Fix For: 3.0, 3.0-beta-2
>
>
> Jar resource and getRealPath cache should not be cleaned while uninstalling 
> embedded WAB in EBA, those cache directories should be cleaned up while 
> uninstalling the EBA.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (GERONIMO-6229) Configuration not found Exception is thrown while accessing EBA portlet page

[Ivan (Closed) (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-6229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan closed GERONIMO-6229.
--

   Resolution: Fixed
Fix Version/s: 3.0
 Assignee: Ivan

> Configuration not found Exception is thrown while accessing EBA portlet page
> 
>
> Key: GERONIMO-6229
> URL: https://issues.apache.org/jira/browse/GERONIMO-6229
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 3.0-beta-1
>Reporter: Ivan
>Assignee: Ivan
> Fix For: 3.0, 3.0-beta-2
>
>
> Configuration GBean running does not mean that its sub GBeans are started, we 
> need to double check with ConfigurationManager.isRunning method. 
> 2011-12-11 21:18:41,605 ERROR [ConfigManagerPortlet] Configuration not found
> org.apache.geronimo.kernel.GBeanNotFoundException: 
> application/org.apache.geronimo.testsuite.simple-eba/1.0.0/eba?AriesApplication=application/org.apache.geronimo.testsuite.simple-eba/1.0.0/eba,j2eeType=GBean,name=AriesApplication
>  not found
>   at 
> org.apache.geronimo.kernel.basic.BasicRegistry.getGBeanInstance(BasicRegistry.java:133)
>   at 
> org.apache.geronimo.kernel.basic.BasicKernel.getGBean(BasicKernel.java:309)
>   at 
> org.apache.geronimo.console.configmanager.ConfigManagerPortlet.doView(ConfigManagerPortlet.java:314)
>   at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:348)
>   at javax.portlet.GenericPortlet.render(GenericPortlet.java:253)
>   at org.apache.geronimo.console.BasePortlet.render(BasePortlet.java:153)
>   at 
> org.apache.pluto.driver.services.container.FilterChainImpl.doFilter(FilterChainImpl.java:163)
>   at 
> org.apache.pluto.driver.services.container.FilterChainImpl.processFilter(FilterChainImpl.java:91)
>   at 
> org.apache.pluto.driver.services.container.FilterManagerImpl.processFilter(FilterManagerImpl.java:105)
>   at 
> org.apache.pluto.container.driver.PortletServlet.dispatch(PortletServlet.java:340)
>   at 
> org.apache.pluto.container.driver.PortletServlet.doGet(PortletServlet.java:261)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:575)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>   at 
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684)
>   at 
> org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:593)
>   at 
> org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:530)
>   at 
> org.apache.pluto.driver.container.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:233)
>   at 
> org.apache.pluto.driver.container.DefaultPortletInvokerService.render(DefaultPortletInvokerService.java:117)
>   at 
> org.apache.pluto.container.impl.PortletContainerImpl.doRender(PortletContainerImpl.java:157)
>   at 
> org.apache.pluto.driver.tags.PortletTag.doStartTag(PortletTag.java:165)
>   at 
> jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspService(portlet_002dskin_jsp.java:108)
>   at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>   at 
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684)
>   at 
> org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:593)
>   at 
> org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:530)
>   at 
> org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:927)
>   at 
> jsp.WEB_002dINF.themes.portlets_002donly_jsp._jspx_meth_c_005fforEach_005f0(portlets_002donly_jsp.java:146)
>   at 
> jsp.WEB_002dINF.themes.portlets_002donly_jsp._jspService(portlets_002donly_jsp.java:80)
>   at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>   at 
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:6