[jira] Commented: (GERONIMO-4694) Upgrade to Derby 10.5.1.1

2009-11-19 Thread Jack Cai (JIRA)

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

Jack Cai commented on GERONIMO-4694:


Derby 10.5 is on maven repo now: 
http://repo1.maven.org/maven2/org/apache/derby/derby/10.5.3.0_1/

Let's upgrade?

> Upgrade to Derby 10.5.1.1
> -
>
> Key: GERONIMO-4694
> URL: https://issues.apache.org/jira/browse/GERONIMO-4694
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: databases
>Affects Versions: 2.2
>Reporter: Jack Cai
> Fix For: Wish List
>
>
> Derby has released a new version 10.5.1.1 last month. Let's upgrade to this 
> version for 2.2.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



Re: Re-categorize the items in navigation pane for G2.2

2009-11-19 Thread Shawn Jiang
On Fri, Nov 20, 2009 at 1:55 PM, David Jencks wrote:

> Hi Jeff,
>
> This organization doesn't quite make sense to me.
>
> I can see something like
>
>
> >App Server
> info
> java system info
> server logs
> shutdown
> thread pools
> web server
> ejb server
> jms server
> DB info
> DB Manager
>
> >Resources
> Jar aliases
> Respository
>


> JMS Resources (why not under applications??)
>
Database pools (again, why not under applications?)
>
They are more like resources other than applications for me.   I also find
they are under resources section in other Java EE app server like WAS.

>
> >Applications
> Deploy New
> Plan Creator
> Plugins
> System Modules
> Application Ears
> Web App Wars
> Ejb Jars
> J2CA Connectors
> App Clients
>
> >Security
> Security Realms
> Keystores
> Certificate Authrotiry
> Users and Groups (this is not useful for real apps since it only looks at
> the default properties file security realm which hopefully no one will ever
> use in production)
>
> >Monitoring
> JMX Viewer
> JNDI Viewere
> Classloader viewer
> Dependency Viewer
> Monitoring
> LDAP Viewer (We don't install ldap by default, and this is a pretty weak
> app compared to e.g. ApacheDS Studio)
>
> I'm not sure about
> Apache HTTP since these are instructions that IIUC don't do anything in the
> actual geronimo server.  I really don't know where to put them.
>
>

> I've tried to put stuff in better categories (e.g. j2ca connectors are
> applications) and to put the most important/ most likely to be used choices
> first.
>
> Since there is some question (at least from me) about a good order I'm not
> sure if this should go in 2.2.  If you like what I suggest and no one else
> objects I guess I'm OK with it but I'd also be OK with just rearranging
> stuff in 3.0.
>
> thanks
> david jencks
>
> On Nov 19, 2009, at 8:31 PM, chi runhua wrote:
>
> I'm also attaching the snapshot of updated navigation layout for your
> reference.
>
>
> Jeff C
>
> On Fri, Nov 20, 2009 at 12:25 PM, chi runhua  wrote:
>
>> Hi devs,
>>
>> With the help of Shawn, we realized it's pretty easy to re-categorize the
>> items in navigation pane because of flexible architecture of Geronimo plugin
>> system. Just wonder if we could include the updates to the coming G2.2
>> release as a transitional stage of Console improvement task in G3.0. Here is
>> how I did it.
>>
>>  Locate all the AdminConsoleExtensionGBean in plan.xml of each portlet and
>> change the pageTitle attribute. For example,
>>   Update
>>  > class="org.apache.geronimo.pluto.AdminConsoleExtensionGBean">
>>Server/JMS Server
>>...
>>   To
>>  > class="org.apache.geronimo.pluto.AdminConsoleExtensionGBean">
>>Application Server/JMS
>> Server
>>...
>>
>>  The new category is nearly identical with the proposal in
>> https://issues.apache.org/jira/browse/GERONIMO-4950. I've built the
>> server assembly locally and looks everything just works fine.
>>
>> If you think it's acceptable, I'll open a new JIRA and submit the patches
>> for 2.2 branch&trunk later.
>>
>> Any comments?
>>
>>
>> Jeff C
>>
>
> 
>
>
>


-- 
Shawn


Re: Re-categorize the items in navigation pane for G2.2

2009-11-19 Thread David Jencks

Hi Jeff,

This organization doesn't quite make sense to me.

I can see something like


>App Server
info
java system info
server logs
shutdown
thread pools
web server
ejb server
jms server
DB info
DB Manager

>Resources
Jar aliases
Respository
JMS Resources (why not under applications??)
Database pools (again, why not under applications?)

>Applications
Deploy New
Plan Creator
Plugins
System Modules
Application Ears
Web App Wars
Ejb Jars
J2CA Connectors
App Clients

>Security
Security Realms
Keystores
Certificate Authrotiry
Users and Groups (this is not useful for real apps since it only looks  
at the default properties file security realm which hopefully no one  
will ever use in production)


>Monitoring
JMX Viewer
JNDI Viewere
Classloader viewer
Dependency Viewer
Monitoring
LDAP Viewer (We don't install ldap by default, and this is a pretty  
weak app compared to e.g. ApacheDS Studio)


