EJBs not deploying
Hi, on my weblogic 5.1 whith sevicepack 7.0.
My EJBs are not deploying at startup.
The discriptors in the weblogic.properties are ok. The paths to the files
are ok. Classpath is ok.
Jars where on another WLS and working fine.
Usualy when a JAR file is not found, I should get a FileNotFound exception
at WLS boot. I dont even get this error. I made up a non existing file
hoping to at least get the FileNotFound exception, but it does not happen.
All I get is 0 files deployed.
Plz help.
Ejb jar file should be in the /applications directory to install at startup.
Melkor wrote:
Hi, on my weblogic 5.1 whith sevicepack 7.0.
My EJBs are not deploying at startup.
The discriptors in the weblogic.properties are ok. The paths to the files
are ok. Classpath is ok.
Jars where on another WLS and working fine.
Usualy when a JAR file is not found, I should get a FileNotFound exception
at WLS boot. I dont even get this error. I made up a non existing file
hoping to at least get the FileNotFound exception, but it does not happen.
All I get is 0 files deployed.
Plz help.
Similar Messages
-
Hello all,
Im running WLS 6.1 with SP3 evaluation version on Win2K Pro with Oracle
8.1.6 database.
Im new to Weblogic's deployment of EAR files. I am facing the following few
problems when i try to deply any cmp entity bean:
1. Though a common file that the EJB jar depends on, is present in the EAR
file, I get errors NoClassDefFound errors for that class. I read posts which
talk about how WLS is a bit different in this regard and that common files
will have to added separately to the classpath or bundled with the ejb jar.
However isnt that defeating the purpose of an EAR file?
2. I added the common class to the classpath in the startup script and
restarted weblogic. I get the following message on the console :
<Sep 10, 2002 10:22:55 AM BST> <Error> <J2EE> <Error deploying application
ejbDeployedCore121:
Unable to deploy EJB: Accbaladj from ejbDeployedCore121.jar:
The Container-Managed Persistence Entity EJB failed while creating its SQL
Type Map. The error was: null, Exception = null
I havent read any posts which answer this problem. I created my ear file
from scratch (compilation and ejbc of the source with the new WLS6.1 tools)
and am trying to deploy it but repeatedly failing.
3. Also could somebody point out a good online article/book/paper, which
talks about WLS 6.1 deployments of EAR files, rather like Websphere's
redbooks do about WAS?
If anybody has any idea of any of the above issues, I would be grateful if
you could mail in a reply.
TAR
PavanThe issues are resolved now.
1. This classpath entry problem was a bit mystifying. The manifest entry was
correct and it should have picked it up automatically. When i restarted the
server though, it started up properly.
2. The CMP problem was a bit more troublesome. I think it was because of an
incorrect datasource and connection pool properties. I used utils.Schema to
check my database connection and once i got the url and driver name
correctly it worked.
TAR,
Pavan -
I deplyed a simple EJB on S17AS. The server.log tells me it is deployed successful.
CORE3282: stdout: ejbCreate() on obj samples.jdbc.simple.ejb.GreeterDBBean@1017ca1
CORE3282: stdout: ejbCreate() on obj samples.jdbc.simple.ejb.GreeterDBBean@9d5793
LDR5010: All ejb(s) of [simpleEjb] loaded successfully!
The relevant simpleEjb.jar_verified.txt is as follows
Test Name : tests.ejb.ias.ASEjbJndiName
Test Assertion :
Test Description : PASSED [AS-EJB ejb] : jndi-name is simpleHome
However, the server log did not indicate the EJB is bound even if I set the log level to finest.
Therefore when I tried to access it, I get the following error
Exception in thread "main" javax.naming.NameNotFoundException: No object bound f
or java:comp/env/ejb/simpleHome
at com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.j
ava:116)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at HelloClient.main(HelloClient.java:61)
The client code is as follows
String JNDIName = "java:comp/env/ejb/simpleHome";
myGreeterDBHome = (GreeterDBHome) javax.rmi.PortableRemoteObject.narrow(
initContext.lookup(JNDIName), GreeterDBHome.class);
The sun-ejb-jar.xml is as follows
<?xml version="1.0" encoding="UTF-8"?>
<!--
Copyright 2002 Sun Microsystems, Inc. All rights reserved.
-->
<!DOCTYPE sun-ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Sun ONE Application Server 7.0 EJB 2.0//EN' 'http://www.sun.com/software/sunone/appserver/dtds/sun-ejb-jar_2_0-0.dtd'>
<sun-ejb-jar>
<enterprise-beans>
<name>simpleEjb.jar</name>
<ejb>
<ejb-name>simpleEJB</ejb-name>
<jndi-name>simpleHome</jndi-name>
<is-read-only-bean>false</is-read-only-bean>
<bean-pool>
<steady-pool-size>2</steady-pool-size>
<resize-quantity>5</resize-quantity>
<max-pool-size>20</max-pool-size>
<pool-idle-timeout-in-seconds>3600</pool-idle-timeout-in-seconds>
</bean-pool>
</ejb>
</enterprise-beans>
</sun-ejb-jar>
I tried to use lookup for both "java:comp/env/ejb/simpleHome" and "java:comp/env/simpleHome". None succeed.
Does anyone know why the ejb is deployed successful but not bound?
ShaHi, Parsuram,
I did restart the server and the error is the same.
Here is the sample code. I did not change them. Only the names in deployment descriptors are modified.
Below is the info.
*************************Remote Interface
Copyright � 2002 Sun Microsystems, Inc. All rights reserved.
package samples.jdbc.simple.ejb;
* Remote interface for the GreeterDBEJB. The remote interface defines all possible
* business methods for the bean. These are the methods going to be invoked remotely
* by the servlets, once they have a reference to the remote interface.
* Servlets generally take the help of JNDI to lookup the bean's home interface and
* then use the home interface to obtain references to the bean's remote interface.
public interface GreeterDB extends javax.ejb.EJBObject {
* Returns the greeting String such as "Good morning, John"
* @return the greeting String
public String getGreeting() throws java.rmi.RemoteException;
*************************Home Interface
Copyright � 2002 Sun Microsystems, Inc. All rights reserved.
package samples.jdbc.simple.ejb;
* Home interface for the GreeterDB EJB. Clients generally use home interface
* to obtain references to the bean's remote interface.
public interface GreeterDBHome extends javax.ejb.EJBHome {
* Gets a reference to the remote interface to the GreeterDBBean.
* @exception throws CreateException and RemoteException.
public GreeterDB create() throws java.rmi.RemoteException, javax.ejb.CreateException;
*************************Bean Class
Copyright � 2002 Sun Microsystems, Inc. All rights reserved.
package samples.jdbc.simple.ejb;
import java.util.*;
import java.io.*;
* A simple stateless session bean which generates the greeting string for jdbc-simple
* application. This bean implements the business method as declared by the remote interface.
public class GreeterDBBean implements javax.ejb.SessionBean {
private javax.ejb.SessionContext m_ctx = null;
* Sets the session context. Required by EJB spec.
* @param ctx A SessionContext object.
public void setSessionContext(javax.ejb.SessionContext ctx) {
m_ctx = ctx;
* Creates a bean. Required by EJB spec.
public void ejbCreate() {
System.out.println("ejbCreate() on obj " + this);
* Removes a bean. Required by EJB spec.
public void ejbRemove() {
System.out.println("ejbRemove() on obj " + this);
* Loads the state of the bean from secondary storage. Required by EJB spec.
public void ejbActivate() {
System.out.println("ejbActivate() on obj " + this);
* Keeps the state of the bean to secondary storage. Required by EJB spec.
public void ejbPassivate() {
System.out.println("ejbPassivate() on obj " + this);
* Required by EJB spec.
public void GreeterDBBean() {
* Returns the Greeting String based on the time
* @return the Greeting String.
public String getGreeting() throws java.rmi.RemoteException {
System.out.println("GreeterDB EJB is determining message...");
String message = null;
Calendar calendar = new GregorianCalendar();
int currentHour = calendar.get(Calendar.HOUR_OF_DAY);
if(currentHour < 12) message = "morning";
else {
if( (currentHour >= 12) &&
(calendar.get(Calendar.HOUR_OF_DAY) < 18)) message = "afternoon";
else message = "evening";
System.out.println("- Message determined successfully");
return message;
************************ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<!--
Copyright 2002 Sun Microsystems, Inc. All rights reserved.
-->
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 1.1//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
<ejb-jar>
<enterprise-beans>
<session>
<display-name>simple</display-name>
<ejb-name>simpleEJB</ejb-name>
<home>samples.jdbc.simple.ejb.GreeterDBHome</home>
<remote>samples.jdbc.simple.ejb.GreeterDB</remote>
<ejb-class>samples.jdbc.simple.ejb.GreeterDBBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Bean</transaction-type>
</session>
</enterprise-beans>
</ejb-jar>
************************sun-ejb-jar.xml
<sun-ejb-jar>
<enterprise-beans>
<name>simpleEjb.jar</name>
<ejb>
<ejb-name>simpleEJB</ejb-name>
<jndi-name>ejb/simpleHome</jndi-name>
<is-read-only-bean>false</is-read-only-bean>
<bean-pool>
<steady-pool-size>2</steady-pool-size>
<resize-quantity>5</resize-quantity>
<max-pool-size>20</max-pool-size>
<pool-idle-timeout-in-seconds>3600</pool-idle-timeout-in-seconds>
</bean-pool>
</ejb>
</enterprise-beans>
</sun-ejb-jar>
************************Assemble Info
C:\Sun\AppServer7\samples\jdbc\simple\assemble\jar>jar cvf simpleEjb.jar *
added manifest
ignoring entry META-INF/
adding: META-INF/ejb-jar.xml(in = 710) (out= 350)(deflated 50%)
adding: META-INF/sun-ejb-jar.xml(in = 803) (out= 424)(deflated 47%)
adding: samples/(in = 0) (out= 0)(stored 0%)
adding: samples/jdbc/(in = 0) (out= 0)(stored 0%)
adding: samples/jdbc/simple/(in = 0) (out= 0)(stored 0%)
adding: samples/jdbc/simple/ejb/(in = 0) (out= 0)(stored 0%)
adding: samples/jdbc/simple/ejb/GreeterDB.class(in = 210) (out= 168)(deflated 20%)
adding: samples/jdbc/simple/ejb/GreeterDBBean.class(in = 1441) (out= 734)(deflated 49%)
adding: samples/jdbc/simple/ejb/GreeterDBHome.class(in = 257) (out= 177)(deflated 31%)
C:\Sun\AppServer7\samples\jdbc\simple\assemble\jar>jar tf simpleEJB.jar
META-INF/
META-INF/MANIFEST.MF
META-INF/ejb-jar.xml
META-INF/sun-ejb-jar.xml
samples/
samples/jdbc/
samples/jdbc/simple/
samples/jdbc/simple/ejb/
samples/jdbc/simple/ejb/GreeterDB.class
samples/jdbc/simple/ejb/GreeterDBBean.class
samples/jdbc/simple/ejb/GreeterDBHome.class
******************************** Deployment Info
server1: Applications: EJB Modules: simpleEjb
EJB Module Name: simpleEjb
Location: C:\Sun\AppServer7\domains\domain1\server1\applications\j2ee-modules\simpleEjb_1
******************************** simplEJB.jar_verified.txt
STATIC VERIFICATION RESULTS
NUMBER OF FAILURES/WARNINGS/ERRORS
# of Failures : 0
# of Warnings : 1
# of Errors : 0
Test Name : tests.ejb.ias.ASEjbJndiName
Test Assertion :
Test Description : PASSED [AS-EJB ejb] : jndi-name is ejb/simpleHome
WARNINGS :
Test Name : tests.ejb.businessmethod.BusinessMethodException
Test Assertion : Enterprise bean business method throws RemoteException test
Test Description : For [ module_simpleEjb#simpleEjb#simpleEJB ]
For EJB Class [ samples.jdbc.simple.ejb.GreeterDBBean ] business method [ getGreeting ]
Error: Compatibility Note: A public business method [ getGreeting ] was found, but EJB 1.0 allowed the business methods to throw the java.rmi.RemoteException to indicate a non-application exception. This practice is deprecated in EJB 1.1 ---an EJB 1.1 compliant enterprise bean should throw the javax.ejb.EJBException or another RuntimeException to indicate non-application exceptions to the Container.
*********************** server log (no binding info)
[05/Jan/2003:17:07:19] FINE ( 1760): [EJBClassPathUtils] EJB Class Path for [simpleEjb] is ...
[C:\Sun\AppServer7\domains\domain1\server1\applications\j2ee-modules\simpleEjb_1, C:\Sun\AppServer7\domains\domain1\server1\generated\ejb\j2ee-modules\simpleEjb]
[05/Jan/2003:17:07:20] FINE ( 1760): Loading StatelessSessionContainer...
[05/Jan/2003:17:07:20] FINE ( 1760): [BaseContainer] Registered EJB [simpleEJB] with MBeanServer under name [ias:instance-name=server1,mclass=stateless-session-bean,name=simpleEJB,root=root,standalone-ejb-module=simpleEjb,type=monitor]
[05/Jan/2003:17:07:20] FINE ( 1760): main: name = "samples.jdbc.simple.ejb._GreeterDBBean_RemoteHomeImpl_Tie", codebase = ""
[05/Jan/2003:17:07:20] FINE ( 1760): main: name = "samples.jdbc.simple.ejb._GreeterDBHome_Stub", codebase = ""
[05/Jan/2003:17:07:20] FINE ( 1760): main: name = "samples.jdbc.simple.ejb._GreeterDBHome_Stub", codebase = ""
[05/Jan/2003:17:07:20] FINE ( 1760): main: name = "samples.jdbc.simple.ejb._GreeterDBBean_EJBObjectImpl_Tie", codebase = ""
[05/Jan/2003:17:07:20] FINE ( 1760): main: name = "samples.jdbc.simple.ejb._GreeterDB_Stub", codebase = ""
[05/Jan/2003:17:07:20] FINE ( 1760): [Pool-ejb/simpleHome]: Added PoolResizeTimerTask...
[05/Jan/2003:17:07:20] FINE ( 1760): Created container with uinque id: 68275827784351744
[05/Jan/2003:17:07:20] FINE ( 1760): Application deployment successful : com.sun.ejb.containers.StatelessSessionContainer@1083717
[05/Jan/2003:17:07:20] INFO ( 1760): LDR5010: All ejb(s) of [simpleEjb] loaded successfully!
[05/Jan/2003:17:07:22] FINE ( 1760): Started 48 request processing threads
[05/Jan/2003:17:07:22] INFO ( 1760): CORE3274: successful server startup
[05/Jan/2003:17:07:22] FINE ( 1760): The server is now ready to process requests
[05/Jan/2003:17:07:22] INFO ( 1760): CORE3282: stdout: ejbCreate() on obj samples.jdbc.simple.ejb.GreeterDBBean@10613aa
[05/Jan/2003:17:07:22] INFO ( 1760): CORE3282: stdout: ejbCreate() on obj samples.jdbc.simple.ejb.GreeterDBBean@1f52460
[05/Jan/2003:17:07:22] INFO ( 1760): CORE5053: Application onReady complete.
*********************** Client class
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import java.util.Properties;
import java.util.Hashtable;
import javax.ejb.*;
import java.sql.*;
import javax.sql.*;
import samples.jdbc.simple.ejb.*;
public class HelloClient {
public static void main(String[] args) throws Exception {
javax.ejb.Handle beanHandle;
GreeterDBHome myGreeterDBHome;
GreeterDB myGreeterDBRemote;
InitialContext initContext = null;
Hashtable env = new java.util.Hashtable(1);
initContext = getContextInfo();
String JNDIName = "java:comp/env/ejb/simpleHome";
System.out.println("- Looking up: " + JNDIName);
myGreeterDBHome = (GreeterDBHome) javax.rmi.PortableRemoteObject.narrow(initContext.lookup(JNDIName), GreeterDBHome.class);
myGreeterDBRemote = myGreeterDBHome.create();
String theMessage = myGreeterDBRemote.getGreeting();
myGreeterDBRemote.remove();
public static InitialContext getContextInfo() {
InitialContext ctx = null;
String url = "iiop://1st:3700";
String fac = "com.sun.enterprise.naming.SerialInitContextFactory";
try {
Properties props = new Properties();
props.put(Context.INITIAL_CONTEXT_FACTORY, fac);
props.put(Context.PROVIDER_URL, url);
ctx = new InitialContext(props);
catch (NamingException ne){
System.out.println("We were unable to get a connection to " +
" the application server at " + url);
ne.printStackTrace();
return ctx;
*********************** Running Client from command line
C:\Sun\AppServer7\samples\jdbc\simple\assemble\jar>java HelloClient
- Looking up: java:comp/env/ejb/simpleHome
Exception in thread "main" javax.naming.NameNotFoundException: No object bound for java:comp/env/ejb/simpleHome
at com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.java:116)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at HelloClient.main(HelloClient.java:34) -
As I mentioned in subject, I am just wondering Whether the java component (Not
ejb, not servlet) can be deployed in App Server and get the services provided
by App Server or not?Nevermind folks - I got it to work. All my configuration was correct; I had other issues with the ejb-jar file that the verifier informed me of (my previous deployments were with the verifier turned-off).
-
EJB Deployment Descriptors not deploying to WLS
Hi,
We're using Eclipse 3.4.1 with the OEPE to target WLS 10.3 with Java 6/JEE 1.4 on a Windows XP Professional development machine.
We have an EJB 2.1 project as part of a larger EAR. The beans (all stateless session beans) and associated interfaces and deployment descriptors within are maintained manually for internal reasons; we do not rely on EJBGen or XDoclet or anything like that to manage these. We are NOT using any annotations in these EJBs, as is the default when you create a bean. Instead we rely on weblogic-ejb-jar.xml and ejb-jar.xml.
We're having an issue where deploying to the local Weblogic server instance fails with the following error displaying in the Eclipse console:
<Dec 19, 2008 9:21:13 AM CST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'xxxxxxx'.>
<Dec 19, 2008 9:21:13 AM CST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: Exception preparing module: EJBModule(xxxxxxxEJB.jar)
[EJB:011023]An error occurred while reading the deployment descriptor. The error was:
No EJBs found in the ejb-jar file {0}. Please ensure the ejb-jar contains EJB declarations via an ejb-jar.xml deployment descriptor or at least one class annotated with the @Stateless, @Stateful or @MessageDriven EJB annotation..
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:452)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
Truncated. see log file for complete stacktrace
java.io.IOException: No EJBs found in the ejb-jar file {0}. Please ensure the ejb-jar contains EJB declarations via an ejb-jar.xml deployment descriptor or at least one class annotated with the @Stateless, @Stateful or @MessageDriven EJB annotation.
at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescriptorReaderImpl.java:199)
at weblogic.ejb.spi.EjbDescriptorFactory.createReadOnlyDescriptorFromJarFile(EjbDescriptorFactory.java:93)
at weblogic.ejb.container.deployer.EJBModule.loadEJBDescriptor(EJBModule.java:1198)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:380)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
Truncated. see log file for complete stacktrace
We DO have multiple beans defined, but it seems that WLS just isn't aware of them due to the lack of a deployment descriptor. It appears that Eclipse/OEPE is not copying the ejb-jar.xml and weblogic-ejb-jar.xml files to the build directory when the project is build:
xxxxxEJB
|-- ejbModule
|.....|-- META-INF
|.....|.....|-- ejb-jar.xml
|.....|.....|-- MANIFEST.MF
|.....|.....|-- weblogic-ejb-jar.xml
|.....|-- com (etc., .java files)
|-- build
......|-- classes
............|-- META-INF
............|......|-- MANIFEST.MF
............|-- com (etc, .class files)
Other notes:
- Cleaning the project does not help.
- Starting a new workspace does not help.
- It works under Eclipse 3.3.2 with the Europa version of OEPE.
- Explicitly exporting an EJB Jar file DOES include the two deployment descriptors (just not deploying to the embedded test server we've defined in our Servers view)
Any ideas? This seems like either a bug in the OEPE, or maybe WTP.Yes, I have a simple EJB2.1 project with hand-crafted EJB remote/home interfaces/classes and deployment descriptors. Also tried Clean/Rebuild and manually delete
files under /build/classes.
Here are my descriptors files:
ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar id="ejb-jar_ID" version="2.1" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd">
<display-name>TestEJB</display-name>
<enterprise-beans>
<session>
<display-name>HelloSessioin</display-name>
<ejb-name>HelloSession</ejb-name>
<home>sessions.HelloSessionHome</home>
<remote>sessions.HelloSession</remote>
<ejb-class>sessions.HelloSessionBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Bean</transaction-type>
<security-identity>
<use-caller-identity/>
</security-identity>
</session>
</enterprise-beans>
</ejb-jar>
weblogic-ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-ejb-jar
xmlns="http://www.bea.com/ns/weblogic/90" xmlns:j2ee="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-ejb-jar.xsd">
<weblogic-enterprise-bean>
<ejb-name>HelloSession</ejb-name>
<stateless-session-descriptor>
</stateless-session-descriptor>
<jndi-name>ejb.HelloSessionRemoteHome</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
Did you check if there is any error/warning in Error Log view? -
Hello JDev Team,
I want to use SSL encryption and authentication in my InfoSwing BC4J Oracle8i application.
For Local Deployment it's quite transparent you just define appropriate LocalConnection class and SSL works fine.
But for EJB/8i Deployment it's not that clear. As I understand EjbConnection class can accept user/password authentication only.
Do I have to extend oracle.dacf.dataset.connections.Connection class and create my own SSL-oriented Connection with my own setConnectionSpecificEnvs method? Is that a possibility?
Could you please give me some directions on this case?
Thanks,
Victor
nullPlease check the "How to's" in the JDeveloper section of OTN (http://otn.oracle.com). That should shed some light.
Happy researching,
Rajesh -
Beans do not deploy under Service Pack 12
Hello, we recently upgraded our Weblogic 5.1 from Service Pack 10 to
Service Pack 12. All the beans compile and jar fine, and most deploy
ok apart from a few that give the exception given below. Does anyone
know anything in SP11 or SP12 that might cause this behaviour?
Thanks!
Z
Wed Jul 24 11:26:41 GMT+00:00 2002:<E> <EJB> Could not deploy:
'D:/FM/SolstraV2/
lib/reports_content.jar': file is not a valid jar file, or does not
contain a valid bean
weblogic.ejb.common.DeploymentException: DeploymentException opening
JAR file D:
\FM\SolstraV2\lib\reports_content.jar; nested exception is:
weblogic.ejb.deployment.JarLoadException - with nested
exception:
[weblogic.ejb.common.DeploymentException: Problem creating deployment
D:/FM/Sols
traV2/lib/reports_content.jar from
D:\FM\SolstraV2\lib\reports_content.jar; nest
ed exception is:
java.lang.StringIndexOutOfBoundsException: String index out of
range: -2
weblogic.ejb.common.DeploymentException: Problem creating deployment
D:/FM/Solst
raV2/lib/reports_content.jar from
D:\FM\SolstraV2\lib\reports_content.jar; neste
d exception is:
java.lang.StringIndexOutOfBoundsException: String index out of
range: -2
java.lang.StringIndexOutOfBoundsException: String index out of range:
-2
at java.lang.String.substring(String.java, Compiled Code)
at java.lang.String.substring(String.java, Compiled Code)
at weblogic.ejb.internal.EJBJarLoader.computeExcludeForInfo(EJBJarLoader
.java, Compiled Code)
at weblogic.ejb.internal.EJBJarLoader.computeExclude(EJBJarLoader.java,
Compiled Code)
at weblogic.ejb.internal.EJBJarLoader.initialize(EJBJarLoader.java:125)
at weblogic.ejb.internal.EJBJarLoader.<init>(EJBJarLoader.java:88)
at weblogic.ejb.internal.EJBJarDeployment.setupJar(EJBJarDeployment.java
, Compiled Code)
at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:21
1)
at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:18
2)
at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:16
4)
at weblogic.ejb.internal.EJBDeploymentImpl.<init>(EJBDeploymentImpl.java
:172)
at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:1
22)
at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:1
12)
at weblogic.ejb.internal.EJBManagerImpl.deploy(EJBManagerImpl.java:311)
at weblogic.ejb.internal.EJBManagerImpl.deployBeans(EJBManagerImpl.java,
Compiled Code)
at weblogic.ejb.internal.EJBManagerImpl.<init>(EJBManagerImpl.java:247)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java, Compiled Code)
at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:879)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:140)
at weblogic.Server.main(Server.java, Compiled Code)
at com.solstra.SolstraWeblogicServer.main(SolstraWeblogicServer.java:23)Hello, we recently upgraded our Weblogic 5.1 from Service Pack 10 to
Service Pack 12. All the beans compile and jar fine, and most deploy
ok apart from a few that give the exception given below. Does anyone
know anything in SP11 or SP12 that might cause this behaviour?
Thanks!
Z
Wed Jul 24 11:26:41 GMT+00:00 2002:<E> <EJB> Could not deploy:
'D:/FM/SolstraV2/
lib/reports_content.jar': file is not a valid jar file, or does not
contain a valid bean
weblogic.ejb.common.DeploymentException: DeploymentException opening
JAR file D:
\FM\SolstraV2\lib\reports_content.jar; nested exception is:
weblogic.ejb.deployment.JarLoadException - with nested
exception:
[weblogic.ejb.common.DeploymentException: Problem creating deployment
D:/FM/Sols
traV2/lib/reports_content.jar from
D:\FM\SolstraV2\lib\reports_content.jar; nest
ed exception is:
java.lang.StringIndexOutOfBoundsException: String index out of
range: -2
weblogic.ejb.common.DeploymentException: Problem creating deployment
D:/FM/Solst
raV2/lib/reports_content.jar from
D:\FM\SolstraV2\lib\reports_content.jar; neste
d exception is:
java.lang.StringIndexOutOfBoundsException: String index out of
range: -2
java.lang.StringIndexOutOfBoundsException: String index out of range:
-2
at java.lang.String.substring(String.java, Compiled Code)
at java.lang.String.substring(String.java, Compiled Code)
at weblogic.ejb.internal.EJBJarLoader.computeExcludeForInfo(EJBJarLoader
.java, Compiled Code)
at weblogic.ejb.internal.EJBJarLoader.computeExclude(EJBJarLoader.java,
Compiled Code)
at weblogic.ejb.internal.EJBJarLoader.initialize(EJBJarLoader.java:125)
at weblogic.ejb.internal.EJBJarLoader.<init>(EJBJarLoader.java:88)
at weblogic.ejb.internal.EJBJarDeployment.setupJar(EJBJarDeployment.java
, Compiled Code)
at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:21
1)
at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:18
2)
at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:16
4)
at weblogic.ejb.internal.EJBDeploymentImpl.<init>(EJBDeploymentImpl.java
:172)
at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:1
22)
at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:1
12)
at weblogic.ejb.internal.EJBManagerImpl.deploy(EJBManagerImpl.java:311)
at weblogic.ejb.internal.EJBManagerImpl.deployBeans(EJBManagerImpl.java,
Compiled Code)
at weblogic.ejb.internal.EJBManagerImpl.<init>(EJBManagerImpl.java:247)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java, Compiled Code)
at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:879)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:140)
at weblogic.Server.main(Server.java, Compiled Code)
at com.solstra.SolstraWeblogicServer.main(SolstraWeblogicServer.java:23) -
Dynamic update of EJB/Web deployment descriptors
In 8.1SP3, is there any provision to allow for dynamic update of EJB/Web deployment descriptors? I'm specifically looking at env var changes.
I noticed that there are some mentions of the ability to dynamically update deployment descriptors, but it appears that the general facility has been deprecated, and they've incorporated all of the WebLogic-specific descriptor information directly into the console.
When I dig through the JMX namespace and some of the MBean classes, I also see mentions of "deployment descriptor editors", but it's not clear how to utilize that.
I'm aware of the fact that my application would have to be aware of possible dynamic updates to the descriptors, so I'd have to be able to implement some sort of listener for that.I have the same question but for a different purpose. I am part of a hosting group and we have app teams that have defined init-params in the web.xml that have to be changed as the app is promoted up through test environments and ultimately to production - only we need to be able to do this WITHOUT "cracking open" the archive.
I was hoping to be able to script something to do the update after deployment.
So any help at all would be appreciated. In the meantime will continue to poke around in the WLST and MBean docs.
Thanks,
Ed -
EJB Application Deployment Error
Hi,
I am trying to deploy an J2EE application ear, which contains both EJB modules and a WEB module, on NW 2004's SP10. Here is the error message that is written out to the defaultTrace file in the server logs directory:
#1.5#00137262AE6E006500000035000012CC000438363739A6D9#1187705412772#com.sap.engine.services.deploy##com.sap.engine.services.deploy#Administrator#27239####38a7ab104ff011dca12600137262ae6e#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#/System/Server#Java#deploy_5029##Exception in operation deploy with application champtech.com/COINejb.#2#deploy#champtech.com/COINejb#
#1.5#00137262AE6E006500000036000012CC000438363739B7D8#1187705412788#com.sap.engine.services.deploy##com.sap.engine.services.deploy#Administrator#27239####38a7ab104ff011dca12600137262ae6e#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception in operation deploy with application champtech.com/COINejb.
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:394)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:294)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)
at com.sap.engine.services.deploy.server.DeployRuntimeControlImpl.deploy(DeployRuntimeControlImpl.java:262)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Cannot deploy application champtech.com/COINejb.
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:330)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
... 33 more
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application champtech.com/COINejb in container EJBContainer.
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:612)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
... 35 more
Caused by: java.lang.NullPointerException
at com.sap.engine.services.ejb.deploy.verifier.entity.EntityBMPCheck.checkEJBLocalHome(EntityBMPCheck.java:83)
at com.sap.engine.services.ejb.deploy.verifier.entity.EntityBMPCheck.check(EntityBMPCheck.java:63)
at com.sap.engine.services.ejb.deploy.verifier.Verifier.checkBean(Verifier.java:95)
at com.sap.engine.services.ejb.deploy.verifier.Verifier.check(Verifier.java:46)
at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:254)
at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2161)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
... 36 more
#1.5#00137262AE6E006500000038000012CC00043836373AA34F#1187705412835#com.sap.engine.services.deploy##com.sap.engine.services.deploy#Administrator#27239####38a7ab104ff011dca12600137262ae6e#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#/System/Server#Plain###
Operation deploy over application champtech.com/COINejb finished with errors on server 9460450. For more detailed information see traces of Deploy Service.#
#1.5#00137262AE6E00650000003B000012CC00043836373ACAFD#1187705412850#com.sap.engine.services.deploy##com.sap.engine.services.deploy#Administrator#27239####38a7ab104ff011dca12600137262ae6e#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#/System/Server#Java#deploy_5047##Cannot deploy application champtech.com/COINejb.#1#champtech.com/COINejb#
#1.5#00137262AE6E00650000003C000012CC00043836373ACCCB#1187705412850#com.sap.engine.services.deploy##com.sap.engine.services.deploy#Administrator#27239####38a7ab104ff011dca12600137262ae6e#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Cannot deploy application champtech.com/COINejb.
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:330)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)
at com.sap.engine.services.deploy.server.DeployRuntimeControlImpl.deploy(DeployRuntimeControlImpl.java:262)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application champtech.com/COINejb in container EJBContainer.
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:612)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
... 35 more
Caused by: java.lang.NullPointerException
at com.sap.engine.services.ejb.deploy.verifier.entity.EntityBMPCheck.checkEJBLocalHome(EntityBMPCheck.java:83)
at com.sap.engine.services.ejb.deploy.verifier.entity.EntityBMPCheck.check(EntityBMPCheck.java:63)
at com.sap.engine.services.ejb.deploy.verifier.Verifier.checkBean(Verifier.java:95)
at com.sap.engine.services.ejb.deploy.verifier.Verifier.check(Verifier.java:46)
at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:254)
at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2161)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
... 36 more
#1.5#00137262AE6E00650000003E000012CC00043836373ADBB9#1187705412850#com.sap.engine.services.jmx.MBeanServerInvoker##com.sap.engine.services.jmx.MBeanServerInvoker#Administrator#27239####38a7ab104ff011dca12600137262ae6e#SAPEngine_Application_Thread[impl:3]_34##0#0#Warning#1#/System/Server#Java###Exception occurred while processing external JMX request [ JMX request (java) v1.0 len: 551 | src: 2 target-node: 9460450 req: invoke params-number: 4 params-bytes: 0 | :name=deploy,j2eeType=SAP_J2EEServiceRuntimePerNode,SAP_J2EEClusterNode=9460450,SAP_J2EECluster="" deploy [Ljava.lang.Object;@67beb7 [Ljava.lang.String;@11a0ebf ]
[EXCEPTION]
#1#javax.management.MBeanException: Exception invoking method deploy
at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:80)
at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.rmi.RemoteException: Cannot deploy application champtech.com/COINejb..
Reason: Exception during generation of components of application champtech.com/COINejb in container EJBContainer.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application champtech.com/COINejb in container EJBContainer.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:567)
at com.sap.engine.services.deploy.server.DeployRuntimeControlImpl.deploy(DeployRuntimeControlImpl.java:262)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
... 24 more
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application champtech.com/COINejb in container EJBContainer.
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:612)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)
... 30 more
Caused by: java.lang.NullPointerException
at com.sap.engine.services.ejb.deploy.verifier.entity.EntityBMPCheck.checkEJBLocalHome(EntityBMPCheck.java:83)
at com.sap.engine.services.ejb.deploy.verifier.entity.EntityBMPCheck.check(EntityBMPCheck.java:63)
at com.sap.engine.services.ejb.deploy.verifier.Verifier.checkBean(Verifier.java:95)
at com.sap.engine.services.ejb.deploy.verifier.Verifier.check(Verifier.java:46)
at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:254)
at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2161)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
... 36 more
caused by -
java.rmi.RemoteException: Cannot deploy application champtech.com/COINejb..
Reason: Exception during generation of components of application champtech.com/COINejb in container EJBContainer.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application champtech.com/COINejb in container EJBContainer.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:567)
at com.sap.engine.services.deploy.server.DeployRuntimeControlImpl.deploy(DeployRuntimeControlImpl.java:262)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application champtech.com/COINejb in container EJBContainer.
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:612)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)
... 30 more
Caused by: java.lang.NullPointerException
at com.sap.engine.services.ejb.deploy.verifier.entity.EntityBMPCheck.checkEJBLocalHome(EntityBMPCheck.java:83)
at com.sap.engine.services.ejb.deploy.verifier.entity.EntityBMPCheck.check(EntityBMPCheck.java:63)
at com.sap.engine.services.ejb.deploy.verifier.Verifier.checkBean(Verifier.java:95)
at com.sap.engine.services.ejb.deploy.verifier.Verifier.check(Verifier.java:46)
at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:254)
at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2161)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
... 36 more
It seems that from the exception message that there is an issue loading or locating the EJB local home interface, however I am not exactly sure what is going as I can't find any additional information on this issue in the NW logs. I have a previous ear that will deploy. This earlier ear file only contains EJB remote interfaces. In the newer ear I have implemented and added the EJB local interface and believe that I have the correct configurations, since the NW IDE doesn't show any errors and is able to generate the EJB archieves and the deployment EAR.
Any assistance or help would be greatly appreciated as I have hit a wall on this.
ThanksHere is one of my EJB modules ejb-jar.xml configuration files:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN"
"http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
<description>EJB JAR description</description>
<display-name>EJB JAR</display-name>
<enterprise-beans>
<session>
<ejb-name>AlertFacadeBean</ejb-name>
<home>com.champtech.coin.alerts.session.remote.RemoteAlertFacadeHome</home>
<remote>com.champtech.coin.alerts.session.remote.RemoteAlertFacade</remote>
<local-home>com.champtech.coin.alerts.session.local.LocalAlertFacadeHome</local-home>
<local>com.champtech.coin.alerts.session.local.LocalAlertFacade</local>
<ejb-class>com.champtech.coin.alerts.session.AlertFacadeBean</ejb-class>
<session-type>Stateful</session-type>
<transaction-type>Container</transaction-type>
</session>
<entity>
<ejb-name>AlertBean</ejb-name>
<home>com.champtech.coin.alerts.entity.remote.RemoteAlertHome</home>
<remote>com.champtech.coin.alerts.entity.remote.RemoteAlert</remote>
<local-home>com.champtech.coin.alerts.entity.local.LocalAlertHome</local-home>
<local>com.champtech.coin.alerts.entity.local.LocalAlert</local>
<ejb-class>com.champtech.coin.alerts.entity.AlertBean</ejb-class>
<persistence-type>Bean</persistence-type>
<prim-key-class>java.lang.Long</prim-key-class>
<reentrant>False</reentrant>
</entity>
<entity>
<ejb-name>AlertInstanceBean</ejb-name>
<home>com.champtech.coin.alerts.entity.remote.RemoteAlertInstanceHome</home>
<remote>com.champtech.coin.alerts.entity.remote.RemoteAlertInstance</remote>
<local-home>com.champtech.coin.alerts.entity.local.LocalAlertInstanceHome</local-home>
<local>com.champtech.coin.alerts.entity.local.LocalAlertInstance</local>
<ejb-class>com.champtech.coin.alerts.entity.AlertInstanceBean</ejb-class>
<persistence-type>Bean</persistence-type>
<prim-key-class>java.lang.Long</prim-key-class>
<reentrant>False</reentrant>
</entity>
<entity>
<ejb-name>AlertLogBean</ejb-name>
<home>com.champtech.coin.alerts.entity.remote.RemoteAlertLogHome</home>
<remote>com.champtech.coin.alerts.entity.remote.RemoteAlertLog</remote>
<local-home>com.champtech.coin.alerts.entity.local.LocalAlertLogHome</local-home>
<local>com.champtech.coin.alerts.entity.local.LocalAlertLog</local>
<ejb-class>com.champtech.coin.alerts.entity.AlertLogBean</ejb-class>
<persistence-type>Bean</persistence-type>
<prim-key-class>java.lang.Long</prim-key-class>
<reentrant>False</reentrant>
</entity>
<entity>
<ejb-name>SubscriptionBean</ejb-name>
<home>com.champtech.coin.alerts.entity.remote.RemoteSubscriptionHome</home>
<remote>com.champtech.coin.alerts.entity.remote.RemoteSubscription</remote>
<local-home>com.champtech.coin.alerts.entity.local.LocalSubscriptionHome</local-home>
<local>com.champtech.coin.alerts.entity.local.LocalSubscription</local>
<ejb-class>com.champtech.coin.alerts.entity.SubscriptionBean</ejb-class>
<persistence-type>Bean</persistence-type>
<prim-key-class>java.lang.Object</prim-key-class>
<reentrant>False</reentrant>
</entity>
</enterprise-beans>
</ejb-jar> -
Could not deploy an JAR archive because JNDI name is already in use.
Hi,
I have a problem.
When the WebLogic server starts, it cannot deploy an EJB application because a
JDNI name is already in use.
What can I do to unregister this name ?
If it is possible a better description is step by step.
The WebLogic server, when starts, prints the next lines:
<18/01/2002 12:35:24 PM GMT-06:00> <Error> <J2EE> <Error deploying EJB Component
: sui_ejb
weblogic.ejb20.EJBDeploymentException: Error deploying stateless EJB; nested exc
eption is:
javax.naming.NameAlreadyBoundException: Can't rebind anything but a repl
ica-aware stub to a name that is currently bound to a replica-aware stub; remain
ing name ''
javax.naming.NameAlreadyBoundException: Can't rebind anything but a replica-awar
e stub to a name that is currently bound to a replica-aware stub; remaining name
<<no stack trace available>>
>
<18/01/2002 12:35:24 PM GMT-06:00> <Error> <J2EE> <Error deploying application
s
ui_ejb: Could not deploy: 'sui_ejb.jar': JNDI name in use
>
<18/01/2002 12:35:26 PM GMT-06:00> <Notice> <WebLogicServer> <WebLogic Server
st
arted>
<18/01/2002 12:35:26 PM GMT-06:00> <Notice> <WebLogicServer> <ListenThread liste
ning on port 7001, ip address 157.253.174.63>
<18/01/2002 12:35:26 PM GMT-06:00> <Notice> <WebLogicServer> <SSLListenThread
li
stening on port 7002, ip address 157.253.174.63>
In advance, thanks for your help.
- Ricardo De la Rosa (Colombia)Cameron,
I resolve the problem using your clues.
The problem was that I include the ejb.jar file in the .ear file and I copy the
ejb.jar file in the applications directory and it is redundant.
It is only needed to include the ejb.jar file in the .ear file.
Best regards,
- Ricardo (Colombia)
"Cameron Purdy" <[email protected]> wrote:
In that case, check the config.xml and make sure that the app isn't being
deployed in ways that you weren't expecting ... just double-check
everything. Sometimes the console does weird things.
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you should be!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"Ricardo De la Rosa" <[email protected]> wrote in message
news:[email protected]...
Cameron,
I think that it isn't the problem because yesterday it deploys correctly,and
today I didn't touch the compilation options.
Thank you !
If you have another idea I really appreciate it.
Best regards,
- Ricardo (Colombia)
"Cameron Purdy" <[email protected]> wrote:
Hi Ricardo,
Certain items are not replica-aware, such as JMS queues, so they must
be
deployed to a single target in the cluster. It sounds like your EJB
is
compiled with an option that turned off the replica aware stubs.
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you shouldbe!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"Ricardo De la Rosa" <[email protected]> wrote in message
news:[email protected]...
Hi,
I have a problem.
When the WebLogic server starts, it cannot deploy an EJB applicationbecause a
JDNI name is already in use.
What can I do to unregister this name ?
If it is possible a better description is step by step.
The WebLogic server, when starts, prints the next lines:
<18/01/2002 12:35:24 PM GMT-06:00> <Error> <J2EE> <Error deployingEJB
Component
: sui_ejb
weblogic.ejb20.EJBDeploymentException: Error deploying stateless
EJB;
nested exc
eption is:
javax.naming.NameAlreadyBoundException: Can't rebind anythingbut
a repl
ica-aware stub to a name that is currently bound to a replica-awarestub;
remain
ing name ''
javax.naming.NameAlreadyBoundException: Can't rebind anything but
a
replica-awar
e stub to a name that is currently bound to a replica-aware stub;remaining name
<<no stack trace available>>
>
<18/01/2002 12:35:24 PM GMT-06:00> <Error> <J2EE> <Error deployingapplication
s
ui_ejb: Could not deploy: 'sui_ejb.jar': JNDI name in use
>
<18/01/2002 12:35:26 PM GMT-06:00> <Notice> <WebLogicServer> <WebLogicServer
st
arted>
<18/01/2002 12:35:26 PM GMT-06:00> <Notice> <WebLogicServer>
<ListenThread
liste
ning on port 7001, ip address 157.253.174.63>
<18/01/2002 12:35:26 PM GMT-06:00> <Notice> <WebLogicServer><SSLListenThread
li
stening on port 7002, ip address 157.253.174.63>
In advance, thanks for your help.
- Ricardo De la Rosa (Colombia) -
Where to store a custom properties file in an EJB 3 deployment
In a web application I can store my own properties file in WEB-INF. However a EJB 3 deployment does not have such a directory.
Where is the correct place within [an ejb 3 jar file] to store my properties file, and how do I retrieve it. (Do I need an absolute url or just a url that checks the classpath?)
Thanks,
natFor JBoss they use something like :
String filename = System.getProperty("jboss.server.home.dir") + "/conf/application.properties";
It will be located in jboss/server/[server-name]/conf/application.properties -
Can not deploy: NoClassDefFoundError
Hi,
i want to create a new folder in KM-Content of my Portal. Therefor i have write the following piece of code and import the libraries below. My problem is that i can not deploy my Application.
I get the error message: Caused by: java.lang.NoClassDefFoundError: com/sapportals/wcm/repository/IResourceContext
I have read that i have to add a Sharing reference to "knowledgemanagement" in the portaapp.xml file.
But i use a Java Bean/Web Service (EJB) with a Application (EAR), so i have nothing with <b>dist/PORTAL-INF</b>.
What can i do? How can i deploy my application and solve the problem?
import bc.rf.framework_api.jar
import bc.util.public_api.jar
import com.sap.portal.usermanagement.admin_api.jar
import com.sap.portal.usermanagementapi.jar
import com.sap.security.api.ep5.jar
try {
com.sapportals.portal.security.usermanagement.IUser user = WPUMFactory.getServiceUserFactory().getServiceUser("cmadmin_service");
ResourceContext ctxt = new ResourceContext(user);
IResourceContext rContext = new ResourceContext(user);
IResourceFactory resourceFactory = ResourceFactory.getInstance();
RID aRid = RID.getRID("/documents/Test");
ICollection aCollection =
(ICollection) resourceFactory.getResource(aRid, rContext);
if (aCollection != null) {
IResource resource =
aCollection.createResource("myFolder", null, null);
} catch (Exception ex) {
ex.printStackTrace();
regards,
SharamHi Sharam,
Make sure that you have your sharing reference set properly in the portalapp.xml file. Open portalapp.xml and click on the Application tab. This is what I like to have mine set to:
SharingReference=usermanagement,knowledgemanagement,landscape,htmlb,exportalJCOclient,exportal
Save your changes and the recompile/deploy.
Hope this helps!
-StephenS -
Weblogic rdms persistence 5.1.0 can not deploy
hi this is rb
we have the wl5.1 in nt and i am in Defcon 1 since i can not deploy
with the deployerTool an entyty in this moment. The entity is ok,
the fields of the data base are equals to the fields of the ejb,
but i have this error:
Persistence type WebLogic RDBMS Persistence 5.1.0 could not be
initialized. Please report this problem to the vendor.
Could not setup PersistenceType for bean 'null'.
Error occurred while processing persistence type 'WebLogic RDBMS
Persistence'.
Due to the following underlying exceptions:
sessionData
Could anybody help me?
thanks for advance.just now,I exam the OS firewall,i find it up.after I stop it via "service iptables stop"command,the console can access now!
[root@dldzfp2 ~]# service iptables status
Table: filter
Chain INPUT (policy ACCEPT)
num target prot opt source destination
1 RH-Firewall-1-INPUT all -- 0.0.0.0/0 0.0.0.0/0
Chain FORWARD (policy ACCEPT)
num target prot opt source destination
1 RH-Firewall-1-INPUT all -- 0.0.0.0/0 0.0.0.0/0
Chain OUTPUT (policy ACCEPT)
num target prot opt source destination
Chain RH-Firewall-1-INPUT (2 references)
num target prot opt source destination
1 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0
2 ACCEPT icmp -- 0.0.0.0/0 0.0.0.0/0 icmp type 255
3 ACCEPT esp -- 0.0.0.0/0 0.0.0.0/0
4 ACCEPT ah -- 0.0.0.0/0 0.0.0.0/0
5 ACCEPT udp -- 0.0.0.0/0 224.0.0.251 udp dpt:5353
6 ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:631
7 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:631
8 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED
9 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:22
10 REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited
[root@dldzfp2 ~]# service iptables stop
Flushing firewall rules: [ OK ]
Setting chains to policy ACCEPT: filter [ OK ]
Unloading iptables modules: [ OK ] -
EJB & Servlet deployment in Clustered Env.
Hi,
I have made a cluster of 3 weblogic servers. I would like to send a request to one
server (e.g. http://myserver1:7001/TestServlet). The servlet utilizes an EJB which
is not located and not deployed on myserver1 , but on other 2 servers in the cluster.
The algorithm is round-robin. It gives me a lot of errors (Impl... classes not found
etc etc).
Do I have to deploy everything on all the servers?
If I do that, the request is not routed to other servers. Since the servlet finds
the EJB locally, it never goes to the other servers, regardless of the algorithm.
I have set up the "home-is-clusterable" and all other relevant properties for EJB
deployment.
Any ideas??
Sharad
If the ejb is deployed on the server that is looking for the ejb, then it
won't go network to use the ejb. That is a "big" WL optimization, and helps
quite a bit for most apps.
If you want to segregate the ejb and web functionality, you should probably
consider running two distinct clusters (in 5.1 parlance).
I suggest putting web and ejb together though and clustering that. Latency
is lower. Scalability is not particularly affected. Configuration is much
simpler.
Peace,
Cameron Purdy
Tangosol, Inc.
http://www.tangosol.com
+1.617.623.5782
WebLogic Consulting Available
"Sharad Joshi" <[email protected]> wrote in message
news:[email protected]...
>
> Hi,
>
> I have made a cluster of 3 weblogic servers. I would like to send a
request to one
> server (e.g. http://myserver1:7001/TestServlet). The servlet utilizes an
EJB which
> is not located and not deployed on myserver1 , but on other 2 servers in
the cluster.
> The algorithm is round-robin. It gives me a lot of errors (Impl... classes
not found
> etc etc).
>
> Do I have to deploy everything on all the servers?
> If I do that, the request is not routed to other servers. Since the
servlet finds
> the EJB locally, it never goes to the other servers, regardless of the
algorithm.
> I have set up the "home-is-clusterable" and all other relevant properties
for EJB
> deployment.
>
> Any ideas??
>
> Sharad
-
Weblogic 6.1SP2 - I need to know what I need to get my EJB to deploy from the console.
I am trying to deploy my Stateful Session Bean that is in a jar on the Console. I
do the steps it says it added and even moves it to the ./config/mydomain/applications
directory but doesn't show up in the EJB window, nore does it seem to deploy when
I restart weblogic as was the case in 6.0.
I have the following classpath:
set WL_HOME=C:\bea\wlserver6.1
set JAVA_HOME=C:\bea\jdk131
set CLASSPATH=%JAVA_HOME%\lib\tools.jar;%WL_HOME%\lib\weblogic_sp.jar;%WL_HOME%\lib\weblogic.jar;c:\bea\utils\utils.jar;c:\bea\wlserver6.1\config\mydomain\applications
I get no errors so that is the confusing part and I am unable to do a lookup on them
from my Servlet, assuming that that is because they were not deployed.
Assistance would be greatly appreciated.Are you starting the server in Development mode or Production mode? Check the -Dweblogic.ProductionModeEnabled=%STARTMODE% property when you are starting the server. If you
are in production mode, putting it in the applications directory will not deploy it on an admin server. I don't think you need the applications directory in the classpath,
either. You could be loading applications with the system classloader which will make them static.
Bill
Eric Tice wrote:
That is in the configure part. I am talking about doing a Install New EJB. When
I choose a jar and hit upload it should deploy the bean but isn't. I shouldn't have
to use the configure tool. It wasn't necessary in past versions of Weblogic. Any
thoughts?
William Kemp <[email protected]> wrote:
Sounds like you are not targeting the bean. Use the 'Targets' tab and select
a server to target the bean to.
Bill
Eric Tice wrote:
I am trying to deploy my Stateful Session Bean that is in a jar on theConsole. I
do the steps it says it added and even moves it to the ./config/mydomain/applications
directory but doesn't show up in the EJB window, nore does it seem todeploy when
I restart weblogic as was the case in 6.0.
I have the following classpath:
set WL_HOME=C:\bea\wlserver6.1
set JAVA_HOME=C:\bea\jdk131
set CLASSPATH=%JAVA_HOME%\lib\tools.jar;%WL_HOME%\lib\weblogic_sp.jar;%WL_HOME%\lib\weblogic.jar;c:\bea\utils\utils.jar;c:\bea\wlserver6.1\config\mydomain\applications
I get no errors so that is the confusing part and I am unable to do alookup on them
from my Servlet, assuming that that is because they were not deployed.
Assistance would be greatly appreciated.
Maybe you are looking for
-
hi i am new to ale ,idoc. pls send me some materials for both. mail id : [email protected]
-
CS3 Indesign error with missing dbghelp.dll
Has anybody got a solution for this?
-
Hi everybody, Since a while it looks like our Coldfusion server random decides to hang. After looking in the CF-log files we cannot point out what causes the hanging. Since the end of May an error message appears in the Application- and Exception-log
-
Trying to transfer everything on my iTunes from my old Macbook to my new Macbook Pro
I recently purchashed new Macbook Pro, and was told that a simple Migration Assistant tool would transfer everything from my old mac to this one; it didnt. I just need to transfer my whole iTunes library now but i dont know how to, what is the best s
-
Security Filter: Computer works, Computer Group doesnt works
Hi @all, Server W2K12R2 ... Name Computer1 When i make a FPO with security filtering on 1.) Computer ... works 2.) Security Group, Global, Security with Member Computer1 ... doesnt works Read, Apply Group Policy are set Why? Help