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: tsa-build-bidmgr-2012-04-12-p173-r2309
MMS Build: p8-r3238
Admax Server: ebiz-dev-ts-node-admax (10.1.3.67)
MMS Server: ebiz-dev-ts-node-mmw (10.1.3.66)
DB: ebiz-dev-ts-node (10.1.3.68)
--------------------------------------------------
-------------------------------------------------- Project: Bing Integration Bidmgr: tsa-build-bidmgr-2012-04-12-p173-r2309 MMS Build: p8-r3238 Admax Server: ebiz-dev-ts-node-admax (10.1.3.67) MMS Server: ebiz-dev-ts-node-mmw (10.1.3.66) DB: ebiz-dev-ts-node (10.1.3.68) --------------------------------------------------
Description
Steps:
1. Deploy an admaxService request for the BING distribution
2. Login to the ebiz-dev-ts-node-admax 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-12 09:06:33.433 (5) [P1T1]: Exception [ (Jakarta Debug) Exception: ]:org.apache.axis.ConfigurationException: No service named SignupCustomer is available
org.apache.axis.ConfigurationException: No service named SignupCustomer is available
at org.apache.axis.configuration.FileProvider.getService(FileProvider.java:233)
>Attaching the complete log
