[JBoss-user] Re: Deadlocks
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 book only has a listing for the jbosscmp-jdbc.xml file. I currently don't use a jboss.xml file (only ejb-jar.xml and jbosscmp-jdbc.xml), but I am happy to add it to get my read-only beans to stop locking. I see the reference for read-only in the DTD, but I was advised that the docs had info on this. I don't mind paying for the docs because I like to have them anyway, but if you are advising them to understand what is required for read-only then where is that part of the documentation hidding? From: Bill Burke [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] Re: Deadlocks Date: Mon, 3 Mar 2003 15:15:03 -0500 Reply-To: [EMAIL PROTECTED] two different things. read-only for CMP means that updates will never happen. read-only in jboss.xml is a container thing. You can either mark the entire bean read-only, which means that the bean will never do any transactional locking, or you can do it per method. See the JBoss for-pay docs for more details. Bill --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] Re: Deadlocks
its in the admin book. There's a chapter on entity bean locking that I wrote. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Jon Swinth Sent: Tuesday, March 04, 2003 5:28 PM To: [EMAIL PROTECTED] Subject: [JBoss-user] Re: Deadlocks 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 book only has a listing for the jbosscmp-jdbc.xml file. I currently don't use a jboss.xml file (only ejb-jar.xml and jbosscmp-jdbc.xml), but I am happy to add it to get my read-only beans to stop locking. I see the reference for read-only in the DTD, but I was advised that the docs had info on this. I don't mind paying for the docs because I like to have them anyway, but if you are advising them to understand what is required for read-only then where is that part of the documentation hidding? From: Bill Burke [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] Re: Deadlocks Date: Mon, 3 Mar 2003 15:15:03 -0500 Reply-To: [EMAIL PROTECTED] two different things. read-only for CMP means that updates will never happen. read-only in jboss.xml is a container thing. You can either mark the entire bean read-only, which means that the bean will never do any transactional locking, or you can do it per method. See the JBoss for-pay docs for more details. Bill --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Re: Deadlocks
Start with the Read-Only Beans section on page 208 Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: Jon Swinth [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, March 04, 2003 2:27 PM Subject: [JBoss-user] Re: Deadlocks 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 book only has a listing for the jbosscmp-jdbc.xml file. I currently don't use a jboss.xml file (only ejb-jar.xml and jbosscmp-jdbc.xml), but I am happy to add it to get my read-only beans to stop locking. I see the reference for read-only in the DTD, but I was advised that the docs had info on this. I don't mind paying for the docs because I like to have them anyway, but if you are advising them to understand what is required for read-only then where is that part of the documentation hidding? --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Re: Deadlocks
Chapter 5? From: Jon Swinth [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Date: Tue, 4 Mar 2003 14:27:55 -0800 To: [EMAIL PROTECTED] Subject: [JBoss-user] Re: Deadlocks I see the reference for read-only in the DTD, but I was advised that the docs had info on this. I don't mind paying for the docs because I like to have them anyway, but if you are advising them to understand what is required for read-only then where is that part of the documentation hidding? --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] Re: Deadlocks
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 March 2003 06:35 pm, [EMAIL PROTECTED]
wrote:
From: Mauricio Hiroshi Nagaoka [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] Deadlocks
Date: Sun, 2 Mar 2003 19:00:12 -0300
Reply-To: [EMAIL PROTECTED]
Hi!
I didn't find any way do detect deadlocks on JBoss but you can change your
jboss.xml to tell JBoss which methods do not need an EJB lock.
In each entity entry in jboss.xml file, do the following change (in this
example, get* methods are read-only):
entity
ejb-nameRole/ejb-name
local-jndi-nameejb/webflow/local/Role/local-jndi-name
!-- this tells JBoss that the get* methods are read-only --
method-attributes
method
method-nameget*/method-name
read-onlytrue/read-only
/method
/method-attributes
/entity
I didn't find any XDoclet @tag to do this but I coded a XSLT transform:
?xml version=1.0 encoding=UTF-8?
xsl:stylesheet version=1.0
xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
xsl:output method=xml version=1.0 encoding=UTF-8 indent=yes/
xsl:template match=@*|node()
xsl:copy
xsl:apply-templates select=@*|node()/
/xsl:copy
/xsl:template
xsl:template match=entity
xsl:copy
xsl:apply-templates/
method-attributes
method
method-nameget*/method-name
read-onlytrue/read-only
/method
/method-attributes
/xsl:copy
/xsl:template
/xsl:stylesheet
If you are using ant to build your project do something like this:
xslt in=${original.jboss.xml} out=${modified.jboss.xml}
style=${location.of.xslt.above}
outputproperty name=method value=xml/
outputproperty name=standalone value=yes/
outputproperty name=encoding value=iso8859_1/
outputproperty name=indent value=yes/
xmlcatalog
dtd publicId=-//JBoss//DTD JBOSS 3.0//EN
location=${location.of.jboss.xml.dtd}/
/xmlcatalog
/xslt
The xmlcatalog tag above is optional. It's included here just to avoid a
remote connection for the xml validation.
I hope this helps.
Greetings from Brazil!
Mauricio
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] Re: Deadlocks
two different things.
read-only for CMP means that updates will never happen.
read-only in jboss.xml is a container thing. You can either mark the entire
bean read-only, which means that the bean will never do any transactional
locking, or you can do it per method. See the JBoss for-pay docs for more
details.
Bill
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Jon Swinth
Sent: Monday, March 03, 2003 1:14 PM
To: [EMAIL PROTECTED]
Subject: [JBoss-user] Re: Deadlocks
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 March 2003 06:35 pm,
[EMAIL PROTECTED]
wrote:
From: Mauricio Hiroshi Nagaoka [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] Deadlocks
Date: Sun, 2 Mar 2003 19:00:12 -0300
Reply-To: [EMAIL PROTECTED]
Hi!
I didn't find any way do detect deadlocks on JBoss but you can
change your
jboss.xml to tell JBoss which methods do not need an EJB lock.
In each entity entry in jboss.xml file, do the following
change (in this
example, get* methods are read-only):
entity
ejb-nameRole/ejb-name
local-jndi-nameejb/webflow/local/Role/local-jndi-name
!-- this tells JBoss that the get* methods are read-only --
method-attributes
method
method-nameget*/method-name
read-onlytrue/read-only
/method
/method-attributes
/entity
I didn't find any XDoclet @tag to do this but I coded a XSLT transform:
?xml version=1.0 encoding=UTF-8?
xsl:stylesheet version=1.0
xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
xsl:output method=xml version=1.0 encoding=UTF-8 indent=yes/
xsl:template match=@*|node()
xsl:copy
xsl:apply-templates select=@*|node()/
/xsl:copy
/xsl:template
xsl:template match=entity
xsl:copy
xsl:apply-templates/
method-attributes
method
method-nameget*/method-name
read-onlytrue/read-only
/method
/method-attributes
/xsl:copy
/xsl:template
/xsl:stylesheet
If you are using ant to build your project do something like this:
xslt in=${original.jboss.xml} out=${modified.jboss.xml}
style=${location.of.xslt.above}
outputproperty name=method value=xml/
outputproperty name=standalone value=yes/
outputproperty name=encoding value=iso8859_1/
outputproperty name=indent value=yes/
xmlcatalog
dtd publicId=-//JBoss//DTD JBOSS 3.0//EN
location=${location.of.jboss.xml.dtd}/
/xmlcatalog
/xslt
The xmlcatalog tag above is optional. It's included here just
to avoid a
remote connection for the xml validation.
I hope this helps.
Greetings from Brazil!
Mauricio
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
