Return-Path: Delivered-To: apmail-incubator-ofbiz-user-archive@locus.apache.org Received: (qmail 33154 invoked from network); 1 Nov 2006 19:11:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 1 Nov 2006 19:11:45 -0000 Received: (qmail 36716 invoked by uid 500); 1 Nov 2006 19:11:55 -0000 Delivered-To: apmail-incubator-ofbiz-user-archive@incubator.apache.org Received: (qmail 36581 invoked by uid 500); 1 Nov 2006 19:11:54 -0000 Mailing-List: contact ofbiz-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ofbiz-user@incubator.apache.org Delivered-To: mailing list ofbiz-user@incubator.apache.org Received: (qmail 36572 invoked by uid 99); 1 Nov 2006 19:11:54 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Nov 2006 11:11:54 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [63.246.7.15] (HELO ofbiz01.contegix.com) (63.246.7.15) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Nov 2006 11:11:38 -0800 Received: (qmail 5041 invoked by uid 89); 1 Nov 2006 19:11:17 -0000 Received: from unknown (HELO ?192.168.1.9?) (jonesde@ofbiz.org@71.4.72.166) by ofbiz01.contegix.com with SMTP; 1 Nov 2006 19:11:17 -0000 Mime-Version: 1.0 (Apple Message framework v752.3) In-Reply-To: References: Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes; format=flowed Message-Id: <91698917-7767-4602-9502-9266F2E802B6@undersunconsulting.com> Content-Transfer-Encoding: quoted-printable From: David E Jones Subject: Re: Error coming frequenly on ofbizUrl Date: Wed, 1 Nov 2006 12:11:09 -0700 To: ofbiz-user@incubator.apache.org X-Mailer: Apple Mail (2.752.3) X-Virus-Checked: Checked by ClamAV on apache.org Please forgive me if this seems pretentious, but could I make a small =20= suggestion? Instead of sending a screen shot of the user interface, go to the log =20= file and look at the full output generated by the server and if =20 needed copy and paste that into an email. This has 2 benefits: 1. you get more complete information, and information that is MEANT =20 for developers to see; in this case, for example, the text in the =20 screen shot does not show the root cause and that is necessary to get =20= even a hint at what might be happening; this stack trace is nearly =20 useless 2. a block of text is much smaller and more efficient to send in an =20 email (consider that this screen shot at 3 MB sent to hundreds of =20 people caused over 1GB of data to be sent out from the ASF mailing =20 list server... So, for a first step toward a "way out", doing the above is what I =20 recommend for now and in the future. -David On Nov 1, 2006, at 9:38 AM, Sayoke Shome wrote: > Hi all, > > I am getting an error very frequently in my ofbiz application, =20 > which is not easily reproducible. Whenever we are using =93ofbizUrl=94 = =20 > in
tag it is throwing up error trace on browser. But if I =20 > just do a refresh, it is showing the page properly as if the error =20 > never occurred. > > > > As it is saying it is failing to get the required map instance and =20 > on second time it is getting the instance properly. > > Is it a bug in ofbiz or I am missing something. Please suggest me =20 > what is the way out. > > > > Thanks and Regards, > > > > Sayoke Shome | Technical Associate | Techmahindra Ltd | Gigaspace, =20 > Gama 1 | Vimannagar, Pune | mobile : 09960969788 > > > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D > > Tech Mahindra, formerly Mahindra-British Telecom. > > Disclaimer: > > This message and the information contained herein is proprietary =20 > and confidential and subject to the Tech Mahindra policy statement, =20= > you may review at http://www.techmahindra.com/Disclaimer.html =20 > externally and http://tim.techmahindra.com/Disclaimer.html =20 > internally within Tech Mahindra. > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D >