Initialization failure - qe, caught signal 15

Please could you help me ?
The OMQ is not running any more.
Now when I try to start the group, It has got a error 'signal 15'
The OS is
$ cat /etc/redhat-release
Red Hat Enterprise Linux Server release 5.8 (Tikanga)
LOG
************ dmqgcp (4985) 24-MAR-2014 10:32:33 ************
gcp, group control process for group 126 is running
************ dmqqe (4987) 24-MAR-2014 10:32:33 ************
qe, queuing engine is running
************ dmqgcp (4985) 24-MAR-2014 10:32:33 ************
ipi, message queue operation failed
************ dmqgcp (4985) 24-MAR-2014 10:32:33 ************
gcp, initialization failure
************ dmqqe (4987) 24-MAR-2014 10:32:33 ************
qe, caught signal 15
************ dmqqe (4987) 24-MAR-2014 10:32:33 ************
qe, queuing engine is exiting
************ dmqgcp (4985) 24-MAR-2014 10:32:33 ************
gcp, group control process for group 126 is exiting
TRACE
Start DMQ Processes - start procedura data: (Mon Mar 24 10:32:33 BRT 2014) nodo: snelnxa113.internal.timbrasil.com.br
%STARTUP-I-STARTING, dmqgcp -b 21 -g 126 -f /BECbmq/dmqdir/group/init/GROUP_126.init -n GROUP_126 -l /BECbmq/dmqdir/group/log/GROUP_126.log
IPI 04985:IPI-initializing
IPI 04985:IPI-using bus id 21, group id 126
IPI 04985:IPI-IPIattach_resources
IPI 04985:IPI-attaching ipc queues
IPI 04985:IPI-IPI_engine_write
IPI 04985:IPI-number of bytes to write, 288 (120)
IPI 04985:IPI-IPI_engine_write status
IPI 04985:IPI-IPI_engine_read
IPI 04985:IPI-number of bytes read, 288 (120)
IPI 04985:IPI-IPI_engine_read status
IPI 04985:QE -error status in response to process connect, -256 (FFFFFF00)
IPI 04985:IPI-initialization failure, -43 (FFFFFFD5)

Solved itself after kernel upgrade.

Similar Messages

AS2 adapter failure: Initialization failure

Hi experts,
We had a message in RWB with this error:
Unable to forward message to JCA adapter. Reason: Fatal exception: com.sap.aii.af.ra.cci.XIDeliveryException: SEEBURGER AS2: AS2 Adapter failure # com.seeburger.dt.security.smime.SMIMEHelper (initialization failure), SEEBURGER AS2: AS2 Adapter failure # com.seeburger.dt.security.smime.SMIMEHelper (initialization failure)
Exception caught by adapter framework: Fatal exception: com.sap.aii.af.ra.cci.XIDeliveryException: SEEBURGER AS2: AS2 Adapter failure # com.seeburger.dt.security.smime.SMIMEHelper (initialization failure), SEEBURGER AS2: AS2 Adapter failure # com.seeburger.dt.security.smime.SMIMEHelper (initialization failure)
Delivery of the message to the application using connection AS2_http://seeburger.com/xi failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Fatal exception: com.sap.aii.af.ra.cci.XIDeliveryException: SEEBURGER AS2: AS2 Adapter failure # com.seeburger.dt.security.smime.SMIMEHelper (initialization failure), SEEBURGER AS2: AS2 Adapter failure # com.seeburger.dt.security.smime.SMIMEHelper (initialization failure): javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIDeliveryException: SEEBURGER AS2: AS2 Adapter failure # com.seeburger.dt.security.smime.SMIMEHelper (initialization failure), SEEBURGER AS2: AS2 Adapter failure # com.seeburger.dt.security.smime.SMIMEHelp
There weren't any errors from sxmb_moni, tried checking the com channels and they seem to be working fine. Any help would be appreciated, thanks in advance.
Regards,
Donnie

Hi Doonie
Please check your system cache
Please go through this blog
Seeburger AS2 Adapter No binding found for: AS2, http://seeburger.com/xi
Thanks
Abhishek
**Reward points if helpful**

[Solved] Google Earth has caught signal 11

