Almost certainly your problem is a config issue or a misunderstanding of how
clustering or MDBs work. If you have a support contract someone can take you
through it.
If you're looking for free support, there have been plenty of threads on this
forum on how to configure MDBs with clustered
If you have a support contract you should be using EAP 4.3 cp01, which already
has JBM 1.4.0.SP3_CP02 built in.
The community versions are not supported.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4164931#4164931
Reply to the post :
There's an FAQ on this.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4164727#4164727
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4164727
___
jboss-user mailing list
Persistent messages never get lost, non persistent messages may get lost
(that's why they're called non persistent ;) )
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4164729#4164729
Reply to the post :
bfach wrote : It turns out that this was a classpath issue. The remoting jar
for SP3 was not included but rather an older version. You need to have the
2.2.2.SP4 remoting jar included or failover will not work for the jms client.
Glad to hear it is working :)
Just to clarify - are you saying
bfach wrote : I did not see it in the users guide
http://www.jboss.org/file-access/default/members/jbossmessaging/freezone/docs/userguide-1.4.0.SP3/html/installation.html#install.extra-steps
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4164772#4164772
Reply
For a start, JBM 1.4.1 is for *JBoss AS 5 only*, I've no idea if it would work
with JBoss AS 4.x.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4164912#4164912
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4164912
JBM will only insert one row in the JBM_MSG_REF table per message for a simple
JMS queue.
Have you looked in the database to see how many rows are there?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4163832#4163832
Reply to the post :
You need to be using the JMS JCA resource adapter (at java:/JmsXA) see wiki for
more info.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4163922#4163922
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4163922
Have you tried a later version of remoting - e.g. 2.2.2.SP8?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4163934#4163934
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4163934
greeneagle- Please search through the old posts on this forum. This question
has been asked (and answered) many times.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4163476#4163476
Reply to the post :
Please always mention the version you are using, or it will be very difficult
for anyone to help you.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4163572#4163572
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4163572
Probably you are sending that message to a topic which has 20 durable
subscriptions.
With a topic the message gets persisted once, then a reference to the message
is persisted in each durable sub.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4163577#4163577
Please use the ejb forum for ejb questions.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4163204#4163204
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4163204
___
jboss-user
http://jira.jboss.org/jira/browse/JBMESSAGING-1396
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4163208#4163208
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4163208
___
Hi mmastrac-
Thanks for your interest in JBM 2.0 :)
We're very excited about it - it's going to form a key part of JBoss flagship
products and we're confident it will take the market by storm.
JBM 2.0 alpha is fully functional, it may well work for you, however it is an
alpha and we wouldn't
I still don't really understand what doc you are looking for.
The user guide explains clustered connection factories, load balancing policies
etc. I'm sure it could be improved but I don't think the information is missing.
View the original post :
This looks like a bug to me. I can see in the code that the max size check is
not being made when the transaction commits.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4163115#4163115
Reply to the post :
I think all this information is in the user guide, or has been answered several
times already in different threads on this forum (have a search), but here goes
again:
mbreuer wrote : How to deploy a clustered queue to jboss as? Which attributes
must be set in a clustered environment,which in a
mbreuer wrote :
| The app server 4.2.2 docs don't describe how jms works with new messaging.
Even there's a note, that future revision will use new jboss messaging. Also it
notes that messaging will work completely different from jbossmq.
|
What do you expect ?
JBoss AS 4.2.2 contains
mbreuer wrote :
| You are right, jbossas 4.2.2 comes with jbossmq, so it does not reference
jboss messaging. But newer manuals (5.0.0 beta) have no changes to the
clustering section, it also adresses jbossmq.
|
JBoss 5 is still a beta.
If you used EAP 4.3 you would find the documentation
There have been various memory and thread leaks in remoting that have been
fixed e.g. http://jira.jboss.org/jira/browse/JBREM-721 . I would suggest
looking in JIRA and trying out a later remoting version e.g. 2.2.2.sp8 -
remember to replace it on both the client and server side.
View the
milkyboss wrote :
| where is the problem?
| thank you for the responses...Hello
Unfortunately my crystal ball is currently out of action so I can't help you
out here.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4162943#4162943
Reply to the post :
Bear in mind, that you'll get much lower performance if you use the HTTP
transport, and we don't recommend it if you want stability.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4160817#4160817
Reply to the post :
Great. Can you create a JIRA feature request and attach it?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4160830#4160830
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4160830
___
Yes, bfach is right, you must *always* change both ports and addresses.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4160832#4160832
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4160832
JBM 1.x will use something like 2 threads per session (I would have to check to
be sure), so if you create a lot of sessions, you'll have a lot of threads. On
later Linux kernels - this is rarely an issue - they can support very large
numbers of lightweight threads.
If you're clients are
ykonrad - what Linux version are you using? (I'm assuming you're running linux)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4160929#4160929
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4160929
The user guide install section explains exactly what jars you need, where to
get them from, and which order they should appear on the classpath.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4160960#4160960
Reply to the post :
The startup time depends entirely on three variables
a) The number of messages in the queues
b) The average size of the messages
c) The database you are using.
Compare this to JBM 2.0 which doesn't by default use a relational database -
startup time is very quick.
View the original post :
There is a simple solution here:
Don't use windows ;)
*** ducks
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4160295#4160295
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4160295
All new work is being carried out on JBM 2 which has a super fast journal,
we'll also support JDBC but we don't recommend it for high performance.
For in memory only, you can also configure a null persistence manager so we
don't really see any need to look at any in memory databases such as
Glad to hear you are looking at JBM 2.0.
A couple of thoughts:
1) I'd strongly recommend against running all tests on the same box. You'll
probably find the results won't give you a real picture of performance since
you really need a network in play (minimum 1GB network).
2) For JBM 1.4 - are
Have you tried Stomp? - we have some users already using this to connect using
C++.
http://stomp.codehaus.org/
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4159718#4159718
Reply to the post :
[EMAIL PROTECTED] wrote : Recently I met
http://jira.jboss.org/jira/browse/JBMESSAGING-1235 - it is not possible to
deploy a queue, undeploy it and deploy it with different clustered attribute.
The workaround says remove the row from JBM_POSTOFFICE table.
|
| Why is not the row deleted
Do the clustering and failover examples in the distro work for you?
Have you tried 1.4.0.SP3_CP02?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4159473#4159473
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4159473
Hmm something fishy here, you say you have started instance 2, which according
to what you said in your post should have a server peer id of 1, but the
console output you posted says:
| 12:26:36,434 INFO [ServerPeer] JBoss Messaging 1.4.0.SP3-CP02 server [0]
started
|
Which tells me it
bfach wrote : Tim,
|
| Thanks for the fast reply. I have tried them before but just to make sure,
could you point me to them so I can verify that I am following the examples
correctly.
|
| Thanks for the help,
Take a look at the installation section in the userguide. It goes on to
By default, failover will *not* occur if you shut down a node cleanly (see FAQ
on wiki).
If you want it to occur in this situation set this property to true.
There's a JIRA about this against the 1.4.0.SP3_CP02 release with info and
links to discussions on the subject.
View the original post
You need to drop your old tables too.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4159608#4159608
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4159608
___
jboss-user mailing
Can you validate your installation by running the examples as per the user
guide?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4159619#4159619
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4159619
That's strange. The example should certainly work when you use the mysql config
(does for me).
This strongly implies either a) wrong config is being used b) for some reason
tables haven't been created properly.
I would check your config and make sure it is from the right place.
View the
Sounds like your selector is just wrong, where are you setting
JMSType=java.lang.String?
Please post a simple java example demonstrating the problem (both sender and
receiver).
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4159635#4159635
Reply to the post :
Why don't you just let JBM create the tables?
If you're manually creating the tables then that's scope for human error. If
you expect me to manually go through what you posted and diff it to the correct
version at 7pm on a Friday night, you've got another thing coming ;)
Also you didn't say
jboss remoting jar and messaging client jar should really be the first items on
the classpath, as explained in the user guide.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4159640#4159640
Reply to the post :
I can't really tell why you get performance without looking at your setup.
Take a look at these though - you can reproduce them too.
http://www.jboss.org/file-access/default/members/jbossmessaging/freezone/docs/userguide-2.0.0.alpha1/html/performance.html#performance.results
View the original
Hi-
I have an object MessagingServer which is instantiate by the MC and declared in
our jbm-beans.xml file.
This object has an attribute MessagingServerManagement which is itself an
interface that provides the management interface of the messaging server.
That interface contains a set of
alesj wrote : Create a simple wrapper/delegate around MsgServerMgmnt
interface, where all invocations delegate the work to
MsgServer::getMsgServerMgmnt attribute.
| And then simply do @JMX as you already know.
| ;-)
Yeah, I thought of this, but it seems pretty ugly. Would be nice if MC
Two obvious things:
1) Database is not colocated with server
2) 100Mb network is *slow* - remember you have all your database traffic going
over that too. I would recommend a 1GB network and that's just for the
client-server traffic (not db traffic)
3) The old perf framework is deprecated - we
ebenezerlovelin wrote : Hi Tim,
|
| I was unable to find the download for 1.4.0.SP3_CP02 and that is why I
thought it 1.4.0.SP3 and 1.4.0.SP3_CP02 were the same.
|
CP stands for cumulative patch.
CP binary releases are available to our paying support customers who get them
first,
gary.c.chen wrote : As you said, Database that persistent manager processes
is bottleneck.
|
Actually I said the *network* would be a bottleneck, but yes the database would
probably be a bottleneck too.
anonymous wrote :
| Is there any method can improve performance of the traffic
gary.c.chen wrote : Another question :
| How can I turn off the persistent while sending and receiving messages ?
That means all the messages sended to the queues are just store in memory.
regardless PERSISTENT message or NON_PERSISTENT message.
There has been a recent thread on this very
After installing, please run the examples as explained in the user guide.
If they don't all run successfully that means your installation was botched.
In which case you would need to re-install.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4159353#4159353
If you look at the JIRA it says fix version 1.4.0.SP3_CP02.
That means, you won't have it in 1.4.0.SP3 since 1.4.0.SP3 comes before
1.4.0.SP3_CP02
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4159057#4159057
Reply to the post :
Pretty much all the info you have asked for is available on the wiki. Please
have a look.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4159058#4159058
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4159058
All this info is on the wiki
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4159059#4159059
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4159059
___
jboss-user mailing list
I think you're misunderstanding how clustering works.
Let me give an overview again. This has also been covered on (many) other
threads
If you use a connection factory with load balancing = true to *create* a
connection to the cluster then subsequent create connection attempts will
connect to
ejb3workshop wrote :
| Our problem is that one incoming message results in several (sometimes 100
/ 1000) individual messages to be send to the other MDBs in the chain. So one
message comes in, and many go to the next MDB. The current behavior we are
observing is hat messages only get
JBM knows nothing about MDBs, MDBs and all their configuration params are part
of the app server, and not part of JBoss Messaging.
All JBM knows about is message consumers, and has no idea of whether the
consumer is an MDB or some other kind of consumer.
JBM determines if a consumer is busy on
What database are you using?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4158844#4158844
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4158844
___
jboss-user mailing list
http://jira.jboss.org/jira/browse/JBMESSAGING-1374
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4158269#4158269
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4158269
___
You shouldn't use a clustered connection factory with MDBs - if you look - the
default configuration uses a non clustered connection factory.
Using a clustered connection factory means subsequent create connection
attempts will round robin - this is typically not what you want with MDBs.
MDBs
Please feel free to mail me directly and we can arrange something :)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4158257#4158257
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4158257
I believe there have been several other threads on this topic in this forum in
the past.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4158272#4158272
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4158272
[EMAIL PROTECTED]|redhat].com
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4158472#4158472
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4158472
___
jboss-user mailing list
Or visit us on our irc channel
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4158477#4158477
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4158477
___
jboss-user mailing list
Well.. JBM 2.0 does not require queues to be predefined in config files.
It really depends what you want to do, without more detail it's hard for me to
say what would be best for you.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4158205#4158205
Reply to the
Just to correct what Clebert said, since it's not quite correct.
JBM will not *always* send messages to local consumers, messages can also be
distributed to other nodes if the local consumers are busy or non existent.
I'd suggest reading the documentation, and looking at other threads which
I moved this from the design forum.
Please don't post user questions in the design forum.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4158135#4158135
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4158135
This is handled by JBoss Remoting, not JBM.
I believe they use statics to identify whether clients and servers are in same
classloader.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4157891#4157891
Reply to the post :
blublinsky wrote : Thanks,
| Do you have an example of integration of JBM with LDAP for queue
definitions (that will work JBM 2.0) anywhere?
I guess I haven't quite understood what you want to achieve - can you explain
in more detail?
You want to put your queue names in LDAP, like you put
I think that's the case at the moment. But it's an implementation detail and
subject to change.
If you rely on such details in your application, it will make it brittle and
also non portable (so other messaging systems will probably have different
behaviour since this is outside the JMS spec).
rdaly wrote :
| In searching through the Jboss-Messaging code, I found the code that parses
the remoting-*-service.xml files. The class is
org.jboss.remoting.transport.Connector. There is a method inside that class
that parses the xml:
|
That's jboss remoting code (not jboss messaging
Yes, JBM will automatically use in vm optimisation if client and server are in
same vm (and classloader).
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4157585#4157585
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4157585
Hello blublinsky-
Yes, JBM 2.0 will support transparent distributed destinations like JBM 1.4,
sounds like this is what you need.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4157587#4157587
Reply to the post :
Different machines should be pretty the same as same machine.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4157644#4157644
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4157644
ejb3workshop wrote :
| However with ClusteredXAConnectionFactory it seems that message is sent
outside the transactional context. Rather frequently it happens that the
message arrives at the next bean, but the persistence has't finnished. The
messages are however distributed evenly across
ejb3workshop wrote : Maybe I didn't explain is correctly. I am sending a
message as well as persisting and entity. Since I would like to use XA, I'd
expect both to succeed. For this to be the case the entity should be persisted
and the message should be placed on the queue. However the message
ejb3workshop wrote : But then it wouldn't be atomic, nor consistent or
durable. What happens in this case if 3 should fail and the transaction has to
be rolled back ?
|
Actually it is all three of those, and you missed the I (Isolated) ;)
In a 2pc protocol, all participants have already
I would wait until beta. 1.4 and 2.0 are significantly different.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4157808#4157808
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4157808
We're currently aiming for Q3/Q4 for beta (October?).
We're not intending to make any more releases between now and beta, but you can
always check out SVN to see the current state of where we are. :)
View the original post :
Have you tried looking at the user guide?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4157152#4157152
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4157152
___
jboss-user
If you rollback a transaction in which you have consumed three messages A, B,
C, then the order will indeed be preserved on rollback with JBM.
However if you rollback each message in it's *own* transaction, then I don't
think it's physically possible to guarantee any order.
Rollback just puts
Please see the userguide for how to install JBM in JBoss AS 4.2.
The guide mentions the remoting version to use is 2.2.2.SP4, this should work
fine, and was correct at the time of writing.
You can also use 2.2.2.SP7 which has some more bugs fixed.
We haven't tested JBR 2.4 yet.
View the
How is this related to JBoss Messaging?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4156582#4156582
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4156582
___
jboss-user mailing
szhigunov wrote :
| Is there the way to tell the system I need just one at a time?
|
|
Not for JBM 1.x.
In JBM 2.0 it allows the behaviour you expect, but that won't be ready for
production for some time.
View the original post :
jamesbo wrote : Is it possible that I'm not getting proper transaction
integration if using connections not obtained via a JCA ConnectionManager?
Yes you must always use the JCA managed connection factory if you want
transaction propagation from EJB--JMS.
View the original post :
armgong wrote : today i have figured out to upgrade to 1.4.0sp3_cp02 on jboss
4.2.2GA,it seem works!
|
| my step as following:
|
| 1 upgrade jboss-remoting 2.2.2-sp7-brew
|
| 2 replace jboss-messaging with we build
|
| 3 modify xxx-persistence-service.xml in
To find out the dependencies for any version, look at the build-thirdparty.xml
file in the root of the tag.
E.g.
http://anonsvn.jboss.org/repos/messaging/tags/JBossMessaging_1_4_0_SP3_CP02/build-thirdparty.xml
These are the versions you need to use. We don't guarantee any thing will work
if
1.4.1.CR1 is for *jboss 5* not for *jboss 4.2.2*.
The latest distro'd 4.x version is JBM 1.4.0.SP3, or you can build
1.4.0.SP3_CP02 from the tag.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4156191#4156191
Reply to the post :
1.4.1.CR1 is for *jboss 5* not for *jboss 4.2.2*.
The latest distro'd 4.x version is JBM 1.4.0.SP3, or you can build
1.4.0.SP3_CP02 from the tag.
All releases are available in svn, whether or not we build a distro for you.
See http://anonsvn.jboss.org/repos/messaging/tags/
View the original
The error message explains it.
You have active subscribers - you need to close them first, as per JMS spec.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4156189#4156189
Reply to the post :
Yes we'll probably create one soon (similar to 1.4.0.SP3_CP02), when we have
some time.
But you may as well just get it from svn, it's pretty much the same thing.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4156220#4156220
Reply to the post :
JBoss messaging 2.0.0 alpha is released!
The goal of JBM 2.0 is simple and uncompromising- to bring unrivalled levels of
performance to reliable messaging, and to be the fastest, best featured and
most scalable open source messaging system. Period.
JBM 2.0 alpha is a technology preview of our
Why are you asking this on the JBoss Messaging forum?
That's like me making as post on the ActiveMQ forum How do I set up Geronimo
to use JBoss Messaging?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4153157#4153157
Reply to the post :
Have you looked in JIRA to see if there is a matching bug report that has been
fixed in a later version?
Have you tried 1.4.0.SP3_CP02?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4152881#4152881
Reply to the post :
That's not correct, ndb *is* supported from JBM 1.4.0.SP3_CP02.
See JIRA http://jira.jboss.org/jira/browse/JBMESSAGING-1261
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4151266#4151266
Reply to the post :
And what has this got to do with JBoss Messaging?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4150945#4150945
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4150945
___
This may be
http://jira.jboss.org/jira/browse/JBREM-947.
http://jira.jboss.org/jira/browse/JBMESSAGING-1268
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4150989#4150989
Reply to the post :
Note the workaround is against *1.4.0.SP3_CP02*, you are using 1.4.0.SP3_CPO1 I
believe.
1.4.0.SP3_CP02 is what Clebert suggested you use some posts back IIRC.
Also any reason why you guys aren't using your support contract?
View the original post :
401 - 500 of 1586 matches
Mail list logo
