update to previous notes.
When my app tries to send a message to a local topic - I get the following
exception :
org.jboss.mq.SpyJMSException: Cannot send a message to the JMS server; - nested
throwable: (java.io.IOException: Client is not connected)at
I _think_ what you guys are seeing is simply a debug message -- it does'nt
indicate any problem -- and can simply be gotten rid of by modifying your
conf/log4j.xml file -- it seems like the standard log4j.xml ships with this
anomalie !
View the original post :
Hi There,
I have my JBoss server setup to listen to a remote queue as per the wiki - and
this works fine,
however - today I noticed - that when the remote machine went down, my app was
no longer able to send messages to local topics (although local queues worked
fine),
when attempting to
If I understand your post and your code correctly -- the problem seems to be to
do with the ConnectionFactory you are using..
if you want your JMS message to be commited(send)/rolled-back as part of the
CMP transaction -- you need to use the XA connection factory : java:/JmsXA ..
otherwise the
Hi There,
I have read the FAQ regarding listening to a Remote Queue/Topic, and setup
something along those lines and it seems to work fine -- however -- I want to
listen to several remote queue's each of which is on a different remote server.
can anyone give me any tips on how to configure
Not a 100% solution -- but I'm pretty sure you can use some kind of variable
names in your xdoclet tags, and then setup your ANT build file and xdoclet task
to replace those as required, e.g.
* @jboss.entity-command name=${entity-command-name}
* @jboss.entity-command-attribute name=sequence
JBoss 3.2.6 3.2.7, CMP, CMT, Postgres DB
I have two tables (salesorderdetail, lock), salesorderdetail has a lock_id
column which is a foreign key into the lock table, and I have two corresponding
entitys (salesorderdetail, lock) one of which has a CMR into the other
SalesOrderDetailBean.java
Seems to work fine in 3.2.6 (although not in 3.2.4 or 3.2.5)
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=382#382
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=382
Just a ME-TOO
We do exactly the same -- use JBoss/J2EE transactions within the middle-tier,
but also have a lockVersion field in the VO sent to the client -- so when the
client hits save -- we lookup the entity - compare the lockVersion with that in
the VO and if they don't match we throw a
(using JBoss 3.2.4 3.2.5, CMP, CMT, and Optimistic Locking using a
lockVersion column)
We have noticed that if we have two tables - lets call them cartitem and item,
and we have a fkey reference from cartitem (cartitem.item_id) into item
(item.item_id) and CartItem has a CMR method getItem(),
Using JBoss 3.2.5, Instance Per Transaction CMP 2.x Container, optimistic-locking,
and modified-strategy..
I have a problem whereby the modified field used in the WHERE clause for the UPDATE
seems to be wrong (includes fields which have not changed).
I've setup a little test case which gets a
Using JBoss 3.2.5, Instance Per Transaction CMP 2.x Container, optimistic-locking,
and modified-strategy..
I have a problem whereby the modified field used in the WHERE clause for the UPDATE
seems to be wrong (includes fields which have not changed).
I've setup a little test case which gets a
12 matches
Mail list logo
