October 2011 - jboss-jira - Jboss List Archives

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

by Tomáš Remeš (Commented) (JIRA)

[ https://issues.jboss.org/browse/AS7-1702?page=com.atlassian.jira.plugin.s... ] Tomáš Remeš commented on AS7-1702: ---------------------------------- I'm facing this error too. Using jdk 1.6.0_24, AS7 latest source from above link or jboss-as-web-7.0.2.Final > 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 > Assignee: Emanuel Muckenhuber > Fix For: 7.0.2.Final > > > 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. 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] (JGRP-1377) Merge: add second line of defense for killing of runaway merge tasks

by Bela Ban (Created) (JIRA)

Merge: add second line of defense for killing of runaway merge tasks -------------------------------------------------------------------- Key: JGRP-1377 URL: https://issues.jboss.org/browse/JGRP-1377 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0 This prevents the following scenario: - A merge ID is set and the merge task started - If the merge task ends without setting merge-id back to null, subsequent merge requests will be rejected, because the merge coordinator thinks there is a merge still ongoing - This should not happen, but I nevertheless want to add a second line of defense to prevent this SOLUTION: - Whenever a merge-id is assigned and the merge task started, we also keep track of the time this happened - A separate timer task is started and runs every (say) M seconds (e.g. 2 minutes) - The task checks whether the time stamp of the last merge (if not 0 (= no merge is running)) is more than N seconds old - (M and N are configurable) - If this is the case, then we force-cancel the merge - The forceCancelMerge() operation is also exposed via JMX, so it can be invoked (e.g.) across a cluster: probe.sh op=GMS.forceCancelMerge -- 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] Created: (JBBUILD-699) Add javadocs and gpg configuration to jboss-parent

by Paul Gier (JIRA)

Add javadocs and gpg configuration to jboss-parent -------------------------------------------------- Key: JBBUILD-699 URL: https://issues.jboss.org/browse/JBBUILD-699 Project: JBoss Build System Issue Type: Feature Request Components: JBoss Parent POM Reporter: Paul Gier Assignee: Paul Gier Fix For: JBoss Parent POM - 7 The JBoss parent pom should include javadoc generation and gpg signature configuration in a profile which can be used during release. -- 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] (JBBUILD-705) Add manifest configuration to source jars

by Paul Gier (Created) (JIRA)

Add manifest configuration to source jars ----------------------------------------- Key: JBBUILD-705 URL: https://issues.jboss.org/browse/JBBUILD-705 Project: JBoss Build System Issue Type: Enhancement Components: JBoss Parent POM Reporter: Paul Gier Assignee: Paul Gier Fix For: JBoss Parent POM - 7 The generated java source jars should include manifest information similar to what's included in the binary jars. -- 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-2209) Support for OpenJPA runtime enhancement of entities

by Antti Laisi (Created) (JIRA)

Support for OpenJPA runtime enhancement of entities --------------------------------------------------- Key: AS7-2209 URL: https://issues.jboss.org/browse/AS7-2209 Project: Application Server 7 Issue Type: Enhancement Components: JPA / Hibernate Affects Versions: 7.1.0.Beta1 Reporter: Antti Laisi Assignee: Scott Marlow Priority: Minor Support for using runtime enhancement (byte code generation for persistent classes) with OpenJPA. OpenJPA javaagent doesn't work with AS7, so currently the only way to use OpenJPA is with build-time enhancement. -- 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-1078) executor in <connector/> of web subsystem doesn't work.

by Jean-Frederic Clere (JIRA)

executor in <connector/> of web subsystem doesn't work. ------------------------------------------------------- Key: AS7-1078 URL: https://issues.jboss.org/browse/AS7-1078 Project: Application Server 7 Issue Type: Bug Components: Web Affects Versions: 7.0.0.Beta3 Reporter: Jean-Frederic Clere Add in threads subsystem: <bounded-queue-thread-pool name="executor" blocking="true"> <core-threads count="10" per-cpu="20"/> <queue-length count="10" per-cpu="20"/> <max-threads count="10" per-cpu="20"/> <keepalive-time time="10" unit="seconds"/> </bounded-queue-thread-pool> and: <connector name="http" scheme="http" protocol="HTTP/1.1" socket-binding="http" executor="executor" /> web will still use the default executor. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
3
0 / 0

[JBoss JIRA] (JBRULES-3262) Rule Search feature

by G Patel (Created) (JIRA)

Rule Search feature ------------------- Key: JBRULES-3262 URL: https://issues.jboss.org/browse/JBRULES-3262 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-core (expert), drools-guvnor Reporter: G Patel Assignee: Mark Proctor Drools sorely lacks a rule search feature i.e - ability to search and display rules that match a particular criteria. For example: show all rules that contain the fact Person whose age > 21 -- 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] (JBRULES-3260) Events with no expiration declared being set to zero expirationOffset during package assembly

by Rob Crawford (Created) (JIRA)

Events with no expiration declared being set to zero expirationOffset during package assembly --------------------------------------------------------------------------------------------- Key: JBRULES-3260 URL: https://issues.jboss.org/browse/JBRULES-3260 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (expert), drools-core (fusion) Affects Versions: 5.3.0.Final, 5.3.0.CR1 Reporter: Rob Crawford Assignee: Mark Proctor Had a problem with events being expired immediately on being inserted. These events have no @expiration declaration. Tracing and debugging led to this line: ReteooRuleBase, line 477: node.setExpirationOffset( Math.max( node.getExpirationOffset(), typeDeclaration.getExpirationOffset()+1 ) ); Since neither the type and its supertype have expirations declared, getExpirationOffset() returns -1 in both cases. Max(-1, -1 + 1) == 0, so the event is assigned an expiration of zero. Should make sure not to set the expiration when both are already -1. -- 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

5
4
0 / 0

[JBoss JIRA] Created: (AS7-1015) Deployment fails with NullPointerException when installing JDBC Driver as a deployment

by Sande Gilda (JIRA)

Deployment fails with NullPointerException when installing JDBC Driver as a deployment -------------------------------------------------------------------------------------- Key: AS7-1015 URL: https://issues.jboss.org/browse/AS7-1015 Project: Application Server 7 Issue Type: Bug Components: JCA Environment: Fedora 14. JBoss AS7 build from June 8, Using MySQL JDBC driver downloaded as an example from http://community.jboss.org/wiki/DataSourceConfigurationinAS7#Installing_a... Reporter: Sande Gilda I am working on the DataSource configuration changes for the EAP5 -> EAP6 migration guide and am following the steps here: http://community.jboss.org/wiki/DataSourceConfigurationinAS7. I have been able to successfully install the MySQL JDBC driver as a module, however, I am not having much luck installing the driver as a deployment, which this document says is the recommended way to install it. I've done the following: - I copied the JDBC-compliant mysql-connector-java-5.1.15.jar (downloaded from the above web site) into my <jboss7>/standalone/deployments directory. - I still have the <datasource> and <driver> elements defined in my standalone.xml file from when I successfully installed the driver as a module. When I start the server, I see the following error in the log: 11:53:42,348 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.deployment.unit."TopicIndex.war".CONFIGURE_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."TopicIndex.war".CONFIGURE_MODULE: Failed to process phase CONFIGURE_MODULE of deployment "TopicIndex.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) [jboss-as-server-7.0.0.Beta4-SNAPSHOT.jar:7.0.0.Beta4-SNAPSHOT] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675) [jboss-msc-1.0.0.Beta8.jar:1.0.0.Beta8] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_25] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_25] at java.lang.Thread.run(Thread.java:662) [:1.6.0_25] Caused by: java.lang.NullPointerException at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:188) [jboss-msc-1.0.0.Beta8.jar:1.0.0.Beta8] at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2165) [jboss-msc-1.0.0.Beta8.jar:1.0.0.Beta8] at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:188) [jboss-msc-1.0.0.Beta8.jar:1.0.0.Beta8] at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2165) [jboss-msc-1.0.0.Beta8.jar:1.0.0.Beta8] at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:325) [jboss-msc-1.0.0.Beta8.jar:1.0.0.Beta8] at org.jboss.as.server.deployment.module.ModuleSpecProcessor.createModuleService(ModuleSpecProcessor.java:193) [jboss-as-server-7.0.0.Beta4-SNAPSHOT.jar:7.0.0.Beta4-SNAPSHOT] at org.jboss.as.server.deployment.module.ModuleSpecProcessor.deploy(ModuleSpecProcessor.java:99) [jboss-as-server-7.0.0.Beta4-SNAPSHOT.jar:7.0.0.Beta4-SNAPSHOT] at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.0.0.Beta4-SNAPSHOT.jar:7.0.0.Beta4-SNAPSHOT] ... 4 more 11:53:42,350 ERROR [org.jboss.as] (MSC service thread 1-1) JBoss AS 7.0.0.Beta4-SNAPSHOT "(TBD)" started (with errors) in 6159ms - Started 136 of 196 services (5 services failed or missing dependencies, 55 services are passive or on-demand) Later I see the message that deployment of my WAR failed due to the missing dependency: 11:53:42,394 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting deployment of "TopicIndex.war" 11:53:42,394 INFO [org.jboss.as.server] (MSC service thread 1-6) Service status report New missing/unsatisfied dependencies: service jboss.jdbc-driver._________________________ (missing) required by [service jboss.data-source.java:/TopicIndexDatasource] Is there something else I need to be doing here? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

6
19
0 / 0

[JBoss JIRA] (AS7-2203) Add support for AS 7 domain controller

by Aslak Knutsen (Moved) (JIRA)

[ https://issues.jboss.org/browse/AS7-2203?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen moved ARQ-498 to AS7-2203: ---------------------------------------- Project: Application Server 7 (was: Arquillian) Key: AS7-2203 (was: ARQ-498) Security: (was: Public) > Add support for AS 7 domain controller > -------------------------------------- > > Key: AS7-2203 > URL: https://issues.jboss.org/browse/AS7-2203 > Project: Application Server 7 > Issue Type: Feature Request > Reporter: Ondrej Zizka > Assignee: Andrew Rubinger > Priority: Critical > > A container for AS 7 domain controller would be very helpful for it's integration testsuite. > Such container should support: > * Attaching hosts to a domain > * Start, stop a domain with multiple hosts > * Configuration (creation) of the domain using domain config file > * Configuration (creation) of a profile using a CLI batch > * Configuration (creation) of a profile using a callback class which would handle communication with Java API > More requirements to come. -- 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 October 2011