[JBoss Cache] Document updated/added: "JBoss Cache Official Documentation"
by Manik Surtani
User development,
The document "JBoss Cache Official Documentation", was updated Feb 22, 2010
by Manik Surtani.
To view the document, visit:
http://community.jboss.org/docs/DOC-12843#cf
Document:
--------------------------------------------------------------
This is the official JBoss Cache documentation page.
> Since JBoss Cache is a key component of JBoss application server clustering and caching, you should review the http://www.jboss.org/jbossas/docs
> for details beyond the documentation outlined below, which is mostly
> intended for those interested in using JBoss Cache standalone or
> directly interacting with the JBoss Cache API from within an
> application deployed in JBoss AS.
Note that the current production release is *JBoss Cache 3.0.3.GA*, codenamed *+"Naga"+*.
In addition to the official documentation provided here, please refer to the http://community.jboss.org/docs/DOC-10242 for more information.
If you are looking for documentation on JBoss Cache Searchable Edition, please look at the http://community.jboss.org/docs/DOC-10286as well.
> Looking for the *JBoss Cache distribution* for download? Click http://community.jboss.org/docs/DOC-12844.
h3. JBoss Cache, Core Edition
|| Version || Users' Guide
|| FAQs
|| Tutorial
|| API Docs
||
| 3.2.1 +"Malagueta"+ | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... |
| 3.1.0 +"Cascabel"+ (Beta) | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... |
| 3.0.3 +"Naga"+ | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... |
| 2.2.2 +"Poblano"++
+ | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... |
| 2.1.1 +"Alegrias"+ | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... |
| 2.0.0 +"Habanero"+ | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... |
| 1.4.1 +"Cayenne"+ | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... |
| 1.4.0 +"Jalapeno"+ | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... |
h3. JBoss Cache, POJO Edition
|| Version || Users' Guide
|| FAQs
|| Tutorial
|| API Docs
||
| 3.0.0.GA +"Naga"+++ | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... |
| 2.2.1 +"Poblano"+++ | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... |
| 2.1.0 +"Alegrias"+ | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... |
| 2.0.0 +"Habanero"+ | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | +(see Core Cache+
+API Docs)+ |
| 1.4.1 +"Cayenne"+ | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | | | +(see Core Cache+
+API Docs)+ |
| 1.4.0 +"Jalapeno"+ | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs...
* http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... | | | +(see Core Cache+
+API Docs)+ |
h3. JBoss Cache, Searchable Edition
|| Version || Users' Guide
|| API Docs
||
| 1.0.0 | * http://community.jboss.org/docs/DOC-10286 (wiki) | * http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... |
--------------------------------------------------------------
16 years, 2 months
[Beginner's Corner] New message: "Re: How do I enable pass-by-reference for EJB3 in JBoss AS container?"
by Jerry Simone
User development,
A new message was posted in the thread "How do I enable pass-by-reference for EJB3 in JBoss AS container?":
http://community.jboss.org/message/527625#527625
Author : Jerry Simone
Profile : http://community.jboss.org/people/jlsimone
Message:
--------------------------------------------------------------
... Only slightly more information, not all that helpful.
I have not been completely sure about whether or not this really was a case of pass-by-reference vs. pass-by-value within the container. When I run my JBoss tests, I notice some strange behavior in the application as well as the NotSerializableException mentioned above. Well, by coincedence, someone was running our WebSphere-based version of the same application the other day and the WebSphere app was showing the same strange behavior and the same NotSerializableException for the same class. The solution in this case was to go to Admin console to the ORB Service configuration for the app and to turn on pass-by-reference (it had gotten turned off somehow). After restarting the app server, the WebSphere app started working normally again. Now I am thinking that this really is a problem with pass-by-value/reference in JBoss.
I have read that JBoss is supposed to, by default, use pass-by-reference for method calls between EJBs within the container. I looked at the org.jboss.invocation.InvokerInterceptor (I cannot remember what led me there) and I saw that it looks like it is trying to do the right thing with a local call. I am wondering what I might have done (or not done) to cause JBoss to not use pass-by-reference in this case. I am still looking for the solution. Please let me know if someone needs more information from me or examples of my code or configuration.
Thanks all.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/527625#527625
16 years, 2 months
[JBoss Microcontainer] New message: "Re: Classloaders & Domains: Some questions & a suggestion"
by Gilles Compienne
User development,
A new message was posted in the thread "Classloaders & Domains: Some questions & a suggestion":
http://community.jboss.org/message/527622#527622
Author : Gilles Compienne
Profile : http://community.jboss.org/people/gcompienne
Message:
--------------------------------------------------------------
Sorry for the delay in responding. As expected your code works but I finally found the difference with my tests:
If I move transl and Services into their own domain, i.e. by adding a domain attribute as the example below:
<Services>/jboss-classoading.xml:
<classloading xmlns="urn:jboss:classloading:1.0" domain="InfinispanCacheDomain">
<requirements>
<package name="com.alesj.spi"/>
</requirements>
</classloading>
<transl>/jboss-classloading.xml:
<classloading xmlns="urn:jboss:classloading:1.0" domain="InfinispanCacheDomain">
<capabilities>
<package name="com.alesj.spi"/>
</capabilities>
</classloading>
Then it does not work anymore and Services suddenly starts seeing the Dummy class, even though I didn't declare any dependencies onto it...
To me this is wrong, especially as I agree with you that, if I start declaring explicitely the <requirements> then I should not see anything else...
Or I am missing something else?
Thanks again for your help.
Gilles.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/527622#527622
16 years, 2 months
[JCA] New message: "Re: How to create a XA aware connection factory"
by Kreek Fred
User development,
A new message was posted in the thread "How to create a XA aware connection factory":
http://community.jboss.org/message/527605#527605
Author : Kreek Fred
Profile : http://community.jboss.org/people/fredk
Message:
--------------------------------------------------------------
After spitting through the jboss sourcecode I solved the problem myself:
the property 'URLProperty' refers to a named property in the config-property XADataSourceProperties
So one should use the following lines in the connection factory:
<config-property name="URLProperty" type="java.lang.String">$PROPNAME</config-property>
<config-property name="XADataSourceProperties" type="java.lang.String">$PROPNAME=$CONNECTIONSTRING</config-property>
where the both $PROPNAME's should be the same and the $CONNECTIONSTRING should be the connection string
e.g.
<config-property name="URLProperty" type="java.lang.String">URL</config-property>
<config-property name="XADataSourceProperties" type="java.lang.String">URL=jdbc:thin:@localhost:1521:XE</config-property>
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/527605#527605
16 years, 2 months
[JBoss Microcontainer Development] New message: "Re: CallbackItem.changeCallback() very expensive due to context tracking"
by Kabir Khan
User development,
A new message was posted in the thread "CallbackItem.changeCallback() very expensive due to context tracking":
http://community.jboss.org/message/527600#527600
Author : Kabir Khan
Profile : http://community.jboss.org/people/kabir.khan@jboss.com
Message:
--------------------------------------------------------------
> mailto:kabir.khan@jboss.com wrote:
>
>
> For B I don't really understand exactly why this is being done? It looks like we check for ContextTracker in each metadata level at INSTANCE level and above, up to JVM. Wouldn't that be handled by the call to metaData.getMetaData() in C anyway?I
Changing this to the following works, but maybe we aren't using context tracking in the kernel tests?
public ContextTracker getContextTracker()
{
if (tracker == null || tracker == NOOP)
{
synchronized (this)
{
// since we got through, we must be the same caller
if (tracker == NOOP)
return null;
// we waited, got through, but it's now changed
if (tracker != null && tracker != NOOP)
return tracker;
tracker = NOOP; // mark that we're initializing
ContextTracker ct = null;
MetaData metaData = scopeInfo.getMetaData();
if (metaData != null)
{
ct = metaData.getMetaData(ContextTracker.class);
// if (ct == null)
// {
// List<ScopeLevel> levels = CommonLevelsUtil.getSubLevels(DEFAULT_MINIMAL);
// int instanceIndex = levels.indexOf(CommonLevels.INSTANCE);
// for (int i = instanceIndex; i >= 0 && ct == null; i--)
// {
// MetaData md = metaData.getScopeMetaData(levels.get(i));
// if (md != null)
// ct = md.getMetaData(ContextTracker.class);
// }
// }
}
tracker = ct; // should we care if it's still null?
}
}
return tracker;
}
In turn about 60% of the time taken by calling ScopeKey.getScopeLevel(). If the above fix is not ok, I'll need to look at optimizing that.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/527600#527600
16 years, 2 months
[JBoss Microcontainer Development] New message: "CallbackItem.changeCallback() very expensive due to context tracking"
by Kabir Khan
User development,
A new message was posted in the thread "CallbackItem.changeCallback() very expensive due to context tracking":
http://community.jboss.org/message/527596#527596
Author : Kabir Khan
Profile : http://community.jboss.org/people/kabir.khan@jboss.com
Message:
--------------------------------------------------------------
I'm running a benchmark with 10 callbacks installed and 990 beans matching those callbacks, so I end up with 9,900 calls to SingleCallbackItem.changeCallback().
Relevant part of stacktrace along with number of calls and %cpu time taken
Thread [main] (Suspended)
(19,800 calls, 46.9% cpu) AbstractKernelControllerContext(AbstractControllerContext).getContextTracker() line: 389
(9,900 calls, 47.3% cpu) AbstractKernelControllerContext(AbstractControllerContext).getTarget(ControllerContext) line: 474
(9,900 calls, 47.6% cpu) ClassSingleCallbackItem(OwnerCallbackItem<T,C>).getTarget(ControllerContext, boolean) line: 68
ClassSingleCallbackItem(SingleCallbackItem<T>).changeCallback(ControllerContext, boolean) line: 62
ClassSingleCallbackItem(AbstractCallbackItem<T>).changeCallback(Controller, ControllerContext, boolean) line: 80
ClassSingleCallbackItem(OwnerCallbackItem<T,C>).changeCallback(Controller, ControllerContext, boolean) line: 116
What is really heavy inside ACC.getContextTracker() are:
A - 138,600 callls, 34% cpu
B - 19,800 calls 10.3% cpu
public ContextTracker getContextTracker()
{
if (tracker == null || tracker == NOOP)
{
synchronized (this)
{
// since we got through, we must be the same caller
if (tracker == NOOP)
return null;
// we waited, got through, but it's now changed
if (tracker != null && tracker != NOOP)
return tracker;
tracker = NOOP; // mark that we're initializing
ContextTracker ct = null;
MetaData metaData = scopeInfo.getMetaData(); //B
if (metaData != null)
{
ct = metaData.getMetaData(ContextTracker.class); //C
if (ct == null)
{
List<ScopeLevel> levels = CommonLevelsUtil.getSubLevels(DEFAULT_MINIMAL);
int instanceIndex = levels.indexOf(CommonLevels.INSTANCE);
for (int i = instanceIndex; i >= 0 && ct == null; i--)
{
MetaData md = metaData.getScopeMetaData(levels.get(i)); //A
if (md != null)
ct = md.getMetaData(ContextTracker.class);
}
}
}
tracker = ct; // should we care if it's still null?
}
}
return tracker;
}
For A, maybe scopeInfo could keep a reference to the MetaData to avoid having to access the repository every time we call scopeInfo.getMetaData()?
For B I don't really understand exactly why this is being done? It looks like we check for ContextTracker in each metadata level at INSTANCE level and above, up to JVM. Wouldn't that be handled by the call to metaData.getMetaData() in C anyway?
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/527596#527596
16 years, 2 months