[JBoss JIRA] (AS7-5442) Graceful shutdown consistently results in "ISPN000172: Failed to prepare view CacheView... java.util.concurrent.TimeoutException"
by Radoslav Husar (JIRA)
Radoslav Husar created AS7-5442:
-----------------------------------
Summary: Graceful shutdown consistently results in "ISPN000172: Failed to prepare view CacheView... java.util.concurrent.TimeoutException"
Key: AS7-5442
URL: https://issues.jboss.org/browse/AS7-5442
Project: Application Server 7
Issue Type: Bug
Components: Clustering
Reporter: Radoslav Husar
Assignee: Paul Ferraro
Fix For: 7.1.3.Final (EAP)
Testing Dan's and Bela's fixes for AS7-5381 and including Paul's AS code fixes, we are consistently seeing Timeout upon node shutdown.
{noformat}
[JBossINF] 14:22:21,362 ERROR [org.infinispan.cacheviews.CacheViewsManagerImpl] ISPN000172: Failed to prepare view CacheView{viewId=5, members=[perf21/web, perf20/web, perf19/web]} for cache default-host/clusterbench, rolling back to view CacheView{viewId=4, members=[perf18/web, perf21/web, perf20/web, perf19/web]}: java.util.concurrent.TimeoutException
[JBossINF] at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:228) [rt.jar:1.6.0_30]
[JBossINF] at java.util.concurrent.FutureTask.get(FutureTask.java:91) [rt.jar:1.6.0_30]
[JBossINF] at org.infinispan.cacheviews.CacheViewsManagerImpl.clusterPrepareView(CacheViewsManagerImpl.java:319) [infinispan-core.jar:5.1.6-SNAPSHOT]
[JBossINF] at org.infinispan.cacheviews.CacheViewsManagerImpl.clusterInstallView(CacheViewsManagerImpl.java:250) [infinispan-core.jar:5.1.6-SNAPSHOT]
[JBossINF] at org.infinispan.cacheviews.CacheViewsManagerImpl$ViewInstallationTask.call(CacheViewsManagerImpl.java:890) [infinispan-core.jar:5.1.6-SNAPSHOT]
[JBossINF] at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [rt.jar:1.6.0_30]
[JBossINF] at java.util.concurrent.FutureTask.run(FutureTask.java:138) [rt.jar:1.6.0_30]
[JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30]
[JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30]
[JBossINF] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
{noformat}
The server is then shutting down for over a minute (when the TO is reached).
https://issues.jboss.org/browse/JBPAPP-9658?focusedCommentId=12712762&pag...
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Failo...
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Failo...
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Failo...
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Failo...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (AS7-5519) CLONE - Upgrade JGroups to 3.0.14.Final
by Radoslav Husar (JIRA)
Radoslav Husar created AS7-5519:
-----------------------------------
Summary: CLONE - Upgrade JGroups to 3.0.14.Final
Key: AS7-5519
URL: https://issues.jboss.org/browse/AS7-5519
Project: Application Server 7
Issue Type: Component Upgrade
Components: Clustering
Reporter: Radoslav Husar
Assignee: Radoslav Husar
Priority: Blocker
Fix For: 7.1.3.Final (EAP)
JGroups 3.0.12 has a couple fixes (see below) and 3.0.13 has another.
On 20/08/12 11:16, Bela Ban wrote:> FYI,
> contains 2 fixes, one of them [1] seems to fix the issue with AS
> clustering which led to incorrect CacheView installation.
>
>
> [1] https://issues.jboss.org/browse/JGRP-1502
--
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
13 years, 9 months
[JBoss JIRA] (AS7-5518) CLONE - Upgrade Infinispan to 5.1.7.Final
by Radoslav Husar (JIRA)
Radoslav Husar created AS7-5518:
-----------------------------------
Summary: CLONE - Upgrade Infinispan to 5.1.7.Final
Key: AS7-5518
URL: https://issues.jboss.org/browse/AS7-5518
Project: Application Server 7
Issue Type: Component Upgrade
Components: Clustering
Reporter: Radoslav Husar
Assignee: Radoslav Husar
Priority: Blocker
Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1
We will probably need a component upgrade in Infinispan incorporating changes in Dan's branch to resolve JBPAPP-9658/AS7-5381 and possibly AS7-5442.
Last release is 5.1.6.Final.
--
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
13 years, 9 months
[JBoss JIRA] (JBAS-9503) Too many Open files in JBoss AS7
by Suman Alapati (JIRA)
Suman Alapati created JBAS-9503:
-----------------------------------
Summary: Too many Open files in JBoss AS7
Key: JBAS-9503
URL: https://issues.jboss.org/browse/JBAS-9503
Project: Application Server 3 4 5 and 6
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Deployers
Reporter: Suman Alapati
Assignee: Ales Justin
Hi,
I am Using Jboss As-7 as my application server in Linux box at the time of deployment i am getting below stack trace. Can one let me the reason behind of the below Stack Trace :
=========================================================================
Caused by: java.io.FileNotFoundException: /home/appuser/dpc/jbossas7/standalone/tmp/vfs/deploymentca2dd52bc934385/xbean-2.1.0.jar-972256156c28c093/xbean-2.1.0.jar (Too many open files)
at java.io.FileOutputStream.open(Native Method) [rt.jar:1.6.0_22]
at java.io.FileOutputStream.<init>(FileOutputStream.java:209) [rt.jar:1.6.0_22]
at java.io.FileOutputStream.<init>(FileOutputStream.java:160) [rt.jar:1.6.0_22]
at org.jboss.vfs.TempDir.createFile(TempDir.java:93)
at org.jboss.vfs.spi.JavaZipFileSystem.<init>(JavaZipFileSystem.java:83)
at org.jboss.vfs.VFS.mountZip(VFS.java:408)
at org.jboss.vfs.VFS.mountZip(VFS.java:434)
at org.jboss.as.web.deployment.WarStructureDeploymentProcessor.createWebInfLibResources(WarStructureDeploymentProcessor.java:170)
... 8 more
13:48:02,874 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "uisearch.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"uisearch.war\".STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"uisearch.war\".STRUCTURE: Failed to process phase STRUCTURE of deployment \"uisearch.war\""}}
13:48:02,915 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment uisearch.war in 41ms
13:48:02,917 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.deployment.unit."uisearch.war".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."uisearch.war".STRUCTURE: Failed to process phase STRUCTURE of deployment "uisearch.war"
=======================================================================
I am Still Confusing where i am doing wrong . And i would like to know is it because of Jboss or Linux box.
Thanks in Advance,
Suman Alapati.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (AS7-5022) Server sometimes crashes during reload operation
by Jan Martiska (JIRA)
[ https://issues.jboss.org/browse/AS7-5022?page=com.atlassian.jira.plugin.s... ]
Jan Martiska closed AS7-5022.
-----------------------------
> Server sometimes crashes during reload operation
> ------------------------------------------------
>
> Key: AS7-5022
> URL: https://issues.jboss.org/browse/AS7-5022
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi
> Affects Versions: 7.1.2.Final (EAP)
> Reporter: Jan Martiska
> Assignee: Thomas Diesler
> Priority: Critical
>
> After some number of server reloads, next reload fails.. the number seems random, for me it is between 6 and 150.
> this error message pops up during boot:
> {noformat}
> 15:21:05,036 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 53) JBAS014612: Operation ("add") failed - address: ([("subsystem" => "osgi")]): org.jboss.msc.service.DuplicateServiceException: Service jbosgi.integration.PersistentBundlesHandler is already registered
> {noformat}
> This shell script can be used for reproduction:
> {noformat}
> #!/bin/sh
> $JBOSS_HOME/bin/standalone.sh > /dev/null &
> sleep 10
> for i in `seq 1 150`; do
> echo $i
> $JBOSS_HOME/bin/jboss-cli.sh -c --command=:reload
> sleep 4
> tail --lines=50 $JBOSS_HOME/standalone/log/server.log | grep ERROR
> done
> {noformat}
> Testing environment> RHEL 5 or 6. This happens both when reloading using jboss-cli.sh and jboss-as-controller-client. It seems it has never happened to me when EAP was running in IPv6 mode (java.net.preferIPv4Stack=false), only IPv4. Affects all standalone profiles. It randomly breaks my admin console testsuite, which uses server reloads quite a lot.
--
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
13 years, 9 months
[JBoss JIRA] (AS7-4167) Admin console: cannot set attribute max-attempts of modcluster subsystem
by Jan Martiska (JIRA)
Jan Martiska created AS7-4167:
---------------------------------
Summary: Admin console: cannot set attribute max-attempts of modcluster subsystem
Key: AS7-4167
URL: https://issues.jboss.org/browse/AS7-4167
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.1.Final
Reporter: Jan Martiska
Assignee: Heiko Braun
Priority: Minor
Under Networking tab of modcluster configuration - property "Max Attempts" cannot be set- console references it as "max-attemps" instead of the correct "max-attempts"
{noformat}
{
"outcome" => "failed",
"result" => {"step-1" => {
"outcome" => "failed",
"failure-description" => "JBAS014792: Unknown attribute max-attemps",
"rolled-back" => true
}},
"failure-description" => {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014792: Unknown attribute max-attemps"}},
"rolled-back" => true,
"response-headers" => {"process-state" => "reload-required"}
}
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (AS7-4166) Admin console: cannot set attribute auto-enable-contexts of modcluster subsystem
by Jan Martiska (JIRA)
Jan Martiska created AS7-4166:
---------------------------------
Summary: Admin console: cannot set attribute auto-enable-contexts of modcluster subsystem
Key: AS7-4166
URL: https://issues.jboss.org/browse/AS7-4166
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.1.Final
Reporter: Jan Martiska
Assignee: Heiko Braun
Priority: Minor
Under Web Contexts tab of modcluster configuration - property "Auto Enable Contexts" cannot be set- console references it as "auto-enableContexts" instead of the correct "auto-enable-contexts"
{noformat}
{
"outcome" => "failed",
"result" => {"step-1" => {
"outcome" => "failed",
"failure-description" => "JBAS014792: Unknown attribute auto-enableContexts",
"rolled-back" => true
}},
"failure-description" => {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014792: Unknown attribute auto-enableContexts"}},
"rolled-back" => true,
"response-headers" => {"process-state" => "reload-required"}
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (JBAS-9512) changed to new version jboss 6.1 from jboss 4.2.2 it is giving exception after deploying my project
by Raghu T (JIRA)
Raghu T created JBAS-9512:
-----------------------------
Summary: changed to new version jboss 6.1 from jboss 4.2.2 it is giving exception after deploying my project
Key: JBAS-9512
URL: https://issues.jboss.org/browse/JBAS-9512
Project: Application Server 3 4 5 and 6
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Deployers
Affects Versions: 6.1.0
Environment: Windows 7 os,64 bit and Java struts platform
Reporter: Raghu T
Assignee: Ales Justin
Fix For: JBossAS-4.2.2.GA
i am getting the following exception ....
Deployment "vfs:///D:/server/jboss-6.1.0.Final/server/default/deploy/MozartCCNewUI.war" is in error due to the following reason(s): org.xml.sax.SAXException: The content of element type "web-app" must match "(icon?,display-name?,description?,distributable?,context-param*,filter*,filter-mapping*,listener*,servlet*,servlet-mapping*,session-config?,mime-mapping*,welcome-file-list?,error-page*,taglib*,resource-env-ref*,resource-ref*,security-constraint*,login-config?,security-role*,env-entry*,ejb-ref*,ejb-local-ref*)". @ vfs:///D:/server/jboss-6.1.0.Final/server/default/deploy/MozartCCNewUI.war/WEB-INF/web.xml[152,11]
this is my web.xml file.....
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app>
<!--
To use non XDoclet filters, create a filters.xml file that
contains the additional filters (eg Sitemesh) and place it in your
project's merge dir. Don't include filter-mappings in this file,
include them in a file called filter-mappings.xml and put that in
the same directory.
-->
<distributable />
<filter>
<filter-name>LoginFilter</filter-name>
<filter-class>
com.zyom.security.LoginMonitorFilter
</filter-class>
</filter>
<filter-mapping>
<filter-name>LoginFilter</filter-name>
<url-pattern>*.do</url-pattern>
</filter-mapping>
<filter-mapping>
<filter-name>LoginFilter</filter-name>
<url-pattern>*.jsp</url-pattern>
</filter-mapping>
<!--
To use non XDoclet filter-mappings, create a filter-mappings.xml file that
contains the additional filter-mappings and place it in your
project's merge dir.
-->
<!--
To use non XDoclet listeners, create a listeners.xml file that
contains the additional listeners and place it in your
project's merge dir.
-->
<servlet>
<servlet-name>action</servlet-name>
<servlet-class>
org.apache.struts.action.ActionServlet
</servlet-class>
<init-param>
<param-name>config</param-name>
<param-value>/WEB-INF/struts-config.xml</param-value>
</init-param>
<init-param>
<param-name>debug</param-name>
<param-value>2</param-value>
</init-param>
<init-param>
<param-name>detail</param-name>
<param-value>2</param-value>
</init-param>
<load-on-startup>2</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>action</servlet-name>
<url-pattern>*.do</url-pattern>
</servlet-mapping>
<servlet>
<servlet-name>CewolfServlet</servlet-name>
<servlet-class>de.laures.cewolf.CewolfRenderer</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>CewolfServlet</servlet-name>
<url-pattern>/cewolf/*</url-pattern>
</servlet-mapping>
<session-config>
<session-timeout>30</session-timeout>
</session-config>
<listener>
<listener-class>com.zyom.reuse.util.SessionListener</listener-class>
</listener>
<!--
To specify mime mappings, create a file named mime-mappings.xml, put it in your project's mergedir.
Organize mime-mappings.xml following this DTD slice:
<!ELEMENT mime-mapping (extension, mime-type)>
-->
<!-- The Welcome File List -->
<welcome-file-list>
<welcome-file>/pages/MozartCostLoginAdmin.jsp</welcome-file>
</welcome-file-list>
<!--
To specify error pages, create a file named error-pages.xml, put it in your project's mergedir.
Organize error-pages.xml following this DTD slice:
<!ELEMENT error-page ((error-code | exception-type), location)>
-->
<taglib>
<taglib-uri>/tags/struts-bean</taglib-uri>
<taglib-location>/WEB-INF/struts-bean.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>/tags/struts-html</taglib-uri>
<taglib-location>/WEB-INF/struts-html.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>/tags/struts-logic</taglib-uri>
<taglib-location>/WEB-INF/struts-logic.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>/tags/struts-nested</taglib-uri>
<taglib-location>/WEB-INF/struts-nested.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>/tags/struts-tiles</taglib-uri>
<taglib-location>/WEB-INF/struts-tiles.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>/tags/pagetaglib</taglib-uri>
<taglib-location>/WEB-INF/pagetaglib.tld</taglib-location>
</taglib>
<!--
To set up security settings for your web app, create a file named web-security.xml, put it in your project's mergedir.
Organize web-security.xml following this DTD slice:
<!ELEMENT security-constraint (display-name?, web-resource-collection+, auth-constraint?, user-data-constraint?)>
<!ELEMENT web-resource-collection (web-resource-name, description?, url-pattern*, http-method*)>
<!ELEMENT web-resource-name (#PCDATA)>
<!ELEMENT url-pattern (#PCDATA)>
<!ELEMENT http-method (#PCDATA)>
<!ELEMENT user-data-constraint (description?, transport-guarantee)>
<!ELEMENT transport-guarantee (#PCDATA)>
<!ELEMENT login-config (auth-method?, realm-name?, form-login-config?)>
<!ELEMENT auth-method (#PCDATA)>
<!ELEMENT realm-name (#PCDATA)>
<!ELEMENT form-login-config (form-login-page, form-error-page)>
<!ELEMENT form-login-page (#PCDATA)>
<!ELEMENT form-error-page (#PCDATA)>
-->
</web-app>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months