[JBoss JIRA] Created: (JBAS-3877) The JMX HtmlAdaptor does not display the exception message
by Lior Shamir (JIRA)
The JMX HtmlAdaptor does not display the exception message
----------------------------------------------------------
Key: JBAS-3877
URL: http://jira.jboss.com/jira/browse/JBAS-3877
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: JMX
Affects Versions: JBossAS-4.0.4.GA
Reporter: Lior Shamir
Assigned To: Scott M Stark
Priority: Minor
In JBoss 3.2.x when exception occurred, the HtmlAdaptor display the exception message.
In JBoss 4.0.x the HtmlAdaptor display only a generic error message.
This is obviously a regression. Can you add the message back?
Here is an example:
4.0.4:
javax.servlet.ServletException: Failed to invoke operation
org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.invokeOp(HtmlAdaptorServlet.java:269)
org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processRequest(HtmlAdaptorServlet.java:100)
org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doPost(HtmlAdaptorServlet.java:82)
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
root cause
javax.management.MBeanException
org.jboss.mx.interceptor.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.java:180)
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:163)
org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
org.jboss.jmx.adaptor.control.Server.invokeOpByName(Server.java:258)
org.jboss.jmx.adaptor.control.Server.invokeOp(Server.java:223)
org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.invokeOp(HtmlAdaptorServlet.java:262)
org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processRequest(HtmlAdaptorServlet.java:100)
org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doPost(HtmlAdaptorServlet.java:82)
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
3.2.6: javax.servlet.ServletException: Failed to invoke operation
org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.invokeOp(HtmlAdaptorServlet.java:248)
org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processRequest(HtmlAdaptorServlet.java:79)
org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doPost(HtmlAdaptorServlet.java:61)
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75)
root cause
MBeanException: com.koko.KOKOException: Invalid type
Cause: com.koko.KOKOException: Invalid type
org.jboss.mx.server.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.java:91)
org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:64)
org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:197)
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
org.jboss.jmx.adaptor.control.Server.invokeOpByName(Server.java:236)
org.jboss.jmx.adaptor.control.Server.invokeOp(Server.java:202)
org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.invokeOp(HtmlAdaptorServlet.java:241)
org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processRequest(HtmlAdaptorServlet.java:79)
org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doPost(HtmlAdaptorServlet.java:61)
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 7 months
[JBoss JIRA] Created: (JBMESSAGING-681) Consolidate JMS related aspects into one JMS aspect
by Tim Fox (JIRA)
Consolidate JMS related aspects into one JMS aspect
---------------------------------------------------
Key: JBMESSAGING-681
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-681
Project: JBoss Messaging
Issue Type: Task
Reporter: Tim Fox
Assigned To: Tim Fox
Fix For: 1.2.1
Currently, client side JMS functionality is implemented in a set of aspects: SessionAspect, TransactionAspect, FactoryAspect, etc. There seems no good reason to have these as separate aspects since we either provide all the jms functionality or none of it.
Having the functionality distributed across several aspects makes it hard to communicate between them meaning the code is messy and hard to follow.
We should consolidate into one aspect, from which hang a set of classes Session, Connection, Consumer etc which implement the jms functionality in a nice OO way. This will make the code simpler and easier to understand and possibly more performant since we would avoid unnecessary calls through the stack.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 7 months
[JBoss JIRA] Created: (JBMESSAGING-884) HTTP transport barfs in stress tests with read timed out
by Tim Fox (JIRA)
HTTP transport barfs in stress tests with read timed out
--------------------------------------------------------
Key: JBMESSAGING-884
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-884
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.2.0.CR1
Reporter: Tim Fox
Assigned To: Tim Fox
Fix For: 1.2.0.GA
When running the stress tests. The HTTP transport intermittently barfs with:
Caused by: org.jboss.remoting.CannotConnectException: Can not connect http client invoker.
at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:327)
at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:133)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
at org.jboss.remoting.Client.invoke(Client.java:1538)
at org.jboss.remoting.Client.invoke(Client.java:527)
at org.jboss.remoting.Client.invoke(Client.java:515)
at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:182)
... 19 more
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:256)
at java.io.BufferedInputStream.read(BufferedInputStream.java:313)
at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:606)
at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:554)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:939)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:367)
at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:274)
... 25 more
This only occurs under high load.
I suspect the server side tomcat server is having problems dealing with so many concurrent poll requests and times them out.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 7 months
[JBoss JIRA] Created: (EJBTHREE-790) Include partition name in cluster name of caches
by Ortwin Glück (JIRA)
Include partition name in cluster name of caches
------------------------------------------------
Key: EJBTHREE-790
URL: http://jira.jboss.com/jira/browse/EJBTHREE-790
Project: EJB 3.0
Issue Type: Bug
Components: Clustering
Affects Versions: EJB 3.0 RC8 - FD
Reporter: Ortwin Glück
For ejb3-entity-cache-service.xml and ejb3-clustered-sfsbcache-service.xml the ClusterName should include the partition name. Here is why:
We have 3 test instances and the two production cluster nodes within the same subnet (VLAN). The test instances have unique partition names (TEST1, TEST2, TEST3) and the production nodes share a common partition name (PROD). In the default configuration all five nodes would form a cluster for the entity and SFSB clusters. This would severely disrupt data consistency! We have solved this by including the partition name in the cluster name in the cache MBeans:
<attribute name="ClusterName">EJB3-entity-cache-${jboss.partition.name:DefaultPartition}</attribute>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 7 months