October 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2130) ResourceAdapter deployed via ra.xml does not get registered

by Carlo de Wolf (Created) (JIRA)

ResourceAdapter deployed via ra.xml does not get registered ----------------------------------------------------------- Key: AS7-2130 URL: https://issues.jboss.org/browse/AS7-2130 Project: Application Server 7 Issue Type: Bug Components: JCA Reporter: Carlo de Wolf Assignee: Jesper Pedersen Priority: Critical Fix For: 7.1.0.Beta1 -- 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, 9 months

4
3
0 / 0

[JBoss JIRA] Created: (AS7-1964) AbstractDataSourceService#stop() doesn't stop anything

by Bob McWhirter (JIRA)

AbstractDataSourceService#stop() doesn't stop anything ------------------------------------------------------ Key: AS7-1964 URL: https://issues.jboss.org/browse/AS7-1964 Project: Application Server 7 Issue Type: Bug Components: JCA Affects Versions: 7.1.0.Alpha1 Reporter: Bob McWhirter Assignee: Jesper Pedersen The Service<T> for DataSources has a stop() method which simply nulls out its value, but doesn't stop/shutdown/destroy/clean-up anything else. {noformat} public synchronized void stop(StopContext stopContext) { sqlDataSource = null; } {noformat} In IRC, Jesper referenced JBJCA-672, resolved for IronJacamar 1.0.5 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
1
0 / 0

[JBoss JIRA] (AS7-2146) Login-Principal is not propagated to Ejb's SessionContext

by Dieter Tengelmann (Created) (JIRA)

Login-Principal is not propagated to Ejb's SessionContext --------------------------------------------------------- Key: AS7-2146 URL: https://issues.jboss.org/browse/AS7-2146 Project: Application Server 7 Issue Type: Bug Components: EJB, Security Affects Versions: 7.0.2.Final Reporter: Dieter Tengelmann Assignee: Carlo de Wolf Right after a form based login the principal is not propagated correctly to the EJB session context. -- 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, 9 months

4
3
0 / 0

[JBoss JIRA] (AS7-2108) Web Jacc Support

by Anil Saldhana (Created) (JIRA)

Web Jacc Support ---------------- Key: AS7-2108 URL: https://issues.jboss.org/browse/AS7-2108 Project: Application Server 7 Issue Type: Sub-task Components: Security, Web Reporter: Anil Saldhana Assignee: Marcus Moyses Fix For: 7.1.0.Beta1 -- 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, 9 months

3
2
0 / 0

[JBoss JIRA] (JGRP-1376) ENCRYPT race condition hangs cluster channel

by Manuel Dominguez Sarmiento (Created) (JIRA)

