Javax.naming.InvalidNameException when deploying JCA project to EP6

Greetings,
I have found the "JCA on EP6: Building Portal Applications with Remote Function Modules" (Mar'04) to be one of the clearest documents on how JCA from EP works. I also found the sample jca package package that comes with it to be one of the cleanest and best commented examples of SAP code I've seen.
However, after working around the typo by using "gl_api.jar" instead of "glserviceapi.jar", I ran into a brick wall. Every attempt to deploy the .par results in the deployment-time exception:
"javax.naming.InvalidNameException: Character not allowed: ' ' in JCA on EP6 sample.par"
I have triple-checked the portalapp.xml and even commented out 90% of the code in the .java source. Nothing will let it by the componentchecker.
Thanks in advance for any help.
Ken

Hi,
Not sure if you had solved this problem, but you might need to restart the EP instance?
Best regards,
Ken

Similar Messages

Javax.naming.InvalidNameException when deploying JCA project

Greetings,
I have found the "JCA on EP6: Building Portal Applications with Remote Function Modules" (Mar'04) to be one of the clearest documents on how JCA from EP works. I also found the sample jca package package that comes with it to be one of the cleanest and best commented examples of SAP code I've seen.
However, after working around the typo by using "gl_api.jar" instead of "glserviceapi.jar", I ran into a brick wall. Every attempt to deploy the .par results in the deployment-time exception:
"javax.naming.InvalidNameException: Character not allowed: ' ' in JCA on EP6 sample.par"
I have triple-checked the portalapp.xml and even commented out 90% of the code in the .java source. Nothing will let it by the componentchecker.
Thanks in advance for any help.
Ken

Hi,
Not sure if you had solved this problem, but you might need to restart the EP instance?
Best regards,
Ken

Javax.naming.NamingException: when deploying to OC4J using admin.jar

Additional details to posting (Problem Deploying to OC4J from Jbuilder8)
Jul 8 2003 @3:27
enter:-
java -jar "\ora9ias\j2ee\home\admin.jar" ormi://myhost:23791 admin password
and you get the error message:-
javax.naming.NamingException: Lookup error: java.net.ConnectException: Connection refused: connect; nested exception is:
java.net.ConnectionException: Connection refused: connect
My server.xml contains entry <rmi-config path="./rmi.xml" />
and my rmi.xml reads:-
<?xml version="1.0" standalone="yes" ?>
<!DOCTYPE rmi-server (View Source for full doctype...)>
- <rmi-server port="23791" host="[ALL]">
- <log>
<file path="../log/rmi.log" />
</log>
</rmi-server>
I have repeatedly checked my hostname port user name and password
along with the statements in the server.xml and rmi.xml as above, but with no
success.
Regards
Gary.

I am facing the same problem from this morning. I was able to start oc4j jvm without any problem today in the morning and i could deploy the war file and was able to test the web pages. But due to some unavoidable reasons i had to restart my machine and ever since then i am running into the following error.
My server.xml has a reference to rmi.xml.
Any help is highly appreciated.
Regards
Kiran
D:\Java\JDev9i\j2ee\home>java -jar oc4j.jar
Node started with id=647722646
Error initializing web-site at ./http-web-site.xml: default-web-app not specifie
d for Oracle9iAS Containers for J2EE HTTP Web Site
Oracle9iAS (9.0.3.0.0) Containers for J2EE initialized

WLS 6.0: javax.naming.NamingNotFoundException when selecting DataSource in server JNDI tree in Admin Console

Summary of problem: Get a javax.naming.NamingNotFoundException when selecting the DataSource (see the configuration below) in server JNDI tree in Admin Console
TheConnection Pool and a corresponding DataSource are configured as follows:
<JDBCDataSource
JNDIName="jdbc.PNStoreDB"
Name="PNStoreDB"
PoolName="PNStorePool"
Targets="serverA"
/>
<JDBCConnectionPool
CapacityIncrement="2"
DriverName="weblogic.jdbc.oci.Driver"
InitialCapacity="2"
LoginDelaySeconds="1"
MaxCapacity="10"
Name="PNStorePool"
Properties="user=rms;password=rms;server=ora81"
RefreshMinutes="10"
Targets="serverA"
TestTableName="dual"
URL="jdbc:weblogic:oracle"
/>
Can't figure out why this is happening. The following is output to the Admin Server command prompt:
<May 18, 2001 10:20:02 AM EDT> <Error> <HTTP> <[WebAppServletContext(6233000,console)] exception raised on '/console/panel
javax.naming.NameNotFoundException: Unable to resolve jdbc. Resolved: '' Unresolved:'jdbc' ; remaining name ''
<<no stack trace available>>
I tried using a different JNDI name for the DataSource (e.g. just PNStoreDB) with no success.
The weird thing is that it messes up other resources bound in the JNDI tree. For e.g. I have some EJB's bound under ejb/XXXX that I can click on and view in the Admin Console (JNDI tree) before I add the pool and DataSource. After I add them though, I see the same NameNotFoundException for these as well.
Thanks in advance for your help.
[att1.html]

Are you sure that the connection pool and datasource deployed
successfully? (Check the logs for an error.)
Also, I suspect that you want a TxDataSource instead of a
JDBCDataSource.
-- Rob
Weblogic NewsGroups wrote:
Summary of problem: Get a javax.naming.NamingNotFoundException when
selecting the DataSource (see the configuration below) in server JNDI
tree in Admin Console
TheConnection Pool and a corresponding DataSource are configured as
follows:
<JDBCDataSource
JNDIName="jdbc.PNStoreDB"
Name="PNStoreDB"
PoolName="PNStorePool"
Targets="serverA"
/>
<JDBCConnectionPool
CapacityIncrement="2"
DriverName="weblogic.jdbc.oci.Driver"
InitialCapacity="2"
LoginDelaySeconds="1"
MaxCapacity="10"
Name="PNStorePool"
Properties="user=rms;password=rms;server=ora81"
RefreshMinutes="10"
Targets="serverA"
TestTableName="dual"
URL="jdbc:weblogic:oracle"
/>
Can't figure out why this is happening. The following is output to
the Admin Server command prompt:
<May 18, 2001 10:20:02 AM EDT> <Error> <HTTP>
<[WebAppServletContext(6233000,console)] exception raised on
'/console/panel
javax.naming.NameNotFoundException: Unable to resolve jdbc. Resolved:
'' Unresolved:'jdbc' ; remaining name ''
<<no stack trace available>>
I tried using a different JNDI name for the DataSource (e.g. just
PNStoreDB) with no success.
The weird thing is that it messes up other resources bound in the JNDI
tree. For e.g. I have some EJB's bound under ejb/XXXX that I can
click on and view in the Admin Console (JNDI tree) before I add the
pool and DataSource. After I add them though, I see the same
NameNotFoundException for these as well.
Thanks in advance for your help.--
Coming Soon: Building J2EE Applications & BEA WebLogic Server
by Michael Girdley, Rob Woollen, and Sandra Emerson
http://learnweblogic.com

Javax.naming.NoInitialContextException when invoking an EJB

Hi,
I've deployed a stateless session EJB in oc4j and invoking it thru a Java client. I'm using Eclipse. I've a jndi.properties in config folder of my application which is in the classpath of the client code.
The jndi.properties has :
java.naming.factory.initial=com.evermind.server.rmi.RMIInitialContextFactory
java.naming.provider.url=ormi://<localhost>:12401/OC4JEJB
java.naming.security.principal=oc4jadmin
java.naming.security.credentials=oc4jadmin
where OC4JEJB is the application name deployed in oc4j.
This jndi.properties file is in the classpath.
My client code is :
Server server = null; //interface
ServerHome testSessionBean; //implementation of methods in Server interface
try {
Context ctx = new InitialContext();
Object objref = ctx.lookup("EJBServer"); //JNDI name
Object obj = PortableRemoteObject.narrow(objref, ServerHome.class);
testSessionBean = (ServerHome) PortableRemoteObject.narrow(objref,
 ServerHome.class);
server = testSessionBean.create();
} catch (...) { }
When i set the properties and do a look up
Properties env = new Properties();
env.put(Context.INITIAL_CONTEXT_FACTORY,
 "com.evermind.server.rmi.RMIInitialContextFactory");
env.put(Context.SECURITY_PRINCIPAL, "oc4jadmin");//oc4jadmin
env.put(Context.SECURITY_CREDENTIALS, "oc4jadmin");
env.put(Context.PROVIDER_URL,
 "ormi://<localhost>:12401/OC4JEJB");
InitialContext ctx = new InitialContext(env);
it works perfectly fine.
But when i use the jndi.properties it gives the following exception.
javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
 at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
 at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
 at javax.naming.InitialContext.getURLOrDefaultInitCtx(Unknown Source)
 at javax.naming.InitialContext.lookup(Unknown Source)
 at client.ORION_EJB_Util.getServer(ORION_EJB_Util.java:203)
 at client.ORION_EJB_Util.<init>(ORION_EJB_Util.java:90)
 at client.TestClient.main(TestClient.java:26)
client.exception.EJBUtilException
 at client.ORION_EJB_Util.getServer(ORION_EJB_Util.java:248)
 at client.ORION_EJB_Util.<init>(ORION_EJB_Util.java:90)
 at client.TestClient.main(TestClient.java:26)
Invoking the server
Inside getServer method
Obtained Initial Context javax.naming.InitialContext@422ede
Exception null
I've tried placing the jndi.properties in j2ee/home/applib too. Where shud i place this jndi.properties and invoke the EJB?
Could anyone help resolve this issue?
Thanks in advance,
Sprightee

Try add your jndi.properties to your CLASSPATH.
See this doc for more details of RMI.
http://download-east.oracle.com/docs/cd/B31017_01/web.1013/b28958/rmi.htm#i1084792

Error when deploy a project in SQL Server Analysis Services

Hi all, I tried deploy my project SSAS, but it send message error.
This is image before deploy myproject, it is star chema of project.
and this is the image when i try deploy it, error list.
I want to complete my project. How i can fix error list??? Help me.

Hi Anhlovevietnam,
According to the error message, it seems that the Analysis Services account lack permission to access ‘QLTICKET’. By default, the default account for AS services has only public permission to few databases. If you haven't change the AS services account,
or haven't grant the permission for this account, then you cannot deploy the AS project to server.
So in your scenario, ensure the service "SQL Server Analysis Services" is running with a proper Log On As user. This user should have administrator permission on Analysis Services and the proper permissions on the database engine. To avoid this issue, you
can grant the SELECT permission for the default account for AS services to data source DB. Or you can change the services account to this domain user who has the corresponding to the data source DB.
http://jetreportskb.host4kb.com/article/AA-00238
Regards,
Charlie Liao
Charlie Liao
TechNet Community Support

Javax.naming.InvalidNameException

Hi I have the following problem.
I want to get an object from AD. But every time I get the follwing result after running:
Lookup failed: javax.naming.NameNotFoundException: [LDAP: error code 32 - 0000208D: NameErr: DSID-031001CD, problem 2001 (NO_OBJECT), data 0, best match of:
 'DC=fzi,DC=de'
I ran successfull *ctx.list*() and *ctx.search()* with SubtreeScope. But when I want to lookup(), It doesn't run successfully.
Here is the sample code (but notice that I deleted my pw in Context.SECURITY_CREDENTIALS
import java.io.IOException;
import java.util.Hashtable;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import javax.naming.ldap.LdapContext;
public class GetUser {
 public static void main(String[] args) throws IOException {
Hashtable<String, Object> env = new Hashtable<String, Object>();
env.put(Context.INITIAL_CONTEXT_FACTORY,"com.sun.jndi.ldap.LdapCtxFactory");
String ldapURL = "ldap://ldap.fzi.de:3268/DC=fzi,DC=de";
//connect to my domain controller
env.put(Context.PROVIDER_URL,ldapURL);
//set security credentials, note using simple cleartext authentication
env.put(Context.SECURITY_AUTHENTICATION,"simple");
env.put(Context.SECURITY_PRINCIPAL,"[email protected]");
env.put(Context.SECURITY_CREDENTIALS,"....");
try {
//Create the initial directory context
Context ctx = new InitialContext(env);
LdapContext user = (LdapContext)ctx.lookup("CN=Ugur Kocak,OU=Users,OU=PROST");
System.out.println(user);
ctx.close();
catch (NamingException e) {
System.out.println("Lookup failed: " + e);
It would be very nice if someone can help me
Best regards
Ugur
Edited by: ugurkocak1980 on Jan 22, 2010 12:35 PM
Edited by: ugurkocak1980 on Jan 22, 2010 12:36 PM

Hi,
I am getting the same error. But I am not running ctx.list or ctx.search method. I am just trying to change the User password in AD.
 DirContext ldapContext;
 String baseName = "CN=APOPSDC, DC=ispl, DC=com";
 String based = " ";
 String serverIP = "apopsdc";
 String modelUsername = "template";
 System.out.println("works");
 Security.addProvider(new com.sun.net.ssl.internal.ssl.Provider());
 String keystore = "C:\\Program Files\\Java\\jdk1.6.0_26\\jre\\lib\\security\\cacerts";
 System.setProperty("javax.net.ssl.trustStore",keystore);
 // the keystore that holds trusted root certificates
 try {
 Hashtable env = new Hashtable(11);
 env.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.ldap.LdapCtxFactory");
 String ldapURL = "ldap://***********:636";
 env.put(Context.PROVIDER_URL, "ldap://********.636");
 env.put(Context.SECURITY_AUTHENTICATION, "Simple");
 //it can be <domain\\userid> something that you use for windows login
 //it can also be
 String userName = "ispl\\navin.kumar";
 env.put(Context.SECURITY_PRINCIPAL, "************");
 env.put(Context.SECURITY_CREDENTIALS, "********");
 env.put(Context.SECURITY_PROTOCOL, "ssl");
 //in following property we specify ldap protocol and connection url.
 //generally the port is 389
 ldapContext = new InitialDirContext(env);
 DirContext ctx = (DirContext)ldapContext;
 System.out.println("Context Sucessfully Initialized");
 ModificationItem[] mods = new ModificationItem[1];
 mods[0] = new ModificationItem(DirContext.REPLACE_ATTRIBUTE, new BasicAttribute("userpassword" ,"********" ));
 System.out.println("step 3");
 //ldapContext.modifyAttributes("cn=" + username + baseName, mods);
 System.out.println("dn = " + "cn=" + ldapURL + userName);
 ctx.modifyAttributes(based, mods);
 System.out.println("step 4");
 System.out.println("success base");
 ctx.close();
 } catch (Exception e) {
 System.out.println(" bind error: " + e);
 e.printStackTrace();
 System.exit(-1);
 }When I run this, I am getting the following error :
"dn = cn=ldap://apopsdc.ispl.com:636ispl\*******
bind error: javax.naming.NameNotFoundException: [LDAP: error code 32 - 0000208D: NameErr: DSID-031001A8, problem 2001 (NO_OBJECT), data 0, best match of:
{code}
What is the problem here?
Edited by: EJP on 21/02/2013 16:09
Edited by: Infanta on May 20, 2013 11:03 PM
Edited by: Infanta on May 20, 2013 11:05 PM

Javax.naming.NotContextException when trying to bind to a context

Hi all.
I am trying to use file system service provider.
This is how I create the context:
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY,
"com.sun.jndi.fscontext.RefFSContextFactory");
env.put(Context.PROVIDER_URL, "file:/test");
DirContext ctx = new InitialDirContext(env);
When I try to invoke bind on ctx ;
ctx.bind(name, obj, attrs)
I get exception:
javax.naming.NotContextException: Not an instance of DirContext
at javax.naming.directory.InitialDirContext.getURLOrDefaultInitDirCtx(Unknown Source)
Can anyone help me get around this problem.
thanks.

I don't think that
com.sun.jndi.fscontext.RefFSContextFactory
supports DirContext; just Context.

Javax.nameing.NameNotFoundException when connection to Standalone OC4J

I have installed a standalone OC4J 10.1.3 for a testing purposes.
It is an out-of-the-zip-file installation, so I have not configured anything except for the administrator password.
I can start/stop the serveren and access the Oracle Enterprise Manager from both the local server and remote PC's. I can browse the instance as expected and everything seems to work.
When creating a testing a connection from JDeveloper on a remote PC I receive the following exception:
Error while getting remote MBeanServer for url: ormi://<the correct server name>:23791/default
Error reading application-client descriptor: Error communication with server oc4j:internal/ResourceFinder not found; nested exception is:
javax.nameing.NameNotFoundException: oc4j:internal/ResourceFinder not found
-- Regards Flemming

I have installed a standalone OC4J 10.1.3 for a testing purposes.
It is an out-of-the-zip-file installation, so I have not configured anything except for the administrator password.
I can start/stop the serveren and access the Oracle Enterprise Manager from both the local server and remote PC's. I can browse the instance as expected and everything seems to work.
When creating a testing a connection from JDeveloper on a remote PC I receive the following exception:
Error while getting remote MBeanServer for url: ormi://<the correct server name>:23791/default
Error reading application-client descriptor: Error communication with server oc4j:internal/ResourceFinder not found; nested exception is:
javax.nameing.NameNotFoundException: oc4j:internal/ResourceFinder not found
-- Regards Flemming

Weblogic not finding javax.naming classes when instantiating bean

Hello,
 I am developing a JSP which contains a JavaBean.
 This bean is a wrapper for a session EJB, the getProperty() methods in
 the bean call methods on the EJB's remote interface.
 I have tested this bean as a stand alone application by adding a
 main(String[] args) method to it and it works.
 However, when adding the bean to the JSP, the JSP does not show in the
 browser, I get a n internal server error 500 instead.
 It seems that Weblogic is not finding the javax.naming.NamingException
 class when instantiating the bean.
 When looking at the weblogic log, I see the following stack trace:
 Fri Aug 18 15:12:06 EDT 2000:<E> <ServletContext-General> Servlet failed
 with Exception
 java.lang.NoClassDefFoundError: javax/naming/NamingException
 at java.lang.ClassLoader.resolveClass0(Native Method)
 at java.lang.ClassLoader.resolveClass(ClassLoader.java:579)
 at
 weblogic.utils.classloaders.GenericClassLoader.reallyLoadClass(GenericClassLoader.java,
 Compiled Code)
 at
 weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java,
 Compiled Code)
 at
 weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java,
 Compiled Code)
 at java.beans.Beans.instantiate(Beans.java:194)
 at java.beans.Beans.instantiate(Beans.java:55)
 at weblogic.servlet.jsp.JspLexer.processBeanTag(JspLexer.java:1138)
 at weblogic.servlet.jsp.JspLexer.mXML_OPEN_USEBEAN(JspLexer.java,
 Compiled Code)
 at weblogic.servlet.jsp.JspLexer.mXML_THING(JspLexer.java:1554)
 at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java, Compiled Code)
 at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java, Compiled
 Code)
 at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java, Compiled Code)
 at weblogic.servlet.jsp.JspParser.doit(JspParser.java, Compiled Code)
 at weblogic.servlet.jsp.JspParser.parse(JspParser.java:116)
 at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:97)
 at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java,
 Compiled Code)
 at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java, Compiled
 Code)
 at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:173)
 at weblogic.servlet.jsp.JspStub.checkForReload(JspStub.java:92)
 at
 weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:191)
 at
 weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:118)
 at
 weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:744)
 at
 weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:692)
 at
 weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:251)
 at
 weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:363)
 at
 weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:263)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
 Any idea on how to fix this?
 Thanks for any help,
 David


 yes, weblogicaux.jar is definitely in the weblogic.class.path. i've even tried starting the server from the command line, declaring the classes there. my "trade.xml" document has the URI set as "http://localhost:7001/BizTalkServer". when i enter this on the "BizClient.jsp" form, i get the error discussed below. however, if i enter "http://localhost:7001", even though this is not the explicit location of the BizTalk server, the server returns:
 Thank you! Your trade has been recieved. A BizTalk document has been sent to http://localhost:7001/ with the following information: etc...............
 So there appears to be something wrong with the "/BizTalkServer" setup on my machine. Any ideas?
 Kumar Allamraju <[email protected]> wrote:
 >Make sure weblogicaux.jar is in your weblogic.class.path
 >
 >i.e -Dweblogic.class.path=$WL_HOME/lib/weblogicaux.jar:$WL_HOME/classes etc etc...
 >
 >--
 >Kumar
 >
 >Mike Bachers wrote:
 >
 >> I'm currently struggling with a similar problem, although as a newcomer to WL I'm having some trouble figuring it out. I'm trying to run the BizTalk server example (http://www.weblogic.com/docs51/examples/xml/biztalk/index.html) under Windows 2000 and JDK1.2.2. I'm able to proceed without problems until I submit the form on the "BizClient.jsp" page. At this point, I receive this error:
 >> ------------------------------------------------
 >> There was a problem connecting to the BizTalk server. Exception caught: java.io.FileNotFoundException: Response: '500' for url: 'http://localhost:7001/BizTalkServer'
 >> ------------------------------------------------
 >>
 >> At the same time, the WL console spits this out:
 >> ------------------------------------------------
 >> java.lang.NoClassDefFoundError: javax/naming/NamingException
 >> ....
 >> ------------------------------------------------
 >>
 >> I know this class is in the weblogicaux.jar, and it's included in my classpath. I think David's fix (see below) is getting at my problem, too, but I'm not sure. Anyone relate?
 >>
 >> "David R. Heffelfinger" <[email protected]> wrote:
 >> >Figured it out. The problem was that the beans were in a directory
 >> >in the JAVA_CLASSPATH in weblogic.properties. Moved the directory to
 >> >WEBLOGIC_CLASSPATH and the problem went away.
 >> >
 >> >David
 >> >
 >> >"David R. Heffelfinger" wrote:
 >> >
 >> >> Hello,
 >> >>
 >> >> I am developing a JSP which contains a JavaBean.
 >> >> This bean is a wrapper for a session EJB, the getProperty() methods in
 >> >> the bean call methods on the EJB's remote interface.
 >> >>
 >> >> I have tested this bean as a stand alone application by adding a
 >> >> main(String[] args) method to it and it works.
 >> >>
 >> >> However, when adding the bean to the JSP, the JSP does not show in the
 >> >> browser, I get a n internal server error 500 instead.
 >> >> It seems that Weblogic is not finding the javax.naming.NamingException
 >> >> class when instantiating the bean.
 >> >>
 >> >> When looking at the weblogic log, I see the following stack trace:
 >> >>
 >> >> Fri Aug 18 15:12:06 EDT 2000:<E> <ServletContext-General> Servlet failed
 >> >> with Exception
 >> >>
 >> >> java.lang.NoClassDefFoundError: javax/naming/NamingException
 >> >>
 >> >> at java.lang.ClassLoader.resolveClass0(Native Method)
 >> >>
 >> >> at java.lang.ClassLoader.resolveClass(ClassLoader.java:579)
 >> >>
 >> >> at
 >> >> weblogic.utils.classloaders.GenericClassLoader.reallyLoadClass(GenericClassLoader.java,
 >> >> Compiled Code)
 >> >>
 >> >> at
 >> >> weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java,
 >> >> Compiled Code)
 >> >>
 >> >> at
 >> >> weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java,
 >> >> Compiled Code)
 >> >>
 >> >> at java.beans.Beans.instantiate(Beans.java:194)
 >> >>
 >> >> at java.beans.Beans.instantiate(Beans.java:55)
 >> >>
 >> >> at weblogic.servlet.jsp.JspLexer.processBeanTag(JspLexer.java:1138)
 >> >>
 >> >> at weblogic.servlet.jsp.JspLexer.mXML_OPEN_USEBEAN(JspLexer.java,
 >> >> Compiled Code)
 >> >>
 >> >> at weblogic.servlet.jsp.JspLexer.mXML_THING(JspLexer.java:1554)
 >> >>
 >> >> at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java, Compiled Code)
 >> >>
 >> >> at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java, Compiled
 >> >> Code)
 >> >>
 >> >> at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java, Compiled Code)
 >> >>
 >> >> at weblogic.servlet.jsp.JspParser.doit(JspParser.java, Compiled Code)
 >> >>
 >> >> at weblogic.servlet.jsp.JspParser.parse(JspParser.java:116)
 >> >>
 >> >> at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:97)
 >> >>
 >> >> at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java,
 >> >> Compiled Code)
 >> >>
 >> >> at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java, Compiled
 >> >> Code)
 >> >>
 >> >> at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:173)
 >> >>
 >> >> at weblogic.servlet.jsp.JspStub.checkForReload(JspStub.java:92)
 >> >>
 >> >> at
 >> >> weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:191)
 >> >>
 >> >> at
 >> >> weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:118)
 >> >>
 >> >> at
 >> >> weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:744)
 >> >>
 >> >> at
 >> >> weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:692)
 >> >>
 >> >> at
 >> >> weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:251)
 >> >>
 >> >> at
 >> >> weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:363)
 >> >>
 >> >> at
 >> >> weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:263)
 >> >>
 >> >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
 >> >>
 >> >> Any idea on how to fix this?
 >> >>
 >> >> Thanks for any help,
 >> >> David
 >> >
 >

