October 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBRULES-3272) Opportunistic Backward Chaining

by Mark Proctor (Created) (JIRA)

Opportunistic Backward Chaining ------------------------------- Key: JBRULES-3272 URL: https://issues.jboss.org/browse/JBRULES-3272 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mark Proctor Assignee: Mark Proctor -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-2426) If a slave host controller fails authentication it just keeps re-trying

by Darran Lofthouse (Created) (JIRA)

If a slave host controller fails authentication it just keeps re-trying ----------------------------------------------------------------------- Key: AS7-2426 URL: https://issues.jboss.org/browse/AS7-2426 Project: Application Server 7 Issue Type: Bug Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.0.CR1 If the slave host controller can not connect to the master host controller due to failed authentication the following message is continually logged as it keeps retrying. "JBREM000200: Remote connection failed: javax.security.sasl.SaslException: No more authentication mechanisms to try" In general for clients connecting using Remoting and authenticating we probably want something more specific to indicate a failed authentication as retrying is probably never going to work. The looping here is also bad if a form of brute force defense is added as this may appear as an attack. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-694) SonicMQ RA in JBoss7 showing lots of IJ000612 warnings (Destroying connection that could not be successfully matched)

by Robert Stupp (Created) (JIRA)

SonicMQ RA in JBoss7 showing lots of IJ000612 warnings (Destroying connection that could not be successfully matched) --------------------------------------------------------------------------------------------------------------------- Key: JBJCA-694 URL: https://issues.jboss.org/browse/JBJCA-694 Project: IronJacamar Issue Type: Bug Affects Versions: 1.0.5.Final Environment: Linux *2.6.32-71.29.1.el6.x86_64 #1 SMP x86_64 x86_64 x86_64 GNU/Linux java version "1.6.0_27" Java(TM) SE Runtime Environment (build 1.6.0_27-b07) Java HotSpot(TM) 64-Bit Server VM (build 20.2-b06, mixed mode) JBoss 7.1.0.Alpha2 AS with current code from git Reporter: Robert Stupp Assignee: Jesper Pedersen Basic integration of SonicMQ RA (version 8.5) works. But when using JMeter with many parallel requests provoke a lot of these warnings: {noformat} 17:25:38,489 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (http--0.0.0.0-8080-5) IJ000612: Destroying connection that could not be successfully matched: org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@7df5f91c[state=NORMAL managed connection=com.sonicsw.sonicmq.j2ee.jmsra.impl.JMSSessionManagedConnection@24f1c9c6 connection handles=0 lastUse=1319815538489 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@6dbd726 pool internal context=org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool@2fb8c90 xaResource=XAResourceWrapperImpl@1fb5dddf[xaResource=com.sonicsw.sonicmq.j2ee.jmsra.impl.XAResourceWrapper(a)5cf96bbc pad=false overrideRmValue=false productName=java:/XAConnectionFactory productVersion=java:/XAConnectionFactory jndiName=java:/XAConnectionFactory] txSync=null] {noformat} With tracing enabled, JCA core connection manager tells this (before the message above): {noformat} 17:25:38,487 TRACE [org.jboss.jca.core.connectionmanager.listener.TxConnectionListener] (http--0.0.0.0-8080-10) connectionClosed called mc=com.sonicsw.sonicmq.j2ee.jmsra.impl.JMSSessionManagedConnection@24f1c9c6 17:25:38,487 TRACE [org.jboss.jca.core.connectionmanager.listener.TxConnectionListener] (http--0.0.0.0-8080-10) unregisterConnection: 0 handles left 17:25:38,487 TRACE [org.jboss.jca.core.connectionmanager.listener.TxConnectionListener] (http--0.0.0.0-8080-10) delisting org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@7df5f91c[state=NORMAL managed connection=com.sonicsw.sonicmq.j2ee.jmsra.impl.JMSSessionManagedConnection@24f1c9c6 connection handles=0 lastUse=1319815538458 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@6dbd726 pool internal context=org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool@2fb8c90 xaResource=XAResourceWrapperImpl@1fb5dddf[xaResource=com.sonicsw.sonicmq.j2ee.jmsra.impl.XAResourceWrapper(a)5cf96bbc pad=false overrideRmValue=false productName=java:/XAConnectionFactory productVersion=java:/XAConnectionFactory jndiName=java:/XAConnectionFactory] txSync=null] 17:25:38,487 TRACE [org.jboss.jca.core.connectionmanager.listener.TxConnectionListener] (http--0.0.0.0-8080-10) isManagedConnectionFree=true mc=com.sonicsw.sonicmq.j2ee.jmsra.impl.JMSSessionManagedConnection@24f1c9c6 17:25:38,489 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (http--0.0.0.0-8080-5) IJ000612: Destroying connection that could not be successfully matched: org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@7df5f91c[state=NORMAL managed connection=com.sonicsw.sonicmq.j2ee.jmsra.impl.JMSSessionManagedConnection@24f1c9c6 connection handles=0 lastUse=1319815538489 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@6dbd726 pool internal context=org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool@2fb8c90 xaResource=XAResourceWrapperImpl@1fb5dddf[xaResource=com.sonicsw.sonicmq.j2ee.jmsra.impl.XAResourceWrapper(a)5cf96bbc pad=false overrideRmValue=false productName=java:/XAConnectionFactory productVersion=java:/XAConnectionFactory jndiName=java:/XAConnectionFactory] txSync=null] ... (somthing else happens in other threads) ... 17:25:38,489 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (http--0.0.0.0-8080-5) IJ000612: Destroying connection that could not be successfully matched: org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@7df5f91c[state=NORMAL managed connection=com.sonicsw.sonicmq.j2ee.jmsra.impl.JMSSessionManagedConnection@24f1c9c6 connection handles=0 lastUse=1319815538489 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@6dbd726 pool internal context=org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool@2fb8c90 xaResource=XAResourceWrapperImpl@1fb5dddf[xaResource=com.sonicsw.sonicmq.j2ee.jmsra.impl.XAResourceWrapper(a)5cf96bbc pad=false overrideRmValue=false productName=java:/XAConnectionFactory productVersion=java:/XAConnectionFactory jndiName=java:/XAConnectionFactory] txSync=null] {noformat} ----------------------------------------- Related to the above (but slightly different messages (productName, productVersion): The first request (after JBoss 7 startup) issues exactly as many of these warnings as the configured minimum pool size. For example: min-size=20 forces 20 of the following messages: {noformat} 17:18:21,545 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (http--0.0.0.0-8080-1) IJ000612: Destroying connection that could not be successfully matched: org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@7d3e3b95[state=NORMAL managed connection=com.sonicsw.sonicmq.j2ee.jmsra.impl.JMSSessionManagedConnection@b9f370 connection handles=0 lastUse=1319815093744 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@6dbd726 pool internal context=org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool@2fb8c90 xaResource=XAResourceWrapperImpl@301d3e6f[xaResource=com.sonicsw.sonicmq.j2ee.jmsra.impl.XAResourceWrapper(a)4fee0216 pad=false overrideRmValue=false productName=SonicMQ productVersion=8.5.377 jndiName=java:/XAConnectionFactory] txSync=null] 17:18:21,547 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (http--0.0.0.0-8080-1) IJ000612: Destroying connection that could not be successfully matched: org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@12cb1b59[state=NORMAL managed connection=com.sonicsw.sonicmq.j2ee.jmsra.impl.JMSSessionManagedConnection@547079b2 connection handles=0 lastUse=1319815093742 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@6dbd726 pool internal context=org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool@2fb8c90 xaResource=XAResourceWrapperImpl@2445c06d[xaResource=com.sonicsw.sonicmq.j2ee.jmsra.impl.XAResourceWrapper(a)5f5c46b5 pad=false overrideRmValue=false productName=SonicMQ productVersion=8.5.377 jndiName=java:/XAConnectionFactory] txSync=null] 17:18:21,550 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (http--0.0.0.0-8080-1) IJ000612: Destroying connection that could not be successfully matched: org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@232645fc[state=NORMAL managed connection=com.sonicsw.sonicmq.j2ee.jmsra.impl.JMSSessionManagedConnection@25bcb56b connection handles=0 lastUse=1319815093740 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@6dbd726 pool internal context=org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool@2fb8c90 xaResource=XAResourceWrapperImpl@82a9728[xaResource=com.sonicsw.sonicmq.j2ee.jmsra.impl.XAResourceWrapper(a)2429c748 pad=false overrideRmValue=false productName=SonicMQ productVersion=8.5.377 jndiName=java:/XAConnectionFactory] txSync=null] ... (17 more) {noformat} I am not sure whether this is caused by ironjacamar or JBoss7 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

