September 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-646) ConnectionTable problem after a while in 2 node cluster

by Martin Vecera (JIRA)

ConnectionTable problem after a while in 2 node cluster ------------------------------------------------------- Key: JGRP-646 URL: http://jira.jboss.com/jira/browse/JGRP-646 Project: JGroups Issue Type: Bug Affects Versions: 2.4.1 SP4 Environment: Two physical machines both running RHEL5, Sun JVM 1.5.0_12, full SOA-P 4.2.0.IR8 based on EAP 4.3.0.GA (build: SVNTag=JBPAPP_4_3_0_GA date=200711291835), Orcale DB on a separate machine Reporter: Martin Vecera Assigned To: Bela Ban Reproducible: 100% 1. I took full IR8 and used dbinstall (https://svn.corp.jboss.com/repos/soa/trunk/qa/dbinstall/) for the 'all' configuration to use Oracle DB. 2. I unsecured jmx-service-invoker. 3. I copied the SOA-P to the second node. 4. I changed the server peer id on the both copies to be different. 5. I started the first node, it was successful. 6. I started the second node successfully as well. 7. I let it be for half an hour. 8. This appeared in the log files: Node 1: 2007-12-13 10:57:07,502 WARN [org.jgroups.blocks.ConnectionTable] peer closed connection, trying to re-send msg 2007-12-13 10:57:07,502 ERROR [org.jgroups.blocks.ConnectionTable] 2nd attempt to send data failed too Node 2: 2007-12-13 10:57:08,927 WARN [org.jgroups.blocks.ConnectionTable] peer closed connection, trying to re-send msg 2007-12-13 10:57:08,928 ERROR [org.jgroups.blocks.ConnectionTable] 2nd attempt to send data failed too It doesn't seem like there's anything related to the problems in the logs (no exceptions, no other JGroups related output...). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-7195) On executing readonly query, WrappedConnection.checkTransactionStatus throws exception when transaction is marked for roll back

by jay xxx (JIRA)

On executing readonly query, WrappedConnection.checkTransactionStatus throws exception when transaction is marked for roll back ------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-7195 URL: https://jira.jboss.org/jira/browse/JBAS-7195 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-5.1.0.GA, JBossAS-5.1.0.CR1, JBossAS-5.1.0.Beta1, JBossAS-5.0.1.GA, JBossAS-5.0.0.GA, JBossAS-5.0.0.CR2, JBossAS-4.2.3.GA Environment: linux/windows, jboss 4.2.3 onwards, jdk 1.5/1.6 Reporter: jay xxx Assignee: Jesper Pedersen Hi, When using jboss 4.2.3 with our app, we got an error of this sort (not exact): Cannot Execute query.....Transaction status marked rollback Caused by: jboss.util.NestedSQLException at ...WrappedConnection.checkTransactionStatus Scenario when the above error happens: a) User submits request from a web page b) A jta transaction is started in a filter c) From UI layer, transaction is propagated to service layer with "Propation Required" setting. d) Service layer throws an exception (validation) and transaction is [i]marked [/i]for rollback. Note that it is [i]marked [/i]for rollback and [i]not [/i]rolledback e) The ui layer now prepares the view which requires some db [i]queries[/i] to be executed. As soon as the first query is tried to be executed, the above exception is thrown. I tried the above same steps with jboss 4.2.1 and it works fine. On further probing, found that in jboss 4.2.3, there was a change made as part of: [url]https://jira.jboss.org/jira/browse/JBAS-5080[/url] [url]https://jira.jboss.org/jira/browse/JBAS-5083[/url] >From jira links above, intention seems to be to prevent update sqls from getting exectuted when transaction is marked for rollback. But looks like the code that was added does not discriminate between read-only and update sqls and prevents even a prepared statement from getting created - WrappedConnection.checkTransactionStatus throws an exception "cannot execute query" transaction marked for rollback. I believe that jca should discriminate between read only and update queries and should *allow* read only queries to go through when transaction is marked for rollback. These would allow the views to get generated in the same transaction. Ours is a 2-tier system (ui + service layer execute in the same jvm) and we are using Hibernate's recommended OpenSessionInViewPattern with one hib session+ one transaction per request. Anyone has any thoughts about this? Is it a legitimate concern? Else, the options before us are: a) refactor our code to have one hib session + 2 transactions (one for service layer and the other for the view). I believe even Jboss Seam does this. b) We have a roadmap to migrate to jboss 4.2.3 followed by jboss 5.1 within next 4 months. Then we'll have to ourselves change the Wrapped connection code to discriminate between read only and update queries. -- 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

16 years, 5 months

4
7
0 / 0

[JBoss JIRA] Created: (JBAS-7134) Modifying ManagedOperation to return either a composite value containing a Boolean and a String

by Noam Malki (JIRA)

Modifying ManagedOperation to return either a composite value containing a Boolean and a String ----------------------------------------------------------------------------------------------- Key: JBAS-7134 URL: https://jira.jboss.org/jira/browse/JBAS-7134 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Noam Malki Assignee: Jesper Pedersen Priority: Minor Returning a composite value containing a Boolean and a String would be useful. For example, when invoking a test operation it would be useful to get a String with the specific failure message if the operation failed (please see JOPR-324). -- 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

16 years, 5 months

5
4
0 / 0

[JBoss JIRA] Created: (JBAS-6074) Investigate Pool MBean removal

by Anil Saldhana (JIRA)

Investigate Pool MBean removal ------------------------------ Key: JBAS-6074 URL: https://jira.jboss.org/jira/browse/JBAS-6074 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: EJB2, JMX Affects Versions: JBossAS-5.0.0.CR2 Reporter: Anil Saldhana Assignee: Alexey Loubyansky Fix For: JBossAS-5.0.0.GA Forum Thread for details. -- 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

16 years, 5 months

5
8
0 / 0

[JBoss JIRA] Created: (JBAS-3632) Too early checking of not closing connections

by Adrian Brock (JIRA)

Too early checking of not closing connections --------------------------------------------- Key: JBAS-3632 URL: http://jira.jboss.com/jira/browse/JBAS-3632 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-4.0.5.CR1 Reporter: Adrian Brock Assigned To: Weston Price Priority: Minor In the case where a transaction is ended early, e.g. JBossTM rollsback transactions at a timeout immediately, the cached connection manager is firing connection not closed events. This is because the ejb is still in the invocation with the connection open but the transaction synchronization is fired by the rollback/timeout. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

5
11
0 / 0

[JBoss JIRA] Created: (JBAS-5897) Web Profile Prototype

by Adrian Brock (JIRA)

Web Profile Prototype --------------------- Key: JBAS-5897 URL: https://jira.jboss.org/jira/browse/JBAS-5897 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web (Tomcat) service Reporter: Adrian Brock Assignee: Adrian Brock This is a holder task for prototype of the "web profile". This is a JBossAS configuration that looks forward to the JavaEE6 Web Profile. The initial prototype work will be done in the testsuite to validate the dependencies and make sure it works. -- 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

16 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-6558) Factor out system-jmx into core mc and deployers projects

by Adrian Brock (JIRA)

Factor out system-jmx into core mc and deployers projects --------------------------------------------------------- Key: JBAS-6558 URL: https://jira.jboss.org/jira/browse/JBAS-6558 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: MicroContainer bus Reporter: Adrian Brock Assignee: Adrian Brock Fix For: JBossAS-6.0.0.Alpha1 The ServiceController and its associated deployers should be moved into the relevant MC projects. i.e. the jmx model should be in a jmx-mc-int project and the "ServiceDeployers" should be in the deployers project. -- 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

16 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-6578) Move the jmx deployers to the jboss-deployers project

by Adrian Brock (JIRA)

Move the jmx deployers to the jboss-deployers project ----------------------------------------------------- Key: JBAS-6578 URL: https://jira.jboss.org/jira/browse/JBAS-6578 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JMX Reporter: Adrian Brock Assignee: Adrian Brock Fix For: JBossAS-6.0.0.Alpha1 -- 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

16 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5339) Support for JMX annotations

by Galder Zamarreno (JIRA)

Support for JMX annotations --------------------------- Key: JBAS-5339 URL: http://jira.jboss.com/jira/browse/JBAS-5339 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JMX Reporter: Galder Zamarreno Assigned To: Galder Zamarreno Fix For: JBossAS-5.0.1.CR1 Provide support for JSR-255 JMX annotations (@ManagedResource, @ManagedAttribute, @ManagedOperation...etc) until Java 7 is supported. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

4
6
0 / 0

[JBoss JIRA] Created: (JBAS-6577) Move the ServiceController and related classes to the microcontainer project as jmx-mc-int

by Adrian Brock (JIRA)

Move the ServiceController and related classes to the microcontainer project as jmx-mc-int ------------------------------------------------------------------------------------------ Key: JBAS-6577 URL: https://jira.jboss.org/jira/browse/JBAS-6577 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: MicroContainer bus Reporter: Adrian Brock Assignee: Adrian Brock Fix For: JBossAS-6.0.0.Alpha1 -- 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

16 years, 5 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 September 2009