J2EE Containers in 9.0.3.0.0 (Preview 3/25/02) don't handle custom UserManager

I can't see any other place to report this, so I guess I'll do it here.
We've written a custom UserManager that works in Orion 1.5.2 and, of course, Oracle J2EE Containers 1.0.2.2 but it gets stuck in an infinite loop calling the following function.
protected boolean inGroup( String username, String groupname )
I've watched it in the debugger, and the function is appropriately returning true to indicate that the user is a member of the group. The application's principal.xml looks like this:
<principals>
 <groups>
 <group name="admin" />
 </groups>
 <users>
 </users>
</principals>
The users list is taken care of by our custom UserManager, and this same principals.xml works great in older versions.
Any ideas?
Tim

Tim -- You may want to use the products-> Application Server -> J2EE forum in the future for this type of questions.
As for your problem, I have not heard this before but I will see if I can make it fail or not.
Thanks -- Jeff

Similar Messages

JDBInsight 2.1.03 (JDBC/J2EE Profiler) with 2.2 Trace-in-Time Preview

We (JInspired) are currently starting to prepare for the next release of JDBInsight
2.2 which is focused on transaction concurrency issues based on detailed tracing
and timeline analysis. If anyone is interested we have an evaluation download
of JDBInsight 2.1.03 which includes an very early preview of "Trace-in-Trace"
that is the basis for the 2.2 release.
I would appreciate any feedback in terms of feature set and performance load of
the tracing. We hope to have the server side aspect finished this week and for
the remaining weeks our focus is on the production of quality visualizations within
the console.
More Information:
http://www.jinspired.com/products/jdbinsight/downloads/index.html
Regards,
William Louth
JDBInsight Product Architect
JInspired
"Tune and Test with Insight"
http://www.jinspired.com

Seems to work for me.
This is what I did.
- Created a new project
- Added a button
- In the CSS file (resources/stylesheet.css) add the following
.commandButton{
color: red;
font-weight: bold;
}- In the button propertysheet clicked on StyleSheet
property editor and entered "commandButton"
- Refreshed the designer using "refresh" context menu
Now in the designer the button immediatly changed to what specified in the CSS selector class .
Have you refreshed designer using "refresh" context menu (BTW, in the next release this may not be required).
- Winston

Brief introduction of J2EE

