[JBoss JIRA] (RF-13250) Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final
by Milo van der Zee (JIRA)
[ https://issues.jboss.org/browse/RF-13250?page=com.atlassian.jira.plugin.s... ]
Milo van der Zee commented on RF-13250:
---------------------------------------
Hello,
Neither of those parameters are set in my web.xml.
I do see that I get spikes in the threadcount but that does not seem to block the system. Normally around 280 live threads with spikes to 3100. The problem in indeed in the OOME's.
> Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final
> --------------------------------------------------------------
>
> Key: RF-13250
> URL: https://issues.jboss.org/browse/RF-13250
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.4
> Environment: Gentoo Linux, Tomcat 7.0.39, MyFaces 2.1.12, Tomahawk 1.1.14, RichFaces 4.3.4, APR 1.4.5
> Reporter: Milo van der Zee
> Assignee: Pavol Pitonak
> Labels: memoryleak
>
> Hello,
> I did an upgrade from RF 4.3.3.Final to 4.3.4.Final and the application started to crash with 'Out Off Memory' errors. I changed the POM back to 4.3.3.Final and the problem is gone.
> I also started seeing this message lot's of times:
> {{WARN org.atmosphere.cpr.AtmosphereResponse - Committed error code 400}}
> I don't know if that has anything to do with the error. I set {{org.atmosphere.cpr.sessionSupport}} to {{true}} and I did not see the message again. But still the application went out-of-memory.
> In the crashed system heap dump I see a lot of:
> - AtomicBoolean (751.000, 15.0MB)
> - ConcurrentLinkedQueue
> - AtmospereRequest$Builder (60.042, 13.8MB)
> To me it looks like it has something to do with Atmosphere. Any ideas?
> Thanks,
> Milo van der Zee
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (RF-13250) Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13250?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak edited comment on RF-13250 at 10/16/13 9:43 AM:
--------------------------------------------------------------
Hi [~MilovdZee],
do you have org.richfaces.push.session.maxInactiveInterval and org.atmosphere.cpr.CometSupport.maxInactiveActivity context parameters set in your web.xml?
I saw OOME in my use-case but it failed because it couldn't create new native thread which isn't a problem described in this issue, is it? Am I correct that your application fills the whole heap?
How long does it take to get OOME? I.e. how fast will you get to the point of "extreme memory usage"?
was (Author: ppitonak):
Hi [~MilovdZee],
do you have org.richfaces.push.session.maxInactiveInterval and org.atmosphere.cpr.CometSupport.maxInactiveActivity context parameters set in your web.xml?
I saw OOME in my use-case but it failed because it couldn't create new native thread which isn't a problem described in this issue, is it? Am I correct that your application fills the whole heap?
> Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final
> --------------------------------------------------------------
>
> Key: RF-13250
> URL: https://issues.jboss.org/browse/RF-13250
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.4
> Environment: Gentoo Linux, Tomcat 7.0.39, MyFaces 2.1.12, Tomahawk 1.1.14, RichFaces 4.3.4, APR 1.4.5
> Reporter: Milo van der Zee
> Assignee: Pavol Pitonak
> Labels: memoryleak
>
> Hello,
> I did an upgrade from RF 4.3.3.Final to 4.3.4.Final and the application started to crash with 'Out Off Memory' errors. I changed the POM back to 4.3.3.Final and the problem is gone.
> I also started seeing this message lot's of times:
> {{WARN org.atmosphere.cpr.AtmosphereResponse - Committed error code 400}}
> I don't know if that has anything to do with the error. I set {{org.atmosphere.cpr.sessionSupport}} to {{true}} and I did not see the message again. But still the application went out-of-memory.
> In the crashed system heap dump I see a lot of:
> - AtomicBoolean (751.000, 15.0MB)
> - ConcurrentLinkedQueue
> - AtmospereRequest$Builder (60.042, 13.8MB)
> To me it looks like it has something to do with Atmosphere. Any ideas?
> Thanks,
> Milo van der Zee
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (RF-12694) <rich:dropDownMenu> throwing a warning: "Cannot set header. Response already committed."
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-12694?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak reassigned RF-12694:
----------------------------------
Assignee: Juraj Húska (was: Pavol Pitonak)
> <rich:dropDownMenu> throwing a warning: "Cannot set header. Response already committed."
> ----------------------------------------------------------------------------------------
>
> Key: RF-12694
> URL: https://issues.jboss.org/browse/RF-12694
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-menu
> Affects Versions: 4.2.3.Final
> Environment: Tested in Galssfish3.1 and WAS8
> Reporter: Srinivas Reddy Malipeddi
> Assignee: Juraj Húska
> Priority: Minor
> Labels: richfaces, waiting_on_user
>
> When rich component like <rich:dropDownMenu is used, throwing warning"
> {quote}
> com.ibm.ws.webcontainer.srt.SRTServletResponse setIntHeader SRVE8094W: WARNING: Cannot set header. Response already committed.
> {quote}
> Project details: JSF2.0, Myfaces implementation, richfaces 4.2.3 jars
> My project have only one page index.xhtml with one component like below. If richfaces component is not used then the warning is not coming.
> {code:title=index.xhtml}
> <?xml version="1.0" encoding="UTF-8" ?>
> <ui:composition xmlns="http://www.w3.org/1999/xhtml"
> xmlns:ui="http://java.sun.com/jsf/facelets"
> xmlns:f="http://java.sun.com/jsf/core"
> xmlns:h="http://java.sun.com/jsf/html"
> xmlns:rich="http://richfaces.org/rich">
> <h:head>
>
> </h:head>
> <h:body>
> <rich:dropDownMenu label="IT Asset">
> <rich:menuItem label="Search" />
> <rich:menuItem label="Create" />
> </rich:dropDownMenu>
> </h:body>
> </ui:composition>
> {code}
> {code:title=Web.xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <web-app id="WebApp_ID" version="3.0"
> xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd">
> <display-name>TestWeb</display-name>
> <context-param>
> <description>
> The location where state information is saved.
> Valid values are 'server' (typically saved in HttpSession) and 'client' (typically
> saved as a hidden field in the form.
> Default is server.</description>
> <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
> <param-value>server</param-value>
> </context-param>
> <context-param>
> <description>
> Comma-delimited list of context-relative resource paths under which the JSF implementation
> will look for application configuration resources, before loading a configuration resource
> named /WEB-INF/faces-config.xml (if such a resource exists).</description>
> <param-name>javax.faces.CONFIG_FILES</param-name>
> <param-value></param-value>
> </context-param>
> <context-param>
> <description>
> The default suffix for extension-mapped resources that contain JSF components.
> Default is '.jsp'.</description>
> <param-name>javax.faces.DEFAULT_SUFFIX</param-name>
> <param-value>.xhtml</param-value>
> </context-param>
> <context-param>
> <description>
> A human readable string describing where this particular JSF application is
> in the software development lifecycle.
> Valid values are 'Development', 'UnitTest', 'SystemTest' and 'Production'.
> Default is 'Production'.
> This parameter is not available in JSF 1.x.</description>
> <param-name>javax.faces.PROJECT_STAGE</param-name>
> <param-value>Development</param-value>
> </context-param>
> <context-param>
> <description>
> Monitors Faces JSP files for modifications and synchronizes a running server with
> the changes without restarting the server. If this parameter is set to false or
> removed from the deployment descriptor, any changes made to Faces JSP files may
> not be seen by the server until it is restarted. This parameter is usually set
> to true while the Faces JSP files are being developed and debugged in order to
> improve the performance of the development environment.</description>
> <param-name>com.ibm.ws.jsf.JSP_UPDATE_CHECK</param-name>
> <param-value>true</param-value>
> </context-param>
> <context-param>
> <description>
> Load JSF runtime when the application server starts up. If this parameter is set to false or removed,
> JSF runtime will be loaded and initialized when the first JSF request is processed.
> This may disable custom JSF extensions, such as factories defined in the project.</description>
> <param-name>com.ibm.ws.jsf.LOAD_FACES_CONFIG_AT_STARTUP</param-name>
> <param-value>true</param-value>
> </context-param>
>
> <servlet>
> <servlet-name>Faces Servlet</servlet-name>
> <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
> <load-on-startup>-1</load-on-startup>
> <enabled>true</enabled>
> <async-supported>false</async-supported>
> </servlet>
> <servlet-mapping>
> <servlet-name>Faces Servlet</servlet-name>
> <url-pattern>*.xhtml</url-pattern>
> </servlet-mapping>
> <servlet-mapping>
> <servlet-name>Faces Servlet</servlet-name>
> <url-pattern>
> *.faces</url-pattern>
> </servlet-mapping>
> <servlet-mapping>
> <servlet-name>Faces Servlet</servlet-name>
> <url-pattern>
> /faces/*</url-pattern>
> </servlet-mapping>
> <welcome-file-list>
> <welcome-file>index.xhtml</welcome-file>
> </welcome-file-list>
> </web-app>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (RF-13266) mediaOutput not working anymore on Glassfish3
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13266?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak reassigned RF-13266:
----------------------------------
Assignee: Matej Novotny (was: Pavol Pitonak)
> mediaOutput not working anymore on Glassfish3
> ---------------------------------------------
>
> Key: RF-13266
> URL: https://issues.jboss.org/browse/RF-13266
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.4
> Environment: Glassfish 3.1.2.2 patched with Weld 1.1.14 (the problem appears also on earlier Weld builds) and JSF 2.1.26 and JDK 1.7.0_45
> Reporter: Fab Mars
> Assignee: Matej Novotny
> Labels: glassfish_v3, mediaOutput
>
> This is a followup to https://issues.jboss.org/browse/RF-13098 focusing on Glassfish3.
> I have 2 mediaOutput in my code, none works.
> The first one passes a Long as the value to the createContent method and the expected output is a PDF. I get
> SEVERE: Input error for deserialize data java.io.InvalidClassException: Unauthorized deserialization attempt; org.jboss.weld.util.el.ForwardingMethodExpression
> The second one passes an array of 3 bytes (a color code) and the expected result is an image. I get
> SEVERE: Input error for deserialize data java.io.InvalidClassException: Unauthorized deserialization attempt; [B
> I'm preparing a reproducer on github and will share the url in the next comment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (RF-13177) rich:extendedDataTable scrolling broken on OS-X
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13177?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak reassigned RF-13177:
----------------------------------
Assignee: Matej Novotny (was: Pavol Pitonak)
> rich:extendedDataTable scrolling broken on OS-X
> -----------------------------------------------
>
> Key: RF-13177
> URL: https://issues.jboss.org/browse/RF-13177
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: base functionality
> Affects Versions: 4.3.3
> Environment: OS-X 10.8.3, Chrome 29.0.1547.62 or Safari or Firefox
> Reporter: Immo Benjes
> Assignee: Matej Novotny
> Labels: osx
> Fix For: 5-Tracking
>
>
> In OS-X scrolling can be done by using two fingers on the touchpad. However this does not work for horizontal scrolling on the rich:extendedDataTable.
> You can scroll vertically but not horizontally.
> The horizontal scrolling with two fingers only works when the mouse is over the actual scrollbar!
> I had a look at the actual html code and it looks like the header, table content and scroller are generated as independent tables. The div that contains the table content (class rf-edt-cnt) has overflow:hidden; set. If you change that to overflow: auto you get the two finger scrolling over the content of the table, however the header and original scrollbar isn't scrolling. Would it be possible to hide the original scroller and synchronize the header (and footer?) when scrolling the content?
> In OS-X you have the option to only show the scrollbar when you scroll. This is quite nice as it gives you a bit more space. However in this case you cannot scroll with the extendedDataTable at all! The scrollbar of the extendedDataTable is hidden in this case and the height/width of the div containing the scrollbar is 0, so you can't navigate over it to enable the scrolling. That basically gives you no way of scrolling!
> See https://community.jboss.org/thread/231502
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (RF-13259) DataTable rowClasses with columnGroup is not rendered
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13259?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak reassigned RF-13259:
----------------------------------
Assignee: Juraj Húska (was: Pavol Pitonak)
> DataTable rowClasses with columnGroup is not rendered
> -----------------------------------------------------
>
> Key: RF-13259
> URL: https://issues.jboss.org/browse/RF-13259
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component
> Affects Versions: 4.3.0.Final
> Environment: java 6
> Reporter: Luca Stancapiano
> Assignee: Juraj Húska
>
> This is my page:
> {code}
> <rich:dataTable id="postsList" value="#{topic.threadsDataModel}" rowClasses="oddRow,noStyle">
> <rich:columnGroup>
> <rich:column styleClass="forumpostleftcolumn">...</rich:column>
> <rich:column>...</rich:column>
> <rich:columnGroup>
> <rich:columnGroup>
> <rich:column styleClass="forumpostleftcolumn">...</rich:column>
> <rich:column">...</rich:column>
> <rich:columnGroup>
> </rich:dataTable>
> {code}
> I expect that the styes oddRow and noStyle are rendered inside the rows but nothing happens. Seems that rowClasses attribute cannot be used with rich:columnGroup.
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (RF-13250) Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13250?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak commented on RF-13250:
------------------------------------
Hi [~MilovdZee],
do you have org.richfaces.push.session.maxInactiveInterval and org.atmosphere.cpr.CometSupport.maxInactiveActivity context parameters set in your web.xml?
I saw OOME in my use-case but it failed because it couldn't create new native thread which isn't a problem described in this issue, is it? Am I correct that your application fills the whole heap?
> Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final
> --------------------------------------------------------------
>
> Key: RF-13250
> URL: https://issues.jboss.org/browse/RF-13250
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.4
> Environment: Gentoo Linux, Tomcat 7.0.39, MyFaces 2.1.12, Tomahawk 1.1.14, RichFaces 4.3.4, APR 1.4.5
> Reporter: Milo van der Zee
> Assignee: Pavol Pitonak
> Labels: memoryleak
>
> Hello,
> I did an upgrade from RF 4.3.3.Final to 4.3.4.Final and the application started to crash with 'Out Off Memory' errors. I changed the POM back to 4.3.3.Final and the problem is gone.
> I also started seeing this message lot's of times:
> {{WARN org.atmosphere.cpr.AtmosphereResponse - Committed error code 400}}
> I don't know if that has anything to do with the error. I set {{org.atmosphere.cpr.sessionSupport}} to {{true}} and I did not see the message again. But still the application went out-of-memory.
> In the crashed system heap dump I see a lot of:
> - AtomicBoolean (751.000, 15.0MB)
> - ConcurrentLinkedQueue
> - AtmospereRequest$Builder (60.042, 13.8MB)
> To me it looks like it has something to do with Atmosphere. Any ideas?
> Thanks,
> Milo van der Zee
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (RF-13098) Regression: mediaOutput broken for CDI MediaData beans
by Fab Mars (JIRA)
[ https://issues.jboss.org/browse/RF-13098?page=com.atlassian.jira.plugin.s... ]
Fab Mars commented on RF-13098:
-------------------------------
Done. RF-13268
> Regression: mediaOutput broken for CDI MediaData beans
> ------------------------------------------------------
>
> Key: RF-13098
> URL: https://issues.jboss.org/browse/RF-13098
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.3.3
> Reporter: Marek Schmidt
> Assignee: Brian Leathem
> Labels: regression
> Fix For: 4.3.4, 5.0.0.Alpha2
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> https://issues.jboss.org/browse/RF-13089 introduced a regression for a4j:mediaOutput component
> Having a
> {code}
> <a4j:mediaOutput element="img" cacheable="true" session="true" createContent="#{mediaBean.paint}" value="#{mediaData}" mimeType="image/jpeg"/>
> {code}
> with mediaData being a CDI bean, e.g.
> {code}
> @javax.inject.Named("mediaData")
> @javax.enterprise.context.RequestScoped
> public class MediaData implements Serializable
> {code}
> the following exception occurs:
> {code}10:39:27,997 SEVERE [org.richfaces.log.Resource] (http-/127.0.0.1:8080-1) Input error for deserialize data : java.io.InvalidClassException: Unauthorized deserialization attempt; org.jboss.weld.bean.proxy.util.SerializableClientProxy
> at org.richfaces.util.LookAheadObjectInputStream.resolveClass(LookAheadObjectInputStream.java:93) [richfaces-core-impl-4.3.3.Final.jar:4.3.3.Final]
> at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1610) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1515) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1769) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1989) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1913) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1796) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1704) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1342) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) [rt.jar:1.7.0_25]
> at org.richfaces.util.Util.decodeObjectData(Util.java:237) [richfaces-core-impl-4.3.3.Final.jar:4.3.3.Final]
> at org.richfaces.resource.DefaultCodecResourceRequestData.getData(DefaultCodecResourceRequestData.java:97) [richfaces-core-impl-4.3.3.Final.jar:4.3.3.Final]
> at org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:337) [richfaces-core-impl-4.3.3.Final.jar:4.3.3.Final]
> at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:156) [richfaces-core-impl-4.3.3.Final.jar:4.3.3.Final]
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:591) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
