January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1561) <distributable> web applications fail to deploy with the DOMAIN HA configuration

by Riccardo Pasquini (JIRA)

<distributable> web applications fail to deploy with the DOMAIN HA configuration -------------------------------------------------------------------------------- Key: AS7-1561 URL: https://issues.jboss.org/browse/AS7-1561 Project: Application Server 7 Issue Type: Bug Components: Web Affects Versions: 7.0.0.Final, 7.1.0.Alpha1 Environment: riccardo@7suse:~> uname -a Linux 7suse.localhost 2.6.37.6-0.7-desktop #1 SMP PREEMPT 2011-07-21 02:17:24 +0200 x86_64 x86_64 x86_64 GNU/Linux riccardo@7suse:~> java -version java version "1.6.0_26" Java(TM) SE Runtime Environment (build 1.6.0_26-b03) Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode) Reporter: Riccardo Pasquini Assignee: Remy Maucherat Using the console to deploy a web application packaged as WAR and described as <distributable /> fails on enabling in the server group with the following message: Failed to disable Webapp-0.1-SNAPSHOT.war. Unexpected HTTP response: 500 Request { "address" => [ ("server-group" => "dragon-standalone"), ("deployment" => "Webapp-0.1-SNAPSHOT.war") ], "operation" => "deploy" } Response Internal Server Error { "outcome" => "failed", "result" => {"server-groups" => [("dragon-standalone" => {"master" => { "host" => "master", "response" => { "outcome" => "failed", "failure-description" => "Operation handler failed to complete", "rolled-back" => true } }})]}, "failure-description" => "Operation failed or was rolled back on all servers.", "rolled-back" => true } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

4
6
0 / 0

[JBoss JIRA] Created: (AS7-1658) Referencing a remote business view within the same server leads to CCE

by Carlo de Wolf (JIRA)

Referencing a remote business view within the same server leads to CCE ---------------------------------------------------------------------- Key: AS7-1658 URL: https://issues.jboss.org/browse/AS7-1658 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.0.1.Final Reporter: Carlo de Wolf Assignee: Carlo de Wolf Priority: Critical Fix For: 7.1.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

5
11
0 / 0

[JBoss JIRA] (AS7-2929) Add support for unscheduled write-behind cache stores to Infinispan subsytem

by Martin Gencur (Created) (JIRA)

Add support for unscheduled write-behind cache stores to Infinispan subsytem ---------------------------------------------------------------------------- Key: AS7-2929 URL: https://issues.jboss.org/browse/AS7-2929 Project: Application Server 7 Issue Type: Feature Request Components: Clustering Reporter: Martin Gencur Assignee: Tristan Tarrant Infinispan subsystem should support unscheduled write-behind cache stores. Currently it is not possible to set this up. In Infinispan this is done via <async> sub-element of <loader> element. E.g. <async enabled="true" threadPoolSize="10" /> Documentation for EDG is mentioning both unscheduled and scheduled write-behind cache stores even though scheduled one is not implemented even in Infinispan (ISPN-328). OTOH, the unscheduled one is implemented and should be available in EDG. So take into account that in future there might be also scheduled write-behind store available and infinispan schema for JBossAS should count with that. -- 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

14 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (AS7-1182) DatabaseServerLoginModule doesn't work

by Juergen Zimmermann (JIRA)