un Microsystems, Inc. in 1996 launched a new pure object-oriented programming language, called Java. Java technology has become the software industry appears one of the most important technology, this platform has nothing to do with the emergence of the programming language, immediately set off a revolution in the software industry, the Internet is now the most popular programming language . Java is a way to explain through the implementation of the language, characterized as: a simple, object-oriented, not dependent on the structure of machines, with portability, robustness, security, and provided with a mechanism and the modern network The perfect combination of technology. At present, in accordance with the Sun Microsystems Web site (http://java.sun.com) announced the standards, depending on the Java language applications will be divided into three platforms:
Java 2 Platform Micro Edition as J2ME, Java 2 Platform Micro Edition. For the development of handheld computers, mobile phones and other mobile communications equipment for use on embedded systems.
Java 2 Platform Standard Edition as J2SE, Java 2 Platform Standard Edition. Mainly used for the development of general desktop applications.
Java 2 Platform Enterprise Edition called J2EE, Java 2 Enterprise Edition platform, To be used for rapid design, development, deployment and management of enterprise-class software system.
J2EE is to use Java to develop a set of extended enterprise norms, it provides component-based design, development, deployment and management of enterprise application solutions. J2EE standards must be based on the J2SE platform, which not only consolidated the Standard Edition of the many advantages, For example, "a compiler, run everywhere" cross-platform features, convenient and efficient database technology to provide seamless connectivity JDBC (Java Data Base Connectivity, Java database connectivity), in Internet applications to ensure data integrity of the security model and support multi - Threading technology, At the same time also against Servlet / JSP, EJB, JMS, JTS / JTA, JCAT and XML technology to provide a comprehensive support. J2EE has been able to establish a set of enterprise-class software application development, shorten the product development cycle structure of the standard system.
In fact, J2EE has become the industrial development of enterprise-class standards and mainstream platform. J2EE for the establishment of a high-availability, high scalability, easy maintenance of enterprise-class system provides the perfect mechanism and the framework model. In J2EE to provide the unified development platform, can greatly reduce development costs and the application of multi-storey complex, the need for high-availability, high security and high scalability software services and the lack of funding for businesses, J2EE the middle Integrated framework of the competent and fully meet their requirements. At the same time, J2EE itself with the comprehensive directory services support and a high degree of security mechanisms and efficient performance show, and many other advantages, for the smooth integration of enterprise application systems have played an enormous role.
J2EE-based enterprise applications, without any particular operating system, network environment, the shackles of hardware platforms.Applications can be developed and deployed in the heterogeneous environment, and to ensure that the system of portability. Therefore, as long as the J2EE development of a standardized system can be deployed to various operating system platforms and network platforms. J2EE as a long-term stable performance, enterprise-class applications platform, to protect 7 ? 24 hours of uninterrupted services to meet customers, partners, the needs of enterprises is an ideal platform for the operation of Internet globalization is an inevitable requirement for the development of the objective. J2EE high scalability features in today's "on demand" (IBM Corporation to the end of 2002) the popularity of e-commerce strategies of the times, made an outstanding contribution. J2EE using load-balancing strategy, the system software and hardware resources to maximize utilization and performance, eliminate bottlenecks in the system. Allow the deployment of integrated multiple servers, and can be highly scalable systems, the preservation of existing enterprise IT assets to reduce repetitive investment in the future but also to meet the needs of business applications.
J2EE Technical
In J2EE platforms, including a large number of technology, in order to provide developers with more comprehensive support.
Servlet Technology Servlet Web application development is the foundation. It is entirely in Java language development is the Java platform on the CGI technology. It runs on the server-side J2EE containers, with high efficiency, to dynamically load and dynamically generate Web pages. Servlet Specializes in process control and conduct of business, the expansion of services for enterprise development strategy tailored and flexible.
JSP technology Its essence is still Servlet, only to create two different ways. JSP documents from HTML files, Java and JSP label procedures constitute a fragment. JSP will be the first through the analyzer generates the Servlet source files, and then compile this document Servlet running. JSP Servlet and, with very high operating efficiency.
JNDI technology Java Naming and Directory Interface, as JNDI. J2EE application components are usually located in different physical address of the machine, so the need for a mechanism to facilitate client users to find and use J2EE components and enterprise system resources. In J2EE system, the use of JNDI technical positioning various objects, including EJB objects, database-driven targets, JDBC data source object and connect information, and other objects. JNDI functions for the application to provide a unified interface to complete the standard definition of directory operations, such as through the object properties to find the target and positioning.

Very hard to read. OP needs to work on his grammar. Not especially accurate either.
When, inevitably, people start arriving here and asking "pls send me teh intro 2 jeee" I suggest they read this link instead:
[http://java.sun.com/developer/technicalArticles/J2EE/Intro/|http://java.sun.com/developer/technicalArticles/J2EE/Intro/]
(They won't of course...)

Is it safe to use ThreadLocal objects in a J2EE component?

I've heard that many J2EE containers implement some form of thread pooling.
Depending on how this is implemented, the same session bean or servlet instance could run on a different thread each time a request is made, making ThreadLocal usage unsafe (please, take a look at http://sys-con.com/itsg/virtualcd/Java/archives/0711/goenka/).
But J2EE 1.3 and 1.4 spec doesn't prohibit ThreadLocal usage. So, what is the de facto standard?

You are right, there is no guarantee that a particular thread will be used by a particular ejb or servlet. So threadlocals should not be used. Even if container picks up the same thread to run the ejb, in a highly available/clustered environment, request may land up in different JVMs, so process wide synchronisation won't suffice.
Refer to section #25.1.2 of EJB 2.1 spec where some programming restrictions for EJB are mentioned. You may also refer to In J2EE platform spec where security permissions for different containers are mentioned.
Sahoo

UML (2.0) profile for J2EE/WebLogic

I am currently creating UML diagrams for deployments of various software releases into various environments in an enterprise. These involve some Java applications including WebLogic. I am on the verge of creating my own UML profile for this, in particular for the WebLogic side of things, with JVMs including WebLogic instances modelled as execution environments, etc. I am also keen to drill into J2EE deployment descriptors to visualize crisp interfaces between J2EE components and the services they require from the J2EE containers, which is "pure" J2EE.
I imagine I am not the first to do this, and someone must have created profiles already. I have found an old draft specification for a UML/EJB mapping. I imagine the profile I am looking for would be in a UML/XMI format that I can import into my tool (SparxSystems Enterprise Architect), but even just a graphical specification would be of help.
Does anyone have some pointers to where I should look?
Andreas

You're absolutely right. For some reason orion.jar isn't in that distribution. However there should be an oc4j.jar file in there, which behaves exactly as the orion.jar file would. So, any place in the documentation where it refers to orion.jar, just substitute oc4j.jar.
Ryan

Reposted: websphere J2EE thin client request

Hi,
I posted this question one month ago and the answer I got is the J2EE thin client for Websphere application server will be ready in two weeks, but after checking this site http://otn.oracle.com/products/reports/htdocs/getstart/examples/Tools/index.html
It is still not there. But I saw IIS client already there.
Please let me know if Websphere client will be available or not, so I can tell my boss to change to other reporting tools.
Thanks.
David

Hi David,
You can see we are working on j2ee thin client for various j2ee containers. Yes, we are working on websphere, but we hit few issues that needs to be addressed before posting to otn. Sorry for the delay. We will do our best to get this done as soon as possible.
Thanks,
Oracle Reports Team

Porting a Workshop app to another J2EE server?

Hello all. I'm new to WL Workshop and have been reading abou the required Workshop
Runtime. Is this something that could be ported to another J2EE compliant server?
I noticed the PageFlow Portability Kit for the page flows... but what about the
Runtime engine itself?
Also, does anyone know what is contained in it or how it is deployed. If its as
simple as a jar that could be moved over that would be nice... but I doubt its
as simple as that. thanks!

Blake--
The "Runtime Engine" that you mention is the Workshop controls
runtime. Carl Sjogreen addresses portability in a post in this
newsgroup from 9/24/2003. Instead of rephrasing his comments, I've
pasted them below and suggest the "Application portability" thread as
good reading.
Controls fall into the class of artifacts that can be built using
Workshop but which are not 100% portable today. This includes controls
like the Database Control and EJB Control. Remember, though, that
controls are often abstractions over standard J2EE technologies; in the
case of these controls for example, the underlying technologies are just
JDBC Prepared / Callable Statements and existing EJBs.
The portable version of Page Flows does not support controls, but it
does support all of the J2EE technologies such as JDBC, JNDI, EJB, and
so on.
Hope that helps...
Eddie
::::: Application Portability from 9/24/2003 by Carl Sjogreen
John --
Good question. We're constantly pulled between delivering innovation
and value to our customers and ensuring that the applications we build
are standards based and portable. Here's what we are doing to address this:
1) You can always build 100% standard based applications in Workshop
that are as portable as any other J2EE application. Write Java files,
use EJBgen to create EJBs, etc.
2) Where we innovate, we innovate on top of existing standards. Witness
what we are doing with Pageflows, which is built on top of Struts. As
Web Services standards mature (JSR 109 in particular) we'll move JWS
files to support 109 deployment artifacts.
3) We are aggressively pursuing standardization, portability, and open
source for innovations we introduce. A few proof points:
* The key innovations behind JWS files are being standardized as part of
the Java Community Process in JSR 181. When this standard goes final
(early next year hopefully) you'll be able to take your JWS files to
other platforms.
* We will provide "portability kits". In SP2 (due later this year)
we'll provide a portability kit so you can take any pageflow file and
run it on other J2EE containers. This basically includes a set of stand
alone build tools and the few runtime classes we've added on top of struts.
* We've open sourced key technologies like XMLBeans. XMLBeans is now
being incubated as part of the Apache Software Foundation
(http://xml.apache.org/xmlbeans).
So I think you'll find that while not everything you build in Workshop
is 100% portable today, a lot is, and more will be down the road.
Any questions, please let me know.
Best,
-Carl
Carl Sjogreen
Group Product Manager
WebLogic Workshop
"John Reynolds" <[email protected]> wrote in message
news:[email protected]...
Raj,
Thanks for forwarding this on to your Product Managers.
Application portability is one of the big selling points for Java, so
it would be a shame if Bea did not have runtime licenses for deploying
the workshop runtimes on any J2EE certified app-server. I don't think
my company has any problems in paying for quality software, but they do
have problems when the "Write once, run anywhere" Java pledge is broken
(since that's what sold them on Java vs. .Net in the first place).
Having said that, I really applaud what Bea has done so far. For
example, Bea's donation of XmlBeans to Apache was a truly great thing.
Blake wrote:
Eddie,
The "Weblogic Workshop Internals" document also talks about the "Runtime Engine".
Here is a blurb from the top of the doc: "<contains> a runtime infrastructure
that supports application features; the runtime consists of J2EE components deployed
on WebLogic Server "
Later in the doc they mention some EJB's such as the SynchBean and AsyncBean which
utilize JMS. This is the info I need to provide my client if they decide to port
to another app server. We now know that the webapp is portable... its the J2EE
components that is the final piece of the puzzle. thanks!
-Blake

J2ee.jar causes problems with commons-logging.jar

Hi All -
(JDK 1.5.0_03, commons-logging 1.0.4, latest j2ee.jar, Eclipse 3.1.0 RC3 )
I am developing some components that are to be used within j2ee containers and in standalone mode as well. When I run the software under Tomcat, it works correctly (Tomcat is not using the j2ee.jar that comes with Sun's App server obviously), but when I develop with the j2ee.jar file that comes with Sun's App server, I can't use commons-logging. For example, the code supplied below (a class with only this line in the main method, not using any j2ee features) will fail JUST by having j2ee.jar in my path, but if I take it out of the path, it works fine. I am also on the commons-logging mail list and no one there has been able to solve this issue for me. Again, if I deploy my application to Tomcat, I don't have this problem.
The isolated line that is giving me the issue (and will give the issue even in a non j2ee application that just has this one line) is this:
log= LogFactory.getLog(CommonsLoggingTest.class);
When I run this without j2ee.jar in the path, it works fine. When I run it with j2ee.jar in the path, I get this:
Exception in thread "main" org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: java.lang.NullPointerException (Caused by java.lang.NullPointerException) (Caused by org.apache.commons.logging.LogConfigurationException: java.lang.NullPointerException (Caused by java.lang.NullPointerException))
     at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:543)
     at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:235)
     at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:209)
     at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351)
     at com.redhawk.testing.CommonsLoggingTest.doTest(CommonsLoggingTest.java:27)
     at com.redhawk.testing.CommonsLoggingTest.main(CommonsLoggingTest.java:45)
