Running a j2ee application

I deployed a j2ee application. and when i tried to run it with localhost:8080/contextroot., it asks me for user name and password. I am running it on windows XP. can anybody please help me?

try j2ee (username) and j2ee (password)
its usually the default user/password

Similar Messages

Error while running a J2EE application on Oracle10gAS

Hi,
I am receiving an error when trying to run a J2EE application on Oracle10gAS. The application runs successfully on Oracle9iAS, but throws the following exception on 10g application server:
<?xml version="1.0" encoding="UTF-8" ?>
- <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
- <SOAP-ENV:Body>
- <SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Server.Exception:</faultcode>
<faultstring>com.evermind.server.rmi.OrionRemoteException: Error in createInstance(): null; nested exception is: java.lang.NoClassDefFoundError</faultstring>
<faultactor>/STAR-TicketBroker-context-root/TicketBrokerWS</faultactor>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Does anyone have any idea why I would be receiving this
error? We are using Session EJBs in our J2EE application. Are there any changes needed in the code in order to migrate a J2EE application from 9i to 10g ???
Please help.
Thanks,
-Prashant

Hi Somil,
I've just had this same error message, and it was because I had a bogus character in my JSP sources. I'd cut-and-pasted the text from a Word document, and it included the "registered trademark" sign (an R in a circle) as a single character. This worked in my test environment, but not in my production environment (where presumably the default encoding is different). I replaced the character with the equivalent HTML entity &reg; (ie. the five characters & r e g ; ) and it all worked.
Have a look through the offending JSPs and see whether you have any characters that might be incompatible with your default encoding (anything that isn't plain old 7-bit ASCII is potentially a problem). Change them to HTML entities and you should be fine.
Hope this helps,
Richie

Can not run the J2EE application on webless iAS

Hi:
I have installed iAS on Salaris, and installed a webconnector on IIS which
hosted on different machine.
Now I can run the simple servlet sample, but I can not run the Helloworld
application that I deployed follow the guide. The error message was: socket
receive error (RecvBuffer 1)

Don wrote:
Hi:
I have installed iAS on Salaris, and installed a webconnector on IIS which
hosted on different machine.Wow, I did not know that iAS support IIS as the web server. I think SP3
will
allow you to use Apache as well as iPlanet's web server, but I not think
IIS is
supported. Perhaps you should use a supported web server.
Kent

Error While running a J2EE application on J2EE Engine.

Hi Guys,
I have a Ear file which I deployed successfully .Now in some jsp pages its throwing some exception.
. I think its related to Sap parser Can any anyone Resolve this?
Application error occurs during request processing.
Internal error while parsing JSP page [D:/usr/sap/JDV/JC00/j2ee/cluster/server0/apps/JavaEE/SP/servlet_jsp/SP/root/Sample.jsp].
*Details:com.sap.engine.services.servlets_jsp.server.jsp.exceptions.ParseException: TagLibValidator returns error(s) for taglib [http://java.sun.com/jsf/core]:*
+[com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Unsupported character: a0(:main:, row:272, col:25)(:main:, row=272, col=25) -> com.sap.engine.lib.xml.parser.ParserException: Unsupported character: a0(:main:, row:272, col:25)].+
Exception id: [000C29A9E97100650000005B00000930000455FCF34E1452]
Edited by: Somil Agarwal on Sep 3, 2008 2:33 PM
Edited by: Somil Agarwal on Sep 3, 2008 2:34 PM

Hi Somil,
I've just had this same error message, and it was because I had a bogus character in my JSP sources. I'd cut-and-pasted the text from a Word document, and it included the "registered trademark" sign (an R in a circle) as a single character. This worked in my test environment, but not in my production environment (where presumably the default encoding is different). I replaced the character with the equivalent HTML entity &reg; (ie. the five characters & r e g ; ) and it all worked.
Have a look through the offending JSPs and see whether you have any characters that might be incompatible with your default encoding (anything that isn't plain old 7-bit ASCII is potentially a problem). Change them to HTML entities and you should be fine.
Hope this helps,
Richie

Running Java/J2EE application On SAP Netweaver

Hi All,
I am a java/J2ee professional who is relatively new to SAP Netweaver studio. I have developed an application which consists of Core java,JSP and Servlets. Can anybody suggest me as to how to deploy this application on SAP Netweaver and how to test the same.I have already created a war file for the application.Quick suggestions will be highly appreciated as its very urgent for my project.
Regards
Ani

Hi
See this help
http://help.sap.com/saphelp_nw2004s/helpdata/en/a8/fcbc3d16f39e33e10000000a11405a/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/b7/9877fe13221244838a16e3683ad344/frameset.htm
Kind Regards
Mukesh

Running a J2EE application (ear file)

I am new to J2EE. I have created a EnpDtls Servlet simply to greet a person by name - like sample application. But i am unable to see it in on web (localhost:8080). What should i give as url to view the application? I am using J2EE 1,4 Application Server 8.2 from SUN. and jsdk 1.5
I can see my html file under Context Root i.e localhost:8080/EmpDtlsCx. But what should be the url to see the class file of my sevlet.
Servlet is : EmpDtls.class
ContextRoot : /EmpDtlsCx
Web Display : EmpDtlsWebDsp
EAR file : EmpDtlsEar
I have used deploytool. I can also see the Application in Admin console (localhost:4848) -> Enterprise Application. But there also the Admin console does not give any otion of launch as it gives for Web Application. Please note that the verifier option in Admin consoile also passes of sucessfully.
The deployment descriptors: application.xml, sun-application.xml are under <J2ee INSTALLDIR>/domains/domain1/applications/j2ee-apps/EmpDtlsEar/ - the name of the EAR file.
Should i get ContextRoot as folder name ?
Could anyone help in solving my problem ?
The structure of directories and files is as follows
   EmpDtlsEar
   |
   |____ META-INF
   |                |
   |                |____ application.xml
   |                |____ sun-spplication.xml
   |                |____ sun-j2ee-ri.project
   |                |____ MANIFEST.MF
   |
   |____ war-ic.war
                   |
                   |____ EmpDtls.html
                   |
                   |____ META-INF
                   |                  |
                   |                  |__ MANIFEST.MF
                   |
                   |____ WEB-INF
                                     |
                                     |__ web.xml
                                     |
                                     |__ sun-web.xml
                                     |
                                     |__ sun-jee-ri.project
                                     |
                                     |__ classes
                                              |
                                              |__ EmpDtls.class
thanks in advance
tshot

Ok, you have your servlet defined, but now you should map it using mapping tags. Try editing your web.xml file as follows (adding mapping):
<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="2.4" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
<display-name>EmpDtlsWarDisp</display-name>
<servlet>
    <display-name>EmpDtlsWebDisp</display-name>
    <servlet-name>EmpDtlsWebComp</servlet-name>
    <servlet-class>tshot.EmpDtls</servlet-class>
</servlet>
<servlet-mapping>
    <servlet-name>EmpDtlsWebComp</servlet-name>
    <url-pattern>/EmpDtls</url-pattern>
</servlet-mapping>
</web-app>Note the adding of "tshot." in front of your EmpDtls in your servlet-class tag.
This means you need to create a directory in your src location called "tshot", move your EmpDtls.java into the new directory, and then edit that java file, placing the following line at the top of it:
package tshot;Once you have re-built and re-deployed this you should be able to access your servlet at:
http://localhost:8080/EmpDtlsCx/EmpDtls
Refactoring is a term used to mean you've decided to change the name of a variable, method or some alteration of your java file such as changing package names (or adding to a package in this case) whereby the results may or may not affect other classes which depend on this class. Typically, nowadays refactoring is usually done by selecting a refactoring command from a menu item or button within an IDE (Integrated Development Environment) whereby the IDE performs all of the dependancy checking for you and copies the change to affected areas where necessary. Thus, all you need to do is choose the right refactoring operation and click "Ok" in most cases. In the old days, you would have to keep track of all affected areas and manually edit where necessary, based on your imposed change.

HELP!!! Cannot deploy J2EE application with Oracle JDBC driver...

Hi,
I am writing a J2EE application which (in theory, at least)
connects to an Oracle 9i database.
I have written a simple Java test app utilising only the
java.sql package classes (e.g. Connection, ResultSet) to directly
connect to the database. As long as the classes12.zip is in the
CLASSPATH it works fine.
Now I have written an Enterprise application (SessionBean,
Remote and Home interface and Client) which I am attempting to
deploy via deploytool.
If I include just the client jar and EJB jar in the application
it deploys okay but when I run the application (using runclient)
it produces the following error:
java.lang.NoClassDefFoundError: oracle/jdbc/OracleDriver
(It is nested within other error output but that is the core
issue).
However if I try to include the JAR libraries into the app
(classes12.jar and nls_charset.jar from $ORACLE_HOME/jdbc/lib),
then I get the following output from deploytool when I hit the
"deploy" (or "redeploy") button:
Deployment error: invalid entry compressed size
(expected 14411 but got 14580 bytes)
Can someone please tell me what is going on???
How can I deploy the J2EE application including the Oracle
JDBC Driver???
My only other option at the moment is to place all the function-
-ality in the client and not use the J2EE framework.
Any help is greatly appreciated.
Regards,
Ben New
Leftclick Software Development
[email protected]

OK Ben,
I admit I'm a bit confused. Let me see if I understand where you're
coming from.
You have written a J2EE application that includes a session bean,
correct? If so, your session bean needs to be deployed to an EJB
container. What container are you using? The Oracle 9i database
has an embedded EJB container which (theoretically) you can use.
However, as far as I know, Oracle recommends you use OC4J as the
EJB container. So again I ask, what EJB container are you using?
If, as you say, you are new to EJB, then I think you should
immediately start working wiht OC4J as your EJB container.
Did you look at the tutorial link I gave in my previous post? It
explains -- step by step -- how to create, deploy and run a J2EE
application using OC4J as the EJB container. It also has links to
introductory material for people without little knowledge of J2EE
and EJB.
I have 9iAS Enterprise Edition and 8.1.7.1.0 database server (and
OC4J) installed on my SUN machine. I cannot find any of the
utilities you mention -- "j2eeadmin","runclient" or "deploytool".
What Oracle software have you installed? What are the versions?
What platform are you using?
A J2EE application (according to the specification from SUN)
consists of modules. A module can either be a client module or an
EJB module. A client module can either be a java application client
or a web-based client (servlet or JSP). A J2EE application usually
contains one client module and one EJB module. A J2EE application
needs to be deployed to a J2EE container.
Hopefully the J2EE picture is becoming clearer. I think you need
to read some introductory material regarding J2EE if you intend
to become proficient at it.
I feel that you are under the impression that a J2EE application
is a glorified JDBC application. It isn't (as far as I'm aware).
Good Luck,
Avi.

J2EE Application Server fails to start...........

When I tried to run the J2EE Application Server on WindowsXP Professional, I am getting the following error message. Any help will be appreciated.
Logging for J2EE Server Version: 1.3.1-b17 started at: Thu Feb 28 13:39:24 MST 2002..
Using the Java HotSpot(TM) Client VM and the version number 1.3.0 from Sun Microsystems Inc..
VM is using the classpath:
c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\system\cloudscape.jar;
c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\system\tools.jar;
c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\cloudscape\RmiJdbc.jar;
c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\cloudscape\cloudclient.jar;
c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\classes;
c:\home\sukesh\J2EE\j2sdkee1.3.1\classes;
c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\j2ee.jar;
c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\toolclasses;
c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\j2eetools.jar;
c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\locale;
.;c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\j2ee.jar;
c:\home\sukesh\J2EE\jdk1.3\lib\tools.jar;
c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\jhall.jar .
J2EE Home Directory has been set to: c:\home\sukesh\J2EE\j2sdkee1.3.1.
java.lang.NoSuchMethodError
     at com.sun.corba.ee.internal.corba.AnyImpl.createTypeCodeForClass(AnyImpl.java:1256)
     at com.sun.corba.ee.internal.iiop.ShutdownUtilDelegate.createTypeCode(ShutdownUtilDelegate.java:223)
     at com.sun.corba.ee.internal.iiop.ShutdownUtilDelegate.writeAny(ShutdownUtilDelegate.java:178)
     at javax.rmi.CORBA.Util.writeAny(Util.java:80)
     at org.omg.stub.com.sun.enterprise.naming._SerialContextProvider_Stub.rebind(Unknown Source)
     at com.sun.enterprise.naming.SerialContext.rebind(SerialContext.java:188)
     at com.sun.enterprise.naming.SerialContext.rebind(SerialContext.java:202)
     at javax.naming.InitialContext.rebind(InitialContext.java:370)
     at com.sun.enterprise.naming.NamingManagerImpl.publishObject(NamingManagerImpl.java:192)
     at com.sun.enterprise.naming.NamingManagerImpl.publishObject(NamingManagerImpl.java:149)
     at com.sun.enterprise.server.J2EEServer.bindObject(J2EEServer.java:718)
     at com.sun.enterprise.server.J2EEServer.createServerObject(J2EEServer.java:473)
     at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:244)
     at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
My environment variables are set as follows:
CLASSPATH=.;c:\home\sukesh\J2EE\jdk1.3\lib\tools.jar;c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\j2ee.jar
JAVA_HOME=c:\home\sukesh\J2EE\jdk1.3
J2EE_HOME=c:\home\sukesh\J2EE\j2sdkee1.3.1
PATH=c:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\Wbem;c:\home\sukesh\J2EE\jdk1.3\bin;
c:\home\sukesh\J2EE\j2sdkee1.3.1]\bi