I'm trying to run Google Earth 7 (latest, AUR: google-earth), but it alway crash after splash screen, output from terminal:
aurelio@Victor-A /opt/google/earth/free % google-earth
Google Earth has caught signal 11.
We apologize for the inconvenience, but Google Earth has crashed.
This is a bug in the program, and should never happen under normal
circumstances. A bug report and debugging data have been written
to this text file:
/home/aurelio/.googleearth/crashlogs/crashlog-516f104c.txt
Please include this file if you submit a bug report to Google.
and file crashlog-516f104c.txt :
Major Version 7
Minor Version 0
Build Number 0003
Build Date Feb 26 2013
Build Time 17:19:26
OS Type 3
OS Major Version 3
OS Minor Version 8
OS Build Version 4
OS Patch Version 0
Crash Signal 11
Crash Time 1366233164
Up Time 1.72212
Stacktrace from glibc:
./libgoogleearth_free.so(+0x1e9f8b)[0xf7611f8b]
./libgoogleearth_free.so(+0x1ea1d3)[0xf76121d3]
linux-gate.so.1(__kernel_sigreturn+0x0)[0xf77c4400]
Thanks in advance!
Last edited by hotvic (2013-04-18 22:06:54)

I've got google-earth alongside google-earth6 and for some reason it isn't working on x86_64, but it is working on i686. It gives me this crashlog:
Major Version 6
Minor Version 2
Build Number 0002
Build Date Apr 14 2012
Build Time 01:09:37
OS Type 3
OS Major Version 3
OS Minor Version 15
OS Build Version 5
OS Patch Version 0
Crash Signal 11
Crash Time 1405604918
Up Time 4.43429
Stacktrace from glibc:
./libgoogleearth_free.so(+0xc645b)[0xf76d445b]
./libgoogleearth_free.so(+0xc66a3)[0xf76d46a3]
linux-gate.so.1(__kernel_sigreturn+0x0)[0xf7786b20]
/opt/google/earth/legacy/libmeasure.so(_ZN5earth7measure5state19MeasureStateContext10OnLoggedInERKNS_4evll11StatusEventE+0x22)[0xe93f3a82]
/opt/google/earth/legacy/libevll.so(_ZN5earth4evll21ConnectionContextImpl11FinishLoginEv+0x4ce)[0xf2d7dc3e]
/opt/google/earth/legacy/libevll.so(_ZN5earth4evll7APIImpl17NotifyInitializedEv+0x165)[0xf2a5c5c5]
/opt/google/earth/legacy/libevll.so(_ZN5earth4evll17RenderContextImpl4initERKNS0_8InitInfoE+0x362)[0xf29db8b2]
./librender.so(_ZN12RenderWidget6SetApiEPN5earth4evll3APIE+0x83)[0xf4890b13]
./librender.so(_ZN5earth6render12RenderWindow12createWidgetEv+0x148)[0xf4876418]
./libgoogleearth_free.so(_ZN5earth6client12ModuleWidget9showEventEP10QShowEvent+0x85)[0xf76a23b5]
./libQtGui.so.4(_ZN7QWidget5eventEP6QEvent+0x770)[0xf6a45a60]
./libQtGui.so.4(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0xac)[0xf69e269c]
./libQtGui.so.4(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x484)[0xf69ed6c4]
./libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x78)[0xf7479ba8]
./libQtGui.so.4(_ZN14QWidgetPrivate11show_helperEv+0x145)[0xf6a476d5]
./libQtGui.so.4(_ZN14QWidgetPrivate14show_recursiveEv+0x7d)[0xf6a473cd]
./libQtGui.so.4(_ZN14QWidgetPrivate12showChildrenEb+0xc5)[0xf6a474b5]
./libQtGui.so.4(_ZN14QWidgetPrivate11show_helperEv+0x61)[0xf6a475f1]
./libQtGui.so.4(_ZN7QWidget10setVisibleEb+0x1db)[0xf6a47a2b]
./libQtGui.so.4(_ZN14QWidgetPrivate12showChildrenEb+0x170)[0xf6a47560]
./libQtGui.so.4(_ZN14QWidgetPrivate11show_helperEv+0x61)[0xf6a475f1]
./libQtGui.so.4(_ZN14QWidgetPrivate14show_recursiveEv+0x7d)[0xf6a473cd]
./libQtGui.so.4(_ZN14QWidgetPrivate12showChildrenEb+0xc5)[0xf6a474b5]
./libQtGui.so.4(_ZN14QWidgetPrivate11show_helperEv+0x61)[0xf6a475f1]
./libQtGui.so.4(_ZN7QWidget10setVisibleEb+0x1db)[0xf6a47a2b]
./libQtGui.so.4(_ZN14QWidgetPrivate12showChildrenEb+0x170)[0xf6a47560]
./libQtGui.so.4(_ZN14QWidgetPrivate11show_helperEv+0x61)[0xf6a475f1]
./libQtGui.so.4(_ZN14QWidgetPrivate14show_recursiveEv+0x7d)[0xf6a473cd]
./libQtGui.so.4(_ZN14QWidgetPrivate12showChildrenEb+0xc5)[0xf6a474b5]
./libQtGui.so.4(_ZN14QWidgetPrivate11show_helperEv+0x61)[0xf6a475f1]
./libQtGui.so.4(_ZN7QWidget10setVisibleEb+0x1db)[0xf6a47a2b]
./libQtGui.so.4(_ZN14QWidgetPrivate12showChildrenEb+0x170)[0xf6a47560]
./libQtGui.so.4(_ZN14QWidgetPrivate11show_helperEv+0x61)[0xf6a475f1]
./libQtGui.so.4(_ZN7QWidget10setVisibleEb+0x1db)[0xf6a47a2b]
./libQtGui.so.4(_ZN14QWidgetPrivate12showChildrenEb+0x170)[0xf6a47560]
./libQtGui.so.4(_ZN14QWidgetPrivate11show_helperEv+0x61)[0xf6a475f1]
./libQtGui.so.4(_ZN7QWidget10setVisibleEb+0x1db)[0xf6a47a2b]
./libQtGui.so.4(_ZN14QWidgetPrivate12showChildrenEb+0x170)[0xf6a47560]
./libQtGui.so.4(_ZN14QWidgetPrivate11show_helperEv+0x61)[0xf6a475f1]
./libQtGui.so.4(_ZN7QWidget10setVisibleEb+0x1db)[0xf6a47a2b]
./libQtGui.so.4(_ZN7QWidget10showNormalEv+0x5c)[0xf6a3516c]
./libgoogleearth_free.so(_ZN10MainWindow18readScreensizeInfoEv+0xdef)[0xf769bacf]
./libgoogleearth_free.so(_ZN5earth6client11Application12SetupMainWinENS0_3Kvw7ProductEb+0x334)[0xf76db8c4]
./libgoogleearth_free.so(_ZN5earth6client11Application3runEv+0x7d2)[0xf76e2e22]
./libgoogleearth_free.so(+0xc511b)[0xf76d311b]
./libgoogleearth_free.so(earthmain+0x249)[0xf76d36f9]
./googleearth-bin[0x804878b]
/usr/lib32/libc.so.6(__libc_start_main+0xde)[0xf512be2e]
I have google-earth installed because I keep having problems with google-earth6, but google-earth is painfully nonresponsive. (Break a new thread if necessary, but it is Signal 11). The font thing is moved to aur, and rebuilding the package from scratch doesn't change anything.

