September 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-759) Subsystem "messaging": security-settings and addressing settings should be subresoures

by Heiko Braun (JIRA)

Subsystem "messaging": security-settings and addressing settings should be subresoures -------------------------------------------------------------------------------------- Key: AS7-759 URL: https://issues.jboss.org/browse/AS7-759 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Heiko Braun Assignee: Jason Greene otherwise it's not possible to update these settings. If they would be subresources then the generic #add() and #remove() operations would apply. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (AS7-1707) jboss-as-arquillian-container-managed gets stuck when starting JBossAS 7.0.1+

by Martin Gencur (JIRA)

jboss-as-arquillian-container-managed gets stuck when starting JBossAS 7.0.1+ ----------------------------------------------------------------------------- Key: AS7-1707 URL: https://issues.jboss.org/browse/AS7-1707 Project: Application Server 7 Issue Type: Bug Components: Test Suite Affects Versions: 7.0.1.Final Reporter: Martin Gencur Assignee: Aslak Knutsen When starting JBossAS 7.0.0.Final with jboss-as-arquillian-container-managed from maven, the JBossAS (even more instances in a cluster) starts smoothly. After updating the version to 7.0.1.Final, the managed container gets stuck when starting first of the JBossAS instances in the cluster. It hangs on "09:39:04,084 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.1.Final "Zap" started in 2570ms - Started 93 of 148 services (55 services are passive or on-demand)" This is still true with JBossAS 7.1.0.Alpha1-SNAPSHOT (where HEAD = commit 0e3e092eb97d2b3d324ca623db0dabc949a6fbbe - AS7-1697 Add test that verifies methods with arrays in their signature are handled correctly) I tried various combinations of maven-surefire-plugin (2.9 with forkMode = once, 2.9 with fork mode never, 2.8.1 with fork mode once), none of them works. The configuration I'm using in arquillian.xml is: {code:xml} <group qualifier="Grid"> <container qualifier="container1" managed="true"> <protocol type="jmx-as7"> <property name="executionType">REMOTE</property> </protocol> <configuration> <property name="bindAddress">test1</property> <property name="managementPort">9999</property> <property name="jbossHome">/home/mgencur/Java/jboss7/jboss-as-7.0.1.Final</property> </configuration> </container> <container qualifier="container2" managed="false"> <protocol type="jmx-as7"> <property name="executionType">REMOTE</property> </protocol> <configuration> <property name="bindAddress">test2</property> <property name="managementPort">19999</property> <property name="jbossHome">/home/mgencur/Java/jboss7/jboss-as-7.0.1.Final-2</property> </configuration> </container> </group> {code} Is this a configuration problem? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
3
0 / 0

[JBoss JIRA] Commented: (AS7-1338) Remote JNDI support for AS7

by Carlo de Wolf (JIRA)