I'm not sure about
Apache HTTP since these are instructions that IIUC don't do anything  
in the actual geronimo server.  I really don't know where to put them.


I've tried to put stuff in better categories (e.g. j2ca connectors are  
applications) and to put the most important/ most likely to be used  
choices first.


Since there is some question (at least from me) about a good order I'm  
not sure if this should go in 2.2.  If you like what I suggest and no  
one else objects I guess I'm OK with it but I'd also be OK with just  
rearranging stuff in 3.0.


thanks
david jencks

On Nov 19, 2009, at 8:31 PM, chi runhua wrote:

I'm also attaching the snapshot of updated navigation layout for  
your reference.



Jeff C

On Fri, Nov 20, 2009 at 12:25 PM, chi runhua   
wrote:

Hi devs,

With the help of Shawn, we realized it's pretty easy to re- 
categorize the items in navigation pane because of flexible  
architecture of Geronimo plugin system. Just wonder if we could  
include the updates to the coming G2.2 release as a transitional  
stage of Console improvement task in G3.0. Here is how I did it.


 Locate all the AdminConsoleExtensionGBean in plan.xml of each  
portlet and change the pageTitle attribute. For example,

  Update
 class="org.apache.geronimo.pluto.AdminConsoleExtensionGBean">

   Server/JMS Server
   ...
  To
 class="org.apache.geronimo.pluto.AdminConsoleExtensionGBean">
   Application Server/JMS  
Server

   ...

 The new category is nearly identical with the proposal in https://issues.apache.org/jira/browse/GERONIMO-4950 
. I've built the server assembly locally and looks everything just  
works fine.


If you think it's acceptable, I'll open a new JIRA and submit the  
patches for 2.2 branch&trunk later.


Any comments?


Jeff C






Re: minimal tomcat server is assembled, but failed on starting module tomcat6

2009-11-19 Thread David Jencks
I don't know how resource bundles work but I expect they have  
assumptions about classloaders loading the resource files that are not  
valid in osgi outside a single bundle.  I'm not sure exactly what  
happens with osgi either but I think that you have to use the Bundle  
object to load classes and resources from other bundles, not the  
classloader that loads the classes in a bundle.


For a modular system I'd expect that the resources would need to be in  
the bundle itself or else supplied through some kind of resource  
service.  If the resources aren't in the right bundle lets move them.


BTW I'm starting to try to get the welcome app to deploy, I'm adding a  
couple mini-assemblies to the build.  I'm starting with the jetty  
server if you'd like to take a look at the tomcat one that might  
be a standardized testbed for this work.  I've just committed the  
server assemblies under plugins/welcome.


thanks
david jencks

On Nov 19, 2009, at 7:51 PM, Forrest Xia wrote:


Hi,

I managed to locally make an assembly of tomcat-minimal  
successfully(of cause, disabled some modules, such as hot-deploy,  
remote-deploy).


But when I tried to start the server, I encounter a strange problem  
that I can not figure out why. The problem is:


When boot comes to plugin "org.apache.geronimo.configs/tomcat6/3.0- 
SNAPSHOT/car", an  java.util.MissingResourceException threw out.  
Full stack trace is:


[*   ]  83%  10s Starting  
org.apache.ger...2009-11-20 11:13:40,920 ERROR [GBeanInstanceState]  
Error while starting; GBean is now in the FAILED state:  
abstractName="org.apache.geronimo.configs/tomcat6/3.0-SNAPSHOT/car? 
ServiceModule=org.apache.geronimo.configs/tomcat6/3.0-SNAPSHOT/ 
car,j2eeType=GBean,name=TomcatServer"
org.apache.xbean.recipe.ConstructionException: Error invoking  
constructor: public  
org.apache.catalina.connector.Connector(java.lang.String) throws  
java.lang.Exception
at org.apache.xbean.recipe.ReflectionUtil 
$ConstructorFactory.create(ReflectionUtil.java:962)
at  
org 
.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java: 
276)
at  
org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96)
at  
org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61)
at  
org 
.apache 
.geronimo.tomcat.model.ConnectorType.getConnector(ConnectorType.java: 
595)
at  
org 
.apache 
.geronimo.tomcat.model.ServiceType.getService(ServiceType.java:278)
at  
org.apache.geronimo.tomcat.model.ServerType.build(ServerType.java:294)
at  
org 
.apache 
.geronimo.tomcat.TomcatServerGBean.(TomcatServerGBean.java:132)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native  
Method)
at  
sun 
.reflect 
.NativeConstructorAccessorImpl 
.newInstance(NativeConstructorAccessorImpl.java:39)
at  
sun 
.reflect 
.DelegatingConstructorAccessorImpl 
.newInstance(DelegatingConstructorAccessorImpl.java:27)

