Bug 777802 (SOA-328) - context.lookup() can return null
Summary: context.lookup() can return null
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-328
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBossESB
Version: 4.2 Beta 1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2 CR1
Assignee: Martin Vecera
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-01-15 16:05 UTC by Martin Vecera
Modified: 2008-02-05 12:31 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
SOA-P 4.2.1.beta1, Oracle DB
Last Closed: 2008-02-05 12:31:53 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 777837 0 high CLOSED NotifyQueues not working: ConnectionException: Could not obtain a JMS connection from the pool 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-328 0 None None None Never

Internal Links: 777837

Description Martin Vecera 2008-01-15 16:05:42 UTC 
Date of First Response: 2008-01-17 05:58:19
project_key: SOA

See linked issue.
Comment 1 Martin Vecera 2008-01-15 16:06:00 UTC 
Link: Added: This issue depends JBESB-1484
Comment 2 Kevin Conner 2008-01-17 10:58:19 UTC 
Martin, this issue should be resolved now.

The JNDI Contexts are now pooled correctly as a lifecycle resource.
Comment 3 Martin Vecera 2008-01-24 16:25:58 UTC 
Link: Added: This issue related SOA-363
Comment 4 Martin Vecera 2008-01-24 16:26:26 UTC 
This issue cannot be verified because of SOA-363.
Comment 5 Martin Vecera 2008-02-05 12:31:52 UTC 
Verified.
Note You need to log in before you can comment on or make changes to this bug.