[jira] [Created] (GERONIMO-6169) Recursive lookup while the default comp entry is configured

2011-09-22 Thread Ivan (JIRA)
Recursive lookup while the default comp entry is configured
---

 Key: GERONIMO-6169
 URL: https://issues.apache.org/jira/browse/GERONIMO-6169
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: deployment
Affects Versions: 3.0-M1
Reporter: Ivan
Assignee: Ivan
 Fix For: 3.0


If there is an resource entry like java:comp/EJBContext configured in the DD or 
added by other modules, and the responsible module has not processed it, 
AdminObjectRefBuilder will add a JndiReference in the binding map, which will 
cause the infinite lookup. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (GERONIMO-6169) Recursive lookup while the default comp entry is configured

2011-09-22 Thread Ivan (JIRA)

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

Ivan commented on GERONIMO-6169:


Commit first step changes to trunk at r1173982. It looks to me that the name 
should be first checked, if it is the default comp name, we should not create a 
JndiReference, and leave other modules processed it.

> Recursive lookup while the default comp entry is configured
> ---
>
> Key: GERONIMO-6169
> URL: https://issues.apache.org/jira/browse/GERONIMO-6169
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: deployment
>Affects Versions: 3.0-M1
>Reporter: Ivan
>Assignee: Ivan
> Fix For: 3.0
>
>
> If there is an resource entry like java:comp/EJBContext configured in the DD 
> or added by other modules, and the responsible module has not processed it, 
> AdminObjectRefBuilder will add a JndiReference in the binding map, which will 
> cause the infinite lookup. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira




Re: [VOTE] Release Geronimo Customized Tomcat 6.0.33.1

2011-09-22 Thread Forrest Xia
+1

Forrest

On Wed, Sep 21, 2011 at 11:09 AM, Shenghao Fang
wrote:

> Please vote for Geronimo Customized Tomcat 6.0.33.1.
>
> The codes are based on Apache Tomcat 6.0.33 tag, and include the
> following extra changes:
> a.  GERONIMO-3451  "Restricted listeners property file not found"
> error logged during Tomcat server startup
> b.  GERONIMO-4685  Build our own tomcat
> c.  Merged security fixes for CVE-2011-3190 from Tomcat 6.0.x trunk
>
> Vote will be open for 72 hours.
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapachegeronimo-082/
>
> Source repo:
>
> https://svn.apache.org/repos/asf/geronimo/external/tags/tomcat-parent-6.0.33.1/
>
>
> --
> Michael
>


Re: Geronimo directory structure & permissions

2011-09-22 Thread Forrest Xia
3.0 does not have the feature like the doc for multiple instances support.
The doc needs update.

Forrest

On Wed, Sep 21, 2011 at 11:03 PM, Russell E Glaue  wrote:

> AFAIK, we still have a desire to support multiple instances per Geronimo
> base
> install.
>
> https://cwiki.apache.org/GMOxDOC30/running-multiple-geronimo-instances.html
>
> We have been working towards a common configuration location in 3.0 trunk
> for
> all parts of Geronimo.
>
> I am expecting to test and use multiple instances with the 3.0 release.
>
> -RG
>
>
> On 09/20/2011 10:08 PM, Rex Wang wrote:
> > If we want to continue maintain such complexity in 3.0? Hard drive is
> pretty
> > cheap nowadays.
> >
> > And I think currently the part that looks a little bit wasting space is
> karaf
> > "copy" the artifacts from repository to cache when start..
> >
> > -Rex
> >
> > 2011/9/21 Forrest Xia mailto:forres...@gmail.com>>
> >
> > This idea is like the multiple instances feature we had in 2.1
> branch, but
> > not supported in trunk now.
> >
> > Geronimo 2.1.x support copying "var" folder to add more instances
> with a
> > same installation, but G trunk code does not support that feature
> now.
> >
> > Do we have a user scenario to mandate that feature for 3.x?
> >
> > Regards,
> > Forrest
> >
> >
> > On Wed, Sep 21, 2011 at 1:55 AM, Jarek Gawor  > > wrote:
> >
> > Hi,
> >
> > In Geronimo binary install which directories do we consider
> read-only
> > vs. write/read? The idea is that the read-only directories could
> be
> > shared among multiple installations to save some space and reduce
> > maintenance.
> >
> > Here's what I identified so far:
> >
> > read-only:
> >  - bin
> >  - jsr88
> >  - schema
> >  - lib
> >
> > read/write:
> >  - deploy
> >  - hotbundles
> >  - etc
> >  - var
> >
> > The repository/ directory is a little weird because parts of it
> could
> > be considered read-only and some write. I wonder if maybe we
> should
> > have separate repository directories one for Geronimo bundles and
> > another one for applications.
> >
> > Thanks,
> > Jarek
> >
> >
> >
> >
> >
> > --
> > Lei Wang (Rex)
> > rwonly AT apache.org 
>


Re: [VOTE] Release Geronimo Customized Tomcat 6.0.33.1

