November 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4287) Console loading is slow over WAN with high ping

by Radim Kolář (JIRA)

Radim Kolář created AS7-4287: -------------------------------- Summary: Console loading is slow over WAN with high ping Key: AS7-4287 URL: https://issues.jboss.org/browse/AS7-4287 Project: Application Server 7 Issue Type: Task Components: Console Affects Versions: 7.1.1.Final Reporter: Radim Kolář Assignee: Heiko Braun Priority: Minor Console loading over WAN network with 250ms ping is very slow. it takes about 1 minute or maybe evenmore to load. I suspect that GWT application is splitted into too many small fragments with GWT splitpoints, which can make loading faster but only if ping time to server is low. On Europe -> USA link it will be very slow. -- 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, 6 months

2
5
0 / 0

[JBoss JIRA] (JGRP-1537) FILE_PING.writeToTempFile prints error without details

by Jesse Glick (JIRA)

Jesse Glick created JGRP-1537: --------------------------------- Summary: FILE_PING.writeToTempFile prints error without details Key: JGRP-1537 URL: https://issues.jboss.org/browse/JGRP-1537 Project: JGroups Issue Type: Bug Affects Versions: 3.1 Reporter: Jesse Glick Assignee: Bela Ban Priority: Minor I am getting log errors such as {code:none} SEVERE: Failed to write temporary file: /…/jgroups/…(a)....tmp {code} with no explanation of why the write failed. (Bad permissions? Low disk space?) {{writeToTempFile}} should call the two-arg overload of {{error}} and pass {{e}}. -- 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, 6 months

2
2
0 / 0

[JBoss JIRA] (AS7-4822) multi-threaded client can't clean up threads

by Rob Stryker (JIRA)

Rob Stryker created AS7-4822: -------------------------------- Summary: multi-threaded client can't clean up threads Key: AS7-4822 URL: https://issues.jboss.org/browse/AS7-4822 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.0.Final Reporter: Rob Stryker Assignee: Brian Stansberry When using a multi-threaded remote management client, several threads refuse to clean up, leaving to a deadlocked / frozen thread during a call to client.close(). Simple POJP to be attached, with stack trace. Jars on the classpath are as follows: jboss-as-controller-client-7.1.0.Final.jar jboss-as-protocol-7.1.0.Final.jar jboss-dmr-1.1.1.Final.jar jboss-logging-3.1.0.GA.jar jboss-marshalling-1.3.9.GA.jar jboss-remoting-3.2.2.GA.jar jboss-remoting-3.2.7.GA.jar jboss-sasl-1.0.0.Final.jar jboss-threads-2.0.0.GA.jar xnio-api-3.0.3.GA.jar xnio-nio-3.0.3.GA.jar -- 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, 6 months

2
5
0 / 0

[JBoss JIRA] (AS7-5857) OSGi Resolution failure should be logged as an error

by David Bosschaert (JIRA)

David Bosschaert created AS7-5857: ------------------------------------- Summary: OSGi Resolution failure should be logged as an error Key: AS7-5857 URL: https://issues.jboss.org/browse/AS7-5857 Project: Application Server 7 Issue Type: Feature Request Components: OSGi Affects Versions: 7.2.0.Alpha1 Reporter: David Bosschaert Assignee: Thomas Diesler When deploying an OSGi bundle that fails to resolve, currently only a warning is logged, this should really be an ERROR. {code}13:21:31,275 WARN [org.jboss.as.osgi] (MSC service thread 1-13) JBAS011910: Cannot resolve requirements: [XPackageRequirement[atts={osgi.wiring.package=javax.servlet, version=[2.1.0,3.0.0)},[TestOSGiHttpService:1.0.0]]] 13:21:31,275 INFO [org.jboss.as.server.deployment] (MSC service thread 1-13) JBAS015970: Defer FIRST_MODULE_USE for TestOSGiHttpService_1.0.0.jar making it NEVER 13:21:31,305 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "TestOSGiHttpService_1.0.0.jar"{code} Additionally, the deployment is marked as 'deployed'. It would be better if it could be marked as 'failed' -- 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, 6 months

2
1
0 / 0

[JBoss JIRA] (AS7-5761) EJB2 entity bean CMP collection toArray throws NPE

by Lucas Galfaso (JIRA)

Lucas Galfaso created AS7-5761: ---------------------------------- Summary: EJB2 entity bean CMP collection toArray throws NPE Key: AS7-5761 URL: https://issues.jboss.org/browse/AS7-5761 Project: Application Server 7 Issue Type: Feature Request Components: EJB Affects Versions: 7.1.1.Final Environment: MAC OSX, Java7 Reporter: Lucas Galfaso Assignee: jaikiran pai >From an EJB2 entity bean that has a CMP collection of entities, calling toArray() on the CMP collection throws NullPointerException Caused by: java.lang.NullPointerException at org.jboss.as.cmp.jdbc.bridge.RelationSet.toArray(RelationSet.java:291) [jboss-as-cmp-7.1.1.Final.jar:7.1.1.Final] Normal iteration thru the collection using the iterator works as expected. -- 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, 6 months

6
5
0 / 0

