[jira] Updated: (GERONIMODEVTOOLS-579) java specs are not included into G server runtime by default

[Delos Dai (JIRA)]

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

Delos Dai updated GERONIMODEVTOOLS-579:
---

Attachment: 579.patch

Seems some dependencies included in server runtime are missing, when you create 
a JEE project. I have added the missing packages for 2.2 server adapter. Maybe 
there will be some update of the server runtime dependencies, if server 2.2 has 
some new lib packages added.

Attachment is the patch. Could anyone help to review it?

Thanks!

> java specs are not included into G server runtime by default
> 
>
> Key: GERONIMODEVTOOLS-579
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-579
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.2.0
> Environment: os:win2003
>Reporter: viola.lu
>Assignee: Tim McConnell
>Priority: Minor
> Attachments: 579.patch
>
>
> 1.Create a web dynamic project ,and add <%@ taglib 
> uri="http://java.sun.com/jsf/core"; prefix='f' %> to a jsp file
> 2.But can't recognize this taglib
> In 
> $GEPsrc\plugins\org\apache\geronimo\st\core\GeronimoServerRuntimeTargetHandler.java
>  file, no support for 2.2 target runtime, so myface spec, javamail spec  
> are not included by default.

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

Re: Default war deployed w/o plan gets /WebApp_ID context?

[Jason Dillon]

Even a random context would be better than always using "/ 
WebApp_ID"... but I would imagine that it should first try and create  
a unique context from the filename, encoding muck as needed.   
Otherwise, how about something more like "/webapp".


--jason


On Jun 16, 2009, at 1:15 PM, Shawn Jiang wrote:


Agreed, use war file name as the default context  is a good start.

On Tue, Jun 16, 2009 at 2:01 PM, Ivan  wrote:
WebApp_ID is not so friendly, not sure when it begins, this should  
be improved, maybe we could use the war file's name as the default  
context.


2009/6/16 Jason Dillon 
Aren't we trying to do something a little bit more intelligent about  
picking a context for deployed wars w/o a plan.xml?






Seems like all of these "default/..." wars want to mount under / 
WebApp_ID... forcing me to make a plan for them, just to set the  
context.


Is this how it always worked?

--jason



--
Ivan



--
Shawn

Re: Errors on console deploy not show in console

[Jason Dillon]

Why is that an extra operation to show the details of the error?

Why not simply include the details?

--jason


On Jun 16, 2009, at 1:18 PM, Shawn Jiang wrote:

There's a "show details" button to show the error.   I agree that  
the *NOT* part should be hi-lighted.


On Tue, Jun 16, 2009 at 1:34 PM, Jason Dillon   
wrote:
Why do we not show the error of a deployment, or in this case app  
start in the console:






Also, shouldn't the *not* part be hi-lighted bold+red or something?

It does not look all that dissimilar to a successful deploy+start,  
so it might be easily missed.


--jason



--
Shawn

[BUILD] trunk: Failed for Revision: 785086

[gawor]

Geronimo Revision: 785086 built with tests included
 
See the full build-0300.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090616/build-0300.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090616/unit-test-reports
 
from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository),
  codehaus.snapshots (http://snapshots.repository.codehaus.org)

Path to dependency: 
1) org.apache.geronimo.modules:geronimo-activemq:jar:2.2-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:79)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
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.activemq:activemq-core:jar': Cannot find parent: 
org.apache.activemq:activemq-parent for project: null:activemq-core:bundle:null 
for project null:activemq-core:bundle:null
  org.apache.activemq:activemq-core:jar:5.3-SNAPSHOT

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

Path to dependency: 
1) org.apache.geronimo.modules:geronimo-activemq:jar:2.2-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.activemq:activemq-core:jar': 
Cannot find parent: org.apache.activemq:activemq-parent for project: 
null:activemq-core:bundle:null for project null:activemq-core:bundle:null
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)
... 22 more
Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find 
parent: org.apache.activemq:activemq-parent for project: 
null:activemq-core:bundle:null for project null:activemq-core:bundle:null
at 
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1369)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:820)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:252)
at 
org.apache.maven.project.ar

Re: Odd (c) text in 2.1.4 console

[Jason Dillon]

Okay, thx.

/me wonders how we let that slide into an official release hrmmm

--jason


On Jun 16, 2009, at 1:20 PM, Shawn Jiang wrote:


Jason,

The odd message at the bottom of console is a known JIRA:

https://issues.apache.org/jira/browse/GERONIMO-4605


On Tue, Jun 16, 2009 at 1:30 PM, Jason Dillon   
wrote:

Was using the 2.1.4+tomcat release and found this very odd:





Also, why do we say "Apache Tomcat/..." instead of "Geronimo+Tomcat/ 
2.1.4"?


Totally agree with you that Geronimo+Tomcat/2.1.4 is more  
appropriate here.



--jason






--
Shawn

[jira] Created: (GERONIMODEVTOOLS-579) java specs are not included into G server runtime by default

[viola.lu (JIRA)]

java specs are not included into G server runtime by default


 Key: GERONIMODEVTOOLS-579
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-579
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 2.2.0
 Environment: os:win2003
Reporter: viola.lu
Assignee: Tim McConnell
Priority: Minor


1.Create a web dynamic project ,and add <%@ taglib 
uri="http://java.sun.com/jsf/core"; prefix='f' %> to a jsp file
2.But can't recognize this taglib

In 
$GEPsrc\plugins\org\apache\geronimo\st\core\GeronimoServerRuntimeTargetHandler.java
 file, no support for 2.2 target runtime, so myface spec, javamail spec  
are not included by default.

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

Re: Odd (c) text in 2.1.4 console

[Shawn Jiang]

Jason,
The odd message at the bottom of console is a known JIRA:

https://issues.apache.org/jira/browse/GERONIMO-4605


On Tue, Jun 16, 2009 at 1:30 PM, Jason Dillon  wrote:

> Was using the 2.1.4+tomcat release and found this very odd:
>
>
>
>
>
> Also, why do we say "Apache Tomcat/..." instead of "Geronimo+Tomcat/2.1.4"?


Totally agree with you that Geronimo+Tomcat/2.1.4 is more appropriate here.

>
>
> --jason
>
>
>
>


-- 
Shawn

Re: Errors on console deploy not show in console

[Shawn Jiang]

There's a "show details" button to show the error.   I agree that the *NOT*
part should be hi-lighted.

On Tue, Jun 16, 2009 at 1:34 PM, Jason Dillon  wrote:

> Why do we not show the error of a deployment, or in this case app start in
> the console:
>
>
>
>
>
> Also, shouldn't the *not* part be hi-lighted bold+red or something?
>
> It does not look all that dissimilar to a successful deploy+start, so it
> might be easily missed.
>
> --jason
>



-- 
Shawn

Re: Default war deployed w/o plan gets /WebApp_ID context?

[Shawn Jiang]

Agreed, use war file name as the default context  is a good start.

On Tue, Jun 16, 2009 at 2:01 PM, Ivan  wrote:

> WebApp_ID is not so friendly, not sure when it begins, this should be
> improved, maybe we could use the war file's name as the default context.
>
> 2009/6/16 Jason Dillon 
>
>> Aren't we trying to do something a little bit more intelligent about
>> picking a context for deployed wars w/o a plan.xml?
>>
>>
>>
>>
>>
>> Seems like all of these "default/..." wars want to mount under
>> /WebApp_ID... forcing me to make a plan for them, just to set the context.
>>
>> Is this how it always worked?
>>
>> --jason
>>
>
>
>
> --
> Ivan
>



-- 
Shawn

Re: Default war deployed w/o plan gets /WebApp_ID context?

[Ivan]

WebApp_ID is not so friendly, not sure when it begins, this should be
improved, maybe we could use the war file's name as the default context.

2009/6/16 Jason Dillon 

> Aren't we trying to do something a little bit more intelligent about
> picking a context for deployed wars w/o a plan.xml?
>
>
>
>
>
> Seems like all of these "default/..." wars want to mount under
> /WebApp_ID... forcing me to make a plan for them, just to set the context.
>
> Is this how it always worked?
>
> --jason
>



-- 
Ivan

Errors on console deploy not show in console

[Jason Dillon]

Why do we not show the error of a deployment, or in this case app  
start in the console:


<>



Also, shouldn't the *not* part be hi-lighted bold+red or something?

It does not look all that dissimilar to a successful deploy+start, so  
it might be easily missed.


--jason

[jira] Resolved: (GERONIMO-4686) No clear hints in startup error when 1050 port is already in use.

[Jarek Gawor (JIRA)]

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

Jarek Gawor resolved GERONIMO-4686.
---

Resolution: Fixed

Committed the new patch to trunk (revision 785067) and branches/2.1 (revision 
785068). Thanks!