Error when deploying a project

Everytime when i want to deploy any simple project i get an error. Even if i try samples, tutorials or something else.
At deployment time I see this in the Ant log:
BUILD FAILED
C:\product\jdevstudio10134\jdev\mywork\DemoExpen\ExpenseRequest\build.xml:97: Error while deploying the form on server "localhost" Error message :
java.lang.SecurityException
at oracle.ide.IdeCore$7.checkExit(IdeCore.java:177)
at java.lang.Runtime.exit(Runtime.java:88)
at java.lang.System.exit(System.java:868)
at oracle.oc4j.admin.deploy.cmdline.Oc4jAdminCmdline.executeCommand(Oc4jAdminCmdline.java:141)
at com.collaxa.cube.ant.taskdefs.DeployForm.deployIAS(DeployForm.java:818)
at com.collaxa.cube.ant.taskdefs.DeployForm.deployForm(DeployForm.java:578)
at com.collaxa.cube.ant.taskdefs.DeployForm.deployForms(DeployForm.java:849)
at com.collaxa.cube.ant.taskdefs.DeployForm.execute(DeployForm.java:875)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at oracle.jdevimpl.ant.runner.AntLauncher.launch(AntLauncher.java:321)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at oracle.jdevimpl.ant.runner.InProcessAntStarter.runAnt(InProcessAntStarter.java:295)
at oracle.jdevimpl.ant.runner.InProcessAntStarter.mav$runAnt(InProcessAntStarter.java:43)
at oracle.jdevimpl.ant.runner.InProcessAntStarter$1.run(InProcessAntStarter.java:71)
Total time: 18 seconds
I just made new basic installation . ANd using oracle soa suite 10.1.3.4
i can use oracle BPEL console, worklist application and other web pages.
Can any1 tell me please what is wrong?