Solaris 8 Installation - Exiting (caught signal 11)

----error message during installation----
Starting Solaris Installation program
Executing Jumpstart preinstall phase
Searching for Solstart directory
Checking rules.ok file
Using begin script: install_begin
Using finish script: patch_finish
Executing Solstart preinstall phase�
Executing begin script �install_begin��.
Begin script install_begin execution completed.
Exiting (caught signal 11)
Type suninstall to restart
After typing suninstall, it hang up and did not continue. I tried to re-install many times but same messages appeared. Please advise at the earliest.
Machine Configuration I Used:
Compaq Proliant 1600 Server
Compaq 15" Monitor
Video Driver = Cirrus Logic GD5446 (1MB)

I don't have any removable media devices connected to this Compaq Proliant 1600 server. I even tried to disconnect the internal tape drive but the same messages I got.
Please advise at the earliest.
Thanks,
Eder

Fileopen Initialization Failure(2)

I receently updated both Acrobat 8 standard and Adobe Reader 9 up to their latest versions. Whenever I open a PDF with either product I get the following message
Fileopen Initialization Failure(2) you will not be able to open protected documents. I am an admin on my system. Anyone have an idea what is going on? I searched the forums and did not find anything related to this issues. Everything worked fine before patching. OS is windows XP SP3 - no microsoft silverlight installed ( I found silverlight could casue much weirdness with Acrobat)

