Bug 780184 (SOA-2559) - Intermittent, recurring problem with EDS adminshell - seeing NPE - with [org.jboss.resource.connectionmanager.NoTxConnectionManager] exception maybe 20% of the time
Summary: Intermittent, recurring problem with EDS adminshell - seeing NPE - with [org....
Keywords:
Status: CLOSED NOTABUG
Alias: SOA-2559
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: EDS
Version: 5.1.0.ER3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-09 19:40 UTC by Len DiMaggio
Modified: 2010-11-09 21:24 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 21:24:34 UTC
Type: Bug


Attachments (Terms of Use)
server.log_SOA_2559 (548.66 KB, application/octet-stream)
2010-11-09 19:42 UTC, Len DiMaggio
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-2559 0 None None None Never
Red Hat Issue Tracker TEIID-1353 0 None None None Never

Description Len DiMaggio 2010-11-09 19:40:16 UTC
project_key: SOA

Seeing this about one time in 5 performing a query and then disconnecting a JDBC and admin connection. Will attacher server.log and pointer to test code.

Logging this as a minor issue as there does not seem to be any functional impact, but the server.log message may concern users.

Comment 1 Len DiMaggio 2010-11-09 19:42:22 UTC
server.log

Comment 2 Len DiMaggio 2010-11-09 19:42:22 UTC
Attachment: Added: server.log_SOA_2559


Comment 4 Len DiMaggio 2010-11-09 19:48:34 UTC
Look at line 4066 in the attached server.log file

Comment 5 Van Halbert 2010-11-09 20:03:52 UTC
Link: Added: This issue Cloned to SOA-2560


Comment 6 Van Halbert 2010-11-09 20:05:13 UTC
Link: Added: This issue Cloned from TEIID-1353


Comment 7 Van Halbert 2010-11-09 21:24:34 UTC
Project engineer rejected issue.   Indicated that jira should be reopened with a reproducible use case.


Note You need to log in before you can comment on or make changes to this bug.