Hello,

We are facing tough time in our production environment with the integration servers hanging frequently. Every time it hangs, we see the below exception in the server.log:

“(58009/-4499) [jcc][t4][2055][11259][3.61.65] The database manager is not able to accept new requests, has terminated all requests in progress, or has terminated this particular request due to unexpected error conditions detected at the target system. ERRORCODE=-4499, SQLSTATE=58009”

Any suggestions for the above will be helpful. Let me know if any extra info is needed.

Thanks,

webMethods version=?

Check your java heap size memory and also generate the java thread dump (for analysis)?

As per the error message it says “due to unexpected error conditions detected at the target system” What is the target system here?

Is the IS DB not accessible during that time which obviously prevented the IS normally and hungs can happen?

Did you check the server logs for more information around that time of hung?

Pl include the IS Version and fixes level also.

HTH,
RMG

Version 7.1.2.

Heap:

JAVA_MIN_MEM=2048M
JAVA_MAX_MEM=2048M
JAVA_MAX_PERM_SIZE=256M

Fixes:
IS_7.1.2_Core_Fix43
PRT_7-1-2_Fix4

We’re not heavily using the Audit DB and there are no issues detected with the Audit DB, rather we see that the above is occurring with regard to DB2 (Application Database). But DB2 team confirms that there is nothing wrong on their side during all these times.

Server logs do not show any useful information (than the above information corresponding to each Query failure).

Bad part is that, the frequency of the server hanging is so high that, it happens at least once or twice in a week. I’m still trying to understand whether the error message I posted above is a cause of the issue or a symptom of the issue.

We’re in the verges to move onto 9.5 environment, however, wanted to make sure we don’t get into this problem in the upgraded environment.

I will be glad to provide any other information that you may need to get into the right direction of root cause.

Thanks,

IS712 happens in many cases if the env wasn’t set right and not update to date patch level/config params tuning etc…

But can you set these entries if you are not using audit db and sessions db turnoff in the extended and restart IS?

Always test this in your pre-prod env.

watt.server.auditlog.gd=false
watt.server.auditlog.session=false
watt.server.jca.connectionPool.thresholdWaitingRequest=20 (tune this value based on your 712 environment volumes to start with)

Hope you are not seeing any memory/java core heap dumps in the IntergrationServer directory.please check it also.

HTH,
RMG

Hi Siva,
Next time you see this hung state, take a thread dump by providing the process id of IS instance which will be of great help to find the root cause. Also check how many connections are active/inactive with db by checking with db team, and see if there is any limit on the number of connections that can be established with the application db you are connection with.

-Senthil

I guess,it might be due to missing of jar files especially, db2jcc_license_cisuz.jar. Kindly also request SQL server DBA to put a trace for a couple of days to find how many requests are arriving to DB and how is db response at all intervals. Kindly update forum with latest findings.

Thanks,

Good chance that its a driver issue. The two systems are not brought in sync.

Regards,
Namit Verma

What is your Fix-Level for the DataDirect-Driver (used internally by wM)?
Fix is usually referd to as SCG_x.x.x_DataDirect_Fix

The driver jar is located under common/lib/ext and is named sl53_cj??.jar.
Starting with wM 9.x the file is simply named dd-cjdbc.jar.

Inside you will find two textfiles indicating the exact version in their names.

Remember that MWS had its own copy in wM before 9.x:
MWS/lib/sl53_cj??_driver.jar

Regards,
Holger

Siva,

Did you try to implement any of the options given by forum members, what’s the latest news on this ?

Thanks,