January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3354) HornetQ backup server won't start when live server is killed

by Miroslav Novak (JIRA)

Miroslav Novak created AS7-3354: ----------------------------------- Summary: HornetQ backup server won't start when live server is killed Key: AS7-3354 URL: https://issues.jboss.org/browse/AS7-3354 Project: Application Server 7 Issue Type: Bug Components: JMS Affects Versions: 7.1.0.CR1 Reporter: Miroslav Novak Assignee: Clebert Suconic Fix For: 7.1.0.Final Test scenario: 1. Start two AS7/EAP6 servers in (hornetq) cluster with HornetQ in colocated topology - server A contains backup for server B and server B contains backup for server A 2. Kill AS7/EAP6 server A using "kill -9 ..." I see following to happen after step 2.: a) HornetQ backup server on server B won't start/come live. b) Server B is not able to update its cluster view. a) and b) -> c) JMS clients on server A are not able to failover to bakcup I've attached reproducer with configuration - reproducer.zip. (logging is set to DEBUG level for "org.hornetq") How to use the reproducer (there are necessary two machines): 1. Download and unzip attached reproducer.zip 2. prepare servers A and B using - "sh prepare.sh" 3. start server A - "sh start-server1.sh serverA_hostname" - on server serverA_hostname 4. start server B - "sh start-server2.sh serverB_hostname" - on server serverB_hostname 5. Kill server A using "kill -9 ..." I've attached JMS client to reproducer (it's using HornetQ core api to create connection factory a queue "testQueue"): 1. Start producer - "sh start-producer.sh server_hostname" 2. Start consumer - "sh start-consumer.sh server_hostname" This could be configuration issue. For this reason I set major priority. Please re-check standalone-ha-A.xml and standalone-ha-B.xml. I could not find a bug in it. Thank you, Mirek -- 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

12 years, 8 months

1
2
0 / 0

[JBoss JIRA] (AS7-3350) Combo boxes stop working after hitting cancel

by David Bosschaert (JIRA)

David Bosschaert created AS7-3350: ------------------------------------- Summary: Combo boxes stop working after hitting cancel Key: AS7-3350 URL: https://issues.jboss.org/browse/AS7-3350 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.0.CR1b Reporter: David Bosschaert Assignee: Heiko Braun This is a general issue with the combo-boxes and their interaction with the editing framework. When you edit a subsystem that uses combo boxes (e.g. EJB 3) and then hit cancel instead of save, the combo box becomes unresponsive when trying to edit the subsystem again. The main problem is with combo boxes that have 2 possible values, although if there are 3 values the problem applies to the 2 values involved (the old and the new). I have also seen the same behaviour with combo boxes in various places. -- 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

12 years, 8 months

2
3
0 / 0

[JBoss JIRA] (AS7-3324) Extend WS EndpointPublisher to allow providing properties/metadata

by Alessio Soldano (JIRA)

Alessio Soldano created AS7-3324: ------------------------------------ Summary: Extend WS EndpointPublisher to allow providing properties/metadata Key: AS7-3324 URL: https://issues.jboss.org/browse/AS7-3324 Project: Application Server 7 Issue Type: Enhancement Components: Web Services Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: 7.1.0.Final The EndpointPublisher spi currently allows for providing @WebService/@WebServiceProvider annotated endpoint class and deploy endpoint(s) to the running JBoss AS container with an api pretty much equivalent to the JAXWS Endpoint.publish(..) api. What is missing is the ability of doing something like: {code} List<Source> metadata = new ArrayList<Source>(); StreamSource source = WSDLUtil.getStream(_config.getWsdl()); metadata.add(source); Map<String, Object> properties = new HashMap<String, Object>(); properties.put(Endpoint.WSDL_SERVICE, portName.getServiceQName()); properties.put(Endpoint.WSDL_PORT, portName.getPortQName()); properties.put(WSDL_LOCATION, WSDLUtil.getURL(_config.getWsdl()).toExternalForm()); ... _endpoint = Endpoint.create(wsProvider); // instance of @WebServiceProvider annotated class, with no attributes in the annotation _endpoint.setMetadata(metadata); _endpoint.setProperties(properties); _endpoint.publish(publishUrl); {code} IOW, we need support for setting properties and metadata and passing them down to the stack (Apache CXF already reads them generated DDBeans/descriptor). This is required for a proper SwitchYard integration into AS7. -- 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

12 years, 8 months

1
4
0 / 0

[JBoss JIRA] (AS7-3353) ActivationSpec.setResourceAdapter called by EJB3

by Jesper Pedersen (JIRA)

Jesper Pedersen created AS7-3353: ------------------------------------ Summary: ActivationSpec.setResourceAdapter called by EJB3 Key: AS7-3353 URL: https://issues.jboss.org/browse/AS7-3353 Project: Application Server 7 Issue Type: Bug Components: EJB Reporter: Jesper Pedersen Assignee: jaikiran pai Priority: Critical Fix For: 7.1.0.Final ./ejb3/src/main/java/org/jboss/as/ejb3/component/messagedriven/MessageDrivenComponentCreateService.java calls activationSpec.setResourceAdapter(ra). This is incorrect, since it is done by the JCA SPI. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-2525) Server Group VM settings switches back to "default"

by Heiko Braun (Created) (JIRA)

Server Group VM settings switches back to "default" --------------------------------------------------- Key: AS7-2525 URL: https://issues.jboss.org/browse/AS7-2525 Project: Application Server 7 Issue Type: Bug Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.1.0.CR1 1.) new server group 2.) add jam setting: "staging", 64m, 64m 3.) after "save" the jam setting "default" is loaded -- 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

12 years, 8 months

6
6
0 / 0

[JBoss JIRA] (AS7-3155) Console does not correctly edit the EE subsystems global-modules

by Stuart Douglas (Created) (JIRA)

Console does not correctly edit the EE subsystems global-modules ---------------------------------------------------------------- Key: AS7-3155 URL: https://issues.jboss.org/browse/AS7-3155 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.0.CR1b Reporter: Stuart Douglas Assignee: Heiko Braun Fix For: 7.1.0.Final If you go to the EE subsystem in the console and try and add a global module the list that pops up is limited to the modules that are provided by the as (i.e. only org.jboss.as.* modules). As the primary use case for this feature is to allow users to create their own system wide libraries, this is not very useful (there should never be any need to add an org.jboss.as module as a global module). -- 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

12 years, 8 months

3
4
0 / 0

[JBoss JIRA] (JBRULES-3316) Drools 5.3.0 Eclipse plugin cannot read audit log Drools 5.3 creates

by Alexis Brouard (Created) (JIRA)

Drools 5.3.0 Eclipse plugin cannot read audit log Drools 5.3 creates -------------------------------------------------------------------- Key: JBRULES-3316 URL: https://issues.jboss.org/browse/JBRULES-3316 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-eclipse Affects Versions: 5.3.0.Final Reporter: Alexis Brouard Assignee: Mark Proctor Audit view of Drools 5.3 Eclipse plugin always display "The selected audit log is empty" but file is a correct xstream dump. The audit log created in Drools 5.3 is correctly interpreted by Drools 5.2 Eclipse plugin. A discussion about this issue is opened on Nabble / Drools-users mailing-list (see link in forum reference) More info: * Eclipse Indigo SR1 (build id: 20110916-0149) * Drools Eclipse plugins installed: JBoss Drools Core 5.3.0.Final, JBoss Drools Guvnor 5.3.0.Final, JBoss Drools Task 5.3.0.Final * Drools version used to create audit log: 5.3.0.Final -- 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

12 years, 8 months

3
2
0 / 0

[JBoss JIRA] Created: (AS7-1153) Arquillian Containers should expose a Context(Initial) to Core

by Aslak Knutsen (JIRA)

Arquillian Containers should expose a Context(Initial) to Core -------------------------------------------------------------- Key: AS7-1153 URL: https://issues.jboss.org/browse/AS7-1153 Project: Application Server 7 Issue Type: Feature Request Components: Test Suite Affects Versions: 7.0.0.CR1 Reporter: Aslak Knutsen If the Container provide a InitialContext to Arquillian, the TestEnrichers like @EJB and @Resource can operate in Client mode. e.g. to lookup Remote EJBs or Remotable Resources in JNDI. @Inject @ContainerScoped private InstanceProducer<Context> contextInst; container.start() { contextInst.set(createInitialContext()); } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
2
0 / 0

[JBoss JIRA] (AS7-3269) "Restart Required" indication in domain mode

by Heiko Braun (Created) (JIRA)

"Restart Required" indication in domain mode -------------------------------------------- Key: AS7-3269 URL: https://issues.jboss.org/browse/AS7-3269 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.1.0.Final -- 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

12 years, 8 months

2
1
0 / 0

[JBoss JIRA] (AS7-3128) Arquillian doesn't wait for the process to really end, causes problems like "port in use".

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/AS7-3128?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen commented on AS7-3128: ------------------------------------ As far as I can tell, the Arquillian AS7 Managed Container does wait for the Process it spawns to end. {code} process.destroy() process.waitFor() {code} Unless there is some other waitFor that should be called as well, I'm not sure why that would leave the process with open ports.. Ondrej; the test you are refering to is not using Arquillian it self, but I assume Arquillian has been running previously.. ? > Arquillian doesn't wait for the process to really end, causes problems like "port in use". > ------------------------------------------------------------------------------------------ > > Key: AS7-3128 > URL: https://issues.jboss.org/browse/AS7-3128 > Project: Application Server 7 > Issue Type: Bug > Components: Test Suite > Affects Versions: 7.1.0.CR1 > Reporter: Ondrej Zizka > Assignee: Aslak Knutsen > Priority: Blocker > Labels: arq_qe_blocker > > (05:54:09) dmlloyd: when running with JDWP enabled on the client or server, I occasionally get bind exceptions due to address in use > (05:54:25) dmlloyd: which means that tests are running into each other without waiting for termination of the previous one > (05:54:35) dmlloyd: which may also be causing other issues > (05:56:04) ozizka: dmlloyd: Yes, lbarrerio observed similar problem too, > (05:56:47) ozizka: And that's arq's issue too - there's no way to get around this currently AFAIK. Or is there? > (05:57:05) ozizka: Perhaps "manually" wait in @AfterClass or such > (05:57:07) dmlloyd: yeah, it can wait for the child process to terminate > (05:57:07) ozizka: which is ugly > (05:57:14) dmlloyd: I mean arq should > (05:59:17) ozizka: dmlloyd: Do you have it somewhere on hudson? > (05:59:24) ozizka: dmlloyd: It never happened to me actually > (05:59:49) ozizka: Send me a log if you have one handy > (06:01:35) dmlloyd: ozizka: no, try running with this command though: > {code} > mvn -DallTests install -Djpda -Dsurefire.jpda.args=-Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n \ > -Dmaven.surefire.debug="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005" > {code} > (06:13:56) ozizka: dmlloyd: That's on linux? > (06:14:03) dmlloyd: yes -- 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

12 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2012