July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8966) Seam 2 Reexplode causes full undeploy + deploy on AS6

by Cody Lerum (JIRA)

Seam 2 Reexplode causes full undeploy + deploy on AS6 ----------------------------------------------------- Key: JBAS-8966 URL: https://issues.jboss.org/browse/JBAS-8966 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.0.0.Final Environment: JBoss AS 6 Final, Seam 2.2.1 Reporter: Cody Lerum After upgrading an existing seam 2 project which runs on AS 4.2.3 to run on AS 6 I'm seeing an issue where if I run an reexplode from the seam-gen ant build the application server does a full undeploy and then deploy of the app. This kills any development as I should be able to edit an jsf xhtml page and have that reflected immediately without having to redeploy. Appears the redeploy scanner is too aggressive or seam-gen is copying over something that worked for reexplode in AS4 but not in AS6 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-2385) A BestSolutionChangedEvent should be fired when a StartingSolutionInitializer generates a new best solution

by Geoffrey De Smet (JIRA)

A BestSolutionChangedEvent should be fired when a StartingSolutionInitializer generates a new best solution ----------------------------------------------------------------------------------------------------------- Key: JBRULES-2385 URL: https://jira.jboss.org/jira/browse/JBRULES-2385 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-solver Affects Versions: 5.1.0.M1 Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet try examination example with exam set 2: after initialization the score in the dialog is stale -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-541) Thread pools in transport protocols not using daemon threads

by Paul Ferraro (JIRA)

Thread pools in transport protocols not using daemon threads ------------------------------------------------------------ Key: JGRP-541 URL: http://jira.jboss.com/jira/browse/JGRP-541 Project: JGroups Issue Type: Bug Affects Versions: 2.5 Reporter: Paul Ferraro Assigned To: Bela Ban Priority: Minor The ThreadFactory used by the ThreadPoolExecutors (for both regular and OOB messages) in org.jgroups.protocols.TP does not create daemon threads. During runtime the JVM will resist exiting unless the channel is explicitly shutdown. -- 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

14 years

4
7
0 / 0

[JBoss JIRA] Created: (AS7-901) Figure out why the JPDA remote debugger crashes in domain mode

by Heiko Braun (JIRA)

Figure out why the JPDA remote debugger crashes in domain mode -------------------------------------------------------------- Key: AS7-901 URL: https://issues.jboss.org/browse/AS7-901 Project: Application Server 7 Issue Type: Task Reporter: Heiko Braun -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

5
8
0 / 0

[JBoss JIRA] Created: (JBRULES-3080) Compilation of rules should fail when is not used quotes in a String attribute

by Alessandro Lazarotti (JIRA)

Compilation of rules should fail when is not used quotes in a String attribute ------------------------------------------------------------------------------ Key: JBRULES-3080 URL: https://issues.jboss.org/browse/JBRULES-3080 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.1.1.FINAL Reporter: Alessandro Lazarotti Assignee: Mark Proctor It is mandatory that Strings are placed between quotes. Guvnor/BRMS or DRL's plain text should fail if you forgot the quotes but currently it just fails the build if you put a value different of numerics: f : Fact( stringAttribute == ab ) It will fail. The same must occur for: f : Fact( stringAttribute == 12 ) ... but it does not happen and the rule is never matched. It is very important keep the same behaviour for both cases. The rule's author needs to know about it before the package is built. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

6
28
0 / 0

[JBoss JIRA] Created: (JBAS-8595) Thread Pooling configuration from jmx-console doesn't update WorkerStack size. Size remains 200 always.

by Nishant Parikh (JIRA)