Make sure that you are deploying using the right ports. I encounter that most often when the RMI ports are wrong. You can find the RMI ports by running opmnctl status -l

ORABPEL-09903 when deploying BPEL project

Hi,
When I am deploy a BPEL project, below error is reported:
C:\jdevstudio10133\jdev\AppsCreateOrder\AppsCreateOrder\build.xml:79: A problem occured while connecting to server "col-hydra2" using port "7777":
bpel_AppsCreateOrder_1.0.jar failed to deploy. Exception message is:
ORABPEL-09903
Could not initialize activation agent.
Any help is greatly appreciated in helping resolve this issue.
Regards,
Balu

Hi everyone,
I have posted this under BPEL forum also where solution for this ORABPEL error is provided.
URL:
Urgent help needed for ORABPEL-09903
But looking at the solution I am not understanding one thing.
If we remove activationAgents from bpel.xml, then how our BPEL process gets initialized.
Removing that xml fragment from the bpel.xml file will essentially render the adapter unserviceable because you have removed the activation agent linked with the adapter. Thus, despite the process getting deployed successfully, the adapter will not work and you will get a run-time error.
Any opinions on this?
Cheers,
Abhi...

GetEntityListXML Error Code: 1000: 5 when deploying ESB project?

All,
I am getting:
GetEntityListXML
error code: 1000 : 5
summary: -
Fix: Contact Oracle Support
when I try to deploy my ESB project. It has worked before.
Has anyone seen anything similar?
Thanks,
Mathias

