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=YX3ztnrkknhMzisgzdxEufqdynFpieDKY7DnrVd2N0IDNXozRjrJeRJ2DvDNiuoZL6STmVd9xgF0CWd8GEvO3EIh7DFwry270AQGfHtpg6yNHi450gOvbEAu/IIipGrY3iy1vWv5Ss5c6X+gNoM2VhlvvA0tlIAgsHRbe2aHaXI=
  ;
Message-Id: <13635B9A-D809-4EFD-A680-502419247819@yahoo.com>
From: David Jencks <david_jencks@yahoo.com>
To: user@geronimo.apache.org
In-Reply-To: <859B6CF7-AF35-4AFB-883A-42F6CD06D28F@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 15:31:37 -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>
 <CE546ACD-4723-48AC-B01D-F8E4B0E88126@yahoo.com>
 <859B6CF7-AF35-4AFB-883A-42F6CD06D28F@gmail.com>


On Jun 26, 2009, at 1:11 PM, Kevan Miller wrote:

>
> On Jun 26, 2009, at 12:15 PM, David Jencks wrote:
>
>>
>> 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.
>
> Well, not necessarily a logic error. Code may be looking for a  
> TransactionManager in a number of jndi locations. For example, see  
> the following OpenJPA code -- http://svn.apache.org/viewvc/incubator/openjpa/trunk/openjpa-kernel/src/main/java/org/apache/openjpa/ee/AutomaticManagedRuntime.java?annotate=421741&pathrev=421741
>
> They are catching Throwable, when looking for a TM in a number of  
> locations. Don't know what Oracle is doing, here. But it sure sounds  
> like they are treating a RuntimeException differently from a  
> NamingException. You might argue that they should be more accepting.  
> We've had two people report this problem. I'm just trying to see if  
> we can/should *fix* the problem...

Ya, you're right... I guess NotContextException is probably good.

thanks
david jencks

>
> --kevan