Executing a java application during startup

{color:#0000ff}Hi
Can anybody help me how to execute a java program during startup?
Is there any java inbuilt codes to execute the program in startup?{color}

hi,
just create the java file and compile it in to .class file.
create a batch file (open notepad write these commands.
cd directory name where your java class is
java classname
then go to control panel and click on schedule tasks and schedule this .bat file at system startup.
it will run......

Similar Messages

Executing a java application from c++ using jni

hi,
how do i execute a java application from c++ ?. it should behave similar to typing 'java abc.class' at the dos prompt.
i've done up till recognizing the method id. GetStaticMethodID(). I tried using CallStaticVoidMethod() but didnt work. are there any other methods i should be using?

Look at the source code to the "java" command that is included in the sources that come with the JDK. Since it is the exact code that is run when you type java at the command line, it should be close to what you want.

How to execute a java application once the server starts

I have created a java application which executes correctly. I want this application to execute everytime I start my server. I have modified my web.xml as shown below
<servlet>
<servlet-name>SendEmail</servlet-name>
<servlet-class>
com.allcorp.alliance.tdocs.servlets.SendEmail</servlet-class>
<init-param>
<param-name>config</param-name>
<param-value>/WEB-INF/struts-config.xml</param-value>
<load-on-startup>1</load-on-startup>
</init-param>
</servlet>
I have extended the class with HttpServlet. When I start the server, I get the message saying the class is being initializing but it does not execute. I want the application to execute. Any idea what I need to do.

BalusC wrote:
Implement ServletContextListener and run the appplication on creation of the ServletContext.Well i understand implementation of ServletContextListener and by overiding contextInitialized(ServletContextEvent se) accordingly can solve the problem.
but you need to consider two cases here first
1).ServletContextListener is not supported by all container especially the minor onces which does not support Servlet 2.3 specification.
2).OP does not have any idea of how to use a Servlet first if you can see he had written his intialization code in the main method.Now how can you expect him to create a listener..... :)
I hope there are no hard issues on what i said this time.
*@OP*
My friend the bad news is that you need to spend bit of time learning about servlets.U'd not be writing intialization code inside a main rather you'd be doing it inside public void init(ServletConfig config) method.
by making <load-on-startup><!--value</load-on-startup> in web.xml enables Servlet container to call init method at the time of deployment of the web application else where it'd call the init method whenever servlet encounters first request from a client.
package com.allcorp.alliance.tdocs.servlets;
import java.util.*;
import javax.mail.*;
import javax.mail.internet.*;
import javax.servlet.http.*;
import javax.servlet.*;
import javax.activation.*;
* @author ssa3z
* TODO To change the template for this generated type comment go to
* Window - Preferences - Java - Code Style - Code Templates
public class SendEmail extends HttpServlet{
public void init(ServletConfig config) {
 // SUBSTITUTE YOUR EMAIL ADDRESSES HERE!!!
 String to = "[email protected]";
 String from = "[email protected]";
 // SUBSTITUTE YOUR ISP'S MAIL SERVER HERE!!!
 String host = "smtp.allstate.com";
 // Create properties, get Session
 Properties props = new Properties();
 // If using static Transport.send(),
// need to specify which host to send it to
props.put("mail.smtp.host", host);
// To see what is going on behind the scene
props.put("mail.debug", "true");
Session session = Session.getInstance(props);
try {
 // Instantiatee a message
 Message msg = new MimeMessage(session);
 //Set message attributes
 msg.setFrom(new InternetAddress(from));
 InternetAddress[] address = {new InternetAddress(to)};
 msg.setRecipients(Message.RecipientType.TO, address);
 msg.setSubject("Test E-Mail through Java");
 msg.setSentDate(new Date());
 // Set message content
 msg.setText("This is a test of sending a " +"plain text e-mail through Java.\n" +"Here is line 2.");
 //Send the message
 Transport.send(msg);
}catch (MessagingException mex) {
 mex.printStackTrace();
} Hope this might help :)
REGARDS,
RaHuL

Executing my java application

I was wanting to use a program called AllowIO to open the parallel port for access when I execute my program. At the moment the shortcut is called using javaw so as to not open a dos shell along with my program. The only way I can think of executing the additional application before I run my own is to create a batch and call it but then I am left with a dos shell which I don't want
Is there anyway I can call the Allowio app along with executing my app which is contain in a jar file.
Please Help

Probably the best solution is to run the AllowIO program from the java code.
It'll look something like:
int res;
try {
   String[] params = new String[]{"c:\\wherever\\AllowIO"};
   Process proc = Runtime.getRuntime().exec(params);
   res = proc.waitFor();
catch(IOException e) {
... action for cant run program
catch(InterruptedException e) {
... action for program interrupted
}If your allowIO program produces output it's slightly more complicated.

Executing a Java application from JAVA

Hello all,
I have a problem spawning a Java IRC client from another Java application. The client only manages to execute itself properly [join a specific channel] once the original parent application has been closed. Any ideas?
The code is as follows:
public void run(){
     String[] cmd = {"java", "IRC"};
     try {
           Process p = Runtime.getRuntime().exec(cmd);
          p.waitFor();
     } catch (Exception exc){
          print ("Could not run the IRC session file" + exc);
}

Well, if you ask me, it's not very good Java style to try to access the command line to run ANOTHER Java application.
My suggestion is simply call the IRC program's methods to get it started. Don't bother with Runtime.exec.

Executing a java application

Well i'm sure i'm not the first asking this, and i think i'v seen it before, but is there someway to get rid of the stupid windows console window when you start an application...?
Atm i run this in a bat file, just doing java Application
But i wanna get rid of that blasted java console type of window that always open up.
It is insanely UGLY... anyway to get rid of it? The application looks really unproffessional, because of it... I want this to work like a normal program.
Thanks in advance.

Hmm maybe its because its in a .bat file?
run.bat
which only includes the line:
javaw Application
When clicking on the run.bat it opens up a win console
thing...
Perhaps i shouldn't use a bat file?Perhaps you should use the "start" construct in your BAT file:
start javaw Application
The DOS window is actually for your BAT file, waiting for the javaw to finish (which it won't until your application exits).
By putting the "start" construct in it, the BAT file launches the javaw in the background and runs to completion without waiting for it to finish.
It'll still flicker a DOS window for a second, however. If you want to prevent that, too, then set the BAT-file shortcut properties to start it minimized. That way, only your taskbar will flicker..

Executing an (java)application remotely

Hi,
My problem is simple to describe. 192.168.0.1 is running a java app who wants to execute an entirely different java app on 192.168.0.2. The app should run on 0.2 rather than 0.1.
Currently I use the ProcessBuilder to execute the different java app locally on 0.1. However I have no clue how to execute it via the network while making sure the app actually runs on the 0.2 machine. What I wish to know is how I can remotely execute an application (preferably via the the ProcessBuilder) and keep it running on that machine.
Thank you
Edited by: killingdjef on May 14, 2008 10:20 AM

The same way you would run any other application remotely on that computer. It doesn't matter whether it's Java or not (although of course you do have to have a Java runtime installed there). How exactly would one run an application via the network using the Processbuilder? Again.. I have no problem starting a process locally but I can't seem to figure out how to run it via a network.
One possibility would be to run a servlet (or a custom RMI server, or plain old socket server) on the remote machine that could spawn the application on that machine when contacted. Just be mindful of the security implications. This possibillity crossed my mind (and searches) but I was hoping there would be a more simpler solution. I'm not sure if you are familar with the processbuilder, forgive me if this is redundant, but the processbuilder allows execution of commands. What im trying to find is a command that allows remote execution of a java app. Maybe this is the inappropriate forum for my question?

How to execute a java application from java itself

Hi,
I�m working in Client Server environment. After starting the server, i want to automatically call the client. ( java Server (in Server.java
the call (java Client) has to be done. Can anyone help me for this problem.
thanks.

In normal client server design the client initiates communication with the server, not the other way around.
So you initiate a conversation just like a normal client server communication.
-The client is running.
-The client listens for a connection (SocketServer)
-The server starts up.
-It connects to the client using a socket. (The server must know the host/ip of the client.)

Regarding executing the java application

Exception in thread "main" java.lang.UnsupportedClassVersionError: Hello (Unsupp
orted major.minor version 49.0)
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(Unknown Source)
at java.security.SecureClassLoader.defineClass(Unknown Source)
at java.net.URLClassLoader.defineClass(Unknown Source)
at java.net.URLClassLoader.access$100(Unknown Source)
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)

49.0 is the java.class.version of Java 5.0 -- meaning you code was compiled by a version 5.0 compiler (or later). The fact that you can't run it shows you are trying to use an earlier version of the JRE. Try this:
java -versionThe solution is to make sure your javac.exe and java.exe match.

How to let users run your Java application

Hello,
I'm writing an application using JBuilder7 and it's wonderful designer: so far it is composed by only 2 class and imports java.awt.* and javax.swing.* (SDK 1.4)
Now, I've yet to finish it but I was wondering: "how will users be able to use it?"
I don't want them to install 30+ Mb of SDK so I've looked into the forums and elsewhere and come up with several answers:
1) Let them install JRE: but it's 10+ Mb and they would need to download it separately from my program.
2) Let them use somehow their browser's JVM..(should I turn my application into applet for this? I guess so)
3) Make an .exe: I know there are many programs to make .exe from java but they would make a one-platform-based file.
Also there were many hints about using .jar files to get things easier.
Is there a 4th option in which users have to download only a few mbs to use the application?
And about .jar, how should I use it?
Thank you very much for all your help :)

Simply put - the users must download or be supplied the JRE. This must be installed before they can execute your java application.
As to distributing the application itself - You can jar (Java Archive) your classes into a single file.
You could as has been suggested create an EXE, but these generally are very large and tend to severely restrict the range of java technologies able to be used (EG Serialization, RMI, Reflection, class loading, ...)
Java is not intended for little tools that get installed separately - It is intended for larger applications or small applets in which case the download of the JRE is a minor concern.
Note that applets targeting Java 1.1.7 functionality work fine with most old browsers inbuilt JVMs - Your customers browser may not however have an inbuilt JVM and the user will still need to download the JRE to execute a SWING based applets.
Talden

JCO-Java application unable to open a Frontend GUI session

Hello,

I am having a problem opening a GUI session on a client PC through the JCo java call. It works on some PC's when I am logged in, but not on my PC. But other persons who login on my PC do not have a problem with the application opening a GUI session. I am at a loss. I have had a basis consultant look into this and he could not find a reason for the problem. I have submitted a customer message to SAP and am being told to file this issue in the forum, so here it is. If this is the wrong forum, please let me know which forum would be the correct one.


Problem:
For test purposes, I have created a Java application using the SAP standalone SAPJCO3 vers. 3.0.1. The R/3 backend is 4.6C. The SAPGui version is 7.1 patch level 13 installed on a Windows XP Pro client PC. The application is supposed to start a Frontend GUI session as part of the initial process. This is not working on all PCu2019s for all users. The following are scenarios for two different users on two different PCu2019s, logged on and executing the Java application. The parameters for the Java application are: User, Password, and System Id in this order on the command line after the Java applicationu2019s name. The system Id in our example is PRP in uppercase. This problem happens while connecting to any of our R/3 instances.


Testing of the issue:
Scenario 1:
User gmcghie: This user is the primary user of his/her PC. This PC has not had its registry entries cleaned up for a long time. Starting the Java application from the Windows command line with the supplied parameters, the program is executed and makes the initial connection with the R/3 backend. When the R/3 system sends back a request to start the GUI session, the SAP Logon is executed and opens on the PC. Nothing seems to happen after this.

Here is the JCO exception from the log file:
JCoException eDest: (136)com.sap.conn.jco.JCoException: (136) JCO_ERROR_ILLEGAL_STATE: Launching SAP GUI failed, though it was requested (error message: Communication with SAPGUI timed out)


When you right click on the SAP Logon icon that is in the Windows System Tray on the PC you see an entry that shows a session for Client 000. This is the wrong client being called by the application. The client being called is 600 in this particular scenario.


Here is the connection string sent to backend for scenario 1:
TYPE=A DEST=PRP USER="gmcghie" PASSWD=********** CLIENT=600 LANG=E ASHOST=10.212.120.53 SYSNR=00 TRACE=1 PCS=1 USE_SAPGUI=2


Scenario 2:
User mshin: This user is the primary user of his/her PC. This PC has had the OS re-installed on it within the last few years, hence the registry is likely more clean. Starting the Java application from the Windows command line with the supplied parameters, the program is executed and makes the initial connection with the R/3 backend. When the R/3 system sends back a request to start the GUI session, the SAP Logon is executed and opens on the PC. The connection is made to Client 600 and the process ends. The screens that appear above for the other scenario are not present when the connection is successful. The log file is not included for this as it was empty because it succeeded.


Here is the connection string sent to backend for scenario 2:
TYPE=A DEST=PRP USER="mshin" PASSWD=********** CLIENT=600 LANG=E ASHOST=10.212.120.53 SYSNR=00 TRACE=1 PCS=1 USE_SAPGUI=2

I have the same issue on my PC as the first scenario.
The steps I took to try to get this to work are as follows.
1. Un-installed and re-installed the SAPGui, several times with no change.
2. Compared the registry settings of SAPGui between working and non-working PCu2019s. These were essentially the same.
3. Compared the system variables between working and non-working PCu2019s. These were essentially the same.
It should also be noted that if user u2018gmcghieu2019 from scenario #1 logs into another PC, the program executes correctly (for most other PCs but not all). Finally, if user u2018mshinu2019 from scenario #2 (certain other users as well) logs into Windows on the primary PC for user u2018gmcghieu2019 from scenario #1, and user u2018gmcghieu2019 is used to connect to SAP using the Java program, the program executes correctly. It seems that this would indicate some problem with the useru2019s Windows account on certain PCs.
Why is the connection information being dropped? How is the process of opening the SAPGui on the frontend done?
Any help with this issue is greatly appreciated.
Thanks,
Mark Shirkey

Created Customer Message and got answer. There were settings in Windows Registry for starting the SAP Logon Launch Pad which had to have a value of 1.

Java application crashes due to some problem in native code

Hi All
I have a Java application that calls APIs in a 3rd party DLL(I don't have access to its source code or logs) through my VC++ DLL(Win32) that acts as the wrapper DLL.
The Application has many functionalities and is based on multithreading (both on Java layer as well as C++ layer). Most of the functionalities are working , but when I try to close the application, it crashes.
Moreover the crashing occurs inconstently, sometimes it does not crash. Instead of showing any debug information , it simply creates a error file with disassembly code that I am not able to understand.
Though the error seems like an java error, but actually it seems to be due to native code. I have try catch blocks in my code and also implemented settranslator functionality to get hold of structured/C exceptions. But still I am not able to catch any exceptions.
I am pasting the the contents of the file here:
# An unexpected error has been detected by HotSpot Virtual Machine:
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x7c9111de, pid=488, tid=1848
# Java VM: Java HotSpot(TM) Client VM (1.4.2_14-b05 mixed mode)
# Problematic frame:
# C [ntdll.dll+0x111de]
--------------- T H R E A D ---------------
Current thread (0x009d1790): JavaThread "CompilerThread0" daemon [_thread_in_native, id=1848]
siginfo: ExceptionCode=0xc0000005, reading address 0x00000001
Registers:
EAX=0x00000001, EBX=0x00030000, ECX=0x02d17a18, EDX=0x00030278
ESP=0x02c2f8e8, EBP=0x02c2fb08, ESI=0x02d17a10, EDI=0x00000001
EIP=0x7c9111de, EFLAGS=0x00010202
Top of Stack: (sp=0x02c2f8e8)
0x02c2f8e8: 009fa9a0 000000c0 00000008 0811d3d8
0x02c2f8f8: 0000000c 00a2c0e0 00000003 00000004
0x02c2f908: 08018216 00000001 02c2fcc4 08018385
0x02c2f918: 00000002 00000001 02c2f93c 02d06d0c
0x02c2f928: 0802a50a 00000000 00000001 02c2f93c
0x02c2f938: 04a3cb4c 02d01008 02c2f964 0802a850
0x02c2f948: 02c2f96e 00000000 00000007 00000000
0x02c2f958: 04a3cb38 00000004 08018216 00000001
Instructions: (pc=0x7c9111de)
0x7c9111ce: 39 89 bd 0c ff ff ff 8b 46 0c 89 85 68 ff ff ff
0x7c9111de: 8b 10 3b 57 04 0f 85 8c 31 02 00 3b d1 0f 85 84
Stack: [0x02bf0000,0x02c30000), sp=0x02c2f8e8, free space=254k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [ntdll.dll+0x111de]
C [MSVCRT.dll+0x1c3c9]
C [MSVCRT.dll+0x1c3e7]
C [MSVCRT.dll+0x1c42e]
V [jvm.dll+0xacda9]
V [jvm.dll+0x17102]
V [jvm.dll+0x16c8d]
V [jvm.dll+0x16dca]
V [jvm.dll+0x170a7]
V [jvm.dll+0x172e8]
V [jvm.dll+0x4dc65]
V [jvm.dll+0x4d894]
V [jvm.dll+0xd3a36]
V [jvm.dll+0xd3a04]
C [MSVCRT.dll+0x2a3b0]
C [kernel32.dll+0xb683]
Current CompileTask:
HotSpot Client Compiler:423 b sun.awt.AWTAutoShutdown.isReadyToShutdown()Z (33 bytes)
--------------- P R O C E S S ---------------
Java Threads: ( => current thread )
0x049d6328 JavaThread "Thread-19" [_thread_blocked, id=1440]
0x049d24d0 JavaThread "Thread-18" [_thread_blocked, id=3620]
0x049d40c8 JavaThread "Thread-17" [_thread_blocked, id=2476]
0x02df0538 JavaThread "TimerQueue" daemon [_thread_blocked, id=3876]
0x00036a78 JavaThread "DestroyJavaVM" [_thread_blocked, id=2448]
0x02e43768 JavaThread "Thread-6" [_thread_blocked, id=3664]
0x02e23130 JavaThread "Thread-4" [_thread_blocked, id=2816]
0x02e21d08 JavaThread "Thread-2" [_thread_blocked, id=3344]
0x02da3f78 JavaThread "Java2D Disposer" daemon [_thread_blocked, id=2528]
0x02da3268 JavaThread "AWT-EventQueue-0" [_thread_in_native, id=4008]
0x02d91f90 JavaThread "AWT-Windows" daemon [_thread_blocked, id=648]
0x02d3a478 JavaThread "AWT-Shutdown" [_thread_blocked, id=2988]
=>0x009d1790 JavaThread "CompilerThread0" daemon [_thread_in_native, id=1848]
0x009d0a90 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=3568]
0x009ce128 JavaThread "Finalizer" daemon [_thread_blocked, id=1824]
0x009ccda0 JavaThread "Reference Handler" daemon [_thread_blocked, id=3280]
Other Threads:
0x00a0b6e8 VMThread [id=608]
0x00a0d620 WatcherThread [id=3012]
VM state:not at safepoint (normal execution)
VM Mutex/Monitor currently owned by a thread: None
Heap
def new generation total 640K, used 583K [0x10010000, 0x100c0000, 0x104f0000)
eden space 576K, 90% used [0x10010000, 0x10091e40, 0x100a0000)
from space 64K, 99% used [0x100b0000, 0x100bfff8, 0x100c0000)
to space 64K, 0% used [0x100a0000, 0x100a0000, 0x100b0000)
tenured generation total 7772K, used 5451K [0x104f0000, 0x10c87000, 0x14010000)
the space 7772K, 70% used [0x104f0000, 0x10a42d80, 0x10a42e00, 0x10c87000)
compacting perm gen total 8192K, used 8137K [0x14010000, 0x14810000, 0x18010000)
the space 8192K, 99% used [0x14010000, 0x148024e8, 0x14802600, 0x14810000)
Dynamic libraries:
0x00400000 - 0x0040b000 c:\dcsthick\jre\bin\java.exe
0x7c900000 - 0x7c9b0000 C:\WINDOWS\system32\ntdll.dll
0x7c800000 - 0x7c8f5000 C:\WINDOWS\system32\kernel32.dll
0x77dd0000 - 0x77e6b000 C:\WINDOWS\system32\ADVAPI32.dll
0x77e70000 - 0x77f01000 C:\WINDOWS\system32\RPCRT4.dll
0x77c10000 - 0x77c68000 C:\WINDOWS\system32\MSVCRT.dll
0x08000000 - 0x08143000 c:\dcsthick\jre\bin\client\jvm.dll
0x7e410000 - 0x7e4a1000 C:\WINDOWS\system32\USER32.dll
0x77f10000 - 0x77f57000 C:\WINDOWS\system32\GDI32.dll
0x76b40000 - 0x76b6d000 C:\WINDOWS\system32\WINMM.dll
0x76390000 - 0x763ad000 C:\WINDOWS\system32\IMM32.DLL
0x10000000 - 0x10007000 c:\dcsthick\jre\bin\hpi.dll
0x76bf0000 - 0x76bfb000 C:\WINDOWS\system32\PSAPI.DLL
0x00390000 - 0x0039e000 c:\dcsthick\jre\bin\verify.dll
0x003b0000 - 0x003c9000 c:\dcsthick\jre\bin\java.dll
0x003d0000 - 0x003de000 c:\dcsthick\jre\bin\zip.dll
0x02e70000 - 0x02f84000 C:\dcsthick\jre\bin\awt.dll
0x73000000 - 0x73026000 C:\WINDOWS\system32\WINSPOOL.DRV
0x774e0000 - 0x7761d000 C:\WINDOWS\system32\ole32.dll
0x5ad70000 - 0x5ada8000 C:\WINDOWS\SYSTEM32\uxtheme.dll
0x02fe0000 - 0x03031000 C:\dcsthick\jre\bin\fontmanager.dll
0x73760000 - 0x737a9000 C:\WINDOWS\system32\ddraw.dll
0x73bc0000 - 0x73bc6000 C:\WINDOWS\system32\DCIMAN32.dll
0x73940000 - 0x73a10000 C:\WINDOWS\system32\D3DIM700.DLL
0x74720000 - 0x7476b000 C:\WINDOWS\system32\MSCTF.dll
0x755c0000 - 0x755ee000 C:\WINDOWS\system32\msctfime.ime
0x03320000 - 0x0333c000 C:\dcsthick\lib\CrewsDmApiJniNt.dll
0x031b0000 - 0x031bb000 c:\dcsthick\lib\CRWNT_DM.dll
0x03240000 - 0x03249000 c:\dcsthick\lib\BAT_API.dll
0x03340000 - 0x03352000 c:\dcsthick\lib\DC_DSM32.dll
0x03360000 - 0x03369000 c:\dcsthick\lib\CRWTOOLS.dll
0x77c00000 - 0x77c08000 C:\WINDOWS\system32\VERSION.dll
0x03370000 - 0x0337a000 c:\dcsthick\lib\PMAPI.dll
0x5d090000 - 0x5d12a000 C:\WINDOWS\system32\COMCTL32.dll
0x03790000 - 0x037b2000 c:\dcsthick\ResaDLL\DC_DSMNB.dll
0x5b860000 - 0x5b8b4000 C:\WINDOWS\system32\NETAPI32.dll
0x038d0000 - 0x038f2000 c:\dcsthick\ResaDLL\DC_DSMIP.dll
0x71ad0000 - 0x71ad9000 C:\WINDOWS\system32\WSOCK32.dll
0x71ab0000 - 0x71ac7000 C:\WINDOWS\system32\WS2_32.dll
0x71aa0000 - 0x71aa8000 C:\WINDOWS\system32\WS2HELP.dll
0x71a50000 - 0x71a8f000 C:\WINDOWS\system32\mswsock.dll
0x662b0000 - 0x66308000 C:\WINDOWS\system32\hnetcfg.dll
0x71a90000 - 0x71a98000 C:\WINDOWS\System32\wshtcpip.dll
0x76f20000 - 0x76f47000 C:\WINDOWS\system32\DNSAPI.dll
0x76fb0000 - 0x76fb8000 C:\WINDOWS\System32\winrnr.dll
0x76f60000 - 0x76f8c000 C:\WINDOWS\system32\WLDAP32.dll
0x66580000 - 0x6658f000 C:\WINDOWS\system32\pnrpnsp.dll
0x76fc0000 - 0x76fc6000 C:\WINDOWS\system32\rasadhlp.dll
0x032e0000 - 0x0330a000 C:\dcsthick\lib\ResaHostConnection.dll
0x03250000 - 0x03257000 c:\dcsthick\lib\CRWNT_GWALC.dll
0x03310000 - 0x03319000 c:\dcsthick\lib\ALCAPI.dll
0x763b0000 - 0x763f9000 C:\WINDOWS\system32\comdlg32.dll
0x77f60000 - 0x77fd6000 C:\WINDOWS\system32\SHLWAPI.dll
0x7c9c0000 - 0x7d1d7000 C:\WINDOWS\system32\SHELL32.dll
0x773d0000 - 0x774d3000 C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2982_x-ww_ac3f9c03\comctl32.dll
VM Arguments:
jvm_args: -Dcfdynaproppath=c:\dcsthick/config/ -Dcfdynapropxml=RESA_KCOdynamicproperties.xml -DConfigPath=c:\dcsthick/config/RESA_KCOConfig.xml -DResolution=High -DWorkstationID=GWGTE -DMode=GateBoarding -DlogPath=c:\temp\kcologs -DlogInformation=0 -DGateway=ALCSQ1 -DNetBiosPort=A
java_command: com.singaporeair.dcs.standalone.application.model.ApplicationModel SQ/IGATEADXX
Launcher Type: SUN_STANDARD
Environment Variables:
JAVA_HOME=c:\dcsthick\jre\bin
PATH=c:\dcsthick\jre\bin;c:\dcsthick/lib;c:\dcsthick/ResaDLL
USERNAME=USER
OS=Windows_NT
PROCESSOR_IDENTIFIER=x86 Family 6 Model 15 Stepping 13, GenuineIntel
--------------- S Y S T E M ---------------
OS: Windows XP Build 2600 Service Pack 2
CPU:total 2 family 6, cmov, cx8, fxsr, mmx, sse, sse2
Memory: 4k page, physical 1039600k(565656k free), swap 2501208k(2091128k free)
vm_info: Java HotSpot(TM) Client VM (1.4.2_14-b05) for windows-x86, built on Mar 14 2007 16:46:11 by "java_re" with MS VC++ 6.0
The JAVA Application during initialisation establishes a connection with the host server for various devices. For each of the device it establishes a separate connection and keeps listening on these connections using multithreading.
During App close, we need to close each of these connections one by one for each device.
The opening /closing of connection is done by 3rd party DLL and call to there APIs is done through a C++ Wrapper DLL that I have built between the Java layer and their DLL.
When we close the Application, I am always able to close the connections on the first 2 devices. Then all of a sudden it crashes either for the 3rd device conn. close or for the 4th one. The code is the same for all the devices . That too sometimes it just goes fine without crashing. If its a null pointer exception, why is it that it crashes on some occassions and not in other times. More importantly, why is it that it does not fail for the first 2 devices , but fails for the 3rd or 4th device connection close?
Can please anyone help me. Please suggest me as to how I can determine the cause of the error.
And is this error really coming in ntdll.dll or is it getting caused of my dll?

The opening /closing of connection is done by 3rd party DLL and call to there APIs is done through a C++ Wrapper DLL that I have built between the Java layer and their DLL.The specific error indicates a pointer/memory problem.
The first place that is likely is in your code.
The second most likely place for the cause is because you are using the third party library incorrectly. For example before exiting you are supposed to clean up resources and you are not doing so.
As a remote possibility, much less likely that either of the above, there is a bug in jnative or in the 3rd party library.

How to execute a Java method when row inserted into a database table?

I have the need to fire off a java method when a row is inserted into a database table. I am unfortunately working with MySQL which just recently supported triggers but these new triggers can not execute a Java application on any event.
What I am looking for is an event driven approach such that when a row is inserted into a specific table I can fire off a java method (sitting in a tomcat container) that will take the contents and send it to a web service.
It has been mentioned that JMS may have the ability to poll and monitor a database table. Just wondering if anyone could point me in the right direction.
thanks
JavaTek

A service handler might be the right way to run some code at the end of a service call (another way would be to make use of filters).
First, make sure your static table is merged with ServiceHandlers.
Secondary, change your custom method name into one that is not already in the service definition of COLLECTION_COPY_LOT (preferably a unique method name like collectionCopyLotLastAction that describes its purpose) and remove the following line from your code:
m_service.doCodeEx("",this);Now create a service definition for COLLECTION_COPY_LOT in your custom component based on the original COLLECTION_COPY_LOT (copy paste from the original service definition) and add you own method collectionCopyLotLastAction as the last step in the service. Play with the load order to make sure CS is using your service definition of COLLECTION_COPY_LOT instead of the original.
regards,
Fabian

Pass return code from Java application to a .bat file.

I have a .bat file which will execute a Java application. I want to pass the return code from the java application to the ".bat" file.
Could you please let me know, how can I accomplish this.

I tried that, but it doesn't return the value...
In my Java app, I had System.exit(returnCode) and in the '.bat' file
I have
@echo off
java <myApp>
set returnCd=%?%
echo %returnCd
and it didn't return any value. What should I specify in set returnCd=%?% instead of ?

Message bean does not start automatically during application server startup

I have a message bean that does not start up during application server startup. I am able to successfully start the application manually using the visual admin tool.I searched the logs and found the following error. The error references the "QueueConnectionFactory" is not deployed or is not started. I have check and the "QueueConnectiopnFactory" is deployed. Is this a problem with the application trying to start before the "QueueConnectionFactory"? Is thier a way to define a dependency on my application not to start until the "QueueConnectionFactory" has been started, if so can how would I define this dependency. Please provide and example.
Thanks,
Bill
#1.5 #001CC4695AD8001A000000100000079C00045DB6C93D4DAD#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Connecting Model Repository ...#
#1.5 #001CC4695AD8001A000000110000079C00045DB6C93D4E1D#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Checking source path: halliburton.com/hal~usrgrpap#
#1.5 #001CC4695AD8001A000000120000079C00045DB6C93D4EAC#1228939548538#System.err##System.err#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Error##Plain###[RunTask] The source file/path doesn't exist: halliburton.com/hal~usrgrpap#
#1.5 #001CC4695AD8001A000000130000079C00045DB6C93D4EF5#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Opening connection to MMR ...#
#1.5 #001CC4695AD8001A000000140000079C00045DB6C93D69D0#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Start local transaction ...#
#1.5 #001CC4695AD8001A000000150000079C00045DB6C93D6B5A#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Commit ...#
#1.5 #001CC4695AD8001A000000160000079C00045DB6C93D6C8B#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Running task 'com.sap.ip.mmr.db.tasks.TaskUndeployFromDB' ...#
#1.5 #001CC4695AD8001A000000170000079C00045DB6C93D8E6C#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Close connection to Model Repository ...#
#1.5 #001CC4695AD8001A000000180000079C00045DB6C93D8EE5#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###done.#
#1.5 #001CC4695AD80018000000000000171400045DBBE9BCCED0#1228961568691#com.sap.engine.services.connector##com.sap.engine.services.connector######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error##Plain###ResourceObjectFactory.getObjectInstance(), Error: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
#1.5 #001CC4695AD80018000000010000171400045DBBE9BCE3CD#1228961568691#com.sap.engine.services.jndi##com.sap.engine.services.jndi######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Warning#1#/System/Audit#Java###Exception #1#com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                ... 24 more
#1.5 #001CC4695AD80018000000030000171400045DBBE9BDBF4A#1228961568753#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Java#deploy_5029##Exception in operation startApp with application halliburton.com/halusrgrpap.#2#startApp#halliburton.com/halusrgrpap#
#1.5 #001CC4695AD80018000000040000171400045DBBE9BDC46C#1228961568753#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception in operation startApp with application halliburton.com/hal~usrgrpap.
                at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:394)
                at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:367)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.
                at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1013)
                at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                ... 12 more
