port killing command for centos

kill running port on Centos OS.

netstat -plten |grep java

Centos Virtual Machine GUI issue fix

GUI Mode issue Fix for CentOS vm.

if Centos VM machine is not coming up in GUI mode and throwing node link errors So in that situation use fsck command in command line mode for cleaning the corrupted link node after that reboot the VM machine. Surly VM will come up in GUI mode.

# fsck

CTGDIS810E handleException - cannot handle exception , initialize java.net.BindException: Address already in use: JVM_Bind

Assembly Line Error in Web Service Connector:-

09:34:17,721 ERROR - [processIdentityFeed] CTGDIS810E handleException - cannot handle exception , initialize

java.net.BindException: Address already in use: JVM_Bind

                at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:413)

                at java.net.ServerSocket.bind(ServerSocket.java:339)

                at java.net.ServerSocket.<init>(ServerSocket.java:205)

                at javax.net.DefaultServerSocketFactory.createServerSocket(ServerSocketFactory.java:3)

                at com.ibm.di.server.ServerSocketFactoryEX.createServerSocket(ServerSocketFactoryEX.java:129)

                at com.ibm.di.server.ServerSocketFactoryEX.createServerSocket(ServerSocketFactoryEX.java:112)

                at com.ibm.di.server.ServerSocketFactoryEX.createServerSocket(ServerSocketFactoryEX.java:100)

                at com.ibm.di.connector.HTTPServerConnector.initialize(HTTPServerConnector.java:412)

                at com.ibm.di.connector.axis2.Axis2WSServerConnector.initializeServer(Axis2WSServerConnector.java:266)

                at com.ibm.di.connector.axis2.Axis2WSServerConnector.initialize(Axis2WSServerConnector.java:211)

                at com.ibm.di.server.AssemblyLineComponent.doInitialize(AssemblyLineComponent.java:1181)

                at com.ibm.di.server.AssemblyLineComponent.initialize(AssemblyLineComponent.java:1143)

                at com.ibm.di.server.AssemblyLine.executeWithALPool(AssemblyLine.java:4366)

                at com.ibm.di.server.AssemblyLine.run(AssemblyLine.java:1309)

09:34:17,731 ERROR - CTGDIS808E Problem encountered while running AssemblyLine Pool

09:34:17,731 INFO  - CTGDIS286I Waiting for AssemblyLine pool to terminate.

09:34:17,731 INFO  - CTGDIS080I Terminated successfully (2 errors).

Solution: - This error come due to multiple process running on same assembly line in TDI so kill the AL all process from Tdi after that run new one once again

Hope this will help.

CTGDIZ413E Entry Attribute 'xmlString' is missing

Web Service attribute Error:-

9:25:40,928 ERROR - [callws] CTGDIS810E handleException - cannot handle exception , functioncall

java.lang.Exception: CTGDIZ413E Entry Attribute 'xmlString' is missing.

                at com.ibm.di.fc.webservice.InvokeSoapWS.perform(InvokeSoapWS.java:343)

                at com.ibm.di.server.AssemblyLineComponent.executeOperation(AssemblyLineComponent.java:3336)

                at com.ibm.di.server.FunctionComponent.callreply(FunctionComponent.java:303)

                at com.ibm.di.server.AssemblyLine.msExecuteNextConnector(AssemblyLine.java:3750)

                at com.ibm.di.server.AssemblyLine.executeMainStep(AssemblyLine.java:3351)

                at com.ibm.di.server.AssemblyLine.executeMainLoop(AssemblyLine.java:2960)

                at com.ibm.di.server.AssemblyLine.executeMainLoop(AssemblyLine.java:2943)

                at com.ibm.di.server.AssemblyLine.executeAL(AssemblyLine.java:2912)

                at com.ibm.di.server.AssemblyLine.run(AssemblyLine.java:1311)

09:25:40,928 ERROR - CTGDIS266E Error in NextConnectorOperation. Exception occurred: java.lang.Exception: CTGDIZ413E Entry Attribute 'xmlString' is missing.

09:25:40,938 INFO  - CTGDIS100I Printing the Connector statistics.

09:25:40,938 INFO  -  [callws] Errors:1

09:25:40,938 INFO  - CTGDIS104I Total: Errors:2.

09:25:40,938 INFO  - CTGDIS101I Finished printing the Connector statistics.

09:25:40,938 ERROR - CTGDIS077I Failed with error: CTGDIZ413E Entry Attribute 'xmlString' is missing..

Solution:-  I did very simple mistake that I did not provide the value in 'xmlString' attribute in “invokeSoap web Service Function component”  so that’s why error coming so return some value in the 'xmlString' attribute after that it will surly call “Axis2 Web Service Server Connector”  

Hope this will help