Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Not able to access home page of websphere portal.

130 views
Skip to first unread message

mank...@yahoo.co.in

unread,
Sep 3, 2007, 9:22:29 AM9/3/07
to
I had installed websphere portal on machine. Till last week it was working fine.
But when i started server today and tried to access portal home page, i could not get it. It is giving HTTP 404 error.
I can successfully access admin page of websphere application server. which shows websphere portal server is running properly.

what could be the problem ? how can i debug this issue ?

Thanks


Oliver Then

unread,
Sep 3, 2007, 10:04:22 AM9/3/07
to
Are there any exceptions in the log files? This would be a good place to
start.


Oliver

mank...@yahoo.co.in

unread,
Sep 3, 2007, 10:41:31 AM9/3/07
to
where can i get log files ?
Because there are more than 2 log folders present on my machine.
should i look into for activity.log because it gets updated after each request or
there is another file ?

mank...@yahoo.co.in

unread,
Sep 3, 2007, 11:06:10 AM9/3/07
to
when i try to invoke portal home page URL i get following exception in SystemOut.log.


[9/3/07 20:34:07:433 IST] 00000014 J2CXAResource W J2CA0061W: Error creating XA Connection and Resource com.ibm.ws.exception.WsException: DSRA8100E: Unable to get a XAConnection from the DataSource. with SQL State : 57019 SQL Code : -1032
at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throw_SQLException(Unknown Source)
at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.check_return_code(Unknown Source)
at COM.ibm.db2.jdbc.app.DB2Connection.connect(Unknown Source)
at COM.ibm.db2.jdbc.app.DB2Connection.<init>(Unknown Source)
at COM.ibm.db2.jdbc.app.DB2ReusableConnection.<init>(Unknown Source)
at COM.ibm.db2.jdbc.DB2PooledConnection.getConnection(Unknown Source)
at COM.ibm.db2.jdbc.DB2XAConnection.<init>(Unknown Source)
at COM.ibm.db2.jdbc.DB2XADataSource.getXAConnection(Unknown Source)
at com.ibm.ws.rsadapter.DSConfigurationHelper$1.run(DSConfigurationHelper.java:1041)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java(Compiled Code))
at com.ibm.ws.rsadapter.DSConfigurationHelper.getPooledConnection(DSConfigurationHelper.java:1036)
at com.ibm.ws.rsadapter.spi.WSRdbDataSource.getPooledConnection(WSRdbDataSource.java:1082)
at com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl.createManagedConnection(WSManagedConnectionFactoryImpl.java:966)
at com.ibm.ejs.j2c.J2CXAResourceFactory$1.run(J2CXAResourceFactory.java:286)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java(Compiled Code))
at com.ibm.ejs.j2c.J2CXAResourceFactory.getXAResource(J2CXAResourceFactory.java:128)
at com.ibm.ws.Transaction.JTA.XARecoveryData.recover(XARecoveryData.java:590)
at com.ibm.ws.Transaction.JTA.PartnerLogTable.recover(PartnerLogTable.java:512)
at com.ibm.ws.Transaction.JTA.RecoveryManager.resync(RecoveryManager.java:1949)
at com.ibm.ws.Transaction.JTA.RecoveryManager.run(RecoveryManager.java:2457)
at java.lang.Thread.run(Thread.java:570)
Caused by: java.sql.SQLException: [IBM][CLI Driver] SQL1032N No start database manager command was issued. SQLSTATE=57019
DSRA0010E: SQL State = 57019, Error Code = -1,032DSRA0010E: SQL State = 57019, Error Code = -1,032
... 21 more