at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at org.apache.xbean.recipe.ReflectionUtil 
$ConstructorFactory.create(ReflectionUtil.java:952)
at  
org 
.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java: 
276)
at  
org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96)
at  
org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61)
at  
org 
.apache 
.geronimo 
.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:917)
at  
org 
.apache 
.geronimo 
.gbean 
.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java: 
269)
at  
org 
.apache 
.geronimo 
.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103)
at  
org 
.apache 
.geronimo 
.gbean 
.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java: 
125)
at  
org 
.apache 
.geronimo 
.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:544)
at  
org 
.apache 
.geronimo 
.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:385)
at  
org 
.apache 
.geronimo 
.kernel 
.config 
.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java: 
459)
at  
org 
.apache 
.geronimo 
.kernel 
.config 
.KernelConfigurationManager.start(KernelConfigurationManager.java:223)
at  
org 
.apache 
.geronimo 
.kernel 
.config 
.SimpleConfigurationManager 
.startConfiguration(SimpleConfigurationManager.java:713)
at  
org 
.apache 
.geronimo.system.main.EmbeddedDaemon.doStartup(EmbeddedDaemon.java: 
149)
at  
org 
.apache 
.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:81)
at  
org.apache.geronimo.main.Bootstrapper.execute(Bootstrapper.java:88)
at  
org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:65)
at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java: 
32)
Caused by: java.util.MissingResourceException: Can't find bundle for  
base name org.apache.catalina.connector.LocalStrings, locale en_US
at  
java 
.util 
.Resou

Re: Re-categorize the items in navigation pane for G2.2

2009-11-19 Thread Shawn Jiang
This change is quite straightforward so that there's no risk from the
technical perspective.

IMO,  If there's no non-tech objections, we should include it in new 22
release.

On Fri, Nov 20, 2009 at 1:09 PM, Rex Wang  wrote:

> Hi Jeff,
> It is OK to me for 3.0
> but 2.2 is going to release. Looks like there is no time to do such
> changes..
>
> -Rex
>
> 2009/11/20 chi runhua 
>
> Hi devs,
>>
>> With the help of Shawn, we realized it's pretty easy to re-categorize the
>> items in navigation pane because of flexible architecture of Geronimo plugin
>> system. Just wonder if we could include the updates to the coming G2.2
>> release as a transitional stage of Console improvement task in G3.0. Here is
>> how I did it.
>>
>>  Locate all the AdminConsoleExtensionGBean in plan.xml of each portlet and
>> change the pageTitle attribute. For example,
>>   Update
>>  > class="org.apache.geronimo.pluto.AdminConsoleExtensionGBean">
>>Server/JMS Server
>>...
>>   To
>>  > class="org.apache.geronimo.pluto.AdminConsoleExtensionGBean">
>>Application Server/JMS
>> Server
>>...
>>
>>  The new category is nearly identical with the proposal in
>> https://issues.apache.org/jira/browse/GERONIMO-4950. I've built the
>> server assembly locally and looks everything just works fine.
>>
>> If you think it's acceptable, I'll open a new JIRA and submit the patches
>> for 2.2 branch&trunk later.
>>
>> Any comments?
>>
>>
>> Jeff C
>>
>
>


-- 
Shawn


Re: Re-categorize the items in navigation pane for G2.2

2009-11-19 Thread Shawn Jiang
my two cents:

1,  two "server logs" in the snapshot.

2, "deply new" should be the first one in applications category.


On Fri, Nov 20, 2009 at 12:31 PM, chi runhua  wrote:

> I'm also attaching the snapshot of updated navigation layout for your
> reference.
>
>
> Jeff C
>
>
> On Fri, Nov 20, 2009 at 12:25 PM, chi runhua  wrote:
>
>> Hi devs,
>>
>> With the help of Shawn, we realized it's pretty easy to re-categorize the
>> items in navigation pane because of flexible architecture of Geronimo plugin
>> system. Just wonder if we could include the updates to the coming G2.2
>> release as a transitional stage of Console improvement task in G3.0. Here is
>> how I did it.
>>
>>  Locate all the AdminConsoleExtensionGBean in plan.xml of each portlet and
>> change the pageTitle attribute. For example,
>>   Update
>>  > class="org.apache.geronimo.pluto.AdminConsoleExtensionGBean">
>>Server/JMS Server
>>...
>>   To
>>  > class="org.apache.geronimo.pluto.AdminConsoleExtensionGBean">
>>Application Server/JMS
>> Server
>>...
>>
>>  The new category is nearly identical with the proposal in
>> https://issues.apache.org/jira/browse/GERONIMO-4950. I've built the
>> server assembly locally and looks everything just works fine.
>>
>> If you think it's acceptable, I'll open a new JIRA and submit the patches
>> for 2.2 branch&trunk later.
>>
>> Any comments?
>>
>>
>> Jeff C
>>
>
>


-- 
Shawn


Re: Re-categorize the items in navigation pane for G2.2

2009-11-19 Thread Rex Wang
Hi Jeff,
It is OK to me for 3.0
but 2.2 is going to release. Looks like there is no time to do such
changes..

-Rex

2009/11/20 chi runhua 

