September 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-840) Common test suite

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-840: ------------------------------------- Summary: Common test suite Key: JBJCA-840 URL: https://issues.jboss.org/browse/JBJCA-840 Project: IronJacamar Issue Type: Task Components: Common Reporter: Jesper Pedersen Assignee: Vladimir Rastseluev Fix For: 1.1.0.Beta2 * Clean up common/ test suite for duplicated tests * Improve code coverage, especially for resource adapter v1.0 * Remove incorrect DTD tests for v1.5 and v1.6 * Give descriptive names for test classes and resources -- 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

11 years, 9 months

2
2
0 / 0

[JBoss JIRA] (AS7-4249) Inhereted start/stop methods are not invoked on a POJO

by Ivo Studensky (JIRA)

Ivo Studensky created AS7-4249: ---------------------------------- Summary: Inhereted start/stop methods are not invoked on a POJO Key: AS7-4249 URL: https://issues.jboss.org/browse/AS7-4249 Project: Application Server 7 Issue Type: Bug Components: POJO Affects Versions: 7.1.1.Final Reporter: Ivo Studensky Assignee: Ales Justin Fix For: 7.1.2.Final Let's say we have a POJO A which extends a class B. The start/stop methods are defined in the class B. In the jboss-beans.xml file is something like this: <bean name="A" class="blah.blah.A"/> Then, only the constructor of A is invoked by AS7, but no invocation of start/stop methods occur. The start/stop methods are invoked only if they are directly defined in A. -- 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

11 years, 9 months

3
4
0 / 0

[JBoss JIRA] (AS7-5369) Allow direct text value in parameter element.

by Tomaz Cerar (JIRA)

Tomaz Cerar created AS7-5369: -------------------------------- Summary: Allow direct text value in parameter element. Key: AS7-5369 URL: https://issues.jboss.org/browse/AS7-5369 Project: Application Server 7 Issue Type: Bug Components: POJO Affects Versions: 7.1.1.Final Reporter: Tomaz Cerar Assignee: Ales Justin Fix For: 7.1.3.Final (EAP), 7.1.2.Final (EAP) pojo subsystem should allow both formats for defining paramters currently only second format is accepted {noformat} <bean name="ParamTextValue" class="org.jboss.as.test.integration.pojo.support.TInjectee"> <constructor> <parameter>Wazup, </parameter> </constructor> <install method="sayHello"> <parameter><value>POJO subsystem!</value></parameter> </install> </bean> {nofomrat} -- 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

11 years, 9 months

2
4
0 / 0

