Hi list;
We encountered "java.net.SocketException : Sockect close " when we upgraded
jboss from 3.2.3 to 3.2.5 on one of our production server. The application
compose of a servlet (recieve request and jms client) and a mdb. Message are
send a text message. Although request got process by md
m.Document;
|
| /**
| * @author jmer
| *
| */
| public class MyBeanRepositorySelector implements RepositorySelector{
|
| private static boolean initialized = false;
| private static Object guard = new Object();
|
| private static Map repositories = n
Hi all;
Am using 2 box of redhat advance server with jboss-3.2.3 and jdk-1.4_02 on
clustered and loadbalance(modjk) production enviroment. So far the application
is running smoothly, we came to the point of adding additional application on
it the only problem we expect to encounter once dev
okay. i switch over to the default cluster-service.xml and restarted node1 and node2
after node1 finishes booting up. But sitll they cant see each other. and also added
bind_addr=
node1
| [EMAIL PROTECTED] deploy]# netstat -nr
| Kernel IP routing table
| Destination Gateway
i found out that the 2 box run on diffrennt version of linux. I formatted one of our
dev server and load same os as the other dev server using redhat9. I also upgraded
j2sdk1.4.0 to j2sdk1.4.2_05. When i started the two box it seems that they can find
each other usign the default cluster-servic
HI list tried to start one node and i get this error? whats causing this. Im using
jboss-3.2.3 and jdk1.4.0 on top linox RDhat 9
2004-09-09 16:53:59,017 DEBUG [org.javagroups.DefaultPartition] [Thu Sep 9 16:53:59
PHT 2004] [ERROR] JChannel.connect(): exception: java.net.SocketException
: setsock
Hi list;
Im trying to set up HTTP session replication as Load Balace scheme for our
application, clustering and farming on two linux box using jboss3.2.3 and jdk1.4.0.
From the payed PDF file its very straigth forward to setup HTTP session replication
and but i lacks content on the Farming S
I agree when you say anonymous wrote : You can also provide the expiration time as
part of the user message headers, which do get copied over to the DLQ message.. So by
changing the TTL on the DLQ the original message expiration increment by what is set
in the TTL seconds so the message never g
i had experience this too on linux box 9, so i make a watch dog script to restart
jboss is things when down. but anyway thanks to the environment export its all hone
now. On windows we have'nt experience such things.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopi
Thank you the reply , greatly appricaited.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3834396#3834396
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3834396
---
T
here is my config, but still i get mo logs /var/log/smart.log
log4j.xml:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
syslog.conf
| local6.*/var/log/smart.log
|
/etc/rc.d/init/syslog:
| SYSLOGD_OPTIONS="-r -m 0"
|
did i miss som
Hi list;
Im trying to point my Application log to syslog. Currently i define this on
jboss-3.2.3 log4j.xml. jboss running on Linux box 9
and
on my Linux box i added
We are deleveloping our codes on windows platform and deployed them on Linux box. Just
an add, a servlet receives incoming xml and send it to QueueA on which MyMDB consumes
it. The sqlserver reside from other box while mysql and jboss reside on same box. I
also assumed that the server (linux) is
Hi list;
Im using jboss-3.2.2 as server. Im doing a load testing my MDB using Jmeter.My
MDB does is read a Object message from a queue and query a stored procedure on sql
server(select) and dump the result to a mysql database and finally create a message
and send to another on which anot
Thank you once again for the enlightenment. By the way i use
messageDrivenContext.setRollbackOnly().
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831672#3831672
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831672
//send_buff_info.send(msg);
send_buff_info.send(msg,DeliveryMode.PERSISTENT, 4,
6);
send_buff_info.close();
conn.stop();
session.close();
resolved this i added setJMSExpiration(6) on my ObjectMessage before
sending it to queue(A). I was expecting the message to expired but setJMSExpiration
seems not to be working. I tried to print the JMSExpiration() on the MDB side but i
get "0". Did i miss something???
Many thanks;
17 matches
Mail list logo