Somehow a version of the fileopen api that was 5 years old was installed in reader directory and the acrobat standard dir. All I did was path the programs and wham error started. I went to the fileopen site and the promptly solved my issue.
Here is their solution
If you aren’t concerned about opening documents using the plug-in you can remove it by finding and deleting all instances of fOpen32.api; as I mentioned, that plug-in was discontinued a long time ago (and our installer only dispenses the current one).
Good job Bernd point me in the right direction
Thanks

NFS stoped working "Caught signal 15, un-registering and exiting"

NFS stoped working for me on my HTPC. I havent updated anything or touched anything at all.
"/etc/rc.d/nfs-common restart" gives me this in "/var/log/errors.log":
Jan 19 22:31:07 Fjuppen mountd[1913]: Caught signal 15, un-registering and exiting.
Dunno whats wrong?

i upgrade yesterday and mounting using the hostname ( mdns ) stop working for some reason i workaround it using udp instead of tcp : mount -o upd hostname.local:/path /localpath not sure if is the same problem ( look like not )

Unable to connect to Oracle Discover Application: ORB Initialization failure

We are running Discoverer 4.1.37 in a DMZ. Some of our internal users receive a "Unable to connect to Oracle Discoverer Application: ORB Initialization failure ..." error when trying to use Discoverer Plus. Our external users are able to connect using Discoverer Plus. We have SSL and Gatekeeper was configured with the machine's IP address (Exterior address), port 443 (exterior port), and exterior proxy address. Networking changes were made to enable users to use one web address instead of two (one for external and one for internal). Also, if I trying to use the machine's IP address in the web address, Discoverer just says "Loading" in the Discoverer Plus status box. If I use the one web address (originally, the external web address), I can log into Discoverer.

How are you trying to connect the database using JPA?
Has your datasource got bind successfully. You should check all these things first. If your datasource has not got binded then debug for that.

CMDTUX_CAT:1685: ERROR: Application initialization failure