Caused by: org.apache.commons.logging.LogConfigurationException: java.lang.NullPointerException (Caused by java.lang.NullPointerException)
     at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:397)
     at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:529)
     ... 5 more
Caused by: java.lang.NullPointerException
     at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:374)
     ... 6 more
Anyone have any ideas? Its really annoying to have to take this jar file out of my path every time I want to run a test. I could just start developing against other implementations of the j2ee classes I need (for example, Tomcat's jar files do not give this error) but for various reasons that is also undesirable.
Thanks!
Jason

This problem does not arise with commons-logging 1.0.3.
Any idea what is different in 1.0.4 that would introduce problems when Sun's j2ee.jar is in the path?

How does J2EE SDK provide JNDI DataSource ?

Still new to J2EE and working my way thorugh Wrox press "professional java server programming". Im using the deploy tool and im wondering how does J2EE provide JNDI names for a DataSource ? Im somewhat familiar with JNDI and I thought you had to use a directory service such as OpenLDAP to use JNDI.
my questions then are:
(1) What kinds of things can you do with JNDI without using a directory service ?
(2) How does the J2EE SDK physically store references to a DataSource without using a directory service. In otherwords, how does the J2EE server provide for using JNDI names for a DataSource and is this a typical feature of J2EE containers ?

i wish someone would answer this. i curious myself about these exact same things.

J2EE Server unable to start

Hi,
first of all, i'm really new to SAP NW. Today I started installing the Sneak Preview of SAP NetWeaver 2004 7.0 SP9
JavaStack on my Virtual Machine (Windows2003Server, J2SE 1.4.2.09) and it worked fine.
After installation I started the SAP Management Console and tried to start my first and only instance J2E.
In J2E i got 3 instances, the DB, Instance 0 and Instance 1.
After start:
DB is working (blue)
Instance 0 is working (green)
Instance 1 failed while starting (turned from yellow to red)
Process List shows:
jcontrol.EXE | J2EE Server | License check failed
igswd.EXE | IGS Watchdog | Running
Problem:
I don't know why the License check failed!
I downloaded the Software about mid of february, its been about 3 month ago and I ran the install for the first time
today. What might be the problem? I searched the SDN-History for similar problems, but i did not find an adequate
answer. I checked dev_jcontrol and the "license check failed" entry is in the file. So I'm wondering why my license
check fails, although I'm installing the software for the first time!
An info i got from the start.htm is:
The license of this Trial Version is for evaluation purposes only and does not allow commercial use.
The license is valid for 90 days and cannot be extended (View license). If the license has expired, the
entry license check failed will appear in the trace file <INST_DRIVE>:\usr\sap\J2E\JC01\work\dev_jcontrol,
if the instance name remains unchanged during the installation process. Please refer to SAP Developer
Network for more information about commercially available editions of SAP Web Application Server and SAP NetWeaver Developer Studio.
May one find some more information in that file?
I realised that a package is missing, but read in the forum, that this is not a obligatory package (?)
JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\J2E\JC01\exe\jvmx.jar
trc file: "D:\usr\sap\J2E\JC01\work\dev_jcontrol", trc level: 1, release: "700"
node name : jcontrol
pid : 2644
system name : J2E
system nr. : 01
started at : Wed May 07 13:28:11 2008
arguments :
 arg[00] : D:\usr\sap\J2E\JC01\exe\jcontrol.EXE
 arg[01] : pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
[Thr 1352] Wed May 07 13:28:11 2008
[Thr 1352] *** WARNING => INFO: Unknown property [instance.system.id=1] [jstartxx.c 841]
[Thr 1352] *** WARNING => INFO: Unknown property [instance.en.host=sope75] [jstartxx.c 841]
[Thr 1352] *** WARNING => INFO: Unknown property [instance.box.number=J2EJC01sope75] [jstartxx.c 841]
[Thr 1352] *** WARNING => INFO: Unknown property [instance.en.port=3200] [jstartxx.c 841]
JStartupReadInstanceProperties: read instance properties [D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties;D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties]
-> ms host : sope75
-> ms port : 3900
-> OS libs : D:\usr\sap\J2E\JC01\j2ee\os_libs
-> Admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Used property files
-> files [00] : D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
-> files [01] : D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties
Instance properties
-> ms host : sope75
-> ms port : 3900
-> os libs : D:\usr\sap\J2E\JC01\j2ee\os_libs
-> admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Bootstrap nodes
-> [00] bootstrap_ID18439050 : D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
-> [01] bootstrap_ID18439000 : D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
-> [02] bootstrap : D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
Worker nodes
-> [00] ID18439050 : D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
-> [01] ID18439000 : D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
-> [02] sdm : D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties
[Thr 1352] [Node: bootstrap] java home is set by profile parameter
 Java Home: C:\Programme\Java\j2sdk1.4.2_09
[Thr 1352] Wed May 07 13:28:19 2008
[Thr 1352] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\J2E\JC01\exe\jvmx.jar
JStartupIReadSection: read node properties [bootstrap]
-> node name : bootstrap
-> node type : bootstrap
-> node execute : yes
-> java path : C:\Programme\Java\j2sdk1.4.2_09
-> java parameters : -Djco.jarm=1 -Djco.jarm=1
-> java vm version : 1.4.2_09-b05
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 512M
-> root path : D:\usr\sap\J2E\JC01\j2ee\cluster
-> class path : .\bootstrap\launcher.jar
-> OS libs path : D:\usr\sap\J2E\JC01\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 : D:\usr\sap\J2E\JC01\exe\jstartup.jar;D:\usr\sap\J2E\JC01\exe\jvmx.jar
-> parameters : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID0184390
-> debuggable : yes
-> debug mode : no
-> debug port : 60000
-> shutdown timeout : 120000
[Thr 1352] JControlExecuteBootstrap: execute bootstrap process [bootstrap]
[Thr 1352] [Node: bootstrap] java home is set by profile parameter
 Java Home: C:\Programme\Java\j2sdk1.4.2_09
[Thr 1352] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\J2E\JC01\exe\jvmx.jar
JStartupIReadSection: read node properties [bootstrap]
-> node name : bootstrap
-> node type : bootstrap
-> node execute : yes
-> java path : C:\Programme\Java\j2sdk1.4.2_09
-> java parameters : -Djco.jarm=1 -Djco.jarm=1
-> java vm version : 1.4.2_09-b05
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 512M
-> root path : D:\usr\sap\J2E\JC01\j2ee\cluster
-> class path : .\bootstrap\launcher.jar
-> OS libs path : D:\usr\sap\J2E\JC01\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 : D:\usr\sap\J2E\JC01\exe\jstartup.jar;D:\usr\sap\J2E\JC01\exe\jvmx.jar
-> parameters : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID0184390
-> debuggable : yes
-> debug mode : no
-> debug port : 60000
-> shutdown timeout : 120000
JControlStartJLaunch: program = D:\usr\sap\J2E\JC01\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\J2E\JC01\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
-> arg[02] = -DSAPINFO=J2E_01_bootstrap
-> arg[03] = -nodeId=-1
-> arg[04] = -file=D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_2644
-> arg[06] = -nodeName=bootstrap
-> arg[07] = -jvmOutFile=D:\usr\sap\J2E\JC01\work\jvm_bootstrap.out
-> arg[08] = -stdOutFile=D:\usr\sap\J2E\JC01\work\std_bootstrap.out
-> arg[09] = -locOutFile=D:\usr\sap\J2E\JC01\work\dev_bootstrap
-> arg[10] = -mode=BOOTSTRAP
-> arg[11] = pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
-> lib path = PATH=C:\Programme\Java\j2sdk1.4.2_09\jre\bin\server;C:\Programme\Java\j2sdk1.4.2_09\jre\bin;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;c:\orabase\1020\bin;C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;c:\prgramme\sharepoint portal server\bin;C:\Programme\Gemeinsame Dateien\Microsoft Shared\web server extensions\60\BIN;C:\Programme\Microsoft SQL Server\80\Tools\Binn\;c:\Programme\Java\jdk1.5.0_13\bin;D:\usr\sap\J2E\SYS\exe\uc\NTI386
-> exe path = PATH=C:\Programme\Java\j2sdk1.4.2_09\bin;D:\usr\sap\J2E\JC01\j2ee\os_libs;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;c:\orabase\1020\bin;C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;c:\prgramme\sharepoint portal server\bin;C:\Programme\Gemeinsame Dateien\Microsoft Shared\web server extensions\60\BIN;C:\Programme\Microsoft SQL Server\80\Tools\Binn\;c:\Programme\Java\jdk1.5.0_13\bin;D:\usr\sap\J2E\SYS\exe\uc\NTI386
[Thr 1352] Wed May 07 13:30:12 2008
[Thr 1352] JControlExecuteBootstrap: read instance values after global bootstrap
[Thr 1352] *** WARNING => INFO: Unknown property [instance.box.number=J2EJC01sope75] [jstartxx.c 841]
[Thr 1352] *** WARNING => INFO: Unknown property [instance.en.host=sope75] [jstartxx.c 841]
[Thr 1352] *** WARNING => INFO: Unknown property [instance.en.port=3200] [jstartxx.c 841]
[Thr 1352] *** WARNING => INFO: Unknown property [instance.system.id=1] [jstartxx.c 841]
JStartupReadInstanceProperties: read instance properties [D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties;D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties]
-> ms host : sope75
-> ms port : 3900
-> OS libs : D:\usr\sap\J2E\JC01\j2ee\os_libs
-> Admin URL :
-> run mode : normal
-> run action : NONE
-> enabled : yes
[Thr 1352] JControlExecuteBootstrap: enumerate the nodes after global bootstrap
Used property files
-> files [00] : D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
-> files [01] : D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties
Instance properties
-> ms host : sope75
-> ms port : 3900
-> os libs : D:\usr\sap\J2E\JC01\j2ee\os_libs
-> admin URL :
-> run mode : normal
-> run action : NONE
-> enabled : yes
Bootstrap nodes
-> [00] bootstrap : D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
-> [01] bootstrap_ID18439000 : D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
-> [02] bootstrap_ID18439050 : D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
Worker nodes
-> [00] ID18439000 : D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
-> [01] ID18439050 : D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
-> [02] sdm : D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties
[Thr 1352] JControlExecuteBootstrap: execute bootstrap process [bootstrap_ID18439000]
[Thr 1352] [Node: dispatcher bootstrap] java home is set by profile parameter
 Java Home: C:\Programme\Java\j2sdk1.4.2_09
[Thr 1352] Wed May 07 13:30:16 2008
[Thr 1352] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\J2E\JC01\exe\jvmx.jar
JStartupIReadSection: read node properties [bootstrap_ID18439000]
-> node name : dispatcher bootstrap
-> node type : bootstrap
-> node execute : yes
-> jlaunch parameters :
-> java path : C:\Programme\Java\j2sdk1.4.2_09
-> java parameters : -Djco.jarm=1
-> java vm version : 1.4.2_09-b05
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 256M
-> root path : D:\usr\sap\J2E\JC01\j2ee\cluster
-> class path : .\bootstrap\launcher.jar
-> OS libs path : D:\usr\sap\J2E\JC01\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 : D:\usr\sap\J2E\JC01\exe\jstartup.jar;D:\usr\sap\J2E\JC01\exe\jvmx.jar
-> parameters : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID018439000
-> debuggable : yes
-> debug mode : no
-> debug port : 60000
-> shutdown timeout : 120000
JControlStartJLaunch: program = D:\usr\sap\J2E\JC01\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\J2E\JC01\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
-> arg[02] = -DSAPINFO=J2E_01_bootstrap
-> arg[03] = -nodeId=-1
-> arg[04] = -file=D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_2644
-> arg[06] = -nodeName=bootstrap_ID18439000
-> arg[07] = -jvmOutFile=D:\usr\sap\J2E\JC01\work\jvm_bootstrap_ID18439000.out
-> arg[08] = -stdOutFile=D:\usr\sap\J2E\JC01\work\std_bootstrap_ID18439000.out
-> arg[09] = -locOutFile=D:\usr\sap\J2E\JC01\work\dev_bootstrap_ID18439000
-> arg[10] = -mode=BOOTSTRAP
-> arg[11] = pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
-> lib path = PATH=C:\Programme\Java\j2sdk1.4.2_09\jre\bin\server;C:\Programme\Java\j2sdk1.4.2_09\jre\bin;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;c:\orabase\1020\bin;C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;c:\prgramme\sharepoint portal server\bin;C:\Programme\Gemeinsame Dateien\Microsoft Shared\web server extensions\60\BIN;C:\Programme\Microsoft SQL Server\80\Tools\Binn\;c:\Programme\Java\jdk1.5.0_13\bin;D:\usr\sap\J2E\SYS\exe\uc\NTI386
-> exe path = PATH=C:\Programme\Java\j2sdk1.4.2_09\bin;D:\usr\sap\J2E\JC01\j2ee\os_libs;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;c:\orabase\1020\bin;C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;c:\prgramme\sharepoint portal server\bin;C:\Programme\Gemeinsame Dateien\Microsoft Shared\web server extensions\60\BIN;C:\Programme\Microsoft SQL Server\80\Tools\Binn\;c:\Programme\Java\jdk1.5.0_13\bin;D:\usr\sap\J2E\SYS\exe\uc\NTI386
[Thr 1352] Wed May 07 13:31:04 2008
[Thr 1352] JControlExecuteBootstrap: execute bootstrap process [bootstrap_ID18439050]
[Thr 1352] [Node: server0 bootstrap] java home is set by profile parameter
 Java Home: C:\Programme\Java\j2sdk1.4.2_09
[Thr 1352] Wed May 07 13:31:06 2008
[Thr 1352] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\J2E\JC01\exe\jvmx.jar
JStartupIReadSection: read node properties [bootstrap_ID18439050]
-> node name : server0 bootstrap
-> node type : bootstrap
-> node execute : yes
-> jlaunch parameters :
-> java path : C:\Programme\Java\j2sdk1.4.2_09
-> java parameters : -Djco.jarm=1
-> java vm version : 1.4.2_09-b05
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 256M
-> root path : D:\usr\sap\J2E\JC01\j2ee\cluster
-> class path : .\bootstrap\launcher.jar
-> OS libs path : D:\usr\sap\J2E\JC01\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 : D:\usr\sap\J2E\JC01\exe\jstartup.jar;D:\usr\sap\J2E\JC01\exe\jvmx.jar
-> parameters : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID018439050
-> debuggable : yes
-> debug mode : no
-> debug port : 60000
-> shutdown timeout : 120000
JControlStartJLaunch: program = D:\usr\sap\J2E\JC01\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\J2E\JC01\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
-> arg[02] = -DSAPINFO=J2E_01_bootstrap
-> arg[03] = -nodeId=-1
-> arg[04] = -file=D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_2644
-> arg[06] = -nodeName=bootstrap_ID18439050
-> arg[07] = -jvmOutFile=D:\usr\sap\J2E\JC01\work\jvm_bootstrap_ID18439050.out
-> arg[08] = -stdOutFile=D:\usr\sap\J2E\JC01\work\std_bootstrap_ID18439050.out
-> arg[09] = -locOutFile=D:\usr\sap\J2E\JC01\work\dev_bootstrap_ID18439050
-> arg[10] = -mode=BOOTSTRAP
-> arg[11] = pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
-> lib path = PATH=C:\Programme\Java\j2sdk1.4.2_09\jre\bin\server;C:\Programme\Java\j2sdk1.4.2_09\jre\bin;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;c:\orabase\1020\bin;C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;c:\prgramme\sharepoint portal server\bin;C:\Programme\Gemeinsame Dateien\Microsoft Shared\web server extensions\60\BIN;C:\Programme\Microsoft SQL Server\80\Tools\Binn\;c:\Programme\Java\jdk1.5.0_13\bin;D:\usr\sap\J2E\SYS\exe\uc\NTI386
-> exe path = PATH=C:\Programme\Java\j2sdk1.4.2_09\bin;D:\usr\sap\J2E\JC01\j2ee\os_libs;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;c:\orabase\1020\bin;C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;c:\prgramme\sharepoint portal server\bin;C:\Programme\Gemeinsame Dateien\Microsoft Shared\web server extensions\60\BIN;C:\Programme\Microsoft SQL Server\80\Tools\Binn\;c:\Programme\Java\jdk1.5.0_13\bin;D:\usr\sap\J2E\SYS\exe\uc\NTI386
[Thr 1352] Wed May 07 13:33:15 2008
[Thr 1352] JControlIBuildProcessList: Maximum error count is set to 4
[Thr 1308] JControlRequestFunc: Thread 1308 started as listener thread for np messages.
[Thr 1352] [Node: dispatcher] java home is set by profile parameter
 Java Home: C:\Programme\Java\j2sdk1.4.2_09
[Thr 1352] Wed May 07 13:33:17 2008
[Thr 1352] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\J2E\JC01\exe\jvmx.jar
JStartupIReadSection: read node properties [ID18439000]
-> node name : dispatcher
-> node type : dispatcher
-> node execute : yes
-> jlaunch parameters :
-> java path : C:\Programme\Java\j2sdk1.4.2_09
-> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -verbose:gc -verbose:gc -XX:NewSize=28m -XX:MaxNewSize=28m -XX:+DisableExplicitGC
-> java vm version : 1.4.2_09-b05
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 170M
-> init heap size : 170M
-> root path : D:\usr\sap\J2E\JC01\j2ee\cluster\dispatcher
-> class path : .\bin\boot\boot.jar;.\bin\system\bytecode.jar;.
-> OS libs path : D:\usr\sap\J2E\JC01\j2ee\os_libs
-> main class : com.sap.engine.boot.Start
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : D:\usr\sap\J2E\JC01\exe\jstartup.jar;D:\usr\sap\J2E\JC01\exe\jvmx.jar
-> parameters :
-> debuggable : no
-> debug mode : no
-> debug port : 60000
-> shutdown timeout : 120000
[Thr 1352] [Node: server0] java home is set by profile parameter
 Java Home: C:\Programme\Java\j2sdk1.4.2_09
[Thr 1352] Wed May 07 13:33:18 2008
[Thr 1352] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\J2E\JC01\exe\jvmx.jar
JStartupIReadSection: read node properties [ID18439050]
-> node name : server0
-> node type : server
-> node execute : yes
-> jlaunch parameters :
-> java path : C:\Programme\Java\j2sdk1.4.2_09
-> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -verbose:gc -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -XX:NewSize=145m -XX:MaxNewSize=145m -XX:MaxPermSize=192m -XX:PermSize=192m -XX:+DisableExplicitGC -XX:+UseParNewGC -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -XX:SoftRefLRUPolicyMSPerMB=1 -verbose:gc
-> java vm version : 1.4.2_09-b05
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 874M
-> init heap size : 874M
-> root path : D:\usr\sap\J2E\JC01\j2ee\cluster\server0
-> class path : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path : D:\usr\sap\J2E\JC01\j2ee\os_libs
-> main class : com.sap.engine.boot.Start
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : D:\usr\sap\J2E\JC01\exe\jstartup.jar;D:\usr\sap\J2E\JC01\exe\jvmx.jar
-> parameters :
-> debuggable : yes
-> debug mode : yes
-> debug port : 50121
-> shutdown timeout : 120000
[Thr 1352] INFO: Invalid property value [Debbugable=yes]
[Thr 1352] [Node: SDM] java home is set by profile parameter
 Java Home: C:\Programme\Java\j2sdk1.4.2_09
[Thr 1352] Wed May 07 13:33:19 2008
[Thr 1352] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\J2E\JC01\exe\jvmx.jar
JStartupIReadSection: read node properties [sdm]
-> node name : SDM
-> node type : sdm
-> node execute : yes
-> java path : C:\Programme\Java\j2sdk1.4.2_09
-> java parameters :
-> java vm version : 1.4.2_09-b05
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 256M
-> root path : D:\usr\sap\J2E\JC01\SDM\program
-> class path : D:\usr\sap\J2E\JC01\SDM\program\bin\SDM.jar
-> OS libs path : D:\usr\sap\J2E\JC01\j2ee\os_libs
-> main class : SDMInternal
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : D:\usr\sap\J2E\JC01\exe\jstartup.jar;D:\usr\sap\J2E\JC01\exe\jvmx.jar
-> shutdown class : com.sap.sdm.jstartup.shutdown.InternalShutDown
-> parameters : server sdmhome=D:\usr\sap\J2E\JC01\SDM\program
-> debuggable : yes
-> debug mode : no
-> debug port : 60000
-> shutdown timeout : 120000
[Thr 1352] JControlMSConnect: attached to message server (sope75/3900)
JControlStartJLaunch: program = D:\usr\sap\J2E\JC01\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\J2E\JC01\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
-> arg[02] = -DSAPINFO=J2E_01_dispatcher
-> arg[03] = -nodeId=0
-> arg[04] = -file=D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_2644
-> arg[06] = -nodeName=ID18439000
-> arg[07] = -jvmOutFile=D:\usr\sap\J2E\JC01\work\jvm_dispatcher.out
-> arg[08] = -stdOutFile=D:\usr\sap\J2E\JC01\work\std_dispatcher.out
-> arg[09] = -locOutFile=D:\usr\sap\J2E\JC01\work\dev_dispatcher
-> arg[10] = -mode=JCONTROL
-> arg[11] = pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
-> lib path = PATH=C:\Programme\Java\j2sdk1.4.2_09\jre\bin\server;C:\Programme\Java\j2sdk1.4.2_09\jre\bin;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;c:\orabase\1020\bin;C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;c:\prgramme\sharepoint portal server\bin;C:\Programme\Gemeinsame Dateien\Microsoft Shared\web server extensions\60\BIN;C:\Programme\Microsoft SQL Server\80\Tools\Binn\;c:\Programme\Java\jdk1.5.0_13\bin;D:\usr\sap\J2E\SYS\exe\uc\NTI386
-> exe path = PATH=C:\Programme\Java\j2sdk1.4.2_09\bin;D:\usr\sap\J2E\JC01\j2ee\os_libs;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;c:\orabase\1020\bin;C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;c:\prgramme\sharepoint portal server\bin;C:\Programme\Gemeinsame Dateien\Microsoft Shared\web server extensions\60\BIN;C:\Programme\Microsoft SQL Server\80\Tools\Binn\;c:\Programme\Java\jdk1.5.0_13\bin;D:\usr\sap\J2E\SYS\exe\uc\NTI386
[Thr 3376] JControlMSMessageFunc: Thread 3376 started as listener thread for ms messages.
[Thr 1352] JControlICheckProcessList: process dispatcher started (PID:724)
JControlStartJLaunch: program = D:\usr\sap\J2E\JC01\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\J2E\JC01\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
-> arg[02] = -DSAPINFO=J2E_01_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_2644
-> arg[06] = -nodeName=ID18439050
-> arg[07] = -jvmOutFile=D:\usr\sap\J2E\JC01\work\jvm_server0.out
-> arg[08] = -stdOutFile=D:\usr\sap\J2E\JC01\work\std_server0.out
-> arg[09] = -locOutFile=D:\usr\sap\J2E\JC01\work\dev_server0
-> arg[10] = -mode=JCONTROL
-> arg[11] = -debugMode=yes
-> arg[12] = pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
-> lib path = PATH=C:\Programme\Java\j2sdk1.4.2_09\jre\bin\server;C:\Programme\Java\j2sdk1.4.2_09\jre\bin;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;c:\orabase\1020\bin;C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;c:\prgramme\sharepoint portal server\bin;C:\Programme\Gemeinsame Dateien\Microsoft Shared\web server extensions\60\BIN;C:\Programme\Microsoft SQL Server\80\Tools\Binn\;c:\Programme\Java\jdk1.5.0_13\bin;D:\usr\sap\J2E\SYS\exe\uc\NTI386
-> exe path = PATH=C:\Programme\Java\j2sdk1.4.2_09\bin;D:\usr\sap\J2E\JC01\j2ee\os_libs;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;c:\orabase\1020\bin;C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;c:\prgramme\sharepoint portal server\bin;C:\Programme\Gemeinsame Dateien\Microsoft Shared\web server extensions\60\BIN;C:\Programme\Microsoft SQL Server\80\Tools\Binn\;c:\Programme\Java\jdk1.5.0_13\bin;D:\usr\sap\J2E\SYS\exe\uc\NTI386
[Thr 1352] JControlICheckProcessList: process server0 started (PID:2276)
JControlStartJLaunch: program = D:\usr\sap\J2E\JC01\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\J2E\JC01\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
-> arg[02] = -DSAPINFO=J2E_01_sdm
-> arg[03] = -nodeId=2
-> arg[04] = -file=D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_2644
-> arg[06] = -nodeName=sdm
-> arg[07] = -jvmOutFile=D:\usr\sap\J2E\JC01\work\jvm_sdm.out
-> arg[08] = -stdOutFile=D:\usr\sap\J2E\JC01\work\std_sdm.out
-> arg[09] = -locOutFile=D:\usr\sap\J2E\JC01\work\dev_sdm
-> arg[10] = -mode=JCONTROL
-> arg[11] = pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
-> lib path = PATH=C:\Programme\Java\j2sdk1.4.2_09\jre\bin\server;C:\Programme\Java\j2sdk1.4.2_09\jre\bin;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;c:\orabase\1020\bin;C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;c:\prgramme\sharepoint portal server\bin;C:\Programme\Gemeinsame Dateien\Microsoft Shared\web server extensions\60\BIN;C:\Programme\Microsoft SQL Server\80\Tools\Binn\;c:\Programme\Java\jdk1.5.0_13\bin;D:\usr\sap\J2E\SYS\exe\uc\NTI386
-> exe path = PATH=C:\Programme\Java\j2sdk1.4.2_09\bin;D:\usr\sap\J2E\JC01\j2ee\os_libs;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;c:\orabase\1020\bin;C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;c:\prgramme\sharepoint portal server\bin;C:\Programme\Gemeinsame Dateien\Microsoft Shared\web server extensions\60\BIN;C:\Programme\Microsoft SQL Server\80\Tools\Binn\;c:\Programme\Java\jdk1.5.0_13\bin;D:\usr\sap\J2E\SYS\exe\uc\NTI386
[Thr 1352] JControlICheckProcessList: process SDM started (PID:3312)
[Thr 1352] JControlMSSendLogon: delete SDM logon information (rc=0)
[Thr 3376] Wed May 07 13:33:47 2008
[Thr 3376] JControlIEnableProcesses: disable processes of type (Exclude:0) [SDM Server]
[Thr 3376] JControlIDisableProcess: disable process SDM
[Thr 3376] JControlIProcessSoftKill: soft kill of process SDM (pid:3312)
[Thr 1352] Wed May 07 13:33:52 2008
[Thr 1352] JControlICheckProcessList: process SDM (pid:3312) died (STOPPING)
[Thr 1352] JControlIResetProcess: reset process SDM
[Thr 1352] Wed May 07 14:20:27 2008
[Thr 1352] JControlICheckProcessList: process dispatcher (pid:724) died (RUN-FLAG)
[Thr 1352] JControlIResetProcess: reset process dispatcher
*[Thr 1352] JControlICheckProcessList: license check failed*
*[Thr 1352] JControlMainLoop: license check failed -> shutdown the instance*
[Thr 1352] JControlProcessMessage: received <shutdown without restart> command
[Thr 1352] JControlIStopInstance: shutting down (command: 0)
[Thr 1352] JControlIProcessSoftKill: soft kill of process server0 (pid:2276)
[Thr 1352] Wed May 07 14:22:33 2008
[Thr 1352] *** ERROR => Can't terminate process (pid = 2276,handle = 00000678,err = 5) [jstartnt.c 690]
[Thr 1352] *** ERROR => Critical error, can't terminate process server0 (pid:2276) (rc=-2) [jcntrxxi.c 407]
[Thr 1352] JControlICheckProcessList: process server0 (pid:2276) died (STOPPING)
[Thr 1352] JControlIResetProcess: reset process server0
[Thr 1352] JControlCloseProgram: started (exitcode = 0)
[Thr 3376] JControlMSMessageFunc: shutdown -> terminate message listener
[Thr 3376] JControlMSMessageFunc: leave listener thread
[Thr 1352] Wed May 07 14:22:34 2008
[Thr 1352] JControlCloseProgram: good bye... (exitcode = -11111)
Regards
RandomStudent
Edited by: RandomStudent on May 7, 2008 4:45 PM
Edited by: RandomStudent on May 7, 2008 4:47 PM

Hello Vijith, thanks for your answer.
Installed a Sneak Preview of SAP NetWeaver 7.1 CE on Monday(5th May), but it failed.
Deinstalled the 7.1 CE Software on Tuesday (6th May).
Installed Sneak Preview of SAP Netweaver (2004s) 7.0 SP9 on Wednesday (7th May) and it was installed correctly, but i got the problem with the license check.
So the Options are:
Change the date on OS before starting the Software
or
Deinstalling the Software and installing SAP Netweaver (2004s) 7.0 SP9 SR 3 (which i downloaded this night). But i think i have to get the registry clean then. Are there Tools to clean the registry from all SAP entries?

Installation of J2EE Adapter Engine with DB on different host

Hello all,
I don't know if this is the right thread, but hopefully it is.
I have got following assignment:
I have to install NW70 PI/XI J2EE Adapter Engine. The trouble is, that due to a CI and DB hosts politics it's necessary to have database on different host than the central instance is.
But unfortunatelly the "SAPINST" program and its choice of J2EE Adapter Engine installation doesn't offer the possibility to install the product (J2EE AE) as a distributed system. SAPINST simply installs J2EE AE on one host including database. I've not succeeded the find a work-around.
I got two ideas, but I would like to confirm them:
1) Instal full SAP Java AS as a distributed system. After proper installation and patching I would use a SDM tool and deploy all necessary components to get a J2EE Adapter Engine "like" system. The only problem is that I don't know exact difference between normal SAP Java AS and SAP J2EE Adapter Engine and I'm not sure where could I get all necessary .SAR files.
2) Make a installation of SAP J2EE Adapter Engine as SAPINST allows. After installation and pathing, shutdown the system and move database to desired host, change all settings and start SAP J2EE AE as a distributed system. Only thing I'm not sure about is, if the J2EE AE would run in such a landscape.
Could anyone help me to get out of this deadend ?
Thank you for your comments in advance. Rewards points granted.
Tomas