This is generally happen if your esb repository is not available.
Please check if you esb server is started properly without any exceptions etc.
Thanks,
Rakesh

Error happened when deployed my project in JDev 11g!Help!!!

First I ran the project successfully, then when I ran it again, error happened and other project had the same error. I found solution in forum that delete the file "system11.1.1.0.31.52.05" in the install path of JDeveloper 11g, but this needs to close the Jdev . It is so inconvenient.
Who would like to tell me how to fix it except above solution?
The following is the error message:
java.lang.RuntimeException: java.lang.NullPointerException
     at oracle.jdevimpl.deploy.common.ModulePackagerImpl.deployProfiles(ModulePackagerImpl.java:88)
     at oracle.jdeveloper.deploy.common.ModulePackager.deployProfiles(ModulePackager.java:63)
     at oracle.jdeveloper.deploy.common.ModulePackager.deployImpl(ModulePackager.java:52)
     at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
     at oracle.jdevimpl.deploy.fwk.WrappedDeployer.deployImpl(WrappedDeployer.java:39)
     at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
     at oracle.jdeveloper.deploy.common.BatchDeployer.deployImpl(BatchDeployer.java:82)
     at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
     at oracle.jdevimpl.deploy.fwk.WrappedDeployer.deployImpl(WrappedDeployer.java:39)
     at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
     at oracle.jdevimpl.deploy.fwk.WrappedDeployer.deployImpl(WrappedDeployer.java:39)
     at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
     at oracle.jdeveloper.deploy.common.BatchDeployer.deployImpl(BatchDeployer.java:82)
     at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
     at oracle.jdevimpl.deploy.fwk.WrappedDeployer.deployImpl(WrappedDeployer.java:39)
     at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
     at oracle.jdeveloper.deplo... [Show more]

