another port besides 8879 to deploy EARs using wsadmin?
Is there another port besides 8879 that is involved in transferring EAR
data? I am getting a time out error which leads me to believe this is a
port issue.
 ** TRACE: Looking for container specification matching this environment
 ** TRACE: Found container spec:
DeploymentManager(name='eagnmnmed92cNetwork',
applications=[Application(name='progreg-external-ear',
standardOptions=['usedefaultbindings', 'nopreCompileJSPs',
'distributeApp', 'nouseMetaDataFromBinary', 'nodeployejb',
'createMBeansForResources', 'noreloadEnabled', 'nodeployws',
'validateinstall warn', 'noprocessEmbeddedConfig', 'filepermission
.*\\.dll=755#.*\\.so=755#.*\\.a=755#.*\\.sl=755',
'noallowDispatchRemoteInclude', 'noallowServiceRemoteInclude',
'asyncRequestDispatchType DISABLED', 'nouseAutoLink'],
classLoader=ApplicationClassLoader(single=False, parentLast=True),
securityMapping=None,
modules=[AllModules(appServers=[AppServer(name='ProgReg-Ext-Dev-1')],
webServers=[WebServer(name='eagnmnmed92c-web')],
classLoader=ModuleClassLoader(parentLast=True),
jndiRefs=[SimpleJndiMapping(ref='jdbc/progreg', target='jdbc/progreg'),
SimpleJndiMapping(ref='jndi/amdcMqConnectionFactory',
target='jndi/amdcMqConnectionFactory')])])])
EarFile(path='external-ear-2.12.8-pt.ear')
external-ear-2.12.8-pt.ear
*** ERROR: Failed to deploy external-ear-2.12.8-pt.ear:
java.net.ConnectException: java.net.ConnectException: Connection timed out
 
No comments:
Post a Comment