ENCRYPT race condition hangs cluster channel -------------------------------------------- Key: JGRP-1376 URL: https://issues.jboss.org/browse/JGRP-1376 Project: JGroups Issue Type: Bug Affects Versions: 3.0 Reporter: Manuel Dominguez Sarmiento Assignee: Bela Ban We have two nodes on a channel. When starting both simultaneously (we spawn threads from a third control server), sometimes the JGroups channel hangs on both servers and we get the following logs forever: [WARN ] 2011-10-15 17:19:17 [ENCRYPT-Incoming-2,null] - attempting to use stored cipher as message does not uses current encryption version [WARN ] 2011-10-15 17:19:17 [ENCRYPT-Incoming-2,null] - Unable to find a matching cipher in previous key map [WARN ] 2011-10-15 17:19:17 [ENCRYPT-Incoming-2,null] - Unrecognised cipher discarding message [WARN ] 2011-10-15 17:19:17 [ENCRYPT-Incoming-3,null] - attempting to use stored cipher as message does not uses current encryption version [WARN ] 2011-10-15 17:19:17 [ENCRYPT-Incoming-3,null] - Unable to find a matching cipher in previous key map [WARN ] 2011-10-15 17:19:17 [ENCRYPT-Incoming-3,null] - Unrecognised cipher discarding message We drilled down to the code in ENCRYPT, and we believe this is related to issue JGRP-706. That issue introduced a fix for a different problem when using dynamic keys which seems to be causing problems when starting nodes simultaneously. This did not happen to us before we moved to a simulatenous multi-node start scenario, so it seems to indicate there is some kind of race condition which is triggered only when the nodes start at almost the same time (they run the same hardware, OS, JVM, etc. so startup times are almost identical) This is the ENCRYPT config: <ENCRYPT sym_init="128" sym_algorithm="AES" asym_init="512" asym_algorithm="RSA" /> The tipoff that something is wrong here, and what led us to study the patch introduced by JGRP-706, is that we have two servers / nodes: one is named gargamel, and the other azrael. The odd thing is that we got these logs in gargamel: [INFO ] 2011-10-15 17:19:13 [ENCRYPT-Incoming-3,null] - handling tmp-view up: MergeView::[azrael-8126|2] [azrael-8126, gargamel-29063], subgroups=[[azrael-8126|0] [azrael-8126], [gargamel-29063|1] [gargamel-29063]] [INFO ] 2011-10-15 17:19:13 [ENCRYPT-Incoming-3,null] - I have become key server azrael-8126 There some kind of identity-crisis going on here - how can gargamel-29063 have become azrael-8126? The preceding log line indicates that the patch introduced by JGRP-706 is at play here. A TMP_VIEW event triggers the node into becoming key server. handleViewChange() is invoked with parameter makeServer=true which triggers this line: becomeKeyServer(tmpKeyServer); where tmpKeyServer is azrael-8126 We are not really knowledgeable of what should actually happen here, in order for everything to work properly, including the situation described by JGRP-706. However, it seems that in any case, if the local node is to become key server, then the method argument should probably be invoked becomeKeyServer(local_addr) - although I'm not sure whether this is correct, either. After this happens, we immediately start to get the log errors described at the beginning of this report. -- 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, 9 months

5
7
0 / 0

[JBoss JIRA] (AS7-2080) Add operation to activate the framework

by Thomas Diesler (Created) (JIRA)

Add operation to activate the framework --------------------------------------- Key: AS7-2080 URL: https://issues.jboss.org/browse/AS7-2080 Project: Application Server 7 Issue Type: Sub-task Components: Domain Management, OSGi Reporter: Thomas Diesler Assignee: David Bosschaert -- 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, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (AS7-1447) data-source connection-url is not writable

by Nicklas Karlsson (JIRA)

data-source connection-url is not writable ------------------------------------------ Key: AS7-1447 URL: https://issues.jboss.org/browse/AS7-1447 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.0.0.Final Reporter: Nicklas Karlsson Assignee: Jesper Pedersen Trying to edit the JDBC URL of a datasource gives 22:51:00,148 ERROR [org.jboss.as.controller] (HttpManagementService-threads - 1) Operation ("write-attribute") failed - address: ([ ("subsystem" => "datasources"), ("data-source" => "java:jboss/datasources/ExampleDS") ]) - failure description: "Attribute connection-url is not writeable" -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
2
0 / 0

[JBoss JIRA] (JBRULES-3259) Full build gives a strange warning "[WARNING] Cannot include project artifact: org.drools:drools-distribution:pom:5.3.0.Final; it doesn't have an associated file or directory."

by Toni Rikkola (Created) (JIRA)

