On 14.12.2006, at 18:52, Chuck Hill wrote:
Wow. That is about all I can come up with. I think I would just
go find some nice beer and try to not think about it.
That's probably the best I can do with my currently completely
limited view of such crazy stuff.
Cheers,
cug
Wow. That is about all I can come up with. I think I would just go
find some nice beer and try to not think about it.
Chuck
On Dec 14, 2006, at 8:31 AM, Guido Neitzer wrote:
On 14.12.2006, at 17:05, Guido Neitzer wrote:
I have now removed two arguments from the additional parameters
f
On 14.12.2006, at 17:05, Guido Neitzer wrote:
I have now removed two arguments from the additional parameters for
this app:
-Xms256m -Xmx384m
And now it seems to work perfectly on all four instances. Scary.
This is now completely crazy for me:
-Xms384m -Xmx384m --> works
-Xms128m -Xmx384m
On 14.12.2006, at 16:19, Guido Neitzer wrote:
I guess there is something totally broken in the settings for this
particular application - I have no deep deployment knowledge - some
hints where I could look for broken things?
I have now removed two arguments from the additional parameters fo
On 14.12.2006, at 15:06, Anjo Krank wrote:
What happens when you don't set a "key" binding is that WO stores
the image in the resource manager under it's own key and removes it
when it is accessed. You could try to log the incoming requests and
see if there are two for one such url...
In
What happens when you don't set a "key" binding is that WO stores the
image in the resource manager under it's own key and removes it when
it is accessed. You could try to log the incoming requests and see if
there are two for one such url...
Cheers, Anjo
Am 14.12.2006 um 15:09 schrieb Gui
On 14.12.2006, at 13:43, Guido Neitzer wrote:
Perhaps this wasn't clear enough:
The same image is displayed properly in one instance and not in the
other instance. Its the same database entry, the same image, the
same page, just a different instance of our DirectAcion application.
Okay. I
On 14.12.2006, at 13:16, Patrick Middleton wrote:
So go looking at all your images, the good and the bad, and see how
long the data for each is in the database.
Perhaps this wasn't clear enough:
The same image is displayed properly in one instance and not in the
other instance. Its the sam
On 14 Dec 2006, at 11:32, Guido Neitzer wrote:
Hi.
We have an application on one of our servers, that behaves very
strange.
Some instances don't load certain images from the database, other
instances do. I have compared the start parameters for the
instances and they are completely the
Hi.
We have an application on one of our servers, that behaves very strange.
Some instances don't load certain images from the database, other
instances do. I have compared the start parameters for the instances
and they are completely the same. They connect to the same database
(on a seco
10 matches
Mail list logo