[JBoss JIRA] (AS7-5887) CLONE - Host controller unregisters server after it doesn't respond for 30 seconds; doesn't reconnect

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5887?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-5887: --------------------------------------- The critical problem here is that there is no automatic reconnection if via the process controller the HC can see the server is still alive. The timeout might need tweaking, but the key thing is getting the server reconnected. If the server reconnects, there won't be an issue as long as there were no commands attempting to modify that server in the interim -- with such a poorly timed modification being unlikely. If there were a mod, the HC knows the reconnecting server is out of sync and marks it as requiring restart. > CLONE - Host controller unregisters server after it doesn't respond for 30 seconds; doesn't reconnect > ----------------------------------------------------------------------------------------------------- > > Key: AS7-5887 > URL: https://issues.jboss.org/browse/AS7-5887 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.1.1.Final, 7.1.2.Final (EAP), 7.1.3.Final (EAP) > Reporter: Travis Rogers > Assignee: Emanuel Muckenhuber > Fix For: 7.2.0.CR1, 7.1.4.Final (EAP) > > > Simple test to reproduce: > (kill -STOP <pid>, 30 seconds later, receive "unregistered" message in the host controller. After restarting (kill -CONT <pid>), no longer able to control instance via the host controller. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-5887) CLONE - Host controller unregisters server after it doesn't respond for 30 seconds; doesn't reconnect

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5887?page=com.atlassian.jira.plugin.s... ] Brian Stansberry moved JBPAPP-10358 to AS7-5887: ------------------------------------------------ Project: Application Server 7 (was: JBoss Enterprise Application Platform) Key: AS7-5887 (was: JBPAPP-10358) Workflow: GIT Pull Request workflow (was: jira) Affects Version/s: 7.1.3.Final (EAP) 7.1.2.Final (EAP) 7.1.1.Final (was: EAP 6.0.0) Security: (was: Public) Fix Version/s: 7.2.0.CR1 7.1.4.Final (EAP) (was: TBD EAP 6) Docs QE Status: (was: NEW) > CLONE - Host controller unregisters server after it doesn't respond for 30 seconds; doesn't reconnect > ----------------------------------------------------------------------------------------------------- > > Key: AS7-5887 > URL: https://issues.jboss.org/browse/AS7-5887 > Project: Application Server 7 > Issue Type: Bug > Affects Versions: 7.1.3.Final (EAP), 7.1.2.Final (EAP), 7.1.1.Final > Reporter: Travis Rogers > Assignee: Brian Stansberry > Fix For: 7.2.0.CR1, 7.1.4.Final (EAP) > > > Simple test to reproduce: > (kill -STOP <pid>, 30 seconds later, receive "unregistered" message in the host controller. After restarting (kill -CONT <pid>), no longer able to control instance via the host controller. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-5887) CLONE - Host controller unregisters server after it doesn't respond for 30 seconds; doesn't reconnect

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5887?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5887: ---------------------------------- Component/s: Domain Management > CLONE - Host controller unregisters server after it doesn't respond for 30 seconds; doesn't reconnect > ----------------------------------------------------------------------------------------------------- > > Key: AS7-5887 > URL: https://issues.jboss.org/browse/AS7-5887 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.1.1.Final, 7.1.2.Final (EAP), 7.1.3.Final (EAP) > Reporter: Travis Rogers > Assignee: Brian Stansberry > Fix For: 7.2.0.CR1, 7.1.4.Final (EAP) > > > Simple test to reproduce: > (kill -STOP <pid>, 30 seconds later, receive "unregistered" message in the host controller. After restarting (kill -CONT <pid>), no longer able to control instance via the host controller. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-5887) CLONE - Host controller unregisters server after it doesn't respond for 30 seconds; doesn't reconnect

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5887?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5887: ---------------------------------- Assignee: Emanuel Muckenhuber (was: Brian Stansberry) > CLONE - Host controller unregisters server after it doesn't respond for 30 seconds; doesn't reconnect > ----------------------------------------------------------------------------------------------------- > > Key: AS7-5887 > URL: https://issues.jboss.org/browse/AS7-5887 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.1.1.Final, 7.1.2.Final (EAP), 7.1.3.Final (EAP) > Reporter: Travis Rogers > Assignee: Emanuel Muckenhuber > Fix For: 7.2.0.CR1, 7.1.4.Final (EAP) > > > Simple test to reproduce: > (kill -STOP <pid>, 30 seconds later, receive "unregistered" message in the host controller. After restarting (kill -CONT <pid>), no longer able to control instance via the host controller. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3679) drools-compiler's CDI does not work in a war

by Geoffrey De Smet (JIRA)

Geoffrey De Smet created JBRULES-3679: ----------------------------------------- Summary: drools-compiler's CDI does not work in a war Key: JBRULES-3679 URL: https://issues.jboss.org/browse/JBRULES-3679 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 6.0.0.Beta1 Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Fix For: 6.0.0.Beta1 KProjectExtension uses weld-se-core, but in a war weld-servlet-core should be used instead. We should aim to make KProjectExtension just use CDI and not depend on weld-se-core or weld-servlet-core, if possible. -- 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, 6 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2012