Full build gives a strange warning "[WARNING] Cannot include project artifact: org.drools:drools-distribution:pom:5.3.0.Final; it doesn't have an associated file or directory." -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-3259 URL: https://issues.jboss.org/browse/JBRULES-3259 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.3.0.Final Reporter: Toni Rikkola Assignee: Geoffrey De Smet Priority: Minor Happens on several modules, here is an example of the log: [INFO] ------------------------------------------------------------------------ [INFO] Building Drools distribution 5.3.0.Final [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ drools-distribution --- [INFO] Deleting /Users/rikkola/Codes/drools/drools/drools-distribution/target [INFO] [INFO] --- maven-enforcer-plugin:1.0:enforce (default) @ drools-distribution --- [INFO] [INFO] >>> maven-source-plugin:2.1.2:jar (default) @ drools-distribution >>> [INFO] [INFO] --- maven-enforcer-plugin:1.0:enforce (default) @ drools-distribution --- [INFO] [INFO] <<< maven-source-plugin:2.1.2:jar (default) @ drools-distribution <<< [INFO] [INFO] --- maven-source-plugin:2.1.2:jar (default) @ drools-distribution --- [INFO] [INFO] >>> maven-source-plugin:2.1.2:test-jar (default) @ drools-distribution >>> [INFO] [INFO] --- maven-enforcer-plugin:1.0:enforce (default) @ drools-distribution --- [INFO] [INFO] <<< maven-source-plugin:2.1.2:test-jar (default) @ drools-distribution <<< [INFO] [INFO] --- maven-source-plugin:2.1.2:test-jar (default) @ drools-distribution --- [INFO] [INFO] --- maven-javadoc-plugin:2.7:jar (default) @ drools-distribution --- [INFO] Not executing Javadoc as the project is not a Java classpath-capable package [INFO] [INFO] --- maven-assembly-plugin:2.2.1:single (default) @ drools-distribution --- [INFO] Reading assembly descriptor: src/main/assembly/assembly-drools.xml [WARNING] Cannot include project artifact: org.drools:drools-distribution:pom:5.3.0.Final; it doesn't have an associated file or directory. [WARNING] Cannot include project artifact: org.drools:drools-distribution:pom:5.3.0.Final; it doesn't have an associated file or directory. [WARNING] Cannot include project artifact: org.drools:drools-distribution:pom:5.3.0.Final; it doesn't have an associated file or directory. [WARNING] Cannot include project artifact: org.drools:drools-distribution:pom:5.3.0.Final; it doesn't have an associated file or directory. [WARNING] Cannot include project artifact: org.drools:drools-distribution:pom:5.3.0.Final; it doesn't have an associated file or directory. [WARNING] Cannot include project artifact: org.drools:drools-distribution:pom:5.3.0.Final; it doesn't have an associated file or directory. [WARNING] Cannot include project artifact: org.drools:drools-distribution:pom:5.3.0.Final; it doesn't have an associated file or directory. [INFO] Copying files to /Users/rikkola/Codes/drools/drools/drools-distribution/target/drools-distribution-5.3.0.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

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBMESSAGING-1901) Deadlock when a node is being shutdown by the MessagingClusterHealthMBean if the DB and Network is broken at the same time

by Yong Hao Gao (Created) (JIRA)

