July 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-873) PicketBox 4.0.9.Final

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-873: ------------------------------------- Summary: PicketBox 4.0.9.Final Key: JBJCA-873 URL: https://issues.jboss.org/browse/JBJCA-873 Project: IronJacamar Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.12.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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-871) JBoss Logging Processor 1.0.3.Final

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-871: ------------------------------------- Summary: JBoss Logging Processor 1.0.3.Final Key: JBJCA-871 URL: https://issues.jboss.org/browse/JBJCA-871 Project: IronJacamar Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.12.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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-872) JBoss LogManager 1.3.1.GA

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-872: ------------------------------------- Summary: JBoss LogManager 1.3.1.GA Key: JBJCA-872 URL: https://issues.jboss.org/browse/JBJCA-872 Project: IronJacamar Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.12.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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-870) JBoss Logging 3.1.1.GA

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-870: ------------------------------------- Summary: JBoss Logging 3.1.1.GA Key: JBJCA-870 URL: https://issues.jboss.org/browse/JBJCA-870 Project: IronJacamar Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.12.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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-869) Track component updates

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-869: ------------------------------------- Summary: Track component updates Key: JBJCA-869 URL: https://issues.jboss.org/browse/JBJCA-869 Project: IronJacamar Issue Type: Task Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.12.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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-5067) CLONE - CLI deploy with --name fails to deploy subdeployments

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/AS7-5067?page=com.atlassian.jira.plugin.s... ] Alexey Loubyansky updated AS7-5067: ----------------------------------- Component/s: Domain Management (was: CLI) It's the runtime-name issue. This deploy simpleejb3.ear --name=b --runtime-name=simpleejb3.ear will work. But if the runtime-name doesn't match the filename, happens what's described in the summary. > CLONE - CLI deploy with --name fails to deploy subdeployments > ------------------------------------------------------------- > > Key: AS7-5067 > URL: https://issues.jboss.org/browse/AS7-5067 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.1.2.Final (EAP) > Reporter: Tom Fonteyne > Assignee: Alexey Loubyansky > Priority: Minor > Attachments: simpleejb3.ear > > > I have an ear file with inside a jar file with an ejb. > Use the CLI to deploy with: > > deploy simpleejb3.ear > In the console log: > 12:22:42,130 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "simpleejb3.ear" > 12:22:42,174 INFO [org.jboss.as.server.deployment] (MSC service thread 1-16) JBAS015876: Starting deployment of "simpleejb3-ejb.jar" > 12:22:42,293 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-5) JNDI bindings for session bean named sbean in deployment unit subdeployment "simpleejb3-ejb.jar" of deployment "simpleejb3.ear" are as follows: > java:global/simpleejb3/simpleejb3-ejb/sbean!tf.sbeanLocal > java:app/simpleejb3-ejb/sbean!tf.sbeanLocal > java:module/sbean!tf.sbeanLocal > java:global/simpleejb3/simpleejb3-ejb/sbean!tf.sbeanRemote > java:app/simpleejb3-ejb/sbean!tf.sbeanRemote > java:module/sbean!tf.sbeanRemote > java:jboss/exported/simpleejb3/simpleejb3-ejb/sbean!tf.sbeanRemote > and the bean will work. > Now undeploy fully (+ restarted) and deploy again with: > > deploy simpleejb3.ear --name=b > and the log : > 12:23:41,300 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "b" > 12:23:41,431 INFO [org.jboss.as.osgi] (MSC service thread 1-4) JBAS011907: Register module: Module "deployment.b:main" from Service Module Loader > 12:23:41,598 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018559: Deployed "b" > A test showed that the EJB was indeed not deployed/accessible. -- 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (HIBERNATE-135) Hibernate 2LC - Infinispan: Query-cache expiration depends on namedCache name

by Anna Manukyan (JIRA)