[ https://issues.jboss.org/browse/AS7-1338?page=com.atlassian.jira.plugin.s... ] Carlo de Wolf commented on AS7-1338: ------------------------------------ Since people keep coming back to this issue for what is actually "Client JNDI support" I've raised AS7-1709. > Remote JNDI support for AS7 > --------------------------- > > Key: AS7-1338 > URL: https://issues.jboss.org/browse/AS7-1338 > Project: Application Server 7 > Issue Type: Task > Components: Naming > Reporter: Richard Opalka > Assignee: David Lloyd > Priority: Blocker > Fix For: No Release > > > <opalka> wolfc, dmlloyd I'm not able to connect to JNDI on AS7. in the AS7 config I see it should be running on 1099, but I'm getting http://fpaste.org/wgy8/ :( > <opalka> wolfc, dmlloyd in the config I see the following ports defined > <opalka> --- > <opalka> <socket-binding name="jndi" port="1099"/> > <opalka> <socket-binding name="jmx-connector-registry" port="1090"/> > <opalka> <socket-binding name="jmx-connector-server" port="1091"/> > <opalka> --- > <dmlloyd> we don't do JNDI over RMI anymore > <dmlloyd> that listing is an error > <opalka> dmlloyd, So we're not able to do JNDI lookups to AS7 anymore and don't plan to? > <opalka> dmlloyd, or we'll be doing JNDI over different binary protocol? > <dmlloyd> no, we will be able to, it'll just work somewhat differently > <opalka> dmlloyd, ok, I'm excluding the tests then ... > <opalka> dmlloyd, Is there a JIRA covering this issue so I can use it in my excludes comment? > <dmlloyd> not that I'm aware of, it's just an outstanding task > <dmlloyd> remote invocation is not planned to be covered in next months' beta release > <opalka> dmlloyd, ok, thx for info ;) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (AS7-1273) Applications (or their libraries) containing persistence units with the connection defined inline via properties case deployment failure.

by Justin Wyer (JIRA)

Applications (or their libraries) containing persistence units with the connection defined inline via properties case deployment failure. ----------------------------------------------------------------------------------------------------------------------------------------- Key: AS7-1273 URL: https://issues.jboss.org/browse/AS7-1273 Project: Application Server 7 Issue Type: Bug Components: JPA / Hibernate Affects Versions: 7.0.0.Final, 7.1.0.Alpha1 Reporter: Justin Wyer Assignee: Scott Marlow Persistence units defined as follows https://github.com/droolsjbpm/jbpm/blob/master/jbpm-human-task/src/main/r... causes deployment to fail due to the fact that no <jta-data-source> or <non-jta-data-source> is present, but none should be present as the datasource has been defined via the properties. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
7
0 / 0

[JBoss JIRA] Created: (JBRULES-1287) Use of reserved word as bound variable in a pattern results as NPE

by Justin Wick (JIRA)

Use of reserved word as bound variable in a pattern results as NPE ------------------------------------------------------------------ Key: JBRULES-1287 URL: http://jira.jboss.com/jira/browse/JBRULES-1287 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder, Eclipse IDE Affects Versions: 4.0.2 Environment: Eclipse 3.2, Windows XP Reporter: Justin Wick Assigned To: Mark Proctor example: rule "This generates an NPE" when result : ReservedWordNPEFact(data < 15) then result.setData(new Integer(1)); end At least in the eclipse IDE, this generates an NPE. Change result to something like: rule "This generates an NPE" when f: ReservedWordNPEFact(data < 15) then f.setData(new Integer(1)); end and it goes away. -- 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, 10 months

5
11
0 / 0

[JBoss JIRA] Updated: (JBRULES-3063) Drools should not allow set two rules with the same name for the same package

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3063?page=com.atlassian.jira.plug... ] RH Bugzilla Integration updated JBRULES-3063: --------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=724753 > Drools should not allow set two rules with the same name for the same package > ----------------------------------------------------------------------------- > > Key: JBRULES-3063 > URL: https://issues.jboss.org/browse/JBRULES-3063 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: drools-compiler > Affects Versions: 5.1.1.FINAL > Reporter: Alessandro Lazarotti > Assignee: Tihomir Surdilovic > Priority: Minor > Fix For: FUTURE > > > Drools should not allow set two rules with the same name for the same package > As expected, Drools does not allow us to define two rules with the same name in a same DRL file. > But if there are two rules with the same name, in the same package, but in separate files, no exception or warning is issued, just one rule overrides the other in silence. > From documentation: > "A rule must have a name, unique within its rule package. If a rule is defined twice in a single DRL, an error will appear when one loads it. If a DRL that includes a rule name already in the package is added, the previous rule is repalced."[1] > [1] http://docs.redhat.com/docs/en-US/JBoss_Enterprise_SOA_Platform/5/html/JB... > Different behavior for a similar action is not good. Both should alert user about a rule name repeated. > For large projects using a lot of DRL files can be hard to track mistakes occurred by rules override . It is really necessary provide an ERROR message for this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-552) Outline problems in DRL editor