> Hi devs,
>
> With the help of Shawn, we realized it's pretty easy to re-categorize the
> items in navigation pane because of flexible architecture of Geronimo plugin
> system. Just wonder if we could include the updates to the coming G2.2
> release as a transitional stage of Console improvement task in G3.0. Here is
> how I did it.
>
>  Locate all the AdminConsoleExtensionGBean in plan.xml of each portlet and
> change the pageTitle attribute. For example,
>   Update
>   class="org.apache.geronimo.pluto.AdminConsoleExtensionGBean">
>Server/JMS Server
>...
>   To
>   class="org.apache.geronimo.pluto.AdminConsoleExtensionGBean">
>Application Server/JMS
> Server
>...
>
>  The new category is nearly identical with the proposal in
> https://issues.apache.org/jira/browse/GERONIMO-4950. I've built the server
> assembly locally and looks everything just works fine.
>
> If you think it's acceptable, I'll open a new JIRA and submit the patches
> for 2.2 branch&trunk later.
>
> Any comments?
>
>
> Jeff C
>


Re-categorize the items in navigation pane for G2.2

2009-11-19 Thread chi runhua
Hi devs,

With the help of Shawn, we realized it's pretty easy to re-categorize the
items in navigation pane because of flexible architecture of Geronimo plugin
system. Just wonder if we could include the updates to the coming G2.2
release as a transitional stage of Console improvement task in G3.0. Here is
how I did it.

 Locate all the AdminConsoleExtensionGBean in plan.xml of each portlet and
change the pageTitle attribute. For example,
  Update
 
   Server/JMS Server
   ...
  To
 
   Application Server/JMS
Server
   ...

 The new category is nearly identical with the proposal in
https://issues.apache.org/jira/browse/GERONIMO-4950. I've built the server
assembly locally and looks everything just works fine.

If you think it's acceptable, I'll open a new JIRA and submit the patches
for 2.2 branch&trunk later.

Any comments?


Jeff C


minimal tomcat server is assembled, but failed on starting module tomcat6

2009-11-19 Thread Forrest Xia
Hi,

I managed to locally make an assembly of tomcat-minimal successfully(of
cause, disabled some modules, such as hot-deploy, remote-deploy).

But when I tried to start the server, I encounter a strange problem that I
can not figure out why. The problem is:

When boot comes to plugin
"org.apache.geronimo.configs/tomcat6/3.0-SNAPSHOT/car", an
java.util.MissingResourceException threw out. Full stack trace is:

[*   ]  83%  10s Starting
org.apache.ger...2009-11-20 11:13:40,920 ERROR [GBeanInstanceState] Error
while starting; GBean is now in the FAILED state:
abstractName="org.apache.geronimo.configs/tomcat6/3.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/tomcat6/3.0-SNAPSHOT/car,j2eeType=GBean,name=TomcatServer"
org.apache.xbean.recipe.ConstructionException: Error invoking constructor:
public org.apache.catalina.connector.Connector(java.lang.String) throws
java.lang.Exception
at
org.apache.xbean.recipe.ReflectionUtil$ConstructorFactory.create(ReflectionUtil.java:962)
at
org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:276)
at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96)
at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61)
at
org.apache.geronimo.tomcat.model.ConnectorType.getConnector(ConnectorType.java:595)
at
org.apache.geronimo.tomcat.model.ServiceType.getService(ServiceType.java:278)
at
org.apache.geronimo.tomcat.model.ServerType.build(ServerType.java:294)
at
org.apache.geronimo.tomcat.TomcatServerGBean.(TomcatServerGBean.java:132)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at
org.apache.xbean.recipe.ReflectionUtil$ConstructorFactory.create(ReflectionUtil.java:952)
at
org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:276)
at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96)
at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:917)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:269)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:125)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:544)
at
org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:385)
at
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:459)
at
org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:223)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:713)
at
org.apache.geronimo.system.main.EmbeddedDaemon.doStartup(EmbeddedDaemon.java:149)
at
org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:81)
at org.apache.geronimo.main.Bootstrapper.execute(Bootstrapper.java:88)
at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:65)
at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:32)
Caused by: java.util.MissingResourceException: Can't find bundle for base
name org.apache.catalina.connector.LocalStrings, locale en_US
at
java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:1521)
at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1260)
at java.util.ResourceBundle.getBundle(ResourceBundle.java:787)
at
org.apache.tomcat.util.res.StringManager.(StringManager.java:77)
at
org.apache.tomcat.util.res.StringManager.(StringManager.java:72)
at
org.apache.tomcat.util.res.StringManager.getManager(StringManager.java:161)
at
org.apache.catalina.connector.MapperListener.(MapperListener.java:79)
at org.apache.catalina.connector.Connector.(Connector.java:266)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at
org.apache.xbean.recipe.ReflectionUtil$ConstructorFactory.create(ReflectionUtil.java:952)
... 29 more

So I double check the catalina bundle(whose bundle id is 122 in my assembly)
and confirmed there are resource files for LocalStrings in the jar. Its
package is exported an

[jira] Closed: (GERONIMO-4658) Console should let you add/edit artifact-aliases. When installing a jar, you should be able to add an artifact alias so it replaces something else.