2011-09-22 Thread Rex Wang
The vote is for
https://repository.apache.org/content/repositories/orgapachegeronimo-082/org/apache/geronimo/ext/tomcat/tomcat-parent-6.0.33/6.0.33.1/tomcat-parent-6.0.33-6.0.33.1-source-release.zip
https://repository.apache.org/content/repositories/orgapachegeronimo-082/org/apache/geronimo/ext/tomcat/tomcat-parent-6.0.33/6.0.33.1/tomcat-parent-6.0.33-6.0.33.1-source-release.tar.gz

build, rat:check, notice/license looks good to me.
+1

-Rex

2011/9/21 Shenghao Fang 

> Please vote for Geronimo Customized Tomcat 6.0.33.1.
>
> The codes are based on Apache Tomcat 6.0.33 tag, and include the
> following extra changes:
> a.  GERONIMO-3451  "Restricted listeners property file not found"
> error logged during Tomcat server startup
> b.  GERONIMO-4685  Build our own tomcat
> c.  Merged security fixes for CVE-2011-3190 from Tomcat 6.0.x trunk
>
> Vote will be open for 72 hours.
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapachegeronimo-082/
>
> Source repo:
>
> https://svn.apache.org/repos/asf/geronimo/external/tags/tomcat-parent-6.0.33.1/
>
>
> --
> Michael
>



-- 
Lei Wang (Rex)
rwonly AT apache.org


Re: [VOTE] Release Aries application-0.2.2 (1st attempt)

2011-09-22 Thread Rex Wang
Hi PMC members, please help review and vote ! :-)

2011/9/21 Rex Wang 

> Hi Devs,
>
> Aries application 0.2.2 is a bug-fix release which includes the fix for:
> ARIES-521: handles zip files without directory entries
> ARIES-635: Move the resource bundle to the right directory
> ARIES-638: Logging improvements for AriesApplicationManagerImpl
> ARIES-667: OBRAriesResolver can return bundle information for bundles with
> higher version than expected
> ARIES-689: Application OBR resolution fails for optional imports
> ARIES-734: Back port improvements made to resolution error messages in OBR
> application resolver
>
> The source up for vote is:
>
> https://repository.apache.org/content/repositories/orgapachearies-083/org/apache/aries/application/application/0.2.2/application-0.2.2-source-release.zip
>
> from the staging repository at:
> https://repository.apache.org/content/repositories/orgapachearies-083/
>
> The tag is:
> http://svn.apache.org/repos/asf/aries/tags/application-0.2.2/
>
> Vote will be open for 72 hours.
>
>  [ ] +1  approve
>  [ ] +0  no opinion
>  [ ] -1  disapprove (and reason why)
>
>
> thanks,
>
> --
> Lei Wang (Rex)
> rwonly AT apache.org
>



-- 
Lei Wang (Rex)
rwonly AT apache.org


Re: Geronimo directory structure & permissions

2011-09-22 Thread chi runhua
The way by sharing the repository or certain folders is not enabled in 3.0
yet.  To run multiple instances on one machine,  the only way is to copy the
server folder to another place on the disk, and then start the server after
changing the offPortset value in config-substitutions.properties file.

Jeff C

On Thu, Sep 22, 2011 at 4:27 PM, Forrest Xia  wrote:

> 3.0 does not have the feature like the doc for multiple instances support.
> The doc needs update.
>
> Forrest
>
>
> On Wed, Sep 21, 2011 at 11:03 PM, Russell E Glaue  wrote:
>
>> AFAIK, we still have a desire to support multiple instances per Geronimo
>> base
>> install.
>>
>>
>> https://cwiki.apache.org/GMOxDOC30/running-multiple-geronimo-instances.html
>>
>> We have been working towards a common configuration location in 3.0 trunk
>> for
>> all parts of Geronimo.
>>
>> I am expecting to test and use multiple instances with the 3.0 release.
>>
>> -RG
>>
>>
>> On 09/20/2011 10:08 PM, Rex Wang wrote:
>> > If we want to continue maintain such complexity in 3.0? Hard drive is
>> pretty
>> > cheap nowadays.
>> >
>> > And I think currently the part that looks a little bit wasting space is
>> karaf
>> > "copy" the artifacts from repository to cache when start..
>> >
>> > -Rex
>> >
>> > 2011/9/21 Forrest Xia mailto:forres...@gmail.com
>> >>
>> >
>> > This idea is like the multiple instances feature we had in 2.1
>> branch, but
>> > not supported in trunk now.
>> >
>> > Geronimo 2.1.x support copying "var" folder to add more instances
>> with a
>> > same installation, but G trunk code does not support that feature
>> now.
>> >
>> > Do we have a user scenario to mandate that feature for 3.x?
>> >
>> > Regards,
>> > Forrest
>> >
>> >
>> > On Wed, Sep 21, 2011 at 1:55 AM, Jarek Gawor > > > wrote:
>> >
>> > Hi,
>> >
>> > In Geronimo binary install which directories do we consider
>> read-only
>> > vs. write/read? The idea is that the read-only directories could
>> be
>> > shared among multiple installations to save some space and
>> reduce
>> > maintenance.
>> >
>> > Here's what I identified so far:
>> >
>> > read-only:
>> >  - bin
>> >  - jsr88
>> >  - schema
>> >  - lib
>> >
>> > read/write:
>> >  - deploy
>> >  - hotbundles
>> >  - etc
>> >  - var
>> >
>> > The repository/ directory is a little weird because parts of it
>> could
>> > be considered read-only and some write. I wonder if maybe we
>> should
>> > have separate repository directories one for Geronimo bundles
>> and
>> > another one for applications.
>> >
>> > Thanks,
>> > Jarek
>> >
>> >
>> >
>> >
>> >
>> > --
>> > Lei Wang (Rex)
>> > rwonly AT apache.org 
>>
>
>


