Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@geronimo.apache.org
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Received:X-Yahoo-SMTP:X-YMail-OSG:X-Yahoo-Newman-Property:Message-Id:From:To:In-Reply-To:Content-Type:Content-Transfer-Encoding:Mime-Version:Subject:Date:References:X-Mailer;
  b=OGs8m6VRyxBWe2186JE/bAhAvKh6XNs2sfVOTG31Q11G5YZaDUAPOoh6eF+EkRpJl2QNwDJdLbboGQTK0Zvk+J3TmyfqAKlHnyjqANCIuf+DvEI2v6WEU/032MSSe2qlUNP4RjVIl4K983lXZVTaeNsRt8DVviz8WfjFTjXY4fk=
  ;
Message-Id: <CE546ACD-4723-48AC-B01D-F8E4B0E88126@yahoo.com>
From: David Jencks <david_jencks@yahoo.com>
To: user@geronimo.apache.org
In-Reply-To: <F1EC0CBD-BBF7-4AC5-969F-4D4BE822029D@gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Subject: Re: Difference between server restart and application restart
Date: Fri, 26 Jun 2009 09:15:42 -0700
References: <24200158.post@talk.nabble.com>
 <0B241F5A-83D0-4D6B-BB06-28D74B55B701@yahoo.com>
 <24215874.post@talk.nabble.com>
 <24130986-5799-4D51-8E35-AF5FC24AF21C@yahoo.com>
 <F1EC0CBD-BBF7-4AC5-969F-4D4BE822029D@gmail.com>


On Jun 26, 2009, at 6:11 AM, Kevan Miller wrote:

>
> On Jun 26, 2009, at 3:26 AM, David Jencks wrote:
>
>>
>> On Jun 26, 2009, at 12:02 AM, chander_bawa wrote:
>>
>>>
>>> Thanks Djencks,
>>> You are right. I tried deploying the ear from command line and  
>>> faced the
>>> same issue.
>>> The thing is i am working on upgrading the geronimo server from  
>>> 1.1.1 to
>>> 2.1.4 and the application is working perfectly in 1.1.1
>>> My confusion is why this error came when app is deployed on 2.1.4  
>>> when it
>>> worked perfectly on 1.1.1?
>>
>> The only reason I can think that this might work on 1.1.1 is that  
>> we had a bug in the jndi implementation in 1.1.1 that lets the  
>> lookup succeed.  It should fail on 1.1.1 just as it does on 2.1.4.
>>
>> If you answer the questions I asked in my previous reply I might be  
>> able to suggest a way to proceed.  For instance you might be able  
>> to look the destinations up in the jca:/ global jndi context.
>
> I don't think they're looking for destinations. Instead, it's  
> looking for a TransactionManager. This same problem was reported  
> back in April. That user reported that the oracle adapter was  
> looking for "java:comp/pm/TransactionManager". I wonder if they  
> could be configured to look for "java:/TransactionManager".
>
> I'm also wondering if throwing a RunTime exception is the  
> appropriate behavior, in this situation. Why not a NamingException?  
> I confess that the subtleties of JNDI are frequently lost on me...
>

I think a RuntimeException might be appropriate here..... there's a  
major logic problem in how the user is attempting to use jndi, this is  
not a problem due to someone forgetting to bind something in jndi.

thanks
david jencks


> --kevan