12 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (AS7-851) Add some form of :whoami operation

by Darran Lofthouse (JIRA)

Add some form of :whoami operation ---------------------------------- Key: AS7-851 URL: https://issues.jboss.org/browse/AS7-851 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Darran Lofthouse Assignee: Jason Greene Fix For: 7.0.0.CR1 Connectivity to the server can make use of authentication automatically handled by either the web broswer or in some cases possibly a CLI using a local Kerberos ticket. This issue is to add a :whoami operation to verify who the connection is running as so the client can see they are connected as the expected user. Later this may also be expanded to make it possible to query what a client can actually do so operations a client can not perform can be potentially hidden / masked. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
6
0 / 0

[JBoss JIRA] (AS7-2386) upgrade to hibernate-core 4.0.0.CR5

by Strong Liu (Created) (JIRA)

upgrade to hibernate-core 4.0.0.CR5 ----------------------------------- Key: AS7-2386 URL: https://issues.jboss.org/browse/AS7-2386 Project: Application Server 7 Issue Type: Task Components: JPA / Hibernate Reporter: Strong Liu Assignee: Scott Marlow Hibernate core 4.0.0.CR5 just released, this release contains two major fix relates to AS7, it would be great if AS7 can upgrade to it asap, 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

12 years, 11 months

3
2
0 / 0

