October 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5464) RESTeasy component integration is not limited to EJB's and managed beans

by Stuart Douglas (JIRA)

Stuart Douglas created AS7-5464: ----------------------------------- Summary: RESTeasy component integration is not limited to EJB's and managed beans Key: AS7-5464 URL: https://issues.jboss.org/browse/AS7-5464 Project: Application Server 7 Issue Type: Bug Components: REST Affects Versions: 7.1.2.Final (EAP) Reporter: Stuart Douglas Assignee: Stuart Douglas The RESTeasy component integration processor can pick up other component types such as web services components. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
1
0 / 0

[JBoss JIRA] (AS7-4127) Intermittent failure in RemotingSubsystemTestCase.testSubsystemWithConnectorPropertyChange()

by Ondrej Zizka (JIRA)

Ondrej Zizka created AS7-4127: --------------------------------- Summary: Intermittent failure in RemotingSubsystemTestCase.testSubsystemWithConnectorPropertyChange() Key: AS7-4127 URL: https://issues.jboss.org/browse/AS7-4127 Project: Application Server 7 Issue Type: Bug Reporter: Ondrej Zizka Spotted in https://hudson.qa.jboss.com/hudson/view/ESSC/job/AS7-TS-valid-default/las... {code} junit.framework.AssertionFailedError: expected not same at junit.framework.Assert.fail(Assert.java:50) at junit.framework.Assert.failSame(Assert.java:276) at junit.framework.Assert.assertNotSame(Assert.java:262) at junit.framework.Assert.assertNotSame(Assert.java:269) at org.jboss.as.remoting.RemotingSubsystemTestCase$CurrentConnectorAndController.checkStatus(RemotingSubsystemTestCase.java:333) at org.jboss.as.remoting.RemotingSubsystemTestCase$CurrentConnectorAndController.updateCurrentConnector(RemotingSubsystemTestCase.java:327) at org.jboss.as.remoting.RemotingSubsystemTestCase.testSubsystemWithConnectorPropertyChange(RemotingSubsystemTestCase.java:186) {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

13 years, 1 month

3
12
0 / 0

[JBoss JIRA] (AS7-3632) Re-enable RemotingSubsystemTestCase.testSubsystemWithBadConnectorProperty

by Tomaz Cerar (JIRA)

Tomaz Cerar created AS7-3632: -------------------------------- Summary: Re-enable RemotingSubsystemTestCase.testSubsystemWithBadConnectorProperty Key: AS7-3632 URL: https://issues.jboss.org/browse/AS7-3632 Project: Application Server 7 Issue Type: Task Affects Versions: 7.1.0.Final Environment: jenkins Reporter: Tomaz Cerar Assignee: Tomaz Cerar testSubsystemWithBadConnectorProperty test randomly fails on some enviroments. until this is resolved test is marked as @Ignored -- 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, 1 month

2
2
0 / 0

