excellent, I would make sure the other config files are also available on the
classpath, queues.xml, jbm-jms.xml and jbm-configuration..xml.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4202277#4202277
Reply to the post :
http://www.jboss.com/index.html?mod
is the jbm-security.xml config in the classpath?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4202037#4202037
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4202037
___
jboss-
I would post on the app server forum, they should be able to help you.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201670#4201670
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201670
anonymous wrote : 1) Above error is because of low pool size ?
I would say yes. also increasing the blocking timeout should also help. This is
an app server question not a messaging question. I would post on the jboss
forum and they should be able to help with settings etc.
View the original p
Messages are deleted from the database once all message references have been
consumed and either acknowledged or the tx commited.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201255#4201255
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=p
have a look at the JBM user guides for you're specific JBM version at
http://www.jboss.org/jbossmessaging/docs/index.html
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200924#4200924
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&m
I seem to be getting lots of warnings when i run the tests. something to do
with paging i think
| 07-Jan-2009 09:14:01 org.jboss.messaging.core.logging.Logger warn
| WARNING: Directory
data/paging/NwA1ADkAMgA1AGUANwA2AC0AYQAyADgAMQAtADQANwA3ADYALQA5ADQANAA5AC0ANABiADQAMQAy
| AGYAYwBmAGIAN
I think the problem you have is you're creating state from a http request. The
http request/response paradigm is stateless and shouldn't be spawning any
threads etc. you can add objects to a http session and access them from within
a servlet but these are tied to the session. Maybe you need a re
I'm not 100% sure what you're problem actually is but it sounds to me like you
need to use durable subscribers!
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199699#4199699
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&
what is it you're trying to achieve
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4198232#4198232
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4198232
___
jboss-user mailing
Obviously you're configuration is incorrect. I would go through it and double
check its correct.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4198217#4198217
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4198217
_
That configuration has changed since that version. If you want to change the
security configuration, you'll see it in messaging-jboss-beans.xml.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4198215#4198215
Reply to the post :
http://www.jboss.com/index.html
I would run the clustering examples to validate your installation is correct.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4197358#4197358
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4197358
_
looks like a network problem, maybe this node has a slightly problematic
network connection.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4197348#4197348
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4197348
_
you'll need clustered set to true for each queue you want clustered. heres a
sampled clustered queue config:
| jboss.messaging:service=ServerPeer
| jboss.messaging:service=PostOffice
| true
|
View the original post :
http://www.jboss.com/index.html?module=bb&op=
This is just the messages being deserialized.
Is you're clustering configuration correct. Maybe you're queue isn't clustered
and the consumer is connecting to a different node. I would run the clustering
examples to validate your installation is correct.
View the original post :
http://www.jbo
This looks like a question for the app server guys. Post on their forum and
they should be able to help
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4196811#4196811
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=419681
anonymous wrote : Is there any limits of no. of messages on one queue ?
| Is there any limits of total no. of messages ?
There are no actual limits. JBM will start to page messages to the database
once a certain threshold is reached. These are read back in to memory when a
queue dips below a
Hypersonic is the out of the box persistence engine. look under
server/messaging/data and you'll see a hypersonic folder. Delete this if you
want to clear the messages.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4196804#4196804
Reply to the post :
http:/
Ok, any chance you can test with jboss 4.2.3.GA to see if you get the same
result.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4196573#4196573
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4196573
___
This is a question for the app server guys. This question has been raised a few
times, search on the forums and you should find the answer.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4196477#4196477
Reply to the post :
http://www.jboss.com/index.html?modu
You probably need to do something like add an interceptor to the following
aspect.
|
|
The aop docs should help you with what you can and can't do.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4196476#4196476
Reply to the post :
http://ww
you need to use the java:/JmsXA connection factory, have a llook at the MDB
examples shipped with JBM 1.4
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4196277#4196277
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4196
you need to commit the session after you have sent the message, i.e.
jmsSession.commit();
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4196261#4196261
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4196261
anonymous wrote : With the first issue I wanted to know if a durable subscriber
receives the published messages in the same order the sender had published
them.
Yes, the JMS spec defines that a messages must be delivered in the order they
were sent.
anonymous wrote : Moreover I wanted to know
anonymous wrote : I don't know what you mean for "rollback" in this case... the
message is posted on the topic, delivered once, never acked. Then the topic is
unsuscribed and the session is closed, I'm expecting not to find the message in
the topic when specified TTL has expired.
Ok, I think I
anonymous wrote : First, is exactly once semantic and ordered garanted on
receiver side?
I'm not 100% sure what problem you have here, could you elaborate.
anonymous wrote : Second, I experimented that a second durable late joiner on a
topic does't receive any message while the first receive i
anonymous wrote : Expired messages are not removed from persistence (JBM_MSG)
util an acknoledge is called
That's correct, all messages must be kept in storage until they are properly
consumed, i.e. they have been acknowledged or rolled back. If they are acked
they are deleted from the database
If you open a JIRA you can attach the test to it.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4192026#4192026
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4192026
___
jboss
actually, on review i think you're correct. This may be a bug.
Any chance you could provide a standalone test to demonstrate it and someone
will take a look.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4192025#4192025
Reply to the post :
http://www.jboss.
anonymous wrote : Is this the expected behaviour?
FIrstly there is nothing in the jms specification regarding scheduling messages
so this will always be vendor specific. Relying on vendor specific
functionality makes your application less portable between jms products.
Anyway, in JBM 1.4 the sc
write a test to do it. send n messages with different priorities, then consume
n messages and check the the order.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190908#4190908
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=r
You need to look up the mbean server not create one.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190860#4190860
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190860
___
jb
anonymous wrote : If you cant wait you can always build it from CVS.
Obviously i meant SVN
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190758#4190758
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190758
__
Firstly, i would make sure that you're closing your connections when you're
finished with them.
Also theres a new release due out in the next week or two (1.4.1), I would give
this a go when its released to see if you get the same problem. If you cant
wait you can always build it from CVS.
I
The load balance is done at a connection level so once youve created you're
connection all message will be sent to the same server. Try creating multiple
connections to see what happens.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4188900#4188900
Reply to
This questions been raised quite a few times, search the forums to see.
in short when you have a distributed queue it will always deliver to its local
consumers first. There's no point wasting a network round trip if there is a
consumer locally.
View the original post :
http://www.jboss.com/in
anonymous wrote : Is there a way to have failover without clustering?
Not with JBM. I guess you create you're queue dynamically, you could make it so
that you always create you're producers and consumers on the same machine you
create the queue on, but this would have to be done at the applicati
If a queue is clustered and it has a local consumers then it distributes the
messages to the local consumers in a round robin fashion. If a queue has no
local consumers then it will distribute the messages around the cluster. If you
have a clustered queue with only one consumer then (apart from
If you say you're closing all the connections and you think the vpn is quite
stable then the clients being disconnected could be caused by something else. I
know remoting has some ping settings that might be affecting things.You could
try changing some of these
View the original post :
http://
I meant which minor version 1.4.0GA, 1.4.1GA etc, its so i can check the stack
trace against the correct svn tag.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187304#4187304
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=repl
The first thing i would do is upgrade to the latest 1.4 version to see if it
fixes the problem.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187275#4187275
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187275
__
which JBM version are you using JBM 1.4.?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187235#4187235
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187235
___
jboss-user ma
It looks like a client isn't closing its connections properly, hence the server
times the client out
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187229#4187229
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187229
_
anonymous wrote : If there's not already in JIRA, shall I go ahead and create
one for this?
feel free, but like I say we can't make promises what gets added to releases.
anonymous wrote : Details, please. A management API so that all subsequent
calls to createQueue/createTopic result in actual
anonymous wrote : Can't you get the same effect by create multiple queues bound
on the same address?
Tim's correct, in JBM 2 we have the notion of addresses. Every queue is bound
to an address so if you bind queue A,B and C to address queueABC, they all
recieve any messages routed to that addre
anonymous wrote : - Virtual destinations. See
http://activemq.apache.org/virtual-destinations.html. Messages sent to single
destination are copied, filtered, and routed to multiple destinations.
we don't virtual destinations but we do support wildcard routing in JBM 2.0.
i.e. if you send a mes
purely for performance reasons I think. adding referential constraints means it
would take longer to insert a record, it wouldn't be much but since you could
be writing 1000's of records a second it can add up. You could always add the
FK your self if you thought it would be beneficial.
View t
It looks like you're database has got out of sync. There are some missing
message references in the JBM_MSG_REF table. deleting the data within this
table would solve you're problem but you would lose these messages.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopi
MDB's are part of the app server not messaging. They should be able to help you
in the app server forum.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185951#4185951
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=41859
anonymous wrote : Or does those blobs contain serialized/crypted objects?
yes the message is serialized.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183147#4183147
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183
This is the JBoss Messaging forum. I woul dpost this on the App server forum.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183146#4183146
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183146
_
Theres plenty about connection factories in the user manual. basically if
you're queue is clustered use the clustered connection factory, if not use a
plain connection factory
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183144#4183144
Reply to the post :
its just a guess bit It looks like you're client is not closing its connections
properly.
I would also suggest using a later version of JBM, theres been a lot of bugs
fixed since 1.3.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183143#4183143
Reply to th
anonymous wrote : I use a clustered environment. But it should also work in
case the other nodes were taken down for example for maintenance...
Of course you are right, but its an edge case. As far as maintenance goes, you
could always make sure there are at least 2 servers running. If you're br
anonymous wrote : Ok I tried to use the ExceptionListener and disabled failover
in the ClusteredConectionFactory. Now it works great if there are more than one
instance running.
|
| However if there is only one instance nothing seems to happen. There are
| no more warnings shown and the me
which version of JBM are you using, there have been issues like this fixed in
the past, for example https://jira.jboss.org/jira/browse/JBMESSAGING-924, but
these have been fixed
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4180588#4180588
Reply to the post
If you could provide a test we can use to recreate it we'll take a look.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4180547#4180547
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4180547
__
Are there any errors or warnings in the server logs, I'm typically thinking of
something to do with a clients connection failing.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4180545#4180545
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=p
the slow start up is probably due to the 'millions of messages' being loaded in
to memory at startup.
The 'createTablesOnStartup' attribute only calls a few sql statments so
changing this is unlikely to make any difference.
The 'UsingBatchUpdates' is for updates only so again thi sshouldn't mak
This is the JBoss Messaging forum, This doesn't seem like a question about
messaging, try the appropriate forum.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174223#4174223
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply
looks like you're missing the jgroups.jar. just add it to the messaging lib
dir.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174222#4174222
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4174222
This looks like a jgroups problem not a JBoss Messaging problem. Try the
appropriate forum and they should be able to help you.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171994#4171994
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=pos
Which version of JBoss Messaging are you using, can you try with the latest
versions (jboss 4.2.2 with JBM 1.4) to make sure it is still a problem.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171431#4171431
Reply to the post :
http://www.jboss.com/index.h
There may be a way of stopping the MDB from consuming messages i don't know,
speak to the App server guys they could help you. Alternatively you couls write
you're own mbean that consumes from the queue and stop and start the connection
your self.
View the original post :
http://www.jboss.com/
firstly, what versions are you using. secondly, if you think its not working as
required can you provide a test case.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171309#4171309
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=
With JBM 1.4 it is possible to specify the earliest time that a message will be
delivered. The user manual explains how to do this, but here you are anyway.
| long now = System.currentTimeMillis();
|
| Message msg = sess.createMessage();
|
This is the JBoss Messaging forum, please use the appropriate forum.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171240#4171240
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171240
__
anonymous wrote : it is an interoperability issue with JBoss
Exactly, this is the JBoss Messaging forum. Try using the correct forum and you
may get some help.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168191#4168191
Reply to the post :
http://www.jbos
anonymous wrote : Anyway to access this function through mbean?
no. Like I said before, if you're application is relying on vendor specific
code, then you are tying yourself into using that vendor. You need to rethink
your solution and make sure it is portable across multiple JMS products.
Vie
anonymous wrote : I am working on migrating code from weblogic to jboss.
|
| In weblogic, it is possible to suspend consumer of a queue by through
mbean. Message will stay in the queue and not be delieved to its receiver
including MDB.
When writing applications you should try not to use ve
anonymous wrote :
| That is not going to work with me since there is no
ClusteredConnectionFactory on machine1 from where I'm trying to send the
messages from. This example assumes that the sender is residing in the same AS
as the queue it self which is not the case for me.
You look up the
You could start by having a look at the clustered examples shipped with JBM.
Also the user doc is a good place to start.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167724#4167724
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mo
try running the clustered examples to make sure you're environment is set
upcorrectly.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167403#4167403
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167403
___
Messages can't be left in a "being delivered" state. If the client does not
consume and acknowledge a message, it is put back on the queue.
If you think this is not the case then can you provide a test case.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=41671
anonymous wrote : Sorry, I'll try to make it clearer. To sum it up, I can only
see 2 ways to resolve my problem (a client disconnecting from the server while
there were messages being delivered and coming back later using another
connection):
I'm still not sure what you're problem is? are you s
Yes, thats the Jira and will be available in Beta
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167007#4167007
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167007
___
jboss
If you are talking about an exposed management interface, which i think you
are, then this is currently being developed. This will be available sometime in
the near future.
What information are you looking for?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4
Looks like you're using the old config file, make sure you use everything from
the new distro, not just the jars.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166953#4166953
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=repl
we dont use maven. check it out using svn from
http://anonsvn.jboss.org/repos/messaging/trunk/ and you can build it using ant,
either 'ant distro' to build a distribution or you can run the server from
source via 'ant runServer';
View the original post :
http://www.jboss.com/index.html?modu
It probably is a bug, I've looked at the current code base and it looks like
its been fixed. You can build from SVN to get the latest version.
This is just an alpha release so there may be some bugs!
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166923#41669
anonymous wrote : I set mine to 400 - is that to high?
That depends on a number of things. How much memory you're client/server has,
how many clients you have etc, etc. This basically limits how many
connections/sessions etc a client can have open at any one time. Best way to
find out is to tr
This looks like a classpath issue, i would make sure you're web app is using
the correct jars
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166895#4166895
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4166895
I'm not sure what the question is you're asking. can you be a bit more
detailed about what you are trying to achieve.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166893#4166893
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode
If you use a clustered connection factory and set 'supportsfailover' to true,
the client will reconnect to another node transparently.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166884#4166884
Reply to the post :
http://www.jboss.com/index.html?module=bb
You should also try JBM 2.0 alpha
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166343#4166343
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4166343
___
jboss-user mailing li
anonymous wrote : One of the reasons I included the time to open a connection
is that I have found that developers often open a connection, send a single
message and then close the connection.
you're right, Spring JMS template does this, it is however a JMS anti pattern
and shouldn't be done.
This is the JBoss Messaging forum, you should post you're problem on the
JBossMQ forum.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165888#4165888
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165888
__
it's unlikely that this is actually an issue, its more likely configuration. If
you provide a test case demonstrating the problem i'll take a look.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165646#4165646
Reply to the post :
http://www.jboss.com/index.h
ok, again, persistent messages are always saved in the database, i.e
'persistent', non persistent message get saved to the database when paging
occurs. When paging occurs all messages are cached, i.e. they are released from
memory but only non persistent messages need to be saved.
View the orig
anonymous wrote : so if I set DeliveryMode=Persistent, the DownCacheSize which
does the batch paging is not useful any more, since it gets saved to database
right away, is it correct?
Wellnot exactly, all messages will actually go in to the down cache however
only non persistent messages will
The MaxBatchSize is how many messages are sent in a batch within a transacted
session. If you're sending lots of messages, increasing this property may
increase performance. As far as MaxBatchTime goes, this is the maximum time to
wait for the batch size to be reached before sending the messages
anonymous wrote : are you talking about DeliveryMode.PERSISTENT ? if I choose
to use database persistence, why do I still have to set this property?
I'm not sure what you mean when you say "if i choose database persistence". If
you're DeliveryMode is Persistent then all messages get saved to t
JBM 1.4 doesn't have producer flow control so its possible to overrun the
server. If you are getting an out of memory error then you can adjust your
paging and caching parameters. See the user doc for more detailed info.
p.s. JBM 2.0 will have full producer and consumer flow control!
View the
If the messages are persistent then they will all get saved to the database,
otherwise only paged messages will get saved.
To ensure that all messages are recovered just make sure you make them
persistent.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=416493
Are the messages persistent, if they are they will all appear in the database,
if not only paged messages will be persisted.
Make sure there are no warnings on the server?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164936#4164936
Reply to the post :
htt
This is a question for the app server guys, post on their forum and they should
be able to help
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164937#4164937
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4164937
__
Are you sure you are starting the connection? i.e. connection.start()
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164934#4164934
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4164934
_
First of all, you are using a very old version, any chance you could upgrade
and see if it still happens. Lots of bugs have been fixed since 1.0.1 GA
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164525#4164525
Reply to the post :
http://www.jboss.com/index
I have to agree with noelo, it looks like a disk problem.
I would suggest running in a different environment to see if the error still
occurs.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164250#4164250
Reply to the post :
http://www.jboss.com/index.html
101 - 200 of 302 matches
Mail list logo
