We are using Jboss4.2.4 with JBM 1.4.2.GA-SP1 and jboss-remoting-2.2.2.SP11.jar.
|invoker transport=bisocket
|attribute name=marshaller
isParam=trueorg.jboss.jms.wireformat.JMSWireFormat/attribute
|attribute name=unmarshaller
I thought there is a issue about remoting callbacktimout setting.The param
setting Socket's reading timeout.
But this problem is about Socket's writing timeout.JBM may blocked in socket
writing for 10 min in solairs.
View the original post :
Yes,This is a serious problem.
The JBM are not reliable in stressful conditions,We have to consider choosing
another mom production.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=457#457
Reply to the post :
I faced the serious problem which messaging blocked by long time-out.It happens
often in stressful conditions.
The issue has been discussed in the following link.
http://www.jboss.org/index.html?module=bbop=viewtopict=152037
http://www.jboss.org/index.html?module=bbop=viewtopicp=457#457
Hi
I know JBM server can work correct behind NAT/Firewall by setting
secondaryBindPort and secondaryConnectPort.
How about client behind NAT connect JBM Server? I tried.It seem works but
failed by connectionValidator?
Any Suggestion,or JBM does not allow the usage?
View the
Thanks for reply.I'll ask remoting.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4222180#4222180
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4222180
___
jboss-user mailing list
Hi all
I faced the same problem,Can Remoting provide a method to resolve the problem
like AMQ.
http://issues.apache.org/activemq/browse/AMQ-1993
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4220151#4220151
Reply to the post :
Thanks for reply.
Any plan to delete the out-of-date msg automatic if no durable subscriber?
The system will slow down when the records increasing in huge messages
situation.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4220150#4220150
Reply to the post :
Test again,It is my mistake.
The new subscriber do not receive old pending msg after JBM reboot.
But,the records in db does not deleted,my JBM_MSG_REF has more than 50,000
records.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4220011#4220011
Reply to the
Hi all
I faced the same problem,Can JBM or Remoting provide a method to resolve the
problem like AMQ.
http://issues.apache.org/activemq/browse/AMQ-1993
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4219749#4219749
Reply to the post :
Hi all
I faced the same problem,Can JBM or Remoting provide a method to resolve the
problem like AMQ.
http://issues.apache.org/activemq/browse/AMQ-1993
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4219752#4219752
Reply to the post :
lanceliao1 wrote : Hi all
|I faced the same problem,Can JBM or Remoting provide a method to resolve
the problem like AMQ.
| http://issues.apache.org/activemq/browse/AMQ-1993
Sorry for post wrong place.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp
We are using Jboss4.2.2 JBM 1.4.2 sp1.
publish persistent 50, msg
| publisher.publish(objMsg, DeliveryMode.PERSISTENT, PRIORITY,0);
|
All msg subscriber are Nondurable subscriber.
Due to some subscriber are very slow,jmx console show depth are increasing.And
we fount the count of
I faced the same problem.
Our db tables JBM_MSG and JBM_MSG_REF have millions records,And taked long time
while rebooting.
Any other solutions ?
How to configure the jms message timeout(eg 1hours)
TopicPublisher.publish(objMsg, DeliveryMode.PERSISTENT,
PRIORITY,60*60*1000);
Thanks for reply.
The JBossMQTimeToLiveNotWorkingProperl doc offer a method to solve message send
by out-of-syc GMT.
Is there any solution for jboss messaging.
http://www.jboss.org/community/docs/DOC-10539
And you meant the message timout only occur when JBM redelivery message to
consumers.Can
HI:
JBM Group.The para in remoting-bisocket-service.xml
| attribute name=validatorPingPeriod isParam=true1/attribute
| attribute name=validatorPingTimeout isParam=true5000/attribute
does not effect client-side.So we got lots of disconnection.
The file of
The problem has been resolved.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4193644#4193644
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4193644
___
jboss-user mailing list
I think there are some subtle mechanism.
JMSRemotingConnection public void start()
| Map config = new HashMap();
|
| config.put(Client.ENABLE_LEASE, String.valueOf(clientPing));
|
| if
Thanks a lot.
I have read the Issue.I make sure my remoting-bisocket-service.xml have the
line and the remoting version is 2.2.2sp7:
| !-- The maximum time to wait before timing out on trying to write a
message to socket for delivery --
| attribute name=callbackTimeout1/attribute
Thanks for reply.
We are using Remoting 2.2.2sp7. I make sure using thre same version of remoting
on both client and server.The remoting-bisocket-service.xml file:
| invoker transport=bisocket
|
|!-- There should be no reason to change these parameters -
1 The MessageingPostOffice need a readwritelock to handle msg,such as
route,binding,removeBinding.
2 Once find a route,get readwritelock,it is using MessagingQueue to handle the
msg(Delivery handle(DeliveryObserver observer, MessageReference reference,
Transaction tx)).
3 while handdling
Using auto_acknowledage mode create connection both on client and server side.
The similar codes are blow:
| TopicConnectionFactory topicFactory = (TopicConnectionFactory)
ContextUtil.getContext() .lookup(ConnectionFactory);
| topicConn =
The memory dump,I hope it will helpful.
Why 287 serversessionEndpoint and 133 ServerConsumerEndpoint? We have about 10
client_end receive and send msg,each end have 19 topic.
| 2124 152928 org.jboss.jms.message.JBossObjectMessage
| 2277 54648 org.jboss.jms.destination.JBossTopic
| 287
Socket info
Solaris: netstat -an
Local AddressRemote AddressSwind Send-Q Rwind Recv-QState
- -- - -- ---
192.166.32.8.4557192.166.32.155.52066 64679 0 49640 0 ESTABLISHED
192.166.32.8.4557
Hi JBMGroup.
We got a trouble about JBM.Using Jboss 4.22, JBM 1.4 sp3 cp04.After Long time
run and load increase,the JBM Server lose any response.
part thread dump:
| WorkerThread#160[192.166.32.8:33764] prio=3 tid=0x01664d88 nid=0x4d00
waiting for monitor entry [0x4927f000..0x4927fc70]
|
25 matches
Mail list logo