I seem to have the exact same error, as you can see below..
Funny thing is, I was also able to run the application without any trouble.
From one moment to the other it gave this error.
Is there someone who knows the way to fix this?
My error message:
#### Deployment incomplete. #### Jun 24, 2009 4:15:03 PM
java.lang.RuntimeException: java.lang.NullPointerException
     at oracle.jdevimpl.deploy.common.ModulePackagerImpl.deployProfiles(ModulePackagerImpl.java:88)
     at oracle.jdeveloper.deploy.common.ModulePackager.deployProfiles(ModulePackager.java:63)
     at oracle.jdeveloper.deploy.common.ModulePackager.deployImpl(ModulePackager.java:52)
     at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
     at oracle.jdevimpl.deploy.fwk.WrappedDeployer.deployImpl(WrappedDeployer.java:39)
     at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
     at oracle.jdeveloper.deploy.common.BatchDeployer.deployImpl(BatchDeployer.java:82)
     at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
     at oracle.jdevimpl.deploy.fwk.WrappedDeployer.deployImpl(WrappedDeployer.java:39)
     at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
     at oracle.jdevimpl.deploy.fwk.WrappedDeployer.deployImpl(WrappedDeployer.java:39)
     at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
     at oracle.jdeveloper.deploy.common.BatchDeployer.deployImpl(BatchDeployer.java:82)
     at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
     at oracle.jdevimpl.deploy.fwk.WrappedDeployer.deployImpl(WrappedDeployer.java:39)
     at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
     at oracle.jdeveloper.deploy.common.BatchDeployer.deployImpl(BatchDeployer.java:82)
     at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
     at oracle.jdevimpl.deploy.fwk.WrappedDeployer.deployImpl(WrappedDeployer.java:39)
     at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
     at oracle.jdeveloper.deploy.common.BatchDeployer.deployImpl(BatchDeployer.java:82)
     at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
     at oracle.jdevimpl.deploy.fwk.WrappedDeployer.deployImpl(WrappedDeployer.java:39)
     at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
     at oracle.jdevimpl.deploy.fwk.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:436)
     at oracle.jdeveloper.deploy.DeploymentManager.deploy(DeploymentManager.java:209)
     at oracle.jdevimpl.runner.adrs.AdrsStarter$5$1.run(AdrsStarter.java:1365)