When I tried to run the J2EE Application Server on WindowsXP Professional, I am getting the following error message. It is a classpath problem. Any help will be appreciated.
Logging for J2EE Server Version: 1.3.1-b17 started at: Thu Feb 28 13:39:24 MST 2002..
Using the Java HotSpot(TM) Client VM and the version number 1.3.0 from Sun Microsystems Inc..
VM is using the classpath:
c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\system\cloudscape.jar;
c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\system\tools.jar;
c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\cloudscape\RmiJdbc.jar;
c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\cloudscape\cloudclient.jar;
c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\classes;
c:\home\sukesh\J2EE\j2sdkee1.3.1\classes;
c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\j2ee.jar;
c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\toolclasses;
c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\j2eetools.jar;
c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\locale;
.;c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\j2ee.jar;
c:\home\sukesh\J2EE\jdk1.3\lib\tools.jar;
c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\jhall.jar .
J2EE Home Directory has been set to: c:\home\sukesh\J2EE\j2sdkee1.3.1.
java.lang.NoSuchMethodError
at com.sun.corba.ee.internal.corba.AnyImpl.createTypeCodeForClass(AnyImpl.java:1256)
at com.sun.corba.ee.internal.iiop.ShutdownUtilDelegate.createTypeCode(ShutdownUtilDelegate.java:223)
at com.sun.corba.ee.internal.iiop.ShutdownUtilDelegate.writeAny(ShutdownUtilDelegate.java:178)
at javax.rmi.CORBA.Util.writeAny(Util.java:80)
at org.omg.stub.com.sun.enterprise.naming._SerialContextProvider_Stub.rebind(Unknown Source)
at com.sun.enterprise.naming.SerialContext.rebind(SerialContext.java:188)
at com.sun.enterprise.naming.SerialContext.rebind(SerialContext.java:202)
at javax.naming.InitialContext.rebind(InitialContext.java:370)
at com.sun.enterprise.naming.NamingManagerImpl.publishObject(NamingManagerImpl.java:192)
at com.sun.enterprise.naming.NamingManagerImpl.publishObject(NamingManagerImpl.java:149)
at com.sun.enterprise.server.J2EEServer.bindObject(J2EEServer.java:718)
at com.sun.enterprise.server.J2EEServer.createServerObject(J2EEServer.java:473)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:244)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
My environment variables are set as follows:
CLASSPATH=.;c:\home\sukesh\J2EE\jdk1.3\lib\tools.jar;c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\j2ee.jar
JAVA_HOME=c:\home\sukesh\J2EE\jdk1.3
J2EE_HOME=c:\home\sukesh\J2EE\j2sdkee1.3.1
PATH=c:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\Wbem;c:\home\sukesh\J2EE\jdk1.3\bin;
c:\home\sukesh\J2EE\j2sdkee1.3.1\bin