Anna Manukyan created HIBERNATE-135: --------------------------------------- Summary: Hibernate 2LC - Infinispan: Query-cache expiration depends on namedCache name Key: HIBERNATE-135 URL: https://issues.jboss.org/browse/HIBERNATE-135 Project: Hibernate Integration Issue Type: Bug Reporter: Anna Manukyan Assignee: Steve Ebersole Hi, I'm writing arquillian tests for Infinispan as a Hibernate 2LC and during writing tests for cache expiration case, I've found out an issue which I cannot explain. I'm running tests under Arquillian AS7 managed container. The tests are using external infinispan configuration (not AS7 subsystem). Here I'm defining 2 named caches, one for Hibernate entities another for query cache. <namedCache name="local-query"> <locking isolationLevel="READ_COMMITTED" concurrencyLevel="1000" lockAcquisitionTimeout="15000" useLockStriping="false"/> <eviction maxEntries="10000" strategy="LRU"/> <expiration lifespan="5000" maxIdle="5000" wakeUpInterval="2000" /> </namedCache> <namedCache name="local-entity"> <locking isolationLevel="READ_COMMITTED" concurrencyLevel="1000" lockAcquisitionTimeout="15000" useLockStriping="false"/> <eviction maxEntries="10000" strategy="LRU"/> <expiration maxIdle="5000" wakeUpInterval="2000" lifespan="5000"/> </namedCache> In the tests I'm accessing the InfinispanRegionFactory using EntityManager's SessionFactory. From here I am able to access my cache regions. When I'm looking through all available regions I can see that the data is stored in the prefixed regions, so e.g. for my app the queries and entities are stored in testable.war#hib2Lc.local-query and testable.war#hib2Lc.local-entity caches. When I'm testing the expiration for "local-query" cache, i.e. I'm performing a query, I'm checking that the query is placed tothe cache. Then I'm waiting for 5 seconds (as it is set in configuration), then I'm checking the cache again and the query is still there. It is not removed from the cache, although it should be expired already. When I'm changing the namedCache name from "local-query" to "testable.war#hib2Lc.local-query", this time the expiration works properly so the second time check succeeds. The same case works without namedCache name change for entity cache. You can find the tests located here: https://github.com/andyuk1986/ispn-hibernate2lc-tests/tree/master/hiberna... - the test is located here: https://github.com/andyuk1986/ispn-hibernate2lc-tests/blob/master/hiberna... I'm using infinispan-core-5.1.2.FINAL, hibernate-core-4.1.3.Final, hibernate-infinispan-4.1.3.Final. Thanks in advance. Best regards, Anna. -- 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-678) Release JBoss Negotiation 2.2.1

by Darran Lofthouse (JIRA)

Darran Lofthouse created SECURITY-678: ----------------------------------------- Summary: Release JBoss Negotiation 2.2.1 Key: SECURITY-678 URL: https://issues.jboss.org/browse/SECURITY-678 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2_2_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

13 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-610) The continuation of SPNEGO requests causes a 'Login failure' error to be reported.

by Darran Lofthouse (JIRA)

The continuation of SPNEGO requests causes a 'Login failure' error to be reported. ---------------------------------------------------------------------------------- Key: SECURITY-610 URL: https://issues.jboss.org/browse/SECURITY-610 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2.2.0 The continuation from the login module now causes the following error to be logged: - 12:46:42,245 ERROR [org.jboss.security.authentication.JBossCachedAuthenticationManager] (http--10.36.4.52-8080-1) Login failure: javax.security.auth.login.LoginException: Continuation Required. at org.jboss.security.negotiation.spnego.SPNEGOLoginModule.login(SPNEGOLoginModule.java:174) [jboss-negotiation-2.2.0.SNAPSHOT.jar:2.2.0.SNAPSHOT] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_24] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_24] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_24] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_24] at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769) [:1.6.0_24] at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186) [:1.6.0_24] at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683) [:1.6.0_24] at java.security.AccessController.doPrivileged(Native Method) [:1.6.0_24] at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680) [:1.6.0_24] at javax.security.auth.login.LoginContext.login(LoginContext.java:579) [:1.6.0_24] at org.jboss.security.authentication.JBossCachedAuthenticationManager.defaultLogin(JBossCachedAuthenticationManager.java:411) [picketbox-infinispan-4.0.1.jar:4.0.1] at org.jboss.security.authentication.JBossCachedAuthenticationManager.authenticate(JBossCachedAuthenticationManager.java:345) [picketbox-infinispan-4.0.1.jar:4.0.1] at org.jboss.security.authentication.JBossCachedAuthenticationManager.isValid(JBossCachedAuthenticationManager.java:154) [picketbox-infinispan-4.0.1.jar:4.0.1] at org.jboss.as.web.security.JBossWebRealm.authenticate(JBossWebRealm.java:127) [jboss-as-web-7.1.0.Alpha1-SNAPSHOT.jar:7.1.0.Alpha1-SNAPSHOT] at org.jboss.security.negotiation.NegotiationAuthenticator.authenticate(NegotiationAuthenticator.java:187) [jboss-negotiation-2.2.0.SNAPSHOT.jar:2.2.0.SNAPSHO Bringing Kerberos to the domain management security is going to require some of the same behaviour as we have in the SPNEGOLoginModule - it may make sense to pull this common behaviour out of the login module anyway for consistency - this would also remove the exception being logged here. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
4
0 / 0

[JBoss JIRA] (AS7-5274) Messaging transport parameters does not allow expressions

by Jeff Mesnil (JIRA)

Jeff Mesnil created AS7-5274: -------------------------------- Summary: Messaging transport parameters does not allow expressions Key: AS7-5274 URL: https://issues.jboss.org/browse/AS7-5274 Project: Application Server 7 Issue Type: Feature Request Components: JMS Affects Versions: 7.1.2.Final (EAP) Reporter: Jeff Mesnil Assignee: Jeff Mesnil Messaging transport parameters (used by xxx-connector and xxx-acceptor elements) does not allow expressions. This prevents to use masked passwords for its values when setting up SSL (e.g. key-store-password and trust-store-password parameter). -- 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

13 years, 11 months

1
1
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 July 2012