[BUILD] branches/2.2: Failed for Revision: 1173900

2011-09-22 Thread Jarek Gawor
Build status: FAILED
 
Geronimo Revision: 1173900 built with tests included
 
See the full build-2000.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20110922/build-2000.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20110922
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 434 minutes 5 seconds
[INFO] Finished at: Thu Sep 22 03:19:36 EDT 2011
[INFO] Final Memory: 313M/738M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20110922/logs-2000-tomcat/
 
[INFO] Running TestSuite
[INFO] Tests run: 40, Failures: 26, Errors: 0, Skipped: 0, Time elapsed: 
193.818 sec <<< FAILURE!
[INFO] Running TestSuite
[INFO] Tests run: 12, Failures: 6, Errors: 0, Skipped: 0, Time elapsed: 71.953 
sec <<< FAILURE!
--
[INFO] Running TestSuite
[INFO] Tests run: 36, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 68.695 
sec <<< FAILURE!
 
Assembly: jetty
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20110922/logs-2000-jetty/
 
[INFO] Running TestSuite
[INFO] Tests run: 40, Failures: 23, Errors: 0, Skipped: 0, Time elapsed: 
225.127 sec <<< FAILURE!
[INFO] Running TestSuite
[INFO] Tests run: 12, Failures: 8, Errors: 0, Skipped: 0, Time elapsed: 68.077 
sec <<< FAILURE!
--
[INFO] Running TestSuite
[INFO] Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 7.77 sec 
<<< FAILURE!
 
Samples: branches/2.2
=
Log: 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20110922/samples-2000.log
 
Build status: OK
 


[jira] [Created] (GERONIMO-6170) jdci-spec AnnotationLiteral hides root Exception

2011-09-22 Thread Mark Struberg (JIRA)
jdci-spec AnnotationLiteral hides root Exception


 Key: GERONIMO-6170
 URL: https://issues.apache.org/jira/browse/GERONIMO-6170
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
Reporter: Mark Struberg


gerinimo_jcdi_1.0_spec AnnotationLiteral#callMethod catches an Exception and 
throws a RuntimeException without passing the root cause.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira




Re: [tranql-dev] Re: Pls help reivew and apply patch from https://jira.codehaus.org/browse/TQL-28

2011-09-22 Thread viola lu
Hi, David:

 tranql-connection-generic build failed on JDK 1.6 coz of some new api and
method introduced in JDK 1.6 such as  java.sql.NClob;
java.sql.RowId;java.sql.SQLXML, should we update code to JDK 1.6
compliant? If so, pls apply http://jira.codehaus.org/browse/TQL-30,  But
this will make build fail on JDK 1.5 coz of new API in JDK 1.6.

On Wed, Sep 21, 2011 at 4:52 PM, Forrest Xia  wrote:

> David, I tried db2 xa adapter with java 5, the adapter functions well. So
> there should have no problem to use java 6 build these adapters and running
> under java 5. So please go ahead to release them. thank you!
>
> Forrest
>
>
> On Wed, Sep 21, 2011 at 6:14 AM, David Jencks wrote:
>
>> I'd prefer to check that what I'm building works with java 5 first.  I
>> pushed snapshots, can you check that they work properly?
>>
>> I think the relevant paths are
>>
>>
>> https://nexus.codehaus.org/content/repositories/snapshots/org/tranql/tranql-connector-sqlserver2008-xa/1.0-SNAPSHOT/
>> (note the version, I also deployed something called version 1.4 by
>> mistake)
>>
>>
>> https://nexus.codehaus.org/content/repositories/snapshots/org/tranql/tranql-connector-db2-xa/1.7-SNAPSHOT/
>>
>> Were there other connectors you want me to release?
>>
>> thanks
>> david jencks
>>
>> On Sep 20, 2011, at 12:25 AM, viola lu wrote:
>>
>> Hi, david:
>>  Thanks. One more request:
>>  Can you help apply  http://jira.codehaus.org/browse/TQL-29, and after
>> that, can you do a tranql release, so we can introduce these patches to
>> G2.1.8 and 3.0 release.
>>
>> On Mon, Sep 19, 2011 at 12:39 AM, David Jencks wrote:
>>
>>> I applied this (after tweaking a couple dates etc) and the tql-22
>>> patch having trouble logging into tranql jira so I haven't closed these.
>>>
>>> thanks
>>> david jencks
>>>
>>> On Sep 17, 2011, at 5:54 PM, viola lu wrote:
>>>
>>> >
>>> >
>>> > --
>>> > viola
>>> >
>>> > Apache Geronimo
>>> >
>>>
>>>
>>> -
>>> To unsubscribe from this list, please visit:
>>>
>>>http://xircles.codehaus.org/manage_email
>>>
>>>
>>>
>>
>>
>> --
>> viola
>>
>> Apache Geronimo
>>
>>
>>
>


