Re: [jira] Commented: (GERONIMO-554) Cannot start Geronimo Server with J2EEDeployment plan

David Jencks 27 Jan 2005 19:06:08 -0000

Hi Sandip,

I'm really confused about what might be happening because it's been working for me for a long time on os x and linux without your patch, and similar problems happened to a lot of people when the class moved to the common package. For a very long time there weren't any downloadable jars with the class in geronimo-common. I'm not entirely sure how that happened, I try to stay out of the build/distribution process. In fact, I think for a while some incorrect jars kept getting refreshed. I always build geronimo, openejb, tranql, tranql-connector, and howl, and sometimes activemq, myself to avoid these problems. Currently there is a really nasty circular dependency between geronimo and several of these other projects which more or less prevents building them individually. However, if you build geronimo, then the other projects, then geronimo again, the dependencies should work out ok. The "m:" build targets help to some extent also. There's supposed to be someone trying to fix this situation this week, I can only hope he succeeds :-)

I'll try to explain what is (supposed) to be happening with classpaths in assembly.

In project.xml, we list all the jars we're going to use. There are properties to indicate how we will use them. repository >> copied into geronimo repository, available for <dependency> elements in plans lib >> copied into lib directory, available to startup classpaths deploy >> added to "bootstrap" deployer.jar manifest classpath server >> added to server.jar manifest classpath client >> added to client.jar manifest classpath

So...

        <dependency>
            <groupId>geronimo</groupId>
            <artifactId>geronimo-common</artifactId>
            <version>${pom.currentVersion}</version>
            <properties>
                <lib>true</lib>
                <deploy>true</deploy>
                <repository>true</repository>
            </properties>
        </dependency>

puts the jar in both lib and the repo, and adds it to the deployer.jar manifest classpath

Can you check that the copy in lib actually has the DeploymentException class in it and that the jar is in the deployer.jar manifest classpath?

----------------

Thanks for nudging me about the transaction timeout issue. I'd like to ping the jta spec lead with some related questions. I'm having a little trouble figuring out who that is:-) Could you send me their email address if you have it handy?

many thanks!

let me know if I can help with anything,
david jencks


On Jan 27, 2005, at 10:35 AM, Sandip Ghayal wrote:

Hi David,
I cleaned up my old geronimo directory and downloaded
the entire directory today.
So it can't be old code.
Also I found that once I put the common's jar file in
the plan then it works properly.
So for some reason common's jar is not in the
classpath when starting server with J2EE Deployment. I
also looked at parent plan for J2EE Deployment and
i.e. deployment-system-plan and this plan also does
not have common's jar file in the classpath.
My knowledge about Maven is limited. So when you put
up the dependecy in maven does it mean its going to be
put in the final plan too ?
Cheers,
Sandip
--- "David Jencks (JIRA)" <[EMAIL PROTECTED]>
wrote:
     [
http://issues.apache.org/jira/browse/GERONIMO-554? page=comments#action_58173
]
David Jencks commented on GERONIMO-554:
---------------------------------------
I think that there is a different problem in your
setup.
The geronimo-common jar is already  on the
j2ee-deployer classpath because it is in the startup
classpath of the parent configuration.
See assembly maven.xml lines 218ff where bootstrap
is using ${deploy.classpath}
In maven.xml lines 95ff deploy.classpath is
constructed using the project.xml dependencies
marked with "deploy"
in project.xml line 105 geronimo-common is marked
with deploy.
Is it possible that you had an old copy of
geronimo-common?  When DeploymentException was moved
there it caused a lot of problems like this.
Cannot start Geronimo Server with J2EEDeployment
plan
-----------------------------------------------------
         Key: GERONIMO-554
         URL:
http://issues.apache.org/jira/browse/GERONIMO-554
     Project: Apache Geronimo
        Type: Bug
  Components: general
 Environment: Windows XP
    Reporter: Sandip Ghayal
 Attachments: j2eeDeployerPlan.patch
When trying to start Geronimo with J2EEDeployer
plan Server crashes with following exception
11:39:55,217 INFO [ReadOnlyRepository] Repository
root is file:/F:/geronimo/mod
ules/assembly/target/geronimo-1.0-SNAPSHOT/repository/
Exception in thread "main"
java.lang.NoClassDefFoundError:
org/apache/geronimo/c
ommon/DeploymentException
        at
java.lang.Class.getDeclaredMethods0(Native Method)
at
java.lang.Class.privateGetDeclaredMethods(Class.java:1647)
at
java.lang.Class.getMethod0(Class.java:1893)
at
java.lang.Class.getMethod(Class.java:976)
at

org.apache.geronimo.gbean.runtime.GBeanOperation.<init>(GBeanOperatio
n.java:90)
        at
org.apache.geronimo.gbean.runtime.GBeanInstance.<init>(GBeanInstance.
java:244)
        at
org.apache.geronimo.kernel.Kernel.loadGBean(Kernel.java:327)
at

org.apache.geronimo.kernel.config.Configuration.<init>(Configuration.
java:221)
        at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at

sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct
orAccessorImpl.java:39)
        at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC
onstructorAccessorImpl.java:27)
        at
java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at

org.apache.geronimo.gbean.runtime.GBeanInstance$GBeanLifecycleCallbac
k.doStart(GBeanInstance.java:763)
        at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart
(GBeanInstanceState.java:318)
        at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInsta
nceState.java:113)
        at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(G
BeanInstanceState.java:135)
        at
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanI
nstance.java:475)
        at
org.apache.geronimo.kernel.Kernel.startRecursiveGBean(Kernel.java:348
)
        at
org.apache.geronimo.system.main.Daemon.main(Daemon.java:154)
The reason for the issue is because
geronimo-common-<version#>.jar is absent from the
j2ee-deployer-plan.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of
the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug
to report see:
   http://www.atlassian.com/software/jira
            
__________________________________
Do you Yahoo!?
Read only the mail you want - Yahoo! Mail SpamGuard.
http://promotions.yahoo.com/new_mail

Re: [jira] Commented: (GERONIMO-554) Cannot start Geronimo Server with J2EEDeployment plan

Reply via email to