DatabaseServerLoginModule doesn't work -------------------------------------- Key: AS7-1182 URL: https://issues.jboss.org/browse/AS7-1182 Project: Application Server 7 Issue Type: Bug Components: Security Affects Versions: 7.0.0.CR1 Reporter: Juergen Zimmermann I want to migrate from JBossAS 6 to 7.0.0.CR1. In standalone.xml I declare the following security domain, but get the stacktrace (see below) looking for UsersRolesLoginModule instead of DatabaseServerLoginModule. Security domain in standalone.xml: <security-domain name="swe2" cache-type="default"> <authentication> <login-module code="Database" flag="required"> <module-option name="dsJndiName" value="java:/swe2DS"/> <module-option name="unauthenticatedIdentity" value="gast"/> <module-option name="principalsQuery" value="SELECT password FROM kunde WHERE username=?"/> <module-option name="rolesQuery" value="SELECT role, 'Roles' FROM swe2_role r INNER JOIN kunde k ON r.kunde_fk = k.k_id WHERE k.username=?"/> <module-option name="hashAlgorithm" value="SHA-1"/> <module-option name="hashEncoding" value="base64"/> </login-module> </authentication> </security-domain> Stacktrace regarding UsersRolesLoginModule (instead of DatabaseServerLoginModule): 16:03:58,528 ERROR [org.jboss.security.auth.spi.UsersRolesLoginModule] (http--127.0.0.1-8080-2) Failed to load users/passwords/role files: java.io.IOException: No properties file: users.properties or defaults: defaultUsers.properties found at org.jboss.security.auth.spi.Util.loadProperties(Util.java:227) [picketbox-4.0.0.CR1.jar:4.0.0.CR1] at org.jboss.security.auth.spi.UsersRolesLoginModule.loadUsers(UsersRolesLoginModule.java:188) [picketbox-4.0.0.CR1.jar:4.0.0.CR1] at org.jboss.security.auth.spi.UsersRolesLoginModule.createUsers(UsersRolesLoginModule.java:202) [picketbox-4.0.0.CR1.jar:4.0.0.CR1] at org.jboss.security.auth.spi.UsersRolesLoginModule.initialize(UsersRolesLoginModule.java:129) [picketbox-4.0.0.CR1.jar:4.0.0.CR1] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_26] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_26] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_26] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_26] at javax.security.auth.login.LoginContext.invoke(LoginContext.java:756) [:1.6.0_26] at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186) [:1.6.0_26] at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683) [:1.6.0_26] at java.security.AccessController.doPrivileged(Native Method) [:1.6.0_26] at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680) [:1.6.0_26] at javax.security.auth.login.LoginContext.login(LoginContext.java:579) [:1.6.0_26] at org.jboss.security.authentication.JBossCachedAuthenticationManager.defaultLogin(JBossCachedAuthenticationManager.java:411) [picketbox-infinispan-4.0.0.CR1.jar:4.0.0.CR1] at org.jboss.security.authentication.JBossCachedAuthenticationManager.authenticate(JBossCachedAuthenticationManager.java:345) [picketbox-infinispan-4.0.0.CR1.jar:4.0.0.CR1] at org.jboss.security.authentication.JBossCachedAuthenticationManager.isValid(JBossCachedAuthenticationManager.java:154) [picketbox-infinispan-4.0.0.CR1.jar:4.0.0.CR1] at org.jboss.as.web.security.JBossWebRealm.authenticate(JBossWebRealm.java:127) [jboss-as-web-7.0.0.CR1.jar:7.0.0.CR1] at org.apache.catalina.authenticator.BasicAuthenticator.authenticate(BasicAuthenticator.java:180) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1] at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:446) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1] at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.0.0.CR1.jar:7.0.0.CR1] at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:49) [jboss-as-jpa-7.0.0.CR1.jar:7.0.0.CR1] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1] at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:893) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1] at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:626) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1] at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:2054) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1] at java.lang.Thread.run(Thread.java:662) [:1.6.0_26] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

5
16
0 / 0

[JBoss JIRA] (JBWEB-226) Prevent Web Crawlers from creating many sessions

by Jason Shepherd (JIRA)

Jason Shepherd created JBWEB-226: ------------------------------------ Summary: Prevent Web Crawlers from creating many sessions Key: JBWEB-226 URL: https://issues.jboss.org/browse/JBWEB-226 Project: JBoss Web Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Core Reporter: Jason Shepherd Assignee: Remy Maucherat Priority: Minor This feature solve the same problem as the Tomcat 7 CrawlerSessionManagerValve, described here [1]. Also the source code for the Valve is available here, [2]. Jean-Frederic has suggested it would be better implement this as a filter instead of a valve. [1] http://www.tomcatexpert.com/blog/2011/05/18/crawler-session-manager-valve [2] http://svn.apache.org/repos/asf/tomcat/tc7.0.x/trunk/java/org/apache/cata... -- 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

14 years, 1 month

2
2
0 / 0

[JBoss JIRA] (AS7-2800) JMX via JNDI not working

by Savas Ali Tokmen (Created) (JIRA)

JMX via JNDI not working ------------------------ Key: AS7-2800 URL: https://issues.jboss.org/browse/AS7-2800 Project: Application Server 7 Issue Type: Bug Components: JMX Affects Versions: 7.1.0.Beta1 Reporter: Savas Ali Tokmen Assignee: John Bailey Fix For: 7.1.0.CR1, 7.1.0.Final The documentation on https://docs.jboss.org/author/display/AS7/JMX+subsystem+configuration as well as the testcase jmx/src/test/java/org/jboss/as/jmx/JMXSubsystemTestCase.java seems to indicate that the JMX URL service:jmx:rmi:///jndi/rmi://localhost:1090/jmxrmi should be accessible via a JMX console (for example, the jconsole). When I open: {noformat} jconsole service:jmx:rmi:///jndi/rmi://localhost:1090/jmxrmi {noformat} I get an error message saying: "the connection to service:jmx:rmi:///jndi/rmi://localhost:1090/jmxrmi did not succeed". -- 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

14 years, 1 month

6
7
0 / 0

[JBoss JIRA] Created: (AS7-1722) dropped message WARNING on node leaving a group

by Radoslav Husar (JIRA)

