[Remoting] - Re: Socket Timeout?
by ron.sigal@jboss.com
If you're using the UnifiedInvoker, which is based on JBossRemoting, then you can go to $JBOSS_HOME/server/$CONFIG/conf/jboss-service.xml and update the "jboss.remoting:service=Connector,transport=socket" MBean with a "timeout" parameter:
| <mbean code="org.jboss.remoting.transport.Connector"
| name="jboss.remoting:service=Connector,transport=socket"
| display-name="Socket transport Connector">
|
| <attribute name="Configuration">
| <config>
| <invoker transport="socket">
| ...
| <!-- set timeout to one minute -->
| <attribute name="timeout" isParam="true">60000</attribute>
| ...
| </invoker>
| ...
| </config>
| </attribute>
| </mbean>
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4219356#4219356
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4219356
17 years, 1 month
[Management, JMX/JBoss] - Re: JBoss LoggingMonitor -
by mobaxkrs
Hi all
I have a webservice hosted and can view the details of MBean in JMX-console.
Under jboss.ws
anonymous wrote :
| context=SampleWebService,endpoint=SampleWebService
|
The attributes listed includes request, response counts
So, I tried to use loggingmonitor to get these values.
my xml file in deploy directory has
| <attribute name="MonitoredObjects">
| <configuration>
| <monitoredmbean name="jboss.ws.SampleWebService"
| logger="SampleLogger">
| <attribute>RequestCount</attribute>
| <attribute>ResponseCount</attribute>
| <attribute>FaultCount</attribute>
| </monitoredmbean>
| </configuration>
| </attribute>
|
But I get error in server log as
anonymous wrote :
| --- Incompletely deployed packages ---
| org.jboss.deployment.DeploymentInfo@4b9e0dcf { url=file:/root/mobicents-all-1.2.0.CR3-jboss-4.2.3.GA-0812022325/jboss-4.2.3.GA/server/default/deploy/SampleWebService-monitor.xml }
| deployer: null
| status: null
| state: INIT_WAITING_DEPLOYER
| watch: file:/root/mobicents-all-1.2.0.CR3-jboss-4.2.3.GA-0812022325/jboss-4.2.3.GA/server/default/deploy/SampleWebService-monitor.xml
| altDD: null
| lastDeployed: 1237442698503
| lastModified: 1237442698000
| mbeans:
|
Pl. help out?
regards
KRS
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4219350#4219350
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4219350
17 years, 1 month
[Remoting] - Re: Messaging blocked by long time-out
by ron.sigal@jboss.com
I have a question.
On the server side, there is an org.jboss.remoting.Lease which, if it doesn't receive pings from the client in a timely fashion, will declare that a connection is broken and inform any registered listeners. Now JBossMessaging registers a listener, so it should be informed about the broken connection, and it should attempt to shut it down. Now, Remoting won't try to kill a Socket in the middle of a read() or write(), but I'm a little surprised that JBossMessaging doesn't clean things up enough to prevent all the other clients from receiving messages.
Are you seeing the output from
| log.trace("Notified connection listener of lease expired due to lost connection from client (client session id = " + clientHolder.getSessionId());
|
on your server logs?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4219349#4219349
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4219349
17 years, 1 month