> No clear hints in startup error when 1050 port is already in use.  
> ---
>
> Key: GERONIMO-4686
> URL: https://issues.apache.org/jira/browse/GERONIMO-4686
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: CORBA
>Affects Versions: 1.1.1, 2.0-M1, 2.0-M2, 2.0-M3, 2.0-M4, 2.0-M5, 2.0-M6, 
> 2.0-M7, 2.0, 2.0.1, 2.0.2, 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.1.5, 2.2
>Reporter: Shawn Jiang
>Assignee: Shawn Jiang
>Priority: Minor
> Fix For: 2.1.5, 2.2
>
> Attachments: G4686_g21.patch, G4686_g21_rework.patch, 
> G4686_trunk.patch, G4686_trunk_rework.patch
>
>
> When 1050 is used by other apps.  If you start geronimo, there will be a 
> startup error:
> org.apache.geronimo.corba.security.config.ConfigException: Error starting 
> transient name service 
> at 
> org.apache.geronimo.yoko.ORBConfigAdapter.createNameService(ORBConfigAdapter.java:179)
>  
> at 
> org.apache.geronimo.yoko.ORBConfigAdapter$$FastClassByCGLIB$$76e4a002.invoke()
>  
> at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) 
> at 
> org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:830)
>  
> at 
> org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) 
> at 
> org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
>  
> at 
> org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
>  
> at 
> org.apache.geronimo.corba.security.config.ConfigAdapter$$EnhancerByCGLIB$$3f9e1dfe.createNameService()
>  
> at org.apache.geronimo.corba.NameService.doStart(NameService.java:164) 
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:996)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:268)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:539) 
> at 
> org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
>  
> at 
> org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
>  
> at 
> org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
>  
> at 
> org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:553)
>  
> at 
> org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379)
>  
> at 
> org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:448)
>  
> at 
> org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187)
>  
> at 
> org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:530)
>  
> at 
> org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastClassByCGLIB$$ce77a924.invoke()
>  
> at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) 
> at 
> org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:830)
>  
> at 
> org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) 
> at 
> org.apache.geronimo.kernel.b

Re: Are these hardcodeed user/pass/host/port in plan.xml of farming correct ?

[Shawn Jiang]

Another question,  Seems config.xml does not support

 
 http://geronimo.apache.org/xml/ns/deployment/javabean-1.0";
class="org.apache.geronimo.farm.deployment.DeploymentExtendedJMXConnectorInfo">
 system
 manager
 rmi
 localhost
  ${NamingPort + PortOffset}

 JMXConnector
 true
 
 

style configuration.   I have to add a "port" attribute to BasicNodeInfo so
that I can expose it to config.xml in pom.xml.

Also, I agree that username and password should not be in
config-substitutions.properties.  But I do think they should be exposed in
config.xml so that the user can change them when he change the user/password
of server.



On Mon, Jun 15, 2009 at 6:50 PM, Gianny Damour <
gianny.dam...@optusnet.com.au> wrote:

> Hi Shawn,
>
> username, password and host should not be in
> config-substitutions.properties.
>
> port is the only candidate and should be set to ${NamingPort + PortOffset}
>
> Thanks,
> Gianny
>
>
> On 15/06/2009, at 6:14 PM, Shawn Jiang wrote:
>
>
>> In  Gtrunk\plugins\clustering\farming\src\main\plan\plan.xml,  there are
>> some  hardcodeed ser/pass/host/port string in it. I'm not sure if they
>> should be something like ${PlanClusterNodeName} so that they can be set in
>> server\config\config_substitution.properties.
>>
>>
>>
>> > class="org.apache.geronimo.farm.config.BasicNodeInfo">
>>  ${PlanClusterNodeName}
>>  
>>  > xmlns:ns="http://geronimo.apache.org/xml/ns/deployment/javabean-1.0";
>> class="org.apache.geronimo.farm.deployment.DeploymentExtendedJMXConnectorInfo">
>>  system
>>  manager
>>  rmi
>>  localhost
>>  1099
>>  JMXConnector
>>  true
>>  
>>  
>>  
>>
>>
>> Can anyone give me any thoughts ?
>>
>> --
>> Shawn
>>
>
>


-- 
Shawn

[jira] Updated: (GERONIMO-4687) System Modules Portlet doesn't list the stopped application names when you stop an application.

[Han Hong Fang (JIRA)]

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

Han Hong Fang updated GERONIMO-4687:


Attachment: GERONIMO-4687.patch

Patch is ready for this problem. 

With this patch, all stopped applications during stop action are listed. 


Janet

> System Modules Portlet doesn't list the stopped application names when you 
> stop an application.
> ---
>
> Key: GERONIMO-4687
> URL: https://issues.apache.org/jira/browse/GERONIMO-4687
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.1.4, 2.2
> Environment: Windows XP + IE 7 + IBM JDK 1.5
>Reporter: Han Hong Fang
>Assignee: Han Hong Fang
> Attachments: GERONIMO-4687.patch
>
>
> When stopping an application, the following msg is showned in the screen.
> "Stopped application"
> but no application names listed as what starting application msg does.
> "Started application
> org.apache.geronimo.framework/plugin/2.1.4/car".
> The problem only exists in admin console. Command deploy.bat|sh start/stop is 
> free of this symptom.

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

[jira] Created: (GERONIMO-4688) hardcode port in plan.xml of plugin farming.

[Shawn Jiang (JIRA)]

 hardcode port in plan.xml of plugin farming.
-

 Key: GERONIMO-4688
 URL: https://issues.apache.org/jira/browse/GERONIMO-4688
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: Clustering
Affects Versions: 2.1.4, 2.1.5, 2.2
Reporter: Shawn Jiang
Assignee: Shawn Jiang
Priority: Minor
 Fix For: 2.1.5, 2.2


In  Gtrunk\plugins\clustering\farming\src\main\plan\plan.xml,  there are some  
hardcodeed ser/pass/host/port string in it.   I'm not sure if they should be 
something like ${PlanClusterNodeName} so that they can be set in 
server\config\config_substitution.properties.   




  ${PlanClusterNodeName}
  
  http://geronimo.apache.org/xml/ns/deployment/javabean-1.0"; 
class="org.apache.geronimo.farm.deployment.DeploymentExtendedJMXConnectorInfo">
  system
  manager
  rmi
  localhost
  1099
  JMXConnector
  true
  
  
  


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

Re: Are these hardcodeed user/pass/host/port in plan.xml of farming correct ?

[Shawn Jiang]

I'm going to open a JIRA for this with a patch.  Thanks Ginanny.

On Mon, Jun 15, 2009 at 6:50 PM, Gianny Damour <
gianny.dam...@optusnet.com.au> wrote:

> Hi Shawn,
>
> username, password and host should not be in
> config-substitutions.properties.
>
> port is the only candidate and should be set to ${NamingPort + PortOffset}
>
> Thanks,
> Gianny
>
>
> On 15/06/2009, at 6:14 PM, Shawn Jiang wrote:
>
>
>> In  Gtrunk\plugins\clustering\farming\src\main\plan\plan.xml,  there are
>> some  hardcodeed ser/pass/host/port string in it. I'm not sure if they
>> should be something like ${PlanClusterNodeName} so that they can be set in
>> server\config\config_substitution.properties.
>>
>>
>>
>> > class="org.apache.geronimo.farm.config.BasicNodeInfo">
>>  ${PlanClusterNodeName}
>>  
>>  > xmlns:ns="http://geronimo.apache.org/xml/ns/deployment/javabean-1.0";
>> class="org.apache.geronimo.farm.deployment.DeploymentExtendedJMXConnectorInfo">
>>  system
>>  manager
>>  rmi
>>  localhost
>>  1099
>>  JMXConnector
>>  true
>>  
>>  
>>  
>>
>>
>> Can anyone give me any thoughts ?
>>
>> --
>> Shawn
>>
>
>


-- 
Shawn

[jira] Updated: (GERONIMO-4686) No clear hints in startup error when 1050 port is already in use.

[Shawn Jiang (JIRA)]

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

Shawn Jiang updated GERONIMO-4686:
--

Attachment: G4686_trunk_rework.patch
G4686_g21_rework.patch

Thanks Jarek for your comments, here are the updated patches. 

