I thought splitting my app between two machines should also give
me a significant performance even though the serialization overhead,
shouldn't it?
This was believed to be true early on in J2EE (1999-2000), but now most
vendors advise in-JVM web and EJB containers to minimize the
It's personal preference for me. I create another directory to keep the
standard JBoss deployed files separate from anything I deploy. If
separating system-level configurations from applications is a requirement,
you could also do it by role with multiple custom deploy directories. For
instance,
?
thanks.
.peter
-Original Message-From: Jason Westra
[mailto:[EMAIL PROTECTED]]Sent: Tuesday, November 05, 2002
12:14 AMTo: [EMAIL PROTECTED]Subject:
RE: [JBoss-user] User Monitoring
You make the custom solution sound way too hard! It is quite
easy
You
make the custom solution sound way too hard! It is quite
easy.
You
need 2 classes.
1
Class implementing HttpBindingListener called
MonitoredUser.java
1
MBean called CurrentUsersMBean.java, which holds a list of MonitoredUser objects
representing currently logged in users.
When
Hi JBoss friends,
I tend to agree with Bill and Dain's last posting here. There are certain
things that CMP is not designed to do *well* and large, heavy reads is one
of them.
I'd venture to guess the same performance problem will occur on other app
servers, in which case, it is not a war of
;lists.sourceforge.net]On Behalf Of Dain
Sundstrom
Sent: Tuesday, October 29, 2002 11:43 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] Entity Bean Performance Tuning Help
Jason Westra wrote:
Hi JBoss friends,
I tend to agree with Bill and Dain's last posting here. There are certain
things
Its much better this way,
because you can have multiple instances of JBoss running on the same
machine, each using a different port.
The old 8082 way only allowed one JBoss console to be accessed
per-machine.
You could always change the port for the JMXHtmlAdaptor, which allowed
multiple JBoss
/*.jar
files or are they required to be in the jboss/server/config/lib?
sorry for the questions, but i can't seem to find docs about this.
Ryan
-Original Message-
From: Jason Westra [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 10, 2002 6:09 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss
It works fine for me under a local Apache instance. Haven't tried it
remotely. It is really cool, but takes forever to boot since it copies the
jars thru http: rather than a nice local copy. My version is
jboss3.0.2-tomcat4.0.4 and there is no crimson.jar.
Jason
-Original Message-
Just set them in the System properties at startup of JBoss. Here are some
system properties I set in an Ant start task. They are self-explanatory, I
hope.
sysproperty key=jboss.server.temp.dir value=${dynamic} /
sysproperty key=jboss.server.data.dir value=${persist} /
Jason
-Original
Hi!
I want to keep all deployed apps in a single location on our network and
start up multiple (non-clustered) JBoss instances that deploy the apps from
HTTP URLs. I know this is *possible* with JBoss however...
1. Is it recommended?
If not, why?
If so, what are some gotchas to look out for,
via HTTP URLs
Warning, I haven't tried much of this, and may not be 100% accurate.
On 2002.09.27 12:01:57 -0400 Jason Westra wrote:
Hi!
I want to keep all deployed apps in a single location on our network and
start up multiple (non-clustered) JBoss instances that deploy the apps
from
HTTP
, the new app's URL should be added to the list in the config file,
since
changes to MBean attributes are not remembered.
Jason Westra wrote:
Here are the results of my findings for HTTP deployment using the supplied
URLDeploymentScanner and URLDirectoryScanner classes.
URLDeploymentScanner
Use a Scheduler MBean or the JMX Timer services on your own if you want the
cache autoflushed every so often. Just have it call the example code below.
Jason
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Randahl Fink
Isaksen
Sent: Tuesday, September
Saroj,
You could try configuring your container-transaction settings in
ejb-jar.xml to be Supports for your entity bean getters and finders.
This should keep locks from happening as well.
Jason
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Saroj
Hi!
We are porting an app from one app server to Jboss. The app starts its own
threads (actually subclasses of threads), and each maintains state during
the course of its lifetime (thus MDBs were not used since they are
essentially stateless).
Also, the thread does no synchronized method
16 matches
Mail list logo