Caused by: java.lang.NullPointerException
     at oracle.ide.net.URLFileSystem$TrackedOutputStream.flush(URLFileSystem.java:2332)
     at java.io.FilterOutputStream.flush(FilterOutputStream.java:123)
     at oracle.jdevimpl.deploy.stripe.MonitoredOutputStream.flush(MonitoredOutputStream.java:84)
     at java.io.FilterOutputStream.close(FilterOutputStream.java:140)
     at oracle.jdevimpl.deploy.stripe.MonitoredOutputStream.close(MonitoredOutputStream.java:89)
     at oracle.jdevimpl.webapp.jsp.libraries.wl.WebLogicDeployerListener.prepared(WebLogicDeployerListener.java:146)
     at oracle.jdevimpl.deploy.fwk.ListenerSupport.firePrepared(ListenerSupport.java:178)
     at oracle.jdeveloper.deploy.common.AbstractDeployer.prepare(AbstractDeployer.java:78)
     at oracle.jdevimpl.deploy.fwk.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:430)
     at oracle.jdeveloper.deploy.DeploymentManager.deploy(DeploymentManager.java:209)
     at oracle.jdevimpl.deploy.common.ModulePackagerImpl.deployProfiles(ModulePackagerImpl.java:82)
     ... 26 more
#### Cannot run application BrowseEditApp due to error deploying to DefaultServer.
[Application BrowseEditApp stopped and undeployed from Server Instance DefaultServer]