2009-11-19 Thread Kevan Miller (JIRA)

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

Kevan Miller closed GERONIMO-4658.
--

Resolution: Fixed

> Console should let you add/edit artifact-aliases.  When installing a jar, you 
> should be able to add an artifact alias so it replaces something else.
> 
>
> Key: GERONIMO-4658
> URL: https://issues.apache.org/jira/browse/GERONIMO-4658
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.2
>Reporter: David Jencks
>Assignee: Kevan Miller
> Fix For: 2.2, 3.0
>
> Attachments: GERONIMO-4658.patch, GERONIMO-4658_2.patch, 
> GERONIMO-4658_MissingMessages.patch
>
>
> Should be able to edit artifact-aliases in the console. I think they are 
> available through the local attribute manager gbean. They can certainly be 
> installed there.
> In particular, when adding a jar, you should be able to add an artifact alias 
> at the same time so it replaces something else.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Resolved: (GERONIMO-4953) No way to set Tomcat native cluster on engine and host level

2009-11-19 Thread Ivan (JIRA)

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

Ivan resolved GERONIMO-4953.


   Resolution: Fixed
Fix Version/s: 3.0
   2.2

Commit changes to trunk At revision: 882391

> No way to set Tomcat native cluster on engine and host level
> 
>
> Key: GERONIMO-4953
> URL: https://issues.apache.org/jira/browse/GERONIMO-4953
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: web
>Affects Versions: 2.2
>Reporter: Ivan
>Assignee: Ivan
> Fix For: 2.2, 3.0
>
>
> Either in the server,xml or gbean definition, there is no way to set Tomcat 
> native cluster on engine and host level.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[BUILD] trunk: Failed for Revision: 882385

2009-11-19 Thread gawor
Geronimo Revision: 882385 built with tests included
 
See the full build-2100.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20091119/build-2100.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20091119/unit-test-reports
 
org.apache.maven.lifecycle.LifecycleExecutionException: Unable to get 
dependency information: Unable to read the metadata file for artifact 
'org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:jar': Cannot 
find parent: org.apache.servicemix.bundles:bundles-pom for project: 
org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle:2.1_3_3-SNAPSHOT
 for project 
org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle:2.1_3_3-SNAPSHOT
  
org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:jar:2.1_3_3-SNAPSHOT

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/),
  apache.snapshots (http://repository.apache.org/snapshots)

Path to dependency: 
1) org.apache.geronimo.framework:geronimo-kernel:bundle:3.0-SNAPSHOT


at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:576)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:599)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.artifact.resolver.ArtifactResolutionException: 
Unable to get dependency information: Unable to read the metadata file for 
artifact 
'org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:jar': Cannot 
find parent: org.apache.servicemix.bundles:bundles-pom for project: 
org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle:2.1_3_3-SNAPSHOT
 for project 
org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle:2.1_3_3-SNAPSHOT
  
org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:jar:2.1_3_3-SNAPSHOT

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/),
  apache.snapshots (http://repository.apache.org/snapshots)

Path to dependency: 
1) org.apache.geronimo.framework:geronimo-kernel:bundle:3.0-SNAPSHOT


at 
org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:432)
at 
org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:74)
at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:300)
at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:288)
at 
org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1417)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:407)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
... 16 more
Caused by: 
org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: Unable 
to read the metadata file for artifact 
'org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:jar': Cannot 
find parent: org.apache.servicemix.bundles:bundles-pom for project: 
org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle

[jira] Assigned: (GERONIMO-4658) Console should let you add/edit artifact-aliases. When installing a jar, you should be able to add an artifact alias so it replaces something else.

2009-11-19 Thread Kevan Miller (JIRA)

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

Kevan Miller reassigned GERONIMO-4658:
--

Assignee: Kevan Miller  (was: David Jencks)

> Console should let you add/edit artifact-aliases.  When installing a jar, you 
> should be able to add an artifact alias so it replaces something else.
> 
>
> Key: GERONIMO-4658
> URL: https://issues.apache.org/jira/browse/GERONIMO-4658
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.2
>Reporter: David Jencks
>Assignee: Kevan Miller
> Fix For: 2.2, 3.0
>
> Attachments: GERONIMO-4658.patch, GERONIMO-4658_2.patch, 
> GERONIMO-4658_MissingMessages.patch
>
>
> Should be able to edit artifact-aliases in the console. I think they are 
> available through the local attribute manager gbean. They can certainly be 
> installed there.
> In particular, when adding a jar, you should be able to add an artifact alias 
> at the same time so it replaces something else.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[BUILD] trunk: Failed for Revision: 882271

2009-11-19 Thread gawor
Geronimo Revision: 882271 built with tests included
 
See the full build-1500.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20091119/build-1500.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20091119/unit-test-reports
 
org.apache.maven.lifecycle.LifecycleExecutionException: Unable to get 
dependency information: Unable to read the metadata file for artifact 
'org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:jar': Cannot 
find parent: org.apache.servicemix.bundles:bundles-pom for project: 
org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle:2.1_3_3-SNAPSHOT
 for project 
