Archive for August 2012
a tiny shell based cms system
Posted on: August 30, 2012
Have no time to update this site recently, since I am busy working on my new Blog sys101.doloveyou.com.
At very beginning, I thought installing a copy of wordpress on my tiny server probably everything I need, but as moving along, I come up with an idea, why the fack I need wordpress, can I just have a site without using php, wordpress and mysql?
For sure, I certainly can have a pure html super fast site, but no doubt to much work need to be done manually, for example, after publish an article, you need to manually update something like “article of this month”， “article under a certain category” “last 10 top articles” …in every single page. The more pages you have, the more works you need to deal with manually, I feel tired even by just describing this.
So I am writting a shell based system which make every single page site wide updated whenever a new html file being created.
If this is what you looking for or you want to have a simple personal blog to begin with, then you can visit my new blog sys101.doloveyou.com to have a look what it looks like
The script is now available by enquery box@doloveyou.com
I saw this error message on my websphere process server
[14/08/12 08:50:16:777 NZST] 00000f7f ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl initialize FFDC0009I: FFDC opened incident stream file C:\Program Files\IBM\WebSphere\ProcServer\profiles\wps-profile\logs\ffdc\WPS1.AppTarget.soawpspr1-node.0_00000f7f_12.08.14_08.50.16_0.txt
[14/08/12 08:50:16:793 NZST] 00000f7f ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed incident stream file C:\Program Files\IBM\WebSphere\ProcServer\profiles\wps-profile\logs\ffdc\WPS1.AppTarget.soawpspr1-node.0_00000f7f_12.08.14_08.50.16_0.txt
[14/08/12 08:50:16:793 NZST] 00000f7f XATransaction E J2CA0027E: An exception occurred while invoking prepare on an XA Resource Adapter from dataSource jms/BPECFC, within transaction ID {XidImpl: formatId(57415344), gtrid_length(36), bqual_length(54), data(0000013921c055fb0000000100026403e72eafcab229fa7e4f92b9d171aa4e9b182667390000013921c055fb0000000100026403e72eafcab229fa7e4f92b9d171aa4e9b18266739000000010000000000000000000000000003)}: javax.transaction.xa.XAException: CWSIC8007E: An exception was caught from the remote server with Probe Id 3-013-0010. Exception: .
at com.ibm.ws.sib.comms.common.JFAPCommunicator.parseSingleException(JFAPCommunicator.java:1849)
at com.ibm.ws.sib.comms.common.JFAPCommunicator.getException(JFAPCommunicator.java:1718)
at com.ibm.ws.sib.comms.common.JFAPCommunicator.checkXACommandCompletionStatus(JFAPCommunicator.java:1671)
at com.ibm.ws.sib.comms.client.OptimizedSIXAResourceProxy.prepare(OptimizedSIXAResourceProxy.java:809)
at com.ibm.ws.sib.api.jmsra.impl.JmsJcaRecoverableSiXaResource.prepare(JmsJcaRecoverableSiXaResource.java:251)
at com.ibm.ejs.j2c.XATransactionWrapper.prepare(XATransactionWrapper.java:1110)
at com.ibm.ws.Transaction.JTA.JTAXAResourceImpl.prepare(JTAXAResourceImpl.java:208)
at com.ibm.ws.Transaction.JTA.RegisteredResources.prepareResource(RegisteredResources.java:1410)
at com.ibm.ws.Transaction.JTA.RegisteredResources.distributePrepare(RegisteredResources.java:1726)
at com.ibm.ws.Transaction.JTA.TransactionImpl.prepareResources(TransactionImpl.java:2095)
at com.ibm.ws.Transaction.JTA.TransactionImpl.stage1CommitProcessing(TransactionImpl.java:1656)
at com.ibm.ws.Transaction.JTA.TransactionImpl.processCommit(TransactionImpl.java:1612)
at com.ibm.ws.Transaction.JTA.TransactionImpl.commit(TransactionImpl.java:1547)
at com.ibm.ws.Transaction.JTA.TranManagerImpl.commit(TranManagerImpl.java:247)
at com.ibm.ws.Transaction.JTA.TranManagerSet.commit(TranManagerSet.java:166)
at com.ibm.ejs.csi.TranStrategy.commit(TranStrategy.java:781)
at com.ibm.ejs.csi.TranStrategy.postInvoke(TranStrategy.java:206)
at com.ibm.ejs.csi.TransactionControlImpl.postInvoke(TransactionControlImpl.java:581)
at com.ibm.ejs.csi.UOWControlImpl.postInvoke(UOWControlImpl.java:383)
at com.ibm.ejs.container.EJSContainer.postInvoke(EJSContainer.java:3988)
at com.ibm.ejs.container.MessageEndpointHandler.afterDelivery(MessageEndpointHandler.java:1353)
at com.ibm.ejs.container.MessageEndpointHandler.invokeMessageEndpointMethod(MessageEndpointHandler.java:775)
at com.ibm.ejs.container.MessageEndpointHandler.invoke(MessageEndpointHandler.java:736)
at $Proxy6.afterDelivery(Unknown Source)
at com.ibm.ws.sib.ra.inbound.impl.SibRaTransactionalDispatcher.afterDelivery(SibRaTransactionalDispatcher.java:469)
at com.ibm.ws.sib.ra.inbound.impl.SibRaDispatcher.dispatch(SibRaDispatcher.java:800)
at com.ibm.ws.sib.ra.inbound.impl.SibRaSingleProcessListener$SibRaWork.run(SibRaSingleProcessListener.java:585)
at com.ibm.ejs.j2c.work.WorkProxy.run(WorkProxy.java:419)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1497)
Caused by: com.ibm.websphere.sib.exception.SIErrorException: CWSIC8002E: An internal error occurred. An unknown or unexpected exception was thrown by the core API: exception com.ibm.ws.sib.msgstore.RollbackException: CWSIS1002E: An unexpected exception was caught during transaction completion. Exception: com.ibm.ws.sib.msgstore.PersistenceException: CWSIS1501E: The data source has produced an unexpected exception: com.ibm.db2.jcc.b.SqlException: DB2 SQL Error: SQLCODE=-964, SQLSTATE=57011, SQLERRMC=null, DRIVER=3.52.110.
at com.ibm.ws.sib.comms.common.JFAPCommunicator.parseSingleException(JFAPCommunicator.java:1996)
… 28 more
Caused by: com.ibm.websphere.sib.exception.SIErrorException: CWSIC8002E: An internal error occurred. An unknown or unexpected exception was thrown by the core API: exception com.ibm.ws.sib.msgstore.PersistenceException: CWSIS1501E: The data source has produced an unexpected exception: com.ibm.db2.jcc.b.SqlException: DB2 SQL Error: SQLCODE=-964, SQLSTATE=57011, SQLERRMC=null, DRIVER=3.52.110.
… 29 more
Caused by: com.ibm.websphere.sib.exception.SIErrorException: CWSIC8002E: An internal error occurred. An unknown or unexpected exception was thrown by the core API: exception com.ibm.db2.jcc.b.SqlException: DB2 SQL Error: SQLCODE=-964, SQLSTATE=57011, SQLERRMC=null, DRIVER=3.52.110.
… 29 more
.
[14/08/12 08:50:16:793 NZST] 00000f7f ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl open FFDC0009I: FFDC opened incident stream file C:\Program Files\IBM\WebSphere\ProcServer\profiles\wps-profile\logs\ffdc\WPS1.AppTarget.soawpspr1-node.0_00000f7f_12.08.14_08.50.16_1.txt
[14/08/12 08:50:16:824 NZST] 00000f7f ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed incident stream file C:\Program Files\IBM\WebSphere\ProcServer\profiles\wps-profile\logs\ffdc\WPS1.AppTarget.soawpspr1-node.0_00000f7f_12.08.14_08.50.16_1.txt
[14/08/12 08:50:16:824 NZST] 00000f7f ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl open FFDC0009I: FFDC opened incident stream file C:\Program Files\IBM\WebSphere\ProcServer\profiles\wps-profile\logs\ffdc\WPS1.AppTarget.soawpspr1-node.0_00000f7f_12.08.14_08.50.16_2.txt
[14/08/12 08:50:16:840 NZST] 00000f7f ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed incident stream file C:\Program Files\IBM\WebSphere\ProcServer\profiles\wps-profile\logs\ffdc\WPS1.AppTarget.soawpspr1-node.0_00000f7f_12.08.14_08.50.16_2.txt
[14/08/12 08:50:16:840 NZST] 00000f7f ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl open FFDC0009I: FFDC opened incident stream file C:\Program Files\IBM\WebSphere\ProcServer\profiles\wps-profile\logs\ffdc\WPS1.AppTarget.soawpspr1-node.0_00000f7f_12.08.14_08.50.16_3.txt
[14/08/12 08:50:16:855 NZST] 00000f7f ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed incident stream file C:\Program Files\IBM\WebSphere\ProcServer\profiles\wps-profile\logs\ffdc\WPS1.AppTarget.soawpspr1-node.0_00000f7f_12.08.14_08.50.16_3.txt
[14/08/12 08:50:16:855 NZST] 00000f7f ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl open FFDC0009I: FFDC opened incident stream
you might see this error message for different reasons, but the most common reason
is you run out of transaction log space on db2
three ways to resolve it
you can go to db2cc, —”configuration parameters“
- 1 change LOGSIZE (the size of each transaction log)
- 2 or change LOGPRIMARY (this is the number of primary transaction logs)
- 3 or change both
“WSWS3028E: Error: A _Helper class was not found for”
there are heaps of reason for you to get this error message
but most likely, it is just you FORGET to tick the “Deploy web service” check box when you deploy your application
vm shows “inaccessable”
Posted on: August 21, 2012
some times, you might see your vm name is grey out and it has “inaccessable” beside its name
one possible root cause is , the physical host lost connect to one datastore
the way it might get fixed is
right click the cluster
and click “Rescan for datastores”
if you are not able to start vms in a HA enable cluster due to insufficient resource to failover, then it just mean you can not power any vms in that cluster, or you could power it up by
right click the cluster and “Edit settings”
and apply following change (NOTE: Do not do this unless you know what you are doing or get permission from the right person or group)
System Blog 