[Remoting] - Re: Problem for Timer of BisocketServerInvoker
by ron.sigal@jboss.com
Well, I've heard of that problem, but I'm not sure it really exists.
1. I've profiled the bisocket code without finding any leak.
2. When java.util.TimerTask.cancel() is called it sets its "state" variable to "CANCELLED". Now, java.util.TimerThread.mainLoop() does this:
| task = queue.getMin();
| synchronized(task.lock) {
| if (task.state == TimerTask.CANCELLED) {
| queue.removeMin();
| continue; // No action required, poll queue again
| }
|
so the first time the cancelled TimerTask gets run, it should be removed from the java.util.Timer's queue.
3. BisocketSocketInvoker will recreate its Timer if the Timer has shut itself down, but the reference to the old Timer would be lost, so the old Timer should get garbage collected eventually.
If I'm wrong about anything here, or if I'm missing something, please let me know.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160712#4160712
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160712
17 years, 10 months
[JBoss Portal] - Re: Multi-CMSPortletWindow uri change with one URL
by cavani
Hey dude... I am feeling very stuped right now, but know I get it!
Try it:
| public class Listener implements PortalNodeEventListener
| {
|
| private String uri;
|
| public PortalNodeEvent onEvent(final PortalNodeEventContext context, final PortalNodeEvent event)
| {
| if (event instanceof WindowNavigationEvent)
| {
| final WindowNavigationEvent windowEvent = (WindowNavigationEvent) event;
|
| final PortalNode node = windowEvent.getNode();
|
| if (!node.getName().equals("Content"))
| return context.dispatch();
|
| final Map<String, String[]> parameters = windowEvent.getParameters();
|
| final String[] param = parameters.get("uri");
|
| if (param == null || param.length == 0 || param[0] == null || param[0].trim().equals(""))
| return context.dispatch();
|
| uri = param[0].replace(".html", "_related.html");
| }
| else if (event instanceof WindowRenderEvent)
| {
| final WindowRenderEvent windowEvent = (WindowRenderEvent) event;
|
| final PortalNode node = windowEvent.getNode();
|
| if (!node.getName().equals("Related"))
| return context.dispatch();
|
| Map<String, String[]> parameters = windowEvent.getParameters();
|
| parameters.put("uri", new String[] { uri });
|
| uri = null;
| }
|
| return context.dispatch();
| }
|
| }
|
Thanks,
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160709#4160709
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160709
17 years, 10 months
[Management, JMX/JBoss] - Re: JDBC Metrics
by indra_joy
Thanks peter. I already checked that before but it gives only
1. AvailableConnectionCount
2. ConnectionCount
3. MaxConnectionsInUseCount
4. InUseConnectionCount
5. ConnectionCreatedCount
6. ConnectionDestroyedCount
I am trying to explain more.
JDBC Connection Pool Wait: Average number of connections waiting in the pool.
JDBC Connection Pool Wait Threads:Drill Down View of threads waiting for a connection from the pool.
JDBC Client Wait Time:Average time that a client waits for a connection from the pool
JDBC Client Wait Time Threads:Drill Down View of threads waiting for a connection from the pool.
JDBC Connection Pool Timeout:Number of times a client waited for a connection
JDBC Connection Pool Timeout Threads:Drill Down View of threads that timed out after waiting for a connection from the pool
JDBC Connection Throughput:Number of connections allocated to and returned by applications
Can you please help me in this.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160708#4160708
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160708
17 years, 10 months
[JBoss Messaging] - Re: JBoss Messaging and Bisocket Transport
by ron.sigal@jboss.com
Hi Ebe,
The bisocket transport needs the second port to support clients behind firewalls, which, as you mention, is the reason the bisocket transport was developed. However, if you're not going to use the bisocket transport, you can just remove the bisocket configuration and it won't run at all.
I believe that the JBossMessaging directory structure might change from version to version, but you should look for a file in the JBM deployment that's called something like "remoting-service.xml" and look for the bisocket Connector MBean:
| <mbean code="org.jboss.remoting.transport.Connector"
| name="jboss.messaging:service=Connector,transport=bisocket"
| display-name="Bisocket Transport Connector">
| <attribute name="Configuration">
| <config>
| <invoker transport="bisocket">
|
| <!-- There should be no reason to change these parameters - warning!
| Changing them may stop JBoss Messaging working correctly -->
| <attribute name="marshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
| <attribute name="unmarshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
| <attribute name="dataType" isParam="true">jms</attribute>
| <attribute name="socket.check_connection" isParam="true">false</attribute>
| <attribute name="timeout" isParam="true">0</attribute>
| <attribute name="serverBindAddress">${jboss.bind.address}</attribute>
| <attribute name="serverBindPort">4457</attribute>
| <attribute name="clientSocketClass" isParam="true">org.jboss.jms.client.remoting.ClientSocketWrapper</attribute>
| <attribute name="serverSocketClass">org.jboss.jms.server.remoting.ServerSocketWrapper</attribute>
| <attribute name="numberOfCallRetries" isParam="true">1</attribute>
| <attribute name="pingFrequency" isParam="true">214748364</attribute>
| <attribute name="pingWindowFactor" isParam="true">10</attribute>
| <attribute name="onewayThreadPool">org.jboss.jms.server.remoting.DirectThreadPool</attribute>
| <!-- End immutable parameters -->
|
| <!-- Periodicity of client pings. Server window by default is twice this figure -->
| <attribute name="clientLeasePeriod" isParam="true">10000</attribute>
|
| <!-- Number of seconds to wait for a connection in the client pool to become free -->
| <attribute name="numberOfRetries" isParam="true">10</attribute>
|
| <!-- Max Number of connections in client pool. This should be significantly higher than
| the max number of sessions/consumers you expect -->
| <attribute name="JBM_clientMaxPoolSize" isParam="true">200</attribute>
|
| <!-- Use these parameters to specify values for binding and connecting control connections to
| work with your firewall/NAT configuration
| <attribute name="secondaryBindPort">xyz</attribute>
| <attribute name="secondaryConnectPort">abc</attribute>
| -->
|
| </invoker>
| <handlers>
| <handler subsystem="JMS">org.jboss.jms.server.remoting.JMSServerInvocationHandler</handler>
| </handlers>
| </config>
| </attribute>
| </mbean>
|
If you delete that and replace it with an HTTP connector, the secondary port will go away.
-Ron
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160706#4160706
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160706
17 years, 10 months