Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: Bing-Integration
-
Fix Version/s: Bing-Integration
-
Component/s: None
-
Labels:None
-
Environment:
--------------------------------------------------
Project: Bing Integration
Bidmgr Build: tsa-build-bidmgr-2012-03-27-p117-r2246
MMS Build: p4-r3232
Admax Server: yell-ec-xml2.ri.thesearchagency.com (192.168.30.226)
MMW Server: yell-ec-mms3.ri.thesearchagency.com (192.168.30.216)
DB: yell-ec-db2 (192.168.30.225)
--------------------------------------------------
-------------------------------------------------- Project: Bing Integration Bidmgr Build: tsa-build-bidmgr-2012-03-27-p117-r2246 MMS Build: p4-r3232 Admax Server: yell-ec-xml2.ri.thesearchagency.com (192.168.30.226) MMW Server: yell-ec-mms3.ri.thesearchagency.com (192.168.30.216) DB: yell-ec-db2 (192.168.30.225) --------------------------------------------------
Description
Pre-conditons:
1. For creating the accounts , do the necessary env set-up as mentioned din the wiki page - http://kbase.ri.thesearchagency.com/index.php/Bing_Integration_release_notes#content_editor_bing
Steps:
1. Deploy an admaxService request for the BING distribution
2. Login to the yell-ec-xml2 system with valid credentials
3. Get inside the jail
4. Tail the listener log and observe:
Expected Behavior:
The deploy should be successful and the account should be successfully created.
Actual Behavior:
The deploy was unsuccessful and failed with the following NPE:
"2012-04-03 12:42:18.734 (2) [pool-3-thread-2]: Exception [Unhandled exception]:java.lang.NullPointerException"
>Attaching the complete log