PeopleTools 8.19.04 requires an upgrade of tuxedo 6.5 patchlev ?? AND
Jolt, patchlev ?? . There are also some HP patches if you're moving
from tools 8.16 or below. We have successfully booted our BBLs on HP
with tools 8.19.04. Exact patch levels are in the release notes. If
problem continues, you might try PeopleSoft's Customer Connection.
"Wayne W. Scott" <[email protected]> wrote in message news:<[email protected]>...
Kevin:
1) You will get better Tuxedo help in tuxedo.general.
2) Okay, Tuxedo 6.5 on HP-UX 11; show the output from
tail $TUXDIR/udataobj/patchlev
3) Fix the NLS problems with: export NLSPATH=$TUXDIR/locale/C
{ it might be NLS_PATH; I often forget which }
4) It seems you are using PeopleSoft. The problem might lie in the PeopleSoft to Tuxedo
interface, whatever it is. I don't know where to direct you for that.
Wayne Scott
Kevin Medlin wrote:
Hi all,
Kinda new at the tuxedo stuff. Any help is appreciated.
Attempting to boot ...
Booting all admin and server processes in /software/pt819/hrms830/appserv/ps819tm1/PSTUXCFG
INFO: TUXEDO(r) System Release 6.5
INFO: Serial #: 101998665, Expiration NONE, Maxusers 1000000
INFO: Licensed to: PeopleSoft
Booting admin processes ...
exec BBL -A :
process id=12485 ... Started.
Booting server processes ...
exec PSAPPSRV -s@../psappsrv.lst -s@../psqcksrv.lst -sICQuery -sSqlQuery:SqlRequest
-- -C psappsrv.cfg -D PT81 -S PSAPPSRV :
CMDTUX_CAT:1685: ERROR: Application initialization failure
tmboot: CMDTUX_CAT:827: ERROR: Fatal error encountered; initiating user error
handler
exec tmshutdown -y
Shutting down all admin and server processes in /software/pt819/hrms830/appserv/ps819tm1/PSTUXCFG
Shutting down server processes ...
tmboot: CMDTUX_CAT:828: NLS:6: Message not found, catalog CMDTUX_CAT, set 1, num
828
==============ERROR!================
Boot attempt encountered errors!. Check the TUXEDO log for details.
==============ERROR!================
Do you wish to see the error messages in the APPSVR.LOG file? (y/n) [n] :
Shutting down admin processes ...
Server Id = 0 Group Id = dbhrt2 Machine = dbhrt2: shutdown succeeded
1 process stopped.
y
PSADMIN.12243 [04/21/03 15:00:57](0) Begin boot attempt on domain ps819tm1
PSAPPSRV.12486 [04/21/03 15:01:06](0) PeopleTools Release 8.19.04 (HP/UX) starting
PSAPPSRV.12486 [04/21/03 15:01:09](0) Open file cache UPM : use
existing content
( 0) 0xc72c35ec DumpStack__18PSExceptionHandlerFi + 0xbc [software/pt819/hrms830/bin/libpssys.sl]
( 1) 0xc72c2e20 DumpStackEventHandler__18PSExceptionHandlerFPCUs + 0x48 [software/pt819/hrms830/bin/libpssys.sl]
( 2) 0xc72c4154 OnEvent__28CPSStackTraceRequestObserverCF8PS_EVENTPCvPv + 0x1c
[software/pt819/hrms830/bin/libpssys.sl]
( 3) 0xc5dca158 Notify__18CPSEventDispatcherF8PS_EVENTPv + 0x60 [software/pt819/hrms830/bin/libpscmn.sl]
( 4) 0xc5dba5b8 PSAssert__FPCcT1Ui + 0x88 [software/pt819/hrms830/bin/libpscmn.sl]
( 5) 0xc743855c SamIsSrcDB + 0x8c [software/pt819/hrms830/bin/libpssys.sl]
( 6) 0xc7498d6c StmSignon + 0x87c [software/pt819/hrms830/bin/libpssys.sl]
( 7) 0xc14fcd10 SgnDBSignon__FP11SGN_DBPARMS + 0x88 [software/pt819/hrms830/bin/libpssgn.sl]
( 8) 0xc620db5c InitInstance__10CNetServerFiPPUs + 0x434 [software/pt819/hrms830/bin/libpsnetapi.sl]
( 9) 0x000595f8 InitInstance__10CAppServerFiPPUs + 0xb0 [software/pt819/hrms830/bin/PSAPPSRV]
(10) 0x000591a4 tpsvrinit + 0xdc [software/pt819/hrms830/bin/PSAPPSRV]
(11) 0xc5a09f84 _tmmain + 0x328 [software/pt819/tuxedo65/lib/libtux.sl]
(12) 0xc59fcc80 _tmstartserver + 0x78 [software/pt819/tuxedo65/lib/libtux.sl]
(13) 0x00037408 main + 0x44 [software/pt819/hrms830/bin/PSAPPSRV]
(14) 0xc0143158 _start + 0xc0 [lib/libc.2]
(15) 0x00036608 $START$ + 0x1a0 [software/pt819/hrms830/bin/PSAPPSRV]
PSADMIN.12243 [04/21/03 15:01:54](0) End boot attempt on domain ps819tm1
Do you wish to see the error messages in the TUXLOG.042103 file? (y/n) [n] :y
150057.dbhrt2!PSADMIN.12243: Begin boot attempt on domain ps819tm1
150101.dbhrt2!BBL.12485: 04212003: TUXEDO Version 6.5 HP-UX B.11.00 U 9000/898
1623623321 unlimited-user license.
150101.dbhrt2!BBL.12485: LIBTUX_CAT:262: INFO: Standard main starting
150106.dbhrt2!PSAPPSRV.12486: 04212003: TUXEDO Version 6.5 HP-UX B.11.00 U 9000/898
1623623321 unlimited-user license.
150106.dbhrt2!PSAPPSRV.12486: LIBTUX_CAT:262: INFO: Standard main starting
150154.dbhrt2!PSAPPSRV.12486: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
150154.dbhrt2!tmboot.12481: 04212003: TUXEDO Version 6.5 HP-UX B.11.00 U 9000/898
1623623321 unlimited-user license.
150154.dbhrt2!tmboot.12481: tmboot: CMDTUX_CAT:827: ERROR: Fatal error encountered;
initiating user error handler
150154.dbhrt2!tmboot.12481: NLS:6: Message not found, catalog CMDTUX_CAT, set
1, num 724
150154.dbhrt2!PSADMIN.12243: End boot attempt on domain ps819tm1