-- 
viola

Apache Geronimo


cross posting

2011-09-22 Thread Kevan Miller

On Sep 22, 2011, at 4:29 AM, Rex Wang wrote:

> Hi PMC members, please help review and vote ! :-)

There's been a lot of cross-posting (multiple mailing lists on a single email), 
recently. Personally, that means emails get filed in strange places by my 
mailer. I now have an Aries vote thread getting filed in my Geronimo folder. 
Parts of an email thread end up in multiple folders.  Many times people will 
"Reply" instead of "Reply All".

I'd prefer to see relevant emails forwarded to geronimo dev, instead of 
cross-posted... Anybody else feel that way?

--kevan

Re: pull aries blueprint 0.3 tag to ext and ship as 0.3.0.1?

2011-09-22 Thread Shawn Jiang
Given the complexity to release a new bluepring from trunk.   we should go
for geronimo fork based on 0.3 tag for G3.0 beta.

We can switch back to the blueprint release in future geronimo release.

On Wed, Sep 21, 2011 at 5:45 PM, Rex Wang  wrote:

> Hi Devs,
>
> I plan to pull aries blueprint 0.3 tag to ext and apply the patch in
> Aries-727, and then ship it as 0.3.0.1.
> Blueprint 0.3.x is developing in aries trunk, and has a great of many other
> snapshot dependencies. Seems we do not have enough time to wait blueprint
> trunk to release, so I will release our fork in ext to catch up the steps of
> Geronimo 3.0-beta release.
>
> If no objection, will do it soon.
>
> regards,
>
> --
> Lei Wang (Rex)
> rwonly AT apache.org
>



-- 
Shawn


Re: [VOTE] Release Geronimo Customized Tomcat 6.0.33.1

2011-09-22 Thread Shawn Jiang
+1

On Wed, Sep 21, 2011 at 11:09 AM, Shenghao Fang
wrote:

> Please vote for Geronimo Customized Tomcat 6.0.33.1.
>
> The codes are based on Apache Tomcat 6.0.33 tag, and include the
> following extra changes:
> a.  GERONIMO-3451  "Restricted listeners property file not found"
> error logged during Tomcat server startup
> b.  GERONIMO-4685  Build our own tomcat
> c.  Merged security fixes for CVE-2011-3190 from Tomcat 6.0.x trunk
>
> Vote will be open for 72 hours.
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapachegeronimo-082/
>
> Source repo:
>
> https://svn.apache.org/repos/asf/geronimo/external/tags/tomcat-parent-6.0.33.1/
>
>
> --
> Michael
>



-- 
Shawn


Re: [tranql-dev] Re: Pls help reivew and apply patch from https://jira.codehaus.org/browse/TQL-28

2011-09-22 Thread Shawn Jiang
Maybe it's time to branch tranql for JDK 1.6 ?

On Thu, Sep 22, 2011 at 7:09 PM, viola lu  wrote:

> Hi, David:
>
>  tranql-connection-generic build failed on JDK 1.6 coz of some new api and
> method introduced in JDK 1.6 such as  java.sql.NClob;
> java.sql.RowId;java.sql.SQLXML, should we update code to JDK 1.6
> compliant? If so, pls apply http://jira.codehaus.org/browse/TQL-30,  But
> this will make build fail on JDK 1.5 coz of new API in JDK 1.6.
>
> On Wed, Sep 21, 2011 at 4:52 PM, Forrest Xia  wrote:
>
>> David, I tried db2 xa adapter with java 5, the adapter functions well. So
>> there should have no problem to use java 6 build these adapters and running
>> under java 5. So please go ahead to release them. thank you!
>>
>> Forrest
>>
>>
>> On Wed, Sep 21, 2011 at 6:14 AM, David Jencks wrote:
>>
>>> I'd prefer to check that what I'm building works with java 5 first.  I
>>> pushed snapshots, can you check that they work properly?
>>>
>>> I think the relevant paths are
>>>
>>>
>>> https://nexus.codehaus.org/content/repositories/snapshots/org/tranql/tranql-connector-sqlserver2008-xa/1.0-SNAPSHOT/
>>> (note the version, I also deployed something called version 1.4 by
>>> mistake)
>>>
>>>
>>> https://nexus.codehaus.org/content/repositories/snapshots/org/tranql/tranql-connector-db2-xa/1.7-SNAPSHOT/
>>>
>>> Were there other connectors you want me to release?
>>>
>>> thanks
>>> david jencks
>>>
>>> On Sep 20, 2011, at 12:25 AM, viola lu wrote:
>>>
>>> Hi, david:
>>>  Thanks. One more request:
>>>  Can you help apply  http://jira.codehaus.org/browse/TQL-29, and after
>>> that, can you do a tranql release, so we can introduce these patches to
>>> G2.1.8 and 3.0 release.
>>>
>>> On Mon, Sep 19, 2011 at 12:39 AM, David Jencks 
>>> wrote:
>>>
 I applied this (after tweaking a couple dates etc) and the tql-22
 patch having trouble logging into tranql jira so I haven't closed 
 these.

 thanks
 david jencks

 On Sep 17, 2011, at 5:54 PM, viola lu wrote:

 >
 >
 > --
 > viola
 >
 > Apache Geronimo
 >


 -
 To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email



