Cannot connect to server

A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.

Moderators: chulett, rschirm, roy

Post Reply
kanasai167
Participant
Posts: 63
Joined: Mon Sep 12, 2011 2:11 am

Cannot connect to server

Post by kanasai167 »

i doing it on vmware ( windows 2003 entreprise)
everything works well , after i give a copy of my vmware mirror to my partner, he got problem login into Datastage , it says " Cannot connect to server " at the login prompt.

i type netstat -ano in command prompt to check whether the port is active or not , but for port 9080 is not exist there.


any idea why this happen ?
dinagiza
Premium Member
Premium Member
Posts: 21
Joined: Tue Dec 11, 2007 3:52 am

Re: Cannot connect to server

Post by dinagiza »

Did you check that all the services are up and running?
(App server, Datastage ...)
kanasai167
Participant
Posts: 63
Joined: Mon Sep 12, 2011 2:11 am

Post by kanasai167 »

yeah , i even restart all the services
the port 9080 is missing i wonder why....
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

The servers are not starting correctly. Check SystemOut.log and SystemErr.log for the WebSphere Application Server. Use the serverStatus.bat command to determine whether server1 is running.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
kanasai167
Participant
Posts: 63
Joined: Mon Sep 12, 2011 2:11 am

Post by kanasai167 »

[9/26/11 10:47:01:663 CST] 0000002d SystemErr R 2011-09-26 10:47:01,600 Error [ISF-SECURITY-REPO] [0013] Error trying to query user "Admin": [Error when executing query:
* SQLException during execution of sql-statement:
* sql statement was 'SELECT A2.password_xmeta FROM ASCLModel_xmetagen_Userb1c497ce A0 INNER JOIN ASCLModel_xmetagen_UserCredentialsb1c497ce A1 ON A0.has_UserCredentials_xmeta = A1.xmeta_repos_object_id_xmeta INNER JOIN ASCLModel_xmetagen_Credentialb1c497ce A2 ON A1.asb_Credential_xmeta = A2.xmeta_repos_object_id_xmeta INNER JOIN ASCLModel_xmetagen_Directoryb1c497ce A3 ON A0.of_Directory_xmeta = A3.xmeta_repos_object_id_xmeta WHERE A0.principalId_xmeta = ? AND A3.name_xmeta = ?'
* Exception message is [[ibm][db2][jcc][t4][2030][11211] A communication error has been detected. Communication protocol being used: TCP/IP.
Communication API being used: SOCKETS. Location where the error was detected: T4Agent.sendRequest().
Communication function detecting the error: OutputStream.flush(). Protocol specific error codes Connection reset by peer: socket write error, *, 0. Message: Connection reset by peer: socket write error]
* Vendor error code [-4499]
* SQL state code [null]
* Target class is 'ASCLModel.xmetagen.User'
* PK of the target object is [_xmeta_repos_object_id]
* 2 values performed in statement:
* [jdbcType=VARCHAR, value=Admin][jdbcType=VARCHAR, value=Security Directory]]. There might be an issue with the database server.