by Dirk Bergstrom (JIRA)

Outline problems in DRL editor ------------------------------ Key: JBRULES-552 URL: http://jira.jboss.com/jira/browse/JBRULES-552 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.0.4 Reporter: Dirk Bergstrom Assigned To: Mark Proctor Priority: Minor Two (possibly related) problems with the outline view in the DRL editor: *) Rules that are commented out via a multi-line comment (/* ... */) still appear in the outline. *) Clicking on the name of a rule highlights some text near that rule. I assume it's supposed to highight the title of the rule, but it misses. Same thing affects the imports. -- 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, 10 months

4
5
0 / 0

[JBoss JIRA] Created: (AS7-1693) The jmx socket-binding should be configured to use the "management" interface

by Brian Stansberry (JIRA)

The jmx socket-binding should be configured to use the "management" interface ----------------------------------------------------------------------------- Key: AS7-1693 URL: https://issues.jboss.org/browse/AS7-1693 Project: Application Server 7 Issue Type: Task Components: Domain Management Affects Versions: 7.0.1.Final, 7.0.0.Final Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.0.2.Final In the standard configs the jmx interface shouldn't be bound by default to the "public" interface, as users are likely to configure that interface to be open for insecure use. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (AS7-1704) Upgrade to Hibernate 4.0.0.CR2

by Scott Marlow (JIRA)

Upgrade to Hibernate 4.0.0.CR2 ------------------------------ Key: AS7-1704 URL: https://issues.jboss.org/browse/AS7-1704 Project: Application Server 7 Issue Type: Task Components: JPA / Hibernate Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 7.0.2.Final -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
1
0 / 0

[JBoss JIRA] Moved: (AS7-1702) Accept <any-address/> in Jboss AS7 configuration

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/AS7-1702?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen moved ARQ-580 to AS7-1702: ---------------------------------------- Project: Application Server 7 (was: Arquillian) Key: AS7-1702 (was: ARQ-580) Affects Version/s: 7.0.1.Final (was: 1.0.0.CR4) Component/s: Test Suite (was: JBoss Containers) Security: (was: Public) > Accept <any-address/> in Jboss AS7 configuration > ------------------------------------------------ > > Key: AS7-1702 > URL: https://issues.jboss.org/browse/AS7-1702 > Project: Application Server 7 > Issue Type: Bug > Components: Test Suite > Affects Versions: 7.0.1.Final > Environment: JBoss AS 7.0.1.Final > Reporter: Alexandre Gattiker > > ERROR ArquillianServiceDeployer - Cannot deploy arquillian service > java.lang.IllegalArgumentException > at org.jboss.dmr.ModelValue.asList(ModelValue.java:128) > at org.jboss.dmr.ModelNode.asList(ModelNode.java:1096) > at org.jboss.as.arquillian.container.ManagementClient.getInterface(ManagementClient.java:185) > at org.jboss.as.arquillian.container.ManagementClient.getBinding(ManagementClient.java:177) > at org.jboss.as.arquillian.container.ManagementClient.extractSubSystemURI(ManagementClient.java:148) > at org.jboss.as.arquillian.container.ManagementClient.getSubSystemURI(ManagementClient.java:90) > at org.jboss.as.arquillian.container.ManagementClient.getDeploymentMetaData(ManagementClient.java:96) > at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:98) > at org.jboss.as.arquillian.protocol.jmx.ArquillianServiceDeployer.doServiceDeploy(ArquillianServiceDeployer.java:58) > After changing the JBoss AS 7 configuration from: > <interface name="public"> > <inet-address value="127.0.0.1"/> > </interface> > to: > <interface name="public"> > <any-address/> > </interface> > Presumed cause: > in org.jboss.as.arquillian.container.ManagementClient in jboss-as-arquillian-common-7.0.1.Final.jar: > return rootNode.get("interface").get(name).get("criteria").asList().get(0).get("inet-address").asString(); -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
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 September 2011