I get a 'dll initialization failure' dialog

On a maching with a DAQ ATMIO16E running LabView 6.1 I get a 'DLL initialization' failure dialog when I try to open a vi (any vi). Clicking OK clears it but it reappears within a second and LabView wont do anything else. I have just upgraded my OS from Win 98 to Win 2000, but removed and reinstalled LabView completely. On a machine without a DAQ I do *not* get the same problem under the same circumstances (having upgraded that one also).
I should say I had no problems under Win 98 and the card appears to be installed correctly (hardware wizard says its running OK).

Hello;
A valid test you can do is to uninstall the NI-DAQ driver and remove the DAQ device from the machine you are getting the error, and try to run the VIs are giving you the error now.
If the error is still there, the problem is probably on the installation of Labview (make sure you are logged on in an account with administrator privilegies before installing Labview).
If you don't see the error anymore, the problem is on the NI-DAQ installation (also make sure to be an administrator on that machine before installing the Software).
Hope this helps.
Filipe A.
Applications Engineer
National Instruments

Callable Object - Web Service: Initialization failure in GenericServiceFact

Hello,
I am just trying to do the NetWeaver 7.0 exercise
"Callable Objects: Web Service
...In this exercise you will create a callable object as an external web service. A prerequisite to the exercise is that ... the web services container settings in the J2EE Visual Administrator must be set to allow access to the internet.
Author: Composite Application Framework Product Management "
However, when setting up the Callable Object, after entering the WSDL-URL given in the pdf I get the error "<b>Initialization failure in GenericServiceFactory when trying to load http://www.webservicex.net/WeatherForecast.asmx?WSDL</b> ".
Is it the missing activation of internet-access in the J2EE Web container? I can't find any such parameter in the J2EE-config tool (and where has the Visual Admin gone?).
Regards,
Jens

.

G550 (Win7) Logon Process Initialization Failure

Hi,
after restoring my G550 (Win7) with a user created backup via OneKey an error during startup occurs:
"Fehler bei der Initialisierung des interaktiven Anmeldeprozess".
(Logon Process Initialization Failure)
Thanks in advance for your help.
Greetings

Hello mate,
Reinstall windows, something went wrong during install.
Knowledge is of two kinds. We know a subject ourselves, or we know where we can find information on it.
ThinkPad T510 4313-CTO Windows 8 x64 - Intel Core i7-620M - NVIDIA NVS 3100M - 8GB RAM - 240GB SSD- Intel Centrino Ultimate-N 6300 - Gobi 2000.
ThinkPad Helix 3697-CTO Windows 8.1 x64 - Intel Core i7-3667U - Intel HD Graphics 4000 - 8GB RAM- 256GB SSD - Intel Centrino Advanced-N 6205 - Ericsson C5621gw

Red Rocket initialization failure

I started a new project this morning that would use Red R3D media and found the playback of 3K 2:1 R3D media quite choppy and then saw that a red X in the bottom right of Premiere CS 5.5.
Event: Rocket Initialization Failure
Unable to initialize the REDRocket(s). 1 requested, 0 initialized. The SDK reports 1 should be available.
Device 0 returned status: Old driver of firmware, driver available: 0.0.0.0 (1.3.5.0 required), firmware available 0.0.0.0 (1.1.10.1 required).
I am running driver 1.4.7.0 and firmware 1.1.14.38
RedCine-X v487 (Win7/64) sees the card and runs smoothly with it. Windows7 control panel sees it (and the driver/firmware) just fine.
Any suggestions as to why Premiere 5.5.0 can't use the card? Any help would be really appreciated, I need to get a jump on this job.
FYI
Win7/64 (all current patches applied)
12Gb RAM
GeForce GTX 480 with hack
external eSATA RAID
Red Rocket