JNDI lookup fails in a thread created by J2EE application on WAS 8.0.0.4 running on Red Hat Enterprise Server 5.8(2.6.18-308.e15).

I am using Jackrabbit Repository (jcr's implementation) as backend in my Web Appl.Whose data persists on Oracle Database. To make connection with Oracle database jackrabbit provide provision of JNDI Lookup to read the data source defined in WAS (using WAS 8.0.0.4 as App Server).
I am able to perform JNDI Lookup everywhere in my application,But in a flow where i am creating a Thread using Java Concurrent Api and insidethread's call() method when I am trying for JNDI Look following exception occurs –
[8/20/13 10:57:35:163 IST] 000000dd System Out O ERROR 20-08 10:57:35,163 (DatabaseFileSystem.java:init:209) failed to initialize file system
javax.jcr.RepositoryException: JNDI name not found: java:comp/env/jdbc/ofsds
at org.apache.jackrabbit.core.util.db.ConnectionFactory.getJndiDataSource(ConnectionFactory.java:295)
at org.apache.jackrabbit.core.util.db.ConnectionFactory.createDataSource(ConnectionFactory.java:233)
at org.apache.jackrabbit.core.util.db.ConnectionFactory.getDataSource(ConnectionFactory.java:166)
at org.apache.jackrabbit.core.fs.db.DbFileSystem.getDataSource(DbFileSystem.java:226)
at org.apache.jackrabbit.core.fs.db.DatabaseFileSystem.init(DatabaseFileSystem.java:190)
at org.apache.jackrabbit.core.config.RepositoryConfigurationParser$6.getFileSystem(RepositoryConfigurationParser.java:1057)
at org.apache.jackrabbit.core.config.RepositoryConfig.getFileSystem(RepositoryConfig.java:911)
at org.apache.jackrabbit.core.RepositoryImpl.<init>(RepositoryImpl.java:285)
at org.apache.jackrabbit.core.RepositoryImpl.create(RepositoryImpl.java:605)
at org.apache.jackrabbit.core.TransientRepository$2.getRepository(TransientRepository.java:232)
at org.apache.jackrabbit.core.TransientRepository.startRepository(TransientRepository.java:280)
at org.apache.jackrabbit.core.TransientRepository.login(TransientRepository.java:376)
at com.mmpnc.icm.server.repository.RepositoryStartupService.newSession(RepositoryStartupService.java:408)
at com.mmpnc.icm.server.repository.RepositoryStartupService.newSession(RepositoryStartupService.java:355)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.jboss.seam.util.Reflections.invoke(Reflections.java:22)
at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31)
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56)
at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:28)
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:44)
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107)
at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:166)
at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:102)
at com.mmpnc.icm.server.repository.RepositoryStartupService_$$_javassist_1.newSession(RepositoryStartupService_$$_javassist_1.java)
at com.mmpnc.icm.server.repository.ICMHouseKeepingSessionManager.create(ICMHouseKeepingSessionManager.java:37)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.jboss.seam.util.Reflections.invoke(Reflections.java:22)
at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31)
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56)
at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:28)
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:77)
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:44)
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107)
at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:166)
at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:102)
at com.mmpnc.icm.server.repository.ICMHouseKeepingSessionManager_$$_javassist_8.create(ICMHouseKeepingSessionManager_$$_javassist_8.java)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.jboss.seam.util.Reflections.invoke(Reflections.java:22)
at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:138)
at org.jboss.seam.Component.callComponentMethod(Component.java:2171)
at org.jboss.seam.Component.callCreateMethod(Component.java:2094)
at org.jboss.seam.Component.newInstance(Component.java:2054)
at org.jboss.seam.Component.getInstance(Component.java:1948)
at org.jboss.seam.Component.getInstance(Component.java:1910)
at org.jboss.seam.Component.getInstance(Component.java:1904)
at org.jboss.seam.Component.getInstanceInAllNamespaces(Component.java:2271)
at org.jboss.seam.Component.getValueToInject(Component.java:2223)
at org.jboss.seam.Component.injectAttributes(Component.java:1663)
at org.jboss.seam.Component.inject(Component.java:1481)
at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:61)
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:44)
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107)
at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:166)
at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:102)
at com.mmpnc.icm.server.repository.ICMHouseKeepingRepository_$$_javassist_7.create(ICMHouseKeepingRepository_$$_javassist_7.java)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.jboss.seam.util.Reflections.invoke(Reflections.java:22)
at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:138)
at org.jboss.seam.Component.callComponentMethod(Component.java:2171)
at org.jboss.seam.Component.callCreateMethod(Component.java:2094)
at org.jboss.seam.Component.newInstance(Component.java:2054)
at org.jboss.seam.Component.getInstance(Component.java:1948)
at org.jboss.seam.Component.getInstance(Component.java:1910)
at org.jboss.seam.Component.getInstance(Component.java:1904)
at org.jboss.seam.Component.getInstanceInAllNamespaces(Component.java:2271)
at org.jboss.seam.Component.getValueToInject(Component.java:2223)
at org.jboss.seam.Component.injectAttributes(Component.java:1663)
at org.jboss.seam.Component.inject(Component.java:1481)
at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:61)
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:44)
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107)
at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:166)
at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:102)
at com.mmpnc.icm.server.repository.ICMHouseKeepingManager_$$_javassist_6.create(ICMHouseKeepingManager_$$_javassist_6.java)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.jboss.seam.util.Reflections.invoke(Reflections.java:22)
at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:138)
at org.jboss.seam.Component.callComponentMethod(Component.java:2171)
at org.jboss.seam.Component.callCreateMethod(Component.java:2094)
at org.jboss.seam.Component.newInstance(Component.java:2054)
at org.jboss.seam.Component.getInstance(Component.java:1948)
at org.jboss.seam.Component.getInstance(Component.java:1910)
at org.jboss.seam.Component.getInstance(Component.java:1904)
at org.jboss.seam.Component.getInstance(Component.java:1899)
at com.mmpnc.icm.server.concurrent.PerformCloseTask.call(PerformCloseTask.java:136)
at com.mmpnc.icm.server.concurrent.PerformCloseTask.call(PerformCloseTask.java:1)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314)
at java.util.concurrent.FutureTask.run(FutureTask.java:149)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:897)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:919)
at java.lang.Thread.run(Thread.java:770)
Caused by:
javax.naming.ConfigurationException: A JNDI operation on a "java:" name cannot be completed because the server runtime is not able to associate the operation's thread with any J2EE application component. This condition can occur when the JNDI client using the "java:" name is not executed on the thread of a server application request. Make sure that a J2EE application does not execute JNDI operations on "java:" names within static code blocks or in threads created by that J2EE application. Such code does not necessarily run on the thread of a server application request and therefore is not supported by JNDI operations on "java:" names. [Root exception is javax.naming.NameNotFoundException: Name comp/env/jdbc not found in context "java:".]
at com.ibm.ws.naming.java.javaURLContextImpl.throwExceptionIfDefaultJavaNS(javaURLContextImpl.java:522)
at com.ibm.ws.naming.java.javaURLContextImpl.throwConfigurationExceptionWithDefaultJavaNS(javaURLContextImpl.java:552)
at com.ibm.ws.naming.java.javaURLContextImpl.lookupExt(javaURLContextImpl.java:481)
at com.ibm.ws.naming.java.javaURLContextRoot.lookupExt(javaURLContextRoot.java:485)
at com.ibm.ws.naming.java.javaURLContextRoot.lookup(javaURLContextRoot.java:370)
at org.apache.aries.jndi.DelegateContext.lookup(DelegateContext.java:161)
at javax.naming.InitialContext.lookup(InitialContext.java:436)
at org.apache.jackrabbit.core.util.db.ConnectionFactory.getJndiDataSource(ConnectionFactory.java:280)
... 114 more
Caused by:
javax.naming.NameNotFoundException: Name comp/env/jdbc not found in context "java:".
at com.ibm.ws.naming.ipbase.NameSpace.getParentCtxInternal(NameSpace.java:1969)
at com.ibm.ws.naming.ipbase.NameSpace.retrieveBinding(NameSpace.java:1376)
at com.ibm.ws.naming.ipbase.NameSpace.lookupInternal(NameSpace.java:1219)
at com.ibm.ws.naming.ipbase.NameSpace.lookup(NameSpace.java:1141)
at com.ibm.ws.naming.urlbase.UrlContextImpl.lookupExt(UrlContextImpl.java:1436)
at com.ibm.ws.naming.java.javaURLContextImpl.lookupExt(javaURLContextImpl.java:477)
... 119 more

