January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2744) Injection resources of type URL by @Resource annotation

by Ondřej Chaloupka (Created) (JIRA)

Injection resources of type URL by @Resource annotation ------------------------------------------------------- Key: AS7-2744 URL: https://issues.jboss.org/browse/AS7-2744 Project: Application Server 7 Issue Type: Bug Reporter: Ondřej Chaloupka Assignee: Stuart Douglas The binding resources of type URL by @Resource annotations leads to not deployable application. The code of the prior test which tests this functionality could be seen on: http://anonsvn.jboss.org/repos/jbossas/projects/ejb3/trunk/testsuite/src/... The problematic injections are following: {code} @Stateless @Remote(ResUrlChecker.class) @Resources({ @Resource(name="url3", type=java.net.URL.class, mappedName="http://localhost/url3") }) public class ResUrlCheckerBean implements ResUrlChecker { @Resource(mappedName="http://localhost") private URL url1; } {code} -- 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

4
4
0 / 0

[JBoss JIRA] (AS7-3471) Cannot Deploy Two Distributable Applications to AS7 Started w/ standalone-ha.xml Config

by Benjamin Browning (JIRA)

Benjamin Browning created AS7-3471: -------------------------------------- Summary: Cannot Deploy Two Distributable Applications to AS7 Started w/ standalone-ha.xml Config Key: AS7-3471 URL: https://issues.jboss.org/browse/AS7-3471 Project: Application Server 7 Issue Type: Bug Reporter: Benjamin Browning Priority: Critical Attachments: node-info.war Trying to deploy two distributable web applications to AS 7.1 master since the upgrade to Infinispan 5.1.0.Final fails with the following error: 12:34:01,899 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC00001: Failed to start service jboss.deployment.unit."node-info-copy.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."node-info-copy.war".INSTALL: Failed to process phase INSTALL of deployment "node-info-copy.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29] at java.lang.Thread.run(Thread.java:680) [:1.6.0_29] Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018027: Failed to add JBoss Web deployment service at org.jboss.as.web.deployment.WarDeploymentProcessor.processDeployment(WarDeploymentProcessor.java:277) at org.jboss.as.web.deployment.WarDeploymentProcessor.deploy(WarDeploymentProcessor.java:106) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] ... 5 more Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.infinispan.web.___defaultcache.registry is already registered at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:154) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:226) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:560) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2211) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2211) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:307) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.as.clustering.web.infinispan.DistributedCacheManagerFactory.addDependencies(DistributedCacheManagerFactory.java:120) at org.jboss.as.web.deployment.WarDeploymentProcessor.processDeployment(WarDeploymentProcessor.java:252) ... 7 more I tested with a dead simple application (attached) but any .war that's marked as distributable should exhibit the same problem. -- 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
2
0 / 0

[JBoss JIRA] (AS7-3223) Protect against ArrayIndexOutOfBoundsException when calling InetAddress.getLocalHost

by Galder Zamarreño (Created) (JIRA)

Protect against ArrayIndexOutOfBoundsException when calling InetAddress.getLocalHost ------------------------------------------------------------------------------------ Key: AS7-3223 URL: https://issues.jboss.org/browse/AS7-3223 Project: Application Server 7 Issue Type: Bug Reporter: Galder Zamarreño Fix For: 7.1.0.Final Can we please implement the equivalent of JGRP-1404 in AS7? Otherwise, when you start offline (under some circumstances), you get: {code}13:40:28,370 ERROR [stderr] java.lang.ArrayIndexOutOfBoundsException: 0 13:40:28,371 ERROR [stderr] at java.net.InetAddress.getLocalHost(InetAddress.java:1356) 13:40:28,371 ERROR [stderr] at org.jboss.as.server.ServerEnvironment.<init>(ServerEnvironment.java:223) 13:40:28,371 ERROR [stderr] at org.jboss.as.server.Main.determineEnvironment(Main.java:219) 13:40:28,371 ERROR [stderr] at org.jboss.as.server.Main.main(Main.java:98) 13:40:28,372 ERROR [stderr] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 13:40:28,372 ERROR [stderr] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 13:40:28,372 ERROR [stderr] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 13:40:28,372 ERROR [stderr] at java.lang.reflect.Method.invoke(Method.java:597) 13:40:28,372 ERROR [stderr] at org.jboss.modules.Module.run(Module.java:272) 13:40:28,373 ERROR [stderr] at org.jboss.modules.Main.main(Main.java:313) {code} I tried this with 7.0.2, so the lines might be diff in latest but I see ServerEnvironment still uses it: https://github.com/galderz/jboss-as/blob/master/server/src/main/java/org/... -- 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
3
0 / 0