>>>
>>>
>>> --
>>> viola
>>>
>>> Apache Geronimo
>>>
>>>
>>>
>>
>
>
> --
> viola
>
> Apache Geronimo
>
>


-- 
Shawn


Re: [VOTE] Release Geronimo Customized Tomcat 6.0.33.1

2011-09-22 Thread viola lu
+1

On Thu, Sep 22, 2011 at 9:19 PM, Shawn Jiang  wrote:

> +1
>
>
> On Wed, Sep 21, 2011 at 11:09 AM, Shenghao Fang <
> michael1224.f...@gmail.com> wrote:
>
>> Please vote for Geronimo Customized Tomcat 6.0.33.1.
>>
>> The codes are based on Apache Tomcat 6.0.33 tag, and include the
>> following extra changes:
>> a.  GERONIMO-3451  "Restricted listeners property file not found"
>> error logged during Tomcat server startup
>> b.  GERONIMO-4685  Build our own tomcat
>> c.  Merged security fixes for CVE-2011-3190 from Tomcat 6.0.x trunk
>>
>> Vote will be open for 72 hours.
>> [ ] +1  approve
>> [ ] +0  no opinion
>> [ ] -1  disapprove (and reason why)
>>
>> Staging repo:
>> https://repository.apache.org/content/repositories/orgapachegeronimo-082/
>>
>> Source repo:
>>
>> https://svn.apache.org/repos/asf/geronimo/external/tags/tomcat-parent-6.0.33.1/
>>
>>
>> --
>> Michael
>>
>
>
>
> --
> Shawn
>



-- 
viola

Apache Geronimo


Re: Geronimo directory structure & permissions

2011-09-22 Thread Russell E Glaue
When there are multiple instances, they do not share repositories. Each instance
must have its own copy of the repository.

That Wiki page is actually still relevant and correct. There is a note on that
page that multiple instances for the javaee6 bundle is currently not working.
That note need only be updated to document the additional JIRA issues that
prevent it.


However, the Geronimo minimal bundle does not package the extra javaee6 stuff
that prohibited multiple instances from working.
And just to make sure, I just successfully tested multiple instances with the
latest minimal SNAPSHOT, geronimo-tomcat7-minimal-3.0-20110922.084001-349. Seems
to work... for me.


If everyone can give me the JIRA numbers of the issues preventing multiple
instances with the javaee6 bundle, I'll add them to that related note on the
Wiki page.

-RG


On 09/22/2011 04:29 AM, chi runhua wrote:
> The way by sharing the repository or certain folders is not enabled in 3.0 
> yet. 
> To run multiple instances on one machine,  the only way is to copy the server
> folder to another place on the disk, and then start the server after changing
> the offPortset value in config-substitutions.properties file.
> 
> Jeff C
> 
> On Thu, Sep 22, 2011 at 4:27 PM, Forrest Xia  > wrote:
> 
> 3.0 does not have the feature like the doc for multiple instances support.
> The doc needs update.
> 
> Forrest
> 
> 
> On Wed, Sep 21, 2011 at 11:03 PM, Russell E Glaue  > wrote:
> 
> AFAIK, we still have a desire to support multiple instances per 
> Geronimo
> base
> install.
> 
> 
> https://cwiki.apache.org/GMOxDOC30/running-multiple-geronimo-instances.html
> 
> We have been working towards a common configuration location in 3.0
> trunk for
> all parts of Geronimo.
> 
> I am expecting to test and use multiple instances with the 3.0 
> release.
> 
> -RG
> 
> 
> On 09/20/2011 10:08 PM, Rex Wang wrote:
> > If we want to continue maintain such complexity in 3.0? Hard drive 
> is
> pretty
> > cheap nowadays.
> >
> > And I think currently the part that looks a little bit wasting space
> is karaf
> > "copy" the artifacts from repository to cache when start..
> >
> > -Rex
> >
> > 2011/9/21 Forrest Xia    >>
> >
> > This idea is like the multiple instances feature we had in 2.1
> branch, but
> > not supported in trunk now.
> >
> > Geronimo 2.1.x support copying "var" folder to add more 
> instances
> with a
> > same installation, but G trunk code does not support that 
> feature now.
> >
> > Do we have a user scenario to mandate that feature for 3.x?
> >
> > Regards,
> > Forrest
> >
> >
> > On Wed, Sep 21, 2011 at 1:55 AM, Jarek Gawor  
> > >> wrote:
> >
> > Hi,
> >
> > In Geronimo binary install which directories do we consider
> read-only
> > vs. write/read? The idea is that the read-only directories
> could be
> > shared among multiple installations to save some space and 
> reduce
> > maintenance.
> >
> > Here's what I identified so far:
> >
> > read-only:
> >  - bin
> >  - jsr88
> >  - schema
> >  - lib
> >
> > read/write:
> >  - deploy
> >  - hotbundles
> >  - etc
> >  - var
> >
> > The repository/ directory is a little weird because parts of
> it could
> > be considered read-only and some write. I wonder if maybe we
> should
> > have separate repository directories one for Geronimo 
> bundles and
> > another one for applications.
> >
> > Thanks,
> > Jarek
> >
> >
> >
> >
> >
> > --
> > Lei Wang (Rex)
> > rwonly AT apache.org  
> 
> 
> 