[JBoss JIRA] (AS7-5699) Exception in thread "KeyAffinityService Thread Pool -- 1" java.lang.ArrayIndexOutOfBoundsException: 1

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-5699: ----------------------------------- Summary: Exception in thread "KeyAffinityService Thread Pool -- 1" java.lang.ArrayIndexOutOfBoundsException: 1 Key: AS7-5699 URL: https://issues.jboss.org/browse/AS7-5699 Project: Application Server 7 Issue Type: Bug Components: Clustering Environment: affects: snapshot Reporter: Radoslav Husar Assignee: Paul Ferraro Fix For: 7.2.0.Alpha1 After ISPN upgrade. {noformat} 23:20:16,415 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "distributable.war" 23:20:16,424 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /home/smarlow/work/as7/testsuite/integration/clust/target/jbossas-clustering-SYNC-tcp-0/standalone/deployments 23:20:16,767 WARN [org.jgroups.stack.Configurator] (ServerService Thread Pool -- 63) [JGRP00013] TP.discard_incompatible_packets has been deprecated: incompatible packets are discarded anyway 23:20:16,957 INFO [stdout] (ServerService Thread Pool -- 63) 23:20:16,957 INFO [stdout] (ServerService Thread Pool -- 63) ------------------------------------------------------------------- 23:20:16,957 INFO [stdout] (ServerService Thread Pool -- 63) GMS: address=node-0/web, cluster=web, physical address=fccc:0:0:0:0:0:0:1%1:7600 23:20:16,957 INFO [stdout] (ServerService Thread Pool -- 63) ------------------------------------------------------------------- 23:20:17,104 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. 23:20:17,105 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-6) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. 23:20:17,106 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. 23:20:17,106 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-6) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. 23:20:17,107 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-4) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. 23:20:17,108 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-4) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. 23:20:17,136 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 63) ISPN000078: Starting JGroups Channel 23:20:17,140 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 63) ISPN000094: Received new cluster view: [node-1/web|3] [node-1/web, node-0/web] 23:20:17,140 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 63) ISPN000079: Cache local address is node-0/web, physical addresses are [fccc:0:0:0:0:0:0:1%1:7600] 23:20:17,141 INFO [org.infinispan.factories.GlobalComponentRegistry] (ServerService Thread Pool -- 63) ISPN000128: Infinispan version: Infinispan 'Delirium' 5.2.0.Beta1 23:20:17,164 INFO [org.infinispan.factories.TransactionManagerFactory] (ServerService Thread Pool -- 56) ISPN000161: Using a batchMode transaction manager 23:20:17,164 INFO [org.infinispan.factories.TransactionManagerFactory] (ServerService Thread Pool -- 63) ISPN000161: Using a batchMode transaction manager 23:20:17,274 INFO [org.infinispan.jmx.CacheJmxRegistration] (ServerService Thread Pool -- 56) ISPN000031: MBeans were successfully registered to the platform MBean server. 23:20:17,274 INFO [org.infinispan.jmx.CacheJmxRegistration] (ServerService Thread Pool -- 63) ISPN000031: MBeans were successfully registered to the platform MBean server. 23:20:17,394 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 56) JBAS010281: Started default-host/distributable cache from web container 23:20:17,396 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 63) JBAS010281: Started repl cache from web container 23:20:17,405 INFO [org.jboss.as.clustering] (MSC service thread 1-5) JBAS010238: Number of cluster members: 2 23:20:17,414 INFO [org.jboss.web] (MSC service thread 1-7) JBAS018210: Register web context: /distributable 23:20:17,533 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS018559: Deployed "distributable.war" 23:20:17,688 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://fccc::1:9990/management 23:20:17,689 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://fccc::1:9990 23:20:17,689 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes" started in 3445ms - Started 171 of 324 services (152 services are passive or on-demand) 23:54:12,922 ERROR [stderr] (KeyAffinityService Thread Pool -- 1) Exception in thread "KeyAffinityService Thread Pool -- 1" java.lang.ArrayIndexOutOfBoundsException: 1 23:54:12,923 ERROR [stderr] (KeyAffinityService Thread Pool -- 1) at org.infinispan.distribution.ch.DefaultConsistentHash.locatePrimaryOwnerForSegment(DefaultConsistentHash.java:137) 23:54:12,923 ERROR [stderr] (KeyAffinityService Thread Pool -- 1) at org.infinispan.distribution.ch.DefaultConsistentHash.locatePrimaryOwner(DefaultConsistentHash.java:152) 23:54:12,923 ERROR [stderr] (KeyAffinityService Thread Pool -- 1) at org.infinispan.affinity.KeyAffinityServiceImpl.getAddressForKey(KeyAffinityServiceImpl.java:347) 23:54:12,924 ERROR [stderr] (KeyAffinityService Thread Pool -- 1) at org.infinispan.affinity.KeyAffinityServiceImpl.access$700(KeyAffinityServiceImpl.java:59) 23:54:12,924 ERROR [stderr] (KeyAffinityService Thread Pool -- 1) at org.infinispan.affinity.KeyAffinityServiceImpl$KeyGeneratorWorker.generateKeys(KeyAffinityServiceImpl.java:270) 23:54:12,924 ERROR [stderr] (KeyAffinityService Thread Pool -- 1) at org.infinispan.affinity.KeyAffinityServiceImpl$KeyGeneratorWorker.run(KeyAffinityServiceImpl.java:242) 23:54:12,925 ERROR [stderr] (KeyAffinityService Thread Pool -- 1) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) 23:54:12,925 ERROR [stderr] (KeyAffinityService Thread Pool -- 1) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) 23:54:12,925 ERROR [stderr] (KeyAffinityService Thread Pool -- 1) at java.lang.Thread.run(Thread.java:662) 23:54:12,925 ERROR [stderr] (KeyAffinityService Thread Pool -- 1) at org.jboss.threads.JBossThread.run(JBossThread.java:122) {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

3
14
0 / 0