Deadlock when a node is being shutdown by the MessagingClusterHealthMBean if the DB and Network is broken at the same time -------------------------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-1901 URL: https://issues.jboss.org/browse/JBMESSAGING-1901 Project: JBoss Messaging Issue Type: Bug Components: JMS Clustering Affects Versions: 1.4.8.SP3, 1.4.0.SP3.CP14 Reporter: Yong Hao Gao Assignee: Yong Hao Gao Fix For: 1.4.0.SP3.CP15, 1.4.8.SP4 The stack trace shows the deadlock: "Thread-23": waiting to lock monitor 0x0000000001681638 (object 0x00000000d730fa60, a org.jboss.jms.server.MessagingClusterHealthMBean), which is held by "Incoming-13,192.168.1.110:55200" "Incoming-13,192.168.1.110:55200": waiting to lock monitor 0x0000000001681c20 (object 0x00000000d92e1580, a org.jboss.messaging.core.impl.postoffice.MessagingPostOffice$StateMonitor), which is held by "Thread-23" Java stack information for the threads listed above: =================================================== "Thread-23": at org.jboss.jms.server.MessagingClusterHealthMBean.stopNodeOnDBFailure(MessagingClusterHealthMBean.java:94) - waiting to lock <0x00000000d730fa60> (a org.jboss.jms.server.MessagingClusterHealthMBean) at org.jboss.jms.server.ServerPeer.stopJBMNodeForRecovery(ServerPeer.java:2115) at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice$StateMonitor.run(MessagingPostOffice.java:4256) - locked <0x00000000d92e1580> (a org.jboss.messaging.core.impl.postoffice.MessagingPostOffice$StateMonitor) "Incoming-13,192.168.1.110:55200": at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice$StateMonitor.shutdown(MessagingPostOffice.java:4280) - waiting to lock <0x00000000d92e1580> (a org.jboss.messaging.core.impl.postoffice.MessagingPostOffice$StateMonitor) at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.stop(MessagingPostOffice.java:797) at org.jboss.messaging.core.jmx.MessagingPostOfficeService.stopService(MessagingPostOfficeService.java:554) at org.jboss.system.ServiceMBeanSupport.jbossInternalStop(ServiceMBeanSupport.java:405) at org.jboss.system.ServiceMBeanSupport.stop(ServiceMBeanSupport.java:281) 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:616) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138) at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:140) at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) at org.jboss.jms.server.MessagingClusterHealthMBean.stopService(MessagingClusterHealthMBean.java:140) at org.jboss.jms.server.MessagingClusterHealthMBean.stopNodeOnDBFailure(MessagingClusterHealthMBean.java:107) - locked <0x00000000d730fa60> (a org.jboss.jms.server.MessagingClusterHealthMBean) at org.jboss.jms.server.ServerPeer.stopJBMNodeForRecovery(ServerPeer.java:2115) at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.quarantine(MessagingPostOffice.java:1751) at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.nodesLeft(MessagingPostOffice.java:1571) at org.jboss.messaging.core.impl.postoffice.GroupMember$ControlMembershipListener.viewAccepted(GroupMember.java:609) at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.handleUpEvent(MessageDispatcher.java:733) at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:776) at org.jgroups.JChannel.up(JChannel.java:1336) at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:454) at org.jgroups.protocols.pbcast.FLUSH.up(FLUSH.java:439) at org.jgroups.protocols.pbcast.STATE_TRANSFER.up(STATE_TRANSFER.java:153) at org.jgroups.protocols.FRAG2.up(FRAG2.java:188) at org.jgroups.protocols.FC.up(FC.java:493) at org.jgroups.protocols.pbcast.GMS.installView(GMS.java:543) - locked <0x00000000d92a8ae0> (a org.jgroups.Membership) at org.jgroups.protocols.pbcast.CoordGmsImpl.handleViewChange(CoordGmsImpl.java:463) at org.jgroups.protocols.pbcast.GMS.up(GMS.java:749) at org.jgroups.protocols.VIEW_SYNC.up(VIEW_SYNC.java:192) at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:233) at org.jgroups.protocols.UNICAST.up(UNICAST.java:328) at org.jgroups.protocols.pbcast.NAKACK.handleMessage(NAKACK.java:895) at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:708) at org.jgroups.protocols.BARRIER.up(BARRIER.java:136) at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:167) at org.jgroups.protocols.FD.up(FD.java:284) at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:328) at org.jgroups.protocols.MERGE2.up(MERGE2.java:144) at org.jgroups.protocols.Discovery.up(Discovery.java:264) at org.jgroups.protocols.PING.up(PING.java:273) at org.jgroups.protocols.TP$ProtocolAdapter.up(TP.java:2319) at org.jgroups.protocols.TP.passMessageUp(TP.java:1253) at org.jgroups.protocols.TP.access$100(TP.java:50) at org.jgroups.protocols.TP$1.run(TP.java:1177) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) Found 1 deadlock. -- 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, 9 months

4
5
0 / 0

[JBoss JIRA] (AS7-2174) RestEasyIntegrationTestCase assumes running OSGi subsystem

by Thomas Diesler (Created) (JIRA)

RestEasyIntegrationTestCase assumes running OSGi subsystem ---------------------------------------------------------- Key: AS7-2174 URL: https://issues.jboss.org/browse/AS7-2174 Project: Application Server 7 Issue Type: Task Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.1.0.Beta1 -- 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, 9 months

1
0
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 2011