> No clear hints in startup error when 1050 port is already in use.  
> ---
>
> Key: GERONIMO-4686
> URL: https://issues.apache.org/jira/browse/GERONIMO-4686
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: CORBA
>Affects Versions: 1.1.1, 2.0-M1, 2.0-M2, 2.0-M3, 2.0-M4, 2.0-M5, 2.0-M6, 
> 2.0-M7, 2.0, 2.0.1, 2.0.2, 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.1.5, 2.2
>Reporter: Shawn Jiang
>Assignee: Shawn Jiang
>Priority: Minor
> Fix For: 2.1.5, 2.2
>
> Attachments: G4686_g21.patch, G4686_g21_rework.patch, 
> G4686_trunk.patch, G4686_trunk_rework.patch
>
>
> When 1050 is used by other apps.  If you start geronimo, there will be a 
> startup error:
> org.apache.geronimo.corba.security.config.ConfigException: Error starting 
> transient name service 
> at 
> org.apache.geronimo.yoko.ORBConfigAdapter.createNameService(ORBConfigAdapter.java:179)
>  
> at 
> org.apache.geronimo.yoko.ORBConfigAdapter$$FastClassByCGLIB$$76e4a002.invoke()
>  
> at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) 
> at 
> org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:830)
>  
> at 
> org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) 
> at 
> org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
>  
> at 
> org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
>  
> at 
> org.apache.geronimo.corba.security.config.ConfigAdapter$$EnhancerByCGLIB$$3f9e1dfe.createNameService()
>  
> at org.apache.geronimo.corba.NameService.doStart(NameService.java:164) 
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:996)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:268)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:539) 
> at 
> org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
>  
> at 
> org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
>  
> at 
> org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
>  
> at 
> org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:553)
>  
> at 
> org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379)
>  
> at 
> org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:448)
>  
> at 
> org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187)
>  
> at 
> org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:530)
>  
> at 
> org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastClassByCGLIB$$ce77a924.invoke()
>  
> at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) 
> at 
> org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:830)
>  
> at 
> org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) 
> at 
> org.ap

Re: Migration from Tomcat to Geronimo

[Rodger]

Thank you , Shawn. Yes, I have read this doc. Actually, I want to write a
test scenario about this migration. Maybe it's not easy to find a sample
with all these diffs.
-- 
Best Regards,
Rodger.

[BUILD] trunk: Failed for Revision: 785033

[gawor]

Geronimo Revision: 785033 built with tests included
 
See the full build-2100.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090615/build-2100.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090615/unit-test-reports
 
from the specified remote repositories:
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository),
  central (http://repo1.maven.org/maven2)

Path to dependency: 
1) org.apache.geronimo.modules:geronimo-activemq:jar:2.2-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.activemq:activemq-core:jar': Cannot find parent: 
org.apache.activemq:activemq-parent for project: null:activemq-core:bundle:null 
for project null:activemq-core:bundle:null
  org.apache.activemq:activemq-core:jar:5.3-SNAPSHOT

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

Path to dependency: 
1) org.apache.geronimo.modules:geronimo-activemq:jar:2.2-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.activemq:activemq-core:jar': 
Cannot find parent: org.apache.activemq:activemq-parent for project: 
null:activemq-core:bundle:null for project null:activemq-core:bundle:null
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)
... 22 more
Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find 
parent: org.apache.activemq:activemq-parent for project: 
null:activemq-core:bundle:null for project null:activemq-core:bundle:null
at 
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1369)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:820)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.

[BUILD] trunk: Failed for Revision: 784895

[gawor]

Geronimo Revision: 784895 built with tests included
 
See the full build-1500.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090615/build-1500.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090615/unit-test-reports
 
from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository)

Path to dependency: 
1) org.apache.geronimo.modules:geronimo-activemq:jar:2.2-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: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.activemq:activemq-core:jar': Cannot find parent: 
org.apache.activemq:activemq-parent for project: null:activemq-core:bundle:null 
for project null:activemq-core:bundle:null
  org.apache.activemq:activemq-core:jar:5.3-SNAPSHOT

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

Path to dependency: 
1) org.apache.geronimo.modules:geronimo-activemq:jar:2.2-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.activemq:activemq-core:jar': 
Cannot find parent: org.apache.activemq:activemq-parent for project: 
null:activemq-core:bundle:null for project null:activemq-core:bundle:null
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)
... 22 more
Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find 
parent: org.apache.activemq:activemq-parent for project: 
null:activemq-core:bundle:null for project null:activemq-core:bundle:null
at 
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1369)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:820)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.

Re: Update the 2.2 release status page?

[David Jencks]

I made some updates.  I think I'm going to be the release manager  
unless someone else volunteers.


thanks
david jencks

On Jun 15, 2009, at 5:45 AM, Donald Woods wrote:

I saw discussions from David J. that he was planning on branching  
2.2 any day now, so it seems that your targets are too far out.   
Also, we normally don't have a whole quarter between branching and  
releasing, but should be something like one month after a branch for  
the target release.



-Donald


Rex Wang wrote:

HI
I notice a user in mail list who complained that the http://cwiki.apache.org/GMOxPMGT/geronimo-22-release-status.html 
 is out of date.

>Ashwill, Steve (Facilities & Services)
>Hello,
>Can anyone tell me if there is a new roadmap in the works defining  
a release schedule for version 2.2.  We have been developing based  
on the Geronimo 2.2 Release Status(OpenEJB 3.1), but if it will  
>not be released in the next few months we may need to re-factor to  
2.1.4.  Our support folks are a bit hesitant to deploy to  
production using a snapshot version.  I’ve checked http://cwiki.apache.org 
>>>/GMOxPMGT/geronimo-22-release-status.html , but it has not been  
updated in a while.
>Any guessimation as to when and if 2.2 will be released would be  
greatly appreciated.

>Thanks,
>Steve
I think at least the dates following should update, can anyone help?
Release Manager:
Proposed Branch/freeze date: 12/12/08 1/9/09 1Q2009->  3Q2009
Proposed Release Candidate: 1/9/09 1/16/09 1Q2009->  4Q2009
Proposed Release date: 1/15/09 1/30/09 1Q2009->  4Q2009
-Rex

[jira] Commented: (GERONIMO-4628) Console plan wizards need to save plans

[David Jencks (JIRA)]

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

David Jencks commented on GERONIMO-4628:


I'm not sure it will be practical to figure out what an inside plan is in the 
DeploymentGBean.  I'm also not entirely sure we have enough info about where 
the configuration is saved in the DeploymentGBean.  However I think I'd be 
happy for 2.2 if we only saved external plans under META-INF/plan.xml -- 
internal plans are already in the car file in some form.

So, I think this is a great way to proceed.

> Console plan wizards need to save plans
> ---
>
> Key: GERONIMO-4628
> URL: https://issues.apache.org/jira/browse/GERONIMO-4628
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Reporter: David Jencks
>Assignee: Rex Wang
> Fix For: 2.1.5, 2.2
>
>
> Currently we have a lot of console wizards that are great at creating basic 
> plans for datasources, security realms, etc etc.  However once you've 
> deployed the plan through the wizard the plan is gone gone gone never to be 
> seen again.
> The wizards need to do _something_ so the plans are saved on disk somehow.
> One possibliity is that deployment could always save the plan into the car 
> file, like the car-maven-plugin does.  I'm not certain but I think this would 
> fix the admin console wizard problem as well.
> Also it would be very handy if the wizard inserted a comment mentioning the 
> intended target artifact, such as which tranql adapter to use for a 
> datasource plan.
> Furthermore you ought to be able to specify all components of the artifact id 
> (groupId, etc) in all the wizards.  In fact you should be able to set the 
> default groupId for the whole admin console -- probably your company wants 
> all the groupIds the same.

-- 
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: 784443

[gawor]

Geronimo Revision: 784443 built with tests included
 
See the full build-1500.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090615/build-1500.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090615/unit-test-reports
 
1K downloaded
Downloading: 
http://geronimo.zones.apache.org:8081/nexus/content/repositories/geronimo/org/apache/maven/shared/maven-shared-components/6/maven-shared-components-6.pom
Downloading: 
http://repo.exist.com/maven2/org/apache/maven/shared/maven-shared-components/6/maven-shared-components-6.pom
3K downloaded
Downloading: 
http://geronimo.zones.apache.org:8081/nexus/content/repositories/geronimo/org/apache/maven/shared/maven-common-artifact-filters/1.1/maven-common-artifact-filters-1.1.jar
Downloading: 
http://repo.exist.com/maven2/org/apache/maven/shared/maven-common-artifact-filters/1.1/maven-common-artifact-filters-1.1.jar
29K downloaded
Downloading: 
http://geronimo.zones.apache.org:8081/nexus/content/repositories/geronimo/org/codehaus/plexus/plexus-archiver/1.0-alpha-11/plexus-archiver-1.0-alpha-11.jar
Downloading: 
http://repo.exist.com/maven2/org/codehaus/plexus/plexus-archiver/1.0-alpha-11/plexus-archiver-1.0-alpha-11.jar
169K downloaded
Downloading: 
http://geronimo.zones.apache.org:8081/nexus/content/repositories/geronimo/org/codehaus/plexus/plexus-io/1.0-alpha-3/plexus-io-1.0-alpha-3.jar
Full thread dump Java HotSpot(TM) Server VM (1.5.0_12-b04 mixed mode):