org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle:2.1_3_3-SNAPSHOT
  
org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:jar:2.1_3_3-SNAPSHOT

from the specified remote repositories:
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots),
  ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/),
  central (http://repo1.maven.org/maven2)

Path to dependency: 
1) org.apache.geronimo.framework:geronimo-kernel:bundle:3.0-SNAPSHOT


at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:576)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.artifact.resolver.ArtifactResolutionException: 
Unable to get dependency information: Unable to read the metadata file for 
artifact 
'org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:jar': Cannot 
find parent: org.apache.servicemix.bundles:bundles-pom for project: 
org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle:2.1_3_3-SNAPSHOT
 for project 
org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle:2.1_3_3-SNAPSHOT
  
org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:jar:2.1_3_3-SNAPSHOT

from the specified remote repositories:
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots),
  ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/),
  central (http://repo1.maven.org/maven2)

Path to dependency: 
1) org.apache.geronimo.framework:geronimo-kernel:bundle:3.0-SNAPSHOT


at 
org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:432)
at 
org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:74)
at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:300)
at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:288)
at 
org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1417)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:407)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
... 16 more
Caused by: 
org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: Unable 
to read the metadata file for artifact 
'org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:jar': Cannot 
find parent: org.apache.servicemix.bundles:bundles-pom for project: 
org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle

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

2009-11-19 Thread gawor
Geronimo Revision: 882244 built with tests included
 
See the full build-1400.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20091119/build-1400.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20091119/unit-test-reports
 
org.apache.maven.lifecycle.LifecycleExecutionException: Unable to get 
dependency information: Unable to read the metadata file for artifact 
'org.apache.maven.reporting:maven-reporting-api:jar': Cannot find parent: 
org.apache.maven.reporting:maven-reporting for project: 
null:maven-reporting-api:jar:2.0.5 for project 
null:maven-reporting-api:jar:2.0.5
  org.apache.maven.reporting:maven-reporting-api:jar:2.0.5

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots)

Path to dependency: 
1) 
org.apache.maven.plugins:maven-remote-resources-plugin:maven-plugin:1.0
2) org.apache.maven:maven-core:jar:2.0.5


at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:576)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.artifact.resolver.ArtifactResolutionException: 
Unable to get dependency information: Unable to read the metadata file for 
artifact 'org.apache.maven.reporting:maven-reporting-api:jar': Cannot find 
parent: org.apache.maven.reporting:maven-reporting for project: 
null:maven-reporting-api:jar:2.0.5 for project 
null:maven-reporting-api:jar:2.0.5
  org.apache.maven.reporting:maven-reporting-api:jar:2.0.5

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots)

Path to dependency: 
1) 
org.apache.maven.plugins:maven-remote-resources-plugin:maven-plugin:1.0
2) org.apache.maven:maven-core:jar:2.0.5


at 
org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:432)
at 
org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:437)
at 
org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:74)
at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:300)
at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:288)
at 
org.apache.maven.plugin.DefaultPluginManager.ensurePluginContainerIsComplete(DefaultPluginManager.java:772)
at 
org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:606)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:431)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
... 16 more
Caused by: 
org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: Unable 
to read the metadata file for artifact 
'org.apache.maven.reporting:maven-reporting-api:jar': Cannot find parent: 
org.apache.maven.reporting:maven-reporting for project: 
null:maven-reporting-api:jar:2.0.5 for project 
null:maven-reporting-api:jar:2.0.5
at 
org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocatedProject(MavenMetad

Re: Odd OpenEJB Remote Connection Behaviour

2009-11-19 Thread Quintin Beukes
Thanks for the quick turnaround :>

Where do I set ${PlanServerHostname} ? You mentioned I can set the 2
new properties as -D arguments when starting Geronimo, but this
variable isn't a property. At least it doesn't look like one.

Q

On Thu, Nov 19, 2009 at 1:39 AM, David Blevins  wrote:
> I added some configuration options to the Geronimo plan and related gbean:
> http://svn.apache.org/viewvc?view=revision&revision=881988
>
> You can actually set the two properties I added in that commit as -D vm
> properties.
>
> I think the use of 0.0.0.0 is the issue. It should be fine to do that on the
> server side, but we may just need to work around it for now and fix it
> later.  Try setting your ${PlanServerHostname} to a "real" address that is
> addressable by the client.  You may need to update the "ejbd.discovery"
> property as well to use the same address, but I think it might just pick it
> up.
>
> -David
>
> Begin forwarded message:
>
>> Resent-From: 
>> From: Quintin Beukes 
>> Date: November 16, 2009 1:14:42 AM PST
>> To: OpenEJB Users List 
>> Subject: Odd OpenEJB Remote Connection Behaviour
>> Reply-To: us...@openejb.apache.org
>>
>> Hey,
>>
>> I have noticed something odd, not sure what is causing this.
>>
>> When I have a client on machine A connecting to a remote OpenEJB
>> server on machine B everything works well. If I take the exact same
>> setup but I have another server running on machine A as well (so there
>> is a client+server  on machineA and a server on machineB), OpenEJB
>> successfully authenticated against machine B but then immediately
>> switches over all it's following connections to it's own machine (ie.
>> localhost).
>>
>> I've noticed if there is no server on machineA with the client, then I
>> receive the following error on stdout:
>>
>> WARNING [OpenEJB.client]: Failover: Cannot connect to server(s):
>> ejbd://0.0.0.0:4201 Exception: Cannot connect to server
>> 'ejbd://0.0.0.0:4201'.  Check that the server is started and that the
>> specified serverURL is correct..  Trying next.
>>
>> When the server is running, then this doesn't happen. I first noticed
>> this as follows:
>> 1. I created a user on serverB
>> 2. Authenticated the client against it which worked, so it obviously
>> connected to the server
>> 3. Started capturing data. The client was showing the data is there,
>> but the server's database doesn't reflect it.
>> 4. When I did a netstat I noticed a localhost :4201 connection.
>> 5. I removed ALL users from the local machine, but it kept authenticating.
>> 6. So I restarted the client and did a netstat, there was both a
>> localhost and 10.0.0.200 :4201 connection. The latter being in
>> TIME_WAIT.
>> 7. Whenever I stop the server on the local machine all works well as
>> intended.
>>
>> Quintin Beukes
>>
>
>


[BUILD] trunk: Failed for Revision: 882148

2009-11-19 Thread gawor
Geronimo Revision: 882148 built with tests included
 
See the full build-0900.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20091119/build-0900.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20091119/unit-test-reports
 
  
org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:jar:2.1_3_3-SNAPSHOT

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/),
  apache.snapshots (http://repository.apache.org/snapshots)

Path to dependency: 
1) org.apache.geronimo.framework:geronimo-kernel:bundle:3.0-SNAPSHOT


