WebMethods TN Document Error/Currupted

Hello,

We are facing an issue in production where webmethods TN document types are getting currupted and on TN console the description of document says

ERROR: The java class for this document type was not found.

After restart the error is resolved.

This issue is occuring very frequently. Not sure if we cache document definition into memory which is getting currpted or is it a database issue (DBA mentioned there are no changes to PARTNER / Bizdoc type table since the code is installed) We are seeing this issue since past 4 days.

Thanks,
Ankit Malhotra

What IS/TN version you are running on?

When are you experiencing this error while transports or some changes in prod or inflight transactions

Have you contacted SAG tech support yet and if not open a ticket them?

Also try google it in Empower site in the knowledge center mean time there might be some fix out there for your version/release:

Never seen this corrupt issue unless some one messing up the TN db:

HTH,
RMG

Webmethods version is 6.5 jvm 1.4.

To me it seems that the data for document definiton is queried and stored into either repo db or cache.

Can you confirm if repository db is used to cache document definition of trading network or is that stored in IS cache memory.

We have a SAG person to work on this issue.

Regards,
Ankit Malhotra

It could be that IS repo/document store got corrupted or some thing…No TN document definition is not cached which is internal to TN db as far I know:

Is there any thing changed or updates to your environment recently?

HTH,
RMG

Webmethods version is 6.5 jvm 1.4.

To me it seems that the data for document definiton is queried and stored into either repo db or cache.

Can you confirm if repository db is used to cache document definition of trading network or is that stored in IS cache memory.

We have a SAG person to work on this issue.

Regards,
Ankit Malhotra

Did you check my comments above as you posted same question again?..

SAG person will have you answer anyways:

we applied a number of changes which includes

  1. database pool for repo increased from 5 to 10.
  2. jdbc transaction type was changed from local_transaction to No_transaction.
  3. Earlier we were reaching threshold connection with database which was 350, the connection pool is doubled.
  4. Min connection pool is set to zero for all.
  5. theads are increased from 600 to 800.

earlier we were seeing issues like no native threads available and OOM errors.

on thursday, we increased the connection threshold to 700 (point# 3), from friday onwards we are seeing this issue with TN documents class getting currupted.

Also, under logs i am seeing error like classCastException through out the logs.

[TABLE]
[TR]
[TD]java.lang.ClassCastException: [Ljava.lang.String;[/TD]
[/TR]
[TR]
[TD]at pub.io.streamToBytes(io.java:77)[/TD]
[/TR]
[TR]
[TD]at sun.reflect.GeneratedMethodAccessor143.invoke(Unknown Source)[/TD]
[/TR]
[TR]
[TD]at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)[/TD]
[/TR]
[TR]
[TD]at java.lang.reflect.Method.invoke(Method.java:324)[/TD]
[/TR]
[TR]
[TD]at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:322)[/TD]
[/TR]
[TR]
[TD]at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:612)[/TD]
[/TR]
[TR]
[TD]at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44)[/TD]
[/TR]
[TR]
[TD]at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:235)[/TD]
[/TR]
[TR]
[TD]at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49)[/TD]
[/TR]
[TR]
[TD]at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:198)[/TD]
[/TR]
[TR]
[TD]at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39)[/TD]
[/TR]
[TR]
[TD]at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:411)[/TD]
[/TR]
[TR]
[TD]at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:521)[/TD]
[/TR]
[TR]
[TD]at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:369)[/TD]
[/TR]
[TR]
[TD]at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246)[/TD]
[/TR]
[TR]
[TD]at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:168)[/TD]
[/TR]
[TR]
[TD]at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:324)[/TD]
[/TR]
[TR]
[TD]at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:581)[/TD]
[/TR]
[TR]
[TD]at com.wm.lang.flow.FlowState.step(FlowState.java:438)[/TD]
[/TR]
[TR]
[TD]at com.wm.lang.flow.FlowState.invoke(FlowState.java:403)[/TD]
[/TR]
[TR]
[TD]at com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:982)[/TD]
[/TR]
[TR]
[TD]at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:612)[/TD]
[/TR]
[TR]
[TD]at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44)[/TD]
[/TR]
[TR]
[TD]at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:235)[/TD]
[/TR]
[TR]
[TD]at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49)[/TD]
[/TR]
[TR]
[TD]at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:198)[/TD]
[/TR]
[TR]
[TD]at com.wm.app.b2b.server.invoke.Dis[/TD]
[/TR]
[/TABLE]

I would suggest you better upgrade from 65 to 712/713 or 8.x soon as its already EOS which can be better performed with tuning.

What is the reason for changing this?

jdbc transaction type was changed from local_transaction to No_transaction.