[JBoss JIRA] (JBJCA-905) Arquillian/Remote support

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-905: ------------------------------------- Summary: Arquillian/Remote support Key: JBJCA-905 URL: https://issues.jboss.org/browse/JBJCA-905 Project: IronJacamar Issue Type: Task Components: Arquillian Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.1.0.Beta3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
1
0 / 0

[JBoss JIRA] (AS7-5833) Missing core queue attributes

by Jeff Mesnil (JIRA)

Jeff Mesnil created AS7-5833: -------------------------------- Summary: Missing core queue attributes Key: AS7-5833 URL: https://issues.jboss.org/browse/AS7-5833 Project: Application Server 7 Issue Type: Bug Components: JMS Affects Versions: 7.1.3.Final (EAP) Reporter: Jeff Mesnil Assignee: Jeff Mesnil Fix For: 7.2.0.Alpha1 the messaging's subsystem queues does not expose all the HornetQ core queue attributes. Missing attributes: * dead-letter-address * expiry-address Incorrect attributes: * temporary is flagged as a read-only attribute but it must still be possible to set it when the queue is created => add it to the add operation parameters (default=false) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
2
0 / 0

[JBoss JIRA] (JBRULES-3389) OSGi-fy drools-spring and drools-camel modules

by Alexander Filipchik (JIRA)

Alexander Filipchik created JBRULES-3389: -------------------------------------------- Summary: OSGi-fy drools-spring and drools-camel modules Key: JBRULES-3389 URL: https://issues.jboss.org/browse/JBRULES-3389 Project: Drools Issue Type: Enhancement Security Level: Public (Everyone can see) Components: drools-camel, drools-spring Affects Versions: 5.4.0.CR1 Reporter: Alexander Filipchik Assignee: Mark Proctor Fix For: 5.4.0.CR1 -- 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, 1 month

5
6
0 / 0

[JBoss JIRA] (AS7-3346) Security audit logging problem

by Jan Lanik (JIRA)

Jan Lanik created AS7-3346: ------------------------------ Summary: Security audit logging problem Key: AS7-3346 URL: https://issues.jboss.org/browse/AS7-3346 Project: Application Server 7 Issue Type: Bug Components: Security Affects Versions: 7.1.0.CR1b Reporter: Jan Lanik Assignee: Anil Saldhana I used the configuration setup + quick testing as documented here https://community.jboss.org/wiki/JBossAS7SecurityAuditing The audit.log file was created but no events was recorded in it. -- 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, 1 month

8
27
0 / 0

[JBoss JIRA] (AS7-4680) Logout a remote client from server and clearing login module cache.

by Serkan Yıldırım (JIRA)

Serkan Yıldırım created AS7-4680: ------------------------------------ Summary: Logout a remote client from server and clearing login module cache. Key: AS7-4680 URL: https://issues.jboss.org/browse/AS7-4680 Project: Application Server 7 Issue Type: Feature Request Components: Remoting, Security, Server Affects Versions: 7.1.1.Final Environment: java 1.6 win 7 64 bit 4 gb ram Reporter: Serkan Yıldırım Assignee: David Lloyd Priority: Blocker I have a custom login module. I authenticate and authorize a user (creating roles) by using this custom module. When i close the remote application, i want to logout the user from server so that clear login module cache, i.e deleting principals and roles from the cache. I couldn't find a solution for this problem in forum. If it exists, could you please explain it, thanks. -- 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, 1 month

4
5
0 / 0

[JBoss JIRA] (AS7-4679) Catching custom login module exceptions in remote client

by Serkan Yıldırım (JIRA)

Serkan Yıldırım created AS7-4679: ------------------------------------ Summary: Catching custom login module exceptions in remote client Key: AS7-4679 URL: https://issues.jboss.org/browse/AS7-4679 Project: Application Server 7 Issue Type: Feature Request Components: Remoting, Security, Server Affects Versions: 7.1.1.Final Environment: Win 7 64 Bit 4 GB RAM java 1.6 Reporter: Serkan Yıldırım Assignee: David Lloyd Priority: Critical This feature request is related with the discussion: https://community.jboss.org/message/732948#732948 I have custom login modules in JBOSS 7.1.2 Snapshot. They are working with no error, i can authenticate and authorize a user. However, when an exception occurs at the time of login, i.e. wrong password, i throw javax.security.auth.login.LoginException with my custom message. But i couldn't catch the exception in the remote client, how is it possible??? -- 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, 1 month

2
4
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 October 2012