[JBoss JIRA] Created: (JBEE-45) Release JACC 1.1 APIs built with JDK 1.4

by Shelly McGowan (JIRA)

Release JACC 1.1 APIs built with JDK 1.4 ---------------------------------------- Key: JBEE-45 URL: https://jira.jboss.org/jira/browse/JBEE-45 Project: JBoss JavaEE APIs Issue Type: Bug Reporter: Shelly McGowan Assignee: Shelly McGowan Fix For: 1.0.0.CR1 To replace this: http://repository.jboss.org/maven2/org/jboss/javaee/jboss-jacc-api_JDK4/1... which contains a servlet snapshot Needed by Hibernate -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBEE-76) Create JavaEE API aggregate for use with JBoss AS 7

by Shelly McGowan (JIRA)

Create JavaEE API aggregate for use with JBoss AS 7 --------------------------------------------------- Key: JBEE-76 URL: https://issues.jboss.org/browse/JBEE-76 Project: JBoss JavaEE APIs Issue Type: Feature Request Components: javaee6_specs_bom, javaee_6.0_spec Reporter: Shelly McGowan Assignee: Shelly McGowan Fix For: 2.0.0-Beta1-javaee_6.0, 2.0.0-Beta1-javaee6-specs-bom Started Version 2.0.x series for use with JBoss AS 7. These APIs are compatible but the versions in the specs bom and aggregate align with the versions in the AS 7 distribution. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
3
0 / 0

[JBoss JIRA] (AS7-2422) Failed to disable datasource

by Heiko Braun (Created) (JIRA)

Failed to disable datasource ---------------------------- Key: AS7-2422 URL: https://issues.jboss.org/browse/AS7-2422 Project: Application Server 7 Issue Type: Bug Components: JCA Reporter: Heiko Braun Assignee: Stefano Maestri Fix For: 7.1.0.Beta1 We've got regression on the datasource management. The datasource is enabled, but disabling fails: {noformat} [standalone@localhost:9999 /] /profile=default/subsystem=datasources/data-source=java\:jboss\/datasources\/ExampleDS:disable { "outcome" => "failed", "result" => {"server-groups" => [("main-server-group" => {"master" => { "host" => "master", "response" => { "outcome" => "failed", "failure-description" => "Data-source service [java:jboss/datasources/ExampleDS] is not enabled", "rolled-back" => true } }})]}, "failure-description" => "Operation failed or was rolled back on all servers.", "rolled-back" => true } {noformat} -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (AS7-1358) UserTransaction not available to non-EE threads

by Chris Lowe (JIRA)

UserTransaction not available to non-EE threads ----------------------------------------------- Key: AS7-1358 URL: https://issues.jboss.org/browse/AS7-1358 Project: Application Server 7 Issue Type: Feature Request Components: Transactions Affects Versions: 7.0.0.Final Reporter: Chris Lowe Assignee: Jonathan Halliday JBoss Seam offers Asynchronous behaviour for non-EJB environments using a Quartz dispatcher. Asynchronous behaviour may also make use of Seam's @Transactional marker to demarcate tx boundaries. Since testing one of our applications in AS7 I noticed Seam "could not discover transaction status" error messages reported as our application ran async sections of code. Examining the Seam code, I could see that Seam would make two attempts to access a JNDI UserTransaction resource: 1 - context.lookup("java:comp/UserTransaction"); If an NameNotFoundException is thrown, then attempt: 2 - context.lookup("UserTransaction"); Under AS6 and below, the latter attempt would succeed. Under AS7 attempts are currently failing. While looking into this issue I came across the following developer discussion which suggests that it might be possible to add a "java:/jboss/UserTransaction" resource: http://lists.jboss.org/pipermail/jboss-as7-dev/2011-June/002298.html Further discussion on my AS7 user forum thread lead to the suggestion that I myself might add this behaviour. I have followed the implementation hints and light testing has been successful (with appropriate mods to Seam to use the new resource name). I aim to perform some more thorough testing on this shortly and submit a patch against this issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

5
8
0 / 0

[JBoss JIRA] (AS7-2318) Web Console: The log4j/log editor should assist users with configurations/settings that do not make sense

by Jim Tyrrell (Created) (JIRA)

Web Console: The log4j/log editor should assist users with configurations/settings that do not make sense --------------------------------------------------------------------------------------------------------- Key: AS7-2318 URL: https://issues.jboss.org/browse/AS7-2318 Project: Application Server 7 Issue Type: Feature Request Reporter: Jim Tyrrell If the root logger is set to info, it will grab all of the log messages and not allow for a debug logging later on in the hierarchy. This is a support issue as they often have users turn on more logging, but the user has not "turned off" the root logger so it is not able to grab any debug messages. -- 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, 11 months

8
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2011