[jira] Closed: (GERONIMODEVTOOLS-558) Testsuite not able to find DefaultSelenium class
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed closed GERONIMODEVTOOLS-558. -- Resolution: Cannot Reproduce Not sure what had happened, but for a few days I couldn't get Selenium to work from my Eclipse installation. It always worked fine on another machine and for Tim. Yesterday it began working again and I haven't had any more problems. Closing this as I think it was just a gremlin in my computer that was stopping it. Testsuite not able to find DefaultSelenium class Key: GERONIMODEVTOOLS-558 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-558 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 2.2.0, 2.1.4 Reporter: B.J. Reed Assignee: Tim McConnell Priority: Blocker Fix For: 2.2.0, 2.1.4 Running the testsuite from Eclipse, I get a java.lang.NoClassDefFoundError: com/thoughtworks/selenium/DefaultSelenium at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(Unknown Source) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.defineClass(DefaultClassLoader.java:165) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineClass(ClasspathManager.java:554) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findClassImpl(ClasspathManager.java:524) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClassImpl(ClasspathManager.java:455) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass_LockClassLoader(ClasspathManager.java:443) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:423) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:193) at org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:368) at org.eclipse.osgi.framework.internal.core.SingleSourcePackage.loadClass(SingleSourcePackage.java:33) at org.eclipse.osgi.framework.internal.core.BundleLoader.findClassInternal(BundleLoader.java:441) at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:397) at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:385) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:87) at java.lang.ClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClassInternal(Unknown Source) at org.apache.geronimo.testsuite.v22.ui.EclipseUITest.installServer(EclipseUITest.java:110) at org.apache.geronimo.testsuite.v22.ui.EclipseUITest.testEclipseUI(EclipseUITest.java:58) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at junit.framework.TestCase.runTest(TestCase.java:164) at junit.framework.TestCase.runBare(TestCase.java:130) at abbot.swt.junit.extensions.SWTTestCase.runBareWrapper(SWTTestCase.java:279) at abbot.swt.junit.extensions.SWTTestCase.access$2(SWTTestCase.java:276) at abbot.swt.junit.extensions.SWTTestCase$4.execute(SWTTestCase.java:253) at abbot.swt.junit.extensions.UserThread.run(UserThread.java:75) Testsuite runs fine when run from maven. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4509) Two EJB server portlet issues
[ https://issues.apache.org/jira/browse/GERONIMO-4509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12666152#action_12666152 ] Manu T George commented on GERONIMO-4509: - Put in a fix for #2 in 736657 Two EJB server portlet issues - Key: GERONIMO-4509 URL: https://issues.apache.org/jira/browse/GERONIMO-4509 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.2 Environment: JDK 1.6 Ubuntu 8.04 AG 2.2 snapshot 20090110 Reporter: Forrest Xia Assignee: Manu T George For the new EJB server portlet, there are these problems: 1. Message prompt just restarting openejb module cause several console exceptions and EJB server portlet disappear in admin console at next time restart server. Steps: 1.1 Change value of a EJB container parameter, then it prompts OpenEJB module should be restarted for effectiveness. So I use expert mode to restart module org.apache.geronimo.configs/openejb/2.2-SNAPSHOT/car, confirm restart, then several exceptions are thrown out as following: 2009-01-14 09:35:45,546 ERROR [ConfigManagerPortlet] Exception java.lang.IllegalStateException: Configuration org.apache.geronimo.configs/axis2-ejb/2.2-SNAPSHOT/car still has children at org.apache.geronimo.kernel.config.ConfigurationStatus.destroy(ConfigurationStatus.java:69) at org.apache.geronimo.kernel.config.ConfigurationModel.removeConfiguration(ConfigurationModel.java:65) ... 2009-01-14 09:35:45,965 ERROR [[SystemModules]] Servlet.service() for servlet SystemModules threw exception java.lang.NullPointerException at org.apache.geronimo.console.configmanager.ConfigManagerPortlet.getConfigurationState(ConfigManagerPortlet.java:325) at org.apache.geronimo.console.configmanager.ConfigManagerPortlet.doView(ConfigManagerPortlet.java:272) ... 2009-01-14 09:37:08,300 ERROR [[SystemModules]] Servlet.service() for servlet SystemModules threw exception java.lang.IllegalStateException: Configuration org.apache.geronimo.configs/jaxws-ejb-deployer/2.2-SNAPSHOT/car still has children at org.apache.geronimo.kernel.config.ConfigurationStatus.destroy(ConfigurationStatus.java:69) at org.apache.geronimo.kernel.config.ConfigurationModel.removeConfiguration(ConfigurationModel.java:65) ... 2009-01-14 09:37:19,125 ERROR [[SystemModules]] Servlet.service() for servlet SystemModules threw exception java.lang.IllegalStateException: Configuration org.apache.geronimo.configs/openejb-deployer/2.2-SNAPSHOT/car still has children at org.apache.geronimo.kernel.config.ConfigurationStatus.destroy(ConfigurationStatus.java:69) at org.apache.geronimo.kernel.config.ConfigurationModel.removeConfiguration(ConfigurationModel.java:65) ... Anyway, the openejb module finally restarted, but no children modules appear anymore. Consequently the EJB server portlet disappears from the admin console. No way to check if the changed parameter takes effect. 2.2 Followed by step 1, restart geronimo by no change of config.xml, still the EJB server portlet is not there. Then check the config.xml, the portlet module module name=org.apache.geronimo.plugins/openejb-console-tomcat/2.2-SNAPSHOT/car/ is load=false Based on the symptom, I think it might be better to suggest user to restart geronimo server as a whole, not just openejb module. 2. Another issue is the parameter value seems be changed only once. For example, if you changed strictpooling from default true to false, then you want to change it back without restarting server, there is no way. This behavior is better to be improved. -- 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: 736649
Geronimo Revision: 736649 built with tests included
See the full build-0900.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090122/build-0900.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090122
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 39 minutes 25 seconds
[INFO] Finished at: Thu Jan 22 09:44:00 EST 2009
[INFO] Final Memory: 394M/1015M
[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/20090122/logs-0900-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:42.919
[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:12.876)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:29.489)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:35.665)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:16.744)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:24.093)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:22.317)
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:46.555)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:46.234)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:00:52.502)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:39.314)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:30.243)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:27.253)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:30.149)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:47.195)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:52.820)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:49.562)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:27.272)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:47.173)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security SUCCESS (0:00:40.519)
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:29.565)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servlets
[jira] Closed: (GERONIMODEVTOOLS-541) move all Abbot testcases to run during a single server install/uninstall
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed closed GERONIMODEVTOOLS-541. -- Resolution: Fixed Fix Version/s: 2.2.0 Assignee: B.J. Reed (was: Tim McConnell) Fixed with r736695 in trunk. Use Eclipse Extension Points and Extensions for each new test case. The EclipseUITest is now the driver for the testsuite. It does a quick sanity check to verify the Geronimo installation, starts the server, and then calls each Test Case Extension to build, run, and clean the test. After all are finished, it uninstalls the server. move all Abbot testcases to run during a single server install/uninstall Key: GERONIMODEVTOOLS-541 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-541 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Reporter: B.J. Reed Assignee: B.J. Reed Priority: Minor Fix For: 2.2.0 For each Abbot test case, each test case creates a new server, starts the server, stops the server, and then removes the server. This is very time consuming for the test cases to run and ends up testing much of the same code over and over again. It would be better to change the test suite to really only have one test (for each server version) with everything else done while the server is running. So the algorithm should be: check valid GEP installation create server start server test A test A cleanup test B test B cleanup . stop server remove server -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Please help me unsubscribe... Tried different things on the Nabble page
-- -- Joern Larsen CEO WHO'S AT JAOO? - http://www.jaoo.dk --- Trifork, Margrethepladsen 4, 8000 Århus C, Denmark Tel: +45 8732 8787 / Fax: +45 8732 8788 / Mob: +45 4072 8483
Re: Please help me unsubscribe... Tried different things on the Nabble page
Have you tried sending an email to dev-unsubscr...@geronimo.apache.org as described in http://geronimo.apache.org/mailing-lists.html? On Thu, Jan 22, 2009 at 11:42 AM, Jørn Larsen j...@trifork.com wrote: -- -- Joern Larsen CEO WHO'S AT JAOO? - http://www.jaoo.dk --- Trifork, Margrethepladsen 4, 8000 Århus C, Denmark Tel: +45 8732 8787 / Fax: +45 8732 8788 / Mob: +45 4072 8483 -- ~Jason Warner
Re: svn commit: r736042 - in /geronimo/server/trunk/framework/modules: geronimo-jmx-remoting/src/main/java/org/apache/geronimo/jmxremoting/JMXConnector.java geronimo-kernel/src/main/java/org/apache/
No. This is a client socket factory. All it should do is just open a
socket to the host and port specified.
If the server is bound to a specific interface the user (on the client
side) must specify the right ip address on the request.
I think the problem with the 'localhost' is that the 'host' parameter
passed into the client socket factory is incorrect. I expected it to
be what the user specified but instead it's the public ip address of
the local host. I think JVM RMI code does that switch but I'm not 100%
sure. And this switch issue seems to happen only when 'localhost' is
used (it works on a specific ip address).
With this patch I'm unable to do any remote JMX operations (without
changing any configuration) so this should be reverted soon.
Jarek
On Wed, Jan 21, 2009 at 10:18 AM, Donald Woods dwo...@apache.org wrote:
So, should the createSocket() default to localhost? That way, if a user has
mapped the server to bind to a specific interface (like 192.168.1.x) then
they should expect to have to supply the IP address/hostname of the server?
-Donald
Jarek Gawor wrote:
Donald,
I was looking at this patch but I didn't have a chance to test it and
comment on the bug but I think this fix is not right. It effectively
ignores the host parameter passed in the createSocket() call. So if
you have two running servers one local and one remote and both have
set sub. property hostname=127.0.0.1 and you issue shutdown -h remote
server host command on the local machine, the local server will be
shutdown!
Jarek
On Tue, Jan 20, 2009 at 12:19 PM, dwo...@apache.org wrote:
Author: dwoods
Date: Tue Jan 20 09:19:57 2009
New Revision: 736042
URL: http://svn.apache.org/viewvc?rev=736042view=rev
Log:
GERONIMO-4518 Can't shutdown the server when host was set to 127.0.0.1 in
config-substitutions.properties. Applied patch from Shawn Jiang.
Modified:
geronimo/server/trunk/framework/modules/geronimo-jmx-remoting/src/main/java/org/apache/geronimo/jmxremoting/JMXConnector.java
geronimo/server/trunk/framework/modules/geronimo-kernel/src/main/java/org/apache/geronimo/kernel/rmi/GeronimoRMIClientSocketFactory.java
Modified:
geronimo/server/trunk/framework/modules/geronimo-jmx-remoting/src/main/java/org/apache/geronimo/jmxremoting/JMXConnector.java
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/framework/modules/geronimo-jmx-remoting/src/main/java/org/apache/geronimo/jmxremoting/JMXConnector.java?rev=736042r1=736041r2=736042view=diff
==
---
geronimo/server/trunk/framework/modules/geronimo-jmx-remoting/src/main/java/org/apache/geronimo/jmxremoting/JMXConnector.java
(original)
+++
geronimo/server/trunk/framework/modules/geronimo-jmx-remoting/src/main/java/org/apache/geronimo/jmxremoting/JMXConnector.java
Tue Jan 20 09:19:57 2009
@@ -188,7 +188,7 @@
} else {
log.warn(Starting unauthenticating JMXConnector for +
jmxServiceURL);
}
-RMIClientSocketFactory socketFactory = new
GeronimoRMIClientSocketFactory(2 * 60 * 1000, 5 * 60 * 1000);
+RMIClientSocketFactory socketFactory = new
GeronimoRMIClientSocketFactory(host, 2 * 60 * 1000, 5 * 60 * 1000);
env.put(RMIConnectorServer.RMI_CLIENT_SOCKET_FACTORY_ATTRIBUTE,
socketFactory);
RMIServerSocketFactory serverSocketFactory = new
GeronimoRMIServerSocketFactory(host);
env.put(RMIConnectorServer.RMI_SERVER_SOCKET_FACTORY_ATTRIBUTE,
serverSocketFactory);
Modified:
geronimo/server/trunk/framework/modules/geronimo-kernel/src/main/java/org/apache/geronimo/kernel/rmi/GeronimoRMIClientSocketFactory.java
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/framework/modules/geronimo-kernel/src/main/java/org/apache/geronimo/kernel/rmi/GeronimoRMIClientSocketFactory.java?rev=736042r1=736041r2=736042view=diff
==
---
geronimo/server/trunk/framework/modules/geronimo-kernel/src/main/java/org/apache/geronimo/kernel/rmi/GeronimoRMIClientSocketFactory.java
(original)
+++
geronimo/server/trunk/framework/modules/geronimo-kernel/src/main/java/org/apache/geronimo/kernel/rmi/GeronimoRMIClientSocketFactory.java
Tue Jan 20 09:19:57 2009
@@ -31,15 +31,20 @@
private int connectionTimeout = -1;
private int readTimeout = -1;
+private String host=null;
-public GeronimoRMIClientSocketFactory(int connectionTimeout, int
readTimeout) {
+public GeronimoRMIClientSocketFactory(String _host,int
connectionTimeout, int readTimeout) {
+this.host=_host;
this.connectionTimeout = connectionTimeout;
this.readTimeout = readTimeout;
}
-public Socket createSocket(String host, int port) throws IOException
{
+public Socket createSocket(String _host, int port) throws
IOException {
Socket socket = new Socket();
-socket.bind(null);
+socket.bind(null);
Re: svn commit: r736042 - in /geronimo/server/trunk/framework/modules: geronimo-jmx-remoting/src/main/java/org/apache/geronimo/jmxremoting/JMXConnector.java geronimo-kernel/src/main/java/org/apache/
Changes reverted from 2.1 and trunk.
-Donald
Jarek Gawor wrote:
No. This is a client socket factory. All it should do is just open a
socket to the host and port specified.
If the server is bound to a specific interface the user (on the client
side) must specify the right ip address on the request.
I think the problem with the 'localhost' is that the 'host' parameter
passed into the client socket factory is incorrect. I expected it to
be what the user specified but instead it's the public ip address of
the local host. I think JVM RMI code does that switch but I'm not 100%
sure. And this switch issue seems to happen only when 'localhost' is
used (it works on a specific ip address).
With this patch I'm unable to do any remote JMX operations (without
changing any configuration) so this should be reverted soon.
Jarek
On Wed, Jan 21, 2009 at 10:18 AM, Donald Woods dwo...@apache.org wrote:
So, should the createSocket() default to localhost? That way, if a user has
mapped the server to bind to a specific interface (like 192.168.1.x) then
they should expect to have to supply the IP address/hostname of the server?
-Donald
Jarek Gawor wrote:
Donald,
I was looking at this patch but I didn't have a chance to test it and
comment on the bug but I think this fix is not right. It effectively
ignores the host parameter passed in the createSocket() call. So if
you have two running servers one local and one remote and both have
set sub. property hostname=127.0.0.1 and you issue shutdown -h remote
server host command on the local machine, the local server will be
shutdown!
Jarek
On Tue, Jan 20, 2009 at 12:19 PM, dwo...@apache.org wrote:
Author: dwoods
Date: Tue Jan 20 09:19:57 2009
New Revision: 736042
URL: http://svn.apache.org/viewvc?rev=736042view=rev
Log:
GERONIMO-4518 Can't shutdown the server when host was set to 127.0.0.1 in
config-substitutions.properties. Applied patch from Shawn Jiang.
Modified:
geronimo/server/trunk/framework/modules/geronimo-jmx-remoting/src/main/java/org/apache/geronimo/jmxremoting/JMXConnector.java
geronimo/server/trunk/framework/modules/geronimo-kernel/src/main/java/org/apache/geronimo/kernel/rmi/GeronimoRMIClientSocketFactory.java
Modified:
geronimo/server/trunk/framework/modules/geronimo-jmx-remoting/src/main/java/org/apache/geronimo/jmxremoting/JMXConnector.java
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/framework/modules/geronimo-jmx-remoting/src/main/java/org/apache/geronimo/jmxremoting/JMXConnector.java?rev=736042r1=736041r2=736042view=diff
==
---
geronimo/server/trunk/framework/modules/geronimo-jmx-remoting/src/main/java/org/apache/geronimo/jmxremoting/JMXConnector.java
(original)
+++
geronimo/server/trunk/framework/modules/geronimo-jmx-remoting/src/main/java/org/apache/geronimo/jmxremoting/JMXConnector.java
Tue Jan 20 09:19:57 2009
@@ -188,7 +188,7 @@
} else {
log.warn(Starting unauthenticating JMXConnector for +
jmxServiceURL);
}
-RMIClientSocketFactory socketFactory = new
GeronimoRMIClientSocketFactory(2 * 60 * 1000, 5 * 60 * 1000);
+RMIClientSocketFactory socketFactory = new
GeronimoRMIClientSocketFactory(host, 2 * 60 * 1000, 5 * 60 * 1000);
env.put(RMIConnectorServer.RMI_CLIENT_SOCKET_FACTORY_ATTRIBUTE,
socketFactory);
RMIServerSocketFactory serverSocketFactory = new
GeronimoRMIServerSocketFactory(host);
env.put(RMIConnectorServer.RMI_SERVER_SOCKET_FACTORY_ATTRIBUTE,
serverSocketFactory);
Modified:
geronimo/server/trunk/framework/modules/geronimo-kernel/src/main/java/org/apache/geronimo/kernel/rmi/GeronimoRMIClientSocketFactory.java
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/framework/modules/geronimo-kernel/src/main/java/org/apache/geronimo/kernel/rmi/GeronimoRMIClientSocketFactory.java?rev=736042r1=736041r2=736042view=diff
==
---
geronimo/server/trunk/framework/modules/geronimo-kernel/src/main/java/org/apache/geronimo/kernel/rmi/GeronimoRMIClientSocketFactory.java
(original)
+++
geronimo/server/trunk/framework/modules/geronimo-kernel/src/main/java/org/apache/geronimo/kernel/rmi/GeronimoRMIClientSocketFactory.java
Tue Jan 20 09:19:57 2009
@@ -31,15 +31,20 @@
private int connectionTimeout = -1;
private int readTimeout = -1;
+private String host=null;
-public GeronimoRMIClientSocketFactory(int connectionTimeout, int
readTimeout) {
+public GeronimoRMIClientSocketFactory(String _host,int
connectionTimeout, int readTimeout) {
+this.host=_host;
this.connectionTimeout = connectionTimeout;
this.readTimeout = readTimeout;
}
-public Socket createSocket(String host, int port) throws IOException
{
+public Socket createSocket(String _host, int port) throws
IOException {
Socket socket = new Socket();
-socket.bind(null);
+socket.bind(null);
+
[jira] Updated: (GERONIMO-4518) Can't shutdown the server when host was set to 127.0.0.1 in config-substitutions.properties
[ https://issues.apache.org/jira/browse/GERONIMO-4518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-4518: --- Priority: Major (was: Blocker) Previous patch to 2.1 trunk has been reverted. Can't shutdown the server when host was set to 127.0.0.1 in config-substitutions.properties --- Key: GERONIMO-4518 URL: https://issues.apache.org/jira/browse/GERONIMO-4518 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: startup/shutdown Affects Versions: 2.1.4, 2.2 Environment: Windows XP + Sun JDK 1.5 Reporter: Shawn Jiang Assignee: Donald Woods Fix For: 2.1.4, 2.2 Attachments: G4518_Shawn.patch 1, change the host in config-substitutions.properties to 127.0.0.1 2, start the server. 3, shutdown the server. *expected result*: the server could be shutdown. *actual result*: the sever can't be shutdown with exception: java.net.ConnectException: Connection refused: connect -- C:\geronimo-tomcat6-javaee5-2.2-SNAPSHOT\binshutdown --host 127.0.0.1 Using GERONIMO_HOME: C:\geronimo-tomcat6-javaee5-2.2-SNAPSHOT Using GERONIMO_TMPDIR: var\temp Using JRE_HOME:D:\dev\JDKs\sun_jdk1.5.0_15\jre log4j:WARN No appenders could be found for logger (org.apache.geronimo.kernel.basic.BasicKernel). log4j:WARN Please initialize the log4j system properly. Username: system Password: *** Locating server on 127.0.0.1:1099... Could not communicate with the server. The server may not be running or the port number may be inco rrect (Connection refused to host: 6.153.277.58; nested exception is: java.net.ConnectException: Connection refused: connect) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4501) Tomcat/Axis ignores jax-ws-catalog.xml while resolving wsdlLocation URLs
[
https://issues.apache.org/jira/browse/GERONIMO-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12666276#action_12666276
]
Jarek Gawor commented on GERONIMO-4501:
---
Committed additional changes (to trunk) to make service-ref work with OASIS
catalogs with CXF (revision 736768).
Tomcat/Axis ignores jax-ws-catalog.xml while resolving wsdlLocation URLs
Key: GERONIMO-4501
URL: https://issues.apache.org/jira/browse/GERONIMO-4501
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Affects Versions: 2.2
Environment: Geronimo 2.2-SNAPSHOT, Tomcat/Axis
Reporter: Janko Heilgeist
Assignee: Jarek Gawor
The problem description's context is identical to GERONIMO-4500 for the
Jetty/CXF assembly. This time the catalog is completely ignored while
resolving the wsdlLocation URL. The exception is:
{noformat}
2009-01-07 17:45:17,701 ERROR [GBeanInstanceState] Error while starting;
GBean is now in the FAILED state:
abstractName=default/geronimo-wsdllocation-jetty_cxf-1.0-SNAPSHOT.jar/1231346713744/car?EJBModule=default/geronimo-wsdllocation-jetty_cxf-1.0-SNAPSHOT.jar/1231346713744/car,J2EEApplication=null,StatelessSessionBean=HelloWorldServiceEJB,j2eeType=WSLink,name=HelloWorldServiceEJB
java.io.FileNotFoundException: http://example.com/HelloWorld.wsdl
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1172)
at java.net.URL.openStream(URL.java:1007)
at
org.apache.geronimo.axis2.AxisServiceGenerator.readWSDL(AxisServiceGenerator.java:302)
at
org.apache.geronimo.axis2.AxisServiceGenerator.getServiceFromWSDL(AxisServiceGenerator.java:141)
at
org.apache.geronimo.axis2.Axis2WebServiceContainer.init(Axis2WebServiceContainer.java:145)
at
org.apache.geronimo.axis2.ejb.EJBWebServiceContainer.init(EJBWebServiceContainer.java:56)
at
org.apache.geronimo.axis2.ejb.EJBWebServiceGBean.init(EJBWebServiceGBean.java:70)
...
{noformat}
The workaround that helped in the case of the Jetty/CXF assembly does not
work with Tomcat/Axis.
--
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: 736773
Geronimo Revision: 736773 built with tests included
See the full build-1500.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090122/build-1500.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090122/unit-test-reports
[INFO] snapshot org.apache.xbean:xbean:3.5-SNAPSHOT: checking for updates from
codehaus-snapshots
Downloading:
http://people.apache.org/repo/m2-snapshot-repository/org/apache/xbean/xbean/3.5-SNAPSHOT/xbean-3.5-SNAPSHOT.pom
18K downloaded
Downloading:
http://people.apache.org/repo/m2-incubating-repository//com/thoughtworks/xstream/xstream/1.3/xstream-1.3.pom
Downloading:
http://repo.exist.com/maven2/com/thoughtworks/xstream/xstream/1.3/xstream-1.3.pom
11K downloaded
Downloading:
http://people.apache.org/repo/m2-incubating-repository//com/thoughtworks/xstream/xstream-parent/1.3/xstream-parent-1.3.pom
Downloading:
http://repo.exist.com/maven2/com/thoughtworks/xstream/xstream-parent/1.3/xstream-parent-1.3.pom
13K downloaded
Downloading:
http://people.apache.org/repo/m2-incubating-repository//xpp3/xpp3_min/1.1.4c/xpp3_min-1.1.4c.pom
Downloading:
http://repo.exist.com/maven2/xpp3/xpp3_min/1.1.4c/xpp3_min-1.1.4c.pom
1K downloaded
[WARNING] POM for 'xpp3:xpp3_min:pom:1.1.4c:compile' is invalid. It will be
ignored for artifact resolution. Reason: Parse error reading POM. Reason:
expected START_TAG or END_TAG not TEXT (position: TEXT seen ...e with exception
of classes directly in package org.xmlpull.v1 )/... @15:169) for project
xpp3:xpp3_min at
/home/geronimo/.m2/repository/xpp3/xpp3_min/1.1.4c/xpp3_min-1.1.4c.pom
Downloading:
http://people.apache.org/repo/m2-incubating-repository//asm/asm/3.1/asm-3.1.jar
Downloading: http://repo.exist.com/maven2/asm/asm/3.1/asm-3.1.jar
42K downloaded
Downloading:
http://people.apache.org/repo/m2-incubating-repository//asm/asm-commons/3.1/asm-commons-3.1.jar
Downloading:
http://repo.exist.com/maven2/asm/asm-commons/3.1/asm-commons-3.1.jar
31K downloaded
Downloading:
http://people.apache.org/repo/m2-snapshot-repository/org/apache/xbean/xbean-reflect/3.5-SNAPSHOT/xbean-reflect-3.5-SNAPSHOT.jar
130K downloaded
Downloading:
http://people.apache.org/repo/m2-incubating-repository//com/thoughtworks/xstream/xstream/1.3/xstream-1.3.jar
Downloading:
http://repo.exist.com/maven2/com/thoughtworks/xstream/xstream/1.3/xstream-1.3.jar
401K downloaded
Downloading:
http://people.apache.org/repo/m2-incubating-repository//xpp3/xpp3_min/1.1.4c/xpp3_min-1.1.4c.jar
Downloading:
http://repo.exist.com/maven2/xpp3/xpp3_min/1.1.4c/xpp3_min-1.1.4c.jar
24K downloaded
[INFO] [enforcer:enforce {execution: default}]
[WARNING] POM for 'xpp3:xpp3_min:pom:1.1.4c:compile' is invalid. It will be
ignored for artifact resolution. Reason: Parse error reading POM. Reason:
expected START_TAG or END_TAG not TEXT (position: TEXT seen ...e with exception
of classes directly in package org.xmlpull.v1 )/... @15:169) for project
xpp3:xpp3_min at
/home/geronimo/.m2/repository/xpp3/xpp3_min/1.1.4c/xpp3_min-1.1.4c.pom
[INFO] [remote-resources:process {execution: process}]
[WARNING] Attempting to build MavenProject instance for Artifact
(xpp3:xpp3_min:1.1.4c) of type: jar; constructing POM artifact instead.
[WARNING] Invalid project model for artifact [xpp3_min:xpp3:1.1.4c]. It will be
ignored by the remote resources Mojo.
[WARNING] POM for 'xpp3:xpp3_min:pom:1.1.4c:compile' is invalid. It will be
ignored for artifact resolution. Reason: Parse error reading POM. Reason:
expected START_TAG or END_TAG not TEXT (position: TEXT seen ...e with exception
of classes directly in package org.xmlpull.v1 )/... @15:169) for project
xpp3:xpp3_min at
/home/geronimo/.m2/repository/xpp3/xpp3_min/1.1.4c/xpp3_min-1.1.4c.pom
[INFO] [remote-resources:process {execution: default}]
[WARNING] Attempting to build MavenProject instance for Artifact
(xpp3:xpp3_min:1.1.4c) of type: jar; constructing POM artifact instead.
[WARNING] Invalid project model for artifact [xpp3_min:xpp3:1.1.4c]. It will be
ignored by the remote resources Mojo.
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[WARNING] POM for 'xpp3:xpp3_min:pom:1.1.4c:compile' is invalid. It will be
ignored for artifact resolution. Reason: Parse error reading POM. Reason:
expected START_TAG or END_TAG not TEXT (position: TEXT seen ...e with exception
of classes directly in package org.xmlpull.v1 )/... @15:169) for project
xpp3:xpp3_min at
/home/geronimo/.m2/repository/xpp3/xpp3_min/1.1.4c/xpp3_min-1.1.4c.pom
[INFO] [compiler:compile]
[INFO] Compiling 208 source files to
/home/geronimo/geronimo/trunk/framework/modules/geronimo-kernel/target/classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO
[jira] Resolved: (GERONIMO-4501) Tomcat/Axis ignores jax-ws-catalog.xml while resolving wsdlLocation URLs
[
https://issues.apache.org/jira/browse/GERONIMO-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor resolved GERONIMO-4501.
---
Resolution: Fixed
Fix Version/s: 2.2
OASIS catalogs should work now with services and service-refs with Axis2 and
CXF.
Tomcat/Axis ignores jax-ws-catalog.xml while resolving wsdlLocation URLs
Key: GERONIMO-4501
URL: https://issues.apache.org/jira/browse/GERONIMO-4501
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Affects Versions: 2.2
Environment: Geronimo 2.2-SNAPSHOT, Tomcat/Axis
Reporter: Janko Heilgeist
Assignee: Jarek Gawor
Fix For: 2.2
The problem description's context is identical to GERONIMO-4500 for the
Jetty/CXF assembly. This time the catalog is completely ignored while
resolving the wsdlLocation URL. The exception is:
{noformat}
2009-01-07 17:45:17,701 ERROR [GBeanInstanceState] Error while starting;
GBean is now in the FAILED state:
abstractName=default/geronimo-wsdllocation-jetty_cxf-1.0-SNAPSHOT.jar/1231346713744/car?EJBModule=default/geronimo-wsdllocation-jetty_cxf-1.0-SNAPSHOT.jar/1231346713744/car,J2EEApplication=null,StatelessSessionBean=HelloWorldServiceEJB,j2eeType=WSLink,name=HelloWorldServiceEJB
java.io.FileNotFoundException: http://example.com/HelloWorld.wsdl
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1172)
at java.net.URL.openStream(URL.java:1007)
at
org.apache.geronimo.axis2.AxisServiceGenerator.readWSDL(AxisServiceGenerator.java:302)
at
org.apache.geronimo.axis2.AxisServiceGenerator.getServiceFromWSDL(AxisServiceGenerator.java:141)
at
org.apache.geronimo.axis2.Axis2WebServiceContainer.init(Axis2WebServiceContainer.java:145)
at
org.apache.geronimo.axis2.ejb.EJBWebServiceContainer.init(EJBWebServiceContainer.java:56)
at
org.apache.geronimo.axis2.ejb.EJBWebServiceGBean.init(EJBWebServiceGBean.java:70)
...
{noformat}
The workaround that helped in the case of the Jetty/CXF assembly does not
work with Tomcat/Axis.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
informix and sqlserver tranql wrappers available for test
I finally got around to fixing the copyright problems in the contributed tranql wrappers for informix and sqlserver and pushing snapshots. It would be great if someone with access to these dbs could make sure they work before I release the wrappers. They are at the codehaus snapshot repo http://snapshots.repository.codehaus.org /org/tranql/tranql-connector-sqlserver2005-xa/1.0-SNAPSHOT/tranql- connector-sqlserver2005-xa-1.0-20090123.002726-1.rar /org/tranql/tranql-connector-sqlserver2000-xa/1.0-SNAPSHOT/tranql- connector-sqlserver2000-xa-1.0-20090123.002451-1.rar /org/tranql/tranql-connector-informix-xa/1.0-SNAPSHOT/tranql-connector- informix-xa-1.0-20090123.002320-1.rar If no one responds within a couple days I will probably go ahead and release them anyway. but it would be much much better to know they work. many thanks david jencks
[jira] Created: (GERONIMO-4521) ejb apps with spec security constraints should only deploy if there are corresponding geronimo security constraints, as with web apps
ejb apps with spec security constraints should only deploy if there are corresponding geronimo security constraints, as with web apps - Key: GERONIMO-4521 URL: https://issues.apache.org/jira/browse/GERONIMO-4521 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: deployment, OpenEJB Affects Versions: 2.1.3, 2.1.4, 2.2 Reporter: David Jencks Assignee: David Jencks Fix For: 2.1.4, 2.2 for quite a while we have only allowed you to deploy a web app with security constraints if you also supply a geronimo security configuration; otherwise you get no security constraints at all. We should be doing the same for ejb apps. While this may be inconvenient for those who want to try deploying an app without completing the configuration, the alternative is to give the impression that the deployed app is enforcing the security constraints -- which it is not. I suppose an alternative might be to figure out a way to deploy and just forbid access to any resources that are constrained. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4521) ejb apps with spec security constraints should only deploy if there are corresponding geronimo security constraints, as with web apps
[ https://issues.apache.org/jira/browse/GERONIMO-4521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed GERONIMO-4521. -- Resolution: Fixed trunk rev 736874 branches/2.1 rev 736877 ejb apps with spec security constraints should only deploy if there are corresponding geronimo security constraints, as with web apps - Key: GERONIMO-4521 URL: https://issues.apache.org/jira/browse/GERONIMO-4521 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: deployment, OpenEJB Affects Versions: 2.1.3, 2.1.4, 2.2 Reporter: David Jencks Assignee: David Jencks Fix For: 2.1.4, 2.2 for quite a while we have only allowed you to deploy a web app with security constraints if you also supply a geronimo security configuration; otherwise you get no security constraints at all. We should be doing the same for ejb apps. While this may be inconvenient for those who want to try deploying an app without completing the configuration, the alternative is to give the impression that the deployed app is enforcing the security constraints -- which it is not. I suppose an alternative might be to figure out a way to deploy and just forbid access to any resources that are constrained. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] branches/2.0: Failed for Revision: 736861
Geronimo Revision: 736861 built with tests included See the full build-2000.log file at http://people.apache.org/builds/geronimo/server/binaries/2.0/20090122/build-2000.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.0/20090122/unit-test-reports org.apache.geronimo.plugins:car-maven-plugin:maven-plugin:2.0.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) org.apache.geronimo.plugins:car-maven-plugin:maven-plugin:2.0.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) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.plugins -DartifactId=car-maven-plugin \ -Dversion=2.0.3-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.geronimo.plugins -DartifactId=car-maven-plugin \ -Dversion=2.0.3-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] org.apache.geronimo.plugins:car-maven-plugin:maven-plugin:2.0.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) org.apache.geronimo.plugins:car-maven-plugin:maven-plugin:2.0.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) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.findExtensions(DefaultLifecycleExecutor.java:184) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:141) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) 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.plugin.PluginNotFoundException: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.plugins -DartifactId=car-maven-plugin \ -Dversion=2.0.3-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.geronimo.plugins -DartifactId=car-maven-plugin \ -Dversion=2.0.3-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] org.apache.geronimo.plugins:car-maven-plugin:maven-plugin:2.0.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) org.apache.geronimo.plugins:car-maven-plugin:maven-plugin:2.0.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) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:236) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:171
[BUILD] trunk: Failed for Revision: 736890
Geronimo Revision: 736890 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090122/build-2100.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090122
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 52 minutes 10 seconds
[INFO] Finished at: Thu Jan 22 21:54:33 EST 2009
[INFO] Final Memory: 634M/954M
[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/20090122/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.252
[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:00.549)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:28.830)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:33.729)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:16.735)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:12.323)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:19.492)
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:42.956)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:43.480)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:00:52.927)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:40.353)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:30.607)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:28.930)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:31.645)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:46.482)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:55.592)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:49.012)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:26.566)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:46.879)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security FAILURE (0:00:36.071) Java
returned: 1
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:29.518)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5
[BUILD] branches/2.0: Failed for Revision: 736958
Geronimo Revision: 736958 built with tests included
See the full build-0200.log file at
http://people.apache.org/builds/geronimo/server/binaries/2.0/20090123/build-0200.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/2.0/20090123/unit-test-reports
[INFO] [dependency:copy {execution: default}]
[INFO] Configured Artifact: org.apache.yoko:yoko-spec-corba:?:jar
[INFO] Configured Artifact: org.apache.yoko:yoko-core:?:jar
Downloading:
http://download.java.net/maven/1//org.apache.yoko/jars/yoko-core-1.0.jar
Downloading:
http://people.apache.org/repo/m2-incubating-repository//org/apache/yoko/yoko-core/1.0/yoko-core-1.0.jar
Downloading:
http://repo.exist.com/maven2/org/apache/yoko/yoko-core/1.0/yoko-core-1.0.jar
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
GroupId: org.apache.yoko
ArtifactId: yoko-core
Version: 1.0
Reason: Unable to download the artifact from any repository
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.yoko -DartifactId=yoko-core \
-Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.apache.yoko -DartifactId=yoko-core \
-Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file \
-Durl=[url] -DrepositoryId=[id]
org.apache.yoko:yoko-core:jar:1.0
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
java.net (http://download.java.net/maven/1/),
apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository),
apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository),
codehaus-snapshots (http://snapshots.repository.codehaus.org),
apache-incubator (http://people.apache.org/repo/m2-incubating-repository/)
[INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Unable to find artifact.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
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.plugin.MojoExecutionException: Unable to find
artifact.
at
org.apache.maven.plugin.dependency.fromConfiguration.AbstractFromConfigurationMojo.getArtifact(AbstractFromConfigurationMojo.java:250)
at
org.apache.maven.plugin.dependency.fromConfiguration.AbstractFromConfigurationMojo.getProcessedArtifactItems(AbstractFromConfigurationMojo.java:146)
at
org.apache.maven.plugin.dependency.fromConfiguration.CopyMojo.execute(CopyMojo.java:65)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
... 16 more
Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable
to download the artifact from any repository
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.yoko -DartifactId=yoko-core \
-Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.apache.yoko
