Tuxedo Client 12 Crash - oracle

We are observing frequent crashes of our Production JVM which runs webMethods v9.12.
After analyzing the crash dumps, we came to conclusion that the reason could be some of the libraries in Tuxedo 12.1.1.0 Client because the crash dump mentioned that the problematic frame was in libwsc.so.71.
To give a history of the issue, the problem of Crash was existing from long time when we were running older version of webMethods (8.2) on JVM 1.6. When we were installing the same, we observed these frequent crashes with Tuxedo 8.x. So, up on advice from our Tuxedo Server Ops Team, we upgraded the Tuxedo client to 12.1.1.0 which reduced the number of crashes considerably.
However, now after upgrading to version 9.12, we are observing the issue of frequent crashes again.
Before Upgrade:
Java Version: 1.6.0_27
Tuxedo: 12.1.1.0
After Upgrade:
Java Version: 1.8.0_151
Tuxedo: 12.1.1.0
Please find sample crash file here
Appreciate any pointers to resolve these crash issues.

I suggest you to report this issue on https://support.oracle.com/ and try to get some help there. I've reported several Tuxedo issues there myself and got fixes or workarounds.
I think StackOverflow is a bad place for asking such questions about Oracle's proprietary software. Programming, configuration - yes, crashes - no/

Related

Twincat run mode error 1861

After trying to start the run mode, I get a fatal error on the target system :
Init7\IO: Set State TComObj PREOP OP >> AdsWarning: 1861 (0x745, ADS
ERROR: timeout elapsed) Anyone of you know how to fix it??
Is your target system running Windows 10? Has it recently been updated (Windows Update) to version 1803? If so, the problem is because TwinCAT is not compatible with the 1803-version of W10. Beckhoff did release an updated TwinCAT version 3.1.4022.20, but removed it as it caused other problems. They will release a new version in the coming days.
That often occurs when you have EtherCAT bus in the system and there are problems. For example you could have an EtherCAT slave configured and it is not found when trying to start the system. So check you I/O configuration.
Of course, the problem could also be the one that Jakob described.
We ran into intermittent 1861 (0x745) errors with Twincat2 on Win10 version 1809 communicating with a CX8090. We did not see the intermittent 1861 errors on Win10 version 1709.
Based off of Jakob's, answer we tried updating the TcAdsDll.dll and AdsDll.dll from the latest Twincat 2.11 x64 Engineering release install (which was 2305) and it resolved our intermittent 1861 errors.
I'm not sure if anyone else out there still uses Twincat2, but this might help someone else searching for a solution to the 1861 error code.

citrix thin client performance issue

I'm having following problem:
We, in our company, are working in a mixed environment. Thin clients (HP-T520) and laptops. Our users connect to a citrix server to go onto the internet. We use a web application for our main business (which we navigate to trough citrix).
We notice a remarkable performance issue on the thin clients. The laptops are not facing this performance issue.
Someone can help me finding the root cause of this issue? I presume there will be some local resources used on the portable which are not available on the thin client, but I do not have a clue where to look or log this.
Thanks in advance!
We managed to resolve the issue. The Thin Clients had Citrix version 4.1 installed. This version doesn't have gfx render. We upgraded to version 4.5, this resolved the issue since it uses hardware acceleration.

freeswitch crash for libspeexdsp.so.1.5.0 error

Hi!I had run a freeswitch for a callcenter ivr service.
During this time, freeswitch crash twice for the similar reasons below:
freeswitch[39310]: segfault at 7f556d514638 ip 00007f55dd909dc6 sp
00007f556d514640 error 6 in libspeexdsp.so.1.5.0[7f55dd8ff000+12000]
Dec 6 17:37:08 calltest kernel: freeswitch[19590]: segfault at
7f96ca9c8b18 ip 00007f96cb3b4dc6 sp 00007f96ca9c8b20 error 6 in
libspeexdsp.so.1.5.0[7f96cb3aa000+12000]
OS version: CentOS release 6.6 (Final)
freeswitch version: FreeSWITCH Version 1.4.19~64bit (64bit)
How can I find out what happen to freeswitch, and fixed the problem?
Thank you for your time.
you need to upgrade FreeSWITCH to the latest version, and open a Jira ticket if the problem persists. You will need to attach as much as possible logs and information to the ticket, so that it's possible to analyze and maybe reproduce.
Also the best would be to migrate to FreeSWITCH version 1.6, as most of development is happening there, and the bugs get fixed faster.

web app deployed on jboss suddenly extremely slow

I have a Web App deployed on JBoss App Server 7.0.2 on Windows XP
It had been running fine for the past 6 months then suddenly, it is painfully slow when launching in Internet Explorer 7
The Web App uses java, facelets, and hibernate. Any suggestions how I can begin to locate the problem? I don't know where I should start.
Start by looking at memory.
Download Visual VM 1.3.3, install all the plugins, and attach it to your JBOSS PID. It'll show you all generations of the heap, CPU, threads, which objects consume the most memory, etc.
Information and insight are what you need. Anything without data is merely a guess.
The other question that needs asking: what "suddenly" changed? I'd start asking about changes on that server: software upgrades, other apps installed, patches, everything.
You should also be looking at dependencies. What about the database server logs?

Idea IntelliJ crash issue on Mac Snow Leopard

I recently installed Idea IntelliJ 10.0.3 on my Mac Snow Leopard. Whenever I try opening a project, IntelliJ starts indexing and in the process crashes!! It happens everytime.
I have Java 1.6.0_15 on my machine. I am not sure if this happens due to specific version of Java or due to a problem with my settings on IntelliJ.
Anybody experienced this before? Any fixes?
JDK 1.6.0_15 is known to crash because of GC bug, installing Apple Java Update is known to resolve this problem (current version is 1.6.0_26). Hardware problem mentioned by #xbit is also possible, but less likely.
I had this issue as well. It turned out to be bad memory in my case. Run Memtest if you are experiencing frequent crashes. Turn computer off, then hold down Command-S while turning on. This will boot you to single user mode. Then run "memtest all 2".

Resources