"Low Memory Detector" daemon prio=1 tid=0xa0da79c0 nid=0x15b5 runnable 
[0x..0x]

"CompilerThread1" daemon prio=1 tid=0xa0da6588 nid=0x15b4 waiting on condition 
[0x..0xa09f7fd8]

"CompilerThread0" daemon prio=1 tid=0xa0da55b0 nid=0x15b3 waiting on condition 
[0x..0xa0a79158]

"AdapterThread" daemon prio=1 tid=0xa0da45a8 nid=0x15b2 waiting on condition 
[0x..0x]

"Signal Dispatcher" daemon prio=1 tid=0xa0da3750 nid=0x15b1 runnable 
[0x..0x]

"Finalizer" daemon prio=1 tid=0xa0d9a858 nid=0x15b0 in Object.wait() 
[0xa0bfc000..0xa0bfcfb0]
at java.lang.Object.wait(Native Method)
- waiting on <0xb1517cc0> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:116)
- locked <0xb1517cc0> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:132)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)

"Reference Handler" daemon prio=1 tid=0xa0d9a2d0 nid=0x15af in Object.wait() 
[0xa0c7d000..0xa0c7e130]
at java.lang.Object.wait(Native Method)
- waiting on <0xb1516c00> (a java.lang.ref.Reference$Lock)
at java.lang.Object.wait(Object.java:474)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116)
- locked <0xb1516c00> (a java.lang.ref.Reference$Lock)

"main" prio=1 tid=0x09875c28 nid=0x15a5 runnable [0xffe96000..0xffe97788]
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
- locked <0xeda72e28> (a java.net.PlainSocketImpl)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.Socket.connect(Socket.java:519)
at java.net.Socket.connect(Socket.java:469)
at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:382)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:509)
- locked <0xeda72da8> (a sun.net.www.http.HttpClient)
at sun.net.www.http.HttpClient.(HttpClient.java:231)
at sun.net.www.http.HttpClient.New(HttpClient.java:304)
at sun.net.www.http.HttpClient.New(HttpClient.java:316)
at 
sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:813)
at 
sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:765)
at 
sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:690)
at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:934)
- locked <0xeda724a8> (a sun.net.www.protocol.http.HttpURLConnection)
at 
org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:83)
at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:68)
at 
org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:470)
at 
org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:354)
at 
org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager

Re: jaxws 2.2 spec jar....

[Jarek Gawor]

Dan,

Let me know when you think you are done with it and I'll move it to Geronimo.

Thanks for working on this, btw.

Jarek

On Fri, Jun 12, 2009 at 9:58 PM, Daniel Kulp wrote:
> On Fri June 12 2009 5:23:42 pm David Jencks wrote:
>> What would your thought be on moving it to the geronimo spec project
>> once it isn't having daily changes?
>
> Actually, with Dims' help, we're now there.   I ran the tool Harmony used to
> compare API's and we're now 100% compatible with the jaxws 2.2 api jar.  Now,
> that is not the same as running the TCK (which we don't have yet), but
> definitely a promising sign.    I think I want to spend a little time early
> next week adding some javadoc, but then it would be good to move it back to
> geronimo-specs and do an "alpha" release.   (wouldn't call it a 1.0 release
> until we have a tck to test it).
>
> Dan
>
>>
>> I'm planning to release the jaxb 2.1 spec jar soon for geronimo 2.2.
>>
>> thanks
>> david jencks
>>
>> On Jun 12, 2009, at 12:51 PM, Daniel Kulp wrote:
>> > On Fri June 12 2009 3:42:23 pm Davanum Srinivas wrote:
>> >> Thanks Dan, we need it for axis2 as well. Looks like we need 2.2 of
>> >> JAXB as
>> >> well.
>> >
>> > I'm slightly less concerned about JAXB for right now for three
>> > reasons:
>> >
>> > 1) It's available in the Sun maven repos already (and now
>> > central ;-) )
>> >
>> > 2) We never have had a JAXB 2.1 version released yet.   We've always
>> > used the
>> > Sun version anyway.
>> >
>> > 3) We don't have an Apache implementation of JAXB so we need the Sun
>> > implementation anyway.
>> >
>> > Yes, a JAXB 2.2 version would be nice, but not critical right now.
>> > JAX-WS
>> > 2.2 is slightly critical as there isn't a version deployed in maven
>> > that we
>> > can start using as a starting point.   We need SOMETHING that we can
>> > use
>> > pretty much ASAP.
>> >
>> > Dan
>> >
>> >> -- dims
>> >>
>> >> On 06/12/2009 03:35 PM, Daniel Kulp wrote:
>> >>> Just to let everyone know, I've started working on creating a
>> >>> specs jar
>> >>> for jaxws 2.2 in the CXF sandbox:
>> >>>
>> >>> http://svn.apache.org/repos/asf/cxf/sandbox/geronimo-jaxws_2.2_spec/
>> >>>
>> >>> All apache committers can commit there so if anyone wants to help
>> >>> out...
>> >>> ;-)
>> >>>
>> >>> Mostly just wanted to let folks know I've started it so someone else
>> >>> doesn't go off and start it as well.
>> >
>> > --
>> > Daniel Kulp
>> > dk...@apache.org
>> > http://www.dankulp.com/blog
>
> --
> Daniel Kulp
> dk...@apache.org
> http://www.dankulp.com/blog
>

[jira] Reopened: (GERONIMO-4686) No clear hints in startup error when 1050 port is already in use.

[Jarek Gawor (JIRA)]

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

Jarek Gawor reopened GERONIMO-4686:
---


The new error message "Error starting transient name service, Port already in 
use:" could be misleading because the BindException could be raised for a few 
different reasons. Maybe the easiest thing to do is just change the error 
message to "Error starting transient name service on port " + port.


> No clear hints in startup error when 1050 port is already in use.  
> ---
>
> Key: GERONIMO-4686
> URL: https://issues.apache.org/jira/browse/GERONIMO-4686
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: CORBA
>Affects Versions: 1.1.1, 2.0-M1, 2.0-M2, 2.0-M3, 2.0-M4, 2.0-M5, 2.0-M6, 
> 2.0-M7, 2.0, 2.0.1, 2.0.2, 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.1.5, 2.2
>Reporter: Shawn Jiang
>Assignee: Shawn Jiang
>Priority: Minor
> Fix For: 2.1.5, 2.2
>
> Attachments: G4686_g21.patch, G4686_trunk.patch
>
>
> When 1050 is used by other apps.  If you start geronimo, there will be a 
> startup error:
> org.apache.geronimo.corba.security.config.ConfigException: Error starting 
> transient name service 
> at 
> org.apache.geronimo.yoko.ORBConfigAdapter.createNameService(ORBConfigAdapter.java:179)
>  
> at 
> org.apache.geronimo.yoko.ORBConfigAdapter$$FastClassByCGLIB$$76e4a002.invoke()
>  
> at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) 
> at 
> org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:830)
>  
> at 
> org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) 
> at 
> org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
>  
> at 
> org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
>  
> at 
> org.apache.geronimo.corba.security.config.ConfigAdapter$$EnhancerByCGLIB$$3f9e1dfe.createNameService()
>  
> at org.apache.geronimo.corba.NameService.doStart(NameService.java:164) 
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:996)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:268)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:539) 
> at 
> org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
>  
> at 
> org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
>  
> at 
> org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
>  
> at 
> org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:553)
>  
> at 
> org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379)
>  
> at 
> org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:448)
>  
> at 
> org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187)
>  
> at 
> org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:530)
>  
> at 
> org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastClassByCGLIB$$ce77a924.invoke()
>  
> at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) 
> at 
> org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:830)

Re: Update the 2.2 release status page?

[Donald Woods]

I saw discussions from David J. that he was planning on branching 2.2 
any day now, so it seems that your targets are too far out.  Also, we 
normally don't have a whole quarter between branching and releasing, but 
should be something like one month after a branch for the target release.



-Donald


Rex Wang wrote:

HI

I notice a user in mail list who complained that the 
http://cwiki.apache.org/GMOxPMGT/geronimo-22-release-status.html is out 
of date.

 >Ashwill, Steve (Facilities & Services)
 >Hello,
 >Can anyone tell me if there is a new roadmap in the works defining a 
release schedule for version 2.2.  We have been developing based on the 
Geronimo 2.2 Release Status(OpenEJB 3.1), but if it will >not be 
released in the next few months we may need to re-factor to 2.1.4.  Our 
support folks are a bit hesitant to deploy to production using a 
snapshot version.  I’ve checked 
http://cwiki.apache.org>>>/GMOxPMGT/geronimo-22-release-status.html , 
but it has not been updated in a while.
 >Any guessimation as to when and if 2.2 will be released would be 