com.ascential.xmeta.exception.ServiceException: Error when executing query:
* SQLException during execution of sql-statement:
* sql statement was 'SELECT A2.password_xmeta FROM ASCLModel_xmetagen_Userb1c497ce A0 INNER JOIN ASCLModel_xmetagen_UserCredentialsb1c497ce A1 ON A0.has_UserCredentials_xmeta = A1.xmeta_repos_object_id_xmeta INNER JOIN ASCLModel_xmetagen_Credentialb1c497ce A2 ON A1.asb_Credential_xmeta = A2.xmeta_repos_object_id_xmeta INNER JOIN ASCLModel_xmetagen_Directoryb1c497ce A3 ON A0.of_Directory_xmeta = A3.xmeta_repos_object_id_xmeta WHERE A0.principalId_xmeta = ? AND A3.name_xmeta = ?'
* Exception message is [[ibm][db2][jcc][t4][2030][11211] A communication error has been detected. Communication protocol being used: TCP/IP.
Communication API being used: SOCKETS. Location where the error was detected: T4Agent.sendRequest().
Communication function detecting the error: OutputStream.flush(). Protocol specific error codes Connection reset by peer: socket write error, *, 0. Message: Connection reset by peer: socket write error]
* Vendor error code [-4499]
* SQL state code [null]
* Target class is 'ASCLModel.xmetagen.User'
* PK of the target object is [_xmeta_repos_object_id]
* 2 values performed in statement:
* [jdbcType=VARCHAR, value=Admin][jdbcType=VARCHAR, value=Security Directory]
at com.ascential.xmeta.service.repository.RepositoryServiceSupport.executeQuery(RepositoryServiceSupport.java:254)
at com.ascential.xmeta.service.repository.RepositoryServiceSupport.executeQuery(RepositoryServiceSupport.java:236)
at com.ascential.xmeta.service.repository.AbstractRepositoryPojoBusiness.executeQuery(AbstractRepositoryPojoBusiness.java:117)
at com.ascential.xmeta.service.repository.AbstractRepositoryPojoBusiness.executeQuery(AbstractRepositoryPojoBusiness.java:195)
at com.ascential.xmeta.binding.repository.impl.AbstractRepositoryBusinessBinding.executeQuery(AbstractRepositoryBusinessBinding.java:169)
at com.ascential.xmeta.binding.repository.impl.AbstractRepositoryBusinessBinding.executeQuery(AbstractRepositoryBusinessBinding.java:122)
at com.ascential.xmeta.client.repository.impl.AbstractDefaultRepositoryClient.query(AbstractDefaultRepositoryClient.java:1402)
at com.ascential.xmeta.client.repository.impl.AbstractDefaultRepositoryClient.query(AbstractDefaultRepositoryClient.java:1309)
at com.ascential.xmeta.client.repository.impl.AbstractDefaultRepositoryClient.query(AbstractDefaultRepositoryClient.java:1282)
at com.ascential.acs.security.repository.ASBRepositoryImpl.findUserPasswordById(ASBRepositoryImpl.java:260)
at com.ascential.acs.security.directory.custom.ASBDirectoryImpl.checkPassword(ASBDirectoryImpl.java:132)
at com.ascential.acs.security.directory.custom.ASBDirectory.checkPassword(ASBDirectory.java:72)
at com.ascential.acs.security.directory.custom.websphere.ASBUserRegistry.checkPassword(ASBUserRegistry.java:90)
at com.ibm.ws.security.registry.UserRegistryImpl.checkPassword(UserRegistryImpl.java:297)
at com.ibm.ws.security.ltpa.LTPAServerObject.authenticate(LTPAServerObject.java:574)
at com.ibm.ws.security.server.lm.ltpaLoginModule.login(ltpaLoginModule.java:437)
at com.ibm.ws.security.common.auth.module.proxy.WSLoginModuleProxy.login(WSLoginModuleProxy.java:122)
at sun.reflect.GeneratedMethodAccessor149.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code))
at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
at javax.security.auth.login.LoginContext.invoke(LoginContext.java:699)
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:151)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:634)
at java.security.AccessController.doPrivileged1(Native Method)
at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))
at javax.security.auth.login.LoginContext.invokeModule(LoginContext.java:631)
at javax.security.auth.login.LoginContext.login(LoginContext.java:557)
at com.ibm.ws.security.auth.JaasLoginHelper.jaas_login(JaasLoginHelper.java:376)
at com.ibm.ws.security.auth.distContextManagerImpl.login(distContextManagerImpl.java:1034)
at com.ibm.ws.security.server.SecurityServerImpl.simple_authenticate(SecurityServerImpl.java:155)
at com.ibm.ws.security.server._SecurityServerImpl_Tie.simple_authenticate(_SecurityServerImpl_Tie.java:116)
at com.ibm.ws.security.server._SecurityServerImpl_Tie._invoke(_SecurityServerImpl_Tie.java:93)
at com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDelegate.java:614)
at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.java:467)
at com.ibm.rmi.iiop.ORB.process(ORB.java:439)
at com.ibm.CORBA.iiop.ORB.process(ORB.java:1761)
at com.ibm.rmi.iiop.Connection.respondTo(Connection.java:2376)
at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2221)
at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:65)
at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:118)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code))
Caused by: com.ascential.xmeta.query.QueryException: Error when executing query:
* SQLException during execution of sql-statement:
* sql statement was 'SELECT A2.password_xmeta FROM ASCLModel_xmetagen_Userb1c497ce A0 INNER JOIN ASCLModel_xmetagen_UserCredentialsb1c497ce A1 ON A0.has_UserCredentials_xmeta = A1.xmeta_repos_object_id_xmeta INNER JOIN ASCLModel_xmetagen_Credentialb1c497ce A2 ON A1.asb_Credential_xmeta = A2.xmeta_repos_object_id_xmeta INNER JOIN ASCLModel_xmetagen_Directoryb1c497ce A3 ON A0.of_Directory_xmeta = A3.xmeta_repos_object_id_xmeta WHERE A0.principalId_xmeta = ? AND A3.name_xmeta = ?'
* Exception message is [[ibm][db2][jcc][t4][2030][11211] A communication error has been detected. Communication protocol being used: TCP/IP.
Communication API being used: SOCKETS. Location where the error was detected: T4Agent.sendRequest().
Communication function detecting the error: OutputStream.flush(). Protocol specific error codes Connection reset by peer: socket write error, *, 0. Message: Connection reset by peer: socket write error]
* Vendor error code [-4499]
* SQL state code [null]
* Target class is 'ASCLModel.xmetagen.User'
* PK of the target object is [_xmeta_repos_object_id]
* 2 values performed in statement:
* [jdbcType=VARCHAR, value=Admin][jdbcType=VARCHAR, value=Security Directory]
at com.ascential.xmeta.persistence.orm.query.impl.sql.util.impl.ojb.OjbSqlQueryExecuter.execute(OjbSqlQueryExecuter.java:132)
at com.ascential.xmeta.persistence.orm.query.impl.sql.SqlQueryPlan.execute(SqlQueryPlan.java:101)
at com.ascential.xmeta.query.impl.engine.RemoveAddedColumns.execute(RemoveAddedColumns.java:45)
at com.ascential.xmeta.query.impl.engine.DataConversionPlan.execute(DataConversionPlan.java:60)
at com.ascential.xmeta.persistence.orm.query.OrmQuery.getResultCollection(OrmQuery.java:161)
at com.ascential.xmeta.persistence.orm.query.OrmQuery.execute(OrmQuery.java:186)
at com.ascential.xmeta.repository.impl.AbstractDefaultRepository.executeQuery(AbstractDefaultRepository.java:1407)
at com.ascential.xmeta.repository.impl.AbstractDefaultRepository.executeQuery(AbstractDefaultRepository.java:737)
at com.ascential.xmeta.service.repository.RepositoryServiceSupport.executeQuery(RepositoryServiceSupport.java:250)
... 40 more
Caused by: org.apache.ojb.broker.PersistenceBrokerSQLException:
* SQLException during execution of sql-statement:
* sql statement was 'SELECT A2.password_xmeta FROM ASCLModel_xmetagen_Userb1c497ce A0 INNER JOIN ASCLModel_xmetagen_UserCredentialsb1c497ce A1 ON A0.has_UserCredentials_xmeta = A1.xmeta_repos_object_id_xmeta INNER JOIN ASCLModel_xmetagen_Credentialb1c497ce A2 ON A1.asb_Credential_xmeta = A2.xmeta_repos_object_id_xmeta INNER JOIN ASCLModel_xmetagen_Directoryb1c497ce A3 ON A0.of_Directory_xmeta = A3.xmeta_repos_object_id_xmeta WHERE A0.principalId_xmeta = ? AND A3.name_xmeta = ?'
* Exception message is [[ibm][db2][jcc][t4][2030][11211] A communication error has been detected. Communication protocol being used: TCP/IP.
Communication API being used: SOCKETS. Location where the error was detected: T4Agent.sendRequest().
Communication function detecting the error: OutputStream.flush(). Protocol specific error codes Connection reset by peer: socket write error, *, 0. Message: Connection reset by peer: socket write error]
* Vendor error code [-4499]
* SQL state code [null]
* Target class is 'ASCLModel.xmetagen.User'
* PK of the target object is [_xmeta_repos_object_id]
* 2 values performed in statement:
* [jdbcType=VARCHAR, value=Admin][jdbcType=VARCHAR, value=Security Directory]
at org.apache.ojb.broker.util.ExceptionHelper.generateException(Unknown Source)
at org.apache.ojb.broker.util.ExceptionHelper.generateException(Unknown Source)
at org.apache.ojb.broker.accesslayer.JdbcAccessImpl.executeSQL(Unknown Source)
at com.ascential.xmeta.persistence.orm.query.impl.sql.util.impl.ojb.OjbSqlQueryExecuter.execute(OjbSqlQueryExecuter.java:99)
... 48 more
Caused by: com.ibm.db2.jcc.c.DisconnectException: [ibm][db2][jcc][t4][2030][11211] A communication error has been detected. Communication protocol being used: TCP/IP.
Communication API being used: SOCKETS. Location where the error was detected: T4Agent.sendRequest().
Communication function detecting the error: OutputStream.flush(). Protocol specific error codes Connection reset by peer: socket write error, *, 0. Message: Connection reset by peer: socket write error
at com.ibm.db2.jcc.b.a.a(a.java:362)
at com.ibm.db2.jcc.b.a.y(a.java(Inlined Compiled Code))
at com.ibm.db2.jcc.b.a.l(a.java(Compiled Code))
at com.ibm.db2.jcc.c.j.c(j.java(Inlined Compiled Code))
at com.ibm.db2.jcc.c.gg.jb(gg.java(Compiled Code))
at com.ibm.db2.jcc.c.gg.a(gg.java(Compiled Code))
at com.ibm.db2.jcc.c.gg.setObject(gg.java(Compiled Code))
at org.apache.ojb.broker.platforms.PlatformDefaultImpl.setObjectForStatement(Unknown Source)
at org.apache.ojb.broker.platforms.PlatformDb2Impl.setObjectForStatement(Unknown Source)
at org.apache.ojb.broker.accesslayer.StatementManager.setObjectForStatement(Unknown Source)
at org.apache.ojb.broker.accesslayer.StatementManager.bindValues(Unknown Source)
... 50 more
Caused by: java.net.SocketException: Connection reset by peer: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java(Compiled Code))
at java.net.SocketOutputStream.write(SocketOutputStream.java(Compiled Code))
at com.ibm.db2.jcc.b.jb.b(jb.java(Compiled Code))
at com.ibm.db2.jcc.b.jb.a(jb.java(Inlined Compiled Code))
... 60 more



this is what i found in my SystemErr.log.
any idea why the servers are not starting correctly?
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

"There might be an issue with the database server."

Has the password you're using when authenticating against XMETA expired?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
kanasai167
Participant
Posts: 63
Joined: Mon Sep 12, 2011 2:11 am

Post by kanasai167 »

ray.wurlod wrote:"There might be an issue with the database server."

Has the password you're using when authenticating against XMETA expired? ...

how can i test whether the XMETA credentials is expired ?
i see in my DB2 control center , the database XMETA DBM state is Started
kanasai167
Participant
Posts: 63
Joined: Mon Sep 12, 2011 2:11 am

Post by kanasai167 »

o , my colleague activate the port 9080 himself and it works now.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

What do you mean by "activate"? Was it blocked in a firewall? There are lots of other ports that may need to be activated too, if this was the problem.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
kanasai167
Participant
Posts: 63
Joined: Mon Sep 12, 2011 2:11 am

Post by kanasai167 »

i not sure how he did that , but now the port 9080 is in listening mode now.

i dont think is firewall issue , because we never switch on the firewall.
Post Reply