On Monday, October 1, 2012, Jeff Pyle <[email protected]> wrote:
> Tonight I did a yum update and found myself with most sipx packages at
build rev 548.  The sipxconfig web interface reports (4.6.0.
2012-09-28EDT03:09:16 ip-10-72-43-110.ec2.internal).  No effect on this
error.  I still see the same exception.
>


Yes, it wasn't addressed. You previously attached sipxproxy log, can you
attach sipxconfig.log instead?

George
> - Jeff
>
> On Sat, Sep 29, 2012 at 4:29 PM, Jeff Pyle <[email protected]>
wrote:
>>
>> Indeed.  The entire exception is attached.  The main part of it is also
here:
>>>
>>>
"2012-09-29T20:27:11.749000Z":553:JAVA:WARNING:sipx46.dtcle.fvd.local:P2-7:00000000:RequestExceptionReporter:"Unable
to process client request: Unable to read OGNL expression '<parsed OGNL
expression>' of
$UserConferencesPanel_168@f2146ec1[user/UserConferences/userConferencesPanel]:
java.lang.NullPointerException"
>>> org.apache.tapestry.BindingException: Unable to read OGNL expression
'<parsed OGNL expression>' of
$UserConferencesPanel_168@f2146ec1[user/UserConferences/userConferencesPanel]:
java.lang.NullPointerException
[context:/WEB-INF/conference/UserConferencesPanel.html, line 2]
>>
>> - Jeff
>>
>> On Sat, Sep 29, 2012 at 3:05 AM, George Niculae <[email protected]> wrote:
>>>
>>> On Sat, Sep 29, 2012 at 6:03 AM, Jeff Pyle <[email protected]>
wrote:
>>> > Hello,
>>> >
>>> > Version 4.6 build 465.
>>> >
>>> > I've noticed if I have any conferences defined anywhere on the system,
>>> > accessing the Conferences page of any user generates "An internal
error has
>>> > occurred. Click here to continue."  I can access them through the
Features
>>> > -> Conferences route, however.
>>> >
>>> > If there are no conferences defined I can access a user's conference
screen.
>>> > I can click the "Add New Conference" link and fill in the fields.
 When I
>>> > click OK, I receive the same error, although the conference does
create.
>>> >
>>> > Restarting services doesn't have any effect.
>>> >
>>>
>>> Can you provide /var/log/sipxpbx/sipxconfig.log, there should be the
exception
>>>
>>> George
>>> _______________________________________________
>>> sipx-users mailing list
>>> [email protected]
>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>
>
>
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to