Return-Path: X-Original-To: apmail-tomcat-users-archive@www.apache.org Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C1A59E995 for ; Wed, 16 Jan 2013 21:58:20 +0000 (UTC) Received: (qmail 11761 invoked by uid 500); 16 Jan 2013 21:58:14 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 11688 invoked by uid 500); 16 Jan 2013 21:58:14 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 11638 invoked by uid 99); 16 Jan 2013 21:58:14 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Jan 2013 21:58:14 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of rop049@gmail.com designates 209.85.212.42 as permitted sender) Received: from [209.85.212.42] (HELO mail-vb0-f42.google.com) (209.85.212.42) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Jan 2013 21:58:10 +0000 Received: by mail-vb0-f42.google.com with SMTP id fa15so1892521vbb.29 for ; Wed, 16 Jan 2013 13:57:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=2pwUgwEMdRzBR4s2ilvJxZmsk6N3bgOxkbDfC6Qd6EY=; b=btg9dWc2WXurM1JwTjdIsd4IcqgcY7MMlcugRmpRzMhpyPvNWAqPESqBCdZQENuj87 eEApbCsZ76mQsni3nub30fLRQmWy1/T1/OKykZ/n1GtbKPvV/3P1tWfQaljnRCKOoRuQ VF3rxJjqx7X47XBdML4zTcrtxRL+nSxwcW4brOlsBVYFhGahkAcBjbnJS7eitDVt1IJS kefiYHebjeiIo908sUgRdIDVDYUyJHQSQPIkZb9u2XXyGHOtQV9gB6Yt5rLVrZTBDaSF eLLW/l/ZcTJ8o6tVJ4MLp+7MXxWFoexetHzzGXCnoSGjUY7kFZbtKumS0F6cSkNhfZ57 TraQ== MIME-Version: 1.0 X-Received: by 10.220.108.142 with SMTP id f14mr3068264vcp.9.1358373469367; Wed, 16 Jan 2013 13:57:49 -0800 (PST) Received: by 10.58.132.211 with HTTP; Wed, 16 Jan 2013 13:57:49 -0800 (PST) In-Reply-To: References: <99C8B2929B39C24493377AC7A121E21FC49B0EDAC4@USEA-EXCH8.na.uis.unisys.com> <99C8B2929B39C24493377AC7A121E21FC49B0EDC59@USEA-EXCH8.na.uis.unisys.com> <50F70299.2030608@verizon.net> Date: Wed, 16 Jan 2013 22:57:49 +0100 Message-ID: Subject: Re: Is error with Bamboo Sonar plugin because of Tomcat 6 instead of Tomcat 7? From: rop To: Tomcat Users List Content-Type: multipart/alternative; boundary=f46d04388ed51d2bbb04d36ef8d6 X-Virus-Checked: Checked by ClamAV on apache.org --f46d04388ed51d2bbb04d36ef8d6 Content-Type: text/plain; charset=ISO-8859-1 Googling the exception, turns up this: https://answers.atlassian.com/questions/54260/potenntial-incopmatibilty-between-tomcat-dpcp-oracle-active-objects If that doesnt answer your question james@atlassian.com is asking you to contact him :) 2013/1/16 KARR, DAVID > > -----Original Message----- > > From: David kerber [mailto:dckerber@verizon.net] > > Sent: Wednesday, January 16, 2013 11:42 AM > > To: Tomcat Users List > > Subject: Re: Is error with Bamboo Sonar plugin because of Tomcat 6 > instead of > > Tomcat 7? > > > > On 1/16/2013 2:38 PM, KARR, DAVID wrote: > > >> -----Original Message----- > > >> From: Caldarale, Charles R [mailto:Chuck.Caldarale@unisys.com] > > >> Sent: Wednesday, January 16, 2013 10:58 AM > > >> To: Tomcat Users List > > >> Subject: RE: Is error with Bamboo Sonar plugin because of Tomcat 6 > instead > > of > > >> Tomcat 7? > > >> > > >>> From: KARR, DAVID [mailto:dk068x@att.com] > > >>> Subject: RE: Is error with Bamboo Sonar plugin because of > > >>> Tomcat 6 instead of Tomcat 7? > > >> > > >>>>> We're running Bamboo 3.4.3 in Tomcat 6.0.20. It mostly apparently > > >> works > > >>>>> fine, but yesterday I tried to get the Bamboo Sonar plugin working, > > >>>> > > >>>> Did you leave out "in Tomcat 7" at the end there? > > >> > > >>> I don't know what you mean. Our Bamboo is running in Tomcat 6. I'm > > >> wondering > > >>> whether the error is due to a change in the Tomcat API between > Tomcat 6 > > and > > >> 7. > > >> > > >> You're not explaining your problem. First you say you have Bamboo > running > > in > > >> Tomcat 6.0.20, then you say it's not running, you're getting an > exception. > > >> (Remember that very few - if any - people on this list have any idea > what > > >> Bamboo is, let alone how it works with Tomcat.) Since your subject > line > > >> refers to Tomcat 7, I assumed (bad idea) that you were having problems > > >> migrating to Tomcat 7. So what's really going on (be precise)? > > > > > > We're running Bamboo with Tomcat 6. We're trying to add the Sonar > plugin. > > When we try to configure it, we get this exception when it tries to call > that > > specific Tomcat API. The theory that I'm exploring is that the plugin > > requires Bamboo to be running with Tomcat 7, not Tomcat 6. I don't want > to > > try moving to Tomcat 7 unless we have some assurance that that will > resolve > > the problem. > > > > Why don't you check with the Bamboo people? As Chuck said, there > > probably aren't very many people here who know anything about Bamboo. I > > certainly have never heard of it. > > That was the first thing I did. Bamboo is a commercial product, and they > don't support the Sonar plugin. I'm also asking the group that built the > Sonar plugin, but replies to that are slow. I also asked on the Sonar > mailing list. Checking with tomcat-users was only the last step. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org > For additional commands, e-mail: users-help@tomcat.apache.org > > --f46d04388ed51d2bbb04d36ef8d6--