Topic
  • 11 replies
  • Latest Post - ‏2011-05-05T19:24:25Z by SystemAdmin
MaheshKharvi
MaheshKharvi
43 Posts

Pinned topic application server created from pfbc doesn't contain unique ports

‏2011-04-27T10:46:03Z |
I am trying to create app server using PFBC. I observed that the ports generated are not unique while it assigns same port for many end points.

I have tried to use server1 as template still same issue exists.

Attached the port lists and props file.
Updated on 2011-05-05T19:24:25Z at 2011-05-05T19:24:25Z by SystemAdmin
  • RohitK
    RohitK
    38 Posts

    Re: application server created from pfbc doesn't contain unique ports

    ‏2011-04-27T15:56:42Z  
    Mahesh,

    Did you try leveraging the -startingPort and the -portsFile parameter when running the manageProfiles command. startingPort starting_port | -portsFile file_path

    During profile creation, the manageprofiles command uses an automatically generated set of recommended ports if you do NOT specify the -startingPort parameter, the -defaultPorts parameter or the -portsFile parameter.

    The recommended port values can be different than the default port values based on the availability of the default ports. Do not use -startingPort parameter, if you are using the managed profile template.

    See http://bit.ly/hthaMj

    Arguments that can be specified with app_server_root\bin\manageprofiles.bat -create

    1. -profileName profile_name
    2. -profilePath profile_root
    3. -templatePath template_path
    4. -nodeName node_name
    5. -cellName cell_name
    6. -hostName host_name
    7. -serverName server_name
    8. -adminUserName adminUser_ID
    9. -adminPassword adminPassword
    10. -appServerNodeName application_server_node_name
    11. -backupFile backupFile_name
    12. -dmgrAdminPassword password
    13. -dmgrAdminUserName user_name
    14. -dmgrProfilePath dmgr_profile_path
    15. -dmgrHost dmgr_host_name
    16. -dmgrPort dmgr_port_number
    17. -debug
    18. -enableAdminSecurity true | false
    19. -federateLater true | false
    20. -importPersonalCertKS keystore_path
    21. -importPersonalCertKSType keystore_type
    22. -importPersonalCertKSPassword keystore_password
    23. -importPersonalCertKSAlias keystore_alias
    24. -importSigningCertKS keystore_path
    25. -importSigningCertKSType keystore_type
    26. -importSigningCertKSPassword keystore_password
    27. -importSigningCertKSAlias keystore_alias
    28. -isDefault
    29. -isDeveloperServer
    30. -applyPerfTuningSetting standard | peak | development
    31. -keyStorePassword keystore_password
    32. -listAugments
    33. -nodeDefaultPorts
    34. -nodePortsFile node_ports_path
    35. -nodeProfilePathnode_profile_path
    36. -omitAction feature1 feature2... featureN
    37. -personalCertDN distinguished_name
    38. -personalCertValidityPeriod validity_period
    39. -response response_file
    40. -securityLevel security_level
    41. -serverType DEPLOYMENT_MANAGER | ADMIN_AGENT | JOB_MANAGER
    42. -signingCertDN distinguished_name
    43. -signingCertValidityPeriod validity_period
    44. -startingPort starting_port | -portsFile file_path | -defaultPorts
    45. -supportedProtocols supported_protocols
    46. -unaugmentAll
    47. -unaugmentDependents true | false
    48. -validatePorts
    49. -webServerCheck true | false
    50. -webServerHostnamewebserver_host_name
    51. -webServerInstallPath webserver_installpath_name
    52. -webServerName webserver_name
    53. -webServerOS webserver_operating_system
    54. -webServerPluginPath webserver_plugin_path
    55. -webServerPort webserver_port
    56. -webServerType webserver_type
  • MaheshKharvi
    MaheshKharvi
    43 Posts

    Re: application server created from pfbc doesn't contain unique ports

    ‏2011-04-27T16:08:46Z  
    • RohitK
    • ‏2011-04-27T15:56:42Z
    Mahesh,

    Did you try leveraging the -startingPort and the -portsFile parameter when running the manageProfiles command. startingPort starting_port | -portsFile file_path

    During profile creation, the manageprofiles command uses an automatically generated set of recommended ports if you do NOT specify the -startingPort parameter, the -defaultPorts parameter or the -portsFile parameter.

    The recommended port values can be different than the default port values based on the availability of the default ports. Do not use -startingPort parameter, if you are using the managed profile template.

    See http://bit.ly/hthaMj

    Arguments that can be specified with app_server_root\bin\manageprofiles.bat -create

    1. -profileName profile_name
    2. -profilePath profile_root
    3. -templatePath template_path
    4. -nodeName node_name
    5. -cellName cell_name
    6. -hostName host_name
    7. -serverName server_name
    8. -adminUserName adminUser_ID
    9. -adminPassword adminPassword
    10. -appServerNodeName application_server_node_name
    11. -backupFile backupFile_name
    12. -dmgrAdminPassword password
    13. -dmgrAdminUserName user_name
    14. -dmgrProfilePath dmgr_profile_path
    15. -dmgrHost dmgr_host_name
    16. -dmgrPort dmgr_port_number
    17. -debug
    18. -enableAdminSecurity true | false
    19. -federateLater true | false
    20. -importPersonalCertKS keystore_path
    21. -importPersonalCertKSType keystore_type
    22. -importPersonalCertKSPassword keystore_password
    23. -importPersonalCertKSAlias keystore_alias
    24. -importSigningCertKS keystore_path
    25. -importSigningCertKSType keystore_type
    26. -importSigningCertKSPassword keystore_password
    27. -importSigningCertKSAlias keystore_alias
    28. -isDefault
    29. -isDeveloperServer
    30. -applyPerfTuningSetting standard | peak | development
    31. -keyStorePassword keystore_password
    32. -listAugments
    33. -nodeDefaultPorts
    34. -nodePortsFile node_ports_path
    35. -nodeProfilePathnode_profile_path
    36. -omitAction feature1 feature2... featureN
    37. -personalCertDN distinguished_name
    38. -personalCertValidityPeriod validity_period
    39. -response response_file
    40. -securityLevel security_level
    41. -serverType DEPLOYMENT_MANAGER | ADMIN_AGENT | JOB_MANAGER
    42. -signingCertDN distinguished_name
    43. -signingCertValidityPeriod validity_period
    44. -startingPort starting_port | -portsFile file_path | -defaultPorts
    45. -supportedProtocols supported_protocols
    46. -unaugmentAll
    47. -unaugmentDependents true | false
    48. -validatePorts
    49. -webServerCheck true | false
    50. -webServerHostnamewebserver_host_name
    51. -webServerInstallPath webserver_installpath_name
    52. -webServerName webserver_name
    53. -webServerOS webserver_operating_system
    54. -webServerPluginPath webserver_plugin_path
    55. -webServerPort webserver_port
    56. -webServerType webserver_type
    You did not understand my question. I am not talking about server1 created during profile creation.
    I am trying to create additional JVM using PFBC. When I use admin console to create JVM, it creates will all unique ports where as wsadmin assigns same port for multiple end points. Hope this clarifies.
  • SystemAdmin
    SystemAdmin
    462 Posts

    Re: application server created from pfbc doesn't contain unique ports

    ‏2011-04-27T21:46:25Z  
    You did not understand my question. I am not talking about server1 created during profile creation.
    I am trying to create additional JVM using PFBC. When I use admin console to create JVM, it creates will all unique ports where as wsadmin assigns same port for multiple end points. Hope this clarifies.
    Mahesh,

    I just created an application server using PFBC, but I did not see the port issue you reported.

    How did you create the application server using PFBC? Did you create the server using the same way as the one described in the InfoCenter (see the link below)? If not, please create the application server by following the procedure in the link. With the step 3>, beside change the value of "SKIP", please also change the values of "name" and "targetObject" - see below:

    http://publib.boulder.ibm.com/infocenter/wasinfo/beta/index.jsp?topic=%2Fcom.ibm.websphere.express.doc%2Finfo%2Fexp%2Fae%2Ftxml_config_prop_server.html

    #
    1. Create parameters
    2. Replace the line `SKIP=true` with 'SKIP=false' under each section that is needed
    3. Set necessary parameters under each command or step sections
    4. Invoke applyConfigProperties command using this properties file.
    #
    ResourceType=Server
    ImplementingResourceType=Server
    ResourceId=Server=
    SKIP=false <--- change the value from true to false
    CreateDeleteCommandProperties=true
    commandName=createApplicationServer
    #

    #
    #Properties
    #
    name=name #String,required <--- change name to your server name
    templateLocation=null #javax.management.ObjectName
    genUniquePorts=null #Boolean
    bitmode=null #String
    specificShortName=null #String
    clusterName=null #String
    targetObject=targetObject #null,required <---- change targetObject to your node name
    templateName=null #String
    genericShortName=null #String

    If that was the way you did for the server creation, I will need to do some diagnostics to understand more about the problem and its cause.

    Regards,
    Susan Odom
    System Management
    IBM WebSphere Application Server
  • MaheshKharvi
    MaheshKharvi
    43 Posts

    Re: application server created from pfbc doesn't contain unique ports

    ‏2011-04-28T08:36:16Z  
    Mahesh,

    I just created an application server using PFBC, but I did not see the port issue you reported.

    How did you create the application server using PFBC? Did you create the server using the same way as the one described in the InfoCenter (see the link below)? If not, please create the application server by following the procedure in the link. With the step 3>, beside change the value of "SKIP", please also change the values of "name" and "targetObject" - see below:

    http://publib.boulder.ibm.com/infocenter/wasinfo/beta/index.jsp?topic=%2Fcom.ibm.websphere.express.doc%2Finfo%2Fexp%2Fae%2Ftxml_config_prop_server.html

    #
    1. Create parameters
    2. Replace the line `SKIP=true` with 'SKIP=false' under each section that is needed
    3. Set necessary parameters under each command or step sections
    4. Invoke applyConfigProperties command using this properties file.
    #
    ResourceType=Server
    ImplementingResourceType=Server
    ResourceId=Server=
    SKIP=false <--- change the value from true to false
    CreateDeleteCommandProperties=true
    commandName=createApplicationServer
    #

    #
    #Properties
    #
    name=name #String,required <--- change name to your server name
    templateLocation=null #javax.management.ObjectName
    genUniquePorts=null #Boolean
    bitmode=null #String
    specificShortName=null #String
    clusterName=null #String
    targetObject=targetObject #null,required <---- change targetObject to your node name
    templateName=null #String
    genericShortName=null #String

    If that was the way you did for the server creation, I will need to do some diagnostics to understand more about the problem and its cause.

    Regards,
    Susan Odom
    System Management
    IBM WebSphere Application Server
    Same error.

    ResourceType=Server
    ImplementingResourceType=Server
    ResourceId=Server=
    SKIP=false <--- change the value from true to false
    CreateDeleteCommandProperties=true
    commandName=createApplicationServer
    #

    #
    #Properties
    #
    name=ITF #String,required <--- change name to your server name
    templateLocation=null #javax.management.ObjectName
    genUniquePorts=null #Boolean
    bitmode=null #String
    specificShortName=null #String
    clusterName=null #String
    targetObject=ws_nodename #null,required <---- change targetObject to your node name
    templateName=null #String
    genericShortName=null #String
    Let me know what traces you need
  • SystemAdmin
    SystemAdmin
    462 Posts

    Re: application server created from pfbc doesn't contain unique ports

    ‏2011-04-28T14:37:43Z  
    Same error.

    ResourceType=Server
    ImplementingResourceType=Server
    ResourceId=Server=
    SKIP=false <--- change the value from true to false
    CreateDeleteCommandProperties=true
    commandName=createApplicationServer
    #

    #
    #Properties
    #
    name=ITF #String,required <--- change name to your server name
    templateLocation=null #javax.management.ObjectName
    genUniquePorts=null #Boolean
    bitmode=null #String
    specificShortName=null #String
    clusterName=null #String
    targetObject=ws_nodename #null,required <---- change targetObject to your node name
    templateName=null #String
    genericShortName=null #String
    Let me know what traces you need
    The driver I ran could be newer than yours. Could you please tell me which driver you are on so I can install the same driver to see if I am able to reproduce the problem. If not, I will get your help on collecting the trace.

    Thanks,
    Susan Odom
    System Management
    IBM WebSphere Application Server
  • SystemAdmin
    SystemAdmin
    462 Posts

    Re: application server created from pfbc doesn't contain unique ports

    ‏2011-04-28T17:17:44Z  
    The driver I ran could be newer than yours. Could you please tell me which driver you are on so I can install the same driver to see if I am able to reproduce the problem. If not, I will get your help on collecting the trace.

    Thanks,
    Susan Odom
    System Management
    IBM WebSphere Application Server
    I also tried the WebSphere Application Server V8.0 Beta3 driver with version number as "build_3324.02" and build date as 2/9/2011, but I was still not able to reproduce the problem.

    Are you using the Beta 3 driver as well? If not, would you please try the scenario on an install using the Beta 3 driver? If you are using the Beta 3 driver already, could you try to see if you can reproduce the problem on a different install or on a different system?

    Thanks,
    Susan Odom
    System Management
    IBM WebSphere Application Server
  • MaheshKharvi
    MaheshKharvi
    43 Posts

    Re: application server created from pfbc doesn't contain unique ports

    ‏2011-04-29T06:46:31Z  
    I also tried the WebSphere Application Server V8.0 Beta3 driver with version number as "build_3324.02" and build date as 2/9/2011, but I was still not able to reproduce the problem.

    Are you using the Beta 3 driver as well? If not, would you please try the scenario on an install using the Beta 3 driver? If you are using the Beta 3 driver already, could you try to see if you can reproduce the problem on a different install or on a different system?

    Thanks,
    Susan Odom
    System Management
    IBM WebSphere Application Server
    Same issue on other environment too.

    diskSetId=com.ibm.websphere.ND.v80_8.0.0.20110225_2312

    Name IBM WebSphere Application Server - ND
    Version 8.0.0.0
    ID ND
    Build Level hh1108.14
    Build Date 2/25/11
    Architecture PPC32

    1. Created both dmgr and base profiles using -portsFile option and federated node with -portsFile otion. One port is assigned to 3 end points.
    2. Created both dmgr and base profiles using -portsFile option and federated node without specifying ports option. One port is assigned to 3 end points. WC_adminhost, DCS_UNICAST_ADDRESS and WC_adminhost_secure. Another port is assigned to two end points i.e, SIP_DEFAULTHOST and SIP_DEFAULTHOST_SECURE

    3. Created both profiles without specifying ports option. One port is assigned to two end points i.e, SIP_DEFAULTHOST and SIP_DEFAULTHOST_SECURE
  • SystemAdmin
    SystemAdmin
    462 Posts

    Re: application server created from pfbc doesn't contain unique ports

    ‏2011-04-29T15:14:04Z  
    Same issue on other environment too.

    diskSetId=com.ibm.websphere.ND.v80_8.0.0.20110225_2312

    Name IBM WebSphere Application Server - ND
    Version 8.0.0.0
    ID ND
    Build Level hh1108.14
    Build Date 2/25/11
    Architecture PPC32

    1. Created both dmgr and base profiles using -portsFile option and federated node with -portsFile otion. One port is assigned to 3 end points.
    2. Created both dmgr and base profiles using -portsFile option and federated node without specifying ports option. One port is assigned to 3 end points. WC_adminhost, DCS_UNICAST_ADDRESS and WC_adminhost_secure. Another port is assigned to two end points i.e, SIP_DEFAULTHOST and SIP_DEFAULTHOST_SECURE

    3. Created both profiles without specifying ports option. One port is assigned to two end points i.e, SIP_DEFAULTHOST and SIP_DEFAULTHOST_SECURE
    Please help us collect the wsadmin trace by doing the followings:
    • cd $WAS_HOME/profiles/<profileName>/properties
    • edit the file wsadmin.properties to un-comment the following line:
    #com.ibm.ws.scripting.traceString=com.ibm.*=all=enabled
    • cd $WAS_HOME/profiles/<profileName>/bin:
    1> start wsadmin in a local mode (wsadmin -conntype none)
    2> run $AdminTask applyConfigProperties command using the properties file created by $AdminTask createPropertiesFileTemplates command
    3> $AdminConfig save
    4> exit from the wsadmin
    • Send us the following files:
    1> $WAS_HOME/profiles/<profileName>/logs/wsadmin.traceout
    2> $WAS_HOME/profiles/<profileName>/config/cells/<cellName>/nodes/<nodeName>/serverindex.xml

    Thanks,
    Susan Odom
    System Management
    IBM WebSphere Application Server
  • MaheshKharvi
    MaheshKharvi
    43 Posts

    Re: application server created from pfbc doesn't contain unique ports

    ‏2011-05-03T06:55:12Z  
    Please help us collect the wsadmin trace by doing the followings:
    • cd $WAS_HOME/profiles/<profileName>/properties
    • edit the file wsadmin.properties to un-comment the following line:
    #com.ibm.ws.scripting.traceString=com.ibm.*=all=enabled
    • cd $WAS_HOME/profiles/<profileName>/bin:
    1> start wsadmin in a local mode (wsadmin -conntype none)
    2> run $AdminTask applyConfigProperties command using the properties file created by $AdminTask createPropertiesFileTemplates command
    3> $AdminConfig save
    4> exit from the wsadmin
    • Send us the following files:
    1> $WAS_HOME/profiles/<profileName>/logs/wsadmin.traceout
    2> $WAS_HOME/profiles/<profileName>/config/cells/<cellName>/nodes/<nodeName>/serverindex.xml

    Thanks,
    Susan Odom
    System Management
    IBM WebSphere Application Server
    Susan,

    I am not able reproduce the issue when connected in local mode. It assigns all unique ports.

    Let me know what traces you want.

    Thanks,
    Mahesh
  • SystemAdmin
    SystemAdmin
    462 Posts

    Re: application server created from pfbc doesn't contain unique ports

    ‏2011-05-03T22:11:44Z  
    Susan,

    I am not able reproduce the issue when connected in local mode. It assigns all unique ports.

    Let me know what traces you want.

    Thanks,
    Mahesh
    Thanks for the good hit! I was able to reproduce the problem using wsadmin in a connected mode. I was able to see two pairs of duplicated ports:
    1> SIP_DEFAULTHOST and SIP_DEFAULTHOST_SECURE
    2> SIB_ENDPOINT_ADDRESS and SIB_ENPOINT_SECURE_ADDRESS

    I am in the process of diagnosing the root cause and will give you an update with my findings once I am done with the investigation.

    Thanks,
    Susan Odom
    System Management
    IBM WebSphere Application Server
  • SystemAdmin
    SystemAdmin
    462 Posts

    Re: application server created from pfbc doesn't contain unique ports

    ‏2011-05-05T19:24:25Z  
    Thanks for the good hit! I was able to reproduce the problem using wsadmin in a connected mode. I was able to see two pairs of duplicated ports:
    1> SIP_DEFAULTHOST and SIP_DEFAULTHOST_SECURE
    2> SIB_ENDPOINT_ADDRESS and SIB_ENPOINT_SECURE_ADDRESS

    I am in the process of diagnosing the root cause and will give you an update with my findings once I am done with the investigation.

    Thanks,
    Susan Odom
    System Management
    IBM WebSphere Application Server
    Mahesh,

    There is a bug in our code that caused the port issue you reported.

    I have opened a defect to track the issue and will work to deliver a resolution that can be applied to the GA version. Meanwhile, you can run the AdminTask applyConfigProperties command with the parameter "ValidateProperties" set to "false" to workaround the port issue for an application server creation using PFBC.

    Thanks,
    Susan Odom
    System Management
    IBM WebSphere Application Server