Thread Pooling configuration from jmx-console doesn't update WorkerStack size. Size remains 200 always. ------------------------------------------------------------------------------------------------------- Key: JBAS-8595 URL: https://jira.jboss.org/browse/JBAS-8595 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX/Web Console Affects Versions: JBossAS-5.0.1.GA Environment: Windows/Linux, JDK1.5, RAM 2GB, Processor 3GHz, Intel Core Due CPU Reporter: Nishant Parikh Assignee: Darran Lofthouse Priority: Critical When we fire concurrent request more than 200, let's say 200+x (With maxThreads specified 1000 from jmx/web console), Everything works fine but after few seconds x NUMBER OF THREADS GETS BUSY and they never get free. On server log we are getting below ArrayIndexOutOfBoundsException. Exception in thread "http-192.168.1.166-8080-4" java.lang.ArrayIndexOutOfBoundsException: 200 at org.apache.tomcat.util.net.JIoEndpoint$WorkerStack.push(JIoEndpoint.java:769) at org.apache.tomcat.util.net.JIoEndpoint.recycleWorkerThread(JIoEndpoint.java:724) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:457) at java.lang.Thread.run(Thread.java:662) Exception in thread "http-192.168.1.166-8080-16" java.lang.ArrayIndexOutOfBoundsException: 201 at org.apache.tomcat.util.net.JIoEndpoint$WorkerStack.push(JIoEndpoint.java:769) at org.apache.tomcat.util.net.JIoEndpoint.recycleWorkerThread(JIoEndpoint.java:724) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:457) at java.lang.Thread.run(Thread.java:662) Exception in thread "http-192.168.1.166-8080-91" java.lang.ArrayIndexOutOfBoundsException: 202 at org.apache.tomcat.util.net.JIoEndpoint$WorkerStack.push(JIoEndpoint.java:769) at org.apache.tomcat.util.net.JIoEndpoint.recycleWorkerThread(JIoEndpoint.java:724) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:457) at java.lang.Thread.run(Thread.java:662) Exception in thread "http-192.168.1.166-8080-98" java.lang.ArrayIndexOutOfBoundsException: 203 at org.apache.tomcat.util.net.JIoEndpoint$WorkerStack.push(JIoEndpoint.java:769) at org.apache.tomcat.util.net.JIoEndpoint.recycleWorkerThread(JIoEndpoint.java:724) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:457) at java.lang.Thread.run(Thread.java:662) 17:08:49,515 ERROR [JIoEndpoint] Error allocating socket processor java.lang.ArrayIndexOutOfBoundsException: 203 at org.apache.tomcat.util.net.JIoEndpoint$WorkerStack.pop(JIoEndpoint.java:778) at org.apache.tomcat.util.net.JIoEndpoint.createWorkerThread(JIoEndpoint.java:661) at org.apache.tomcat.util.net.JIoEndpoint.getWorkerThread(JIoEndpoint.java:702) at org.apache.tomcat.util.net.JIoEndpoint.processSocket(JIoEndpoint.java:737) at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:313) at java.lang.Thread.run(Thread.java:662) 17:08:49,530 ERROR [JIoEndpoint] Error allocating socket processor java.lang.ArrayIndexOutOfBoundsException: 202 at org.apache.tomcat.util.net.JIoEndpoint$WorkerStack.pop(JIoEndpoint.java:778) at org.apache.tomcat.util.net.JIoEndpoint.createWorkerThread(JIoEndpoint.java:661) at org.apache.tomcat.util.net.JIoEndpoint.getWorkerThread(JIoEndpoint.java:702) at org.apache.tomcat.util.net.JIoEndpoint.processSocket(JIoEndpoint.java:737) at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:313) at java.lang.Thread.run(Thread.java:662) 17:08:49,546 ERROR [JIoEndpoint] Error allocating socket processor java.lang.ArrayIndexOutOfBoundsException: 201 at org.apache.tomcat.util.net.JIoEndpoint$WorkerStack.pop(JIoEndpoint.java:778) at org.apache.tomcat.util.net.JIoEndpoint.createWorkerThread(JIoEndpoint.java:661) at org.apache.tomcat.util.net.JIoEndpoint.getWorkerThread(JIoEndpoint.java:702) at org.apache.tomcat.util.net.JIoEndpoint.processSocket(JIoEndpoint.java:737) at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:313) at java.lang.Thread.run(Thread.java:662) 17:08:49,548 ERROR [JIoEndpoint] Error allocating socket processor java.lang.ArrayIndexOutOfBoundsException: 200 at org.apache.tomcat.util.net.JIoEndpoint$WorkerStack.pop(JIoEndpoint.java:778) at org.apache.tomcat.util.net.JIoEndpoint.createWorkerThread(JIoEndpoint.java:661) at org.apache.tomcat.util.net.JIoEndpoint.getWorkerThread(JIoEndpoint.java:702) at org.apache.tomcat.util.net.JIoEndpoint.processSocket(JIoEndpoint.java:737) at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:313) at java.lang.Thread.run(Thread.java:662) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
5
0 / 0

[JBoss JIRA] Created: (AS7-829) make-pristine.sh to reset an AS installation to factory settings

by Bob McWhirter (JIRA)

make-pristine.sh to reset an AS installation to factory settings ---------------------------------------------------------------- Key: AS7-829 URL: https://issues.jboss.org/browse/AS7-829 Project: Application Server 7 Issue Type: Enhancement Reporter: Bob McWhirter Assignee: Jason Greene Not sure how this is better than unzip -q jboss-as-bin.zip, but being able to "reset" the domain and such (and bootstrap logging props) to out-of-the-box settings might be nice. Perhaps a separate script to clean the deployments and content repo. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1744) Create an ivy resolver for maven uniquely versioned snapshots

by Carlo de Wolf (JIRA)

Create an ivy resolver for maven uniquely versioned snapshots ------------------------------------------------------------- Key: EJBTHREE-1744 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1744 Project: EJB 3.0 Issue Type: Feature Request Reporter: Carlo de Wolf Assignee: Carlo de Wolf -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2464) Unexpected test failures on IBM JDK 6

by Lukáš Petrovický (JIRA)

Unexpected test failures on IBM JDK 6 ------------------------------------- Key: JBRULES-2464 URL: https://jira.jboss.org/jira/browse/JBRULES-2464 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core, drools-testing Reporter: Lukáš Petrovický Assignee: Mark Proctor See BRMS-287. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
13
0 / 0

[JBoss JIRA] Created: (JBAS-8366) Failure to deploy a war file with JBoss 5.0

by Sasha Matison (JIRA)

Failure to deploy a war file with JBoss 5.0 ------------------------------------------- Key: JBAS-8366 URL: https://jira.jboss.org/browse/JBAS-8366 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ClassLoading Affects Versions: JBossAS-5.0.0.GA Environment: Windows 2003 R2 SP2, JBoss AS 5.0, JDK 1.6_16 Reporter: Sasha Matison Assignee: Scott M Stark Priority: Blocker While deploying our war file with JBoss AS 5.0 we are getting the following error: org.jboss.xb.binding.JBossXBRuntimeException: Failed to create a new SAX parser We are shipping the product with a version of Xerces-j 2.9.1. Removing this version from the product is not an option. Note that the war file used to work with JBoss 4.x. This issue is blocking JBoss 5.0 testing. Please advise on the solution. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
5
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2011