January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-1398) Faulty node which doesn't respond to START_FLUSHes cripples the cluster

by Nicolas Estrada (Created) (JIRA)

Faulty node which doesn't respond to START_FLUSHes cripples the cluster ----------------------------------------------------------------------- Key: JGRP-1398 URL: https://issues.jboss.org/browse/JGRP-1398 Project: JGroups Issue Type: Bug Affects Versions: 2.12.2 Environment: Windows XP, jre1.6_10 Reporter: Nicolas Estrada Assignee: Bela Ban http://sourceforge.net/mailarchive/forum.php?thread_name=4EE06742.7070003... I will begin on my end to add more traces in the FLUSH protocol but any suggestions are welcome -- 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

6
6
0 / 0

[JBoss JIRA] (AS7-2420) Include JA metrics in the console

by Heiko Braun (Created) (JIRA)

Include JA metrics in the console --------------------------------- Key: AS7-2420 URL: https://issues.jboss.org/browse/AS7-2420 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun -- 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] (AS7-2030) Hardcoded localhost:8080 in some tests

by Ondrej Zizka (Created) (JIRA)

Hardcoded localhost:8080 in some tests -------------------------------------- Key: AS7-2030 URL: https://issues.jboss.org/browse/AS7-2030 Project: Application Server 7 Issue Type: Bug Components: Test Suite Affects Versions: 7.1.0.Alpha1 Reporter: Ondrej Zizka Assignee: Ondrej Zizka E.g. in org.jboss.as.test.clustering.web SimpleWebTestCase -- 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
3
0 / 0

[JBoss JIRA] Created: (JBRULES-3192) FUSE 4.3.0 OSGI Bundles for Drools 5.2.0.Final

by Sankar Vinnakota (JIRA)

FUSE 4.3.0 OSGI Bundles for Drools 5.2.0.Final ---------------------------------------------- Key: JBRULES-3192 URL: https://issues.jboss.org/browse/JBRULES-3192 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-core (expert) Affects Versions: 5.2.0.Final Environment: QA Reporter: Sankar Vinnakota Assignee: Mark Proctor Priority: Minor Hi, I am planning to use Drools 5.2.0.Final in FUSE (apache-servicemix-4.3.0-fuse-00-00 & apache-servicemix-4.4.0-fuse-00-27). Can you let me know what are the OSGI bundles need to install in order to run my simple drools application inside FUSE. I have downloaded Drools OSGi bundles for 5.2.0.Final. It is too big list do we need to install all those bundles to work with Drools? Is there any optimal way to install less bundles to FUSE. Do we need to install any extra bundles for 4.30 & 4.4.0 ? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
2
0 / 0

[JBoss JIRA] (AS7-3337) AS7 does not work when it is installed in a path containing space character

by Dominik Pospisil (JIRA)

Dominik Pospisil created AS7-3337: ------------------------------------- Summary: AS7 does not work when it is installed in a path containing space character Key: AS7-3337 URL: https://issues.jboss.org/browse/AS7-3337 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.0.Final Reporter: Dominik Pospisil [dpospisi@simkin bin]$ ./standalone.sh ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /home/dpospisi/run times/jboss-as-7.1.0.Final-SNAPSHOT JAVA: java JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true ========================================================================= WARNING: No log manager service descriptor found in specified logmodule org.jboss.logmanager:main WARNING: No mbeanserver service descriptor found in specified mbeanserverbuildermodule org.jboss.as.jmx:main Exception in thread "main" java.lang.ExceptionInInitializerError at org.jboss.as.server.Main.main(Main.java:91) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.jboss.modules.Module.run(Module.java:248) at org.jboss.modules.Main.main(Main.java:313) Caused by: java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager") at org.jboss.logmanager.Logger.getLogger(Logger.java:60) at org.jboss.logmanager.log4j.BridgeRepositorySelector.<clinit>(BridgeRepositorySelector.java:42) ... 7 more [dpospisi@simkin bin]$ -- 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
14
0 / 0

[JBoss JIRA] (AS7-2942) when EJB method called from application client with proper authorization call is wrongly denied

by Peter Skopek (Created) (JIRA)

when EJB method called from application client with proper authorization call is wrongly denied ----------------------------------------------------------------------------------------------- Key: AS7-2942 URL: https://issues.jboss.org/browse/AS7-2942 Project: Application Server 7 Issue Type: Bug Components: EJB, Security Affects Versions: 7.1.0.CR1 Reporter: Peter Skopek Assignee: jaikiran pai Fix For: 7.1.0.CR1 When calling EJB method from client with authenticated user holding proper authorization, method call is denied. It is happening for stateless as well as stateful beans. See server exception: 09:31:58,254 INFO [org.jboss.as.test.integration.ejb.security.SingleMethodsAnnSFSBTestCase] (main) JNDI name=ejb:/singleMethodsAnnOnlySFSB//SingleMethodsAnnOnlyCheckSFSB!org.jboss.as.test.integration.ejb.security.authorization.SimpleAuthorizationRemote?stateful 09:31:58,299 ERROR [org.jboss.ejb3.invocation] (pool-8-thread-5) JBAS014134: EJB Invocation failed on component SingleMethodsAnnOnlyCheckSFSB for method public abstract java.lang.String org.jboss.as.test.integration.ejb.security.authorization.SimpleAuthorizationRemote.roleBasedAccessOne(java.lang.String): javax.ejb.EJBAccessException: JBAS014502: Invocation on method: public abstract java.lang.String org.jboss.as.test.integration.ejb.security.authorization.SimpleAuthorizationRemote.roleBasedAccessOne(java.lang.String) of bean: SingleMethodsAnnOnlyCheckSFSB is not allowed at org.jboss.as.ejb3.security.AuthorizationInterceptor.processInvocation(AuthorizationInterceptor.java:99) [jboss-as-ejb3-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:] at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:70) [jboss-as-ejb3-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:] at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:] at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:57) [jboss-as-ejb3-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:] at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:] at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) [jboss-as-ee-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.invokeMethod(MethodInvocationMessageHandler.java:259) [jboss-as-ejb3-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$200(MethodInvocationMessageHandler.java:56) [jboss-as-ejb3-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:177) [jboss-as-ejb3-7.1.0.CR1-SNAPSHOT.jar:] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [:1.6.0_27] at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [:1.6.0_27] at java.util.concurrent.FutureTask.run(FutureTask.java:138) [:1.6.0_27] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_27] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_27] at java.lang.Thread.run(Thread.java:662) [:1.6.0_27] -- 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

