Regarding ZDATA Path on App' Server
hi ,
i try with ans' posted for this topic but it is not useful..cause.
i will tell my scenario clearly...
i have selection-sceen..in that s.s 1 radio button called display delta file..ok
select this radio button and after press execute button our control directly go to the our zdata path ...not simply go to the AL11 t.code..
in that t.code after 5 screens our control should stop....(zdata->c.code>xyz->intfid->ext part--->....(like this)..
i think now it is clearly que'...
Please help me..
Think you missed out this bit.
'i will tell my scenario clearly'.
Similar Messages
-
Naming Convention for path in Application Server
Hello Guru's,
I asked my basis team to create flat file source system. he asked me " what path to follow, any sub directories"?.
they are asking me naming convention for a path in App server to create i think ? usually what will be the naming convention for path.
please help me
Thanks,
PrashanthHi,
Create flatfile source system is no need path and sub directory on app server. You can create yourself go TCODE RSA1>Source system>file-->create.
path and sub directory only need if you want to load data from flatfile which is stored in application server. This will be determined in extraction tab of your datasource and infopackage.
Hope this helps.
BR
TRUC -
Virtual Directory / path mapping in Sun ONE App Server 7
Hi,
I am trying to migrate my application from WebLogic 7
to Sun ONE App Server 7.0
In WebLogic, we used the following mapping in weblogic.xml:
<virtual-directory-mapping>
<local-path>f:/ekm</local-path>
<url-pattern>/data/*</url-pattern>
</virtual-directory-mapping>
What would be the equivalent in sun-web.xml in Sun ONE?
Thanks
AmritThis is not deployment instructions.
Its deployment descriptor like web.xml
You can find more info here:
http://docs-pdf.sun.com/816-7150-10/816-7150-10.pdf
on page 91 -
Office web apps server 2013 - launching search on loading page
Hello!
I use Office Web Apps Server 2013 for viewing documents on internal portal (it is not SharePoint, and documents is read only) with automatic generating links. Links are generated according instruction
on http://<OWA host>/op/generate.aspx (for example, http://<OWA host>/op/view.aspx?src=<path to file>).
I have some questions:
1) In some cases, when a document is openedI want
immediately start the search with some terms.
Can I give terms
to search in url params in generated url? For example, http://<OWA host>/op/view.aspx?src=<path to file>#search=<terms>?
Is there any other
way to run a search on page load?
2) I want to use multi-term search (when my search query is 'tame tamed taming', and
all individual words ('tame', 'tamed', 'taming')
are highlighted in document).
Is there a way to do it?
3)I want to use whole-word search (when my search query is'act', and words 'practice' or 'action' are not
highlighted in document).
Is there a way to do it?Hi Jazzy.em
Thanks for posting in MSDN forum.
This forum is for developers discussing developing issues about
apps for Office. Since the issue is more about Office web app, I suggest that you get more effective response from
Office 365 forum.
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us.
Thanks for your understanding.
Regards & Fei
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey. -
Download PDF file from APP server!
Hi!
Has anyone tried uplaoding and downloding a PDF table from app server as I tried from a normal method by Open dataset, Transfer but it wont work.
Please provide any inputs.
Thanks.Hi park,
1. Using open data set, transfer , close etc,
also it will work.
( it will download / upload any kind of file from app server)
2. Just make sure the
FULL PATHNAME and the FILENAME
are mentioned in EXACT CASE
(small/CAPITAL).
3. U can check thru transaction AL11, to see the file and path.
regards,
amit m. -
Can i use office web app server without adding to a domain ?
spserver.local is my domain controller webapp.spsserver.local is my office web app server(OWA)(IP:79.123.161.xxx )
I manage to use office web app with sharepoint 2013 my OWA is in a domain (spserver.local) and it's address is http://webapp.spserver.local/hosting/discovery There
is no problem. But I want to seperate OWA with Sharepoint and its domain I want to remove the domain.Is it possible?
For example my OWA's ip is 79.123.161.xxx
I want to work like this: http://79.123.161.xxx/hosting/discovery
When I enter the path http://79.123.161.xxx/hosting/discovery there
is an iis message "File or directory not found."Are you asking if you can have your OWA in different domain compared to SharePoint server domain or are you asking that your OWA does not belong to any domain and you still want to use it with SharePoint?
If your question is regarding using OWA in different domain then I think (someone can correct me if I am wrong) OWA can run into different domain. You just need to add your SharePoint Server host domain to the Allow List for an Office Web Apps Server farm.
http://technet.microsoft.com/en-us/library/jj219459.aspx
If your question is related to OWA not belonging to any domain then I do not think that will work and its not supported scenario. If you read the following article it states
"All servers in the Office Web Apps Server farm must be part of a domain. They can be in the same domain (recommended) or in domains that are in the same forest. However, Office Web Apps Server won’t work if you try to install it on a domain controller."
http://technet.microsoft.com/en-us/library/jj219435.aspx
Amit -
JDK1.5.0_12 crash when I try to startup a tomcat app server with it.
Hi,
I am support a Blackboard application running on a PrimePower box.
Recently I installed JDK1.5.0_12 on the box. When I re-configured Blackboard to use the new JDK and tried to restart the server, the tomcat portion will keep getting the JVM Hotspot crash error as illustrated below.
The startup is invoked from a shell script that starts the web server as well as the tomcat (app) server. As long as the root partition has enough diskspace, the script will try to "start" the tomcat server.
The JVM will keep throwing core dumps and issuing messages like the following, with each core dump taking about 100 to 150MB in space from the root partition.
Only when there isn't enough space in the root partition for another core dump, did I notice that it stopped.
My sys admin has since cleaned up the dump files and I have reverted back to the earlier minor release of JDK1.5.0.
I have used ldd -r libjvm.so and the command could return me the list of libraries that the libjvm.so depends on (not a problem with the loading of the dynamic libraries and such).
I have submitted the JVM crash report. But no one has gotten back to me.
Has anyone encountered the same problems / have any suggestions on what could be cause and how to resolved this?
Thanks.
Regards,
Hon Peng.
=============================
# An unexpected error has been detected by HotSpot Virtual Machine:
# SIGSEGV (0xb) at pc=0xfea84b00, pid=13715, tid=1
# Java VM: Java HotSpot(TM) Server VM (1.5.0_12-b04 mixed mode)
# Problematic frame:
# V [libjvm.so+0x284b00]
--------------- T H R E A D ---------------
Current thread (0x00036e20): JavaThread "main" [_thread_in_vm, id=1]
siginfo:si_signo=11, si_errno=0, si_code=1, si_addr=0x57726974
Registers:
O0=0x00000000 O1=0x00000000 O2=0x0000015c O3=0x00000000
O4=0x0000015c O5=0x0000015c O6=0xffbfe6f8 O7=0x0000015c
G1=0x00000000 G2=0x0000015c G3=0x0000015c G4=0x00000000
G5=0x00000000 G6=0x00000000 G7=0xff350000 Y=0x00000000
PC=0xfea84b00 nPC=0xfea84b04
Top of Stack: (sp=0xffbfe6f8)
0xffbfe6f8: 000373fc 57726974 000adfb0 ff028d48
0xffbfe708: 00032778 fefdc000 001b3990 b4805210
0xffbfe718: ffbfe84c 00000000 00000000 ff010c40
0xffbfe728: 00009c00 80000000 ffbfe7e8 fea84674
0xffbfe738: 00000000 e3908660 ffbfe7c0 f900587c
0xffbfe748: b4a64018 007f9a80 ffbfe7b4 b4a5e2c5
0xffbfe758: ffbfe7b8 ffbfe8e0 f9015b04 00000000
0xffbfe768: 00000000 f900576c b4a64018 007f9a80
Instructions: (pc=0xfea84b00)
0xfea84af0: 80 a5 a0 00 04 40 00 15 b4 10 20 00 e2 04 a0 08
0xfea84b00: d4 04 60 00 d2 04 60 04 8b 2a b0 20 88 12 40 05
Stack: [0xffb80000,0xffc00000), sp=0xffbfe6f8, free space=505k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V [libjvm.so+0x284b00]
V [libjvm.so+0x28467c]
j java.lang.Object.notify()V+0
j blackboard.util.Queue.put(Ljava/lang/Object;)V+19
j blackboard.platform.log.impl.QueuedLogger.doLogMessage(Ljava/lang/String;)V+77
j blackboard.platform.log.impl.BaseLogger.log(Ljava/lang/String;Lblackboard/platform/log/LogService$Verbosity;)V+10
j blackboard.platform.log.impl.BaseLogger.logInfo(Ljava/lang/String;)V+5
j blackboard.platform.log.impl.BbLogServiceImpl.logInfo(Ljava/lang/String;)V+5
j blackboard.platform.BbServiceManager.init(Ljava/io/File;Ljava/util/Properties;Z)V+249
j blackboard.platform.BbServiceManager.init(Ljava/lang/String;Ljava/util/Properties;Z)V+44
j blackboard.platform.ApplicationLauncher.main([Ljava/lang/String;)V+479
v ~StubRoutines::call_stub
V [libjvm.so+0x19b4dc]
V [libjvm.so+0x2dd2cc]
C [java+0x222c] main+0x1164
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j java.lang.Object.notify()V+0
j blackboard.util.Queue.put(Ljava/lang/Object;)V+19
j blackboard.platform.log.impl.QueuedLogger.doLogMessage(Ljava/lang/String;)V+77
j blackboard.platform.log.impl.BaseLogger.log(Ljava/lang/String;Lblackboard/platform/log/LogService$Verbosity;)V+10
j blackboard.platform.log.impl.BaseLogger.logInfo(Ljava/lang/String;)V+5
j blackboard.platform.log.impl.BbLogServiceImpl.logInfo(Ljava/lang/String;)V+5
j blackboard.platform.BbServiceManager.init(Ljava/io/File;Ljava/util/Properties;Z)V+249
j blackboard.platform.BbServiceManager.init(Ljava/lang/String;Ljava/util/Properties;Z)V+44
j blackboard.platform.ApplicationLauncher.main([Ljava/lang/String;)V+479
v ~StubRoutines::call_stub
--------------- P R O C E S S ---------------
Java Threads: ( => current thread )
0x0037fbe8 JavaThread "FileLogSinkImpl Daemon" [_thread_blocked, id=15]
0x0015ddc0 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=13]
0x0015c4e8 JavaThread "CompilerThread1" daemon [_thread_blocked, id=12]
0x0015b670 JavaThread "CompilerThread0" daemon [_thread_blocked, id=11]
0x0015a7f8 JavaThread "AdapterThread" daemon [_thread_blocked, id=10]
0x001599e8 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=9]
0x0014d768 JavaThread "Finalizer" daemon [_thread_blocked, id=8]
0x0014d228 JavaThread "Reference Handler" daemon [_thread_blocked, id=7]
=>0x00036e20 JavaThread "main" [_thread_in_vm, id=1]
Other Threads:
0x0014ab40 VMThread [id=6]
0x000aff90 WatcherThread [id=14]
VM state:not at safepoint (normal execution)
VM Mutex/Monitor currently owned by a thread: ([mutex/lock_event])
[0x00032778/0x00035dd0] SignatureHandlerLibrary_lock - owner thread: 0x00036e20
Heap
PSYoungGen total 39424K, used 5458K [0xe3400000, 0xe6000000, 0xf8c00000)
eden space 33792K, 16% used [0xe3400000,0xe3954b40,0xe5500000)
from space 5632K, 0% used [0xe5a80000,0xe5a80000,0xe6000000)
to space 5632K, 0% used [0xe5500000,0xe5500000,0xe5a80000)
PSOldGen total 90112K, used 0K [0xb8800000, 0xbe000000, 0xe3400000)
object space 90112K, 0% used [0xb8800000,0xb8800000,0xbe000000)
PSPermGen total 16384K, used 4896K [0xb4800000, 0xb5800000, 0xb8800000)
object space 16384K, 29% used [0xb4800000,0xb4cc83e8,0xb5800000)
Dynamic libraries:
0x00010000 /usr/local/jdk1.5.0_12/bin/java
0xff370000 /usr/lib/libthread.so.1
0xff3fa000 /usr/lib/libdl.so.1
0xff280000 /usr/lib/libc.so.1
0xff3a0000 /usr/platform/FJSV,GPUS/lib/libc_psr.so.1
0xfe800000 /usr/local/jdk1.5.0_12/jre/lib/sparc/server/libjvm.so
0xff240000 /usr/lib/libsocket.so.1
0xff220000 /usr/lib/libsched.so.1
0xff1f0000 /usr/lib/libCrun.so.1
0xff1a0000 /usr/lib/libm.so.1
0xff080000 /usr/lib/libnsl.so.1
0xff170000 /usr/lib/libmp.so.2
0xfe7e0000 /usr/local/jdk1.5.0_12/jre/lib/sparc/native_threads/libhpi.so
0xfe7b0000 /usr/local/jdk1.5.0_12/jre/lib/sparc/libverify.so
0xfe770000 /usr/local/jdk1.5.0_12/jre/lib/sparc/libjava.so
0xfe740000 /usr/local/jdk1.5.0_12/jre/lib/sparc/libzip.so
0xf8cd0000 /usr/local/jdk1.5.0_12/jre/lib/sparc/libj2pkcs11.so
0xb3580000 /usr/lib/libpkcs11.so
0xf8c50000 /usr/lib/libasn1.so
0xb3400000 /usr/lib/libcmicmn.so
0xb47a0000 /opt/FJSVsmee/lib/libinfoca.so
0xf8f90000 /opt/FJSVsmee/lib/libinfocacom.so
0xf8c30000 /opt/FJSVsmee/lib/libsctl15d.so
VM Arguments:
java_command: blackboard.platform.ApplicationLauncher -S ../config/update-tool-vm/install-tool-vm-servicedef.properties -A blackboard.apis.updatetools.CommandLineToolInvokerApp blackboard.apis.updatetools.tooldefs.install.ServiceControllerTool services.stop
Launcher Type: SUN_STANDARD
Environment Variables:
JAVA_HOME=/usr/local/jdk1.5.0_12
CLASSPATH=
PATH=/usr/local/blackboard/apps/openssl/bin:/usr/local/blackboard/apps/bbcms/bin:/usr/local/jdk1.5.0_12/bin:/usr/bin:/usr/ucb:/etc:/usr/local/bin:.
LD_LIBRARY_PATH=/usr/local/jdk1.5.0_12/jre/lib/sparc/server:/usr/local/jdk1.5.0_12/jre/lib/sparc:/usr/local/jdk1.5.0_12/jre/../lib/sparc
SHELL=/bin/ksh
HOSTTYPE=sparc
OSTYPE=solaris2.9
MACHTYPE=sparc-sun-solaris2.9
Signal Handlers:
SIGSEGV: [libjvm.so+0x70cb50], sa_mask[0]=0x7fbffeff, sa_flags=0x00000004
SIGBUS: [libjvm.so+0x70cb50], sa_mask[0]=0x7fbffeff, sa_flags=0x00000004
SIGFPE: [libjvm.so+0x2743ac], sa_mask[0]=0x7fbffeff, sa_flags=0x0000000c
SIGPIPE: [libjvm.so+0x2743ac], sa_mask[0]=0x7fbffeff, sa_flags=0x0000000c
SIGILL: [libjvm.so+0x2743ac], sa_mask[0]=0x7fbffeff, sa_flags=0x0000000c
SIGUSR1: [libjvm.so+0x67f5f0], sa_mask[0]=0x00000000, sa_flags=0x00000008
SIGUSR2: [libjvm.so+0x2743ac], sa_mask[0]=0x7fbffeff, sa_flags=0x0000000c
SIGHUP: [libjvm.so+0x67e22c], sa_mask[0]=0x7fbffeff, sa_flags=0x00000004
SIGINT: [libjvm.so+0x67e22c], sa_mask[0]=0x7fbffeff, sa_flags=0x00000004
SIGQUIT: [libjvm.so+0x67e22c], sa_mask[0]=0x7fbffeff, sa_flags=0x00000004
SIGTERM: [libjvm.so+0x67e22c], sa_mask[0]=0x7fbffeff, sa_flags=0x00000004
--------------- S Y S T E M ---------------
OS: Solaris 9 4/04 s9s_u6wos_08a SPARC
Copyright 2004 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 22 March 2004
uname:SunOS 5.9 Generic_118558-33 sun4us (T2 libthread)
rlimit: STACK 8192k, CORE infinity, NOFILE 5120, AS infinity
load average:0.05 0.12 0.16
CPU:total 4 has_v8, has_v9, has_vis1, has_vis2, is_ultra3
Memory: 8k page, physical 8388608k(6679936k free)
vm_info: Java HotSpot(TM) Server VM (1.5.0_12-b04) for solaris-sparc, built on May 2 2007 02:33:21 by unknown with unknown Workshop:0x550Hi,
Thanks for the reply. I have tried this on another machine running the same version of Blackboard. It works fine.
Only difference is that the machine that has the JVM crash is running on Fujitsu PrimePower and the OS is Solaris 9 (but twigged for PrimePower).
The one where it runs and starts up successfully is running on SunFire (OS is Solaris 10).
I am wondering if there is a problem with the JVM loading required libraries because of the OS being different versions.
Any leads on this is welcomed. Thank you.
Regards,
Hon Peng
===================
On Fujitsu Primepower
SunOS 5.9 Generic_118558-33 sun4us sparc FJSV,GPUS
the Dependencies for libjvm.so are as follows:
===================
bash-2.05$ ldd -r libjvm.so
libsocket.so.1 => /usr/lib/libsocket.so.1
libsched.so.1 => /usr/lib/libsched.so.1
libdl.so.1 => /usr/lib/libdl.so.1
libCrun.so.1 => /usr/lib/libCrun.so.1
libm.so.1 => /usr/lib/libm.so.1
libthread.so.1 => /usr/lib/libthread.so.1
libc.so.1 => /usr/lib/libc.so.1
libnsl.so.1 => /usr/lib/libnsl.so.1
libmp.so.2 => /usr/lib/libmp.so.2
/usr/platform/FJSV,GPUS/lib/libc_psr.so.1
=====================================
On SunFire, Sun machine
SunOS 5.10 Generic_118833-36 sun4u sparc SUNW,Sun-Fire-280R
the dependencies are different for the libjvm.so:
=====================================
bash-2.05$ ldd -r libjvm.so
libsocket.so.1 => /lib/libsocket.so.1
libsched.so.1 => /usr/lib/libsched.so.1
libdl.so.1 => /lib/libdl.so.1
libCrun.so.1 => /usr/lib/libCrun.so.1
libm.so.1 => /lib/libm.so.1
libthread.so.1 => /lib/libthread.so.1
libc.so.1 => /lib/libc.so.1
libnsl.so.1 => /lib/libnsl.so.1
libmp.so.2 => /lib/libmp.so.2
libmd5.so.1 => /lib/libmd5.so.1
libscf.so.1 => /lib/libscf.so.1
libdoor.so.1 => /lib/libdoor.so.1
libuutil.so.1 => /lib/libuutil.so.1
/platform/SUNW,Sun-Fire-280R/lib/libc_psr.so.1
libm.so.2 => /lib/libm.so.2
/platform/SUNW,Sun-Fire-280R/lib/libmd5_psr.so.1 -
How to access JDBC Resource registered in Sun Java System App Server ?
I want to create a stand-alone JDBC application with Java SE using Swing technologies and JNDI technology. The purpose of using JNDI technology is to avoid change of Java Source Code every time I move the database to different location. This Java application will be used in a standalone PC installed with Windows XP Professional with no LAN / WAN connection. Of course, Internet connection is available with the PC.
I use JavaDB to store the data tables and the location of the database is D:\E-DRIVE\SAPDEV. Tomorrow, if I move this database to C:\SAPDEV or any network drive, I do not want to change the Java Source code. I want to use JNDI which, if I am not wrong, helps developers to avoid manual change of Java source code whenever the database location is changed. Changes have to be made only in the JNDI Name which contains all relevant information about the database in order to get connection no matter where the database SAPDEV is stored; it can be placed under D:\E-DRIVE directory or C:\ directory of the hard disk. To implement my intention, I started developing Java application as per the steps mentioned below:
Step 1:
To proceed, first, I sought the help of Sun Java System Application Server Admin Console. I created JNDI object for Connection Pool using the menu path Common Tasks->Resources->JDBC->Connection Pools.
JNDI Name : ABAPRPY
Resource Type : javax.sql.DataSource
Datasource class : org.apache.derby.jdbc.ClientDataSource
Description : ABAP Program Repository
The Connection Pool creation has options for General, Advanced and Additional Settings tabs and I made all the settings relevant to the database I created in D:\E-DRIVE\SAPDEV.
To confirm whether the above settings are correct, I pressed the Ping push button which is available in the General tab of the connection pool creation screen. The system responded with the message Ping Succeeded.
Step 2:
I created a JDBC Resource using the menu path Common Tasks->Resources->JDBC->JDBC Resources.
JNDI Name : jdbc/SAPDEV
Pool Name : ABAPRPY
Description : Database Connection for SAPDEV database
Status : Enabled
I can see all the above settings recorded in the domain.xml which is placed in the folder
C:\Sun\AppServer\domains\domain1\config
Step 3:
I have made sure that Sun Java System Application Server is up and running in the background with JavaDB server. I created a Java Program making sure the following JAR files are included in the classpath:
appserv-admin.jar
appserv-ee.jar
appserv-rt.jar
javaee.jar
fscontext.jar
Plus, the lib directory of JDK 1.6 & C:\Sun\AppServer\domains\domain1\config
Source code of the program is as follows: I used NetBeans IDE to create my project file.
import java.util.logging.Level;
import java.util.logging.Logger;
import javax.naming.*;
import javax.activation.DataSource;
public class JNDILookup {
public static void main(String[] args) {
try {
InitialContext initCtx = new InitialContext();
DataSource ds = (DataSource) initCtx.lookup("java:comp/env/jdbc/sapdev>");
} catch (NamingException ex) {
Logger.getLogger(JNDILookup.class.getName()).log(Level.SEVERE, null, ex);
When I attempted to compile the above program in NetBeans IDE ,no compilation error reported. But while executing the program, I got the following run-time error message:
SEVERE: null
javax.naming.NameNotFoundException: No object bound for java:comp/env/jdbc/sapdev> [Root exception is java.lang.NullPointerException]
at com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.java:224)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:396)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at SAPConnect.JNDILookup.main(JNDILookup.java:21)
Caused by: java.lang.NullPointerException
at com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.java:173)
... 3 more
Now, I want to come out of this situation; at the same time, I want to preserve the settings I have made in the Sun Java System Application Server Admin Console. That is, I want to programmatically access the data source using Connection Pool created in Sun Java System Application Server Admin Console.
I request dear forum members to provide me an appropriate solution.
Thanks and regards,
K. Rangarajan.jay44 wrote:
Bare in mind I am attempting the context.lookup() from inside the container (my code is in a session bean). I have accessed the server and have my bean "say hello" first to verify the bean works OK, then I call a method with this rather standard code:
String jndiDataSourceName ="Second_EJB_Module_DataBase";
Logger.getLogger(DynamicPU.class.getName()).log(Level.INFO,"Programatically acquiring JNDI DataDource: "+ jndiDataSourceName);
InitialContext ctx;
try {
ctx = new InitialContext();
ds =(DataSource)ctx.lookup("java:comp/env/jdbc/"+jndiDataSourceName);
} catch (NamingException ex) {
Logger.getLogger(DynamicPU.class.getName()).log(Level.SEVERE, null, ex);
return "Exception generated trying to preform JDBC DataSource lookup. \n"+ex.toString();
But when I run the code the server log shows the initial context is created Ok, but an exception is thrown becasue the resource name is not found:
(and i have tried vriations of ctx.lookup("jdbc/"+jndiDataSourceName) etc etc
You are fine here. It works in container because the InitialContext properties have been supplied already. That was the link I forwarded earlier. The InitialContext you create locally needs to locate the container JNDI. That is what the properties specify.
Where I am confused is where you indicate the stack below is from the server log. So, you initiate a standalone (java main method) application, create an InitialContext, and you see the results in your app server log?
LDR5010: All ejb(s) of [EJB_Module_1] loaded successfully!
Programatically acquiring JNDI DataDource: Second_EJB_Module_DataBase
The log message is null.
javax.naming.NameNotFoundException: Second_EJB_Module_DataBase not found
at com.sun.enterprise.naming.TransientContext.doLookup(TransientContext.java:216)
at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.java:188)
at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.java:192)...
at com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:555)
This is strange since I can see this resource (a JDBC connection named Second_EJB_Module_DataBase) is configured on the server from the server's admin console.
That is why you can obtain a lookup from within the container (app server).
For this lookup to work it may be that one must map the name inside an ejb-jar.xml deployed with the application, but I have also read some resources like jdbc connection should have a default name. Does anyone know if my lookup() should work without using an ejb-jar.xml mfile to explcitly map the reource for my application?
Both EBJ's and data sources can be referenced via JNDI. It's a remote lookup (that is normally optimized if it is running in the same JVM). You should not have any dependencies on a JDBC data source being set-up on ejb-jar.xml. That file can of course impact your EJB's. However, data sources are normally set-up on a container-specific basis (e.g., you probably did it through a console, but there is a spec somewhere about how to set up a data source via a resource the app server looks for; it varies from app server to app server). However, once you have that container-specific data source set-up, JNDI operates vendor-neutral. You should be able to take the code above and move it to JBoss or Weblogic or Tomcat or whatever (this is an ideal, in practice, the vendors sometimes put a data source in a name you would not expect, but again, you can use their JMX console to see what the JNDI name is).
(As I stated above if I have to use a deployment discriptor to get at this JNDI datasource, then solution is not "programmatic" as newly configured datasources could not be accessed without redeploying the entire application).
As JSchell alluded to, you will always have at least something vendor-specific. JNDI itself (the code you wrote) is totally portable. However, you have to set the various JNDI environment properties to a given vendor's spec. Ideally, you should not need a vendor's actual InitialContext application, but it's a possibility. Once you can safely cast to Context, you should be vendor-neutral (if not, demand your money back).
So that is exactly where I am stuck, trying to get the lookup to work and wondering if it should work without and xml file mapping the resource for my app.
What we ended up doing for standalone was to provide our own JNDI. If you look at the open source project JOTM, there are examples on how to use that with XBean (if integrating with Spring, as we did), you can easily set up a data source that runs standalone exactly as you get in the container. Another benefit is you get full JTA/JTS support and the ability to run XA transactions. (This might all be alphabet soup, but the app server gives it to you, and this is the way we ended up doing the same: JNDI + JTA + JTS + XA). It ends up the same application code uses a "vanilla" InitialContext and all we have to do is write one or two xml files (one for our app server, a couple for JOTM), and our actual code works the same.
I still think you have a shot at getting to the container's JNDI, just not using their full-blown app server JAR.
I think there must be a simple way to do this with an ejb-jar.xml, I am no expert in JNDI, I could be missing something simple, I will keep at it and post an answer here if I come up with it.
Thanks, jayIt is simple to code. Getting it to integrate with your app server, yes, that can be challenging. But it has nothing to do with EJB's. Write a simple test. Using nothing but DataSource and InitialContext. Let us know where you get stuck.
- Saish -
Error installing the App Server 10.1.2.0.3 Metadata Repo Creation Asst
Hi,
I have upgraded the Database from 10.2.0.1 to 10.2.0.4,
ORACLE_HOME=D:\oracle\product\10.2.0\db_1
but while installing the App Server 10.1.2.0.3 Metadata Repo Creation Asst, im encountered with (in the OUI 'Destination' is Name:OracleAS1, Path:C:\OraHome_1)
"There was error while loading the libaray:rgsQueries
1. Stop Installation of all products
2. Stop installation of this component only.
Any help would be great.
Regards,
- SriAnybody there to help me on this....
Regards,
- Sri -
Problems while deploying a JSF/ ADF Faces App to Apps Server 10.1.3.0.1
Dear All,
I built a JSF based application (Using ADF Faces Components) developed in JDeveloper 10.1.3.1.0 (Application Configuration: [JSF, ADF BC]. The application is running fine with the embedded OC4J intance (automatically aunch by JDeveloper).
I am now trying to deploy it on the installed Oracle Application Server (running on the same local machine). The details of the versioning for different components in this App server are as follows:
1. OracleAS J2EE 10.1.3.0.0
2. Oracle ADF 10.1.3.1.0
The deployment steps I followed (as given in Chapter 34 of 'Oracle ADF - Developer's Guide for Forms/4GL Developers') seems to be running smoothly. This is because the deploy process ends up showing no erros in the message window.
However when I tried to test the application with a browser using the Apps Server URL (HTTP://localhost:8888/<my-app>/<firstfile.jspx>), I am finding 'Page not found error'.
I also tried a manual deployment (using deploy to a WAR file then copy the resulting war & ear files and the xml descriptor file to the Apps server's http root) and gives the war file URL in the browser.
In this case now I am getting the following error page:
=====================================================
The XML page cannot be displayed
Cannot view XML input using style sheet. Please correct the error and then click the Refresh button, or try again later.
An invalid character was found in text content. Error processing resource
'http://localhost:8888/HousingWithADF.war'.
=====================================================
Any idea?
Regards,
Irfan Ilyas
PS: I am doubtful about creation of Deployment Descriptors step as the documentation is not very clear about exactly which descriptors we need to create. Using my own idea, I tried to create J2EE descriptor, and one tld (taglibrary) file. However, the manual war deployment generates only the tld file in the deploy folder.Thanks for the hint.
OBSERVATION #1:
After looking through the administration console for OC4J instance, I found my application name with UP status. When drill-down further, the console gives me the URL which can be used to test the application.
While using the URL, a different error message was found:
URL: http://localhost:8888/KFUPMHousing/
Error:
====================
HTTP 403:(Forbidden)
================
You are not authorized to view this page
You might not have permission to view this directory or page using the credentials you supplied.
From my experience of Microsoft IIS, I know here I may need to configure the folder permissions for a web-user. But exactly which user and where it is defined (at OS Level or in AS), I am not much sure.
Can you elaborate?
OBSERVATION #2:
The log text for my application shows the following error (for the attempt I did with the URL shown above)
Log Text
07/01/05 22:43:38.62 HousingWithADF: JspServlet: unable to dispatch to requested page: Exception:java.io.FileNotFoundException: C
:\product\10.1.3.1\OracleAS_1\j2ee\home\applications\HousingWithADF\HousingWithADF\HosReqInfo.jspx (The system cannot find the file specified)
However, I can browse the file on my local disk in the path specified with a little change in the path. The file is found in 'pages' folder within the last folder,named HousingWIthADF. I tried to move the file in the exact path specified in the log and now finding the 'Page not found' error.
Any idea?
Irfan Ilyas -
Can't execute web app from NetBeans 3.6 with Sun Java App Server 8
Hi there,
I'm tyring to execute a java web application called myfirstjsp.
In directory ...\myfirstsjp I've got:
- index.jsp
- WEB-INF dir
- META-INF dir.
I can run myfirstjsp from NetBeans if I choose the Netbeans default server, Tomcat 5.0.19 (this web server is configured to port 8084).
However, when I try to execute myfirstjsp from NetBeans with Sun Java System Application Server 8(configured to port 8080), it gives me an annoying message:
The Sun Java System Application Server 8 could not start.
More information about the cause is in the Server log file.
Possible reasons include:
- Port conflicts. (use netstat -a to detect possible port numbers already used by the operating system.)
- Incorrect server configuration (domain.xml to be corrected manually)
- Corrupted Deployed Applications preventing the server to start.(This can be seen in the server.log file. In this case, domain.xml needs to be modified).
I checked port conflicts but none found.
The other two options don't give me a place to start (I don't know what to do with domain.xml)
I'm working with:
- Windows XP Pro
- J2SE 1.4.2_04 (installed in C:\Program Files\j2sdk1.4.2_04)
- Sun Java Application Server 8 (installed in C:\Program Files\Sun\AppServer)
- Netbeans 3.6 + Sun Java System Application Server Plugin (installed in C:\Program Files\NetBeans3.6).
My PC has the following environment variables:
PATH(in user MGoncalv)=C:\Program Files\Sun\AppServer\bin;,?ut
PATH(system variable)=C:\Program Files\j2sdk1.4.2_04\bin;D:\ProgramFiles\OraReportNT\bin;C:\OraHome92\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Program Files\Personal Communications\;C:\Program Files\IBM\Trace Facility\;%SystemRoot%\system32\nls;%SystemRoot%\system32\nls\ENGLISH
CLASSPATH(system variable)=.;C:\OraHome92\jdbc\lib\ojdbc14.jar
By looking at the Sun App Server log file, I discovered that the log outputs of
- Start Default Server (a link in the folder created by the installation of Sun App Server)
- and trying to execute myfirstjsp from NetBeans through Sun App Server
are very similar.
Below is a piece of server.log when I tried to execute myfirstjsp from NetBeans through Sun App Server. Please, pay attention to the EJBC error:
Starting Sun Java System Application Server Platform Edition 8.0 (build b57-fcs) ...
[#|2004-05-19T17:20:05.198+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_04] from [Sun Microsystems Inc.]|#]
[#|2004-05-19T17:20:08.713+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-05-19T17:20:09.384+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-05-19T17:20:14.752+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-05-19T17:20:14.772+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-05-19T17:20:14.792+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-05-19T17:20:20.200+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-05-19T17:20:23.645+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-05-19T17:20:24.336+0100|INFO|sun-appserver-pe8.0|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-05-19T17:20:26.098+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-05-19T17:20:27.811+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-05-19T17:20:27.921+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|Selecting file [C:\Program Files\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear] for autodeployment|#]
[#|2004-05-19T17:20:27.931+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ C:\Program Files\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear ] for autodeployment.|#]
[#|2004-05-19T17:20:30.004+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [__ejb_container_timer_app]|#]
[#|2004-05-19T17:20:33.459+0100|WARNING|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|Compilation failed: Native compiler returned an error: 2
Error messages are: |#]
[#|2004-05-19T17:20:33.479+0100|WARNING|sun-appserver-pe8.0|javax.enterprise.system.stream.err|_ThreadID=10;|Compilation failed: Native compiler returned an error: 2
Error messages are:
at com.sun.ejb.codegen.IASEJBC.compileClasses(IASEJBC.java:301)
at com.sun.ejb.codegen.CmpCompiler.compile(CmpCompiler.java:230)
at com.sun.ejb.codegen.IASEJBC.doCompile(IASEJBC.java:617)
at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:565)
at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBCompiler.java:360)
at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:208)
at com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:292)
at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:173)
at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:105)
at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:124)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:74)
at com.sun.enterprise.deployment.phasing.DeploymentService.executePhases(DeploymentService.java:233)
at com.sun.enterprise.deployment.phasing.DeploymentService.deploy(DeploymentService.java:150)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:275)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:287)
at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:280)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:221)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:228)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:823)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
at $Proxy1.invoke(Unknown Source)
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:471)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:367)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:346)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:167)
at com.sun.enterprise.server.SystemAppLifecycle.deployToTarget(SystemAppLifecycle.java:180)
at com.sun.enterprise.server.SystemAppLifecycle.deploySystemApps(SystemAppLifecycle.java:155)
at com.sun.enterprise.server.SystemAppLifecycle.onStartup(SystemAppLifecycle.java:77)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:295)
at com.sun.enterprise.server.PEMain.run(PEMain.java:220)
at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: com.sun.ejb.codegen.JavaCompilerException: Native compiler returned an error: 2
Error messages are:
at com.sun.ejb.codegen.JavaCompiler.javacCompile(JavaCompiler.java:139)
at com.sun.ejb.codegen.JavaCompiler.internal_compile(JavaCompiler.java:60)
at com.sun.ejb.codegen.Compiler.compile(Compiler.java:57)
at com.sun.ejb.codegen.IASEJBC.compileClasses(IASEJBC.java:293)
... 45 more
|#]
[#|2004-05-19T17:20:33.739+0100|WARNING|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|Deployment Error
com.sun.enterprise.deployment.backend.IASDeploymentException: Fatal Error from EJB Compiler -- Compilation failed: Native compiler returned an error: 2
Error messages are:
at com.sun.ejb.codegen.IASEJBC.compileClasses(IASEJBC.java:301)
at com.sun.ejb.codegen.CmpCompiler.compile(CmpCompiler.java:230)
at com.sun.ejb.codegen.IASEJBC.doCompile(IASEJBC.java:617)
at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:565)
at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBCompiler.java:360)
at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:208)
at com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:292)
at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:173)
at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:105)
at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:124)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:74)
at com.sun.enterprise.deployment.phasing.DeploymentService.executePhases(DeploymentService.java:233)
at com.sun.enterprise.deployment.phasing.DeploymentService.deploy(DeploymentService.java:150)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:275)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:287)
at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:280)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:221)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:228)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:823)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
at $Proxy1.invoke(Unknown Source)
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:471)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:367)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:346)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:167)
at com.sun.enterprise.server.SystemAppLifecycle.deployToTarget(SystemAppLifecycle.java:180)
at com.sun.enterprise.server.SystemAppLifecycle.deploySystemApps(SystemAppLifecycle.java:155)
at com.sun.enterprise.server.SystemAppLifecycle.onStartup(SystemAppLifecycle.java:77)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:295)
at com.sun.enterprise.server.PEMain.run(PEMain.java:220)
at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
|#]
[#|2004-05-19T17:20:33.739+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 5187 msec, Total EJB Compiler Module Time: 0 msec, Portion spent EJB Compiling: 0%|#]
[#|2004-05-19T17:20:33.759+0100|SEVERE|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|Exception occured in J2EEC Phase
com.sun.enterprise.deployment.backend.IASDeploymentException: Fatal Error from EJB Compiler -- Compilation failed: Native compiler returned an error: 2
Error messages are:
at com.sun.ejb.codegen.IASEJBC.compileClasses(IASEJBC.java:301)
at com.sun.ejb.codegen.CmpCompiler.compile(CmpCompiler.java:230)
at com.sun.ejb.codegen.IASEJBC.doCompile(IASEJBC.java:617)
at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:565)
at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBCompiler.java:360)
at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:208)
at com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:292)
at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:173)
at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:105)
at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:124)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:74)
at com.sun.enterprise.deployment.phasing.DeploymentService.executePhases(DeploymentService.java:233)
at com.sun.enterprise.deployment.phasing.DeploymentService.deploy(DeploymentService.java:150)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:275)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:287)
at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:280)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:221)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:228)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:823)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
at $Proxy1.invoke(Unknown Source)
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:471)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:367)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:346)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:167)
at com.sun.enterprise.server.SystemAppLifecycle.deployToTarget(SystemAppLifecycle.java:180)
at com.sun.enterprise.server.SystemAppLifecycle.deploySystemApps(SystemAppLifecycle.java:155)
at com.sun.enterprise.server.SystemAppLifecycle.onStartup(SystemAppLifecycle.java:77)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:295)
at com.sun.enterprise.server.PEMain.run(PEMain.java:220)
at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
|#]
[#|2004-05-19T17:20:33.789+0100|SEVERE|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|Exception while deploying : Fatal Error from EJB Compiler -- Compilation failed: Native compiler returned an error: 2
Error messages are:
.|#]
[#|2004-05-19T17:20:33.799+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Autodeploy failed : C:\Program Files\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear.|#]
[#|2004-05-19T17:20:33.879+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-05-19T17:20:34.811+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-05-19T17:20:35.111+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-05-19T17:20:35.121+0100|WARNING|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
[#|2004-05-19T17:20:35.161+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2004-05-19T17:20:35.181+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [hello] in virtual server [server] at [hello]|#]
[#|2004-05-19T17:20:35.201+0100|INFO|sun-appserver-pe8.0|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-05-19T17:20:35.201+0100|INFO|sun-appserver-pe8.0|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-05-19T17:20:35.412+0100|INFO|sun-appserver-pe8.0|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server-PE-8.0|#]
[#|2004-05-19T17:20:37.945+0100|INFO|sun-appserver-pe8.0|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-05-19T17:20:38.456+0100|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2004-05-19T17:20:38.556+0100|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2004-05-19T17:20:38.847+0100|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2004-05-19T17:20:38.887+0100|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2004-05-19T17:20:38.987+0100|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-05-19T17:20:39.007+0100|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-05-19T17:20:39.558+0100|INFO|sun-appserver-pe8.0|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [C:\Program Files\Sun\AppServer\imq\bin].|#]
[#|2004-05-19T17:20:39.568+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1084983639568|#]
[#|2004-05-19T17:20:39.568+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2004-05-19T17:20:39.588+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
[#|2004-05-19T17:20:44.475+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1041:Sent the event to instance:[com.sun.enterprise.admin.event.ConfigChangeEvent -- server [1 Change(s), Id:1, ts:1084983644465]]|#]
[#|2004-05-19T17:20:44.545+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1046:A change notification was not handled sucessfully, the server will need a restart for the change to be effective.|#]
Is this EJB compilation error normal ? if not what does it mean ? Sun Java App Server installation isn't OK ?
I tried to look into the Sun App Server Troubleshooting, searched forums... but couldn't squeeze any valuable info from any of them.
If you have any sugestion regarding this problem, or you know some web site that addresses it please tell me !
Many thanks,
MiguelI seem to have the same problem, I cant run sun application server 8.1. The server is in c:\sun\appserver\, I am using netbeans 4.1. I recieve the same comment above:
The Sun Java System Application Server 8 could not start.
More information about the cause is in the Server log file.
Possible reasons include:
- Port conflicts. (use netstat -a to detect possible port numbers already used by the operating system.)
- Incorrect server configuration (domain.xml to be corrected manually)
- Corrupted Deployed Applications preventing the server to start.(This can be seen in the server.log file. In this case, domain.xml needs to be modified).
I cant see any port conflict, the server is set to port 4848. I dont know about any configurations.
This is the Exception:
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=C:/Sun/AppServer/domains/domain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=domain1
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
-Dcom.sun.aas.configRoot=C:/Sun/AppServer/config
-Djava.library.path=C:\Program Files\Java\jdk1.5.0_04\jre\bin\client;C:\Sun\AppServer\lib;C:\Sun\AppServer\lib;C:\Program Files\Java\jdk1.5.0_04\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Rational\ClearQuest;
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
C:/Program Files/Java/jdk1.5.0_04/lib/tools.jar;C:/Sun/AppServer/lib/appserv-rt.jar;C:/Sun/AppServer/lib\admin-cli.jar;C:/Sun/AppServer/lib\appserv-admin.jar;C:/Sun/AppServer/lib\dom.jar;C:/Sun/AppServer/lib\jmxremote.jar;C:/Sun/AppServer/lib\jmxremote_optional.jar;C:/Sun/AppServer/lib\jsf-api.jar;C:/Sun/AppServer/lib\jsf-impl.jar;C:/Sun/AppServer/lib\rmissl.jar;C:/Sun/AppServer/lib\xalan.jar;C:/Sun/AppServer/lib\xercesImpl.jar;C:/Sun/AppServer/lib\appserv-assemblytool_ja.jar;C:/Sun/AppServer/lib\appserv-cmp_ja.jar;C:/Sun/AppServer/lib\appserv-rt_ja.jar;C:/Sun/AppServer/lib\commons-launcher_ja.jar;C:/Sun/AppServer/lib\deployhelp_ja.jar;C:/Sun/AppServer/lib\j2ee_ja.jar;C:/Sun/AppServer/lib\appserv-assemblytool_zh.jar;C:/Sun/AppServer/lib\appserv-assemblytool_zh_CN.jar;C:/Sun/AppServer/lib\appserv-cmp_zh.jar;C:/Sun/AppServer/lib\appserv-cmp_zh_CN.jar;C:/Sun/AppServer/lib\appserv-rt_zh.jar;C:/Sun/AppServer/lib\appserv-rt_zh_CN.jar;C:/Sun/AppServer/lib\commons-launcher_zh.jar;C:/Sun/AppServer/lib\commons-launcher_zh_CN.jar;C:/Sun/AppServer/lib\deployhelp_zh.jar;C:/Sun/AppServer/lib\deployhelp_zh_CN.jar;C:/Sun/AppServer/lib\j2ee_zh.jar;C:/Sun/AppServer/lib\j2ee_zh_CN.jar;C:/Sun/AppServer/lib\appserv-assemblytool_ko.jar;C:/Sun/AppServer/lib\appserv-cmp_ko.jar;C:/Sun/AppServer/lib\appserv-rt_ko.jar;C:/Sun/AppServer/lib\commons-launcher_ko.jar;C:/Sun/AppServer/lib\deployhelp_ko.jar;C:/Sun/AppServer/lib\j2ee_ko.jar;C:/Sun/AppServer/lib\appserv-assemblytool_fr.jar;C:/Sun/AppServer/lib\appserv-cmp_fr.jar;C:/Sun/AppServer/lib\appserv-rt_fr.jar;C:/Sun/AppServer/lib\commons-launcher_fr.jar;C:/Sun/AppServer/lib\deployhelp_fr.jar;C:/Sun/AppServer/lib\j2ee_fr.jar;C:/Sun/AppServer/lib\appserv-assemblytool_es.jar;C:/Sun/AppServer/lib\appserv-cmp_es.jar;C:/Sun/AppServer/lib\appserv-rt_es.jar;C:/Sun/AppServer/lib\commons-launcher_es.jar;C:/Sun/AppServer/lib\deployhelp_es.jar;C:/Sun/AppServer/lib\j2ee_es.jar;C:/Sun/AppServer/lib\appserv-upgrade.jar;C:/Sun/AppServer/lib\appserv-ext.jar;C:/Sun/AppServer/lib\j2ee.jar;C:/Sun/AppServer/lib\activation.jar;C:/Sun/AppServer/lib\appserv-cmp.jar;C:/Sun/AppServer/lib\appserv-jstl.jar;C:/Sun/AppServer/lib\commons-launcher.jar;C:/Sun/AppServer/lib\commons-logging.jar;C:/Sun/AppServer/lib\j2ee-svc.jar;C:/Sun/AppServer/lib\jax-qname.jar;C:/Sun/AppServer/lib\jaxr-api.jar;C:/Sun/AppServer/lib\jaxr-impl.jar;C:/Sun/AppServer/lib\jaxrpc-api.jar;C:/Sun/AppServer/lib\jaxrpc-impl.jar;C:/Sun/AppServer/lib\mail.jar;C:/Sun/AppServer/lib\relaxngDatatype.jar;C:/Sun/AppServer/lib\saaj-api.jar;C:/Sun/AppServer/lib\saaj-impl.jar;C:/Sun/AppServer/lib\xsdlib.jar;C:/Sun/AppServer/lib/install/applications/jmsra/imqjmsra.jar;C:/Sun/AppServer/imq/lib/jaxm-api.jar;C:/Sun/AppServer/imq/lib/fscontext.jar;C:/Sun/AppServer/lib/ant/lib/ant.jar;C:/Sun/AppServer/pointbase/lib/pbclient.jar;C:/Sun/AppServer/pointbase/lib/pbembedded.jar
com.sun.enterprise.server.PEMain
start
display
native|#]
[#|2005-11-02T11:45:43.930+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5034: Could not start the JMS service broker process.|#]
[#|2005-11-02T11:45:43.940+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5036: More details may be available in the log file for the JMS service broker instance imqbroker. Please refer to the JMS provider documentation for the exact location of this log file.|#]
[#|2005-11-02T11:45:43.940+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5024: JMS service startup failed.|#]
[#|2005-11-02T11:45:43.950+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
com.sun.appserv.server.ServerLifecycleException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:289)
at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Caused by: com.sun.appserv.server.ServerLifecycleException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:276)
... 5 more
Caused by: java.io.IOException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at java.lang.ProcessImpl.create(Native Method)
at java.lang.ProcessImpl.<init>(ProcessImpl.java:81)
at java.lang.ProcessImpl.start(ProcessImpl.java:30)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
at java.lang.Runtime.exec(Runtime.java:591)
at java.lang.Runtime.exec(Runtime.java:464)
at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.startProvider(JMSAdminImpl.java:769)
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:269)
... 5 more
|#]
[#|2005-11-02T11:45:43.960+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|Exception while stoppping Lifecycle.
java.lang.NullPointerException
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:389)
at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:67)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
|#]
[#|2005-11-02T11:47:53.507+0300|WARNING|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER005:Spaces in your PATH have been detected. The PATH must be consistently formated (e.g. C:\Program Files\Java\jdk1.5.0\bin; ) or the Appserver may not be able to start and/or stop. Mixed quoted spaces in your PATH can cause problems, so the launcher will remove all double quotes before invoking the process. The most reliable solution would be to remove all spaces from your path before starting the Appservers components. |#]
[#|2005-11-02T11:47:53.517+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|
C:/Program Files/Java/jdk1.5.0_04\bin\java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=C:/Sun/AppServer/domains/domain1/logs/server.log
-Djava.endorsed.dirs=C:/Sun/AppServer/lib/endorsed
-Djava.security.policy=C:/Sun/AppServer/domains/domain1/config/server.policy
-Djava.security.auth.login.config=C:/Sun/AppServer/domains/domain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=C:/Sun/AppServer/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=C:/Sun/AppServer/domains/domain1/config/cacerts.jks
-Djava.ext.dirs=C:/Program Files/Java/jdk1.5.0_04/jre/lib/ext;C:/Sun/AppServer/domains/domain1/lib/ext
-Djdbc.drivers=com.pointbase.jdbc.jdbcUniversalDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
-Dcom.sun.aas.configName=server-config
-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
-Ddomain.name=domain1
-Djmx.invoke.getters=true
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=C:/Sun/AppServer/domains/domain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=domain1
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
-Dcom.sun.aas.configRoot=C:/Sun/AppServer/config
-Djava.library.path=C:\Program Files\Java\jdk1.5.0_04\jre\bin\client;C:\Sun\AppServer\lib;C:\Sun\AppServer\lib;C:\Program Files\Java\jdk1.5.0_04\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Rational\ClearQuest;
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
C:/Program Files/Java/jdk1.5.0_04/lib/tools.jar;C:/Sun/AppServer/lib/appserv-rt.jar;C:/Sun/AppServer/lib\admin-cli.jar;C:/Sun/AppServer/lib\appserv-admin.jar;C:/Sun/AppServer/lib\dom.jar;C:/Sun/AppServer/lib\jmxremote.jar;C:/Sun/AppServer/lib\jmxremote_optional.jar;C:/Sun/AppServer/lib\jsf-api.jar;C:/Sun/AppServer/lib\jsf-impl.jar;C:/Sun/AppServer/lib\rmissl.jar;C:/Sun/AppServer/lib\xalan.jar;C:/Sun/AppServer/lib\xercesImpl.jar;C:/Sun/AppServer/lib\appserv-assemblytool_ja.jar;C:/Sun/AppServer/lib\appserv-cmp_ja.jar;C:/Sun/AppServer/lib\appserv-rt_ja.jar;C:/Sun/AppServer/lib\commons-launcher_ja.jar;C:/Sun/AppServer/lib\deployhelp_ja.jar;C:/Sun/AppServer/lib\j2ee_ja.jar;C:/Sun/AppServer/lib\appserv-assemblytool_zh.jar;C:/Sun/AppServer/lib\appserv-assemblytool_zh_CN.jar;C:/Sun/AppServer/lib\appserv-cmp_zh.jar;C:/Sun/AppServer/lib\appserv-cmp_zh_CN.jar;C:/Sun/AppServer/lib\appserv-rt_zh.jar;C:/Sun/AppServer/lib\appserv-rt_zh_CN.jar;C:/Sun/AppServer/lib\commons-launcher_zh.jar;C:/Sun/AppServer/lib\commons-launcher_zh_CN.jar;C:/Sun/AppServer/lib\deployhelp_zh.jar;C:/Sun/AppServer/lib\deployhelp_zh_CN.jar;C:/Sun/AppServer/lib\j2ee_zh.jar;C:/Sun/AppServer/lib\j2ee_zh_CN.jar;C:/Sun/AppServer/lib\appserv-assemblytool_ko.jar;C:/Sun/AppServer/lib\appserv-cmp_ko.jar;C:/Sun/AppServer/lib\appserv-rt_ko.jar;C:/Sun/AppServer/lib\commons-launcher_ko.jar;C:/Sun/AppServer/lib\deployhelp_ko.jar;C:/Sun/AppServer/lib\j2ee_ko.jar;C:/Sun/AppServer/lib\appserv-assemblytool_fr.jar;C:/Sun/AppServer/lib\appserv-cmp_fr.jar;C:/Sun/AppServer/lib\appserv-rt_fr.jar;C:/Sun/AppServer/lib\commons-launcher_fr.jar;C:/Sun/AppServer/lib\deployhelp_fr.jar;C:/Sun/AppServer/lib\j2ee_fr.jar;C:/Sun/AppServer/lib\appserv-assemblytool_es.jar;C:/Sun/AppServer/lib\appserv-cmp_es.jar;C:/Sun/AppServer/lib\appserv-rt_es.jar;C:/Sun/AppServer/lib\commons-launcher_es.jar;C:/Sun/AppServer/lib\deployhelp_es.jar;C:/Sun/AppServer/lib\j2ee_es.jar;C:/Sun/AppServer/lib\appserv-upgrade.jar;C:/Sun/AppServer/lib\appserv-ext.jar;C:/Sun/AppServer/lib\j2ee.jar;C:/Sun/AppServer/lib\activation.jar;C:/Sun/AppServer/lib\appserv-cmp.jar;C:/Sun/AppServer/lib\appserv-jstl.jar;C:/Sun/AppServer/lib\commons-launcher.jar;C:/Sun/AppServer/lib\commons-logging.jar;C:/Sun/AppServer/lib\j2ee-svc.jar;C:/Sun/AppServer/lib\jax-qname.jar;C:/Sun/AppServer/lib\jaxr-api.jar;C:/Sun/AppServer/lib\jaxr-impl.jar;C:/Sun/AppServer/lib\jaxrpc-api.jar;C:/Sun/AppServer/lib\jaxrpc-impl.jar;C:/Sun/AppServer/lib\mail.jar;C:/Sun/AppServer/lib\relaxngDatatype.jar;C:/Sun/AppServer/lib\saaj-api.jar;C:/Sun/AppServer/lib\saaj-impl.jar;C:/Sun/AppServer/lib\xsdlib.jar;C:/Sun/AppServer/lib/install/applications/jmsra/imqjmsra.jar;C:/Sun/AppServer/imq/lib/jaxm-api.jar;C:/Sun/AppServer/imq/lib/fscontext.jar;C:/Sun/AppServer/lib/ant/lib/ant.jar;C:/Sun/AppServer/pointbase/lib/pbclient.jar;C:/Sun/AppServer/pointbase/lib/pbembedded.jar
com.sun.enterprise.server.PEMain
start
display
native|#]
[#|2005-11-02T11:47:57.533+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5034: Could not start the JMS service broker process.|#]
[#|2005-11-02T11:47:57.543+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5036: More details may be available in the log file for the JMS service broker instance imqbroker. Please refer to the JMS provider documentation for the exact location of this log file.|#]
[#|2005-11-02T11:47:57.543+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5024: JMS service startup failed.|#]
[#|2005-11-02T11:47:57.563+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
com.sun.appserv.server.ServerLifecycleException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:289)
at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Caused by: com.sun.appserv.server.ServerLifecycleException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:276)
... 5 more
Caused by: java.io.IOException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at java.lang.ProcessImpl.create(Native Method)
at java.lang.ProcessImpl.<init>(ProcessImpl.java:81)
at java.lang.ProcessImpl.start(ProcessImpl.java:30)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
at java.lang.Runtime.exec(Runtime.java:591)
at java.lang.Runtime.exec(Runtime.java:464)
at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.startProvider(JMSAdminImpl.java:769)
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:269)
... 5 more
|#]
[#|2005-11-02T11:47:57.563+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|Exception while stoppping Lifecycle.
java.lang.NullPointerException
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:389)
at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:67)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
|#]
[#|2005-11-02T11:47:58.224+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=11;|sending notification to server...server|#]
[#|2005-11-02T11:47:58.224+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=11;|Server shutdown complete.|#]
[#|2005-11-02T11:49:01.705+0300|WARNING|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER005:Spaces in your PATH have been detected. The PATH must be consistently formated (e.g. C:\Program Files\Java\jdk1.5.0\bin; ) or the Appserver may not be able to start and/or stop. Mixed quoted spaces in your PATH can cause problems, so the launcher will remove all double quotes before invoking the process. The most reliable solution would be to remove all spaces from your path before starting the Appservers components. |#]
[#|2005-11-02T11:49:01.715+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|
C:/Program Files/Java/jdk1.5.0_04\bin\java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=C:/Sun/AppServer/domains/domain1/logs/server.log
-Djava.endorsed.dirs=C:/Sun/AppServer/lib/endorsed
-Djava.security.policy=C:/Sun/AppServer/domains/domain1/config/server.policy
-Djava.security.auth.login.config=C:/Sun/AppServer/domains/domain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=C:/Sun/AppServer/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=C:/Sun/AppServer/domains/domain1/config/cacerts.jks
-Djava.ext.dirs=C:/Program Files/Java/jdk1.5.0_04/jre/lib/ext;C:/Sun/AppServer/domains/domain1/lib/ext
-Djdbc.drivers=com.pointbase.jdbc.jdbcUniversalDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
-Dcom.sun.aas.configName=server-config
-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
-Ddomain.name=domain1
-Djmx.invoke.getters=true
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=C:/Sun/AppServer/domains/domain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=domain1
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
-Dcom.sun.aas.configRoot=C:/Sun/AppServer/config
-Djava.library.path=C:\Program Files\Java\jdk1.5.0_04\jre\bin\client;C:\Sun\AppServer\lib;C:\Sun\AppServer\lib;C:\Program Files\Java\jdk1.5.0_04\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Rational\ClearQuest;
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
C:/Program Files/Java/jdk1.5.0_04/lib/tools.jar;C:/Sun/AppServer/lib/appserv-rt.jar;C:/Sun/AppServer/lib\admin-cli.jar;C:/Sun/AppServer/lib\appserv-admin.jar;C:/Sun/AppServer/lib\dom.jar;C:/Sun/AppServer/lib\jmxremote.jar;C:/Sun/AppServer/lib\jmxremote_optional.jar;C:/Sun/AppServer/lib\jsf-api.jar;C:/Sun/AppServer/lib\jsf-impl.jar;C:/Sun/AppServer/lib\rmissl.jar;C:/Sun/AppServer/lib\xalan.jar;C:/Sun/AppServer/lib\xercesImpl.jar;C:/Sun/AppServer/lib\appserv-assemblytool_ja.jar;C:/Sun/AppServer/lib\appserv-cmp_ja.jar;C:/Sun/AppServer/lib\appserv-rt_ja.jar;C:/Sun/AppServer/lib\commons-launcher_ja.jar;C:/Sun/AppServer/lib\deployhelp_ja.jar;C:/Sun/AppServer/lib\j2ee_ja.jar;C:/Sun/AppServer/lib\appserv-assemblytool_zh.jar;C:/Sun/AppServer/lib\appserv-assemblytool_zh_CN.jar;C:/Sun/AppServer/lib\appserv-cmp_zh.jar;C:/Sun/AppServer/lib\appserv-cmp_zh_CN.jar;C:/Sun/AppServer/lib\appserv-rt_zh.jar;C:/Sun/AppServer/lib\appserv-rt_zh_CN.jar;C:/Sun/AppServer/lib\commons-launcher_zh.jar;C:/Sun/AppServer/lib\commons-launcher_zh_CN.jar;C:/Sun/AppServer/lib\deployhelp_zh.jar;C:/Sun/AppServer/lib\deployhelp_zh_CN.jar;C:/Sun/AppServer/lib\j2ee_zh.jar;C:/Sun/AppServer/lib\j2ee_zh_CN.jar;C:/Sun/AppServer/lib\appserv-assemblytool_ko.jar;C:/Sun/AppServer/lib\appserv-cmp_ko.jar;C:/Sun/AppServer/lib\appserv-rt_ko.jar;C:/Sun/AppServer/lib\commons-launcher_ko.jar;C:/Sun/AppServer/lib\deployhelp_ko.jar;C:/Sun/AppServer/lib\j2ee_ko.jar;C:/Sun/AppServer/lib\appserv-assemblytool_fr.jar;C:/Sun/AppServer/lib\appserv-cmp_fr.jar;C:/Sun/AppServer/lib\appserv-rt_fr.jar;C:/Sun/AppServer/lib\commons-launcher_fr.jar;C:/Sun/AppServer/lib\deployhelp_fr.jar;C:/Sun/AppServer/lib\j2ee_fr.jar;C:/Sun/AppServer/lib\appserv-assemblytool_es.jar;C:/Sun/AppServer/lib\appserv-cmp_es.jar;C:/Sun/AppServer/lib\appserv-rt_es.jar;C:/Sun/AppServer/lib\commons-launcher_es.jar;C:/Sun/AppServer/lib\deployhelp_es.jar;C:/Sun/AppServer/lib\j2ee_es.jar;C:/Sun/AppServer/lib\appserv-upgrade.jar;C:/Sun/AppServer/lib\appserv-ext.jar;C:/Sun/AppServer/lib\j2ee.jar;C:/Sun/AppServer/lib\activation.jar;C:/Sun/AppServer/lib\appserv-cmp.jar;C:/Sun/AppServer/lib\appserv-jstl.jar;C:/Sun/AppServer/lib\commons-launcher.jar;C:/Sun/AppServer/lib\commons-logging.jar;C:/Sun/AppServer/lib\j2ee-svc.jar;C:/Sun/AppServer/lib\jax-qname.jar;C:/Sun/AppServer/lib\jaxr-api.jar;C:/Sun/AppServer/lib\jaxr-impl.jar;C:/Sun/AppServer/lib\jaxrpc-api.jar;C:/Sun/AppServer/lib\jaxrpc-impl.jar;C:/Sun/AppServer/lib\mail.jar;C:/Sun/AppServer/lib\relaxngDatatype.jar;C:/Sun/AppServer/lib\saaj-api.jar;C:/Sun/AppServer/lib\saaj-impl.jar;C:/Sun/AppServer/lib\xsdlib.jar;C:/Sun/AppServer/lib/install/applications/jmsra/imqjmsra.jar;C:/Sun/AppServer/imq/lib/jaxm-api.jar;C:/Sun/AppServer/imq/lib/fscontext.jar;C:/Sun/AppServer/lib/ant/lib/ant.jar;C:/Sun/AppServer/pointbase/lib/pbclient.jar;C:/Sun/AppServer/pointbase/lib/pbembedded.jar
com.sun.enterprise.server.PEMain
start
display
native|#]
[#|2005-11-02T11:49:05.671+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5034: Could not start the JMS service broker process.|#]
[#|2005-11-02T11:49:05.671+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5036: More details may be available in the log file for the JMS service broker instance imqbroker. Please refer to the JMS provider documentation for the exact location of this log file.|#]
[#|2005-11-02T11:49:05.681+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5024: JMS service startup failed.|#]
[#|2005-11-02T11:49:05.691+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
com.sun.appserv.server.ServerLifecycleException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:289)
at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Caused by: com.sun.appserv.server.ServerLifecycleException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:276)
... 5 more
Caused by: java.io.IOException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at java.lang.ProcessImpl.create(Native Method)
at java.lang.ProcessImpl.<init>(ProcessImpl.java:81)
at java.lang.ProcessImpl.start(ProcessImpl.java:30)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
at java.lang.Runtime.exec(Runtime.java:591)
at java.lang.Runtime.exec(Runtime.java:464)
at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.startProvider(JMSAdminImpl.java:769)
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:269)
... 5 more
|#]
[#|2005-11-02T11:49:05.691+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|Exception while stoppping Lifecycle.
java.lang.NullPointerException
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:389)
at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:67)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
|#]
[#|2005-11-02T11:49:06.432+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=11;|sending notification to server...server|#]
[#|2005-11-02T11:50:38.915+0300|WARNING|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER005:Spaces in your PATH have been detected. The PATH must be consistently formated (e.g. C:\Program Files\Java\jdk1.5.0\bin; ) or the Appserver may not be able to start and/or stop. Mixed quoted spaces in your PATH can cause problems, so the launcher will remove all double quotes before invoking the process. The most reliable solution would be to remove all spaces from your path before starting the Appservers components. |#]
[#|2005-11-02T11:50:38.925+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|
C:/Program Files/Java/jdk1.5.0_04\bin\java
-client
-Xdebug
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=9009
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=C:/Sun/AppServer/domains/domain1/logs/server.log
-Dcom.sun.aas.jdwpOptions=transport=dt_socket,server=y,suspend=n,address=9009
-Djava.endorsed.dirs=C:/Sun/AppServer/lib/endorsed
-Djava.security.policy=C:/Sun/AppServer/domains/domain1/config/server.policy
-Djava.security.auth.login.config=C:/Sun/AppServer/domains/domain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=C:/Sun/AppServer/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=C:/Sun/AppServer/domains/domain1/config/cacerts.jks
-Djava.ext.dirs=C:/Program Files/Java/jdk1.5.0_04/ -
Accessing txt files in the App server from web application
Hi All,
We have a use case, where we need to access txt files from the ADF web application.
We will display to the user the path of the file and whenever he/she clicks, it should be downloaded automatically to the users machine.
Environments we need to develop: JDeveloper 10.1.3.4 and Oracle App Server 10.1.3.1
And our server has credentials and only those who have access to the server can access the files.
Point me or suggest me a good solution to this use case.
Regards,
Naga.Hi Joonas,
i was able to download the files, thanks a lot for your guidance. i will mark your answer as correct.
Can you let me know how to achieve the following usecase.
1. there will be multiple text files in the server i.e., out of our web application context like in some folder
2. And we need to give user a http link and if he clicks on the link that file should be downloaded automatically to his machine.
and we are using oracle app server 10.1.3.4, please point me to some document or example.
thank you.
naga. -
J2EE on Windows App server wont start after JSPM patching
Hi,
I've patched an ECC6 system on DB2 V5R4 to SP16 level on ABAP side, and Enhancement pack 3, and then did an update to JSPM and installed new SP16 levels of the Java components.
Now my Windows App server starts only the ABAP Work processes, not the J2EE side. I get a yellow light and the message
J2EE Status info unavailable.
On the Windows work directory for Dialog instance D00, I see that the dev_server0 has only messages about the last shutdown 2 days ago.
The dev_jcontrol has errors in it abot Unknown property and
JStartupICheckFrameworkPackage: can't find framework package U:\usr\sap\WFD\D00\exe\jvmx.jar
see below.
Any ideas?
regards
Michael.
trc file: "U:\usr\sap\WFD\D00\work\dev_jcontrol", trc level: 1, release: "700"
node name : jcontrol
pid : 2308
system name : WFD
system nr. : 00
started at : Thu Sep 25 15:46:00 2008
arguments :
arg[00] : U:\usr\sap\WFD\D00\exe\jcontrol.EXE
arg[01] : pf=
sapdev\sapmnt\WFD\SYS\profile\WFD_D00_dfbhl6
arg[02] : -DSAPSTART=1
arg[03] : -DCONNECT_PORT=64990
arg[04] : -DSAPSYSTEM=00
arg[05] : -DSAPSYSTEMNAME=WFD
arg[06] : -DSAPMYNAME=dfbhl6_WFD_00
arg[07] : -DSAPPROFILE=
sapdev\sapmnt\WFD\SYS\profile\WFD_D00_dfbhl6
arg[08] : -DFRFC_FALLBACK=ON
arg[09] : -DFRFC_FALLBACK_HOST=localhost
[Thr 2040] Thu Sep 25 15:46:00 2008
[Thr 2040] *** WARNING => INFO: Unknown property [instance.box.number=WFDD00dfbhl6] [jstartxx.c 841]
[Thr 2040] *** WARNING => INFO: Unknown property [instance.en.host=sapdev] [jstartxx.c 841]
[Thr 2040] *** WARNING => INFO: Unknown property [instance.en.port=3241] [jstartxx.c 841]
[Thr 2040] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c 841]
JStartupReadInstanceProperties: read instance properties [U:\usr\sap\WFD\D00\j2ee\cluster\instance.properties]
-> ms host : sapdev
-> ms port : 3941
-> OS libs : U:\usr\sap\WFD\D00\j2ee\os_libs
-> Admin URL :
-> run mode : safe
-> run action : UPGRADE
-> enabled : no
Used property files
-> files [00] : U:\usr\sap\WFD\D00\j2ee\cluster\instance.properties
Instance properties
-> ms host : sapdev
-> ms port : 3941
-> os libs : U:\usr\sap\WFD\D00\j2ee\os_libs
-> admin URL :
-> run mode : safe
-> run action : UPGRADE
-> enabled : no
Bootstrap nodes
-> [00] bootstrap : U:\usr\sap\WFD\D00\j2ee\cluster\instance.properties
-> [01] bootstrap_ID2623900 : U:\usr\sap\WFD\D00\j2ee\cluster\instance.properties
-> [02] bootstrap_ID2623950 : U:\usr\sap\WFD\D00\j2ee\cluster\instance.properties
Worker nodes
-> [00] ID2623900 : U:\usr\sap\WFD\D00\j2ee\cluster\instance.properties
-> [01] ID2623950 : U:\usr\sap\WFD\D00\j2ee\cluster\instance.properties
[Thr 2040] JControlExecuteBootstrap: execute bootstrap process [bootstrap]
[Thr 3504] JControlDPMessageProxy: Thread 3504 started as handler thread for R/3 dispatcher messages.
[Thr 2040] [Node: bootstrap] java home is set by profile parameter
Java Home: C:\j2sdk1.4.2_13
[Thr 2040] JStartupICheckFrameworkPackage: can't find framework package U:\usr\sap\WFD\D00\exe\jvmx.jar
JStartupIReadSection: read node properties [bootstrap]
-> node name : bootstrap
-> node type : bootstrap
-> node execute : yes
-> java path : C:\j2sdk1.4.2_13
-> java parameters : -Djco.jarm=1 -verbose:gc -Djava.compiler=jitc -Dos400.run.mode=jitc -Dos400.disable.explicit.gc -Dos400.define.class.cache.file=/usr/sap/WFD/SYS/j2ee/cache/QDefineClassCache.jar -Dos400.define.class.cache.hours=9999 -Dos400.define.class.cache.maxpgms=40000 -Djava.ext.dirs=/usr/sap/WFD/SYS/j2ee/ext
-> java vm version : 1.4.2_13-b06
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 512M
-> root path : U:\usr\sap\WFD\D00\j2ee\cluster
-> class path : .\bootstrap\launcher.jar
-> OS libs path : U:\usr\sap\WFD\D00\j2ee\os_libs
-> main class : com.sap.engine.offline.OfflineToolStart
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : U:\usr\sap\WFD\D00\exe\jstartup.jar;U:\usr\sap\WFD\D00\exe\jvmx.jar
-> parameters : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID0026239
-> debuggable : yes
-> debug mode : no
-> debug port : 60000
-> shutdown timeout : 120000
JControlStartJLaunch: program = U:\usr\sap\WFD\D00\exe\jlaunch.exe
-> arg[00] = U:\usr\sap\WFD\D00\exe\jlaunch.exe
-> arg[01] = pf=
sapdev\sapmnt\WFD\SYS\profile\WFD_D00_dfbhl6
-> arg[02] = -DSAPINFO=WFD_00_bootstrap
-> arg[03] = -nodeId=-1
-> arg[04] = -file=U:\usr\sap\WFD\D00\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_2308
-> arg[06] = -nodeName=bootstrap
-> arg[07] = -jvmOutFile=U:\usr\sap\WFD\D00\work\jvm_bootstrap.out
-> arg[08] = -stdOutFile=U:\usr\sap\WFD\D00\work\std_bootstrap.out
-> arg[09] = -locOutFile=U:\usr\sap\WFD\D00\work\dev_bootstrap
-> arg[10] = -mode=BOOTSTRAP
-> arg[11] = pf=
sapdev\sapmnt\WFD\SYS\profile\WFD_D00_dfbhl6
-> arg[12] = -DSAPSTART=1
-> arg[13] = -DCONNECT_PORT=4556
-> arg[14] = -DSAPSYSTEM=00
-> arg[15] = -DSAPSYSTEMNAME=WFD
-> arg[16] = -DSAPMYNAME=dfbhl6_WFD_00
-> arg[17] = -DSAPPROFILE=
sapdev\sapmnt\WFD\SYS\profile\WFD_D00_dfbhl6
-> arg[18] = -DFRFC_FALLBACK=ON
-> arg[19] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;U:\usr\sap\APD\D31\exe;
sapdev\SAPMNT\APD\exe\run_nt;U:\sapdb\programs\bin;U:\sapdb\programs\pgm;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;C:\WINNT\AS400WSV\Admin;C:\WINNT\AS400WSV\Service;C:\WINNT\AS400WSV\Drivers;C:\PROGRA1\IBM\CLIENT1;C:\PROGRA1\IBM\CLIENT1\Shared;C:\PROGRA1\IBM\CLIENT1\Emulator;C:\Program Files\Symantec\pcAnywhere\;;
sapdev\sapmnt\WFD\SYS\exe\uc\NTI386;U:\usr\sap\WFD\D00\exe
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;U:\usr\sap\WFD\D00\j2ee\os_libs;U:\usr\sap\APD\D31\exe;
sapdev\SAPMNT\APD\exe\run_nt;U:\sapdb\programs\bin;U:\sapdb\programs\pgm;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;C:\WINNT\AS400WSV\Admin;C:\WINNT\AS400WSV\Service;C:\WINNT\AS400WSV\Drivers;C:\PROGRA1\IBM\CLIENT1;C:\PROGRA1\IBM\CLIENT1\Shared;C:\PROGRA1\IBM\CLIENT1\Emulator;C:\Program Files\Symantec\pcAnywhere\;;
sapdev\sapmnt\WFD\SYS\exe\uc\NTI386;U:\usr\sap\WFD\D00\exe
[Thr 2040] Thu Sep 25 15:46:26 2008
[Thr 2040] JControlExecuteBootstrap: read instance values after global bootstrap
[Thr 2040] *** WARNING => INFO: Unknown property [instance.box.number=WFDD00dfbhl6] [jstartxx.c 841]
[Thr 2040] *** WARNING => INFO: Unknown property [instance.en.host=sapdev] [jstartxx.c 841]
[Thr 2040] *** WARNING => INFO: Unknown property [instance.en.port=3241] [jstartxx.c 841]
[Thr 2040] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c 841]
JStartupReadInstanceProperties: read instance properties [U:\usr\sap\WFD\D00\j2ee\cluster\instance.properties]
-> ms host : sapdev
-> ms port : 3941
-> OS libs : U:\usr\sap\WFD\D00\j2ee\os_libs
-> Admin URL :
-> run mode : safe
-> run action : UPGRADE
-> enabled : no
[Thr 2040] JControlExecuteBootstrap: enumerate the nodes after global bootstrap
Used property files
-> files [00] : U:\usr\sap\WFD\D00\j2ee\cluster\instance.properties
Instance properties
-> ms host : sapdev
-> ms port : 3941
-> os libs : U:\usr\sap\WFD\D00\j2ee\os_libs
-> admin URL :
-> run mode : safe
-> run action : UPGRADE
-> enabled : no
Bootstrap nodes
-> [00] bootstrap : U:\usr\sap\WFD\D00\j2ee\cluster\instance.properties
-> [01] bootstrap_ID2623900 : U:\usr\sap\WFD\D00\j2ee\cluster\instance.properties
-> [02] bootstrap_ID2623950 : U:\usr\sap\WFD\D00\j2ee\cluster\instance.properties
Worker nodes
-> [00] ID2623900 : U:\usr\sap\WFD\D00\j2ee\cluster\instance.properties
-> [01] ID2623950 : U:\usr\sap\WFD\D00\j2ee\cluster\instance.properties
[Thr 2040] JControlCheckRunMode: run mode of the instance = safe
[Thr 2040] Instance is disabled -> terminate.
[Thr 2040] JControlCloseProgram: started (exitcode = -11113)
[Thr 2040] JControlCloseProgram: good bye... (exitcode = -11113)Thanks Kaushal,
I hadn't done any changes to UME, but I have got a JSPM support package (EP-PSERV SP16) in status of ERROR that seems to be at the bottom of the problem.
Apparently, JSPM is not able to cope with any flavour of IBM DB2 (Windows, AIX, or i) at a point in this support package. There is a note 1156313 and it matches the error which is in the sdm log file:
Sep 25, 2008 4:51:32 PM Info: 16:51:31 2008-09-25 dbs-Info: WCR_USERSTAT modify column LOGONID to type : VARCHAR,len : 255,dec : 0,not null : true,default :
Sep 25, 2008 4:51:32 PM Info: 16:51:31 2008-09-25 dbs-Info: WCR_USERSTAT modify column LOGONID to type : VARCHAR,len : 255,dec : 0,not null : true,default :
Sep 25, 2008 4:51:32 PM Info: 16:51:31 2008-09-25 db4-Info: existsData() returns true.
Sep 25, 2008 4:51:32 PM Info: 16:51:31 2008-09-25 dbs-Info: Action: CONVERT
Sep 25, 2008 4:51:32 PM Info: 16:51:31 2008-09-25 dbs-Info: Action: CONVERT
Sep 25, 2008 4:51:32 PM Info: 16:51:31 2008-09-25 dbs-Info: Table has to be converted
Sep 25, 2008 4:51:32 PM Info: 16:51:31 2008-09-25 dbs-Info: Table has to be converted
Sep 25, 2008 4:51:32 PM Info:
Sep 25, 2008 4:51:32 PM Info: E R R O R ******* (DbModificationManager)
Sep 25, 2008 4:51:32 PM Info: 16:51:31 2008-09-25 dbs-Error: Table WCR_USERSTAT: Conversion currently not possible
Sep 25, 2008 4:51:32 PM Info:
Sep 25, 2008 4:51:32 PM Info: E R R O R ******* (DbModificationManager)
Sep 25, 2008 4:51:32 PM Info: 16:51:31 2008-09-25 dbs-Error: Table WCR_USERSTAT: Conversion currently not possible
Meanwhile, the commands in the note don't work as the DB (Owner ) *ALL
PUBLIC *EXCLUDE
regards
Michael -
How to store the report output in app server local directory
Dear All,
I would like to store the reports output in the app server folder. How do i achieve?
I am using reports10g, app server 10g. I am using web.show_document to call the reports. I would like to the achieve the same using this web.show_document built in.
Thanks
BalajiHi,
using desname pointing to an path on the apps-server the output is stored there. But when opening before in browser, then this document is stored in temporary folder on the client and you can't store them then to the apps server (if you not map the apps server or use web dav to do that).
Regards
Rainer -
Using FILE to interact with the CI from an App server
Hi All.
We have a custom code function where a user takes a text file and uploads it into the SAP system. The file is immediately processed and a new 'outbound' file is created. Currently, we have the dirctory structure set-up on out CI/DB server. Our users access the system from one of 2 application servers.
The issue we have is that due to the definition in FILE, when the users execute the report, it errors out. This is becasue when they execute, SAP looks to the local server - the app servers - for the directory. As stated, this directory lives on the CI. Does anyone know how to adjust the functionality of FILE so that I can point the program to execute on the CI and not the app server? Thanks!Hello Tim,
We have a similar scenario like you but dont face this issue. 2 things are imüportant here:
1. The directory residing on CI should be accessible from the other application server i.e the mount should be correct.
2. The logical file path name in FILE should be correct. This is very important.
Believe me we have a more complex arrangement where 5 SAP s are involved and the directory resides on only one of them
Also FILE cannot dicate on which system the program is executed.It purely depends on the app server where the user is logged in.
Regards.
Ruchit.
Maybe you are looking for
-
Mac running slow and Mackeeper not working since 10.9.2 installation
Why is my MacMini2 running slow after installing Mavericks? Why is MacKeeper no longer available?
-
Acrobat 5.0 How do I keep the original file name after I have converted a Word doc to PDF?
MY colleague has a certain setting in Acrobat that allows him to keep the original file name when he converts documents from Word to PDF. Every time I convert Word, Acrobat overwrites the filename and names it "untitled.pdf". I would like to retain t
-
Message redigest inequality at server side
Hello! This issue has been giving me headaches for several days: I have a client-server application. The server receives from the client the following: message + messageDigest. It recomputes the digest to see if any transmission errors have occured,
-
Call x.exe and write command in opened DOS window
Hi, I am using Labview 10 and Window 7. Just wondering how to use labview to 1. run x.exe under opened DOS window? 2. write command in opened DOS window? Any commends welcome, Thanks, Ott
-
Printing from Adobe Acrobat 8.1 under OS 10.6.7 to CANON PIXMA MX300 printer
If I DRAG the icon for my Adobe Acrobat file (made with AA ver.8.1 on OS 10.6.7) to printer icon (printer is a CANON PIXMA MX300 I bought at Apple store), I print just fine but if I try to print from within Adobe Acrobat, I get an error message in th