Tuxedo SALT 12.2.2 — oracle-tech

    Forum Stats

  • 3,715,760 Users
  • 2,242,859 Discussions
  • 7,845,561 Comments

Discussions

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Tuxedo SALT 12.2.2

Teodoro Orlow Wey
Teodoro Orlow Wey Member Posts: 1
edited February 2020 in Tuxedo

My question is about Oracle Tuxedo 12.2.2. My project is being upgraded from Oracle Tuxedo 12.1.3 to 12.2.2 using the EXACT same codebase for all the domain configuration, same Outbound plugin business logic, libraries and so on. The C code is successfully built, packaged and deployed to the 12.2.2 machine running on RHEL7. The tuxedo instance is up and running, but when I test a request to our Outbound system, the Tuxedo GWWS server crashes and we get a generated coredump. I run the GWWS executable with the coredump in gdb and it shows a segmentation fault:

$ gdb /opt/oracle/tux/tux12.2_salt/tuxedo12.2.2.0.0/bin/GWWS core--GWWS-11-16225-5932-107333-1552309581

GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-110.el7

Copyright (C) 2013 Free Software Foundation, Inc.

License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html

This is free software: you are free to change and redistribute it.

There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details.

This GDB was configured as "x86_64-redhat-linux-gnu".

For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/...

Reading symbols from /opt/oracle/tux/tuxedo_salt-2.2.2.036_S021/tuxedo12.2.2.0.0/bin/GWWS...(no debugging symbols found)...done.

[New LWP 57213]

[New LWP 107333]

[New LWP 107334]

[New LWP 107335]

[New LWP 107336]

[Thread debugging using libthread_db enabled]

Using host libthread_db library "/lib64/libthread_db.so.1".

Core was generated by `GWWS -C dom=[my domain] -g 150 -i 1 -u [my machine address] -U [my codebase]'.

Program terminated with signal 11, Segmentation fault.

#0 0x00007fa8b6638229 in wscfg_svcparam_out () from /opt/oracle/tux/tux12.2_salt/tuxedo12.2.2.0.0/lib/libwsconf.so

I backtrace and it shows:

(gdb) bt

#0 0x00007fa8b6638229 in wscfg_svcparam_out () from /opt/oracle/tux/tux12.2_salt/tuxedo12.2.2.0.0/lib/libwsconf.so

#1 0x00000000004cc384 in nestSoap2Buf ()

#2 0x00000000004b7ea3 in soap2buffer ()

#3 0x000000000043dfb9 in FSM ()

#4 0x00000000004417c6 in thr_func ()

#5 0x00007fa8b422cdd5 in start_thread (arg=0x7fa89ffff700) at pthread_create.c:308

#6 0x00007fa8b30e2b3d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

The build log doesn't show any difference between the code deployed in 12.1.3 and 12.2.2. This is a memory mapping problem but Oracle can't find any issue in the 12.2.2 version of Tuxedo/SALT. What can be the fix if we use identical code and it works on the previous 12.1.3 version?

Sign In or Register to comment.