Failure When Deploying EJB Project That Uses Library Onto Glassfish

Hi,
I have a multi project application that I am developing and I am having issues testing it. I have set up a EAR, WAR, EJB, and two library JARs. The EJB contains classes that use components from the library JARs or implement abstract classes from the library JARs. I have added the library JARs to the compile-time libraries of the EJB. I then also added the library JARs to the libraries of the EAR. However when I then go to deploy the EAR onto the Glassfish server I get this error, displayed in the Glassfish log: 
WARNING: Error in annotation processing: java.lang.NoClassDefFoundError: com/foo/sdk/core/AbstractClass 
WARNING: Error in annotation processing: java.lang.NoClassDefFoundError: com/foo/sdk/core/AbstractClass 
WARNING: Error in annotation processing: java.lang.NoClassDefFoundError: com/foo/sdk/core/AbstractClass 
WARNING: Error in annotation processing: java.lang.NoClassDefFoundError: com/foo/sdk/core/AbstractClas 
SEVERE: Class [ com/foo/sdk/core/InterfaceClass ] not found. Error while loading [ class com.foo2.BeanFooClass ] 
SEVERE: Exception while deploying the app [FooEAR] 
SEVERE: Invalid ejb jar [BeanFoo.jar]: it contains zero ejb. 
Note:
1. A valid ejb jar requires at least one session, entity (1.x/2.x style), or message-driven bean.
2. EJB3+ entity beans (@Entity) are POJOs and please package them as library jar.
3. If the jar file contains valid EJBs which are annotated with EJB component level annotations (@Stateless, @Stateful, @MessageDriven, @Singleton), please check server.log to see whether the annotations were processed properly.
java.lang.IllegalArgumentException: Invalid ejb jar [BeanFoo.jar]: it contains zero ejb.
Note:
1. A valid ejb jar requires at least one session, entity (1.x/2.x style), or message-driven bean.
2. EJB3+ entity beans (@Entity) are POJOs and please package them as library jar.
3. If the jar file contains valid EJBs which are annotated with EJB component level annotations (@Stateless, @Stateful, @MessageDriven, @Singleton), please check server.log to see whether the annotations were processed properly.
 at com.sun.enterprise.deployment.util.EjbBundleValidator.accept(EjbBundleValidator.java:76)
 at com.sun.enterprise.deployment.util.ApplicationValidator.accept(ApplicationValidator.java:128)
 at com.sun.enterprise.deployment.EjbBundleDescriptor.visit(EjbBundleDescriptor.java:730)
 at com.sun.enterprise.deployment.Application.visit(Application.java:1768)
 at com.sun.enterprise.deployment.archivist.ApplicationArchivist.validate(ApplicationArchivist.java:799)
 at com.sun.enterprise.deployment.archivist.ApplicationArchivist.openWith(ApplicationArchivist.java:277)
 at com.sun.enterprise.deployment.archivist.ApplicationFactory.openWith(ApplicationFactory.java:240)
 at org.glassfish.javaee.core.deployment.DolProvider.load(DolProvider.java:170)
 at org.glassfish.javaee.core.deployment.DolProvider.load(DolProvider.java:93)
 at com.sun.enterprise.v3.server.ApplicationLifecycle.loadDeployer(ApplicationLifecycle.java:826)
 at com.sun.enterprise.v3.server.ApplicationLifecycle.setupContainerInfos(ApplicationLifecycle.java:768)
 at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:368)
 at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240)
 at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:370)
 at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:355)
 at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:370)
 at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1067)
 at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:96)
 at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1247)
 at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1235)
 at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:465)
 at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:222)
 at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:168)
 at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:117)
 at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:234)
 at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:822)
 at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:719)
 at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1013)
 at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:225)
 at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
 at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
 at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
 at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
 at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
 at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
 at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
 at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
 at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
 at java.lang.Thread.run(Thread.java:679)