Caused by: com.sap.engine.services.ejb.ContainerInitializationException: Cannot initialize message system bridge com.sap.engine.services.ejb.message.JMSBridgeFP.
                at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:451)
                at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                ... 16 more
Caused by: com.sap.engine.services.ejb.message.JMSBridgeException: Destination name PortalUserGroupProcessingQueue not found in the naming.
                at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:129)
                at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                ... 19 more
Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                ... 20 more
Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                ... 24 more
#1.5 #001CC4695AD80018000000060000171400045DBBE9BE0AF5#1228961568769#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Plain###
Operation startApp over application halliburton.com/hal~usrgrpap finished with errors on server 105677750. For more detailed information see traces of Deploy Service.#
#1.5 #001CC4695AD80018000000080000171400045DBBE9BE27D1#1228961568769#com.sap.engine.services.ejb##com.sap.engine.services.ejb######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Java#ejb_2119##Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.#1#com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP#
#1.5 #001CC4695AD80018000000090000171400045DBBE9BE2842#1228961568769#com.sap.engine.services.ejb##com.sap.engine.services.ejb######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.
                at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1013)
                at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.engine.services.ejb.ContainerInitializationException: Cannot initialize message system bridge com.sap.engine.services.ejb.message.JMSBridgeFP.
                at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:451)
                at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                ... 16 more