Hi Jitendra,
thank you for your effort.
Maybe the question is more to Oracle forum part, because I don't think, that I would be able to do the installation as I described in point 1) (distributed JAVA AS and manuall deploying of AE components).
Probably the SAPINST is built up in this way, because in most cases it's needed to install J2EE AE on side of the other integrated system and there is one special machine dedicated to it.
If this is true and J2EE AE is really "normal JAVA AS" with some more functionality, I think the installation can be done as I described in point 2) - to install the J2EE AE locally, then shut it down and move the database to different host as required.
Anybody with different idea ?
Thank you
Regards
Tomas

How to access j2ee servlet directly?

Hi All,
I have a question about Doc 333862.1
My customer wants to follow test case in the CAUSE section.
He wants to call SimpleServlet with bellow URL.
http://hostname:port/j2ee/servlet/SimpleServlet
When I execute it in our test instance, I can't access j2ee servlet directly and faced bellow HTTP 403 Forbidden warning.
"You don't have permission to access /j2ee on this server."
How to access the SimpleServlet?
If you have any solution or advice, please give me the feedback freely.
Regards,

how to create a new project of type J2EE -> EJB Module Project.
First of all u need to have NWDS.
There go to File -> New -> Project -> Select J2EE -> Select EJB Module Project
any prerequisites required to create this apart from the java gui
None. U may create the project here in NWDS and can deploy on XI server.
all in all i want to find how to access J2EE explorer.
J2EE Explorer can be seen under Windows -> Show View -> J2EE Explorer
Regards,
Prateek