[JBoss JIRA] (AS7-5521) CLONE - Warn "IllegalStateException: channel is not connected" on clean shutdown

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-5521: ----------------------------------- Summary: CLONE - Warn "IllegalStateException: channel is not connected" on clean shutdown Key: AS7-5521 URL: https://issues.jboss.org/browse/AS7-5521 Project: Application Server 7 Issue Type: Bug Components: Clustering Reporter: Radoslav Husar Assignee: Paul Ferraro Fix For: 7.1.3.Final (EAP) The current fix in for AS7-5442 doesn't result in a timeout exception, Infinispan now checks whether channel is open however results in a WARN message. Looks like AS is closing the channel before the cache is stopped. {noformat} [JBossINF] 06:25:23,758 INFO [org.jboss.as.clustering.infinispan] JBAS010282: Stopped default-host/clusterbench cache from web container [JBossINF] 06:25:23,767 INFO [org.jboss.as.server.deployment] JBAS015877: Stopped deployment clusterbench-ee6-ejb.jar in 1061ms [JBossINF] 06:25:23,765 WARN [org.infinispan.cacheviews.CacheViewsManagerImpl] ISPN000169: Error committing cache view 5 for cache default-host/clusterbench: org.infinispan.CacheException: java.lang.IllegalStateException: channel is not connected [JBossINF] at org.infinispan.util.Util.rewrapAsCacheException(Util.java:526) [infinispan-core-5.1.7-SNAPSHOT.jar:5.1.7-SNAPSHOT] [JBossINF] at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.invokeRemoteCommands(CommandAwareRpcDispatcher.java:139) [infinispan-core-5.1.7-SNAPSHOT.jar:5.1.7-SNAPSHOT] [JBossINF] at org.infinispan.remoting.transport.jgroups.JGroupsTransport.invokeRemotely(JGroupsTransport.java:492) [infinispan-core-5.1.7-SNAPSHOT.jar:5.1.7-SNAPSHOT] [JBossINF] at org.infinispan.cacheviews.CacheViewsManagerImpl.clusterCommitView(CacheViewsManagerImpl.java:378) [infinispan-core-5.1.7-SNAPSHOT.jar:5.1.7-SNAPSHOT] [JBossINF] at org.infinispan.cacheviews.CacheViewsManagerImpl.clusterInstallView(CacheViewsManagerImpl.java:272) [infinispan-core-5.1.7-SNAPSHOT.jar:5.1.7-SNAPSHOT] [JBossINF] at org.infinispan.cacheviews.CacheViewsManagerImpl$ViewInstallationTask.call(CacheViewsManagerImpl.java:894) [infinispan-core-5.1.7-SNAPSHOT.jar:5.1.7-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] [JBossINF] Caused by: java.lang.IllegalStateException: channel is not connected [JBossINF] at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.down(MessageDispatcher.java:619) [jgroups-3.0.14.Final.jar:3.0.14.Final] [JBossINF] at org.jgroups.blocks.RequestCorrelator.sendUnicastRequest(RequestCorrelator.java:193) [jgroups-3.0.14.Final.jar:3.0.14.Final] [JBossINF] at org.jgroups.blocks.UnicastRequest.sendRequest(UnicastRequest.java:44) [jgroups-3.0.14.Final.jar:3.0.14.Final] [JBossINF] at org.jgroups.blocks.Request.execute(Request.java:83) [jgroups-3.0.14.Final.jar:3.0.14.Final] [JBossINF] at org.jgroups.blocks.MessageDispatcher.sendMessageWithFuture(MessageDispatcher.java:419) [jgroups-3.0.14.Final.jar:3.0.14.Final] [JBossINF] at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.processCalls(CommandAwareRpcDispatcher.java:329) [infinispan-core-5.1.7-SNAPSHOT.jar:5.1.7-SNAPSHOT] [JBossINF] at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.invokeRemoteCommands(CommandAwareRpcDispatcher.java:132) [infinispan-core-5.1.7-SNAPSHOT.jar:5.1.7-SNAPSHOT] [JBossINF] ... 9 more [JBossINF] [JBossINF] 06:25:23,768 INFO [org.jboss.as.server.deployment] JBAS015877: Stopped deployment clusterbench-ee6-web-granular.war in 1062ms [JBossINF] 06:25:23,769 INFO [org.jboss.as.server.deployment] JBAS015877: Stopped deployment clusterbench-ee6-web.war in 1063ms [JBossINF] 06:25:23,770 INFO [org.jboss.as.server.deployment] JBAS015877: Stopped deployment clusterbench-ee6.ear in 1076ms [JBossINF] 06:25:24,128 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] ISPN000082: Stopping the RpcDispatcher [JBossINF] 06:25:24,132 INFO [org.jboss.as] JBAS015950: JBoss AS 7.1.3.Final-SNAPSHOT "Arges" stopped in 1337ms {noformat} -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-5381) CLONE - "IllegalStateException: repl: Received prepare cache view request, but we are not a member"

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/AS7-5381?page=com.atlassian.jira.plugin.s... ] Radoslav Husar updated AS7-5381: -------------------------------- Fix Version/s: 7.2.0.Alpha1 > CLONE - "IllegalStateException: repl: Received prepare cache view request, but we are not a member" > --------------------------------------------------------------------------------------------------- > > Key: AS7-5381 > URL: https://issues.jboss.org/browse/AS7-5381 > Project: Application Server 7 > Issue Type: Bug > Components: Clustering > Environment: affected 6.0.1 DR1 CI build > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Blocker > Labels: as713tracking, eap601candidate > Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 > > > Track on JBPAPP-9658. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-5381) CLONE - "IllegalStateException: repl: Received prepare cache view request, but we are not a member"

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/AS7-5381?page=com.atlassian.jira.plugin.s... ] Radoslav Husar resolved AS7-5381. --------------------------------- Assignee: Radoslav Husar (was: Paul Ferraro) Resolution: Done Resolved with AS7-5478 & AS7-5398. > CLONE - "IllegalStateException: repl: Received prepare cache view request, but we are not a member" > --------------------------------------------------------------------------------------------------- > > Key: AS7-5381 > URL: https://issues.jboss.org/browse/AS7-5381 > Project: Application Server 7 > Issue Type: Bug > Components: Clustering > Environment: affected 6.0.1 DR1 CI build > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Blocker > Labels: as713tracking, eap601candidate > Fix For: 7.1.3.Final (EAP) > > > Track on JBPAPP-9658. -- 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

11 years, 9 months

1
0
0 / 0

[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

11 years, 9 months

2
4
0 / 0

[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

11 years, 9 months

1
0
0 / 0

[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

11 years, 9 months

1
0
0 / 0

[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

11 years, 9 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2012