Caused by: com.sap.engine.services.ejb.message.JMSBridgeException: Destination name PortalUserGroupProcessingQueue not found in the naming.
                at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:129)
                at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                ... 19 more
Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                ... 20 more
Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                ... 24 more
#1.5 #001CC4695AD80019000000000000171400045DBBEB38B908#1228961593581#com.sap.jpe.engine.impl.common.AnalyzerModel#sap.com/com.sapportals.supportplatform#com.sap.jpe.engine.impl.common.AnalyzerModel#Administrator#67####43c8e9d0c72911ddcedd001cc4695ad8#SAPEngine_Application_Thread[impl:3]_38##0#0#Error##Plain###Exception while loading class: com.sapportals.supportplatform.plugins.portal.connectors.ConnectorGatewayServiceCheck
java.lang.NoClassDefFoundError: com/sapportals/portal/prt/resource/ResourceException
                at java.lang.Class.getDeclaredConstructors0(Native Method)
                at java.lang.Class.privateGetDeclaredConstructors(Class.java:1618)
                at java.lang.Class.getConstructor0(Class.java:1930)
                at java.lang.Class.newInstance0(Class.java:278)
                at java.lang.Class.newInstance(Class.java:261)
                at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadClass(PluginCollector.java:881)
                at com.sap.jpe.engine.impl.pluginloading.PluginCollector.getPluginDescFromXMLFile(PluginCollector.java:387)
                at com.sap.jpe.engine.impl.pluginloading.PluginCollector.getPluginDescFromXMLFile(PluginCollector.java:274)
                at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadPluginsFromJarFile(PluginCollector.java:169)
                at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadFromExtDirectory(PluginCollector.java:121)
                at com.sap.jpe.engine.impl.common.AnalyzerModel.loadPlugins(AnalyzerModel.java:411)
                at com.sap.jpe.engine.impl.common.AnalyzerModel.loadPlugins(AnalyzerModel.java:399)
                at com.sapportals.supportplatform.SupportPlatform.init(SupportPlatform.java:81)
                at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:59)
                at java.security.AccessController.doPrivileged(Native Method)
                at javax.security.auth.Subject.doAs(Subject.java:379)
                at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:141)
                at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:386)
                at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)
                at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                at java.security.AccessController.doPrivileged(Native Method)
                at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
                at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

I though the same thing, but XE LISTENER is running on localhost and port 1522. On the other hand XE have local_listener explicitly set to the very same connection descriptor. Even XE installation was second on this server.
I've could change that yes, but the startup script doesn't seemed to have this mind.
Regards,
Sve

Executing a java application during startup

Similar Messages

Maybe you are looking for