RE: Error Upgrading to Turbine 2.2b3

[Johnny Quazar]

I also was stopping cold right at the tail end of my upgrade effort with this error.

I found it to be Torque.properties torque.database.default, I overlooked it. When I updated it to the proper production database name I got past that error. YMMV



At 12:23 PM -0500 9/3/02, Dave Everson wrote:

I have **tried** to dig into the code and identify the source of the
error.  This was a frustrating process, the method where the error is
getting generated is around 300 line of nested if-else clauses.  Putting
in debugging statements often caused greater harm.

This seems like a bug to me and that the security functionality in 2.2b3
is broken.  If one can't log into a site with 2.2b3, I wonder how many
more bug lurk in the rest of the code.  I see that someone else had the
same issue with no resolution and postponed their upgrade.  Is the
recommended course of action?

-----Original Message-----
From: Rodney Schneider [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 03, 2002 2:31 AM
To: Turbine Users List
Subject: Re: Error Upgrading to Turbine 2.2b3

On Tue, 3 Sep 2002 10:09, you wrote:

 Hi,

 Over the last several days, I have been in the process of testing the
 upgrade of our web application to Turbine 2.2b3 from 2.2b1.  I believe

I

 have worked through all the issues except for the following error that

I

 get when a user logs into the web application.  Can anybody shed some
 light on the reason for this error and how I can fix the error so that

I

 can complete the upgrade?

 Thanks,
 Dave

 [Sun Sep 01 21:54:50 CDT 2002] -- ERROR --
	Exception:
 org.apache.turbine.util.security.DataBackendException: Failed to build
 ACL for user 'sdsadmin': getGroups(Criteria) failed
	Stack Trace follows:
	java.lang.NullPointerException
	at
 org.apache.torque.util.BasePeer.createQueryString(BasePeer.java:1168)

Hi,

I am not sure why this exception is occurring, but why don't you try
editing
the BasePeer.java source code and adding some debugging output so that
you
can figure out which object on line 1168 is null?

That would probably be the quickest way of figuring out what is wrong
unless
someone else on this list has already encountered this exception.

I know my suggestion might seem obvoius, but I just thought I'd mention
it.

Kind regards,

-- Rodney

--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>




--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]