geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Howe (JIRA)" <>
Subject [jira] Commented: (GERONIMO-2168) NPE when deploying RAR
Date Sun, 09 Jul 2006 21:46:30 GMT
    [ ] 

Tim Howe commented on GERONIMO-2168:

Donald, thanks for your input.

I haven't yet.  Currently I'm rebuilding Geronimo from source and adding debugging statements.
 However if I can't quickly and obviously find the problem I'll try that.  Regardless, I'll
update with the results.

Are your suggestions related to known issues or just an attempt to get rid of possible trouble

I thought I'd seen spaces in some of the names of sample applications, and Geronimo seems
to be escaping them properly.  Where should they be removed from?  The deployment plan, ra.xml,
or both?

As far as the version number, is Maven used for deployment as well?  I thought it was only
used for building Geronimo itself.  In fact, before beginning to build from source, I didn't
even have Maven installed.

> NPE when deploying RAR
> ----------------------
>          Key: GERONIMO-2168
>          URL:
>      Project: Geronimo
>         Type: Bug
>     Security: public(Regular issues) 
>     Versions: 1.1
>  Environment: Solaris 9 (Sparc), Java 1.5.0_06 (also appears in 1.4.2_05)
>     Reporter: Tim Howe
>     Priority: Critical

> I've been using Geronimo 1.0, and now 1.1, as the app server for the
> development of a JCA connector for our proprietary EIS and generally
> been very happy with it.
> I've had no problem running servlets, deploying WARs, and the like.
> However, I've run into a problem deploying a RAR that I built.  I view
> it as highly probably that there's a bug somewhere in my resource
> adapter, but it seems to be triggering a bug in Geronimo, which appears
> in both Java 1.4.2 and 1.5:
> {quote}
> {{23:52:38,091 ERROR [GBeanInstanceState] Error while starting; GBean is now in the FAILED
state: abstractName="com.celebrityresorts/rcc/0/rar?J2EEApplication=null,JCAConnectionFactory=Celebrity%20Resorts%20RCC%20development%20instance,JCAResource=com.celebrityresorts/rcc/0/rar,ResourceAdapter=com.celebrityresorts/rcc/0/rar,ResourceAdapterModule=com.celebrityresorts/rcc/0/rar,j2eeType=JCAManagedConnectionFactory,name=Celebrity%20Resorts%20RCC%20development%20instance"
> java.lang.NullPointerException
>         at
>         at
>         at
>         at java.lang.Throwable.printStackTrace(
>         at org.apache.geronimo.gbean.runtime.GBeanInstance.printException(
>         at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(
>         at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(
>         at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(
>         at org.apache.geronimo.gbean.runtime.GBeanInstance.start(
>         at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(
>         at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(
>         at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(
>         at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(
>         at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(
>         at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(
>         at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(
>         at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(
>         at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(
>         at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(}}
> {quote}
> and so on.  The only thing I can figure is that somehow the Exception
> getting thrown is null, but I can't see how, as it seems to stem from
> bq. {{throw new Exception("A reference has failed so construction can not complete");}}
> so I'm very confused.  Of course it's also quite late for me and I may
> be reading the stack trace wrong.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message