Hi,
I've just started using JBossCache now recently so I'm still going through the teehing
pains with it...
We also use JBoss 3.2.3 and I managed to get it working, by recreating the
cluster-service as a cluster.sar and moving the jgroups.jar in the lib folder into the
sar. And then deploying
No, you are not hallucinating. :-) The JNDI exposure has been fixed in the latest
source. It was commented out because of the aop. In 3.2, there is no aop, so that will
be fine anyway.
-Ben
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3852369#3852369
Reply
The bind/unbind code has been uncommented recently. It will be in version 1.2 (already
in the CVS).
Wrt Sleepycat: we ship it but you don't need to use it if you don't want to. This is
all a config issue. Sleepycat is our current default because we like its simplicity
and power. lf you don't,
Hi Ben
Thanks for that - yes, that'll do nicely!
Incidently,just one more question - Bela said some time back that the cache code would
be refactored and one of the new features would be the ability to use other transports
over jgroups. Is this still the case?
Thanks
Nick
View the original
Hi Ben
Thanks for that - yes, that'll do nicely!
Incidently,just one more question - Bela said some time back that the cache code would
be refactored and one of the new features would be the ability to use other transports
over jgroups. Is this still the case?
Thanks
Nick
View the original
Hi Bela
I've just discovered that with 1.1 you have bundled sleepycats java db. Thi s is a
little awkward for us as sleepycats license conflicts with jboss' lgpl.
is there any chance you could find/use a db that is consistent with lgpl?
Thanks
Nick
View the original post :
In 1.2 release (scheduled sometime in November), we plan to ship a cache loader that
uses JDBC. That may be what you need.
-Ben
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3851788#3851788
Reply to the post :
Arbitrary refers to the demand to patch x in timeframe y. I'm currently working on
finalizing the 3.2.6 release which includes the pooling fix along with others and do
not have the time for arbitrary time demands from non-support customers. If a support
customer needs the feature now they will
How quickly this thread turned into a push for services.
I thank Joe for explaining his problems with the product. A working JDBC connection
pool and cache are basic functionality in an application server.
I've heard and read so many good things about JBoss and have been monitoring the
boards
You must know it takes a lot of effort to deliver a patch. And that is the resources
many times that we can't afford unless it is critical (wtiness 3.2.4 to 3.2.5).
I don't think we are pushing services at all cost. But services is our bread and
butter. Product is free. Like Bela mentioned, we
Hi Bela,
Thanks for the response. What I would like to see is higher priority on released
versions of jboss. The current release is 3.2.5 but it seems virtually abandoned.
There is currently a major bug in the jboss jdbc connection pool. The fix is only
available in the 3.2.6 cvs tree. The
darthjoe wrote : Hi Bela,
|
| Thanks for the response. What I would like to see is higher priority on released
versions of jboss. The current release is 3.2.5 but it seems virtually abandoned.
|
| There is currently a major bug in the jboss jdbc connection pool. The fix is only
anonymous wrote :
| Thanks for the response. What I would like to see is higher priority on released
versions of jboss. The current release is 3.2.5 but it seems virtually abandoned.
|
| There is currently a major bug in the jboss jdbc connection pool. The fix is only
available in the
I develop software for a medium sized ecommerce site.
We are currently running jboss 3.2.3 with treecache 1.01 and hybernate 2.1
Treecache is in local mode with jboss invalidation bridge for cache invalidation
Our experiences with treecache have not been great so far.
The first problem occurred
Hi Joe,
we are listening and take your suggestions and comments seriously.
I think the biggest problem for you was patch/release management. When we release, we
strive to provide releases for JBoss head, the 4.x and the 3.2.x branch. We don't
backport to older (released versions), as this
it's been 50 days since launch, and so far no memory leaks or whatsoever. good
product!
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3850681#3850681
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3850681
I cannot go into many details but we just started to use jbosscache with hibernate.
If all goes well we will be going live in 2 weeks.
Is there anything anybody can tell me to watch for using this as hibernate's 2nd tier
cache?
In particular,
- anything I need to know to get the query cache
17 matches
Mail list logo
