On Jun 21, 2011, at 2:23 AM, Mattias Jiderhamn wrote:
> I'm so glad you posted this Jeff, since the same thing happened to us
> yesterday. I still don't know how, but finally we realized that somehow
> the same JSP page was compiled both as case sensitive and all lower case
> (_myJsp__jsp.java
I'm so glad you posted this Jeff, since the same thing happened to us
yesterday. I still don't know how, but finally we realized that somehow
the same JSP page was compiled both as case sensitive and all lower case
(_myJsp__jsp.java and _myjsp__jsp.java).
What really threw us off though, was th
On 06/08/2011 12:43 AM, Jeff Schnitzer wrote:
> Dunno, I create it with ant just like every other warfile I've ever
> made... but now that you mention it, when I examine the jar it appears
> to have two copies of every classfile. Didn't notice that before!
>
> And thus the mystery is solved. Wow,
Dunno, I create it with ant just like every other warfile I've ever
made... but now that you mention it, when I examine the jar it appears
to have two copies of every classfile. Didn't notice that before!
And thus the mystery is solved. Wow, this one drove me nuts.
At one point I was running th
Jeff, is it possible that there is something strange about the WAR file
itself, like the compression...?
May I ask how the WAR is created?
Have you compared checksums between where it is created and where it is
deployed so it isn't messed up in some transfer?
Jeff Schnitzer wrote (2011-06-07 0
t; something about my WARfile. But there's nothing about my WAR that is
>>> special - it deploys just fine on other containers. If I unjar it by
>>> hand, it deploys just fine on Resin.
>>>
>>> Jeff
>>>
>>> On Sun, Jun 5, 2011 at 11:18
>>> What does the /resin-admin for that webapp show?
>>>
>>> If you've deployed the war using the deploy command, for example, it will
>>> take precedence over a new deployed .war.
>>>
>>> -- Scott
>>>
>>>
>>> --- On
.com wrote:
>> What does the /resin-admin for that webapp show?
>>
>> If you've deployed the war using the deploy command, for example, it will
>> take precedence over a new deployed .war.
>>
>> -- Scott
>>
>>
>> --- On Sun, 6/5/11, Jef
deployed the war using the deploy command, for example, it will
>> take precedence over a new deployed .war.
>>
>> -- Scott
>>
>>
>> --- On Sun, 6/5/11, Jeff Schnitzer wrote:
>>
>>> From: Jeff Schnitzer
>>> Subject: Re: [Resin-interest] Res
ed .war.
>
> -- Scott
>
>
> --- On Sun, 6/5/11, Jeff Schnitzer wrote:
>
>> From: Jeff Schnitzer
>> Subject: Re: [Resin-interest] Resin no longer deploys my war
>> To: "General Discussion for the Resin application server"
>>
>> Date: Sunday, Ju
What does the /resin-admin for that webapp show?
If you've deployed the war using the deploy command, for example, it will take
precedence over a new deployed .war.
-- Scott
--- On Sun, 6/5/11, Jeff Schnitzer wrote:
> From: Jeff Schnitzer
> Subject: Re: [Resin-interest] Resi
I finally got around to trying this out, and no luck. I can't for the
life of me figure out why Resin refuses to unpack my WAR. Every other
appserver will, including an old copy of resin 4.0.9 I found lying
around (unfortunately 4.0.9 has other issues).
Jeff
On Fri, Jun 3, 2011 at 9:57 AM, Jeff
Thanks - I will try this out.
I gave up and switched to Tomcat. But I like it less than Resin, so
maybe I will switch back.
Jeff
On Fri, Jun 3, 2011 at 9:43 AM, Keith Fetterman
wrote:
> Hi Jeff,
>
> Are you still experiencing this problem? I experienced the same problem
> in resin 4.0.16 pro.
Hi Jeff,
Are you still experiencing this problem? I experienced the same problem
in resin 4.0.16 pro. I pulled my hair out including performing the
steps you talked about in your email. I finally discovered that I had to
turn versioning off. Here is a snippet from my resin.xml file:
>
>
>
On Tue, May 24, 2011 at 2:04 PM, Scott Ferguson wrote:
>
> Also, what does the /resin-admin webapps tab say?
It reports a webapp at /, but just the "stock" one.
> For example, if you've deployed a .war using the command-line "deploy",
> that overrides the webapps/ directory.
I haven't done anyt
On 05/24/2011 01:50 PM, Jeff Schnitzer wrote:
> On Tue, May 24, 2011 at 8:11 AM, Paul Cowan wrote:
>> Hi Jeff,
>> We fixed a few bugs related to deployment in 4.0.17 and 4.0.18, perhaps the
>> behavior you're expecting has changed.
>> I tested by simply overwriting ROOT.war with a different ROOT.w
On Tue, May 24, 2011 at 8:11 AM, Paul Cowan wrote:
>
> Hi Jeff,
> We fixed a few bugs related to deployment in 4.0.17 and 4.0.18, perhaps the
> behavior you're expecting has changed.
> I tested by simply overwriting ROOT.war with a different ROOT.war and didn't
> have any issues.
> Resin will recr
On May 24, 2011, at 4:52 AM, Jeff Schnitzer wrote:
> I tried upgrading to 4.0.18 recently and deployment seems broken.
>
> Normally I copy my war file over webapps/ROOT.war, restart appserver,
> and it works.
>
> Now it seems the only way I can get a deployment working is by:
>
> 1) Deleting w
On May 24, 2011, at 4:52 AM, Jeff Schnitzer wrote:
> I tried upgrading to 4.0.18 recently and deployment seems broken.
>
> Normally I copy my war file over webapps/ROOT.war, restart appserver,
> and it works.
>
> Now it seems the only way I can get a deployment working is by:
>
> 1) Deleting w
Just do double check, you are running both the watchdog process and the
actual Resin instance as root?
Anything on the finest logging level?
- Original Message -
Subject: Re: [Resin-interest] Resin no longer deploys my war
Date: Tue, 24 May 2011 02:26:44 -0700
From: Jeff Schnitzer
It does sound like that, but I'm running Resin as root.
Jeff
On Tue, May 24, 2011 at 1:56 AM, Mattias Jiderhamn
wrote:
> Sounds like a file permission issue, but you've checked that, haven't
> you...?
>
>
>
> - Original Message -
> Subject: [Resin-
Sounds like a file permission issue, but you've checked that, haven't
you...?
- Original Message -
Subject: [Resin-interest] Resin no longer deploys my war
Date: Tue, 24 May 2011 01:52:04 -0700
From: Jeff Schnitzer
I tried upgrading to 4.0.18 recently and deployment se
I tried upgrading to 4.0.18 recently and deployment seems broken.
Normally I copy my war file over webapps/ROOT.war, restart appserver,
and it works.
Now it seems the only way I can get a deployment working is by:
1) Deleting webapps/ROOT (the directory)
2) Manually un-jaring ROOT.war
3) Deletin
23 matches
Mail list logo
