Re: Errors seen in systemout.log during federation

Federation is successful in all scenarios, but errors are shown in the logfiles.

After fixing the plugin path, no error found in addNode.log file.

But still SystemOut.log was showing "profiles/dmgr2/WEB-INF/classes/wsdl/WS-MetadataExchange-2004_09.xsd (No such file or directory)" and many more.

I found significant files are not present under DMR_PROFILE_CONFIGROOT/nd_cellname/applications/WebSphereWSDM.ear/deployments/WebSphereWSDM/WebSphereWSDM.war/WEB-INF/classes/wsdl compared to WAS_HOME/systemApps//WebSphereWSDM.ear/WebSphereWSDM.war/WEB-INF/classes/wsdl.

Now I copied systemApps wsdl directory dmgr_profile applications directory prior to federation and I dont see any error message now.

IBM has to look into it why not all files are getting copied to applications directory.

Re: Errors seen in systemout.log during federation

Sorry for the delay in responding to this post. Thanks to Ahmed for your participation in this thread. The WAS development team would like to investigate the issues you have encountered to ensure any potential defects are addressed in future updates to our product. I had asked several of our testers to attempt to recreate the problem(s) you encountered in our lab but I see that you have updated the thread as 'Answered'. Do you feel there are outstanding issues with the Beta that we should address in future offerings?

Re: Errors seen in systemout.log during federation

Thank you for reporting this. We are trying to recreate this problem in the lab here at IBM in case it can be resolved in a future update. So far, addNode has been successful in all of our tests on the beta. If this is still a concern, do you mind telling us a little more about your setup so we can determine what we are doing differently? Our environment is one Linux machine with WAS8 beta ND (x86_64), IHS, and web server plugin. There are two profiles created through the manageprofiles command like so:
manageprofiles -create -templatePath <WAS_HOME>/profileTemplates/dmgr
manageprofiles -create -templatePath <WAS_HOME>/profileTemplates/default

After starting the dmgr, addNode is run as follows from WAS_HOME:
addNode <host> <dmgr_port> -includeapps -startingport 15060 -profileName AppSrv01

Is there any way in which this environment and these steps differ from yours?

Re: Errors seen in systemout.log during federation

Thank you for working on this.
Still I am facing the same problem.
I am not seeing any error during the federation, the output indicates successfully federated, when refered dmgr logs, it shows some of the files are missing for WebSphereWSDM.

I tried different configuration,
Installed only WAS ND, created two profiles with default and dmgr as the templates without any other options to manageprofile.
Ran the addnode command, still errors are shown in the dmgr systemOut.log.

Re: Errors seen in systemout.log during federation

We have a process in place to diagnose and debug node federation issues. If you are amenable to repeating the scenario, can you please follow the steps listed here in the MustGather document for Federation or removal of node issues
http://www-01.ibm.com/support/docview.wss?rs=180&context=SSCMPDZ&q1=MustGatherDocument&uid=swg21196227&loc=en_US&cs=utf-8&lang=en

The output of the collector script in <WAS_HOME>/bin directory will also help us in debugging this issue. Please note that the Collector tool (collector.bat/sh) can not be run in the WebSphere install directory or a WebSphere install sub directory.
--Thanks,
Rohit Kelapure

Re: Errors seen in systemout.log during federation

Thanks for the additional information on environment. You had mentioned Solaris, and we are also trying to reproduce on Solaris now since the problem has not been found yet on Linux. Knowing that it can happen without supporting products installed helps. There must still be some key difference between our lab environment and yours that explains why we are not hitting the exception regularly, and we are looking for that difference on our side. If you have the time to answer any of the following questions, it would help in providing a faster resolution, but we will continue to work on this either way.

1. Have you tried this at any time on any platform, looked in the logs for this exception, and not seen it? If so, what platform was that on? Since there are some differences between platforms, having an idea if it is all of them or some of them would make a difference.
2. Do you know of any processes that are running on both your Linux and Solaris machine that could be interfering? That may be why we have not been able to reproduce in the IBM lab so far - perhaps you have some additional software running on your systems beyond WAS and the default configuration, i.e. a database or software required by your company.
3. Is there anything in the logs/ffdc directories for either profile? Sometimes the exceptions here provide us with better detail of a failure.

Re: Errors seen in systemout.log during federation

Don't worry about the above questions anymore. This has now been reproduced in the lab on Solaris. We have enough information for the time being. Once again, we appreciate your help in bringing this to our attention so that we can fix the problem in the future.

Re: Errors seen in systemout.log during federation

I wanted to post a follow-up to this thread. I'm attempting to federate a node to a cell on another server, and I receive the exact same errors in the SystemOut.log.

In addition, the node I'm attempting to federate is a WSRR node, and I'm federating to a cell running ESB. The problem I am faced with is, even though the WSRR node federates with errors, when I start the WSRR node, the ESB clusters no longer start. When the WSRR node is stopped or not federated, the ESB clusters start correctly.