dropped message WARNING on node leaving a group ----------------------------------------------- Key: AS7-1722 URL: https://issues.jboss.org/browse/AS7-1722 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.0.1.Final, 7.0.0.Final Reporter: Radoslav Husar Assignee: Paul Ferraro On node leaving the group there is a warning {code} 17:57:31,340 INFO [org.jboss.as.clustering.CoreGroupCommunicationService.lifecycle.web] (Incoming-13,web,rhusar-7808) New cluster view for partition web (id: 4, delta: -1, merge: false) : [rhusar-7808] 17:57:31,340 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-13,web,rhusar-7808) ISPN000094: Received new cluster view: [rhusar-7808|4] [rhusar-7808] 17:57:31,345 WARNING [org.jgroups.protocols.pbcast.NAKACK] (Incoming-15,web,rhusar-7808) rhusar-7808: dropped message from rhusar-41106 (not in table [rhusar-7808]), view=[rhusar-7808|4] [rhusar-7808] {code} because it removes the member before receiving the last message {code} 17:57:31,286 INFO [org.jboss.as.clustering.infinispan.subsystem] Stopped repl cache from web container 17:57:31,290 INFO [jacorb.orb] prepare ORB for shutdown... 17:57:31,290 INFO [jacorb.orb] ORB going down... 17:57:31,305 INFO [jacorb.orb.iiop] Listener exited 17:57:31,310 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] ISPN000080: Disconnecting and closing JGroups Channel 17:57:31,312 INFO [org.hornetq.core.server.impl.HornetQServerImpl] HornetQ Server version 2.2.7.Final (HQ_2_2_7_FINAL_AS7, 121) [8ee2c584-d740-11e0-ad66-0022fabb0b50] stopped 17:57:31,310 INFO [jacorb.orb] ORB shutdown complete 17:57:31,313 INFO [jacorb.orb] ORB run, exit 17:57:31,349 INFO [org.jboss.as.server.deployment] Stopped deployment SessionTest-2.0-SNAPSHOT.war in 197ms 17:57:31,636 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] ISPN000082: Stopping the RpcDispatcher 17:57:31,637 INFO [com.arjuna.ats.jbossatx] ARJUNA32018: Destroying TransactionManagerService 17:57:31,638 INFO [com.arjuna.ats.jbossatx] ARJUNA32014: Stopping transaction recovery manager {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
3
0 / 0

[JBoss JIRA] (AS7-2407) Cannot connect to domain controller - more detail needed

by Kevin Barfield (Created) (JIRA)

Cannot connect to domain controller - more detail needed -------------------------------------------------------- Key: AS7-2407 URL: https://issues.jboss.org/browse/AS7-2407 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Kevin Barfield Assignee: Brian Stansberry There needs to be more detail when a host controller can't connect to a domain controller. Several times we saw the "cannot connect to the domain controller" message when we knew the two servers could see each other. The host tried 5-6 times to connect then shut down. There were no other messages on the host or domain controller with more detail (even at DEBUG logging level). We could stop the domain controller while the host was trying to connect and we would see an immediate error message on the host. -- 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

14 years, 1 month

4
4
0 / 0

[JBoss JIRA] (AS7-2432) CLI does not allow a new security-realm to be defined within the management section of a host

by Rich Raposa (Created) (JIRA)

CLI does not allow a new security-realm to be defined within the management section of a host --------------------------------------------------------------------------------------------- Key: AS7-2432 URL: https://issues.jboss.org/browse/AS7-2432 Project: Application Server 7 Issue Type: Bug Components: CLI Reporter: Rich Raposa Assignee: Alexey Loubyansky The CLI does not allow for attributes to be defined when adding a new security realm at the host=master/core-service=management level. To replicate, enter the following command in the CLI: /host=master/core-service=management/security-realm=MyDomainRealm:add() Within the add() operation I need to define an <authentication> section, but the CLI will not allow it. The message is: Operation 'add' does not expect any property. -- 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

14 years, 1 month

7
15
0 / 0

[JBoss JIRA] Created: (JASSIST-44) Maven profiles for tools.jar should take account of Mac OS

by Martin Burger (JIRA)

Maven profiles for tools.jar should take account of Mac OS ---------------------------------------------------------- Key: JASSIST-44 URL: http://jira.jboss.com/jira/browse/JASSIST-44 Project: Javassist Issue Type: Bug Environment: Maven version: 2.0.8 Java version: 1.5.0_13 OS name: "mac os x" version: "10.4.11" arch: "i386" Family: "unix" Reporter: Martin Burger Assigned To: Shigeru Chiba The pom.xml uses different profiles to add the tools.jar to the dependencies. However, it is already included in the runtime for Mac OS X and some free JDKs and does not exist as a separate file 'tools.jar'. See: http://maven.apache.org/general.html#tools-jar-dependency As soon as http://jira.codehaus.org/browse/MNG-3106 gets fixed, activation should look like the following example: <activation> <jdk>1.6</jdk> <property> <name>java.vendor</name> <value>Sun Microsystems Inc.</value> </property> </activation> In the meantime <profiles> <profile> <id>tools.jar</id> <activation> <property> <name>java.vendor</name> <value>Sun Microsystems Inc.</value> </property> </activation> <dependencies> <dependency> <groupId>com.sun</groupId> <artifactId>tools</artifactId> <version>1.6</version> <scope>system</scope> <optional>true</optional> <systemPath>${java.home}/../lib/tools.jar</systemPath> </dependency> </dependencies> </profile> </profiles> should do the job. It could be a permanent solution because the different profiles differ only in the version element. -- 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, 1 month

2
5
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 January 2012