Bump.
Any Adobe folks reading this? I've tried posting on Reduser as well without any replies.

Worker thread initialization failure

Hello All,
After deploying the application and loading the first page, I am getting the below error.
Can you let me know as what is causing the below issue.
Also let me know If anything more info is needed.
I am using jboss to deploy and It is a enterprise application with ejbs, spring , hibernate and mysql database.
14:17:10,908 ERROR [ServerThread] Worker thread initialization failure
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at org.jboss.remoting.transport.socket.ServerThread.createServerSocketWrapper(ServerThread.java:755)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:375)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:173)
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:258)
at java.io.BufferedInputStream.read(BufferedInputStream.java:317)
at java.io.ObjectInputStream$PeekInputStream.read(ObjectInputStream.java:2266)
at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2279)
at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2750)
at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:780)
at java.io.ObjectInputStream.<init>(ObjectInputStream.java:280)
at org.jboss.remoting.loading.ObjectInputStreamWithClassLoader.<init>(ObjectInputStreamWithClassLoader.java:95)
at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.createInput(JavaSerializationManager.java:54)
at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.getMarshallingStream(SerializableUnMarshaller.jav
a:72)
at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.getMarshallingStream(SerializableUnMarshaller.jav
a:55)
at org.jboss.remoting.transport.socket.ClientSocketWrapper.createInputStream(ClientSocketWrapper.java:179)
at org.jboss.remoting.transport.socket.ClientSocketWrapper.createStreams(ClientSocketWrapper.java:162)
at org.jboss.remoting.transport.socket.ClientSocketWrapper.<init>(ClientSocketWrapper.java:66)
at org.jboss.remoting.transport.socket.ServerSocketWrapper.<init>(ServerSocketWrapper.java:46)
... 7 more
14:17:10,910 ERROR [ServerThread] Worker thread initialization failure
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at org.jboss.remoting.transport.socket.ServerThread.createServerSocketWrapper(ServerThread.java:755)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:375)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:173)
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:258)
at java.io.BufferedInputStream.read(BufferedInputStream.java:317)
at java.io.ObjectInputStream$PeekInputStream.read(ObjectInputStream.java:2266)
at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2279)
at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2750)
at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:780)
at java.io.ObjectInputStream.<init>(ObjectInputStream.java:280)
at org.jboss.remoting.loading.ObjectInputStreamWithClassLoader.<init>(ObjectInputStreamWithClassLoader.java:95)
at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.createInput(JavaSerializationManager.java:54)
at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.getMarshallingStream(SerializableUnMarshaller.jav
a:72)
at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.getMarshallingStream(SerializableUnMarshaller.jav
a:55)
at org.jboss.remoting.transport.socket.ClientSocketWrapper.createInputStream(ClientSocketWrapper.java:179)
at org.jboss.remoting.transport.socket.ClientSocketWrapper.createStreams(ClientSocketWrapper.java:162)
at org.jboss.remoting.transport.socket.ClientSocketWrapper.<init>(ClientSocketWrapper.java:66)
at org.jboss.remoting.transport.socket.ServerSocketWrapper.<init>(ServerSocketWrapper.java:46)
... 7 more

Its in the stacktrace itself.
Caused by: java.net.SocketTimeoutException: Read timed outApparently something in the networking environment is fudging things up. A firewall perhaps? Who knows, good luck finding out.

NoClassDefFoundError: SVGDOMImplementation (initialization failure)