SEVERE: Exception while deploying the app [FooEAR] : Invalid ejb jar [FooBean.jar]: it contains zero ejb. 
Note:
1. A valid ejb jar requires at least one session, entity (1.x/2.x style), or message-driven bean.
2. EJB3+ entity beans (@Entity) are POJOs and please package them as library jar.
3. If the jar file contains valid EJBs which are annotated with EJB component level annotations (@Stateless, @Stateful, @MessageDriven, @Singleton), please check server.log to see whether the annotations were processed properly. 
I am using these technologies:
NetBeans IDE 7.0 for Java EE
Glassfish 3.1
I did read that putting the libraries in this directory: <glassfish_home>/domains/domain1/lib may resolve the problem, however there must be a better way.
Any help would be greatly appreciated!
Edited by: 866180 on Jun 15, 2011 2:32 PM

First of all, use a normal font when posting a question. This is just terrible to read.
You have multiple failures here. Did you actually read and try to understand the error?
java.lang.NoClassDefFoundError: com/foo/sdk/core/AbstractClassJava is not going to lie, this class is not on the classpath of the application. Either the jar is missing, the class is missing from the jar or you put the jar in the wrong place. Open up the ear using your favorite zip tool and check out its structure. What is the path to the jar inside it?
Also, open up the META-INF/manifest.mf file inside the EJB jar. Is there a class-path line in there? There shouldn't be!
A valid ejb jar requires at least one session, entity (1.x/2.x style), or message-driven bean. Apparently your EJB jar contains not a single EJB or MDB class. Did you forget some annotations perhaps?
Seems to me that your application compiles, but other than that it is very much broken.

Javax.naming.InvalidNameException when deploying JCA project to EP6

Similar Messages

Maybe you are looking for