[BUILD] trunk: Failed for Revision: 774968
Geronimo Revision: 774968 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090514/build-2100.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090514
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 36 minutes 40 seconds
[INFO] Finished at: Thu May 14 21:39:40 EDT 2009
[INFO] Final Memory: 669M/980M
[INFO]
TESTSUITE RESULTS (Failures only)
=
See detailed results at
http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html
Assembly: tomcat
=
See the full test.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090514/logs-2100-tomcat/test.log
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from codehaus-snapshots
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:41.257
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2-SNAPSHOT/testsuite-2.2-SNAPSHOT.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 36 test builds
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deploy RUNNING
[INFO] commands-testsuite/deploy SUCCESS (0:01:06.300)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:27.896)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:34.046)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:15.640)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:20.989)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:28.563)
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:54.141)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:50.411)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:00:39.716)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:45.343)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:30.978)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:31.024)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:33.533)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:01:03.776)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:57.034)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:52.535)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:27.224)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:50.434)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security FAILURE (0:00:37.388) Java
returned: 1
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:31.423)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5
[jira] Created: (GERONIMO-4631) Installing stuff from the console should let you specify the repo to install into
Installing stuff from the console should let you specify the repo to install into - Key: GERONIMO-4631 URL: https://issues.apache.org/jira/browse/GERONIMO-4631 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Reporter: David Jencks Fix For: 2.1.5, 2.2 deploying from gshell lets you specify the target repo in case there's more than one. We should let you choose in the admin console as well. Same for installing jars... I'm not sure if you can specify the target repo from gshell here. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4630) Need good ways to override env-entry values in jndi
Need good ways to override env-entry values in jndi --- Key: GERONIMO-4630 URL: https://issues.apache.org/jira/browse/GERONIMO-4630 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: general Reporter: David Jencks Currently we have no way to override env-entry values supplied in spec deployment descriptors or annotations. Minimally we need to be able to override them in geronimo plans, I think there's already a jira for that. However people may want to set these from some kind of global configuration file for the server. We need to think up a way to do something like this. One possibility -- not sure how good it is -- would be to have the geronimo plan configure jndii links to global jndi. Then you can put whatever you want in global jndi such as by reading in a property file using a gbean and binding stuff. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4629) Documentation should have instructions on how to deploy lots of datasources that use the same natve libraries
Documentation should have instructions on how to deploy lots of datasources that use the same natve libraries - Key: GERONIMO-4629 URL: https://issues.apache.org/jira/browse/GERONIMO-4629 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: documentation Reporter: David Jencks In order to avoid problems with trying to load the same native library more than once per jvm lifetime, you need to put code that loads native libraries (such as many db drivers) into a classloader plugin that can be shared among all the datasource plugins that need the classes. We need instructions on how to do this in the docs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4628) Console plan wizards need to save plans
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 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] Commented: (GERONIMO-4625) JMS statistics does not work correctly while the server url is of vm protocol
[ https://issues.apache.org/jira/browse/GERONIMO-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709615#action_12709615 ] David Jencks commented on GERONIMO-4625: I think that in j2ca 1.5 admin objects such as queues are not associated with a particular resource adapter, so there is probably no way to get the broker from the client side j2ca configuration. In j2ca 1.6 admin objects can be associated with a resource adapter. Have you checked what the amq web console shows? If you start at the broker you can definitely get statistics. > JMS statistics does not work correctly while the server url is of vm protocol > - > > Key: GERONIMO-4625 > URL: https://issues.apache.org/jira/browse/GERONIMO-4625 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: ActiveMQ >Affects Versions: 2.2 > Environment: WIndows XP > JDK 1.5.0 >Reporter: Ivan >Priority: Minor > > While doing the statistics for queue, we need the name of the broker, so that > we could query the status in the MBeanServer by the borker name, current > codes could not handle the server url like vm://. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4627) Adding virtual host config causes an error message upon server startup
[
https://issues.apache.org/jira/browse/GERONIMO-4627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Louis Savoldy updated GERONIMO-4627:
Fix Version/s: (was: 1.1.2)
> Adding virtual host config causes an error message upon server startup
> --
>
> Key: GERONIMO-4627
> URL: https://issues.apache.org/jira/browse/GERONIMO-4627
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
>Affects Versions: 2.1.1, 2.1.2
> Environment: Both WinXP and Redhat
>Reporter: Louis Savoldy
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> When adding a virtual host to the /var/config/config.xml, I
> get the following error upon server startup:
> Module 15/72 org.apache.geronimo.configs/tomcat6/2.1.4/car
> 2009-05-14 09:53:20,386 ERROR [JAASRealm] Class
> org.apache.geronimo.security.realm.providers.GeronimoUserPrincipal not found!
> Class not added.
> 2009-05-14 09:53:20,387 ERROR [JAASRealm] Class
> org.apache.geronimo.security.realm.providers.GeronimoGroupPrincipal not
> found! Class not added.
> started in 1.268s
> If I remove the virtual host configuration, the error is gone.
> Here is an example of xml config that was added.
> {code:xml}
> name="org.apache.geronimo.configs/tomcat6/2.1.4/car?ServiceModule=org.apache.geronimo.configs/tomcat6/2.1.4/car,j2eeType=Host,name=virtual-host-1"
> gbeanInfo="org.apache.geronimo.tomcat.HostGBean">
> name="className">org.apache.catalina.core.StandardHost
> name=foo-1.domain.org
> appBase=
> workDir=work
> name="aliases">foo-2.domain.org,foo-3.domain.org
>
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4627) Adding virtual host config causes an error message upon server startup
Adding virtual host config causes an error message upon server startup
--
Key: GERONIMO-4627
URL: https://issues.apache.org/jira/browse/GERONIMO-4627
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Affects Versions: 2.1.2, 2.1.1
Environment: Both WinXP and Redhat
Reporter: Louis Savoldy
Fix For: 1.1.2
When adding a virtual host to the /var/config/config.xml, I get
the following error upon server startup:
Module 15/72 org.apache.geronimo.configs/tomcat6/2.1.4/car
2009-05-14 09:53:20,386 ERROR [JAASRealm] Class
org.apache.geronimo.security.realm.providers.GeronimoUserPrincipal not found!
Class not added.
2009-05-14 09:53:20,387 ERROR [JAASRealm] Class
org.apache.geronimo.security.realm.providers.GeronimoGroupPrincipal not found!
Class not added.
started in 1.268s
If I remove the virtual host configuration, the error is gone.
Here is an example of xml config that was added.
{code:xml}
org.apache.catalina.core.StandardHost
name=foo-1.domain.org
appBase=
workDir=work
foo-2.domain.org,foo-3.domain.org
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: svn commit: r774794 - /geronimo/sandbox/blueprint/blueprint-core/src/main/java/org/apache/geronimo/blueprint/context/ReferenceRecipe.java
See UnaryServiceReferenceRecipe.internalCreate()
Jarek
On Thu, May 14, 2009 at 11:35 AM, Guillaume Nodet wrote:
> Where is that done ? The only reference to
> ServiceReferenceAccessor#getServiceReference() comes from the
> ReferenceRecipe which will not be used when using constructor
> arguments or even when using something like;
>
>
>
>
>
>
>
> Do I miss something ? I'll try to fix the integration tests which are
> broken for some reason and add a test there, but any insight would be
> nice.
>
> 2009/5/14 gawor :
>> Author: gawor
>> Date: Thu May 14 14:48:00 2009
>> New Revision: 774794
>>
>> URL: http://svn.apache.org/viewvc?rev=774794&view=rev
>> Log:
>> fix the todo as ServiceReference conversion is supported for direct and
>> indirect injections
>>
>> Modified:
>>
>> geronimo/sandbox/blueprint/blueprint-core/src/main/java/org/apache/geronimo/blueprint/context/ReferenceRecipe.java
>>
>> Modified:
>> geronimo/sandbox/blueprint/blueprint-core/src/main/java/org/apache/geronimo/blueprint/context/ReferenceRecipe.java
>> URL:
>> http://svn.apache.org/viewvc/geronimo/sandbox/blueprint/blueprint-core/src/main/java/org/apache/geronimo/blueprint/context/ReferenceRecipe.java?rev=774794&r1=774793&r2=774794&view=diff
>> ==
>> ---
>> geronimo/sandbox/blueprint/blueprint-core/src/main/java/org/apache/geronimo/blueprint/context/ReferenceRecipe.java
>> (original)
>> +++
>> geronimo/sandbox/blueprint/blueprint-core/src/main/java/org/apache/geronimo/blueprint/context/ReferenceRecipe.java
>> Thu May 14 14:48:00 2009
>> @@ -116,9 +116,7 @@
>> Recipe recipe = (Recipe) object;
>> object = recipe.create(expectedType, false);
>> } else if (isServiceReferenceInjection(object, expectedType)) {
>> - // TODO: I don't think this is sufficient as the reference
>> injection may be done by
>> - // TODO: having a direct dependency on the service and not
>> go through a element
>> - // TODO: the conversion has to be done by the conversion
>> service imho
>> + // TODO: this conversion might potentially be done via
>> conversion service
>> object = ((ServiceReferenceAccessor)
>> object).getServiceReference();
>> }
>> }
>>
>>
>>
>
>
>
> --
> Cheers,
> Guillaume Nodet
>
> Blog: http://gnodet.blogspot.com/
>
> Open Source SOA
> http://fusesource.com
>
Re: svn commit: r774794 - /geronimo/sandbox/blueprint/blueprint-core/src/main/java/org/apache/geronimo/blueprint/context/ReferenceRecipe.java
Where is that done ? The only reference to
ServiceReferenceAccessor#getServiceReference() comes from the
ReferenceRecipe which will not be used when using constructor
arguments or even when using something like;
Do I miss something ? I'll try to fix the integration tests which are
broken for some reason and add a test there, but any insight would be
nice.
2009/5/14 gawor :
> Author: gawor
> Date: Thu May 14 14:48:00 2009
> New Revision: 774794
>
> URL: http://svn.apache.org/viewvc?rev=774794&view=rev
> Log:
> fix the todo as ServiceReference conversion is supported for direct and
> indirect injections
>
> Modified:
>
> geronimo/sandbox/blueprint/blueprint-core/src/main/java/org/apache/geronimo/blueprint/context/ReferenceRecipe.java
>
> Modified:
> geronimo/sandbox/blueprint/blueprint-core/src/main/java/org/apache/geronimo/blueprint/context/ReferenceRecipe.java
> URL:
> http://svn.apache.org/viewvc/geronimo/sandbox/blueprint/blueprint-core/src/main/java/org/apache/geronimo/blueprint/context/ReferenceRecipe.java?rev=774794&r1=774793&r2=774794&view=diff
> ==
> ---
> geronimo/sandbox/blueprint/blueprint-core/src/main/java/org/apache/geronimo/blueprint/context/ReferenceRecipe.java
> (original)
> +++
> geronimo/sandbox/blueprint/blueprint-core/src/main/java/org/apache/geronimo/blueprint/context/ReferenceRecipe.java
> Thu May 14 14:48:00 2009
> @@ -116,9 +116,7 @@
> Recipe recipe = (Recipe) object;
> object = recipe.create(expectedType, false);
> } else if (isServiceReferenceInjection(object, expectedType)) {
> - // TODO: I don't think this is sufficient as the reference
> injection may be done by
> - // TODO: having a direct dependency on the service and not
> go through a element
> - // TODO: the conversion has to be done by the conversion
> service imho
> + // TODO: this conversion might potentially be done via
> conversion service
> object = ((ServiceReferenceAccessor)
> object).getServiceReference();
> }
> }
>
>
>
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
[jira] Created: (GERONIMO-4626) Tomcat Clustering with WADI - JSESSIONID with jvmRoute to support mod_jk routing
Tomcat Clustering with WADI - JSESSIONID with jvmRoute to support mod_jk routing Key: GERONIMO-4626 URL: https://issues.apache.org/jira/browse/GERONIMO-4626 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: Clustering Affects Versions: 2.1.4 Reporter: Gianny Damour Assignee: Gianny Damour It is not possible to fulfill session affinity with Apache mod_jk as the value of the JSESSIONID cookie does not embed a jvmRoute. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4524) Can't start the 2.2 server with Sun JDK 1.5, IBM JDK 1.5, or IBM JDK 6.0.
[ https://issues.apache.org/jira/browse/GERONIMO-4524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang closed GERONIMO-4524. - Resolution: Fixed Fix Version/s: 2.2 Can't reproduce this. Closing it. > Can't start the 2.2 server with Sun JDK 1.5, IBM JDK 1.5, or IBM JDK 6.0. > - > > Key: GERONIMO-4524 > URL: https://issues.apache.org/jira/browse/GERONIMO-4524 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: startup/shutdown >Affects Versions: 2.2 > Environment: Windows XP + IBM JDK 1.5 > Windows XP + SUN JDK 1.5 > Windows XP + IBM JDK 6.0 >Reporter: Shawn Jiang >Priority: Blocker > Fix For: 2.2 > > > I can only start the server successfully with SUN JDK 6.0. Or there will be > exceptions thrown: > * For *JDK 1.5*, the exceptions was > - > Could not load gbean > org.apache.geronimo.framework/j2ee-security/2.2-SNAPSHOT/car?ServiceModule=org.apache.geronimo.framework/j2ee-security/2.2-SNAPSHOT/car,j2eeType=GBean,name=LoginConfiguration > org.apache.geronimo.gbean.InvalidConfigurationException: Could not load > attribute class: javax.security.auth.login.Configuration$Parameters > at > org.apache.geronimo.gbean.runtime.GBeanAttribute.(GBeanAttribute.java:199) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.buildAttributes(GBeanInstance.java:366) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.(GBeanInstance.java:240) > .. > Caused by: java.lang.ClassNotFoundException: Could not load class > javax.security.auth.login.Configuration$Parameters from classloader: > org.apache.geronimo.framework/j2ee-security/2.2-SNAPSHOT/car, destroyed > state: false > at > org.apache.geronimo.kernel.ClassLoading.loadClass(ClassLoading.java:213) > at > org.apache.geronimo.gbean.runtime.GBeanAttribute.(GBeanAttribute.java:197) > ... 22 more > * For *IBM JDK 6.0* , the exception was: > -- > ERROR [GBeanInstanceState] Error while starting; GBean is now in the FAILED > state: > abstractName="org.apache.geronimo.configs/activemq-broker/2.2-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/activemq-broker/2.2-SNAPSHOT/car,j2eeType=JMSServer,name=DefaultActiveMQBroker" > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'org.apache.activemq.xbean.XBeanBrokerService#0' defined in file > [C:\geronimo-tomcat6-javaee5-2.2-SNAPSHOT\var\activemq\conf\activemq.xml]: > Cannot create inner bean '(inner bean)' of type > [org.apache.activemq.store.amq.AMQPersistenceAdapter] while setting bean > property 'persistenceAdapter'; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name '(inner bean)#3' defined in file > [C:\geronimo-tomcat6-javaee5-2.2-SNAPSHOT\var\activemq\conf\activemq.xml]: > Initialization of bean failed; nested exception is > java.lang.UnsatisfiedLinkError: > com/ibm/jvm/ClassLoader.getClassContext()[Ljava/lang/Class; > at > org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:230) > at > org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:122) > . > Caused by: org.springframework.beans.factory.BeanCreationException: Error > creating bean with name '(inner bean)#3' defined in file > [C:\geronimo-tomcat6-javaee5-2.2-SNAPSHOT\var\activemq\conf\activemq.xml]: > Initialization of bean failed; nested exception is > java.lang.UnsatisfiedLinkError: > com/ibm/jvm/ClassLoader.getClassContext()[Ljava/lang/Class; > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:480) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409) > at > java.security.AccessController.doPrivileged(AccessController.java:224) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380) > at > org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:219) > ... 53 more > Caused by: java.lang.UnsatisfiedLinkError: > com/ibm/jvm/ClassLoader.getClassContext()[Ljava/lang/Class; > at com.ibm.jvm.ClassLoader.getLastClassLoader(ClassLoader.java:55) > at java.net.URL.getURLStreamHandler(URL.java:1141) > at java.net.URL.(URL.java:572) >
[jira] Closed: (GERONIMO-4499) can't use PortOffset in var\config\config-substitutions.properties to start two geronimo instance at the same machine.
[ https://issues.apache.org/jira/browse/GERONIMO-4499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang closed GERONIMO-4499. - Resolution: Fixed Fix Version/s: 2.2 Can't reproduce this with the latest build. Closing it. > can't use PortOffset in var\config\config-substitutions.properties to start > two geronimo instance at the same machine. > -- > > Key: GERONIMO-4499 > URL: https://issues.apache.org/jira/browse/GERONIMO-4499 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: ActiveMQ >Affects Versions: 2.2 > Environment: Windows XP SP 2 + IBM SDK 1.5.0 >Reporter: Shawn Jiang >Priority: Minor > Fix For: 2.2 > > > I'm trying to use PortOffset in var\config\config-substitutions.properties to > start two geronimo instance at the same machine. > 1, install two geronimo server serverA, serverB. > 2, update the PortOffset in var\config\config-substitutions.properties from 0 > to 10 for serverB. > 3, start serverA. > 4, start serverB. > *expected result*: Both serverA and serverB could be started without > problems. > *actual result*: serverA started, but server B failed to start with a > exception below in log: > - > 2009-01-07 17:23:08,562 ERROR [BrokerService] Failed to start ActiveMQ JMS > Message Broker. Reason: java.io.IOException: Transport Connector could not be > registered in JMX: Failed to bind to server socket: tcp://localhost:61616 due > to: java.net.BindException: Address already in use: JVM_Bind > java.io.IOException: Transport Connector could not be registered in JMX: > Failed to bind to server socket: tcp://localhost:61616 due to: > java.net.BindException: Address already in use: JVM_Bind > at > org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:27) > at > org.apache.activemq.broker.BrokerService.registerConnectorMBean(BrokerService.java:1427) > at > org.apache.activemq.broker.BrokerService.startTransportConnector(BrokerService.java:1886) > at > org.apache.activemq.broker.BrokerService.startAllConnectors(BrokerService.java:1837) > at > org.apache.activemq.broker.BrokerService.start(BrokerService.java:473) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4532) Port the GERONIMO-4484 patch for V2.1
[ https://issues.apache.org/jira/browse/GERONIMO-4532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kan Ogawa updated GERONIMO-4532: Attachment: sysdb-portlets.patch plugin-portlets.patch plancreator-portlets.patch > Port the GERONIMO-4484 patch for V2.1 > - > > Key: GERONIMO-4532 > URL: https://issues.apache.org/jira/browse/GERONIMO-4532 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4 >Reporter: Kan Ogawa >Assignee: Kan Ogawa >Priority: Minor > Attachments: console-core.patch, console-portal-driver.patch, > debugviews-portlets.patch, plancreator-portlets.patch, plugin-portlets.patch, > sysdb-portlets.patch > > > I think that this issue is very important. > After the GERONIMO-4485 patches are committed, I will try to port > GERONIMO-4484 patches for 2.1 version. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4532) Port the GERONIMO-4484 patch for V2.1
[ https://issues.apache.org/jira/browse/GERONIMO-4532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kan Ogawa updated GERONIMO-4532: Attachment: console-core.patch > Port the GERONIMO-4484 patch for V2.1 > - > > Key: GERONIMO-4532 > URL: https://issues.apache.org/jira/browse/GERONIMO-4532 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4 >Reporter: Kan Ogawa >Assignee: Kan Ogawa >Priority: Minor > Attachments: console-core.patch, console-portal-driver.patch, > debugviews-portlets.patch > > > I think that this issue is very important. > After the GERONIMO-4485 patches are committed, I will try to port > GERONIMO-4484 patches for 2.1 version. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4532) Port the GERONIMO-4484 patch for V2.1
[ https://issues.apache.org/jira/browse/GERONIMO-4532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kan Ogawa updated GERONIMO-4532: Attachment: (was: sysdb-portlets.patch) > Port the GERONIMO-4484 patch for V2.1 > - > > Key: GERONIMO-4532 > URL: https://issues.apache.org/jira/browse/GERONIMO-4532 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4 >Reporter: Kan Ogawa >Assignee: Kan Ogawa >Priority: Minor > Attachments: console-core.patch, console-portal-driver.patch, > debugviews-portlets.patch > > > I think that this issue is very important. > After the GERONIMO-4485 patches are committed, I will try to port > GERONIMO-4484 patches for 2.1 version. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4532) Port the GERONIMO-4484 patch for V2.1
[ https://issues.apache.org/jira/browse/GERONIMO-4532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kan Ogawa updated GERONIMO-4532: Attachment: (was: console-core.patch) > Port the GERONIMO-4484 patch for V2.1 > - > > Key: GERONIMO-4532 > URL: https://issues.apache.org/jira/browse/GERONIMO-4532 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4 >Reporter: Kan Ogawa >Assignee: Kan Ogawa >Priority: Minor > Attachments: console-portal-driver.patch, debugviews-portlets.patch, > sysdb-portlets.patch > > > I think that this issue is very important. > After the GERONIMO-4485 patches are committed, I will try to port > GERONIMO-4484 patches for 2.1 version. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4532) Port the GERONIMO-4484 patch for V2.1
[ https://issues.apache.org/jira/browse/GERONIMO-4532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kan Ogawa updated GERONIMO-4532: Attachment: (was: plancreator-portlets.patch) > Port the GERONIMO-4484 patch for V2.1 > - > > Key: GERONIMO-4532 > URL: https://issues.apache.org/jira/browse/GERONIMO-4532 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4 >Reporter: Kan Ogawa >Assignee: Kan Ogawa >Priority: Minor > Attachments: console-portal-driver.patch, debugviews-portlets.patch, > sysdb-portlets.patch > > > I think that this issue is very important. > After the GERONIMO-4485 patches are committed, I will try to port > GERONIMO-4484 patches for 2.1 version. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4532) Port the GERONIMO-4484 patch for V2.1
[ https://issues.apache.org/jira/browse/GERONIMO-4532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kan Ogawa updated GERONIMO-4532: Attachment: (was: plugin-portlets.patch) > Port the GERONIMO-4484 patch for V2.1 > - > > Key: GERONIMO-4532 > URL: https://issues.apache.org/jira/browse/GERONIMO-4532 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4 >Reporter: Kan Ogawa >Assignee: Kan Ogawa >Priority: Minor > Attachments: console-portal-driver.patch, debugviews-portlets.patch, > sysdb-portlets.patch > > > I think that this issue is very important. > After the GERONIMO-4485 patches are committed, I will try to port > GERONIMO-4484 patches for 2.1 version. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4602) Unexpected tomcat session destroy in the server container while the client is stil alive
[ https://issues.apache.org/jira/browse/GERONIMO-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Cai closed GERONIMO-4602. -- Resolution: Cannot Reproduce Unable to reproduce the problem now. Close it. > Unexpected tomcat session destroy in the server container while the client is > stil alive > > > Key: GERONIMO-4602 > URL: https://issues.apache.org/jira/browse/GERONIMO-4602 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Tomcat >Affects Versions: 2.1.5 > Environment: Windows/Linux, FireFox/IE, IBM Java 5 >Reporter: Jack Cai >Assignee: Jack Cai >Priority: Critical > > After logging in the admin console, and keep refreshing the welcome page, at > some random point (usually less than 100 times of refreshing), the user is > unexpectedly logged out and redirected to the login form. I can see that the > original session is destoryed in the server container. > This could be a problem in Tomcat. I need to look deeper into it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
