Hello
If you're seeing this:
java.lang.NullPointerException
com.remedy.arsys.goat.field.FieldGraph.getFieldGraphKey(Unknown
Source)
Then I'm afraid it is a product defect. NPEs are runtime exceptions, ie
they happen and shouldn't. That's why Java devs put in an if statement.
Tomcat
If the suggestions LJ made don't work you can try the the steps below.
We recently had an issue where one user would get HTTP 500 error no matter
what machine they logged in from. It turns out there was something the
system did not like about their AR System User Preference record (let us
gt;
> ** **
>
> *Danny Herrera*
>
> ** **
>
> *From:* Action Request System discussion list(ARSList) [mailto:
> arslist@ARSLIST.ORG] *On Behalf Of *Longwing, Lj
> *Sent:* Thursday, August 08, 2013 9:46 AM
>
> *To:* arslist@ARSLIST.ORG
> *Subject:* Re: HTTP 500 err
rera
From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>] On Behalf Of Longwing,
Lj
Sent: Thursday, August 08, 2013 8:23 AM
To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>
Subject: Re: HTTP 500 error
**
thick client wouldn't be
> *From:* Action Request System discussion list(ARSList) [mailto:
> arslist@ARSLIST.ORG] *On Behalf Of *Longwing, Lj
> *Sent:* Thursday, August 08, 2013 8:23 AM
> *To:* arslist@ARSLIST.ORG
> *Subject:* Re: HTTP 500 error
>
> ** **
>
> **
>
> thick client would
: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Longwing, Lj
Sent: Thursday, August 08, 2013 8:23 AM
To: arslist@ARSLIST.ORG
Subject: Re: HTTP 500 error
**
thick client wouldn't be getting a web 500 error of course because it isn't
using the we
thick client wouldn't be getting a web 500 error of course because it isn't
using the web :)so...this is saying that your Web server is getting a
null value in an unexpected place. I would start by flushing the Mid-Tier
cache, and then the user cache if they continue experiencing issues.
On
This is bugging me, this is happening to only two users right now that I know
of on the web interface of the Change Management module. Using the thick
client to access this works fine however. Any ideas on why this would be
happening?
HTTP Status 500 -
type Ex
8 matches
Mail list logo