You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@isis.apache.org by Erik de Hair <er...@pocos.nl> on 2014/11/11 10:15:02 UTC
Exception by restful different than shown by Wicket viewer
Hi,
I have a service method that I only want to expose via restful. I
suppressed the method from showing up in the Wicket viewer so I didn't
try to call it with the Wicket viewer.
Now restful throws an error(which is not very useful) when calling the
method:
org.apache.tomcat.util.http.parser.TokenMgrError: Lexical error at line 1, column 29. Encountered: ":" (58), after : ""
org.apache.tomcat.util.http.parser.HttpParserTokenManager.getNextToken(HttpParserTokenManager.java:434)
org.apache.tomcat.util.http.parser.HttpParser.jj_ntk(HttpParser.java:300)
org.apache.tomcat.util.http.parser.HttpParser.MediaType(HttpParser.java:21)
For some reason I now also exposed the action via Wicket. That way I get
another exception with more useful information about my problem:
javax.jdo.JDOUserExceptionInvalid operator "=". Did you mean to use
"=="?
org.datanucleus.api.jdo.NucleusJDOHelper#getJDOExceptionForNucleusException(NucleusJDOHelper.java:549)
org.datanucleus.api.jdo.JDOQuery#execute(JDOQuery.java:299)
nl.pocos.dom.workflow.WorkFlowStatusses#checkNumberOfPGSMLicences(WorkFlowStatusses.java:55)
sun.reflect.NativeMethodAccessorImpl#invoke0(NativeMethodAccessorImpl.java:-2)
sun.reflect.NativeMethodAccessorImpl#invoke(NativeMethodAccessorImpl.java:57)
sun.reflect.DelegatingMethodAccessorImpl#invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method#invoke(Method.java:606)
After fixing this error the restful call works fine. I had this
behaviour before but couldn't reproduce it. It looks like the
TokenMgrError is thrown when some exception occurs in an action called
via restful and the real reason/exception can't be found in the logs.
Is there some reason not to show the original exception?
Met vriendelijke groet,
Erik de Hair
--
Pocos bv
Croy 9c - 5653 LC Eindhoven
Telefoon: 088 0100 700 - Fax: 088 0100 799
http://www.pocos.nl/ - http://www.sipo.nl/
K.v.K. nummer: 17097024
Follow Pocos bv
<https://twitter.com/intent/follow?original_referer=https%3A%2F%2Ftwitter.com%2Fabout%2Fresources%2Fbuttons®ion=follow_link&screen_name=Pocosbv&source=followbutton&variant=2.0>
Aanmelden van incidenten en/of changes graag via servicedesk@pocos.nl
<ma...@pocos.nl>
Re: Exception by restful different than shown by Wicket viewer
Posted by Dan Haywood <da...@haywood-associates.co.uk>.
many thanks
On 11 November 2014 09:39, Erik de Hair <er...@pocos.nl> wrote:
> Raised ticket ISIS-945 [1]
>
> Erik
>
> [1] https://issues.apache.org/jira/browse/ISIS-945
>
> <ma...@pocos.nl>
> On 11/11/2014 10:20 AM, Dan Haywood wrote:
>
>> Thanks for this... should be easy enough for me to reproduce.
>>
>> In 1.8.0-SNAPSHOT I have done some improvements so that the
>> ExceptionRecognizer services is now used by the Restful viewer as well as
>> Wicket viewer. So it might've been fixed.
>>
>> Even so, could you raise a ticket so that this doesn't get lost as an
>> issue?
>>
>> Thx
>> Dan
>>
>>
>>
>> On 11 November 2014 09:15, Erik de Hair <erik@pocos.nl <mailto:
>> erik@pocos.nl>> wrote:
>>
>> Hi,
>>
>> I have a service method that I only want to expose via restful. I
>> suppressed the method from showing up in the Wicket viewer so I
>> didn't try to call it with the Wicket viewer.
>>
>> Now restful throws an error(which is not very useful) when calling
>>
>> the method:
>>
>> org.apache.tomcat.util.http.parser.TokenMgrError: Lexical error at
>> line 1, column 29. Encountered: ":" (58), after : ""
>> org.apache.tomcat.util.http.parser.HttpParserTokenManager.
>> getNextToken(HttpParserTokenManager.java:434)
>> org.apache.tomcat.util.http.parser.HttpParser.jj_ntk(
>> HttpParser.java:300)
>> org.apache.tomcat.util.http.parser.HttpParser.MediaType(
>> HttpParser.java:21)
>>
>>
>> For some reason I now also exposed the action via Wicket. That way
>> I get another exception with more useful information about my problem:
>>
>> javax.jdo.JDOUserExceptionInvalid operator "=". Did you mean to
>> use "=="?
>> org.datanucleus.api.jdo.NucleusJDOHelper#
>> getJDOExceptionForNucleusException(NucleusJDOHelper.java:549)
>> org.datanucleus.api.jdo.JDOQuery#execute(JDOQuery.java:299)
>> nl.pocos.dom.workflow.WorkFlowStatusses#checkNumberOfPGSMLicences(
>> WorkFlowStatusses.java:55)
>> sun.reflect.NativeMethodAccessorImpl#invoke0(
>> NativeMethodAccessorImpl.java:-2)
>> sun.reflect.NativeMethodAccessorImpl#invoke(
>> NativeMethodAccessorImpl.java:57)
>> sun.reflect.DelegatingMethodAccessorImpl#invoke(
>> DelegatingMethodAccessorImpl.java:43)
>> java.lang.reflect.Method#invoke(Method.java:606)
>>
>> After fixing this error the restful call works fine. I had this
>> behaviour before but couldn't reproduce it. It looks like the
>> TokenMgrError is thrown when some exception occurs in an action
>> called via restful and the real reason/exception can't be found in
>> the logs.
>>
>> Is there some reason not to show the original exception?
>>
>> Met vriendelijke groet,
>>
>> Erik de Hair
>>
>> --
>> Pocos bv
>> Croy 9c - 5653 LC Eindhoven
>> Telefoon: 088 0100 700 - Fax: 088 0100 799
>> http://www.pocos.nl/ - http://www.sipo.nl/
>> K.v.K. nummer: 17097024
>> Follow Pocos bv
>> <https://twitter.com/intent/follow?original_referer=https%
>> 3A%2F%2Ftwitter.com%2Fabout%2Fresources%2Fbuttons®ion=
>> follow_link&screen_name=Pocosbv&source=followbutton&variant=2.0>
>>
>> Aanmelden van incidenten en/of changes graag via
>> servicedesk@pocos.nl <ma...@pocos.nl>
>>
>>
>>
>
Re: Exception by restful different than shown by Wicket viewer
Posted by Erik de Hair <er...@pocos.nl>.
Raised ticket ISIS-945 [1]
Erik
[1] https://issues.apache.org/jira/browse/ISIS-945
<ma...@pocos.nl>
On 11/11/2014 10:20 AM, Dan Haywood wrote:
> Thanks for this... should be easy enough for me to reproduce.
>
> In 1.8.0-SNAPSHOT I have done some improvements so that the
> ExceptionRecognizer services is now used by the Restful viewer as well
> as Wicket viewer. So it might've been fixed.
>
> Even so, could you raise a ticket so that this doesn't get lost as an
> issue?
>
> Thx
> Dan
>
>
>
> On 11 November 2014 09:15, Erik de Hair <erik@pocos.nl
> <ma...@pocos.nl>> wrote:
>
> Hi,
>
> I have a service method that I only want to expose via restful. I
> suppressed the method from showing up in the Wicket viewer so I
> didn't try to call it with the Wicket viewer.
>
> Now restful throws an error(which is not very useful) when calling
> the method:
>
> org.apache.tomcat.util.http.parser.TokenMgrError: Lexical error at line 1, column 29. Encountered: ":" (58), after : ""
> org.apache.tomcat.util.http.parser.HttpParserTokenManager.getNextToken(HttpParserTokenManager.java:434)
> org.apache.tomcat.util.http.parser.HttpParser.jj_ntk(HttpParser.java:300)
> org.apache.tomcat.util.http.parser.HttpParser.MediaType(HttpParser.java:21)
>
>
> For some reason I now also exposed the action via Wicket. That way
> I get another exception with more useful information about my problem:
>
> javax.jdo.JDOUserExceptionInvalid operator "=". Did you mean to
> use "=="?
> org.datanucleus.api.jdo.NucleusJDOHelper#getJDOExceptionForNucleusException(NucleusJDOHelper.java:549)
> org.datanucleus.api.jdo.JDOQuery#execute(JDOQuery.java:299)
> nl.pocos.dom.workflow.WorkFlowStatusses#checkNumberOfPGSMLicences(WorkFlowStatusses.java:55)
> sun.reflect.NativeMethodAccessorImpl#invoke0(NativeMethodAccessorImpl.java:-2)
> sun.reflect.NativeMethodAccessorImpl#invoke(NativeMethodAccessorImpl.java:57)
> sun.reflect.DelegatingMethodAccessorImpl#invoke(DelegatingMethodAccessorImpl.java:43)
> java.lang.reflect.Method#invoke(Method.java:606)
>
> After fixing this error the restful call works fine. I had this
> behaviour before but couldn't reproduce it. It looks like the
> TokenMgrError is thrown when some exception occurs in an action
> called via restful and the real reason/exception can't be found in
> the logs.
>
> Is there some reason not to show the original exception?
>
> Met vriendelijke groet,
>
> Erik de Hair
>
> --
> Pocos bv
> Croy 9c - 5653 LC Eindhoven
> Telefoon: 088 0100 700 - Fax: 088 0100 799
> http://www.pocos.nl/ - http://www.sipo.nl/
> K.v.K. nummer: 17097024
> Follow Pocos bv
> <https://twitter.com/intent/follow?original_referer=https%3A%2F%2Ftwitter.com%2Fabout%2Fresources%2Fbuttons®ion=follow_link&screen_name=Pocosbv&source=followbutton&variant=2.0>
>
> Aanmelden van incidenten en/of changes graag via
> servicedesk@pocos.nl <ma...@pocos.nl>
>
>
Re: Exception by restful different than shown by Wicket viewer
Posted by Dan Haywood <da...@haywood-associates.co.uk>.
Thanks for this... should be easy enough for me to reproduce.
In 1.8.0-SNAPSHOT I have done some improvements so that the
ExceptionRecognizer services is now used by the Restful viewer as well as
Wicket viewer. So it might've been fixed.
Even so, could you raise a ticket so that this doesn't get lost as an issue?
Thx
Dan
On 11 November 2014 09:15, Erik de Hair <er...@pocos.nl> wrote:
> Hi,
>
> I have a service method that I only want to expose via restful. I
> suppressed the method from showing up in the Wicket viewer so I didn't try
> to call it with the Wicket viewer.
>
> Now restful throws an error (which is not very useful) when calling the
> method:
>
> org.apache.tomcat.util.http.parser.TokenMgrError: Lexical error at line 1, column 29. Encountered: ":" (58), after : ""
> org.apache.tomcat.util.http.parser.HttpParserTokenManager.getNextToken(HttpParserTokenManager.java:434)
> org.apache.tomcat.util.http.parser.HttpParser.jj_ntk(HttpParser.java:300)
> org.apache.tomcat.util.http.parser.HttpParser.MediaType(HttpParser.java:21)
>
>
> For some reason I now also exposed the action via Wicket. That way I get
> another exception with more useful information about my problem:
>
> javax.jdo.JDOUserExceptionInvalid operator "=". Did you mean to use
> "=="?
> org.datanucleus.api.jdo.NucleusJDOHelper#getJDOExceptionForNucleusException(NucleusJDOHelper.java:549)
> org.datanucleus.api.jdo.JDOQuery#execute(JDOQuery.java:299)
>
> nl.pocos.dom.workflow.WorkFlowStatusses#checkNumberOfPGSMLicences(WorkFlowStatusses.java:55)
>
> sun.reflect.NativeMethodAccessorImpl#invoke0(NativeMethodAccessorImpl.java:-2)
>
> sun.reflect.NativeMethodAccessorImpl#invoke(NativeMethodAccessorImpl.java:57)
>
> sun.reflect.DelegatingMethodAccessorImpl#invoke(DelegatingMethodAccessorImpl.java:43)
> java.lang.reflect.Method#invoke(Method.java:606)
>
> After fixing this error the restful call works fine. I had this behaviour
> before but couldn't reproduce it. It looks like the TokenMgrError is
> thrown when some exception occurs in an action called via restful and the
> real reason/exception can't be found in the logs.
>
> Is there some reason not to show the original exception?
>
> Met vriendelijke groet,
>
> Erik de Hair
>
> --
> Pocos bv
> Croy 9c - 5653 LC Eindhoven
> Telefoon: 088 0100 700 - Fax: 088 0100 799
> http://www.pocos.nl/ - http://www.sipo.nl/
> K.v.K. nummer: 17097024
> [image: Follow Pocos bv]
> <https://twitter.com/intent/follow?original_referer=https%3A%2F%2Ftwitter.com%2Fabout%2Fresources%2Fbuttons®ion=follow_link&screen_name=Pocosbv&source=followbutton&variant=2.0>
>
> Aanmelden van incidenten en/of changes graag via servicedesk@pocos.nl
>