at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:576)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:599)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.artifact.resolver.ArtifactResolutionException: 
Unable to get dependency information: Unable to read the metadata file for 
artifact 
'org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:jar': Cannot 
find parent: org.apache.servicemix.bundles:bundles-pom for project: 
org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle:2.1_3_3-SNAPSHOT
 for project 
org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle:2.1_3_3-SNAPSHOT
  
org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:jar:2.1_3_3-SNAPSHOT

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/),
  apache.snapshots (http://repository.apache.org/snapshots)

Path to dependency: 
1) org.apache.geronimo.framework:geronimo-kernel:bundle:3.0-SNAPSHOT


at 
org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:432)
at 
org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:74)
at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:300)
at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:288)
at 
org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1417)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:407)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
... 16 more
Caused by: 
org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: Unable 
to read the metadata file for artifact 
'org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:jar': Cannot 
find parent: org.apache.servicemix.bundles:bundles-pom for project: 
org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle:2.1_3_3-SNAPSHOT
 for project 
org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle:2.1_3_3-SNAPSHOT
at 
org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocatedProject(MavenMetadataSource.java:183)
at 
org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocatedArtifact(MavenMetadataSource.java:91)
at 
org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:388)
.

[jira] Resolved: (GERONIMO-4955) Tomcat Clustering via Uni Cast doesn't work

2009-11-19 Thread Ivan (JIRA)

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

Ivan resolved GERONIMO-4955.


   Resolution: Fixed
Fix Version/s: 2.1.5

For 2.1.4, it should be fixed after merging the patch of Geronimo-4187 to 2.1 
branch.

