Re: code review for transport patch
I think this belongs on the ActiveMQ dev list... --jason On Nov 11, 2006, at 2:40 PM, Nathan Mittler wrote: Hey guys, I took a crack at a fix which sends a stomp error frame back to the client in the event of a failure during authentication or authorization. I haven't been through much of this code before, so I'd like to get some feedback on my changes. Part of my concern is that some of the tweaks will affect all protocols (not only stomp) so I want to make sure I get it right. In particular, a connection error is returned back to the client if an exception is caught by the TransportConnection.onCommand. In the case of stomp, this ends up as a stomp error frame. Here's the patch against the latest trunk: http://people.apache.org/~nmittler/patch.txt I also have a tarball if anyone wants to check it out: http://people.apache.org/~nmittler/apache-activemq-4.2-incubator- SNAPSHOT.tar.gz Thanks, Nate
[jira] Work started: (SM-732) Fault-messages cause JbiChannel to throw NullPointerException
[ https://issues.apache.org/activemq/browse/SM-732?page=all ] Work on SM-732 started by Grant McDonald. Fault-messages cause JbiChannel to throw NullPointerException - Key: SM-732 URL: https://issues.apache.org/activemq/browse/SM-732 Project: ServiceMix Issue Type: Bug Components: servicemix-jsr181 Affects Versions: 3.0 Environment: not relevant Reporter: Horst Studer Assigned To: Grant McDonald From a service (jsr181 pojo), I am calling another service (also implemented as a jsr181 pojo), using a jsr181 proxy. This works fine if the called service returns an out message. If, however, the called service throws an exception (i.e. returns a fault), there is a NullPointerException in ...jsr181.xfire.JbiChannel. There are two problems: After the sendSync, there is a check to see if the exchange status is ERROR, and if not, getOutMessage().getContent() is called. The code assumes that after a fault, the exchange status is ERROR, but in fact, it is ACTIVE and the fault-Message is set, while the out-Message is null. So this causes the NullPointerException. The other problem is that the code for handling the fault-Message is missing (marked as // TODO, but as stated above, with the wrong assumption that the exchange status is ERROR). It would be nice, if the fault message would be processed an cause xfire to throw a corresponding exception on the proxy. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] Commented: (SM-536) The defaultMep is a mandatory attribute on consumer endpoints and should be checked
Guillaume, The more I look at this the more I come up with questions :) The AbstractXBeanDeployer and AbstractWsdl1Deployer are both part of the inheritance hierarchy of AbstractDeloyer. Should there actually be a validate method on the AbstractDeployer instead which would allow for the validation across the entire deployer hierarchy? I am assuming here that the idea was to introduce a way to have both a generic and specific validation hierarchy. And further, would the other endpoint deployers require calls to validate after their endpoints are created? The endpoint deployers involved here are (Other than AbstractWsdl1Deployer and AbstractXBeanDeployer): BPEDeployer ScaDeployer WSNDeployer Currently there would be no additional validations but the introduction of a validate method would be more consistent if it was applied across all the endpoint deployers instead of in just a couple. Grant M. On 11/10/06, Grant McDonald (JIRA) [EMAIL PROTECTED] wrote: [ https://issues.apache.org/activemq/browse/SM-536?page=comments#action_37404] Grant McDonald commented on SM-536: --- I thought as much. I'll update it to throw DeploymentException and add in a validate method to the AbstractWsd1Deployer The defaultMep is a mandatory attribute on consumer endpoints and should be checked --- Key: SM-536 URL: https://issues.apache.org/activemq/browse/SM-536 Project: ServiceMix Issue Type: Bug Components: servicemix-http, servicemix-jms Reporter: Guillaume Nodet Assigned To: Grant McDonald Attachments: SM-536.patch -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (SM-732) Fault-messages cause JbiChannel to throw NullPointerException
[ https://issues.apache.org/activemq/browse/SM-732?page=all ] Grant McDonald resolved SM-732. --- Fix Version/s: 3.1 incubation Resolution: Fixed Author: grantm Date: Sun Nov 12 03:47:00 2006 GMT+10 New Revision: 473875 URL: http://svn.apache.org/viewvc?view=revrev=473875 Log: Issue: SM-732 Description: refactored to test for fault condition and return fault content as string argument to XFireFault Modified: F:\Grant\Apache\ServiceMix\deployables\serviceengines\servicemix-jsr181\src\main\java\org\apache\servicemix\jsr181\xfire\JbiChannel.java Fault-messages cause JbiChannel to throw NullPointerException - Key: SM-732 URL: https://issues.apache.org/activemq/browse/SM-732 Project: ServiceMix Issue Type: Bug Components: servicemix-jsr181 Affects Versions: 3.0 Environment: not relevant Reporter: Horst Studer Assigned To: Grant McDonald Fix For: 3.1, incubation From a service (jsr181 pojo), I am calling another service (also implemented as a jsr181 pojo), using a jsr181 proxy. This works fine if the called service returns an out message. If, however, the called service throws an exception (i.e. returns a fault), there is a NullPointerException in ...jsr181.xfire.JbiChannel. There are two problems: After the sendSync, there is a check to see if the exchange status is ERROR, and if not, getOutMessage().getContent() is called. The code assumes that after a fault, the exchange status is ERROR, but in fact, it is ACTIVE and the fault-Message is set, while the out-Message is null. So this causes the NullPointerException. The other problem is that the code for handling the fault-Message is missing (marked as // TODO, but as stated above, with the wrong assumption that the exchange status is ERROR). It would be nice, if the fault message would be processed an cause xfire to throw a corresponding exception on the proxy. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SM-744) Request/Response for jms through MessageID/CorrelationID
[ https://issues.apache.org/activemq/browse/SM-744?page=comments#action_37417 ] Grant McDonald commented on SM-744: --- Martin, Could you please expand upon the circumstances/scenarios where this occurs? The only places I found the JMS correlation id being set to the exchange id was in MultiplexingProviderProcessor(161) and StandardProviderProcessor(101) which you would expect from messages coming from the NMR onto JMS and having an InOut MEP. Under what scenario is there an expectation in the client that the JMS correlation id will be a message exchange id? Request/Response for jms through MessageID/CorrelationID Key: SM-744 URL: https://issues.apache.org/activemq/browse/SM-744 Project: ServiceMix Issue Type: Improvement Components: servicemix-jms Environment: All platforms Reporter: Martin Landua Priority: Minor The servicemix-jms component assumes that the request/reponse pattern is implemented by the client by using some artificial correlation id as the connection between the messages (as described in http://activemq.org/site/how-should-i-implement-request-response-with-jms.html). However, there are cases where the client assumes that the server sets the correlation id of the response to the message id (!) of the request. Currently, the servicemix-jms component does not support this, but it would be convenient if it were configurable. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
GOperationInfo questions?
What is the difference between 'name' and methodName in GOperationInfo? Why is the return type of the method not included in GoperationInfo? Is it a good idea to include a human readable description of the method in GOperationInfo? Thanks In Advance Anita Yahoo! Music Unlimited Access over 1 million songs. http://music.yahoo.com/unlimited
Re: Build failed, looking for maven-jaxb2-plugin
I seem to be able to build trunk fine at home, so I'm thinking that my problems were related to some sort of firewall issues at work. On 11/10/06, Murphree, Michael [EMAIL PROTECTED] wrote: Nate, I've been having the same trouble as you: https://issues.apache.org/activemq/browse/AMQ-1017. I have far less experience with Maven, though. I can get through most of the build but I get stuck there with the same error. I'm not sure what I'd actually need to do to get my local Maven repository configured manually to get past this, or if that's possible. Regards, Michael -Original Message- From: Mittler, Nathan [mailto:[EMAIL PROTECTED] Sent: Friday, November 10, 2006 8:25 AM To: activemq-dev@geronimo.apache.org Subject: Build failed, looking for maven-jaxb2-plugin A clean build of trunk (with mvn 2.0.4) is failing for me when building the XMPP module, trying to download the maven-jaxb2-plugin: https://maven2-repository.dev.java.net/nonav/repository/org/jvnet/jaxb2/ maven2/maven-jaxb2-plugin/0.1/maven-jaxb2-plugin-0.1.pom The funny thing is that I can view the pom file through a web browser, so I'm not sure what is giving Maven heartburn. I've had my Maven proxy settings set up for a while, so I'm confident that's not it. A listing of the directory https://maven2-repository.dev.java.net/nonav/repository/org/jvnet/jaxb2/ maven2/maven-jaxb2-plugin/0.1/ fails - I guess they have directory listing disabled on the server. Is anyone else having this problem ... And does anyone know how I can get past it? Thanks, Nate The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
[jira] Resolved: (AMQ-1012) Receiving a BytesMessage sent from Java using CMS listener causes exception thrown in class BufferedInputStream
[ https://issues.apache.org/activemq/browse/AMQ-1012?page=all ]
Nathan Mittler resolved AMQ-1012.
-
Resolution: Cannot Reproduce
I'm not having this problem against either 4.0.2 or the latest trunk. If it
happens again, please submit a unit test that demonstrates the problem and
we'll open a new issue.
Receiving a BytesMessage sent from Java using CMS listener causes exception
thrown in class BufferedInputStream
Key: AMQ-1012
URL: https://issues.apache.org/activemq/browse/AMQ-1012
Project: ActiveMQ
Issue Type: Bug
Components: CMS (C++ client)
Affects Versions: 4.0.2
Environment: Ubuntu Linux 6.06 LTS, ActiveMQ 4.0.2, CMS version 0.0.2
with STOMP
Reporter: Mark Silberbauer
Fix For: 4.0.3
Original Estimate: 1 day
Remaining Estimate: 1 day
1) Setup a MessageListener to listen for messages on Topic X using CMS.
2) Send a BytesMessage from ActiveMQ java JMS interface to Topic X
3) An exception is thrown from BufferedInputStream::bufferData() with
description failed reading bytes from stream
int bytesRead = stream-read( buffer+tail, bufferSize-tail );
if( bytesRead == 0 ){
throw IOException( __FILE__, __LINE__,
BufferedInputStream::read() - failed reading bytes from stream);
}
4) The operation of the CMS interface is broken thereafter.
Note:
This only occurs when sending a BytesMessage from Java to C++
Sending a BytesMessage from C++ to Java or C++ to C++ works perfectly.
Sending messages of Type TextMessage also works perfectly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
code review for transport patch
Hey guys, I took a crack at a fix which sends a stomp error frame back to the client in the event of a failure during authentication or authorization. I haven't been through much of this code before, so I'd like to get some feedback on my changes. Part of my concern is that some of the tweaks will affect all protocols (not only stomp) so I want to make sure I get it right. In particular, a connection error is returned back to the client if an exception is caught by the TransportConnection.onCommand. In the case of stomp, this ends up as a stomp error frame. Here's the patch against the latest trunk: http://people.apache.org/~nmittler/patch.txt I also have a tarball if anyone wants to check it out: http://people.apache.org/~nmittler/apache-activemq-4.2-incubator-SNAPSHOT.tar.gz Thanks, Nate
Re: code review for transport patch
I think this belongs on the ActiveMQ dev list...--jasonOn Nov 11, 2006, at 2:40 PM, Nathan Mittler wrote:Hey guys, I took a crack at a fix which sends a stomp error frame back to the client in the event of a failure during authentication or authorization. I haven't been through much of this code before, so I'd like to get some feedback on my changes. Part of my concern is that some of the tweaks will affect all protocols (not only stomp) so I want to make sure I get it right. In particular, a connection error is returned back to the client if an exception is caught by the TransportConnection.onCommand. In the case of stomp, this ends up as a stomp error frame. Here's the patch against the latest trunk: http://people.apache.org/~nmittler/patch.txt I also have a tarball if anyone wants to check it out: http://people.apache.org/~nmittler/apache-activemq-4.2-incubator-SNAPSHOT.tar.gz Thanks, Nate
Re: code review for transport patch
oops - You're right, My mistake!On 11/11/06, Jason Dillon [EMAIL PROTECTED] wrote: I think this belongs on the ActiveMQ dev list...--jasonOn Nov 11, 2006, at 2:40 PM, Nathan Mittler wrote: Hey guys, I took a crack at a fix which sends a stomp error frame back to the client in the event of a failure during authentication or authorization. I haven't been through much of this code before, so I'd like to get some feedback on my changes. Part of my concern is that some of the tweaks will affect all protocols (not only stomp) so I want to make sure I get it right. In particular, a connection error is returned back to the client if an exception is caught by the TransportConnection.onCommand. In the case of stomp, this ends up as a stomp error frame. Here's the patch against the latest trunk: http://people.apache.org/~nmittler/patch.txt I also have a tarball if anyone wants to check it out: http://people.apache.org/~nmittler/apache-activemq-4.2-incubator-SNAPSHOT.tar.gz Thanks, Nate
Re: Can't build trunk for an java.io.InvalidClassException
I've update my local old trunk and build it, the InvalidClassException problem has gone. Thanks.- Jian LiaoOn 11/11/06, Jian Liao [EMAIL PROTECTED] wrote: Thanks for all your response.I have worked around this issue by check out a fresh trunk and setup an empty maven repository, then build it successfully.I still keep the old environment and I can test again if someone fix this problem. thanks,- Jian LiaoOn 11/11/06, Gianny Damour [EMAIL PROTECTED] wrote: Hi,I had a look and it seems that the backward compatibility was onlypartially fixed; my bad: basically, GBeanData is backward compatible however it references GBeanInfo which is not. I will fix this problem.Thanks,GiannyOn 11/11/2006, at 4:38 AM, David Jencks wrote: I'm worried that we didn't fix all the backward compatibility issues adding priority into GBeanData and GBeanInfo.I wonder if you are doing an online build and somehow pulling down out of date config snapshots with old-style serialized GBeanInfos. I'll try to figure this out... but I could probably use some help from gianny or dblevins. Meanwhile doing an offline build or cleaning the geronimo artifacts out of your m2 repo may help. thanks david jencks On Nov 9, 2006, at 7:03 PM, Jian Liao wrote: I am trying to build geronimo trunk with command mvn clean install -U -up, but encountered the following exception while building Building Geronimo Configs :: Jetty Deployer. Could someone help me? thanks, - Jian Liao [INFO] - --- [ERROR] BUILD ERROR [INFO] - --- [INFO] Unable to create configuration for deployment org.apache.geronimo.gbean.GBeanInfo; local class incompatible: stream classdesc serialVersionUID = -619880406710221, local class serialVersionUID = 10536550 34244747613 [INFO] - --- [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException : Unable to create configu ration for deployment at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:559) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi fecycle(DefaultLifecycleExecutor.java :475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (Defau ltLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures( DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute (DefaultLi fecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java: 115) at org.apache.maven.cli.MavenCli.main (MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAcces sorImpl.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 create conf iguration for deployment at org.apache.geronimo.genesis.MojoSupport.execute (MojoSupport.java:137) at org.apache.maven.plugin.DefaultPluginManager.executeMojo (DefaultPlugi nManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (Defa ultLifecycleExecutor.java:534) ... 16 more Caused by: org.apache.geronimo.common.DeploymentException : Unable to create conf iguration for deployment at org.apache.geronimo.deployment.DeploymentContext.createTempConfigurat ion(DeploymentContext.java:121) at org.apache.geronimo.deployment.DeploymentContext .init (DeploymentCon text.java:101) at org.apache.geronimo.deployment.DeploymentContext.init (DeploymentCon text.java:81) at org.apache.geronimo.deployment.service.ServiceConfigBuilder.buildConf iguration(ServiceConfigBuilder.java:206) at org.apache.geronimo.deployment.service.ServiceConfigBuilder.buildConf iguration(ServiceConfigBuilder.java:178) at org.apache.geronimo.deployment.service.ServiceConfigBuilder$$FastClas sByCGLIB$$9f173be6.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethod Invoker.java :38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke (GBeanOperatio n.java:122) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke (GBeanInstance. java:820) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke
[jira] Commented: (GERONIMO-2515) load of geronimo/rmi-naming/1.1.1/car failed on Solaris 10
[ http://issues.apache.org/jira/browse/GERONIMO-2515?page=comments#action_12449080 ] Marcus Wibmer commented on GERONIMO-2515: - same problem running on solaris 10, java 1.5 , V60 x86 bash-3.00# echo $JAVA_HOME /usr bash-3.00# java -jar /usr/geronimo-1.1.1/bin/server.jar Booting Geronimo Kernel (in Java 1.5.0_01)... Starting Geronimo Application Server v1.1.1 [*-] 0% 3s Startup failed org.apache.geronimo.kernel.config.LifecycleException: load of geronimo/rmi-naming/1.1.1/car failed at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:294) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:275) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:250) at org.apache.geronimo.kernel.config.KernelConfigurationManager.loadConfiguration(KernelConfigurationManager.java:112) at org.apache.geronimo.kernel.config.KernelConfigurationManager$$FastClassByCGLIB$$b117102f.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:122) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:817) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$8cf056b2.loadConfiguration(generated) at org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:294) at org.apache.geronimo.system.main.Daemon.init(Daemon.java:74) at org.apache.geronimo.system.main.Daemon.main(Daemon.java:377) Caused by: org.apache.geronimo.kernel.repository.MissingDependencyException: Unable to resolve dependency org.apache.geronimo.specs/geronimo-activation_1.0.2_spec//jar at org.apache.geronimo.kernel.repository.DefaultArtifactResolver.resolveInClassLoader(DefaultArtifactResolver.java:119) at org.apache.geronimo.kernel.repository.DefaultArtifactResolver.resolveInClassLoader(DefaultArtifactResolver.java:98) at org.apache.geronimo.kernel.repository.DefaultArtifactResolver$$FastClassByCGLIB$$e847b746.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:122) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:817) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.kernel.repository.ArtifactResolver$$EnhancerByCGLIB$$1d1424d7.resolveInClassLoader(generated) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.resolveParentIds(SimpleConfigurationManager.java:466) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadDepthFirst(SimpleConfigurationManager.java:425) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:291) ... 15 more Server shutdown begun Server shutdown completed bash-3.00# load of geronimo/rmi-naming/1.1.1/car failed on Solaris 10 -- Key: GERONIMO-2515 URL: http://issues.apache.org/jira/browse/GERONIMO-2515 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: startup/shutdown Affects Versions: 1.1.1 Environment: Solaris 10 , JDK 1.4.2 Reporter: K Wesley Priority: Blocker $ java -jar server.jar Booting Geronimo Kernel (in Java 1.4.2_12)... Starting Geronimo Application Server v1.1.1 [*-] 0% 2s Startup failed org.apache.geronimo.kernel.config.LifecycleException: load of geronimo/rmi-naming/1.1.1/car failed at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:294) at
[jira] Commented: (GERONIMO-2515) load of geronimo/rmi-naming/1.1.1/car failed on Solaris 10
[ http://issues.apache.org/jira/browse/GERONIMO-2515?page=comments#action_12449086 ] M Wibmer commented on GERONIMO-2515: same outcome using Java 1.5.0_09 from java_ee_sdk-5_01-solaris-i586.bin bash-3.00# pwd /opt/SDK/jdk/bin bash-3.00# ./java -jar /usr/geronimo-1.1.1/bin/server.jar Booting Geronimo Kernel (in Java 1.5.0_09)... Starting Geronimo Application Server v1.1.1 [*-] 0% 3s Startup failed org.apache.geronimo.kernel.config.LifecycleException: load of geronimo/rmi-naming/1.1.1/car failed at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:294) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:275) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:250) at org.apache.geronimo.kernel.config.KernelConfigurationManager.loadConfiguration(KernelConfigurationManager.java:112) at org.apache.geronimo.kernel.config.KernelConfigurationManager$$FastClassByCGLIB$$b117102f.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:122) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:817) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$762e2ee4.loadConfiguration(generated) at org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:294) at org.apache.geronimo.system.main.Daemon.init(Daemon.java:74) at org.apache.geronimo.system.main.Daemon.main(Daemon.java:377) Caused by: org.apache.geronimo.kernel.repository.MissingDependencyException: Unable to resolve dependency org.apache.geronimo.specs/geronimo-activation_1.0.2_spec//jar at org.apache.geronimo.kernel.repository.DefaultArtifactResolver.resolveInClassLoader(DefaultArtifactResolver.java:119) at org.apache.geronimo.kernel.repository.DefaultArtifactResolver.resolveInClassLoader(DefaultArtifactResolver.java:98) at org.apache.geronimo.kernel.repository.DefaultArtifactResolver$$FastClassByCGLIB$$e847b746.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:122) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:817) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.kernel.repository.ArtifactResolver$$EnhancerByCGLIB$$651fd09.resolveInClassLoader(generated) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.resolveParentIds(SimpleConfigurationManager.java:466) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadDepthFirst(SimpleConfigurationManager.java:425) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:291) ... 15 more Server shutdown begun Server shutdown completed bash-3.00# load of geronimo/rmi-naming/1.1.1/car failed on Solaris 10 -- Key: GERONIMO-2515 URL: http://issues.apache.org/jira/browse/GERONIMO-2515 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: startup/shutdown Affects Versions: 1.1.1 Environment: Solaris 10 , JDK 1.4.2 Reporter: K Wesley Priority: Blocker $ java -jar server.jar Booting Geronimo Kernel (in Java 1.4.2_12)... Starting Geronimo Application Server v1.1.1 [*-] 0% 2s Startup failed org.apache.geronimo.kernel.config.LifecycleException: load of geronimo/rmi-naming/1.1.1/car failed at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:294) at
