Option #1 you manage to get it successfully running in one box but failed
when deploying to second one.
Option #2 you haven't managed to get it working on both box
What possibilities that I can think of:
You seemed to have a cluttered path and libraries set forth by the user or
environment configu
On 2/1/2014 1:49 PM, Konstantin Kolinko wrote:
2014-02-01 Jerry Malcolm <2ndgenfi...@gmail.com>:
Well I turned on Firebug. This is what it gives me. Doesn't look
like there is much useful info in here. If there's something specific
you are looking for that's not here, I can do more tracing...
2014-02-01 Jerry Malcolm <2ndgenfi...@gmail.com>:
> Well I turned on Firebug. This is what it gives me. Doesn't look
> like there is much useful info in here. If there's something specific
> you are looking for that's not here, I can do more tracing.
>
> This is the "response" tab conten
On 1/31/2014 7:01 PM, Jerry Malcolm wrote:
Well I turned on Firebug. This is what it gives me. Doesn't look
like there is much useful info in here. If there's something specific
you are looking for that's not here, I can do more tracing.
This is the "response" tab content:
POST stop?
The usual comes to mind:
Are you at the same PTF and CUME levels between the two boxes?
Do you have the same Java licensed programs installed on both boxes?
It the default JVM set the same on both boxes?
Those things are what usually come back to haunt me when I deploy on IBM i
Pete Helgren
www
On Jan 31, 2014 7:36 PM, "Mark Thomas" wrote:
>
> On 31/01/2014 11:52, Yann Simon wrote:
> > On Jan 31, 2014 10:25 AM, "Mark Thomas" wrote:
> >>
> >> On 31/01/2014 07:58, Yann Simon wrote:
> >> On Jan 30, 2014, at 11:18 AM, Yann Simon
> >>
> >>> Jetty seems to allow this. Why not tomcat? Is
