Please use the Apache issue tracking system for new NetBeans issues (https://issues.apache.org/jira/projects/NETBEANS0/issues) !!

Bug 87160

Summary: Discovery unregistration failed while deploying webapp on remote system with wss liberty profile.
Product: serverplugins Reporter: _ hlu <hlu>
Component: IdentityAssignee: Srividhya Narayanan <vidhya>
Status: RESOLVED WONTFIX QA Contact: issues <issues.netbeans.org>
Priority: P2    
Version: 5.x   
Target Milestone: TBD   
Hardware: All   
OS: All   
Whiteboard:
Issue Type: DEFECT Exception Report:
Attachments: ide snapshot

Description _ hlu 2006-10-14 05:22:22 UTC
build22:
The following exceptions are thrown during deploying a webapp on remote system.
The same application was deployed successfully on local system previous:
am-init:
am-deploy:
amConfigFile: C:\Sun\AppServerbundleb22/addons/amserver/AMConfig.properties
amConfigXmlDir: C:\hlu\testb22\WebAp4server/src/conf
Deploying wsp provider TestWS
ServerProperties: palmultra (palmultra:8081)
SERVICE_TYPE: urn:TestWS
Registering provider with Discovery Service
unregister failed null
com.sun.identity.wss.provider.ProviderException: Discovery unregistration failed.
        at
com.sun.identity.wss.provider.DiscoveryConfig.unregisterProviderWithTA(DiscoveryConfig.java:185)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at
org.netbeans.modules.identity.profile.api.configurator.impl.dynamic.DiscoveryConfigImpl.unregisterProvider(DiscoveryConfigImpl.java:85)
        at
org.netbeans.modules.identity.profile.api.configurator.DiscoveryConfigurator.unregisterProvider(DiscoveryConfigurator.java:50)
        at
org.netbeans.modules.identity.ant.AMDeploy.deployWSPProviders(AMDeploy.java:181)
        at org.netbeans.modules.identity.ant.AMDeploy.execute(AMDeploy.java:93)
        at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
        at org.apache.tools.ant.Task.perform(Task.java:364)
        at org.apache.tools.ant.Target.execute(Target.java:341)
        at org.apache.tools.ant.Target.performTasks(Target.java:369)
        at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
        at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
        at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
        at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
        at
org.apache.tools.ant.module.bridge.impl.BridgeImpl.run(BridgeImpl.java:240)
        at
org.apache.tools.ant.module.run.TargetExecutor.run(TargetExecutor.java:293)
        at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:131)
Comment 1 _ hlu 2006-10-14 05:23:16 UTC
Created attachment 35206 [details]
ide snapshot
Comment 2 _ hlu 2006-10-14 05:25:54 UTC
Comments from Vidhya:
Hong reported this error when she tried to deploy a web app on a remote system.
The web app was on jsqai6 and the AM was running on palmultra. Malla helped
resolve this. This is related to time difff between the two systems. There is a
setting in AMConfig.properties for a timeout limit on response from discovery
service. In this case jsqai6 sent a unregister request to palmultra which
responded back and because of the time diff between the system clocks.. the
response was rejected by jsqai6 as an "ols message".. and hence the exception.
When I made jsqai6 in sync with palmultra the exception went away and
registration succeeded.
Comment 3 Srividhya Narayanan 2006-10-14 06:14:26 UTC
This is an AM feature. Not an issue. Needs to be documented
By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo