[jira] [Closed] (GERONIMODEVTOOLS-751) No keys of Keyboard can jump out of the input box
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tina Li closed GERONIMODEVTOOLS-751. verified on build 20110531125652 No keys of Keyboard can jump out of the input box - Key: GERONIMODEVTOOLS-751 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-751 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Environment: windows xp x86-32 ,eclipse 3.6 SR1,IBM jdk6 Reporter: Tina Li Assignee: Yi Xiao Priority: Trivial Fix For: 3.0 Attachments: 1.1Keyboard access problem.JPG 1.Install gep 3.0-snapshot via deployable way 2.Create a new server using gep3.0 and the May 19 's build of geronimo server-3.0 snapshot 3.Using Jaws to read the Overviewinfo of this server, then found the accessibility problem:no keys of Keyboard can jump out of the input box 4.1.1Keyboard access problem.JPG is attached for detail. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[BUILD] trunk: Failed for Revision: 1130420
Geronimo Revision: 1130420 built with tests included
See the full build-0300.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20110602/build-0300.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20110602/unit-test-reports
T E S T S
---
There are no tests to run.
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO] [bundle:bundle {execution: default-bundle}]
[INFO] [geronimo-osgi:verify-manifest {execution: verify-manifest}]
[INFO] Resolving OSGi bundle: org.apache.geronimo.framework.geronimo-obr
[INFO] OSGi bundle is resolved: org.apache.geronimo.framework.geronimo-obr
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] Checking legal files in: geronimo-obr-3.0-SNAPSHOT.jar
[INFO] [install:install {execution: default-install}]
[INFO] Installing
/home/geronimo/geronimo/trunk/framework/modules/geronimo-obr/target/geronimo-obr-3.0-SNAPSHOT.jar
to
/home/geronimo/.m2/repository/org/apache/geronimo/framework/geronimo-obr/3.0-SNAPSHOT/geronimo-obr-3.0-SNAPSHOT.jar
[INFO] [bundle:install {execution: default-install}]
[INFO] Parsing file:/home/geronimo/.m2/repository/repository.xml
[INFO] Installing
org/apache/geronimo/framework/geronimo-obr/3.0-SNAPSHOT/geronimo-obr-3.0-SNAPSHOT.jar
[INFO] Writing OBR metadata
[INFO]
[INFO] Building Geronimo Framework, Modules :: Deployment
[INFO]task-segment: [install]
[INFO]
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/src/main/resources
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 33 source files to
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/target/classes
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/src/test/resources
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/src/test/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Compiling 2 source files to
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/target/test-classes
[INFO] [surefire:test {execution: default-test}]
[INFO] Surefire report directory:
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/target/surefire-reports
---
T E S T S
---
Running org.apache.geronimo.deployment.SingleFileHotDeployerTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.164 sec
Running org.apache.geronimo.deployment.DeploymentContextTest
Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.037 sec
FAILURE!
Results :
Failed tests:
testMainfestClassPath3(org.apache.geronimo.deployment.DeploymentContextTest)
Tests run: 13, Failures: 1, Errors: 0, Skipped: 0
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] There are test failures.
Please refer to
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/target/surefire-reports
for the individual test results.
[INFO]
[INFO] Trace
org.apache.maven.BuildFailureException: There are test failures.
Please refer to
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/target/surefire-reports
for the individual test results.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:715)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java
[jira] [Commented] (GERONIMODEVTOOLS-757) Karaf shell still working after stopped geronimo server through GEP and error happened when excute geronimo server related commands
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13042668#comment-13042668 ] Yi Xiao commented on GERONIMODEVTOOLS-757: -- Tina, I've traced the code and find the GEP's shutdown method invokes the JMX remoting method to shutdown server finally! So, I'm not sure whether it's the server's problem. Also, I test the GEP3 Server2.2.1, gep could not turn off the server correctly! Could you pls test the scenario under GEP2.2.1 Server2.2.1? thanks~ Karaf shell still working after stopped geronimo server through GEP and error happened when excute geronimo server related commands --- Key: GERONIMODEVTOOLS-757 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-757 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Environment: geronimo server build: 2011.05.25-3.0 snapshot Gep version:Build id: 20110531125652 Eclipse:Helios Service Release 1 JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr9-20110203_74623 (JIT enabled, AOT enabled) Reporter: Tina Li Priority: Minor 1.Start geronimo server using command: geronimo run 2.Create a dynamic web project named testWeb and create an html file named index.html and add the text Helloļ¼ inside the body section 3.Right-click this project and choose Run As--Run on server, create the server runtime using jdk 6 and geronimo 3.0 snapshot 4.Delete the created server and make sure the checkbox Delete running servers and Stop server(s) before deleting choosed when the Delete Server dialog pops up. 5.Then find the server has stopped but karaf shell still working. 6.Input geronimo server related commands such as deploy:list-modules,then error happened: Error executing command: GBean is not running: org.apache.geronimo.configs/conne ctor-deployer-1_6/3.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/con nector-deployer-1_6/3.0-SNAPSHOT/car,j2eeType=DeploymentConfigurer,name=RARConfi gurer -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-752) Fail to start server in profile mode
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13042685#comment-13042685 ] Yi Xiao commented on GERONIMODEVTOOLS-752: -- Viola, the root cause is that the start command could not start server correctly under IBM jdk at server side. Fail to start server in profile mode Key: GERONIMODEVTOOLS-752 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-752 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Environment: winxp, ibm jdk 1.6 Reporter: viola.lu Priority: Minor Fix For: 3.0 1.Install geronimo eclipse plugin 2.New a server, right-click server, choose profile, fail to start server. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-5991) org.apache.myfaces.el.VariableResolverImpl throws java.lang.IllegalStateException when it unsets the scope as null
org.apache.myfaces.el.VariableResolverImpl throws java.lang.IllegalStateException when it unsets the scope as null -- Key: GERONIMO-5991 URL: https://issues.apache.org/jira/browse/GERONIMO-5991 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: myfaces Affects Versions: 2.1.7 Environment: Linux Apache Geronimo 2.1.7 Reporter: Mohan Reddy Fix For: 2.1.8 The following issue has been reported in MyFaces community under JIRA MYFACES-3166. This Geronimo JIRA is created to track the fix integration into geronimo. I am running an application in Geronimo 2.1.7 that requires valid scope and it fails with the following exception Servlet.service() for servlet jsp threw exception java.lang.IllegalStateException: unknown scope defined: null at org.apache.myfaces.el.VariableResolverImpl.resolveVariable(VariableResol verImpl.java:71) at org.apache.myfaces.el.convert.VariableResolverToELResolver.getValue(Vari ableResolverToELResolver.java:93) at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) --- --- Servlet.service() for servlet jsp threw exception java.lang.NullPointerException at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) at org.apache.myfaces.el.unified.resolver.FacesCompositeELResolver.access$3 01(FacesCompositeELResolver.java:46) at org.apache.myfaces.el.unified.resolver.FacesCompositeELResolver$4.invoke (FacesCompositeELResolver.java:108) at org.apache.myfaces.el.unified.resolver.FacesCompositeELResolver.invoke(F acesCompositeELResolver.java:148) at org.apache.myfaces.el.unified.resolver.FacesCompositeELResolver.getValue (FacesCompositeELResolver.java:104) at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-5987) The ActiveMQ working directory and port are not referenced correctly - multiple instances not possible
[
https://issues.apache.org/jira/browse/GERONIMO-5987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Russell E Glaue updated GERONIMO-5987:
--
Description:
I am testing with geronimo-tomcat7-javaee6-web-3.0-SNAPSHOT,
geronimo-tomcat7-javaee6-web-3.0-20110523.171218-97
ActiveMQ is configured to run as org.apache.geronimo.home.dir/var/activemq
and port 61616, and does not cooperate with multi-server configurations, nor
does it use the PortOffset. This is the use of the
org.apache.geronimo.server.name option and PortOffset in
var/config/config-substitutions.properties. (see:
https://cwiki.apache.org/GMOxDOC30/running-multiple-geronimo-instances.html)
First, Problem with working directory
When wanting to run more than a single server instance, the ActiveMQ startup
will block waiting for the lock file $GERONIMO_HOME/var/activemq/lock to
become available.
Obviously this causes any server instance started after the first server
instance is started to block during startup while waiting for the lock file to
become available.
Second, Problem with PortOffset
When configuring the PortOffset in
var/config/config-substitutions.properties, all Geroniomo components expect
and attempt to connect to ActiveMQ at the port {ActiveMQ + PortOffset}.
However, regardless of what you set the PortOffset to be, the ActiveMQ service
only ever binds to port 61616, the default configured port (or whatever you
have the port set as for this service).
Steps to repeat working directory problem:
1. Download and unpack G3.0 SNAPSHOT (3.0-20110523 tested)
2. Create the server instances:
-- 2A. cd ${GERONIMO_HOME}
-- 2B-1. mkdir gserver1
-- 2B-2. cp -rp var gserver1/
-- 2B-3. cp -rp etc gserver1/
-- 2B-4. cp -rp repository gserver1/
3. update the PortOffset parameter in
gserver1/var/config/config-substitutions.properties for the gserver1 instance.
4. Start the default instance and gserver1 instance:
-- bin/startup
-- env GERONIMO_OPTS=-Dorg.apache.geronimo.server.name=gserver2 bin/startup
5. `tail -f gserver1/var/logs/geronimo.log` and you will see this as the last
line that outputs:
2011-05-31 16:26:39,609 WARN [AMQPersistenceAdapter] Waiting to Lock the
Store var/activemq
The server waits here indefinitely.
6. Shutdown the default instance and you will see the gserver1 instance
continue on in the startup procedures. (of course you will see errors due to
the PortOffset problem)
* When I first start the gserver1 instance, the directory
org.apache.geronimo.home.dir/var/activemq is created and populated. Instead
it should be
org.apache.geronimo.home.dir/org.apache.geronimo.server.name/var/activemq
that is created and populated.
* Probably the patch should be to reference the ActiveMQ working directory as
org.apache.geronimo.server.dir/var/activemq
Steps to repeat PortOffset problem:
1. Download and unpack G3.0 SNAPSHOT (3.0-20110523 tested)
2. Create the server instances:
-- 2A. cd ${GERONIMO_HOME}
-- 2B-1. mkdir gserver1
-- 2B-2. cp -rp var gserver1/
-- 2B-3. cp -rp etc gserver1/
-- 2B-4. cp -rp repository gserver1/
3. update the PortOffset parameter in
gserver1/var/config/config-substitutions.properties in the instance
4. Start the server instance:
-- env GERONIMO_OPTS=-Dorg.apache.geronimo.server.name=gserver1 bin/startup
This is the two error messages you receive when configuring PortOffset to 100
(for example). The second error message, regarding XAResource, repeats:
-
2011-06-01 16:26:49,883 ERROR [MCFConnectionInterceptor] Error occurred creating
ManagedConnection for handle: nullManagedConnectionInfo:
org.apache.geronimo.connector.outbound.ManagedConnectionInfo@1c211b3. mc: null]
javax.resource.ResourceException: Could not create connection.
at
org.apache.activemq.ra.ActiveMQManagedConnectionFactory.createManagedConnection(ActiveMQManagedConnectionFactory.java:171)
...
Caused by: java.net.ConnectException: Connection refused
...
-
This one reveals the problem that ActiveMQ ia not using PortOffset.
RecoveryController wants to connect to ${ActiveMQ + PortOffset} (61616 + 100).
-
2011-06-01 16:26:49,885 ERROR [RecoveryController] Recovery error: Could not get
XAResource for recovery for mcf:
geronimo:J2EEApplication=null,J2EEServer=geronimo,JCAConnectionFactory=DefaultActiveMQConnectionFactory,JCAManagedConnectionFactory=DefaultActiveMQConnectionFactory,JCAResource=geronimo-activemq-ra-3.0-SNAPSHOT,ResourceAdapter=geronimo-activemq-ra-3.0-SNAPSHOT,ResourceAdapterModule=org.apache.geronimo.configs/activemq-ra/3.0-SNAPSHOT/car,j2eeType=JCAConnectionManager,name=DefaultActiveMQConnectionFactory
2011-06-01 16:27:05,894 ERROR [MCFConnectionInterceptor] Error occurred creating
ManagedConnection for handle: nullManagedConnectionInfo:
org.apache.geronimo.connector.outbound.ManagedConnectionInfo@287dba. mc: null]
javax.resource.ResourceException: Could not create connection.
...
Caused by: javax.jms.JMSException: Could
[jira] [Updated] (GERONIMO-5987) The ActiveMQ working directory and port are not referenced correctly - multiple instances not possible
[
https://issues.apache.org/jira/browse/GERONIMO-5987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Russell E Glaue updated GERONIMO-5987:
--
Description:
I am testing with geronimo-tomcat7-javaee6-web-3.0-SNAPSHOT,
geronimo-tomcat7-javaee6-web-3.0-20110523.171218-97
ActiveMQ is configured to run as org.apache.geronimo.home.dir/var/activemq
and port 61616, and does not cooperate with multi-server configurations, nor
does it use the PortOffset. This is the use of the
org.apache.geronimo.server.name option and PortOffset in
var/config/config-substitutions.properties. (see:
https://cwiki.apache.org/GMOxDOC30/running-multiple-geronimo-instances.html)
First, Problem with working directory
When wanting to run more than a single server instance, the ActiveMQ startup
will block waiting for the lock file $GERONIMO_HOME/var/activemq/lock to
become available.
Obviously this causes any server instance started after the first server
instance is started to block during startup while waiting for the lock file to
become available.
Second, Problem with PortOffset
When configuring the PortOffset in
var/config/config-substitutions.properties, all Geroniomo components expect
and attempt to connect to ActiveMQ at the port {ActiveMQ + PortOffset}.
However, regardless of what you set the PortOffset to be, the ActiveMQ service
only ever binds to port 61616, the default configured port (or whatever you
have the port set as for this service).
Steps to repeat working directory problem:
1. Download and unpack G3.0 SNAPSHOT (3.0-20110523 tested)
2. Create the server instances:
-- 2A. cd ${GERONIMO_HOME}
-- 2B-1. mkdir gserver1
-- 2B-2. cp -rp var gserver1/
-- 2B-3. cp -rp etc gserver1/
-- 2B-4. cp -rp repository gserver1/
3. update the PortOffset parameter in
gserver1/var/config/config-substitutions.properties for the gserver1 instance.
4. Start the default instance and gserver1 instance:
-- bin/startup
-- env GERONIMO_OPTS=-Dorg.apache.geronimo.server.name=gserver1 bin/startup
5. `tail -f gserver1/var/logs/geronimo.log` and you will see this as the last
line that outputs:
2011-05-31 16:26:39,609 WARN [AMQPersistenceAdapter] Waiting to Lock the
Store var/activemq
The server waits here indefinitely.
6. Shutdown the default instance and you will see the gserver1 instance
continue on in the startup procedures. (of course you will see errors due to
the PortOffset problem)
* If I first start the gserver1 instance by itself (before starting the
default instance), the directory org.apache.geronimo.home.dir/var/activemq is
created and populated. Instead it should be
org.apache.geronimo.home.dir/org.apache.geronimo.server.name/var/activemq
that is created and populated.
* Probably the patch should be to reference the ActiveMQ working directory as
org.apache.geronimo.server.dir/var/activemq
Steps to repeat PortOffset problem:
1. Download and unpack G3.0 SNAPSHOT (3.0-20110523 tested)
2. Create the server instances:
-- 2A. cd ${GERONIMO_HOME}
-- 2B-1. mkdir gserver1
-- 2B-2. cp -rp var gserver1/
-- 2B-3. cp -rp etc gserver1/
-- 2B-4. cp -rp repository gserver1/
3. update the PortOffset parameter in
gserver1/var/config/config-substitutions.properties in the instance
4. Start the server instance:
-- env GERONIMO_OPTS=-Dorg.apache.geronimo.server.name=gserver1 bin/startup
This is the two error messages you receive when configuring PortOffset to 100
(for example). The second error message, regarding XAResource, repeats:
-
2011-06-01 16:26:49,883 ERROR [MCFConnectionInterceptor] Error occurred creating
ManagedConnection for handle: nullManagedConnectionInfo:
org.apache.geronimo.connector.outbound.ManagedConnectionInfo@1c211b3. mc: null]
javax.resource.ResourceException: Could not create connection.
at
org.apache.activemq.ra.ActiveMQManagedConnectionFactory.createManagedConnection(ActiveMQManagedConnectionFactory.java:171)
...
Caused by: java.net.ConnectException: Connection refused
...
-
This one reveals the problem that ActiveMQ ia not using PortOffset.
RecoveryController wants to connect to ${ActiveMQ + PortOffset} (61616 + 100).
-
2011-06-01 16:26:49,885 ERROR [RecoveryController] Recovery error: Could not get
XAResource for recovery for mcf:
geronimo:J2EEApplication=null,J2EEServer=geronimo,JCAConnectionFactory=DefaultActiveMQConnectionFactory,JCAManagedConnectionFactory=DefaultActiveMQConnectionFactory,JCAResource=geronimo-activemq-ra-3.0-SNAPSHOT,ResourceAdapter=geronimo-activemq-ra-3.0-SNAPSHOT,ResourceAdapterModule=org.apache.geronimo.configs/activemq-ra/3.0-SNAPSHOT/car,j2eeType=JCAConnectionManager,name=DefaultActiveMQConnectionFactory
2011-06-01 16:27:05,894 ERROR [MCFConnectionInterceptor] Error occurred creating
ManagedConnection for handle: nullManagedConnectionInfo:
org.apache.geronimo.connector.outbound.ManagedConnectionInfo@287dba. mc: null]
javax.resource.ResourceException: Could not create connection.
Re: Progress on osgi-friendliness
On Jun 2, 2011, at 2:05 AM, Kevan Miller wrote: fyi, this looks like the cause of the corba failure: java.lang.IllegalStateException: On a thread without an initialized context at org.apache.geronimo.openwebbeans.GeronimoSingletonService.getContext(GeronimoSingletonService.java:62) at org.apache.geronimo.openwebbeans.GeronimoSingletonService.get(GeronimoSingletonService.java:56) at org.apache.geronimo.openwebbeans.GeronimoSingletonService.get(GeronimoSingletonService.java:31) at org.apache.webbeans.config.WebBeansFinder.getSingletonInstance(WebBeansFinder.java:51) at org.apache.webbeans.config.WebBeansContext.getInstance(WebBeansContext.java:143) at org.apache.openejb.BeanContext.newInstance(BeanContext.java:1109) at org.apache.openejb.core.stateless.StatelessInstanceManager.ceateInstance(StatelessInstanceManager.java:178) at org.apache.openejb.core.stateless.StatelessInstanceManager.getInstance(StatelessInstanceManager.java:171) at org.apache.openejb.core.stateless.StatelessContainer.invoke(StatelessContainer.java:173) at org.apache.geronimo.corba.StandardServant._invoke(StandardServant.java:250) at org.apache.yoko.orb.OBPortableServer.ServantDispatcher.dispatch(ServantDispatcher.java:187) at org.apache.yoko.orb.OBPortableServer.POA_impl._OB_dispatch(POA_impl.java:1644) at org.apache.yoko.orb.OB.DispatchRequest_impl.invoke(DispatchRequest_impl.java:56) at org.apache.yoko.orb.OB.DispatchThreadPerRequest_impl$Dispatcher.run(DispatchStrategyFactory_impl.java:78) As Shawn has noted on the OpenEJB dev list, this seems to be caused by recent OpenEJB changes. So probably is unrelated to your changes... --kevan
[jira] [Commented] (GERONIMO-5987) The ActiveMQ working directory and port are not referenced correctly - multiple instances not possible
[
https://issues.apache.org/jira/browse/GERONIMO-5987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13043024#comment-13043024
]
Russell E Glaue commented on GERONIMO-5987:
---
Apparently there are two places in which the ActiveMQ Host and Port could be
configured in a bundle deployment.
1. var/config/config-substitutions.properties
2. etc/blueprint-activemq-placeholder.cfg
(The fact that the second file has the word placeholder in the file name
makes me curious about the developer's status of the ActiveMQ plugin.)
Configuring the port in either file is not utilized by ActiveMQ
Also, the activemq.data working directory can be configured in the second
file. But ActiveMQ does not utilize that either.
The ActiveMQ working directory and port are not referenced correctly -
multiple instances not possible
--
Key: GERONIMO-5987
URL: https://issues.apache.org/jira/browse/GERONIMO-5987
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: ActiveMQ
Affects Versions: 3.0-M1, 3.0-M2, 3.0
Environment: Linux x86, Red Hat Enterprise Linux Server release 5.4
(Tikanga)
Reporter: Russell E Glaue
Labels: geronimo
I am testing with geronimo-tomcat7-javaee6-web-3.0-SNAPSHOT,
geronimo-tomcat7-javaee6-web-3.0-20110523.171218-97
ActiveMQ is configured to run as org.apache.geronimo.home.dir/var/activemq
and port 61616, and does not cooperate with multi-server configurations, nor
does it use the PortOffset. This is the use of the
org.apache.geronimo.server.name option and PortOffset in
var/config/config-substitutions.properties. (see:
https://cwiki.apache.org/GMOxDOC30/running-multiple-geronimo-instances.html)
First, Problem with working directory
When wanting to run more than a single server instance, the ActiveMQ startup
will block waiting for the lock file $GERONIMO_HOME/var/activemq/lock to
become available.
Obviously this causes any server instance started after the first server
instance is started to block during startup while waiting for the lock file
to become available.
Second, Problem with PortOffset
When configuring the PortOffset in
var/config/config-substitutions.properties, all Geroniomo components expect
and attempt to connect to ActiveMQ at the port {ActiveMQ + PortOffset}.
However, regardless of what you set the PortOffset to be, the ActiveMQ
service only ever binds to port 61616, the default configured port (or
whatever you have the port set as for this service).
Steps to repeat working directory problem:
1. Download and unpack G3.0 SNAPSHOT (3.0-20110523 tested)
2. Create the server instances:
-- 2A. cd ${GERONIMO_HOME}
-- 2B-1. mkdir gserver1
-- 2B-2. cp -rp var gserver1/
-- 2B-3. cp -rp etc gserver1/
-- 2B-4. cp -rp repository gserver1/
3. update the PortOffset parameter in
gserver1/var/config/config-substitutions.properties for the gserver1 instance.
4. Start the default instance and gserver1 instance:
-- bin/startup
-- env GERONIMO_OPTS=-Dorg.apache.geronimo.server.name=gserver1 bin/startup
5. `tail -f gserver1/var/logs/geronimo.log` and you will see this as the last
line that outputs:
2011-05-31 16:26:39,609 WARN [AMQPersistenceAdapter] Waiting to Lock the
Store var/activemq
The server waits here indefinitely.
6. Shutdown the default instance and you will see the gserver1 instance
continue on in the startup procedures. (of course you will see errors due to
the PortOffset problem)
* If I first start the gserver1 instance by itself (before starting the
default instance), the directory org.apache.geronimo.home.dir/var/activemq
is created and populated. Instead it should be
org.apache.geronimo.home.dir/org.apache.geronimo.server.name/var/activemq
that is created and populated.
* Probably the patch should be to reference the ActiveMQ working directory as
org.apache.geronimo.server.dir/var/activemq
Steps to repeat PortOffset problem:
1. Download and unpack G3.0 SNAPSHOT (3.0-20110523 tested)
2. Create the server instances:
-- 2A. cd ${GERONIMO_HOME}
-- 2B-1. mkdir gserver1
-- 2B-2. cp -rp var gserver1/
-- 2B-3. cp -rp etc gserver1/
-- 2B-4. cp -rp repository gserver1/
3. update the PortOffset parameter in
gserver1/var/config/config-substitutions.properties in the instance
4. Start the server instance:
-- env GERONIMO_OPTS=-Dorg.apache.geronimo.server.name=gserver1 bin/startup
This is the two error messages you receive when configuring PortOffset to 100
(for example). The second error message, regarding XAResource, repeats:
-
2011-06-01 16:26:49,883 ERROR [MCFConnectionInterceptor] Error occurred
creating
ManagedConnection for handle: nullManagedConnectionInfo:
[jira] [Resolved] (GERONIMODEVTOOLS-752) Fail to start server in profile mode
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao resolved GERONIMODEVTOOLS-752. -- Resolution: Fixed Fail to start server in profile mode Key: GERONIMODEVTOOLS-752 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-752 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Environment: winxp, ibm jdk 1.6 Reporter: viola.lu Priority: Minor Fix For: 3.0 1.Install geronimo eclipse plugin 2.New a server, right-click server, choose profile, fail to start server. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Progress on osgi-friendliness
On Thu, Jun 2, 2011 at 2:01 PM, Forrest Xia forres...@gmail.com wrote: On Thu, Jun 2, 2011 at 11:22 AM, David Jencks david_jen...@yahoo.comwrote: Hi Forrest, I've pushed today's source to people.apache.org. It compiles for me :-) I just committed an update to OWB that makes it more compatible with aries proxying/weaving so you may want to build owb also. OWB is in the build chain already :) I'll probably be around on and off tonight so if you run into problems soon I might be able to fix them tonight. Triggering an execution just now, so far no problem. thanks! Hi David J, After compiling the snapshot dependencies of aries, I still get compilation error at plugins/aries/geronimo-aries and geronimo-aries-builder. [INFO] Compilation failure /home/tcker/tckdata/tckbuildsrc/djg30/plugins/aries/geronimo-aries/src/main/java/org/apache/geronimo/aries/GeronimoApplication.java:[52,46] [deprecation] createDeploymentMetadata(java.io.InputStream) in org.apache.aries.application.DeploymentMetadataFactory has been deprecated /home/tcker/tckdata/tckbuildsrc/djg30/plugins/aries/geronimo-aries/src/main/java/org/apache/geronimo/aries/GeronimoApplication.java:[63,31] cannot find symbol symbol : constructor SimpleBundleInfo(org.apache.aries.util.manifest.BundleManifest,java.lang.String) location: class org.apache.aries.application.utils.management.SimpleBundleInfo I tried to fix them, but confused around variant aries util/utils classes. Forrest
appclient testsuite failure
Looks like an appclient failure was introduced sometime between May 28 and now. I'm getting a failure in testsuite/enterprise-testsuite/sec-client-tests: Deployer operation failed: AppClientModuleBuilder: Could not load main class: org.apache.geronimo.test.TestClient org.apache.geronimo.common.DeploymentException: AppClientModuleBuilder: Could not load main class: org.apache.geronimo.test.TestClient at org.apache.geronimo.client.builder.AppClientModuleBuilder.createAppClientClassFinder(AppClientModuleBuilder.java:880) at org.apache.geronimo.client.builder.AppClientModuleBuilder.addGBeans(AppClientModuleBuilder.java:747) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:730) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:252) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:138) 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.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:872) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245) at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:344) 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.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:872) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245) at org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:172) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1427) at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1265) at java.security.AccessController.doPrivileged(Native Method) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1367) at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788) at sun.reflect.GeneratedMethodAccessor57.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305) at sun.rmi.transport.Transport$1.run(Transport.java:159) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:155) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:680) Caused by: java.lang.ClassNotFoundException: org.apache.geronimo.test.TestClient at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:513) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107) at java.lang.ClassLoader.loadClass(ClassLoader.java:248) at org.eclipse.osgi.internal.loader.BundleLoader.loadClass(BundleLoader.java:345) at
Re: appclient testsuite failure
I'll take a look On Fri, Jun 3, 2011 at 10:05 AM, Kevan Miller kevan.mil...@gmail.comwrote: Looks like an appclient failure was introduced sometime between May 28 and now. I'm getting a failure in testsuite/enterprise-testsuite/sec-client-tests: Deployer operation failed: AppClientModuleBuilder: Could not load main class: org.apache.geronimo.test.TestClient org.apache.geronimo.common.DeploymentException: AppClientModuleBuilder: Could not load main class: org.apache.geronimo.test.TestClient at org.apache.geronimo.client.builder.AppClientModuleBuilder.createAppClientClassFinder(AppClientModuleBuilder.java:880) at org.apache.geronimo.client.builder.AppClientModuleBuilder.addGBeans(AppClientModuleBuilder.java:747) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:730) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:252) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:138) 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.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:872) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245) at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:344) 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.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:872) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245) at org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:172) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1427) at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1265) at java.security.AccessController.doPrivileged(Native Method) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1367) at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788) at sun.reflect.GeneratedMethodAccessor57.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305) at sun.rmi.transport.Transport$1.run(Transport.java:159) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:155) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:680) Caused by: java.lang.ClassNotFoundException: org.apache.geronimo.test.TestClient at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:513) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107) at java.lang.ClassLoader.loadClass(ClassLoader.java:248) at
Re: appclient testsuite failure
On Jun 2, 2011, at 10:36 PM, Shawn Jiang wrote: I'll take a look Thanks Shawn. Just noticed that the AppClientModuleBuilder line numbers will be off by two (I'd reverted the latest commit, I think...). --kevan
Re: Progress on osgi-friendliness
On Jun 2, 2011, at 9:52 PM, Forrest Xia wrote: On Thu, Jun 2, 2011 at 2:01 PM, Forrest Xia forres...@gmail.com wrote: On Thu, Jun 2, 2011 at 11:22 AM, David Jencks david_jen...@yahoo.com wrote: Hi Forrest, I've pushed today's source to people.apache.org. It compiles for me :-) I just committed an update to OWB that makes it more compatible with aries proxying/weaving so you may want to build owb also. OWB is in the build chain already :) I'll probably be around on and off tonight so if you run into problems soon I might be able to fix them tonight. Triggering an execution just now, so far no problem. thanks! Hi David J, After compiling the snapshot dependencies of aries, I still get compilation error at plugins/aries/geronimo-aries and geronimo-aries-builder. [INFO] Compilation failure /home/tcker/tckdata/tckbuildsrc/djg30/plugins/aries/geronimo-aries/src/main/java/org/apache/geronimo/aries/GeronimoApplication.java:[52,46] [deprecation] createDeploymentMetadata(java.io.InputStream) in org.apache.aries.application.DeploymentMetadataFactory has been deprecated /home/tcker/tckdata/tckbuildsrc/djg30/plugins/aries/geronimo-aries/src/main/java/org/apache/geronimo/aries/GeronimoApplication.java:[63,31] cannot find symbol symbol : constructor SimpleBundleInfo(org.apache.aries.util.manifest.BundleManifest,java.lang.String) location: class org.apache.aries.application.utils.management.SimpleBundleInfo I tried to fix them, but confused around variant aries util/utils classes. Everything builds fine for me. Are you certain you're building the current version of Aries trunk? Sure looks like SimpleBundleInfo contains the constructor that the compiler is complaining about... --kevan
Re: Progress on osgi-friendliness
Are you refresh the code from https://people.apache.org/~djencks/? Here is the list that I built for dependencies: https://svn.apache.org/repos/asf/aries/branches/0.3-RCx/util/ https://svn.apache.org/repos/asf/aries/branches/0.3-RCx/blueprint/ https://svn.apache.org/repos/asf/aries/branches/0.3-RCx/application/ https://svn.apache.org/repos/asf/aries/trunk/ I there are mixed version for aries dependencies, some are in branches, some are in trunk. Maybe geronimo side has something left need to update, I don't know. Forrest On Fri, Jun 3, 2011 at 10:44 AM, Kevan Miller kevan.mil...@gmail.comwrote: On Jun 2, 2011, at 9:52 PM, Forrest Xia wrote: On Thu, Jun 2, 2011 at 2:01 PM, Forrest Xia forres...@gmail.com wrote: On Thu, Jun 2, 2011 at 11:22 AM, David Jencks david_jen...@yahoo.com wrote: Hi Forrest, I've pushed today's source to people.apache.org. It compiles for me :-) I just committed an update to OWB that makes it more compatible with aries proxying/weaving so you may want to build owb also. OWB is in the build chain already :) I'll probably be around on and off tonight so if you run into problems soon I might be able to fix them tonight. Triggering an execution just now, so far no problem. thanks! Hi David J, After compiling the snapshot dependencies of aries, I still get compilation error at plugins/aries/geronimo-aries and geronimo-aries-builder. [INFO] Compilation failure /home/tcker/tckdata/tckbuildsrc/djg30/plugins/aries/geronimo-aries/src/main/java/org/apache/geronimo/aries/GeronimoApplication.java:[52,46] [deprecation] createDeploymentMetadata(java.io.InputStream) in org.apache.aries.application.DeploymentMetadataFactory has been deprecated /home/tcker/tckdata/tckbuildsrc/djg30/plugins/aries/geronimo-aries/src/main/java/org/apache/geronimo/aries/GeronimoApplication.java:[63,31] cannot find symbol symbol : constructor SimpleBundleInfo(org.apache.aries.util.manifest.BundleManifest,java.lang.String) location: class org.apache.aries.application.utils.management.SimpleBundleInfo I tried to fix them, but confused around variant aries util/utils classes. Everything builds fine for me. Are you certain you're building the current version of Aries trunk? Sure looks like SimpleBundleInfo contains the constructor that the compiler is complaining about... --kevan
Re: Progress on osgi-friendliness
I just pushed another source zip which should fix a few more problems. Please try it, we'll get slightly more reasonable results. It all builds for me against current aries, owb, and openejb. thanks david jencks On Jun 2, 2011, at 7:44 PM, Kevan Miller wrote: On Jun 2, 2011, at 9:52 PM, Forrest Xia wrote: On Thu, Jun 2, 2011 at 2:01 PM, Forrest Xia forres...@gmail.com wrote: On Thu, Jun 2, 2011 at 11:22 AM, David Jencks david_jen...@yahoo.com wrote: Hi Forrest, I've pushed today's source to people.apache.org. It compiles for me :-) I just committed an update to OWB that makes it more compatible with aries proxying/weaving so you may want to build owb also. OWB is in the build chain already :) I'll probably be around on and off tonight so if you run into problems soon I might be able to fix them tonight. Triggering an execution just now, so far no problem. thanks! Hi David J, After compiling the snapshot dependencies of aries, I still get compilation error at plugins/aries/geronimo-aries and geronimo-aries-builder. [INFO] Compilation failure /home/tcker/tckdata/tckbuildsrc/djg30/plugins/aries/geronimo-aries/src/main/java/org/apache/geronimo/aries/GeronimoApplication.java:[52,46] [deprecation] createDeploymentMetadata(java.io.InputStream) in org.apache.aries.application.DeploymentMetadataFactory has been deprecated /home/tcker/tckdata/tckbuildsrc/djg30/plugins/aries/geronimo-aries/src/main/java/org/apache/geronimo/aries/GeronimoApplication.java:[63,31] cannot find symbol symbol : constructor SimpleBundleInfo(org.apache.aries.util.manifest.BundleManifest,java.lang.String) location: class org.apache.aries.application.utils.management.SimpleBundleInfo I tried to fix them, but confused around variant aries util/utils classes. Everything builds fine for me. Are you certain you're building the current version of Aries trunk? Sure looks like SimpleBundleInfo contains the constructor that the compiler is complaining about... --kevan
Re: Progress on osgi-friendliness
The last two source uploads should only be using aries trunk. The aries branches/0.3-RCx builds jars with the same version as trunk but they definitely won't work. thanks david jencks On Jun 2, 2011, at 8:41 PM, Forrest Xia wrote: Are you refresh the code from https://people.apache.org/~djencks/? Here is the list that I built for dependencies: https://svn.apache.org/repos/asf/aries/branches/0.3-RCx/util/ https://svn.apache.org/repos/asf/aries/branches/0.3-RCx/blueprint/ https://svn.apache.org/repos/asf/aries/branches/0.3-RCx/application/ https://svn.apache.org/repos/asf/aries/trunk/ I there are mixed version for aries dependencies, some are in branches, some are in trunk. Maybe geronimo side has something left need to update, I don't know. Forrest On Fri, Jun 3, 2011 at 10:44 AM, Kevan Miller kevan.mil...@gmail.com wrote: On Jun 2, 2011, at 9:52 PM, Forrest Xia wrote: On Thu, Jun 2, 2011 at 2:01 PM, Forrest Xia forres...@gmail.com wrote: On Thu, Jun 2, 2011 at 11:22 AM, David Jencks david_jen...@yahoo.com wrote: Hi Forrest, I've pushed today's source to people.apache.org. It compiles for me :-) I just committed an update to OWB that makes it more compatible with aries proxying/weaving so you may want to build owb also. OWB is in the build chain already :) I'll probably be around on and off tonight so if you run into problems soon I might be able to fix them tonight. Triggering an execution just now, so far no problem. thanks! Hi David J, After compiling the snapshot dependencies of aries, I still get compilation error at plugins/aries/geronimo-aries and geronimo-aries-builder. [INFO] Compilation failure /home/tcker/tckdata/tckbuildsrc/djg30/plugins/aries/geronimo-aries/src/main/java/org/apache/geronimo/aries/GeronimoApplication.java:[52,46] [deprecation] createDeploymentMetadata(java.io.InputStream) in org.apache.aries.application.DeploymentMetadataFactory has been deprecated /home/tcker/tckdata/tckbuildsrc/djg30/plugins/aries/geronimo-aries/src/main/java/org/apache/geronimo/aries/GeronimoApplication.java:[63,31] cannot find symbol symbol : constructor SimpleBundleInfo(org.apache.aries.util.manifest.BundleManifest,java.lang.String) location: class org.apache.aries.application.utils.management.SimpleBundleInfo I tried to fix them, but confused around variant aries util/utils classes. Everything builds fine for me. Are you certain you're building the current version of Aries trunk? Sure looks like SimpleBundleInfo contains the constructor that the compiler is complaining about... --kevan
Re: Progress on osgi-friendliness
I ever encounter build problem on aries trunk, and now they are fixed, the aries trunk artifacts now in my local repo. Just trigger a new server build, and let's wait to see :) Forrest On Fri, Jun 3, 2011 at 12:07 PM, David Jencks david_jen...@yahoo.comwrote: The last two source uploads should only be using aries trunk. The aries branches/0.3-RCx builds jars with the same version as trunk but they definitely won't work. thanks david jencks On Jun 2, 2011, at 8:41 PM, Forrest Xia wrote: Are you refresh the code from https://people.apache.org/~djencks/? Here is the list that I built for dependencies: https://svn.apache.org/repos/asf/aries/branches/0.3-RCx/util/ https://svn.apache.org/repos/asf/aries/branches/0.3-RCx/blueprint/ https://svn.apache.org/repos/asf/aries/branches/0.3-RCx/application/ https://svn.apache.org/repos/asf/aries/trunk/ I there are mixed version for aries dependencies, some are in branches, some are in trunk. Maybe geronimo side has something left need to update, I don't know. Forrest On Fri, Jun 3, 2011 at 10:44 AM, Kevan Miller kevan.mil...@gmail.comwrote: On Jun 2, 2011, at 9:52 PM, Forrest Xia wrote: On Thu, Jun 2, 2011 at 2:01 PM, Forrest Xia forres...@gmail.com wrote: On Thu, Jun 2, 2011 at 11:22 AM, David Jencks david_jen...@yahoo.com wrote: Hi Forrest, I've pushed today's source to people.apache.org. It compiles for me :-) I just committed an update to OWB that makes it more compatible with aries proxying/weaving so you may want to build owb also. OWB is in the build chain already :) I'll probably be around on and off tonight so if you run into problems soon I might be able to fix them tonight. Triggering an execution just now, so far no problem. thanks! Hi David J, After compiling the snapshot dependencies of aries, I still get compilation error at plugins/aries/geronimo-aries and geronimo-aries-builder. [INFO] Compilation failure /home/tcker/tckdata/tckbuildsrc/djg30/plugins/aries/geronimo-aries/src/main/java/org/apache/geronimo/aries/GeronimoApplication.java:[52,46] [deprecation] createDeploymentMetadata(java.io.InputStream) in org.apache.aries.application.DeploymentMetadataFactory has been deprecated /home/tcker/tckdata/tckbuildsrc/djg30/plugins/aries/geronimo-aries/src/main/java/org/apache/geronimo/aries/GeronimoApplication.java:[63,31] cannot find symbol symbol : constructor SimpleBundleInfo(org.apache.aries.util.manifest.BundleManifest,java.lang.String) location: class org.apache.aries.application.utils.management.SimpleBundleInfo I tried to fix them, but confused around variant aries util/utils classes. Everything builds fine for me. Are you certain you're building the current version of Aries trunk? Sure looks like SimpleBundleInfo contains the constructor that the compiler is complaining about... --kevan