greatly appreciated.

 >Thanks,
 >Steve

I think at least the dates following should update, can anyone help?
Release Manager:
Proposed Branch/freeze date: 12/12/08 1/9/09 1Q2009->  3Q2009
Proposed Release Candidate: 1/9/09 1/16/09 1Q2009->  4Q2009
Proposed Release date: 1/15/09 1/30/09 1Q2009->  4Q2009


-Rex

Re: Update the 2.2 release status page?

[Juergen Weber]

Hi, 

I think it would be a pity for 2.2 to appear only in 4Q2009 (hope, this
doesn't mean XMas ;-)

Generally, I feel Geronimo's release cycles should be faster:
- Users would get bug fixes much earlier (there appeared several interesting
fixes on the list here in the last weeks)
- there would be more and earlier feedback for new features (and new bugs)
- release early, release often
- the Geronimo web site would show more signs of life and the whole project
would look more active when there are more often News entries
- Getting a new release is like unwrapping a gift 8-)

I am not sure how much more work shorter release cycles would mean for the
Geronimo team. But shouldn't it suffice to automatically build and run the
testsuite, at least for minor releases?

Thanks you,
Juergen




Rex Wang-2 wrote:
> 
> HI
> 
> I notice a user in mail list who complained that the
> http://cwiki.apache.org/GMOxPMGT/geronimo-22-release-status.html is out of
> date.
>>Ashwill, Steve (Facilities & Services)
>>Hello,
>>Can anyone tell me if there is a new roadmap in the works defining a
> release schedule for version 2.2.  We have been developing based on the
> Geronimo 2.2 Release Status(OpenEJB 3.1), but if it will >not be released
> in
> the next few months we may need to re-factor to 2.1.4.  Our support folks
> are a bit hesitant to deploy to production using a snapshot version.  I’ve
> checked
> http://cwiki.apache.org>>>/GMOxPMGT/geronimo-22-release-status.html
> , but it has not been updated in a while.
>>Any guessimation as to when and if 2.2 will be released would be greatly
> appreciated.
>>Thanks,
>>Steve
> 
> I think at least the dates following should update, can anyone help?
> Release Manager:
> Proposed Branch/freeze date: 12/12/08 1/9/09 1Q2009->  3Q2009
> Proposed Release Candidate: 1/9/09 1/16/09 1Q2009->  4Q2009
> Proposed Release date: 1/15/09 1/30/09 1Q2009->  4Q2009
> 
> 
> -Rex
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Update-the-2.2-release-status-page--tp24030920s134p24032328.html
Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.

Re: Are these hardcodeed user/pass/host/port in plan.xml of farming correct ?

[Gianny Damour]

Hi Shawn,

username, password and host should not be in config- 
substitutions.properties.


port is the only candidate and should be set to ${NamingPort +  
PortOffset}


Thanks,
Gianny

On 15/06/2009, at 6:14 PM, Shawn Jiang wrote:



In  Gtrunk\plugins\clustering\farming\src\main\plan\plan.xml,   
there are some  hardcodeed ser/pass/host/port string in it. I'm not  
sure if they should be something like ${PlanClusterNodeName} so  
that they can be set in server\config\config_substitution.properties.




class="org.apache.geronimo.farm.config.BasicNodeInfo">

  ${PlanClusterNodeName}
  
  http://geronimo.apache.org/xml/ 
ns/deployment/javabean-1.0"  
class="org.apache.geronimo.farm.deployment.DeploymentExtendedJMXConnec 
torInfo">

  system
  manager
  rmi
  localhost
  1099
  JMXConnectorns:property>

  true
  
  
  


Can anyone give me any thoughts ?

--
Shawn

Re: Migration from Tomcat to Geronimo

[Shawn Jiang]

Have you ever look at this Doc before ?
http://cwiki.apache.org/confluence/display/GMOxDOC21/Best+Practices+Tomcat+to+Geronimo+Migration

On Mon, Jun 15, 2009 at 5:51 PM, Rodger  wrote:

> I'm summarizing all the modifyings when migrating from tomcat to geronimo.
> As I know, there are:
> 1. datasource configuration in context.xml vs in geronimo-web.xml
> 2. security realm configuration
> 3. Ports configuration in server.xml vs in config.xml
> 4. some other configurations which can be configed in
> /var/catalina/conf/web.xml,such as jsp reloading, persist
> jsp compilation
>
> Any other difference, pls reply.
> --
> Best Regards,
> Rodger.
>



-- 
Shawn

Migration from Tomcat to Geronimo

[Rodger]

I'm summarizing all the modifyings when migrating from tomcat to geronimo.
As I know, there are:
1. datasource configuration in context.xml vs in geronimo-web.xml
2. security realm configuration
3. Ports configuration in server.xml vs in config.xml
4. some other configurations which can be configed in
/var/catalina/conf/web.xml,such as jsp reloading, persist jsp
compilation

Any other difference, pls reply.
-- 
Best Regards,
Rodger.

[jira] Resolved: (GERONIMO-4686) No clear hints in startup error when 1050 port is already in use.

[Ivan (JIRA)]

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

Ivan resolved GERONIMO-4686.


Resolution: Fixed

Commit changes to 2.2 trunk At revision: 784694, and 2.1.5 snapshot At 
revision: 784695.
Thanks, Shawn Jiang !

> No clear hints in startup error when 1050 port is already in use.  
> ---
>
> Key: GERONIMO-4686
> URL: https://issues.apache.org/jira/browse/GERONIMO-4686
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: CORBA
>Affects Versions: 1.1.1, 2.0-M1, 2.0-M2, 2.0-M3, 2.0-M4, 2.0-M5, 2.0-M6, 
> 2.0-M7, 2.0, 2.0.1, 2.0.2, 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.1.5, 2.2
>Reporter: Shawn Jiang
>Assignee: Shawn Jiang
>Priority: Minor
> Attachments: G4686_g21.patch, G4686_trunk.patch
>
>
> When 1050 is used by other apps.  If you start geronimo, there will be a 
> startup error:
> org.apache.geronimo.corba.security.config.ConfigException: Error starting 
> transient name service 
> at 
> org.apache.geronimo.yoko.ORBConfigAdapter.createNameService(ORBConfigAdapter.java:179)
>  
> at 
> org.apache.geronimo.yoko.ORBConfigAdapter$$FastClassByCGLIB$$76e4a002.invoke()
>  
> at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) 
> at 
> org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:830)
>  
> at 
> org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) 
> at 
> org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
>  
> at 
> org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
>  
> at 
> org.apache.geronimo.corba.security.config.ConfigAdapter$$EnhancerByCGLIB$$3f9e1dfe.createNameService()
>  
> at org.apache.geronimo.corba.NameService.doStart(NameService.java:164) 
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:996)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:268)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:539) 
> at 
> org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
>  
> at 
> org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
>  
> at 
> org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
>  
> at 
> org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:553)
>  
> at 
> org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379)
>  
> at 
> org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:448)
>  
> at 
> org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187)
>  
> at 
> org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:530)
>  
> at 
> org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastClassByCGLIB$$ce77a924.invoke()
>  
> at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) 
> at 
> org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:830)
>  
> at 
> org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) 
> at 
> org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
>  
> at 
> org.apache.

[jira] Updated: (GERONIMO-4686) No clear hints in startup error when 1050 port is already in use.

[Ivan (JIRA)]

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

Ivan updated GERONIMO-4686:
---

Fix Version/s: 2.2
   2.1.5

> No clear hints in startup error when 1050 port is already in use.  
> ---
>
> Key: GERONIMO-4686
> URL: https://issues.apache.org/jira/browse/GERONIMO-4686
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: CORBA
>Affects Versions: 1.1.1, 2.0-M1, 2.0-M2, 2.0-M3, 2.0-M4, 2.0-M5, 2.0-M6, 
> 2.0-M7, 2.0, 2.0.1, 2.0.2, 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.1.5, 2.2
>Reporter: Shawn Jiang
>Assignee: Shawn Jiang
>Priority: Minor
> Fix For: 2.1.5, 2.2
>
> Attachments: G4686_g21.patch, G4686_trunk.patch
>
>
> When 1050 is used by other apps.  If you start geronimo, there will be a 
> startup error:
> org.apache.geronimo.corba.security.config.ConfigException: Error starting 
> transient name service 
> at 
> org.apache.geronimo.yoko.ORBConfigAdapter.createNameService(ORBConfigAdapter.java:179)
>  
> at 
> org.apache.geronimo.yoko.ORBConfigAdapter$$FastClassByCGLIB$$76e4a002.invoke()
>  
> at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) 
> at 
> org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:830)
>  
> at 
> org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) 
> at 
> org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
>  
> at 
> org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
>  
> at 
> org.apache.geronimo.corba.security.config.ConfigAdapter$$EnhancerByCGLIB$$3f9e1dfe.createNameService()
>  
> at org.apache.geronimo.corba.NameService.doStart(NameService.java:164) 
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:996)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:268)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:539) 
> at 
> org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
>  
> at 
> org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
>  
> at 
> org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
>  
> at 
> org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:553)
>  
> at 
> org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379)
>  
> at 
> org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:448)
>  
> at 
> org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187)
>  
> at 
> org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:530)
>  
> at 
> org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastClassByCGLIB$$ce77a924.invoke()
>  
> at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) 
> at 
> org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:830)
>  
> at 
> org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) 
> at 
> org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
>  
> at 
> org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercep

[jira] Commented: (GERONIMO-4203) Restarting configurations from the system modules portlet gives erroneous warning message

[Han Hong Fang (JIRA)]

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

Han Hong Fang commented on GERONIMO-4203:
-

Hi,

I can not reproduce the problem described on RHEL 5.2 using either IE or 
firefox.  The geronimo build I used for testing is 20090527, and the jdk is IBM 
Java SDK 6 SR4.  When I restarted the system module. I got the following 
message.

"Restarted application
org.apache.geronimo.framework/plugin/2.2-SNAPSHOT/car"

Could you give more details configuration and steps to reproduce the problem? 

Thanks!

Janet


> Restarting configurations from the system modules portlet gives erroneous 
> warning message
> -
>
> Key: GERONIMO-4203
> URL: https://issues.apache.org/jira/browse/GERONIMO-4203
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.2
> Environment: RHEL 5
>Reporter: Manu T George
>Priority: Minor
>
> If I restart any of the system modules it gives an erroneous warning
> Restarting this component may prevent the server or admin console from 
> functioning properly. As part of the stop action all dependant components and 
> subsequent dependencies will also be stopped. Only this component will be 
> restarted.
> However the restart actually starts all of the dependencies and at the bottom 
> of the screen it shows the dependencies that have been started. 

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

Update the 2.2 release status page?

[Rex Wang]

HI

I notice a user in mail list who complained that the
http://cwiki.apache.org/GMOxPMGT/geronimo-22-release-status.html is out of
date.
>Ashwill, Steve (Facilities & Services)
>Hello,
>Can anyone tell me if there is a new roadmap in the works defining a
release schedule for version 2.2.  We have been developing based on the
Geronimo 2.2 Release Status(OpenEJB 3.1), but if it will >not be released in
the next few months we may need to re-factor to 2.1.4.  Our support folks
are a bit hesitant to deploy to production using a snapshot version.  I’ve
checked http://cwiki.apache.org>>>/GMOxPMGT/geronimo-22-release-status.html
, but it has not been updated in a while.
>Any guessimation as to when and if 2.2 will be released would be greatly
appreciated.
>Thanks,
>Steve

I think at least the dates following should update, can anyone help?
Release Manager:
Proposed Branch/freeze date: 12/12/08 1/9/09 1Q2009->  3Q2009
Proposed Release Candidate: 1/9/09 1/16/09 1Q2009->  4Q2009
Proposed Release date: 1/15/09 1/30/09 1Q2009->  4Q2009


-Rex

[jira] Resolved: (GERONIMO-4679) many [ERROR] "The protocol for the JAR file's URL is not supported" in the build log when building geronimo on windows

[Ivan (JIRA)]

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

Ivan resolved GERONIMO-4679.


Resolution: Fixed

Commit to trunk At revision: 784687, 2.1.5 snapshot At revision: 784688.
Thanks Shawn Jiang for the patch !