[9/3/07 20:34:07:448 IST] 00000014 J2CXAResource W J2CA0061W: Error creating XA Connection and Resource java.security.PrivilegedActionException: com.ibm.ws.Transaction.XAResourceNotAvailableException: com.ibm.ws.rsadapter.exceptions.DataStoreAdapterException: DSRA8100E: Unable to get a XAConnection from the DataSource., error code: JAVAX_CONN_ERR
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java(Compiled Code))
at com.ibm.ejs.j2c.J2CXAResourceFactory.getXAResource(J2CXAResourceFactory.java:128)
at com.ibm.ws.Transaction.JTA.XARecoveryData.recover(XARecoveryData.java:590)
at com.ibm.ws.Transaction.JTA.PartnerLogTable.recover(PartnerLogTable.java:512)
at com.ibm.ws.Transaction.JTA.RecoveryManager.resync(RecoveryManager.java:1949)
at com.ibm.ws.Transaction.JTA.RecoveryManager.run(RecoveryManager.java:2457)
at java.lang.Thread.run(Thread.java:570)
Caused by: com.ibm.ws.Transaction.XAResourceNotAvailableException: com.ibm.ws.rsadapter.exceptions.DataStoreAdapterException: DSRA8100E: Unable to get a XAConnection from the DataSource., error code: JAVAX_CONN_ERR
at com.ibm.ejs.j2c.J2CXAResourceFactory$1.run(J2CXAResourceFactory.java:309)
... 7 more
Caused by: com.ibm.ws.rsadapter.exceptions.DataStoreAdapterException: DSRA8100E: Unable to get a XAConnection from the DataSource., error code: JAVAX_CONN_ERR
at com.ibm.ws.rsadapter.AdapterUtil.createDataStoreAdapterException(AdapterUtil.java:232)
at com.ibm.ws.rsadapter.spi.WSRdbDataSource.getPooledConnection(WSRdbDataSource.java:1091)
at com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl.createManagedConnection(WSManagedConnectionFactoryImpl.java:966)
at com.ibm.ejs.j2c.J2CXAResourceFactory$1.run(J2CXAResourceFactory.java:286)
... 7 more
Caused by: java.sql.SQLException: [IBM][CLI Driver] SQL1032N No start database manager command was issued. SQLSTATE=57019
DSRA0010E: SQL State = 57019, Error Code = -1,032DSRA0010E: SQL State = 57019, Error Code = -1,032
at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throw_SQLException(Unknown Source)
at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.check_return_code(Unknown Source)
at COM.ibm.db2.jdbc.app.DB2Connection.connect(Unknown Source)
at COM.ibm.db2.jdbc.app.DB2Connection.<init>(Unknown Source)
at COM.ibm.db2.jdbc.app.DB2ReusableConnection.<init>(Unknown Source)
at COM.ibm.db2.jdbc.DB2PooledConnection.getConnection(Unknown Source)
at COM.ibm.db2.jdbc.DB2XAConnection.<init>(Unknown Source)
at COM.ibm.db2.jdbc.DB2XADataSource.getXAConnection(Unknown Source)
at com.ibm.ws.rsadapter.DSConfigurationHelper$1.run(DSConfigurationHelper.java:1041)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java(Compiled Code))
at com.ibm.ws.rsadapter.DSConfigurationHelper.getPooledConnection(DSConfigurationHelper.java:1036)
at com.ibm.ws.rsadapter.spi.WSRdbDataSource.getPooledConnection(WSRdbDataSource.java:1082)
... 9 more

[9/3/07 20:34:07:448 IST] 00000014 RoleBasedAuth E SECJ0306E: No received or invocation credential exist on the thread. The Role based authorization check will not have an accessId of the caller to check. The parameters are: access check method queryConfigObjects:com.ibm.websphere.management.Session:javax.management.ObjectName:javax.management.ObjectName:javax.management.QueryExp on resource ConfigService and module ConfigService. The stack trace is java.lang.Exception: Invocation and received credentials are both null
at com.ibm.ws.security.role.RoleBasedAuthorizerImpl.checkAccess(RoleBasedAuthorizerImpl.java(Compiled Code))
at com.ibm.ws.management.configservice.ConfigServiceServerProxy.securityCheck(ConfigServiceServerProxy.java(Compiled Code))
at com.ibm.ws.management.configservice.ConfigServiceServerProxy$10.run(ConfigServiceServerProxy.java:406)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java(Compiled Code))
at com.ibm.ws.management.configservice.ConfigServiceServerProxy.queryConfigObjects(ConfigServiceServerProxy.java:401)
at com.ibm.ejs.j2c.RALifeCycleManagerImpl.isProviderInstalled(RALifeCycleManagerImpl.java:2688)
at com.ibm.ws.Transaction.JTA.XARecoveryData.recover(XARecoveryData.java:615)
at com.ibm.ws.Transaction.JTA.PartnerLogTable.recover(PartnerLogTable.java:512)
at com.ibm.ws.Transaction.JTA.RecoveryManager.resync(RecoveryManager.java:1949)
at com.ibm.ws.Transaction.JTA.RecoveryManager.run(RecoveryManager.java:2457)
at java.lang.Thread.run(Thread.java:570)

Sebastian Fratini

unread,
Sep 3, 2007, 10:48:01 AM9/3/07
to
You could also try to enter the Portal directly trough the automatic login link. I cannot remember how it is but it would let you authenticate right away. Just in case there is something wrong with just the home page.

Also, did you try http://hostname:10038/myportal ?

Lokk for PortalServerRoot/logs and check traceLog, errorlog, SystemOut or SystemErr

I think those should tell you which is the problem. Also, is the Portal starting as a service? Sometimes it doesn´t start that way and it gives you a -1 error. If you are starting it like that, try starting it from a command and see if everything goes well.

Regards,

Sebastian "Jack" Fratini
IBM Certified System Administrator (Lotus & WebSphere)
dW Space = http://www.ibm.com/developerworks/spaces/yellowsphere
Sebastia...@e-nsx.com
NSX SA

Sebastian Fratini

unread,
Sep 3, 2007, 11:18:22 AM9/3/07
to
I believe there is something wrong with the Database. I would check if DB2 (or your DB Server) is running fine and also, check the admin console to see if there are any references of ODBJ connections. Did you make any change?

Sebastian "Jack" Fratini
IBM Certified System Administrator (Workplace & WebSphere)

mank...@yahoo.co.in

unread,
Sep 3, 2007, 11:35:58 AM9/3/07
to
Thanks Sebastian.
but i haven't made any changes related to database.
how to check whether my DB is running properly or not ?
Also there are many DB2 services running, which services are required to run the portal smoothly ?

Sebastian Fratini

unread,
Sep 3, 2007, 2:56:31 PM9/3/07
to
Well, it should be one big process which is the main service for DB2. I would install the DB2 client and then try to access the Portal databases.

fang

unread,
Sep 3, 2007, 8:12:00 PM9/3/07
to
You can try the following:
1. Stop Portal. If they can't be stopped, kill the Java processes;
2. Restart DB2.
3. Delete the tranlog (<wsas_
4. Restart Portal.

<mank...@yahoo.co.in> wrote in message
news:37113746.1188833795...@ltsgwas010.sby.ibm.com...

mank...@yahoo.co.in

unread,
Sep 6, 2007, 8:22:49 AM9/6/07
to
Now i am able to access portal home page.

some one has installed some software on that machine and after that DB2 server was unable to start-up.(It was showing red square dot on DB2 icon in system try).
I just started that database and restarted server. Now the portal is running smoothly.

pescador

unread,
Sep 6, 2007, 10:17:12 AM9/6/07
to
For future reference, please review the following RedBook for troubleshooting techniques for upgrade problems, "WebSphere Portal Version 6 Enterprise Scale Deployment Best Practices"

http://www.redbooks.ibm.com/abstracts/sg247387.html?Open

Chapter 8 describes troubleshooting techniques for startup problems as well as upgrade, install, configuration, etc.

mank...@yahoo.co.in

unread,
Sep 8, 2007, 2:55:17 AM9/8/07
to
Thank you very much.
0 new messages