Where is jasper-runtime.jar in the J2EE Server?
I'm trying to use the J2EE server that comes with the J2EE-SDK rather than a straight Apache/Tomcat installation. I want to hand compile one of the files created by the server when it processes a .JSP in order to get more reasonable error messages than the ones that the server reports. This used to work just fine because all of the apache .jar files were on my CLASSPATH, but now I'm getting a host of
package org.apache.jasper.runtime does not exist
How do I set up the CLASSPATH so that javac can see the same packages that are visible to the compiler invoked from the server when it compiles a JSP?
regarding your question you can find it in appserv-rt.jar file located at
C:\Sun\AppServer\lib\appserv-rt.jar
Similar Messages
-
How to add a Jar file to J2EE Server Component Library ?
Hello,
My objective:
=====================================================
To add a 3rd party jar file to be a runtime jar file to J2EE Server Component
Library project.
I have created a J2EE Server Component Library project.
I have built the J2EE Server Component Library project to get the provider.xml file and place the provider.xml under the J2EE Server Component Library project's server folder.
Here is my problem:
=====================================================
I can't open the provider.xml with SAP's special editor for the provider.xml.
The special SAP editor doesn't exist for me.
Here is my question:
=====================================================
Q1) Do I copy/paste my JAR_X file where <jar_0> is located? (Below is the
J2EE Server Component Library SDA structure.)
Q2) If you were to update the provider.xml with notepad, what would you
type in provider.xml for JAR_X?
Q3) Is there anything else that I need to do?
Thanks,
Steve
J2EE Server Component Library SDA structure.
======================================
|-META-INF_
| |-manifest.mf
| |-sap_manifest.mf
| |-SearchRules.xml
| |-<SDA>.xml
| |...
|-<jar_0>
|- ...
|-<jar_N>
|-dispatcher_
| |-provider.xml
| |-properties
| |-runtime.properties
| |-persistent__
| | |-<persistent_files(2)>
| |-descriptors_
| |-<descriptor_files(3)>
|-server_____
| |-provider.xml
| |-properties
| |-runtime.properties
| |-persistent__
| | |-<persistent_files>
| |-descriptors_
| |-<descriptor_files>
|-os_libs____
|-<char set>__
|-<platform>__
|-<jvm bitlength>__
|-<native lib files>Thank you for all your solution...
my provider.xml was missing the <!DOCTYPE> tag for me to use the SAP LibraryDD Editor
Thanks again,
Steve
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE provider-descriptor SYSTEM "library.provider.dtd">
<provider-descriptor>
<display-name>
Your_Lib_Name
</display-name>
<component-name>
Your_Lib_Name
</component-name>
<major-version>6</major-version>
<minor-version>40</minor-version>
<micro-version>0</micro-version>
<provider-name>
sap.com
</provider-name>
<references>
<reference
provider-name="sap.com"
strength="weak"
type="library">Your_Lib_Name</reference>
</references>
<jars>
<jar-name>my_jar.jar</jar-name>
</jars>
</provider-descriptor> -
Where to find the information to setup the J2EE server to run optimal CPS
Hello,
I am looking for the information, how the J2EE server should be setup, to run optimal CPS.
In the installation guide I am not finding it, our I am not looking on the right pages.
We are using CPS for 4 dev. systems, 1 q und 5 prod. systems.
On the dev. system we want to run the default sap jobs and the db13 jobs on CPS.
On the prod. system we are talking around 300 jobs.
I am looking for a hint, like use 4 jlaunch process with mem 4 gb, or something.
Run the CPS in the evalution right now, it performs very slow.
We are using two jlaunch process, using 2 GB each.
The both processes are clusterd.
Many thanks for your feedback.
Best regards
Carlos BehlauHi Neil and Anton,
many thanks for your feedback.
Concerning the sizing guide:
I am aware of the sizing guide.
What I do not find, with what setting the J2EE Server should run.
Lets say: We having a 64 Bit OS u2013 should the J2EE Server process run with 2 GB, the default, or would it speed up the application if we would give the process 4 GB.
What about the caching settings, of the J2EE Server?
Are there any best practice documents for VMware ESX environment?
Best regards and many thanks for your replyu2019s.
Carlos Behlau -
How to read the J2EE server hostname and port programmatically
Is there any API to read the J2EE server host and port programmatically? I am looking for the hostname where the components are deployed so that I can append the wsdl path to the server and create an URL.
Hi Larry,
there is a standard J2EE Servlet API for your case.
In a servlet or jsp file you can get the host and prot from the request object.
For example in a JSP file :
request.getScheme();
request.getServerName()
request.getServerPort()
You can check the whole API here :
http://java.sun.com/products/servlet/2.2/javadoc/javax/servlet/ServletRequest.html#getServerName()
Bets Regards
Bojidar -
The J2EE Server not starting.
Hello,
The J2EE Server not starting. (Not able to communicate with message server)
The following is the description I got from SAP.
" Most likely you did configurations on the instance properties, instead
of the global properties, which is the one where the the configurations
should be done. That is why now you did set local properties
which are now false, for example : ume.ldap.access.server_port=[]
This is the cause why the LDAP connection data cannot be retrieved.
This is why the UME service cannot be started.
This is why the J2ee engine is not comming up. "
Pls help.Hi Karan
1.Go to \usr\sap\SID\JCXX\j2ee\configtool and start the config tool.
2.No go to instance -
>server----->services--->com.sap.security.core.ume.services node.
3.Look for ume.ldap.access.server_port=[]
4.See if you have changed the value for the above parameter.If yes change the value to default and restart the engine.It will work
If at all you want to change any configurations you should do it following the below steps:
1.Go to \usr\sap\SID\JCXX\j2ee\configtool and start the config tool
2.Go to Global Server Configurations-->Services--
>
Please award points: -
Hi:
I am having problem starting the J2EE Server.
I have looked through this page where lots of people had similar problem:
http://forum.java.sun.com/thread.jsp?forum=136&thread=468079
but the solutions provided there could not solve my problem...
My problem, specifically, is that when I try to start the sever, I get:
com.sun.enterprise.admin.servermgmt.DomainException: ...
CLI156 Could not start the domain domain1.
I am using Windows XP Professional on IBM ThinkPad X30.
Does anyone have some idea how to solve the problem?
Thanx!bsankararao,
Thanks for the quick response. I am currently using the latest IE6.0 XPXP2 version and yes I doe have a successful start of the domain1 process. Here is the startup log for verification:
[#|2004-02-02T15:03:04.765-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_02] from [Sun Microsystems Inc.]|#]
[#|2004-02-02T15:03:12.246-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-02-02T15:03:12.436-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-02-02T15:03:14.649-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating Engine server|#]
[#|2004-02-02T15:03:15.470-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-02-02T15:03:15.491-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-02-02T15:03:15.521-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-02-02T15:03:32.084-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-02-02T15:03:34.338-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-02-02T15:03:34.938-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-02-02T15:03:36.391-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-02-02T15:03:36.421-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|autoDeployment status dir missing, creating a new one|#]
[#|2004-02-02T15:03:36.451-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Selecting file [D:\Sun\AppServer\lib\install\applications\MEjbApp.ear] for autodeployment|#]
[#|2004-02-02T15:03:36.471-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Selecting file [D:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear] for autodeployment|#]
[#|2004-02-02T15:03:36.481-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ D:\Sun\AppServer\lib\install\applications\MEjbApp.ear ] for autodeployment.|#]
[#|2004-02-02T15:03:38.043-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [MEjbApp]|#]
[#|2004-02-02T15:03:38.203-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5108: EJBC - Generated code for remote home and EJBObject implementations for [MEjbApp]|#]
[#|2004-02-02T15:03:48.818-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [MEjbApp]|#]
[#|2004-02-02T15:03:49.549-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 12728 msec, Total EJB Compiler Module Time: 10775 msec, Portion spent EJB Compiling: 84%
Breakdown of EJBC Module Time: Total Time for EJBC: 10775 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 10605 msec (98%), JAX-RPC Generation: 20 msec (0%),
|#]
[#|2004-02-02T15:03:49.750-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy MEjbApp]|#]
[#|2004-02-02T15:03:50.571-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-02-02T15:03:50.591-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2004-02-02T15:03:50.591-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : D:\Sun\AppServer\lib\install\applications\MEjbApp.ear.|#]
[#|2004-02-02T15:03:50.591-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ D:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear ] for autodeployment.|#]
[#|2004-02-02T15:03:51.292-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [__ejb_container_timer_app]|#]
[#|2004-02-02T15:03:56.029-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [__ejb_container_timer_app]|#]
[#|2004-02-02T15:03:56.309-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 5688 msec, Total EJB Compiler Module Time: 4737 msec, Portion spent EJB Compiling: 83%
Breakdown of EJBC Module Time: Total Time for EJBC: 4737 msec, CMP Generation: 2674 msec (56%), Java Compilation: 1933 msec (40%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 0 msec (0%),
|#]
[#|2004-02-02T15:03:56.339-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy __ejb_container_timer_app]|#]
[#|2004-02-02T15:03:56.740-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-02-02T15:03:56.740-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-02-02T15:03:56.740-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2004-02-02T15:03:56.740-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : D:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear.|#]
[#|2004-02-02T15:03:56.810-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-02-02T15:03:57.210-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-02-02T15:03:57.461-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-02-02T15:03:57.521-0600|INFO|j2ee-appserver1.4|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-02-02T15:03:57.571-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-02-02T15:03:57.571-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-02-02T15:03:57.721-0600|INFO|j2ee-appserver1.4|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: J2EETM 1.4 Application Server|#]
[#|2004-02-02T15:03:59.924-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-02-02T15:04:00.315-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-02T15:04:00.355-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-02T15:04:00.936-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-02T15:04:00.946-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-02T15:04:00.966-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-02T15:04:00.986-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-02T15:04:01.266-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = domain1_server, Home = [D:\Sun\AppServer\imq\bin].|#]
[#|2004-02-02T15:04:01.276-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1075755841276|#]
[#|2004-02-02T15:04:01.276-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2004-02-02T15:04:01.276-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
[#|2004-02-02T15:18:13.512-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=11;|SEC5046: Audit: Authentication refused for [].|#]
[#|2004-02-02T15:18:13.522-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=11;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for .|#]
[#|2004-02-02T15:18:39.119-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=11;|SEC5046: Audit: Authentication refused for [admin].|#]
[#|2004-02-02T15:18:39.119-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=11;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for admin.|#]
[#|2004-02-02T19:27:40.443-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=12;|SEC5046: Audit: Authentication refused for [].|#]
[#|2004-02-02T19:27:41.174-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=12;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for .|#]
[#|2004-02-02T19:27:49.076-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=12;|SEC5046: Audit: Authentication refused for [].|#]
[#|2004-02-02T19:27:49.076-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=12;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for .|#]
[#|2004-02-02T19:31:57.022-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=11;|SEC5046: Audit: Authentication refused for [admin].|#]
[#|2004-02-02T19:31:57.022-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=11;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for admin.|#]
[#|2004-02-02T19:32:08.869-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=12;|SEC5046: Audit: Authentication refused for [admin].|#]
[#|2004-02-02T19:32:08.869-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=12;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for admin.|#]
[#|2004-02-02T20:00:22.424-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=12;|SEC5046: Audit: Authentication refused for [admin].|#]
[#|2004-02-02T20:00:22.424-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=12;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for admin.|#]
[#|2004-02-03T08:30:22.556-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_02] from [Sun Microsystems Inc.]|#]
[#|2004-02-03T08:30:23.808-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-02-03T08:30:23.998-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-02-03T08:30:26.422-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating Engine server|#]
[#|2004-02-03T08:30:27.143-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-02-03T08:30:27.203-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-02-03T08:30:27.253-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-02-03T08:30:31.509-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-02-03T08:30:33.462-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-02-03T08:30:33.963-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-02-03T08:30:34.914-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-02-03T08:30:36.036-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-02-03T08:30:36.877-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-02-03T08:30:36.877-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-02-03T08:30:37.027-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-02-03T08:30:37.428-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-02-03T08:30:37.618-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-02-03T08:30:37.638-0600|INFO|j2ee-appserver1.4|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-02-03T08:30:37.668-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-02-03T08:30:37.668-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-02-03T08:30:37.798-0600|INFO|j2ee-appserver1.4|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: J2EETM 1.4 Application Server|#]
[#|2004-02-03T08:30:39.901-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-02-03T08:30:40.202-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-03T08:30:40.242-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-03T08:30:40.402-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-03T08:30:40.412-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-03T08:30:40.442-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-03T08:30:40.452-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-03T08:30:40.732-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = domain1_server, Home = [D:\Sun\AppServer\imq\bin].|#]
[#|2004-02-03T08:30:40.752-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1075818640752|#]
[#|2004-02-03T08:30:40.752-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2004-02-03T08:30:40.752-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
[#|2004-02-03T08:48:32.383-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=11;|[AutoDeploy] Selecting file [ D:\Sun\AppServer\domains\domain1\autodeploy\hello.war ] for autodeployment.|#]
[#|2004-02-03T08:48:33.785-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=11;|DPL5109: EJBC - START of EJBC for [hello]|#]
[#|2004-02-03T08:48:33.835-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=11;|DPL5110: EJBC - END of EJBC for [hello]|#]
[#|2004-02-03T08:48:34.606-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=11;|Total Deployment Time: 1862 msec, Total EJB Compiler Module Time: 50 msec, Portion spent EJB Compiling: 2%
Breakdown of EJBC Module Time: Total Time for EJBC: 50 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 10 msec (20%),
|#]
[#|2004-02-03T08:48:34.807-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1041:Sent the event to instance:[ModuleDeployEvent -- deploy web/hello]|#]
[#|2004-02-03T08:48:35.007-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=11;|WEB0100: Loading web module [hello] in virtual server [server] at [hello]|#]
[#|2004-02-03T08:48:36.719-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2004-02-03T08:48:36.729-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=11;|[AutoDeploy] Successfully autodeployed : D:\Sun\AppServer\domains\domain1\autodeploy\hello.war.|#]
[#|2004-02-03T14:53:47.246-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_02] from [Sun Microsystems Inc.]|#]
[#|2004-02-03T14:53:48.718-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-02-03T14:53:48.929-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-02-03T14:53:51.222-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating Engine server|#]
[#|2004-02-03T14:53:52.003-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-02-03T14:53:52.033-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-02-03T14:53:52.043-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-02-03T14:53:56.449-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-02-03T14:53:58.492-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-02-03T14:53:58.983-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-02-03T14:53:59.985-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-02-03T14:54:01.206-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-02-03T14:54:02.048-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-02-03T14:54:02.048-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-02-03T14:54:02.188-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-02-03T14:54:02.678-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-02-03T14:54:02.899-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-02-03T14:54:02.919-0600|INFO|j2ee-appserver1.4|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-02-03T14:54:02.939-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [hello] in virtual server [server] at [hello]|#]
[#|2004-02-03T14:54:02.989-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-02-03T14:54:02.989-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-02-03T14:54:03.119-0600|INFO|j2ee-appserver1.4|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: J2EETM 1.4 Application Server|#]
[#|2004-02-03T14:54:05.563-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-02-03T14:54:05.883-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-03T14:54:05.943-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-03T14:54:06.083-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-03T14:54:06.093-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-03T14:54:06.123-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-03T14:54:06.133-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-03T14:54:06.424-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = domain1_server, Home = [D:\Sun\AppServer\imq\bin].|#]
[#|2004-02-03T14:54:06.434-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1075841646434|#]
[#|2004-02-03T14:54:06.434-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2004-02-03T14:54:06.434-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
[#|2004-02-03T23:32:20.272-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_02] from [Sun Microsystems Inc.]|#]
[#|2004-02-03T23:32:22.004-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-02-03T23:32:22.234-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-02-03T23:32:24.608-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating Engine server|#]
[#|2004-02-03T23:32:25.629-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-02-03T23:32:25.659-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-02-03T23:32:25.689-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-02-03T23:32:31.237-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-02-03T23:32:33.781-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-02-03T23:32:34.332-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-02-03T23:32:35.453-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-02-03T23:32:37.156-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-02-03T23:32:38.137-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-02-03T23:32:38.137-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-02-03T23:32:38.317-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-02-03T23:32:38.948-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-02-03T23:32:39.179-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-02-03T23:32:39.199-0600|INFO|j2ee-appserver1.4|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-02-03T23:32:39.229-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [hello] in virtual server [server] at [hello]|#]
[#|2004-02-03T23:32:39.269-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-02-03T23:32:39.269-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-02-03T23:32:39.439-0600|INFO|j2ee-appserver1.4|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: J2EETM 1.4 Application Server|#]
[#|2004-02-03T23:32:42.343-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-02-03T23:32:42.724-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-03T23:32:42.764-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-03T23:32:42.944-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-03T23:32:42.954-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-03T23:32:42.994-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-03T23:32:43.014-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-03T23:32:43.315-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = domain1_server, Home = [D:\Sun\AppServer\imq\bin].|#]
[#|2004-02-03T23:32:43.335-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1075872763335|#]
[#|2004-02-03T23:32:43.335-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2004-02-03T23:32:43.335-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
[#|2004-02-04T08:31:44.681-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_02 -
Hi:
I am new to J2EE and I followed the instruction on the J2EE Tutorial setting up the J2EE SDK. When I tried to start the J2EE server by typing in "C:\j2ee -verbose", the server can't seem to start... After it gets to "Starting JMS service..." , it jumps back to the command prompt "C:\>"
If I then try to do a "j2ee -stop", I get an error "javax.naming.CommunicationException: Can't find SerialContextProvider" (which, I think, indicates the server never got started)
I am using Windows 2000 and I am pretty sure I have the environment variables set properly. Does anyone know why this is happening? Thanx!
The following is the trace of me doing "j2ee -verbose"
J2EE server listen port: 1050
Naming service started:1050
Binding DataSource, name = jdbc/DB1, url = jdbc:cloudscape:rmi:CloudscapeDB;crea
te=true
Binding DataSource, name = jdbc/EstoreDB, url = jdbc:cloudscape:rmi:CloudscapeDB
;create=true
Binding DataSource, name = jdbc/Cloudscape, url = jdbc:cloudscape:rmi:Cloudscape
DB;create=true
Binding DataSource, name = jdbc/InventoryDB, url = jdbc:cloudscape:rmi:Cloudscap
eDB;create=true
Binding DataSource, name = jdbc/DB2, url = jdbc:cloudscape:rmi:CloudscapeDB;crea
te=true
Binding DataSource, name = jdbc/XACloudscape, url = jdbc/XACloudscape__xa
Binding DataSource, name = jdbc/XACloudscape__xa, dataSource = COM.cloudscape.co
re.RemoteXaDataSource@b301f2
Starting JMS service...
C:\j2sdkee1.3.1\bin>
EugeneI have read some posts and get the answer
change the pc language to English
and reinstall j2ee
all should be ok!
I get message "J2EE server startup complete" now.
luck! -
Configuring the J2EE server in WSADMIN
I am a newbie to the WAS (although not to ABAP). Futhermore I am a developer, not a BASIS person. So please gentle and kind in your responses
I am trying to test my first Web Service that I've created from an ABAP RFC. In testing it via WSADMIN, I have found that I need to configure a J2EE server.
Here's the message I am receiving...
Diagnosis
The J2EE Server provides the Web Service homepage with test functions. To use these test functions, the address of the J2EE Server must be defined.
My questions are:
1) Do I need this J2EE server defined to make my web service work or is it only required for testing?
2) What are the requirements for a J2EE server?
Thanks,
WardellHelpppp!!!!, i have the same problem, could you resolve it??? please help me.
-
Trying to call a Webservice - "Settings for the J2EE Server do not exist."
Hi, we're on SAP ECC 6.0 and I'm trying to get access to a webservice:
BAPI converted to Webservice ok
Webservice activated ok
http active ok
WSADMIN - click on the WSDL button - browser launches, user id requested, userid given, WSDL displays perfect! Even tested from the outside.
WSADMIN - click on the Web service homepage - Settings for WDSL generation (RPC or Document style, same result) - Error - "Settings for the J2EE Server do not exist."
Internet browesr - I go to the URL for the WSDL - works again perfect!
Internet browesr - I go to the URL - error ! <faultstring xml:lang="en">SOAP processing failure, error id = 112 </faultstring>
Are the two errors the same?
Do I have to have a J2EE server to enable Webservices?
Is this a complex system change?
Is there a workaround?
Thanks for any tips on getting Webservice to function
Philiphi,
when the WAS ABAP has a webserver running and the WSDL service up and running (WSDLs are created dynamically) you get the WSDL served from WAS ABAP.
"Webservice homepage" is an application written in Java and running on WAS Java., So, if you want to use that application you have to have a WAS JAVA up and running, you have to have the application 'Webservice homepage' up and running and of course on WAS ABAP you have to have the URL of the WAS JAVA specified to enable the WSADMIN function to link you to the Java app.
Most probably you do not even have a WAS Java running and/or the application 'webservice homepage" not set up. Either way, in my opinion the application "webservice homepage" is crap anyway (because it is not really independent. if SAP implements something strangely on the server side they of course implement it the same way on the client/testing side, so you never find out that in real world scenarios e.g. no client understands the feature X the way SAP implemented it). use any non-SAP-tool to test your SAP webservices, e.g. XML Spy, or SOAPUI.
my 2 cents,
anton -
Com.sap.mw.jco.JCO$Exception starting the J2EE server 620
We are using J2EE 620 pl26, with the latest JCO, but often trying to acces the J2EE services like Mobile Engine Webconsole 21 or the WebEnabled Sapconsole 640 we recive the message:
'Dispatche runningbut no server connected'.
The J2EE dispatcher and server are started at Sap startup. Just after that time the J2EE is working fine, but after some time the J2EE server get down.
We found this message into the J2EE console_logs:
"RFCEngine: Server startup error, stopping "SAPProfile:F:\usr\sap\CAM\SYS\profile\CAM_DVEBMGS00_itmif089" :
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Fri Oct 15 09:58:20 CEST 2004.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 2 seconds.
Could not establish the lcom accepted connection: lcomListenCreate failed with rc 9"
We do not find any Oss notes for that.
Any advise is wellcome.
RegardsHi Mauro,
normally when you apply a new SAP Kernel a frfclib.sar file is delivered. This frfclib file need to be copied to the J2EE directory /os_libs and need to be extracted there. This frfclib version must always match to the SAP Kernel version.
Ciao
tc -
Problem installing the J2EE server on a 6.40 WebAS System
On an AIX server I've installed Oracle 9.2, WebAS Central ABAP instance and
now I'm trying to install the J2EE server. When it gets to phase
"Deployment of JDDI" I get the following error. Does anyone have any
ideas on how to resolve this. Thanks!
Apr 4, 2005 2:17:21 PM Info: Starting deployment
Apr 4, 2005 2:17:21 PM Info: Loading selected archives...
Apr 4, 2005 2:17:21 PM Info: Loading archive '/dvd/igs/J2EE1/J2EE-ENG/JDD/SYNCLOG.SDA'
Apr 4, 2005 2:17:21 PM Info: Selected archives successfully loaded.
Apr 4, 2005 2:17:21 PM Info: Error handling strategy: OnErrorStop
Apr 4, 2005 2:17:21 PM Info: Update strategy: UpdateLowerVersions
Apr 4, 2005 2:17:21 PM Info: Starting to execute deployment action (deploy) for "synclog".
Apr 4, 2005 2:17:24 PM Info: Creating connections to database "DBW".
Apr 4, 2005 2:17:24 PM Info: Creating vendor connection to database.
Apr 4, 2005 2:17:24 PM Error: Creation of vendor connection failed.
Original error message is:
java.sql.SQLException: Io exception: Invalid number format for port number
Stack trace of original Exception or Error is:
java.sql.SQLException: Io exception: Invalid number format for port number
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:334)
at oracle.jdbc.ttc7.TTC7Protocol.handleIOException(TTC7Protocol.java:3649)
at oracle.jdbc.ttc7.TTC7Protocol.logon(TTC7Protocol.java:353)
at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:368)
at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:549)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:349)
at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:149)
at com.sap.sql.connect.OpenSQLDataSourceImpl.createConnection(OpenSQLDataSourceImpl.java:472)
at com.sap.sql.connect.OpenSQLDataSourceImpl.getConnection(OpenSQLDataSourceImpl.java:253)
at com.sap.sdm.serverext.servertype.dbsc.extern.DBSCConnectionManager.createSDMVendorConnection(DBSCConnectionManager.java:214)
at com.sap.sdm.serverext.servertype.dbsc.extern.DBSCConnectionManager.createSDMConnections(DBSCConnectionManager.java:77)
at com.sap.sdm.serverext.servertype.dbsc.ConnectionManagerDecorator.createSDMConnections(ConnectionManagerDecorator.java:73)
at com.sap.sdm.serverext.servertype.dbsc.DatabaseTargetSystem.connect(DatabaseTargetSystem.java:140)
at com.sap.sdm.serverext.servertype.dbsc.DBSCDeploymentActionProcessor.executeAction(DBSCDeploymentActionProcessor.java:115)
at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:58)
at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:181)
at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:51)
at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:84)
at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:61)
at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:78)
at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:88)
at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:74)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:121)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:90)
at com.sap.sdm.control.command.cmds.Deploy.execute(Deploy.java:162)
at com.sap.sdm.control.command.decorator.AssureStandaloneMode.execute(AssureStandaloneMode.java:54)
at com.sap.sdm.control.command.decorator.AssureOneRunningSDMOnly.execute(AssureOneRunningSDMOnly.java:61)
at com.sap.sdm.control.command.decorator.SDMInitializer.execute(SDMInitializer.java:52)
at com.sap.sdm.control.command.decorator.GlobalParamEvaluator.execute(GlobalParamEvaluator.java:60)
at com.sap.sdm.control.command.decorator.AbstractLibDirSetter.execute(AbstractLibDirSetter.java:46)
at com.sap.sdm.control.command.decorator.ExitPostProcessor.execute(ExitPostProcessor.java:48)
at com.sap.sdm.control.command.decorator.CommandNameLogger.execute(CommandNameLogger.java:49)
at com.sap.sdm.control.command.decorator.AdditionalLogFileSetter.execute(AdditionalLogFileSetter.java:65)
at com.sap.sdm.control.command.decorator.AbstractLogDirSetter.execute(AbstractLogDirSetter.java:52)
at com.sap.sdm.control.command.Command.exec(Command.java:42)
at SDM.main(SDM.java:21)
Apr 4, 2005 2:17:24 PM Error: Execution of deployment action for "synclog" aborted: Db connect failed.
Apr 4, 2005 2:17:25 PM Error: Deployment NOT successful for synclog
Apr 4, 2005 2:17:25 PM Error: At least one of the Deployments failed
Apr 4, 2005 2:17:25 PM Info: Summarizing the deployment results:
Apr 4, 2005 2:17:25 PM Error: Aborted: /dvd/igs/J2EE1/J2EE-ENG/JDD/SYNCLOG.SDA
Apr 4, 2005 2:17:25 PM Error: Processing error. Return code: 4Also, I should mention I'm running the 64bit capable SDK for version 1.4.2 for AIX.
Thanks again! -
Jbuilder 6 and the J2EE server.
I love Jbuilder and I have been using the J2EE Server(Through the Forte Ide) to develop a few J2EE applications. Is it possible to develop and deploy J2EE applications using only Jbuilder6 and the J2EE server.
NB: Applications are for educational purposes.I'm presently trying to get the Java Pet Store demo
http://interstagedemo.fs.fujitsu.com:8000/petstore/index.jsp
working in JBuilder 7 Enterprise, and I've made at least some headway (some of the JPS 1.3_01 source files aren't in the right subdirectories- per their package declarations- which I've reported to Sun and which they've promised to fix in v1.3_02). JPS works out-of-the-box with the Cloudscape database that's distributed with J2EE v1.3, but at the moment, I can't figure out how to make the JPS connect to Cloudscape through JBuilder.
Borland has their own J2EE server/container, and in fact I just received their 60-day trial on 2 CDs today ("Borland Solution for Java Trial" $19.90 US including shipping; includes JBuilder 7 Enterprise 30-day trial):
http://shop.borland.com/dr/v2/ec_MAIN.Entry10?V1=396710&PN=1&SP=10023&xid=39696&DSP=&CUR=840&PGRP=0&CACHE_ID=0
BES (Borland Enterprise Server) claims to be well-integrated with JBuilder, so it may be a better bet than trying to use the freebie J2EE server, at least to start off with. -
Error in starting the j2ee server
Hi...... I installed the j2sdkee-1_3_1-win........... I was able to deploy and run some sample web apps but after compiling a java file (tag lib) and setting my classpath (to point to a servlet jar file) I started getting this errors (see below).... Can someone tell me how to go about this? the keystore.jks is definitely existing in my C:\j2sdkee1.3.1\lib\security\ folder.
Thanks in advance!
C:\Documents and Settings\cruzm1>j2ee
Cannot write the seed file for fast startup. The next startup will be slow.
J2EE server listen port: 1050
java.io.FileNotFoundException: C:\j2sdkee1.3.1\lib\security\keystore.jks (The sy
stem cannot find the path specified)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:106)
at java.io.FileInputStream.<init>(FileInputStream.java:66)
at com.sun.enterprise.security.SSLUtils.loadKS(SSLUtils.java:147)
at com.sun.enterprise.security.SSLUtils.initKeyStore(SSLUtils.java:78)
at com.sun.enterprise.iiop.IIOPSSLSocketFactory.init(IIOPSSLSocketFactor
y.java:74)
at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSSLServerSocket(II
OPSSLSocketFactory.java:153)
at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createServerSocket(IIOPS
SLSocketFactory.java:139)
at com.sun.corba.ee.internal.iiop.GIOPImpl.createListener(GIOPImpl.java:
243)
at com.sun.corba.ee.internal.iiop.GIOPImpl.getEndpoint(GIOPImpl.java:205
at com.sun.corba.ee.internal.iiop.GIOPImpl.initEndpoints(GIOPImpl.java:1
40)
at com.sun.corba.ee.internal.POA.POAORB.getServerEndpoint(POAORB.java:49
2)
at com.sun.corba.ee.internal.POA.POAImpl.pre_initialize(POAImpl.java:156
at com.sun.corba.ee.internal.POA.POAImpl.<init>(POAImpl.java:114)
at com.sun.corba.ee.internal.POA.POAORB.makeRootPOA(POAORB.java:114)
at com.sun.corba.ee.internal.POA.POAORB$1.evaluate(POAORB.java:132)
at com.sun.corba.ee.internal.core.Future.evaluate(Future.java:21)
at com.sun.corba.ee.internal.corba.ORB.resolveInitialReference(ORB.java:
2488)
at com.sun.corba.ee.internal.corba.ORB.resolve_initial_references(ORB.ja
va:2423)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:196)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
org.omg.CORBA.INTERNAL: vmcid: SUN minor code: 209 completed: No
at com.sun.corba.ee.internal.iiop.GIOPImpl.createListener(GIOPImpl.java:
256)
at com.sun.corba.ee.internal.iiop.GIOPImpl.getEndpoint(GIOPImpl.java:205
at com.sun.corba.ee.internal.iiop.GIOPImpl.initEndpoints(GIOPImpl.java:1
40)
at com.sun.corba.ee.internal.POA.POAORB.getServerEndpoint(POAORB.java:49
2)
at com.sun.corba.ee.internal.POA.POAImpl.pre_initialize(POAImpl.java:156
at com.sun.corba.ee.internal.POA.POAImpl.<init>(POAImpl.java:114)
at com.sun.corba.ee.internal.POA.POAORB.makeRootPOA(POAORB.java:114)
at com.sun.corba.ee.internal.POA.POAORB$1.evaluate(POAORB.java:132)
at com.sun.corba.ee.internal.core.Future.evaluate(Future.java:21)
at com.sun.corba.ee.internal.corba.ORB.resolveInitialReference(ORB.java:
2488)
at com.sun.corba.ee.internal.corba.ORB.resolve_initial_references(ORB.ja
va:2423)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:196)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
java.lang.RuntimeException: Unable to create ORB. Possible causes include TCP/IP
ports in use by another process
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:206)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
java.lang.RuntimeException: Unable to create ORB. Possible causes include TCP/IP
ports in use by another process
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:206)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
java.lang.RuntimeException: Unable to create ORB. Possible causes include TCP/IP
ports in use by another process
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:346)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
J2EE server reported the following error: Unable to create ORB. Possible causes
include TCP/IP ports in use by another process
Error executing J2EE server ...
C:\Documents and Settings\cruzm1>j2ee
Cannot write the seed file for fast startup. The next startup will be slow.
J2EE server listen port: 1050
java.io.FileNotFoundException: C:\j2sdkee1.3.1\lib\security\keystore.jks (The sy
stem cannot find the path specified)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:106)
at java.io.FileInputStream.<init>(FileInputStream.java:66)
at com.sun.enterprise.security.SSLUtils.loadKS(SSLUtils.java:147)
at com.sun.enterprise.security.SSLUtils.initKeyStore(SSLUtils.java:78)
at com.sun.enterprise.iiop.IIOPSSLSocketFactory.init(IIOPSSLSocketFactor
y.java:74)
at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSSLServerSocket(II
OPSSLSocketFactory.java:153)
at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createServerSocket(IIOPS
SLSocketFactory.java:139)
at com.sun.corba.ee.internal.iiop.GIOPImpl.createListener(GIOPImpl.java:
243)
at com.sun.corba.ee.internal.iiop.GIOPImpl.getEndpoint(GIOPImpl.java:205
at com.sun.corba.ee.internal.iiop.GIOPImpl.initEndpoints(GIOPImpl.java:1
40)
at com.sun.corba.ee.internal.POA.POAORB.getServerEndpoint(POAORB.java:49
2)
at com.sun.corba.ee.internal.POA.POAImpl.pre_initialize(POAImpl.java:156
at com.sun.corba.ee.internal.POA.POAImpl.<init>(POAImpl.java:114)
at com.sun.corba.ee.internal.POA.POAORB.makeRootPOA(POAORB.java:114)
at com.sun.corba.ee.internal.POA.POAORB$1.evaluate(POAORB.java:132)
at com.sun.corba.ee.internal.core.Future.evaluate(Future.java:21)
at com.sun.corba.ee.internal.corba.ORB.resolveInitialReference(ORB.java:
2488)
at com.sun.corba.ee.internal.corba.ORB.resolve_initial_references(ORB.ja
va:2423)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:196)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
org.omg.CORBA.INTERNAL: vmcid: SUN minor code: 209 completed: No
at com.sun.corba.ee.internal.iiop.GIOPImpl.createListener(GIOPImpl.java:
256)
at com.sun.corba.ee.internal.iiop.GIOPImpl.getEndpoint(GIOPImpl.java:205
at com.sun.corba.ee.internal.iiop.GIOPImpl.initEndpoints(GIOPImpl.java:1
40)
at com.sun.corba.ee.internal.POA.POAORB.getServerEndpoint(POAORB.java:49
2)
at com.sun.corba.ee.internal.POA.POAImpl.pre_initialize(POAImpl.java:156
at com.sun.corba.ee.internal.POA.POAImpl.<init>(POAImpl.java:114)
at com.sun.corba.ee.internal.POA.POAORB.makeRootPOA(POAORB.java:114)
at com.sun.corba.ee.internal.POA.POAORB$1.evaluate(POAORB.java:132)
at com.sun.corba.ee.internal.core.Future.evaluate(Future.java:21)
at com.sun.corba.ee.internal.corba.ORB.resolveInitialReference(ORB.java:
2488)
at com.sun.corba.ee.internal.corba.ORB.resolve_initial_references(ORB.ja
va:2423)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:196)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
java.lang.RuntimeException: Unable to create ORB. Possible causes include TCP/IP
ports in use by another process
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:206)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
java.lang.RuntimeException: Unable to create ORB. Possible causes include TCP/IP
ports in use by another process
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:206)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
java.lang.RuntimeException: Unable to create ORB. Possible causes include TCP/IP
ports in use by another process
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:346)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
J2EE server reported the following error: Unable to create ORB. Possible causes
include TCP/IP ports in use by another process
Error executing J2EE server ...
C:\Documents and Settings\cruzm1>deploytool
Starting Deployment tool, version 1.3.1
(Type 'deploytool -help' for command line options.)
Could not connect to localhostI'm not sure the IOException is the real issue. It looks like there may be some other process using one of the ports the SDK is attempting to bind to. Did you try rebooting your machine and restarting the SDK? If there is another process using a port the SDK requires you may need to change the ports used by the SDK. You can find most of the port settings in the config directory in one of the properties files, depending which port you would like to change. Looks like the orb port is you issue so reboot or modify orb.properties.
-
Deploying a WAR to the J2EE Server - Suggestions Plz.
Hi,
I have a WAR file from my previous project, I would like to deploy it to my SAP WAS can some one tell me how I can do it also is there is way to Deploy a JAR file to a Server or to upload it there so all my applications can use it in the future without me having to add it to the Lib folder of my projects, I would appreciate any help.
Best Wishes,
John.Hi John,
Open the source of application.xml in the EAR project and the add the following
<module>
<web>
<web-uri>sampleweb.war</web-uri>
<context-root>sampleweb</context-root>
</web>
</module>
Replace your war file name and context root in the above snippet and add it in your application.xml as follows...
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN"
"http://java.sun.com/dtd/application_1_3.dtd">
<application>
<display-name>sample</display-name>
<description>EAR description</description>
<module>
<web>
<web-uri>sampleweb.war</web-uri>
<context-root>sampleweb</context-root>
</web>
</module>
</application>
Once you do it, your war is referred in ear and u can seperately deploy the war and ear and it will be recognized.
Hope this will solve your problem..
You may reward points if the solution helped..
Thanks and regards
Deepa Jampunathan -
Deploying a jar file into J2EE server
Hello,
I need to deploy a few jar files I need in my jsp pages I deploy into EP 6. I'm using SAP Web AS 6.40. I tried to copy them into F:\usr\sap\DEP\JC00\j2ee\cluster\server1\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\lib folder but after restarting J2EE server, I still have an error for each import I'm doing for the classes contained in my jar files.
I also tried to pu them in PORTALINF/lib folder of my project but it doesn't work.
Does anyone have an idea ?
Thank you !Hi Olivier,
you could try the following approach:
1. Package your JAR files as J2EE Engine libraries and deploy them on it as described here: <a href="http://help.sap.com/saphelp_nw04/helpdata/en/9f/2ade3fc6c6ec06e10000000a1550b0/frameset.htm">Working with J2EE Libraries</a>.
2. Set reference to this library from the application that use them. Depending on your application, refer to the appropriate documentation:
-- reference from a J2EE app -> see <a href="http://help.sap.com/saphelp_nw04/helpdata/en/15/d5d93fe80fed06e10000000a1550b0/frameset.htm">Referencing Libraries in Applications</a>
-- reference from a portal app -> see <a href="http://help.sap.com/saphelp_nw04/helpdata/en/02/788540ae1dbb4de10000000a1550b0/frameset.htm">Referencing Elements</a>
Hope that helps!
Maybe you are looking for
-
Where is "Save As"? (Want to move a project)
iMovie project files are HUGE. I accept that. I wanted to move my project from one disk to another. Somehow, last week, I imported my raw video to my Firewire drive, but the project files stayed in my Movies directory on my system drive. How do I mov
-
Does Ipad adobe reader allow to fill a dynamic xml form created on LiveCycle?
The form was created using LiveCycle Designer ES3 for the purpose of being filled out on the spot at the client and then submitted as email attachment. However, Adobe reader does not seem to be able to open it giving the following error: "Please wait
-
[SOLVED] Kernel 2.6.26.2-1 upgrade, broken DRI with fglrx
Hello, after upgrade from kernel26 (2.6.26-2 -> 2.6.26.2-1) from testing repository I'am without working DRI with fglrx driver. Has anyone similar problem ? If yes, let me known, I will create bugreport. Thanks for cooperation. FlatEric Part of Xorg
-
HTML Help 1.4 - Where?
During the RoboHelp install, a message box popped up informing me that I would need to get HTML Help 1.4 from the MSDN website. So after the install was completed, I went to the MSDN website and looked for HTML Help 1.4. And I found a file that seeme
-
When using my new ipad I am trying to download an app,when I press install it is asking me to fill in 3security questions...when I tap on first one it just stays blank! Can anyone help?