[jira] [Commented] (GERONIMO-5987) The ActiveMQ working directory and port are not referenced correctly - multiple instances not possible

2011-09-22 Thread Russell E Glaue (JIRA)

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

Russell E Glaue commented on GERONIMO-5987:
---

Update from testing with geronimo-tomcat7-javaee6-3.0-20110922.084001-348-bin 
SNAPSHOT

ActiveMQ does show up in the list of "Listening on Ports", and lists the port 
it is actually listening on and not the port it is configured to be listening 
on - which is good because that is the correct information to report. This 
actually resolves part of the reported issue requesting that the service and 
port be listed at startup.

But as this suggests, though I have PortOffset set to 100 in 
var/config/config-substitutions.properties, the ActiveMQ service still binds to 
the default port 61616, and all other dependent services are attempting to bind 
to ActiveMQ at the configured port 61716.
So ActiveMQ's configuration is not unified into config-substitutions yet.

Also, the etc/blueprint-activemq-placeholder.cfg file still exists in the 
latest snapshot which contains supposed configuration for ActiveMQ. However, as 
before, setting the activemq.port or the portOffset in this config file does 
not change anything either.


> The ActiveMQ working directory and port are not referenced correctly - 
> multiple instances not possible
> --
>
> Key: GERONIMO-5987
> URL: https://issues.apache.org/jira/browse/GERONIMO-5987
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: ActiveMQ
>Affects Versions: 3.0-M1, 3.0
> Environment: Linux x86, Red Hat Enterprise Linux Server release 5.4 
> (Tikanga)
>Reporter: Russell E Glaue
>Assignee: Rex Wang
>  Labels: geronimo
> Attachments: GERONIMO-5987-detail.patch, GERONIMO-5987-new.patch, 
> GERONIMO-5987.patch
>
>
> I am testing with geronimo-tomcat7-javaee6-web-3.0-SNAPSHOT, 
> geronimo-tomcat7-javaee6-web-3.0-20110523.171218-97
> ActiveMQ is configured to run as "org.apache.geronimo.home.dir/var/activemq" 
> and port 61616, and does not cooperate with multi-server configurations, nor 
> does it use the PortOffset. This is the use of the 
> "org.apache.geronimo.server.name" option and PortOffset in 
> "var/config/config-substitutions.properties". (see: 
> https://cwiki.apache.org/GMOxDOC30/running-multiple-geronimo-instances.html)
> First, Problem with working directory
> When wanting to run more than a single server instance, the ActiveMQ startup 
> will block waiting for the lock file "$GERONIMO_HOME/var/activemq/lock" to 
> become available.
> Obviously this causes any server instance started after the first server 
> instance is started to block during startup while waiting for the lock file 
> to become available.
> Second, Problem with PortOffset
> When configuring the PortOffset in  
> "var/config/config-substitutions.properties", all Geroniomo components expect 
> and attempt to connect to ActiveMQ at the port {ActiveMQ + PortOffset}. 
> However, regardless of what you set the PortOffset to be, the ActiveMQ 
> service only ever binds to port 61616, the default configured port (or 
> whatever you have the port set as for this service).
> Steps to repeat working directory problem:
> 1. Download and unpack G3.0 SNAPSHOT (3.0-20110523 tested)
> 2. Create the server instances:
> -- 2A. cd ${GERONIMO_HOME}
> -- 2B-1. mkdir gserver1
> -- 2B-2. cp -rp var gserver1/
> -- 2B-3. cp -rp etc gserver1/
> -- 2B-4. cp -rp repository gserver1/
> 3. update the "PortOffset" parameter in 
> gserver1/var/config/config-substitutions.properties for the gserver1 instance.
> 4. Start the default instance and gserver1 instance:
> -- bin/startup
> -- env GERONIMO_OPTS=-Dorg.apache.geronimo.server.name=gserver1 bin/startup
> 5. `tail -f gserver1/var/logs/geronimo.log` and you will see this as the last 
> line that outputs:
> "2011-05-31 16:26:39,609 WARN  [AMQPersistenceAdapter] Waiting to Lock the 
> Store var/activemq"
> The server waits here indefinitely.
> 6. Shutdown the default instance and you will see the "gserver1" instance 
> continue on in the startup procedures. (of course you will see errors due to 
> the PortOffset problem)
> * If I first start the "gserver1" instance by itself (before starting the 
> default instance), the directory "org.apache.geronimo.home.dir/var/activemq" 
> is created and populated. Instead it should be 
> "org.apache.geronimo.home.dir/org.apache.geronimo.server.name/var/activemq" 
> that is created and populated.
> * Probably the patch should be to reference the ActiveMQ working directory as 
> "org.apache.geronimo.server.dir/var/activemq"
> Steps to repeat PortOffset problem:
> 1. Download and unpack G3.0 SNAPSHOT (3.0-20110523 tested)
> 2

Re: Geronimo directory structure & permissions

2011-09-22 Thread Russell E Glaue
It should be noted that as long as JIRA GERONIMO-5987 goes unresolved, even if
you install several copies of Geronimo into different file structure locations
(e.g. /opt/g1 and /opt/g2), the javaee6 bundle does not allow multiple Geronimo
servers to run within the same runtime OS.

GERONIMO-5987 is the open issue for the ActiveMQ port configuration. Currently
ActiveMQ listens on port 61616 and you cannot change that in any configuration.
Thus prohibiting anymore than one Geronimo javaee6 server from running on a
single runtime OS.

I just updated JIRA GERONIMO-5987 to reflect the current status of the issue,
which has made a small step forward by listing the ActiveMQ service and actual
bind port (opposed to the configured bind port) in the Geronimo startup output.

-RG


On 09/22/2011 04:29 AM, chi runhua wrote:
> The way by sharing the repository or certain folders is not enabled in 3.0 
> yet. 
> To run multiple instances on one machine,  the only way is to copy the server
> folder to another place on the disk, and then start the server after changing
> the offPortset value in config-substitutions.properties file.
> 
> Jeff C
> 
> On Thu, Sep 22, 2011 at 4:27 PM, Forrest Xia  > wrote:
> 
> 3.0 does not have the feature like the doc for multiple instances support.
> The doc needs update.
> 
> Forrest
> 
> 
> On Wed, Sep 21, 2011 at 11:03 PM, Russell E Glaue  > wrote:
> 
> AFAIK, we still have a desire to support multiple instances per 
> Geronimo
> base
> install.
> 
> 
> https://cwiki.apache.org/GMOxDOC30/running-multiple-geronimo-instances.html
> 
> We have been working towards a common configuration location in 3.0
> trunk for
> all parts of Geronimo.
> 
> I am expecting to test and use multiple instances with the 3.0 
> release.
> 
> -RG
> 
> 
> On 09/20/2011 10:08 PM, Rex Wang wrote:
> > If we want to continue maintain such complexity in 3.0? Hard drive 
> is
> pretty
> > cheap nowadays.
> >
> > And I think currently the part that looks a little bit wasting space
> is karaf
> > "copy" the artifacts from repository to cache when start..
> >
> > -Rex
> >
> > 2011/9/21 Forrest Xia    >>
> >
> > This idea is like the multiple instances feature we had in 2.1
> branch, but
> > not supported in trunk now.
> >
> > Geronimo 2.1.x support copying "var" folder to add more 
> instances
> with a
> > same installation, but G trunk code does not support that 
> feature now.
> >
> > Do we have a user scenario to mandate that feature for 3.x?
> >
> > Regards,
> > Forrest
> >
> >
> > On Wed, Sep 21, 2011 at 1:55 AM, Jarek Gawor  
> > >> wrote:
> >
> > Hi,
> >
> > In Geronimo binary install which directories do we consider
> read-only
> > vs. write/read? The idea is that the read-only directories
> could be
> > shared among multiple installations to save some space and 
> reduce
> > maintenance.
> >
> > Here's what I identified so far:
> >
> > read-only:
> >  - bin
> >  - jsr88
> >  - schema
> >  - lib
> >
> > read/write:
> >  - deploy
> >  - hotbundles
> >  - etc
> >  - var
> >
> > The repository/ directory is a little weird because parts of
> it could
> > be considered read-only and some write. I wonder if maybe we
> should
> > have separate repository directories one for Geronimo 
> bundles and
> > another one for applications.
> >
> > Thanks,
> > Jarek
> >
> >
> >
> >
> >
> > --
> > Lei Wang (Rex)
> > rwonly AT apache.org  
> 
> 
> 


Re: [tranql-dev] Re: Pls help reivew and apply patch from https://jira.codehaus.org/browse/TQL-28

2011-09-22 Thread David Jencks
Hi Viola,

I think it would be acceptable to require building tranql on jdk 1.6 if the 
result still works with jdk 1.5.  I haven't spent enough time to verify this.  
If your patch results in something we can verify will still work with jdk 1.5 
(including drivers that work with jdk 1.5 that don't include the new methods)  
I'll apply it and release all the connectors to use it.

thanks
david jencks

On Sep 22, 2011, at 4:09 AM, viola lu wrote:

> Hi, David:
> 
>  tranql-connection-generic build failed on JDK 1.6 coz of some new api and 
> method introduced in JDK 1.6 such as  java.sql.NClob; 
> java.sql.RowId;java.sql.SQLXML, should we update code to JDK 1.6 compliant? 
> If so, pls apply http://jira.codehaus.org/browse/TQL-30,  But this will make 
> build fail on JDK 1.5 coz of new API in JDK 1.6.
> 
> On Wed, Sep 21, 2011 at 4:52 PM, Forrest Xia  wrote:
> David, I tried db2 xa adapter with java 5, the adapter functions well. So 
> there should have no problem to use java 6 build these adapters and running 
> under java 5. So please go ahead to release them. thank you!
> 
> Forrest
> 
> 
> On Wed, Sep 21, 2011 at 6:14 AM, David Jencks  wrote:
> I'd prefer to check that what I'm building works with java 5 first.  I pushed 
> snapshots, can you check that they work properly?
> 
> I think the relevant paths are
> 
> https://nexus.codehaus.org/content/repositories/snapshots/org/tranql/tranql-connector-sqlserver2008-xa/1.0-SNAPSHOT/
> (note the version, I also deployed something called version 1.4 by mistake)
> 
> https://nexus.codehaus.org/content/repositories/snapshots/org/tranql/tranql-connector-db2-xa/1.7-SNAPSHOT/
> 
> Were there other connectors you want me to release?
> 
> thanks
> david jencks
> 
> On Sep 20, 2011, at 12:25 AM, viola lu wrote:
> 
>> Hi, david:
>>  Thanks. One more request:
>>  Can you help apply  http://jira.codehaus.org/browse/TQL-29, and after that, 
>> can you do a tranql release, so we can introduce these patches to G2.1.8 and 
>> 3.0 release.
>> 
>> On Mon, Sep 19, 2011 at 12:39 AM, David Jencks  
>> wrote:
>> I applied this (after tweaking a couple dates etc) and the tql-22 patch 
>> having trouble logging into tranql jira so I haven't closed these.
>> 
>> thanks
>> david jencks
>> 
>> On Sep 17, 2011, at 5:54 PM, viola lu wrote:
>> 
>> >
>> >
>> > --
>> > viola
>> >
>> > Apache Geronimo
>> >
>> 
>> 
>> -
>> To unsubscribe from this list, please visit:
>> 
>>http://xircles.codehaus.org/manage_email
>> 
>> 
>> 
>> 
>> 
>> -- 
>> viola
>> 
>> Apache Geronimo
>> 
> 
> 
> 
> 
> 
> -- 
> viola
> 
> Apache Geronimo
> 



Re: [VOTE] Release Geronimo Customized Tomcat 6.0.33.1

2011-09-22 Thread Kevan Miller
Please include pointers to the source artifacts in your vote.

Here's my +1

--kevan

On Sep 20, 2011, at 11:09 PM, Shenghao Fang wrote:

> Please vote for Geronimo Customized Tomcat 6.0.33.1.
> 
> The codes are based on Apache Tomcat 6.0.33 tag, and include the
> following extra changes:
> a.  GERONIMO-3451  "Restricted listeners property file not found"
> error logged during Tomcat server startup
> b.  GERONIMO-4685  Build our own tomcat
> c.  Merged security fixes for CVE-2011-3190 from Tomcat 6.0.x trunk
> 
> Vote will be open for 72 hours.
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
> 
> Staging repo:
> https://repository.apache.org/content/repositories/orgapachegeronimo-082/
> 
> Source repo:
> https://svn.apache.org/repos/asf/geronimo/external/tags/tomcat-parent-6.0.33.1/
> 
> 
> -- 
> Michael



Re: [VOTE] Release Geronimo Customized Tomcat 6.0.33.1

2011-09-22 Thread David Jencks
+1

david jencks

On Sep 20, 2011, at 8:09 PM, Shenghao Fang wrote:

> Please vote for Geronimo Customized Tomcat 6.0.33.1.
> 
> The codes are based on Apache Tomcat 6.0.33 tag, and include the
> following extra changes:
> a.  GERONIMO-3451  "Restricted listeners property file not found"
> error logged during Tomcat server startup
> b.  GERONIMO-4685  Build our own tomcat
> c.  Merged security fixes for CVE-2011-3190 from Tomcat 6.0.x trunk
> 
> Vote will be open for 72 hours.
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
> 
> Staging repo:
> https://repository.apache.org/content/repositories/orgapachegeronimo-082/
> 
> Source repo:
> https://svn.apache.org/repos/asf/geronimo/external/tags/tomcat-parent-6.0.33.1/
> 
> 
> -- 
> Michael



[jira] [Commented] (GERONIMODEVTOOLS-706) Consider enabling Karaf shell in Eclipse console

2011-09-22 Thread Yi Xiao (JIRA)

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

Yi Xiao commented on GERONIMODEVTOOLS-706:
--

Hi Hong fang, the rev #1173019 misses an file: 
plugins/org.apache.geronimo.st.v30.ui/src/main/java/org/apache/geronimo/st/v30/ui/view/KarafShellSSHTerminalView.java,
 pls append it, thx~
I try to use the trunk code to build and find the problem.

> Consider enabling Karaf shell in Eclipse console
> 
>
> Key: GERONIMODEVTOOLS-706
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-706
> Project: Geronimo-Devtools
>  Issue Type: Improvement
>  Components: eclipse-plugin
>Affects Versions: 3.0-M2
>Reporter: Jarek Gawor
>Assignee: Ted Kirby
> Attachments: enableKarafShell_706.patch, 
> enableKarafShell_706_m0.patch, enableKarafShell_706_m1.patch, 
> karafSSHTerminal.jpg, karafSSHTerminal_improvement.jpg
>
>
> (If possible) I think it would be pretty nice to have an option to enable and 
> access Karaf shell directly in Eclipse console window. If that can be done 
> make sure to start Geronimo server with 
> -Djline.terminal=jline.UnsupportedTerminal option.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira