[Management, JMX/JBoss] - Can't use JMX query syntax in JMX console filter
by metricsdude
This is just a rant, but it would be nice if the JMX console let you use JMX query syntax, instead of supplying a 'user friendly' filter. The filter is pretty close to JMX query syntax, but it's not, so I find it frustrating.
In particular, the thing I hate is that you cannot put the * anywhere you want to in the list of ObjectName key properties. For example '*:*,type=channel' is a valid ObjectName pattern, but can't be used as a filter in the JBoss JMX console. It fails in the JMX console because JBoss appends it's own ',*' to the 'filter'. Jboss assumes you didn't do it and assumes that you want a pattern.
I find that odd, considering JBoss' persistence that it's fully standards compliant, though in all fairness there is no claim in the JMX console that you can use ObjectName patterns, just that you can use a 'filter'. Hoaky, imho.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4152801#4152801
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4152801
17 years, 11 months
[Clustering/JBoss] - Re: HAJNDI failover exception
by davidchen
Thank you very much Brain for quick reply. Here, I just want to list my couple cents on that issue which may help for others:
1. number of retries to get connection from pool is by default the maximum value, 30. That's the reason, it keeps trying for about 30 seconds (about a second every try).
So, I reduced that number to the minimum value 1 by adding following attribute
| <attribute name="numberOfRetries" isParam="true">1</attribute>
|
inside jboss-service.xml, like:
| <attribute name="Configuration">
| <!-- Using the following <invoker> element instead of the InvokerLocator above because specific attributes needed. -->
| <!-- If wanted to use any of the parameters below, can just add them as parameters to the url above if wanted use the InvokerLocator attribute. -->
| <config>
| <!-- Other than transport type and handler, none of these configurations are required (will just use defaults). -->
| <invoker transport="socket">
| <attribute name="dataType" isParam="true">invocation</attribute>
| <attribute name="marshaller" isParam="true">org.jboss.invocation.unified.marshall.InvocationMarshaller</attribute>
| <attribute name="unmarshaller" isParam="true">org.jboss.invocation.unified.marshall.InvocationUnMarshaller</attribute>
| <!-- This will be port on which the marshall loader port runs on. -->
| <!-- <attribute name="loaderport" isParam="true">4447</attribute> -->
| <!-- The following are specific to socket invoker -->
| <!-- <attribute name="numAcceptThreads">1</attribute>-->
| <!-- <attribute name="maxPoolSize">303</attribute>-->
| <!-- <attribute name="clientMaxPoolSize" isParam="true">304</attribute>-->
| <attribute name="socketTimeout" isParam="true">600000</attribute>
| <attribute name="serverBindAddress">${jboss.bind.address}</attribute>
| <attribute name="serverBindPort">4446</attribute>
| <!-- <attribute name="clientConnectAddress">216.23.33.2</attribute> -->
| <!-- <attribute name="clientConnectPort">7777</attribute> -->
| <attribute name="enableTcpNoDelay" isParam="true">true</attribute>
| <attribute name="numberOfRetries" isParam="true">1</attribute>
|
2. Cache ejb home in client code will help a lot:
It seems failover and raise that connection exception only whenever I did a new jndi lookup for an ejb. So, in my client code, I cache ejb home as much as I can, which will avoid those connection retries a lot.
Again, any further hints or suggestions are highly appreciated. Thanks a lot again for the help.
David
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4152796#4152796
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4152796
17 years, 11 months
[JNDI/Naming/Network] - Re: java.lang.NoClassDefFoundError: org/jnp/server/NamingSe
by sagi7
Hello,
the class i see in the verbose mode in the working environment is NamingServer_Stub
from the jbossall_client and never NamingServer.
Here is the full stacktrace
Exception in thread "AWT-EventQueue-0" java.lang.NoClassDefFoundError: org/jnp/server/NamingServer
at org.jboss.naming.java.javaURLContextFactory.(javaURLContextFactory.java:37)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:242)
at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:50)
at com.sun.naming.internal.ResourceManager.getFactory(ResourceManager.java:371)
at javax.naming.spi.NamingManager.getURLObject(NamingManager.java:575)
at javax.naming.spi.NamingManager.getURLContext(NamingManager.java:533)
at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:279)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at de.test.pps.util.GenericFactoryUtil.lookupHome(GenericFactoryUtil.java:21)
at de.test.pps.util.GenericFactoryUtil.getHome(GenericFactoryUtil.java:41)
at de.test.pps.gui.Login.doLogin(Login.java:159)
at de.test.pps.gui.Login.jPasswordField1KeyReleased(Login.java:139)
at de.test.pps.gui.Login.access$1(Login.java:134)
at de.test.pps.gui.Login$2.keyReleased(Login.java:98)
at java.awt.Component.processKeyEvent(Component.java:5478)
at javax.swing.JComponent.processKeyEvent(JComponent.java:2722)
at java.awt.Component.processEvent(Component.java:5294)
at java.awt.Container.processEvent(Container.java:1966)
at java.awt.Component.dispatchEventImpl(Component.java:3984)
at java.awt.Container.dispatchEventImpl(Container.java:2024)
at java.awt.Component.dispatchEvent(Component.java:3819)
at java.awt.KeyboardFocusManager.redispatchEvent(KeyboardFocusManager.java:1826)
at java.awt.DefaultKeyboardFocusManager.dispatchKeyEvent(DefaultKeyboardFocusManager.java:681)
at java.awt.DefaultKeyboardFocusManager.preDispatchKeyEvent(DefaultKeyboardFocusManager.java:938)
at java.awt.DefaultKeyboardFocusManager.typeAheadAssertions(DefaultKeyboardFocusManager.java:810)
at java.awt.DefaultKeyboardFocusManager.dispatchEvent(DefaultKeyboardFocusManager.java:645)
at java.awt.Component.dispatchEventImpl(Component.java:3857)
at java.awt.Container.dispatchEventImpl(Container.java:2024)
at java.awt.Window.dispatchEventImpl(Window.java:1791)
at java.awt.Component.dispatchEvent(Component.java:3819)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
best regards
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4152791#4152791
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4152791
17 years, 11 months