> many [ERROR] "The protocol for the JAR file's URL is not supported" in  the 
> build log when building geronimo on windows
> ---
>
> Key: GERONIMO-4679
> URL: https://issues.apache.org/jira/browse/GERONIMO-4679
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: kernel
>Affects Versions: 2.1.1, 2.1.2, 2.1.3, 2.1.4
> Environment: windows + trunk
>Reporter: Shawn Jiang
>Assignee: Shawn Jiang
>Priority: Minor
> Fix For: 2.1.5, 2.2
>
> Attachments: G4679.patch
>
>
> When building the Geronimo from source code on windows.  There are
> many [ERROR] "The protocol for the JAR file's URL is not supported" in
> the build log like following.
> -
> [ERROR] The protocol for the JAR file's URL is not supported
> java.lang.UnsupportedOperationException: Only local file jars are
> supported jar:file:/D:/ws/gtrunck/
> server_repo/org/apache/geronimo/configs/system-database/2.2-SNAPSHOT/
> system-database-2.2-SNAPSHOT.ca
> r!/rar/tranql-connector-1.4.jar
>  
> org.apache.geronimo.kernel.classloader.UrlResourceFinder.cacheUrl(UrlResourceFinder.java:231)
>  
> org.apache.geronimo.kernel.classloader.UrlResourceFinder.rebuildClassPath(UrlResourceFinder.java
> :188)
>  
> org.apache.geronimo.kernel.classloader.UrlResourceFinder.addUrls(UrlResourceFinder.java:142)
>  
> org.apache.geronimo.kernel.classloader.UrlResourceFinder.addUrls(UrlResourceFinder.java:127)
>  
> org.apache.geronimo.kernel.classloader.JarFileClassLoader$2.run(JarFileClassLoader.java:153)
> 
> This message was thrown in  UrlResourceFinder.cacheUrl() and logged as
> ERROR in UrlResourceFinder.rebuildClassPath().
> --
>  } catch (UnsupportedOperationException ex) {
>// the protocol for the JAR file's URL is not
> supported.  This can occur when
>// the jar file is embedded in an EAR or CAR
> file.  Proceed but log the message.
>log.error("The protocol for the JAR file's URL
> is not supported", ex);
>continue;
>}
> -
> We'd better to log this as INFO or DEBUG instead of an ERROR so that the user 
> will not be mislead by a lot of ERRORs in the build log. 

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

[jira] Commented: (GERONIMO-4628) Console plan wizards need to save plans

[Rex Wang (JIRA)]

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

Rex Wang commented on GERONIMO-4628:


Hi David, I'd like to work on this jira and prefer the deployment could always 
save the plan into car file. I think this cound be achieved in the Deployer 
GBean, that is, we can get the plan file either the outside one or the inside 
one and then save it in the META-INF with the uniform name -"plan.xml".
Any thoughts?

-Rex

> Console plan wizards need to save plans
> ---
>
> Key: GERONIMO-4628
> URL: https://issues.apache.org/jira/browse/GERONIMO-4628
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Reporter: David Jencks
>Assignee: Rex Wang
> Fix For: 2.1.5, 2.2
>
>
> Currently we have a lot of console wizards that are great at creating basic 
> plans for datasources, security realms, etc etc.  However once you've 
> deployed the plan through the wizard the plan is gone gone gone never to be 
> seen again.
> The wizards need to do _something_ so the plans are saved on disk somehow.
> One possibliity is that deployment could always save the plan into the car 
> file, like the car-maven-plugin does.  I'm not certain but I think this would 
> fix the admin console wizard problem as well.
> Also it would be very handy if the wizard inserted a comment mentioning the 
> intended target artifact, such as which tranql adapter to use for a 
> datasource plan.
> Furthermore you ought to be able to specify all components of the artifact id 
> (groupId, etc) in all the wizards.  In fact you should be able to set the 
> default groupId for the whole admin console -- probably your company wants 
> all the groupIds the same.

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

[jira] Created: (GERONIMO-4687) System Modules Portlet doesn't list the stopped application names when you stop an application.

[Han Hong Fang (JIRA)]

System Modules Portlet doesn't list the stopped application names when you stop 
an application.
---

 Key: GERONIMO-4687
 URL: https://issues.apache.org/jira/browse/GERONIMO-4687
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: console
Affects Versions: 2.1.4, 2.2
 Environment: Windows XP + IE 7 + IBM JDK 1.5
Reporter: Han Hong Fang
Assignee: Han Hong Fang


When stopping an application, the following msg is showned in the screen.

"Stopped application"

but no application names listed as what starting application msg does.

"Started application

org.apache.geronimo.framework/plugin/2.1.4/car".

The problem only exists in admin console. Command deploy.bat|sh start/stop is 
free of this symptom.

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

Are these hardcodeed user/pass/host/port in plan.xml of farming correct ?

[Shawn Jiang]

In  Gtrunk\plugins\clustering\farming\src\main\plan\plan.xml,  there are
some  hardcodeed ser/pass/host/port string in it. I'm not sure if they
should be something like ${PlanClusterNodeName} so that they can be set in
server\config\config_substitution.properties.




  ${PlanClusterNodeName}
  
  http://geronimo.apache.org/xml/ns/deployment/javabean-1.0";
class="org.apache.geronimo.farm.deployment.DeploymentExtendedJMXConnectorInfo">
  *system*
  *manager*
  rmi
  *localhost*
  *1099*
  JMXConnector
  true
  
  
  


Can anyone give me any thoughts ?

-- 
Shawn

[jira] Assigned: (GERONIMO-4628) Console plan wizards need to save plans

[Rex Wang (JIRA)]

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

Rex Wang reassigned GERONIMO-4628:
--

Assignee: Rex Wang

> Console plan wizards need to save plans
> ---
>
> Key: GERONIMO-4628
> URL: https://issues.apache.org/jira/browse/GERONIMO-4628
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Reporter: David Jencks
>Assignee: Rex Wang
> Fix For: 2.1.5, 2.2
>
>
> Currently we have a lot of console wizards that are great at creating basic 
> plans for datasources, security realms, etc etc.  However once you've 
> deployed the plan through the wizard the plan is gone gone gone never to be 
> seen again.
> The wizards need to do _something_ so the plans are saved on disk somehow.
> One possibliity is that deployment could always save the plan into the car 
> file, like the car-maven-plugin does.  I'm not certain but I think this would 
> fix the admin console wizard problem as well.
> Also it would be very handy if the wizard inserted a comment mentioning the 
> intended target artifact, such as which tranql adapter to use for a 
> datasource plan.
> Furthermore you ought to be able to specify all components of the artifact id 
> (groupId, etc) in all the wizards.  In fact you should be able to set the 
> default groupId for the whole admin console -- probably your company wants 
> all the groupIds the same.

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

Re: Possible for G to directly consume a Tomcat server config w/o changes?

[Ivan]

Tomcat-ext from
https://repository.apache.org/content/repositories/snapshots/org/apache/geronimo/ext/tomcat/
.
I added the url
https://repository.apache.org/content/repositories/snapshotsto
my local pom.xml, then I could build the whole Geronimo server.
By the way, the server failed to start, I am trying to find why.
Thanks !
Ivan

2009/6/15 David Jencks 

>
> On Jun 14, 2009, at 11:15 PM, Ivan wrote:
>
> See, I got those artifacts from that url,
>
>
> which artifacts from which url?
>
> So do we need to add this url to the pom.xml of Geronimo's root folder. I
> found that it is comment out in that file ?
>
>
> Which url?  the apache nexus snapshot repo is already in the apache 6 root
> pom.  It looks like some of the links on the index page at
> http://repository.apache.org/snapshots
> don't work but typing in more of a url seems to get to the right content.
>
> thanks
> david jencks
>
>
>
> Thanks !
> Ivan
>
> 2009/6/15 David Jencks 
>
>>
>> On Jun 14, 2009, at 8:30 PM, Ivan wrote:
>>
>> In which snapshot site, I could find the tomcat build ? I have checked the
>> people, not found.
>>
>>
>>
>> https://repository.apache.org/content/repositories/snapshots/org/apache/geronimo/ext/tomcat/
>>
>> This is in the apache 6 pom... are you having trouble accessing it from
>> china?
>>
>> Then I tried to build them on my local machine, some errors occured, is
>> there any option that I could set ? (I just run 'mvn install')
>>
>>
>> Don't build the archetype directly run ./build-archetype.sh.  It only
>> works on unix like systems.
>>
>> did you check out  this?
>>
>> https://svn.apache.org/repos/asf/geronimo/external/trunk/tomcat-parent-6.0.18
>>
>> For the tomcat-archetype, it said that
>> org.eclipse.jdt:core:jar:3.2.3.v_686_R32x could not be found
>>
>>
>> that's odd, I thought my local nexus found it in maven central repo but
>> it's not there now.  I'll update it to 3.3.0-v_771
>>
>> For the tomcat-parent-6.0.18, it said
>> --->
>> /home/xuhaihong/external/tomcat-parent-6.0.18/catalina/src/main/java/org/apache/catalina/core/DefaultInstanceManager.java:[42,20]
>> package javax.xml.ws does not exist
>>
>>
>> I was compiling on java 6.  I'll add geronimo-jaxws_2.1_spec
>>
>> Thanks for trying it out, let me know if there are more problems!
>> david jencks
>>
>>
>> /home/xuhaihong/external/tomcat-parent-6.0.18/catalina/src/main/java/org/apache/catalina/session/StandardSession.java:[47,26]
>> [deprecation] javax.servlet.http.HttpSessionContext in javax.servlet.http
>> has been deprecated
>>
>> /home/xuhaihong/external/tomcat-parent-6.0.18/catalina/src/main/java/org/apache/catalina/session/StandardSessionFacade.java:[26,26]
>> [deprecation] javax.servlet.http.HttpSessionContext in javax.servlet.http
>> has been deprecated
>>
>> /home/xuhaihong/external/tomcat-parent-6.0.18/catalina/src/main/java/org/apache/catalina/session/StandardSession.java:[268,21]
>> [deprecation] javax.servlet.http.HttpSessionContext in javax.servlet.http
>> has been deprecated
>>
>> /home/xuhaihong/external/tomcat-parent-6.0.18/catalina/src/main/java/org/apache/catalina/session/StandardSessionFacade.java:[104,11]
>> [deprecation] javax.servlet.http.HttpSessionContext in javax.servlet.http
>> has been deprecated
>>
>> /home/xuhaihong/external/tomcat-parent-6.0.18/catalina/src/main/java/org/apache/catalina/core/StandardWrapper.java:[43,21]
>> [deprecation] javax.servlet.SingleThreadModel in javax.servlet has been
>> deprecated
>>
>> /home/xuhaihong/external/tomcat-parent-6.0.18/catalina/src/main/java/org/apache/coyote/Response.java:[477,43]
>> [deprecation] isSpace(char) in java.lang.Character has been deprecated
>>
>> /home/xuhaihong/external/tomcat-parent-6.0.18/catalina/src/main/java/org/apache/catalina/connector/Response.java:[756,47]
>> [deprecation] isSpace(char) in java.lang.Character has been deprecated
>>
>> /home/xuhaihong/external/tomcat-parent-6.0.18/catalina/src/main/java/org/apache/catalina/connector/Connector.java:[1012,36]
>> [deprecation] encode(java.lang.String) in java.net.URLEncoder has been
>> deprecated
>>
>> /home/xuhaihong/external/tomcat-parent-6.0.18/catalina/src/main/java/org/apache/catalina/core/DefaultInstanceManager.java:[263,53]
>> cannot find symbol
>> symbol  : class WebServiceRef
>> location: class org.apache.catalina.core.DefaultInstanceManager
>>
>> /home/xuhaihong/external/tomcat-parent-6.0.18/catalina/src/main/java/org/apache/catalina/core/DefaultInstanceManager.java:[264,20]
>> cannot find symbol
>> symbol  : class WebServiceRef
>> location: class org.apache.catalina.core.DefaultInstanceManager
>>
>> /home/xuhaihong/external/tomcat-parent-6.0.18/catalina/src/main/java/org/apache/catalina/core/DefaultInstanceManager.java:[265,44]
>> cannot find symbol
>> symbol  : class WebServiceRef
>> location: class org.apache.catalina.core.DefaultInstanceManager
>>
>> /home/xuhaihong/external/tomcat-parent-6.0.18/catalina/

[jira] Updated: (GERONIMO-4686) No clear hints in startup error when 1050 port is already in use.

[Shawn Jiang (JIRA)]

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

Shawn Jiang updated GERONIMO-4686:
--

Attachment: G4686_trunk.patch
G4686_g21.patch

Patches for this JIRA.

> No clear hints in startup error when 1050 port is already in use.  
> ---
>
> Key: GERONIMO-4686
> URL: https://issues.apache.org/jira/browse/GERONIMO-4686
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: CORBA
>Affects Versions: 1.1.1, 2.0-M1, 2.0-M2, 2.0-M3, 2.0-M4, 2.0-M5, 2.0-M6, 
> 2.0-M7, 2.0, 2.0.1, 2.0.2, 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.1.5, 2.2
>Reporter: Shawn Jiang
>Assignee: Shawn Jiang
>Priority: Minor
> Attachments: G4686_g21.patch, G4686_trunk.patch
>
>
> When 1050 is used by other apps.  If you start geronimo, there will be a 
> startup error:
> org.apache.geronimo.corba.security.config.ConfigException: Error starting 
> transient name service 
> at 
> org.apache.geronimo.yoko.ORBConfigAdapter.createNameService(ORBConfigAdapter.java:179)
>  
> at 
> org.apache.geronimo.yoko.ORBConfigAdapter$$FastClassByCGLIB$$76e4a002.invoke()
>  
> at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) 
> at 
> org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:830)
>  
> at 
> org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) 
> at 
> org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
>  
> at 
> org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
>  
> at 
> org.apache.geronimo.corba.security.config.ConfigAdapter$$EnhancerByCGLIB$$3f9e1dfe.createNameService()
>  
> at org.apache.geronimo.corba.NameService.doStart(NameService.java:164) 
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:996)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:268)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:539) 
> at 
> org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
>  
> at 
> org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
>  
> at 
> org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
>  
> at 
> org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:553)
>  
> at 
> org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379)
>  
> at 
> org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:448)
>  
> at 
> org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187)
>  
> at 
> org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:530)
>  
> at 
> org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastClassByCGLIB$$ce77a924.invoke()
>  
> at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) 
> at 
> org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
>  
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:830)
>  
> at 
> org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) 
> at 
> org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
>  
> at 
> org.apache.geronimo.kernel.basic.ProxyMethod