> Tomcat Clustering via Uni Cast doesn't work
> ---
>
> Key: GERONIMO-4955
> URL: https://issues.apache.org/jira/browse/GERONIMO-4955
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Clustering
>Affects Versions: 2.1.4, 2.2
> Environment: Server 1:
> OS:Windows Vista  amd64  6.0 build 6001 Service Pack 1  
> Geronimo:  2.2-SNAPSHOT Build 2009.09.28-12:26:20.913+0800
> JVM: JDK 6 
> Server 2:
> OS:   Windows Server 2008 amd64  Version  6.0 build 6002 Service Pack 2
> Geronimo:2.2-SNAPSHOT2009.09.28-12:26:20.913+0800
> JVM:JDK 6
>Reporter: Lu Jiang
> Fix For: 2.1.5
>
> Attachments: node02ExcerptFromConfig.xml.txt, 
> node03ExcerptFromConfig.xml.txt, realm.xml, 
> servlet-examples-cluster-plan2.xml, servlet-examples-cluster-plan3.xml, 
> servlet-examples-cluster-server2.war, servlet-examples-cluster-server3.war, 
> simple-servlet-examples-cluster-plan2.xml
>
>
> Below is a senario:
> 1.Install geronimo 2.2 on two machines,namely  
> 9.186.10.60(NODE02),9.186.10.89(NODE03).
> 2.Configure Apache http server.
>  (1)add mod_jk.so to ApacheHttpServer_HOME/modules.
>  (2)add or modify workers.properties under ApacheHttpServer_HOME/conf like
> worker.list=loadbalancer,status
> worker.maintain=60
> worker.NODE02.port=8009
> worker.NODE02.host=9.186.10.60
> worker.NODE02.type=ajp13
> worker.NODE02.lbfactor=1
> worker.NODE03.port=8009
> worker.NODE03.host=9.186.10.89
> worker.NODE03.type=ajp13
> worker.NODE03.lbfactor=1
> worker.loadbalancer.type=lb
> worker.loadbalancer.balance_workers=NODE02,NODE03
> worker.loadbalancer.sticky_session=1
> worker.status.type=status
>  (3)add information below to  ApacheHttpServer_HOME/conf/
>  LoadModule jk_module modules/mod_jk.so   
> JkWorkersFile conf/workers.properties
> JkLogFile logs/mod_jk.log
> JkLogLeveldebug
> JkMount /* loadbalancer
> 3.
> For NODE02:
>   (1)Modify GERONIMO_HOME/var/config/config-substitutions.properties
>  ClusterNodeName=NODE02
>   (2)Modify GERONIMO_HOME/var/catalina/server.xml.
>  
> 
>For NODE03:
>   (1)Modify GERONIMO_HOME/var/config/config-substitutions.properties
>  ClusterNodeName=NODE03
>   (2)Modify GERONIMO_HOME/var/config/config.xml.
>  
>  
> 3.
> I tried two ways to enable unicast clustering..One is to enable it in 
> config.xml and the other is to enable it in the deploy plan.
> (Deploy the ream.xml first cause we have security realm configuration in the 
> application )
> The first way:(enable it in config.xml)
> On the two server,separately add GBean information under name="org.apache.geronimo.configs/tomcat6/2.2-SNAPSHOT/car"> 
> Refer to the attachment:node02ExcerptFromConfig.xml and 
> node03ExcertFromConfig.xml
> Then deploy the application servlet-examples-cluster-server2.war using Simple 
> simple-servlet-examples-cluster-plan2.xml as a deploy plan.
> deploy the application servlet-examples-cluster-server3.war using Simple 
> simple-servlet-examples-cluster-plan3.xml as a deploy plan.
> The second way:(enable it in deploy plan)
> Without modification to config.xml,deploy the application directly.
> deploy the application servlet-examples-cluster-server2.war using 
> servlet-examples-cluster-plan2.xml as a deploy plan.
> deploy the application servlet-examples-cluster-server3.war using  
> servlet-examples-cluster-plan3.xml as a deploy plan.
> Expected:
> Session will be replicated .When node 02 fails,the node 03 will be the back 
> up.and vice versa.
> But currently both way don't work, when node2 fails ,session is not 
> replicated to node03

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[BUILD] trunk: Failed for Revision: 882066

2009-11-19 Thread gawor
Geronimo Revision: 882066 built with tests included
 
See the full build-0300.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20091119/build-0300.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20091119/unit-test-reports
 
org.apache.maven.lifecycle.LifecycleExecutionException: Unable to get 
dependency information: Unable to read the metadata file for artifact 
'org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:jar': Cannot 
find parent: org.apache.servicemix.bundles:bundles-pom for project: 
org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle:2.1_3_3-SNAPSHOT
 for project 
org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle:2.1_3_3-SNAPSHOT
  
org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:jar:2.1_3_3-SNAPSHOT

from the specified remote repositories:
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots),
  ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/),
  central (http://repo1.maven.org/maven2)

Path to dependency: 
1) org.apache.geronimo.framework:geronimo-kernel:bundle:3.0-SNAPSHOT


at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:576)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.artifact.resolver.ArtifactResolutionException: 
Unable to get dependency information: Unable to read the metadata file for 
artifact 
'org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:jar': Cannot 
find parent: org.apache.servicemix.bundles:bundles-pom for project: 
org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle:2.1_3_3-SNAPSHOT
 for project 
org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle:2.1_3_3-SNAPSHOT
  
org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:jar:2.1_3_3-SNAPSHOT

from the specified remote repositories:
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots),
  ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/),
  central (http://repo1.maven.org/maven2)

Path to dependency: 
1) org.apache.geronimo.framework:geronimo-kernel:bundle:3.0-SNAPSHOT


at 
org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:432)
at 
org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:74)
at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:300)
at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:288)
at 
org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1417)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:407)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
... 16 more
Caused by: 
org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: Unable 
to read the metadata file for artifact 
'org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:jar': Cannot 
find parent: org.apache.servicemix.bundles:bundles-pom for project: 
org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle

[jira] Commented: (GERONIMO-4953) No way to set Tomcat native cluster on engine and host level

2009-11-19 Thread Ivan (JIRA)

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

Ivan commented on GERONIMO-4953:


Commit changes to 2.2 branch At revision: 882092

> No way to set Tomcat native cluster on engine and host level
> 
>
> Key: GERONIMO-4953
> URL: https://issues.apache.org/jira/browse/GERONIMO-4953
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: web
>Affects Versions: 2.2
>Reporter: Ivan
>Assignee: Ivan
>
> Either in the server,xml or gbean definition, there is no way to set Tomcat 
> native cluster on engine and host level.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.