Okay "damorgan", you seem to have me confused with a newbie. All I'm posting is the info that I got from my Sys Admin on the fix to my problem I encountered when trying to install Oracle 11g (11.2.0.0) on Red Hat Linux Enterprise 5. Since we're mouting onto an NFS, these are the steps he took. I'm not trying to "hide" information or post as little as possible. What other info do you want? I don't know what you are referring to when you mention "Filer, make, model, software version"? Please elaborate. I was just trying to post to others that may have encountered this problem, and I get somewhat attacked by you. I don't assume anyone can read my mind (especially you).

Help:How can I run the J2EE Client Application? Thanks

Help:How can I run the J2EE Client Application that will access the remote J2EE1.4 application server which runs on another host computer?
I have developped a stateles senterprise java bean name converter and deloyed it in the j2ee1.4 application server on the host machine A. The converterbean provides the remote home interface and remote interface. At the same time I have developped the j2ee application client named convertappclient. When I access the conveter bean at host computer A through the script 'appclient.bat' as 'appclient -client convertappclient.jar', the client can access the bean sucessfully. Now I want to access the bean through the script 'appclient.bat' at host computer B,what files should I copy from host computer A to host computer B;and what the command line should be like? Thanks!
The following are the code of the enterprise java bean and it's home interface .
The client code is also provided.
The enterprise java bean:
package converter;
import java.rmi.RemoteException;
import javax.ejb.SessionBean;
import javax.ejb.SessionContext;
import java.math.*;
public class ConverterBean implements SessionBean {
BigDecimal yenRate = new BigDecimal("121.6000");
BigDecimal euroRate = new BigDecimal("0.0077");
public ConverterBean() {
public BigDecimal dollarToYen(BigDecimal dollars) {
BigDecimal result = dollars.multiply(yenRate);
return result.setScale(2, BigDecimal.ROUND_UP);
public BigDecimal yenToEuro(BigDecimal yen) {
BigDecimal result = yen.multiply(euroRate);
return result.setScale(2, BigDecimal.ROUND_UP);
public void ejbCreate() {
public void ejbRemove() {
public void ejbActivate() {
public void ejbPassivate() {
public void setSessionContext(SessionContext sc) {
The bean's remote home interface :
package converter;
import java.rmi.RemoteException;
import javax.ejb.CreateException;
import javax.ejb.EJBHome;
public interface ConverterHome extends EJBHome {
Converter create() throws RemoteException, CreateException;
The bean's remote interface:
package converter;
import javax.ejb.EJBObject;
import java.rmi.RemoteException;
import java.math.*;
public interface Converter extends EJBObject {
public BigDecimal dollarToYen(BigDecimal dollars) throws RemoteException;
public BigDecimal yenToEuro(BigDecimal yen) throws RemoteException;
The j2ee application client:
import converter.Converter;
import converter.ConverterHome;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.rmi.PortableRemoteObject;
import java.math.BigDecimal;
public class ConverterClient {
public static void main(String[] args) {
try {
Context initial = new InitialContext();
System.setProperty("java.naming.factory.initial","org.jnp.interfaces.NamingContextFactory");
System.setProperty("java.naming.provider.url","jnp://10.144.97.250:3700");
Context myEnv = (Context) initial.lookup("java:comp/env");
Object objref = myEnv.lookup("ejb/SimpleConverter");
ConverterHome home =
(ConverterHome) PortableRemoteObject.narrow(objref,
ConverterHome.class);
Converter currencyConverter = home.create();
BigDecimal param = new BigDecimal("100.00");
BigDecimal amount = currencyConverter.dollarToYen(param);
System.out.println(amount);
amount = currencyConverter.yenToEuro(param);
System.out.println(amount);
System.exit(0);
} catch (Exception ex) {
System.err.println("Caught an unexpected exception!");
ex.printStackTrace();
}

Surprisingly I find an upsurge in the number of posts with this same problem. I recently found a post which gave a nice link for this. Follow the steps and it should help:
http://docs.sun.com/source/819-0079/dgacc.html#wp1022105

Can j2ee applications run on windows xp

i have a problem i am unable to run j2ee applications on windows xp help me..............

i have a problem i am unable to run j2ee applications
on windows xp help me..............Yes, press start > click on shutdown and press ok and go to sleep.
You need to describe something about your problem.

How to create and run J2EE application client for Hello World EJB

Hi
I am new to NWDS EJB deployment.I have created a "Hello World" bean. But how to deploy it and run using a J2EE application client step by step.
Also please help in the steps of the deploy tool.
Thanks in Advance

Hi Ananda
Check this link,
http://help.sap.com/saphelp_nw04/helpdata/en/55/600e64a6793d419b82a3b7d59512a5/content.htm
cheers
Sameer

I unable to run ejb with application client using oc4j j2ee container

Hi,
I have installe oracle9i (1.0.2.2) oc4j j2ee container.
I unable to run the ejbs . please help me how to run ejbs with application client and which files are shall configure.
See the client application is :
public static void main (String []args)
try {
//Hashtable env = new Hashtable();
//env.put("java.naming.provider.url", "ormi://localhost/Demo");
//env.put("java.naming.factory.initial", "com.evermind.server.ApplicationClientInitialContextFactory");
//env.put(Context.SECURITY_PRINCIPAL, "guest");
//env.put(Context.SECURITY_CREDENTIALS, "welcome");
//Context ic = new InitialContext (env);
System.out.println("\nBegin statelesssession DemoClient.\n");
Context context = new InitialContext();
Object homeObject = context.lookup("java:comp/env/DemoApplication");
DemoHome home= (DemoHome)PortableRemoteObject.narrow(homeObject, DemoHome.class);
System.out.println("Creating Demo\n");
Demo demo = home.create();
System.out.println("The result of demoSelect() is.. " +demo.sayHello());
}catch ( Exception e )
System.out.println("::::::Error:::::: ");
e.printStackTrace();
System.out.println("End DemoClient....\n");
When I am running client application I got this type of Exception
java.lang.SecurityException : No such domain/application: sampledemo
at com.evermind.server.rmi.RMIConnection.connect(RMIConnection.java : 2040)
at com.evermind.server.rmi.RMIConnection.connect(RMIConnection.java : 1884)
at com.evermind.server.rmi.RMIConnection.lookup(RMIConnection.java : 1491)
at com.evermind.server.rmi.RMIServer.lookup(RMIServer.java : 323)
at com.evermind.server.rmi.RMIContext.lookup(RMIConext.java : 106)
at com.evermind.server.administration.LazyResourceFinder.lookup(LazyResourceFinder.java : 59)
at com.evermind.server.administration.LazyResourceFinder.getEJBHome(LazyResourceFinder.java : 26)
at com.evermind.server.Application.createContext(Application.java: 653)
at com.evermind.server.ApplicationClientInitialContext.getInitialContext(ApplicationClientInitialContextFactory.java :179 )
at javax.naming.spi.NamingManager.getInitialContext(NamingManger.java : 246)
at javax.naming.InitialContext.getDefaultInitialCtx(InitialContext.java : 246)
at javax.naming.InitialContext.init(InitialContext.java : 222)
at javax.naming.InitialContext.<init>(InitialContext.java : 178)
at DemoClient.main(DemoClient.java : 23)
.ear file is copied into applications directory.
I have configured server.xml file like this
<application name="sampledemo" path="../applications/demos.ear" />
demos.ear file Contains following files
application.xml
demobean.jar
Manifest.mf
demobean.jar file contains following files
application-client.xml
Demo.class
DemoBean.class
DemoHome.class
ejb-jar.xml
jndi.properties
Mainifest.mf
Please give me your valuable suggestions. Which are shall i configure .
Thanks & Regards,
Badri

Hi Badri,
ApplicationClientInitialContextFactory is for clients which got deployed inside OC4J container..
For looking up EJB from a stand alone java client please use RMIInitialContextFactory..So please change ur code....
Also please check ur server.xml
Since you have specified your ejb domain as "sampledemo"
you have to use that domian only for look up..But it seems that you are looking up for "Demo" domain instead of "sampledemo" domain...So change your code to reflect that..
Code snippet for the same is :
Hashtable env = new Hashtable();
env.put("java.naming.provider.url", "ormi://localhost/sampledemo");
env.put("java.naming.factory.initial", "om.evermind.server.rmi.RMIInitialContextFactory");
env.put(Context.SECURITY_PRINCIPAL, "guest");
env.put(Context.SECURITY_CREDENTIALS, "welcome");
Context ic = new InitialContext (env);
Hope this helps
--Venky

Configuring SAP J2EE 6.40 to run BI SDK applications

Hi,
We deployed a BI SDK application and while running we are getting an error.
Portal Runtime Error
An exception occurred while processing a request for :
iView : N/A
Component Name : N/A
Could not find portal application SAPJ2EE::library:bimmrdb.
Exception id: 09:13_21/09/05_0017_1511750
See the details for the exception ID in the log file
Do we need to install any thing more on J2EE to run
BI SDK applications.
Pl. suggest.
Thanks & regards
Mrutyunjay

Hello Kim,
Its by design that SDM either expects the server to be in completely started state ('Running' status) or completely stopped state.
Anything in between, SDM will hang indefinitely for the server to go up. So in a case like yours, you could give it a try to redeploy the offline components first by shutting down the server. For the online deployments, SDM will try to restart the server. If it still hangs in 'Starting applications', the best way is to take threaddumps as per note 710154 and check using the threaddump viewer what is causing the hang. Is it exhaustion of the threads or thread blockage waiting on some action! You can find more info about threaddumpviewer @
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/2015bb75-a9da-2910-e0b1-c5ba9fe90012?quicklink=index&overridelayout=true
Also, one tip for SDM redeployment, its always good to select option 3 on the deployment screen which says 'upgrade regardless of sca/sda version'
SafeMode means the applicaitons are not started during the server startup. This is done during the upgrade when the engine is put in the safemode to avoid long startups. So, the application start forbidden is just indicating that the application was not started due to that mode. Doesn't indicate any error with the application as such.
To check for the startup errors, please check std_server* from <j2ee engine>/work & defaultrace file in server<n>log always. You can get hints from here.
Hope the above helps.
Regards,
Snehal Bhaidasna
SAP Labs, Palo Alto, CA(USA)

Performance of J2ee Application running in Portal Server

Hi,
We have developed the J2ee Application using JSPDynPage and the performance of this Application is going down day by day.
It is taking arround 30 sec to load the page.Sometimes I am getting iView Timed out error if the Load is Very high.
This is all happening in Production server.Can any one please help me to increase the Performance of the Portal.
Thanks in Advance
Ajay

> Thanks for the response.
>
> There is no problem in the application as i know the
> code in this application is perfectly fine.
>
> There will be huge load on monday that too between
> 9-11 AM as too many people will be doing the the
> Database transactions at that point of time (adding
> the data in to the DB extracting huge amount of data
> from DB) the CPU usage in the porduction server will
> reach 90 % to 99 % and it will never come down
> ...this will again come to the normal situation when
> we restart the portal database.
>
> But every monday i cannot restart the server as this
> is in production.
>
> Can anyone please give some tips to increase the
> performance of the portal.
Have you checked your Garbage Collector log file ?
I posted some hints about how to do that in the thread "Server Performance Issue" in this forum.
I could be that you are running out of memory after the heavy load and then everything will be slow afterwards, because full GC's might be triggered frequently.
Regards,
Markus
>
> Thanks
> Ajay

Running a j2ee application

Similar Messages

Maybe you are looking for