[jira] Created: (GERONIMO-4686) No clear hints in startup error when 1050 port is already in use.

[Shawn Jiang (JIRA)]

No clear hints in startup error when 1050 port is already in use.  
---

 Key: GERONIMO-4686
 URL: https://issues.apache.org/jira/browse/GERONIMO-4686
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public (Regular issues)
  Components: CORBA
Affects Versions: 2.1.4, 2.1.3, 2.1.2, 2.1.1, 2.1, 2.0.2, 2.0.1, 2.0, 
2.0-M7, 2.0-M6, 2.0-M5, 2.0-M4, 2.0-M3, 2.0-M2, 2.0-M1, 1.1.1, 2.1.5, 2.2
Reporter: Shawn Jiang
Assignee: Shawn Jiang
Priority: Minor


When 1050 is used by other apps.  If you start geronimo, there will be a 
startup error:

org.apache.geronimo.corba.security.config.ConfigException: Error starting 
transient name service 
at 
org.apache.geronimo.yoko.ORBConfigAdapter.createNameService(ORBConfigAdapter.java:179)
 
at 
org.apache.geronimo.yoko.ORBConfigAdapter$$FastClassByCGLIB$$76e4a002.invoke()
 
at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) 
at 
org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
 
at 
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
 
at 
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:830) 
at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) 
at 
org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
 
at 
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
 
at 
org.apache.geronimo.corba.security.config.ConfigAdapter$$EnhancerByCGLIB$$3f9e1dfe.createNameService()
 
at org.apache.geronimo.corba.NameService.doStart(NameService.java:164) 
at 
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:996)
 
at 
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:268)
 
at 
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
 
at 
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:539) 
at 
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
 
at 
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
 
at 
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
 
at 
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
 
at 
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
 
at 
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
 
at 
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294)
 
at 
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
 
at 
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124)
 
at 
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:553)
 
at 
org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379)
 
at 
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:448)
 
at 
org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187)
 
at 
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:530)
 
at 
org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastClassByCGLIB$$ce77a924.invoke()
 
at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) 
at 
org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
 
at 
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
 
at 
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:830) 
at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) 
at 
org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
 
at 
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
 
at 
org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$236fa26e.startConfiguration()
 
at 
org.apache.geronimo.system.main.EmbeddedDaemon.doStartup(EmbeddedDaemon.java:161)
 
at 
org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:83) 
at 
org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45)
 
at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:67) 
at org.apache.geronimo.cli.da

Re: Possible for G to directly consume a Tomcat server config w/o changes?

[David Jencks]

On Jun 14, 2009, at 11:15 PM, Ivan wrote:


See, I got those artifacts from that url,


which artifacts from which url?

So do we need to add this url to the pom.xml of Geronimo's root  
folder. I found that it is comment out in that file ?


Which url?  the apache nexus snapshot repo is already in the apache 6  
root pom.  It looks like some of the links on the index page at

http://repository.apache.org/snapshots
don't work but typing in more of a url seems to get to the right  
content.


thanks
david jencks




Thanks !
Ivan

2009/6/15 David Jencks 

On Jun 14, 2009, at 8:30 PM, Ivan wrote:

In which snapshot site, I could find the tomcat build ? I have  
checked the people, not found.


https://repository.apache.org/content/repositories/snapshots/org/apache/geronimo/ext/tomcat/

This is in the apache 6 pom... are you having trouble accessing it  
from china?


Then I tried to build them on my local machine, some errors  
occured, is there any option that I could set ? (I just run 'mvn  
install')


Don't build the archetype directly run ./build-archetype.sh.  It  
only works on unix like systems.


did you check out  this?
https://svn.apache.org/repos/asf/geronimo/external/trunk/tomcat-parent-6.0.18

For the tomcat-archetype, it said that org.eclipse.jdt:core:jar: 
3.2.3.v_686_R32x could not be found


that's odd, I thought my local nexus found it in maven central repo  
but it's not there now.  I'll update it to 3.3.0-v_771



For the tomcat-parent-6.0.18, it said
--->
/home/xuhaihong/external/tomcat-parent-6.0.18/catalina/src/main/ 
java/org/apache/catalina/core/DefaultInstanceManager.java:[42,20]  
package javax.xml.ws does not exist


I was compiling on java 6.  I'll add geronimo-jaxws_2.1_spec

Thanks for trying it out, let me know if there are more problems!
david jencks



/home/xuhaihong/external/tomcat-parent-6.0.18/catalina/src/main/ 
java/org/apache/catalina/session/StandardSession.java:[47,26]  
[deprecation] javax.servlet.http.HttpSessionContext in  
javax.servlet.http has been deprecated


/home/xuhaihong/external/tomcat-parent-6.0.18/catalina/src/main/ 
java/org/apache/catalina/session/StandardSessionFacade.java:[26,26]  
[deprecation] javax.servlet.http.HttpSessionContext in  
javax.servlet.http has been deprecated


/home/xuhaihong/external/tomcat-parent-6.0.18/catalina/src/main/ 
java/org/apache/catalina/session/StandardSession.java:[268,21]  
[deprecation] javax.servlet.http.HttpSessionContext in  
javax.servlet.http has been deprecated


/home/xuhaihong/external/tomcat-parent-6.0.18/catalina/src/main/ 
java/org/apache/catalina/session/StandardSessionFacade.java: 
[104,11] [deprecation] javax.servlet.http.HttpSessionContext in  
javax.servlet.http has been deprecated


/home/xuhaihong/external/tomcat-parent-6.0.18/catalina/src/main/ 
java/org/apache/catalina/core/StandardWrapper.java:[43,21]  
[deprecation] javax.servlet.SingleThreadModel in javax.servlet has  
been deprecated


/home/xuhaihong/external/tomcat-parent-6.0.18/catalina/src/main/ 
java/org/apache/coyote/Response.java:[477,43] [deprecation]  
isSpace(char) in java.lang.Character has been deprecated


/home/xuhaihong/external/tomcat-parent-6.0.18/catalina/src/main/ 
java/org/apache/catalina/connector/Response.java:[756,47]  
[deprecation] isSpace(char) in java.lang.Character has been  
deprecated


/home/xuhaihong/external/tomcat-parent-6.0.18/catalina/src/main/ 
java/org/apache/catalina/connector/Connector.java:[1012,36]  
[deprecation] encode(java.lang.String) in java.net.URLEncoder has  
been deprecated


/home/xuhaihong/external/tomcat-parent-6.0.18/catalina/src/main/ 
java/org/apache/catalina/core/DefaultInstanceManager.java:[263,53]  
cannot find symbol

symbol  : class WebServiceRef
location: class org.apache.catalina.core.DefaultInstanceManager

/home/xuhaihong/external/tomcat-parent-6.0.18/catalina/src/main/ 
java/org/apache/catalina/core/DefaultInstanceManager.java:[264,20]  
cannot find symbol

symbol  : class WebServiceRef
location: class org.apache.catalina.core.DefaultInstanceManager

/home/xuhaihong/external/tomcat-parent-6.0.18/catalina/src/main/ 
java/org/apache/catalina/core/DefaultInstanceManager.java:[265,44]  
cannot find symbol

symbol  : class WebServiceRef
location: class org.apache.catalina.core.DefaultInstanceManager

/home/xuhaihong/external/tomcat-parent-6.0.18/catalina/src/main/ 
java/org/apache/catalina/core/DefaultInstanceManager.java:[295,54]  
cannot find symbol

symbol  : class WebServiceRef
location: class org.apache.catalina.core.DefaultInstanceManager

/home/xuhaihong/external/tomcat-parent-6.0.18/catalina/src/main/ 
java/org/apache/catalina/core/DefaultInstanceManager.java:[296,20]  
cannot find symbol

symbol  : class WebServiceRef
location: class org.apache.catalina.core.DefaultInstanceManager

/home/xuhaihong/external/tomcat-parent-6.0.18/catalina/src/main/ 
java/org/apache/catalina/core/DefaultInstanceManager.java:[297,45]  
cannot find symbol

symbol  : class WebServiceRef