J2EE Proxy client

I need to call an external webservice from oracle db... but this web service does not support "SOAP with attachments" and its specification says that we have to develop a J2EE proxy client to access this web service, this still could be done in a stored procedure?, I know that with Jdeveloper I can generate a 'web service stub/skeleton' but how make this stub accesible from oracle with PL/SQL? is this possible?
thanks in advance

I feel following links will help...
http://www.oracle.com/technology/tech/webservices/htdocs/samples/dbwebservice/DBWebServices_PLSQL.html
http://www.oracle-base.com/articles/9i/ConsumingWebServices9i.php

Deploying a custom login module to the J2EE engine

I have developed a custom login module, and want to deploy it to the SAP j2ee engine. How should I go about this ? I tried packaging it as a jar and then using the deploytool, went into user management to register the module, but when the module was invoked I got an error in the log saying "Cannot load a login module".
The way I currently deploy it is packaged with the Example Calculator, and this works. I just add my 2 java files into the web module (in com.sap.examples.calculator.beans) and it gets packaged in the war file.
Can anyone help with the "proper" way of deploying my module ?
Thanks in advance

Hi Brad,
>
> What I'm actually trying to do is NOT deploy my
> custom login module with an application. But rather
> deploy the jar file as a library to the J2EE engine,
> so that any application can use it by configuring it
> in their login stacks. I'm still not totally clear
> whether this is possible or not.
Once again - It is possible to deploy the login module as a library to the J2EE Engine; furthermore, this is the PREFERRED way to use login modules!
>
> What I have currently done:
>
> 1. developed custom login module packaged as a jar in
> NW studio (2 class files)
>
> 2. Using deploytool I deploy the jar as a library to
> the j2ee engine. This works and the library shows up
> under the libraries section.
>
> 3. Register the login module in the user
> management->manage security stores section. I'm
> unsure if this works properly. Do I just provide the
> full path to the required class ? For example
> "com.example.myloginmodule.LoginModule"
> I have a suspicion that my error of "cannot load a
> login module" stems from here.
>
> 4. I have then followed your step and added a
> reference to the libray (Hard reference) and this
> seems ok.
>
Sorry, Brad, I've made a mistake here. You need to set a reference from the Security Provider Service to the library that contains the login module (not from the application). To do that at runtime, you'll have to use the Configuration Adapter service on the J2EE Engine. For a description of the procedure, see this page in the documentation: http://help.sap.com/saphelp_nw04/helpdata/en/dd/1e3a3e5069eb6ce10000000a114084/frameset.htm
You need to provide additional entry of the following type in the security-provider.xml file:
<reference type="library" strength="weak">
Your-library-name-here
</reference>
Regards,
Ivo.
Message was edited by: Ivaylo Ivanov

Zones or Containers Live Upgrade Solaris10 Update 8

Good Day,
I am running my Solaris OS in a ZFS root pool. My containers/zones are running in their own ZPOOLS. They are not part of the root pool.
How can I get Live Upgrade to not make snapshopts of my running containers/zones?
To shut the containers down and detach them is not an option.
Many Thanks,
Gilbert

Our client has a strange request :-)
The idea is to run live upgrade and patch the new boot environment. On the day of the reboot, the containers are detached before reboot. Once the Global Domain rebooted successfully, the containers/zones are atached again.
They have limites space and don't have the luxury for Live Upgrade to make clones of their container/zone environments.
I tried commenting out the running zones in /etc/zones/index but somehow, Live Upgrade still detects the running zone and makes a snapshot of the ZFS filesystem in that ZPOOL.
Any suggestions?

J2EE Containers in 9.0.3.0.0 (Preview 3/25/02) don't handle custom UserManager

Similar Messages

Maybe you are looking for