[JBoss JIRA] (AS7-2948) Unsupported configuration attributes silently ignored

by Martin Vecera (Created) (JIRA)

Unsupported configuration attributes silently ignored ----------------------------------------------------- Key: AS7-2948 URL: https://issues.jboss.org/browse/AS7-2948 Project: Application Server 7 Issue Type: Bug Components: Server Affects Versions: 7.1.0.Beta1 Reporter: Martin Vecera Assignee: Jason Greene When there is an unsupported configuration attribute in standalone.xml, it is silently ignored and deleted from the configuration without a single warning the first time the server writes the configuration back to the disk. Sample piece of configuration (in standalone.xml): <connection-factory name="RemoteConnectionFactory"> <transaction mode="xa"/> <connectors> <connector-ref connector-name="netty"/> </connectors> <entries> <entry name="RemoteConnectionFactory"/> </entries> </connection-factory> Transaction mode is unsupported in an ordinary connection-factory. It must be pooled-connection-factory. -- 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

4
3
0 / 0

[JBoss JIRA] Created: (JBAS-9096) Management only domain mode

by Brian Stansberry (JIRA)

Management only domain mode --------------------------- Key: JBAS-9096 URL: https://issues.jboss.org/browse/JBAS-9096 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.Beta4 See parent task for core concept. With domain mode this is fairly simple. A host controller / domain controller is essentially a "management only" process. So implement this feature should be a simple matter of adding a command line flag that tells the process not to launch servers. If the host is the master DC, we need to think through what the behavior should be if a remote host tries to register. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

6
12
0 / 0

[JBoss JIRA] (AS7-3464) add-user.sh - possibility of setting another Realms should be considered again

by Rajesh Rajasekaran (JIRA)

