-miss-period1/min-cache-miss-period
cache-load-factor0.75/cache-load-factor
/cache-policy-conf
/container-cache-conf
/container-configuration
/container-configurations
/jboss
From: Jon Swinth [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: Wed, 12 Mar 2003 15:32:50
We recently fixed our application configuration for read-only beans. We
have seen great increases in speed and a reduction in deadlocks. Now we have
the issue of read-only beans not updating from the DB after updates.
Eventually they drop off and reload, but it doesn't seem to happen in the
Ok, you say this is described in the for-pay docs. My subscription ran out so
I re-upped for another year for all docs. Mind pointing me in the right
direction? I heard someone say there was a whole chapter on this.
The 2.4.6 book doesn't seem to have anything on read-only. The 3.0.5 CMP
Does this mean that putting the following in the jbosscmp-jdbc.xml file
doesn't make the beans read-only any more?
entity
ejb-nameCarrierBeanRO/ejb-name
table-namecarrier/table-name
read-onlytrue/read-only
read-time-out3/read-time-out
/entity
On Sunday 02
-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]De la part de Jon Swinth
Envoyé : vendredi, 22 novembre 2002 18:56
À : [EMAIL PROTECTED]
Objet : [JBoss-user] Locking and Readonly Beans
We have been having some periodic issues with deadlock using
JBoss 3.0.3 and
CMP beans
We have been having some periodic issues with deadlock using JBoss 3.0.3 and
CMP beans. In looking at the conflicts, we found that much of the access to
the beans was just to read so we created readonly versions of the beans for
those functions. This was done by making duplicate entries in
Javier,
You should also be aware the unless bug 574130 has been fixed (which the
status says it hasn't), you will not be able to access a UserTransaction on a
different machine using properties in the InitialContext() constructor. This
is because ClientUserTransaction tries to lookup
I understand everyone is busy with 3.0.2, put has anybody run into my socket
problem? I am using JBoss 3.0.1 with the Blackdown 1.3.1 Java. I have a
session bean method that needs to open a socket connection. When I run the
code outside of JBoss (with Balckdown) it works fine. When I run
I am using Redhat, not Suse, so I don't have the issue of 127.0.0.2. But I
did try changing the hosts file so that the server name resolved to the
external IP address instead of the loopback address. This allowed me to
connect.
Doesn't this mean that JBoss would not be able to work on a
I'm trying to connect using the java.net.Socket class from within a Session
bean. It works outside of JBoss, but I get Connection Refused in Jboss.
Socket socket = new Socket(localhost,9000);
I'd check the forums but www.jboss.org is down for me.
Is there some security that I am not aware
What is the correct way to access, from one Jboss server, a bean that resides
on a different JBoss server? I have one session bean that needs to talk to
another session bean on a different server. I tried having the session bean
act as just a regular client, but it just errors. Here is the
Thanks for the guess, but as you will note, I am trying to access the other
server by IP address. The hosts file is not being used.
On Tuesday 27 August 2002 02:56 pm, [EMAIL PROTECTED]
wrote:
Date: Tue, 27 Aug 2002 17:26:20 -0300
From: =?ISO-8859-15?Q?Emerson_Cargnin_-_SICREDI_Servi=E7os?=
This is just a note for other users of PostgreSQL. With the latest version
of JBoss3.0.1 you can no longer be able to use a column definition of TIME in
Postgre. This is NOT a bug in JBoss, but rather a bug in jdbc driver for
PostgreSQL (even the latest dev driver). The JBoss3.0.1 changes
: Re: [JBoss-user] FYI on JBoss3.0.1 and PostgreSQL TIME
Reply-To: [EMAIL PROTECTED]
Jon Swinth wrote:
This is just a note for other users of PostgreSQL. With the latest
version of JBoss3.0.1 you can no longer be able to use a column
definition of TIME in Postgre. This is NOT a bug
I have a few custom finders (those implemented in the bean) that end up in a
single bean instance found rather than a Collection. This works fine except
that when I throw a FinderException because no row is found the exception
ends up in the log as an ERROR even though it is being caught by
Connecting from Tomcat without the -nonaming option looks like this:
Properties props = new Properties();
props.setProperty(Context.INITIAL_CONTEXT_FACTORY,org.jnp.interfaces.NamingContextFactory);
props.setProperty(Context.URL_PKG_PREFIXES, org.jnp.interfaces);
Hi all,
I have a CMP2 been in which I have created a helper method adjust the value
of a date column. Basically, I have a date column which is updated by the
client. The client then calls the helper method which makes sure the
selected date is not on a Sunday and checks other beans to make
.
-dain
Jon Swinth wrote:
Hi all,
I have a CMP2 been in which I have created a helper method adjust the
value of a date column. Basically, I have a date column which is updated
by the client. The client then calls the helper method which makes sure
the selected date is not on a Sunday
Simply remove/move $JBOSS_HOME/server/default/deploy/jetty-plugin.sar so that
Jetty will not start up. That will leave port 8080 available for Tomcat. Oh, and
don't just put the file in a subdirectory of /deploy, JBoss looks inside subdirectories
now at startup (it doesn't catch
Thanks Brian and Marc for the responses.
The credit card database is used for audit and for capture. When an order is placed,
the user must enter their credit card info and the system authorizes the charge right
then
while it still has the unencrypted cc number. The system then uses the
What is the best way to keep a object bound in memory for stateless session bean use?
Specifically, I have a java.security.Key that I need to make available to very
specific stateless session bean.
Since the key is the private RSA key for the credit card database, I do not want to
put it in
I had simular problems using Tomcat in a separate JVM. For me it turned out
that Tomcat security requires and java.* or javax.* to be in the Tomcat lib directory
rather than the web application lib directory.
From: Artur Jonak [EMAIL PROTECTED]
To: [EMAIL PROTECTED] [EMAIL PROTECTED]
Date:
You are most likely already doing this, but make sure you are using the interface to
call bar().
If you don't, JBoss can't catch the method call in order to create a new Transaction
and bar()
will be running in the same transaction as foo(). Like this from foo():
Thanks Guy, for the response. That is the way I used to do things. However,
there is code in org.jboss.tm.usertx.client.ClientUserTransaction that calls new
InitialContext()
when you are trying to use a transaction from Tomcat. If I don't use jndi.properties
then the
client transaction will
Thanks for the reply Dain.
Yes, I have set the row-locking element for JBossCMP. However, the problem
I have is that there will be a lot of access to the inventory rows that are just
checking to
see if there is still available and don't need a lock. I would also like it if those
reads did
Thanks Marc for the reply.
The issue with your solution is that the inventory checks are for different
users than the where we are updating inventory. Each time an item is
displayed on a page, the server checks inventory to see if it is still in
stock. This is required because the data keeps
First off, thanks to all of you that help out on this list. It is greatly appreciated.
Is there someone out there that has been successful at deploying JBoss 3.0.0 Final
on a different machine than Tomcat 4.0.3?
Everything works fine for us as long as JBoss and Tomcat are on the same machine.
Sorry for the length of this post, but it is a complicated issue.
The application we are working on is a shopping cart that reserves the inventory as
soon as it is put in the cart. This is due to the fact that there are scarce
quantities of
items and they come and go (rental business). In my
Hi Todd,
I have run into this same issue when trying to control transactions. Although this is
not what some would like
me to say, my experience is that Entity beans in JBoss only work properly with
Required. In fact, you are
better off not setting any container-transaction attributes for
Since nobody seems to have answered you. Here is what I use to connect standalone
Tomcat to Jboss.
There is more here than you asked for, but you get the idea.
private static final String contextFactory =
org.jnp.interfaces.NamingContextFactory ;
private static final String
Also, if anyone has any ideas about how to solve my problem with
incorrect SQL being generated for findAll(), please share them. If not, is
there some other mailing list I should try?
I am not sure why you are having the issue with the findAll() because I was
unable to view your config
Since downloading RC3, I have used the standard log4j.xml file unedited.
Today I decided to cut down on the amount of messages by uncommenting the following:
category name=org.jboss
priority value=INFO/
/category
Now JBoss silently crashes after the second page load of my application
Dirk,
If you are trying to access the Tomcat JNDI from an external program then you
are most likely out of luck since it doesn't look as if Tomcat is exposing it
via a port like JBoss does.
Tomcat 4 provides a JNDI InitialContext implementation instance to web
applications running under it
-
From: Jon Swinth [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, May 21, 2002 4:09 PM
Subject: [JBoss-user] RC3 breaks Tomcat 4.0.3 Standalone
I have been using JBoss and Tomcat 4.0.3 standalone for a number of
months
now. In order to connect from the servlet to JBoss I use
The solution to the problem was to place the JSSE jars in the
CATALINA_HOME/lib rather than the WEB_INF/lib directory. There was no log
entries in Tomcat that had any security errors or anything. I just guessed.
I don't understand why, but I can now use RC3.
Thanks again for the help.
Thanks Justin for sharing the pain. I thought I was alone.
I am very interested to see the source where you have duplicated this issue.
I would like you to also include your ejb-jar.xml sections. If I can find
the exact situation, I may be able to come up with a test case, a work
around,
Thanks, Justin, for the quick response. I had hoped that there would be
simularities between the two issues, but I don't see any other than the error
message. I am using PostGre on the same machine as JBoss. I have other code
that does something very simular to yours without issue. I guess
Well Justin, I have solved the issue, although I think this may qualify for a
bug. Basically, it boils down to returning null in a custom finder. I
couldn't find documentation on implementing a custom finder in which a single
record was returned instead of a Collection. The method signiture
I have been using JBoss and Tomcat 4.0.3 standalone for a number of months now. In
order to connect from the servlet to JBoss I use the following:
Properties props = new Properties();
props.setProperty(Context.INITIAL_CONTEXT_FACTORY,org.jnp.interfaces.NamingContextFactory);
, May 18, 2002, at 09:36 AM, Jon Swinth wrote:
System.setProperty(java.protocal.handler.pkgs,com.sun.net.ssl.internal
. www.protocal);
___
Hundreds of nodes, one monster rendering program.
Now that's a super model! Visit http
Thanks Scott for pointing me to the test case. I had looked in that directory but did
not find it because it is in the Attic (don't know why it would be there).
The test case does not add anything that I am not already doing except for setting the
trusted keystore. Is this something required
I am using JBoss3.0.0RC2 and have a complex process that creates new orders
as they are submitted from the web. On order submission, a credit card is
authorized via SSL. If the credit card is declined then the order is rolled
back, however the credit card information must stay because we
I am still looking for how to change the pool parameters. Can anybody point
me in the right direction?
On Friday 10 May 2002 10:09 am, Jon Swinth wrote:
Dan the answer man.
Your pool shouldn't be a problem (unless you have a lot of users all
trying to do this at the same time).
Umm
I have a few finders that bring back 100 - 500 beans. As the number of beans
returned climbs, there is a point (i.e. number of beans) where everything
slows down significantly. I get a notification in the log that says the pool
for my bean is overloaded and You should change pool parameters.
Dan the answer man.
Your pool shouldn't be a problem (unless you have a lot of users all
trying to do this at the same time).
Umm, yes, I may have a lot of users at one time. It happens when users try
and look at thier order history on the website. I have no control over how
many of them
Hi all,
I have had no luck figuring out how to change the log4j.xml file so that I
don't get DEBUG messages in the server.log anymore (or on the console for
that matter). Based on looking at the file, I shouldn't be getting DEBUG. I
am using the standard file from the sourceforge
Does anyone have an entity bean that has a method that
returns a Collection that performs well with ~200 elements
in the Collection? Reaching it through a session bean is
fine. If so, would you share the source? I'm beginning to
believe that no one actually has done this successfully.
Yes,
47 matches
Mail list logo