Hi All,
I am trying to convert FO document to PCL using fop and getting
following error while instantiating FOPFactory :
java.lang.NoClassDefFoundError:
org.apache.batik.dom.svg.SVGDOMImplementation (initialization failure)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:134)
at java.lang.Class.forNameImpl(Native Method)
at java.lang.Class.forName(Class.java:130)
at org.apache.fop.image.loader.batik.BatikUtil.isBatikAvailable(BatikUtil.java:33)
at org.apache.fop.image.loader.batik.ImageLoaderFactorySVG.isAvailable(ImageLoaderFactorySVG.java:60)
at org.apache.xmlgraphics.image.loader.spi.ImageImplRegistry.registerLoaderFactory(ImageImplRegistry.java:163)
at org.apache.xmlgraphics.image.loader.spi.ImageImplRegistry.discoverClasspathImplementations(ImageImplRegistry.java:97)
at org.apache.xmlgraphics.image.loader.spi.ImageImplRegistry.<init>(ImageImplRegistry.java:70)
at org.apache.xmlgraphics.image.loader.spi.ImageImplRegistry.getDefaultInstance(ImageImplRegistry.java:79)
at org.apache.xmlgraphics.image.loader.ImageManager.<init>(ImageManager.java:48)
at org.apache.fop.apps.FopFactory.<init>(FopFactory.java:154)
at org.apache.fop.apps.FopFactory.newInstance(FopFactory.java:166)
I am running code on Weblogic 9.2 and all the required libraries
(fop.jar, batik-all.jar and xmlgraphics-commons-1.3.1.jar) are in
class path.
I am using FOP version 0.95
This error does not comes when i run this as a stand-alone program.
And in Weblogic, it appears on a random basis not always.
I doubt that this error appears because weblogic also uses an implementation of batik API but do not have a proof.
Any help in this regard will be much appreciated.
Thanks!
Sanjeev
Edited by: user8649772 on Jul 6, 2010 2:29 PM

Hi and Welcome to the Community!!
I suggest the following steps, in order, even if they seem redundant to what you have already tried (steps 1 and 2 each should result in a message coming to your BB...please wait for that before proceeding to the next step):
1) Register HRT
KB00510 How to register a BlackBerry smartphone with the wireless network
Please wait for one "registration" message to arrive to your Messages app
2) Resend Service Books
KB02830 Send the service books for the BlackBerry Internet Service
Please wait for "Activation" Messages, one per already configured email account, to arrive in your Messages. If you have no already configured email accounts, please wait 1 hour.
3) Batt Pull Reboot
Anytime random strange behavior or sluggishness creeps in, the first thing to do is a battery pop reboot. With power ON, remove the back cover and pull out the battery. Wait about a minute then replace the battery and cover. Power up and wait patiently through the long reboot -- ~5 minutes. See if things have returned to good operation. Like all computing devices, BB's suffer from memory leaks and such...with a hard reboot being the best cure.
Hopefully that will get things going again for you! If not, then you should contact your mobile service provider for formal support.
Good luck!
Occam's Razor nearly always applies when troubleshooting technology issues!
If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
Join our BBM Channels
BSCF General Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code

: ERROR: Application initialization failure

The error report for the subect matter is some what vague on how to go about resolving an initialization failure. Can anyone give some pointers on what to check to try and isolate the problem.
Regards

Hi Todd,
Here's a part of my ULOG file you were asking for. While booting Tuxedo all the other servers booted properly except Rating (6 instances) and Counter server gave following WARNING message.
164949.DCDELSPST!Counter.356542.1.0: 06-09-2007: Tuxedo Version 8.1, 32-bit
164949.DCDELSPST!Counter.356542.1.0: LIBTUX_CAT:262: INFO: Standard main starting
164949.DCDELSPST!Counter.356542.1.0: Initializing Update counter Service ....
164950.DCDELSPST!Counter.356542.1.0: LOGTYPE/S:
164950.DCDELSPST!Counter.356542.1.0: ... Successfully initialized
164950.DCDELSPST!Counter.356542.1.0: LIBTUX_CAT:6205: WARN: Server initialization function did not call tx_open() or tpopen() or this call failed
164950.DCDELSPST!Rating.577820.1.0: 06-09-2007: Tuxedo Version 8.1, 32-bit
164950.DCDELSPST!Rating.577820.1.0: LIBTUX_CAT:262: INFO: Standard main starting
164950.DCDELSPST!Rating.577820.1.0: LOG: ERROR OFF, WARNING OFF, INFO OFF, DEBUG OFF
164950.DCDELSPST!Rating.577820.1.0: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
164950.DCDELSPST!TMSYSEVT.487536.1.0: LIBTUX_CAT:1478: ERROR: .SysServerInit: Rating, group AMDL_APPS_GR, id 200 server initialization failure

Initialization failure - qe, caught signal 15

Similar Messages

Maybe you are looking for