[ https://issues.jboss.org/browse/AS7-3464?page=com.atlassian.jira.plugin.s... ] Rajesh Rajasekaran updated AS7-3464: ------------------------------------ Priority: Minor (was: Critical) add-user.sh is just to get the user quickly started with the admin console. Adding new security realms would be managed by the admin console or CLI. The UI installer for EAP6 will bypass the add-user script and provide functionality in the installer for adding user. > add-user.sh - possibility of setting another Realms should be considered again > ------------------------------------------------------------------------------ > > Key: AS7-3464 > URL: https://issues.jboss.org/browse/AS7-3464 > Project: Application Server 7 > Issue Type: Bug > Components: Security > Affects Versions: 7.1.0.CR1b > Reporter: Pavel Janousek > Assignee: Anil Saldhana > Priority: Minor > > I'm aware of add-user.sh isn't general tool for managing an user/groups/roles credential store at all. Is it supposed only as shorthand for quick definition of users access to admin console out of the box. Well.. > According previous paragraph it isn't to much meaningful for me to bring possibility of specify another realm during the invocation of this tool. I think already - Admin console can use another realm than ManagementRealm by change default configuration. I think already too - property file can't contain users definition belong multiple realms. As is stated in comment in the begin of file mgmt-users.properties, this file is for "declaration of users for the realm 'ManagementRealm'". > I think we should avoid to insert new user with different realm there (it is possible now). add-user.sh doesn't manage any other file and other property file(s) can't be specified during invocation. > I think this present situation/behavior should confuse hard our end-users - especially users with their own experiences with other JEE servers (Apache Geronimo, Sun/Oracle GlassFish etc.). > Because we don't provide/support any tool for general CRUD managing of credential store of type like property file(s) - like other JEE app. servers do, we really should use this script/tool only as way to simple very basic user creation in default AS7 environment, because we can't support this tool in any other situation with present behavior and in a such changed environments behavior or final state is hardly understandable (if we create property file (by other way) with the same username, but in different realms, we can't log to admin console never more; if we have users in one realm, switch AS7 instance to use other "admin" realm, we can't add any from existing user to this new realm; we don't know which user belongs to which realm later etc.) > So conclusion - I think we should remove specification of Realm from input process of add-user.sh script at all and use this script only to define users belongs to ManagementRealm realm and manages only properly mgmt-users.properties files (standalone and domain configuration) -- 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-3470) ChannelService and dependent services should start asynchronously

by Paul Ferraro (JIRA)

Paul Ferraro created AS7-3470: --------------------------------- Summary: ChannelService and dependent services should start asynchronously Key: AS7-3470 URL: https://issues.jboss.org/browse/AS7-3470 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.1.0.CR1b Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 7.1.0.Final Otherwise, the MSC service thread pool can dry up. ChannelService.getValue() should block on availability of started channel. Same async start logic should be applied to dependent services. -- 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-3447) IllegalStateException when Query Cache is enabled

by Zbyněk Roubalík (JIRA)

Zbyněk Roubalík created AS7-3447: ------------------------------------ Summary: IllegalStateException when Query Cache is enabled Key: AS7-3447 URL: https://issues.jboss.org/browse/AS7-3447 Project: Application Server 7 Issue Type: Bug Components: JPA / Hibernate Affects Versions: 7.1.0.CR1b Reporter: Zbyněk Roubalík Assignee: Scott Marlow Fix For: 7.1.0.Final I've updated AS7 sources from master branch, then enabled Query cache in [SecondLevelCacheTestCase|https://github.com/jbossas/jboss-as/blob/master/...] (put <property name="hibernate.cache.use_query_cache" value="true"/> in persistence.xml) and then got IllegalStateException. This tests passes but the exception can be found in server.log: ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (pool-4-thread-1) ISPN000136: Execution error: java.lang.IllegalStateException: Transaction TransactionImple < ac, BasicAction: 0:ffff7f000001:cbbd222:4f1f2b9a:8 status: ActionStatus.COMMITTED > is not in a valid state to be invoking cache operations on. server output: http://pastebin.com/xMZEuMp1 When Query cache is disabled, everything is OK. -- 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
4
0 / 0

[JBoss JIRA] (AS7-3466) Inconsistency in --help output between domain and standalone

by Rostislav Svoboda (JIRA)

Rostislav Svoboda created AS7-3466: -------------------------------------- Summary: Inconsistency in --help output between domain and standalone Key: AS7-3466 URL: https://issues.jboss.org/browse/AS7-3466 Project: Application Server 7 Issue Type: Bug Components: Scripts Affects Versions: 7.1.0.CR1b Reporter: Rostislav Svoboda Assignee: Brian Stansberry Fix For: 7.1.0.Final Help for standalone.sh is using logging infrastructure and help for domain.sh is probably using just stdout. - I'd prefer to use domain.sh way without '16:42:57,124 INFO [stdout]' details. Please sync output for both commands. - There is typo in help for standalone.sh, it says '\-\-\-\-server-config=<config>', '\-' should be there just twice. {code} bin/domain.sh --help ... --admin-only JBAS012066: Set the host controller's running type to ADMIN_ONLY causing it to open administrative interfaces and accept management requests but not start servers or, if this host controller is the master for the domain, accept incoming connections from slave host controllers. ... bin/standalone.sh --help ... 16:42:57,124 INFO [stdout] --admin-only Set the server's running type to 16:42:57,124 INFO [stdout] ADMIN_ONLY causing it to open 16:42:57,124 INFO [stdout] administrative interfaces and accept 16:42:57,124 INFO [stdout] management requests but not start other 16:42:57,124 INFO [stdout] runtime services or accept end user 16:42:57,124 INFO [stdout] requests. ... {code} -- 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-2670) Interface constraints not properly handled

by Heiko Braun (Created) (JIRA)

Interface constraints not properly handled ------------------------------------------ Key: AS7-2670 URL: https://issues.jboss.org/browse/AS7-2670 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Heiko Braun Assignee: Emanuel Muckenhuber Fix For: 7.1.0.CR1 I would think this combination is valid, but it leads to "JBAS014696: any-address is invalid in combination with any-ipv4-address, any-ipv6-address" {noformat} [INFO] "steps" => [ [INFO] { [INFO] "address" => [("interface" => "management")], [INFO] "operation" => "write-attribute", [INFO] "name" => "inet-address", [INFO] "value" => undefined [INFO] }, [INFO] { [INFO] "address" => [("interface" => "management")], [INFO] "operation" => "write-attribute", [INFO] "name" => "any-address", [INFO] "value" => false [INFO] }, [INFO] { [INFO] "address" => [("interface" => "management")], [INFO] "operation" => "write-attribute", [INFO] "name" => "any-ipv6-address", [INFO] "value" => true [INFO] }, [INFO] { [INFO] "address" => [("interface" => "management")], [INFO] "operation" => "write-attribute", [INFO] "name" => "any-ipv4-address", [INFO] "value" => false [INFO] } [INFO] ] [INFO] } {noformat} -- 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2012