12
18
0 / 0

[JBoss JIRA] (AS7-3359) Clustering for JMS/HornetQ should be configured by default in standalone-ha.xml

by Miroslav Novak (JIRA)

Miroslav Novak created AS7-3359: ----------------------------------- Summary: Clustering for JMS/HornetQ should be configured by default in standalone-ha.xml Key: AS7-3359 URL: https://issues.jboss.org/browse/AS7-3359 Project: Application Server 7 Issue Type: Feature Request Components: JMS Affects Versions: 7.1.0.CR1 Reporter: Miroslav Novak Assignee: Clebert Suconic Fix For: 7.1.0.Final Messaging subsystem should be configured to create cluster for HA profile - in standalone-ha.xml. Also there should be enabled message-redistribution and load-balancing by default. -- 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
8
0 / 0

[JBoss JIRA] (AS7-3161) FileCacheStore ISPN000064: Problems creating the directory

by Radoslav Husar (Created) (JIRA)

FileCacheStore ISPN000064: Problems creating the directory ---------------------------------------------------------- Key: AS7-3161 URL: https://issues.jboss.org/browse/AS7-3161 Project: Application Server 7 Issue Type: Bug Components: Clustering Reporter: Radoslav Husar Assignee: Paul Ferraro Fix For: 7.1.0.Final while AS7 logs {noformat} [JBossINF] 05:03:55,074 WARN [org.infinispan.loaders.file.FileCacheStore] (MSC service thread 1-7) ISPN000064: Problems creating the directory: /tmp/hudson/jboss-as-7.1.0.Final-SNAPSHOT/standalone/data/repl/repl {noformat} the directory has been created in the end (at different time so it looks) {noformat} [rhusar@perf20 repl]$ ll /tmp/hudson/jboss-as-7.1.0.Final-SNAPSHOT/standalone/data/repl/repl total 12 drwxrwxr-x. 3 hudson hudson 4096 Jan 3 05:17 org.jboss.test.clusterbench.ejb.stateful.LocalStatefulSB drwxrwxr-x. 3 hudson hudson 4096 Jan 3 05:17 org.jboss.test.clusterbench.ejb.stateful.RemoteStatefulSBImpl drwxrwxr-x. 2 hudson hudson 4096 Jan 3 05:17 repl {noformat} any thoughts why this is? -- 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
5
0 / 0

[JBoss JIRA] (AS7-3349) Data-source add allows adding data sources with non existing JDBC driver

by Dominik Pospisil (JIRA)

Dominik Pospisil created AS7-3349: ------------------------------------- Summary: Data-source add allows adding data sources with non existing JDBC driver Key: AS7-3349 URL: https://issues.jboss.org/browse/AS7-3349 Project: Application Server 7 Issue Type: Bug Components: CLI, Domain Management Affects Versions: 7.1.0.Final Reporter: Dominik Pospisil Assignee: Alexey Loubyansky Data-source add allows adding data sources with non existing JDBC driver. The data-source add command should warn / prevent user from doing such thing. [standalone@localhost:9999 /] ls /subsystem=datasources/data-source ExampleDS [standalone@localhost:9999 /] data-source add --jndi-name=java:/TestDS --connection-url=jdbc:postgresql://localhost/test --driver-name=NON_EXISTING_DRIVER [standalone@localhost:9999 /] ls /subsystem=datasources/data-source ExampleDS java:/TestDS [standalone@localhost:9999 /] -- 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
10
0 / 0

[JBoss JIRA] (AS7-3477) If DataSourceDisable fails the stopped/removed services need bringing back to their original state

by Kabir Khan (JIRA)

Kabir Khan created AS7-3477: ------------------------------- Summary: If DataSourceDisable fails the stopped/removed services need bringing back to their original state Key: AS7-3477 URL: https://issues.jboss.org/browse/AS7-3477 Project: Application Server 7 Issue Type: Feature Request Components: JCA Reporter: Kabir Khan Assignee: Jesper Pedersen Priority: Critical Fix For: 7.1.0.Final In my https://github.com/kabir/jboss-as/commits/recycle_data_source_AS7_3085 branch I changed DataSourceDisable to use OperationContext.remove() meaning that the operation will be rolled back if other services have the DS injected. I've added a skeleton rollback handler which should reinstate the services to their original state if it does get rolled back. -- 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
3
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