UNdeploying an EJB

Is there an automated way to "un"-deploy an EJB? ...or, is
removing the generated classes and unpublishing the object
sufficient? (Does that leave anything behind?)
null

Hi John,
following are steps.
->Using the bean JAR file that contains the class files for the
bean, run the 'dropjava' tool to delete the classes from the
database.
->Use the session shell tool to remove the bean home interface
name from the published object name space.
regards
raghu
John K. Peterson (guest) wrote:
: Is there an automated way to "un"-deploy an EJB? ...or, is
: removing the generated classes and unpublishing the object
: sufficient? (Does that leave anything behind?)
null

Similar Messages

Problems servicing EJB requests on SOA server. SOA Suite 11g.

Hi all
I recently installed SOA Suite 11g on my Windows 7 machine for a project that will be employing SOA, BPM and EJB services. I created a new SOA domain with an admin server and a managed SOA server. When creating the domain, I specified BPM Suite, SOA Suite, Enterprise manager, WSM Policy Manager and JRF to be included as per project requirements.
SOA and BPM project have been deployed to and are working fine on the SOA server, but I observed the following odd behaviour when I tried to deploy and use a Java EJB service: -
1. Via the admin console, I successfully deployed my EJB ear to the managed SOA server and can see it in the JNDI tree of the server.
2. When I try to invoke the EJB from a remote client, the service is successfully located via JNDI and a request is sent, but it is as though the service then simply swallows the request and does nothing with it. No output is returned from the EJB service and none of the logging from the EJB service appears in the logs. No errors are reported on the console or in any of the Weblogic logs that I have looked through.
3. I tried deploying the ear to the admin server instead and invoking it with the same client. This time it works absolutely fine.
4. When messing around with setDomainEnv.cmd, I accidentally removed jrf.jar from the classpath. When the SOA server subsequently started, this caused lots of errors while deploying the SOA components, but my EJB service worked with no problems on the SOA server. When I correcteed the classpath and restarted, the original problem returned.
It seems as though a conflict is occurring, which I am pretty baffled by. I would be very grateful for any advice or suggestions on this issue.
Many thanks
Jon

Hi Jon
I don't know the root cause of this issue. But try this and see if it works. Undeploy this EJB EAR application from weblogic admin console. Then Login into EM Console. And in EM Console, expand weblogic domain and select your soa server under this folder and right click and try to Deploy your EAR. And then access the EJB.
We have some BPM Applications where we have one Workflow project that we deploy from EM Console. This BPM App also have lots of EJB projects. We deploy all of them as single EAR from em console under weblogic domain. So far we have not faced any issues.
Thanks
Ravi Jegga

Undeploying bean in weblogic6

hi ,
I dont know how to undeploy a bean from web logic 6. If i remove teh check in
the weblogic console it is undeployed but still there in the application folder.
Also it tries to deploy at restart .... Any help is much appreciated..
regards,
srini

Undeploying a webapp or ejb does not physically remove the application
from WebLogic Server.
Undeploying an EJB does not remove the associated deployment name,
because you may later re-use that name to deploy the bean.
In 6.1, there's an option called "delete this webapp or ejb" which will
undeploy and physically remove the deployment from the apps directory.
BTW, apps dir is used for development purposes only. If you want
the WLS not to deploy the applications upon startup, you better
deploy them outside of applications directory.
Kumar
srinivasan wrote:
hi ,
I dont know how to undeploy a bean from web logic 6. If i remove teh check in
the weblogic console it is undeployed but still there in the application folder.
Also it tries to deploy at restart .... Any help is much appreciated..
regards,
srini

Create EJB Control For Remote Server

I'm having trouble creating an EJB control for a EJB residing in a remote server.
First, I've a JAR containing the remote/home interfaces and added it as a Library in the WLW 8.1 application.
When creating a new EJB Control, there's no way to successfully create the control.
At the STEP 2 GUI:
I am able to specify a JNDI-NAME, but the home/bean interface fields are empty. If I click on "Browse application EJBs..." button, nothing is available. If I click on "Browse server EJBs", it only shows EJBs in the current server.
Thanks

Hi
I believe you are on Workshop8.1 Spx.
This is a known issue. The reason the ejb does not show up as an application ejb because we have just the interfaces as a library and not the whole EJB.
Since the EJB's are not deployed on the server it will not show up either.
Unfortunately there is no way to point to a remote domain and get all the ejb's deployed there.
Workaround:
You can deploy the ejb locally, create the ejbcontrol and then undeploy the EJB. You need to manually change the home jndiname to use the remote server url.
Thanks
Vimala

Failing EJBs without killing server?

          Hi All,
          Is there anyway to fail an EJB to cause failover without actually killing the WLS its deployed on?
          I tried undeploying an EJB using the console but that didn't work.
          I wish to verify EJB failover without the server going down.
          Thanks in advance,
          Andrew Quinan


Killing the server is one way to cause the RemoteException.
          EJB automatic failover can only happen in idempotent stateless session bean
          or read only entity bean. For other ejbs, you have to write special code in
          the CLIENT side to implement the failover.
          You can write special ejb method that can generate the RemoteException, in
          your client side code, you can catch such exception and replace the remote
          interface and make call again.
          Hope this can help.
          Andrew Quinan <[email protected]> wrote in message
          news:3a54f5b6$[email protected]..
          >
          > Hi All,
          >
          > Is there anyway to fail an EJB to cause failover without actually killing
          the WLS its deployed on?
          >
          > I tried undeploying an EJB using the console but that didn't work.
          >
          > I wish to verify EJB failover without the server going down.
          >
          > Thanks in advance,
          > Andrew Quinan

Automatic ejb redeploy when deploying a webapp

Hi all,
I' got a problem with bea 6.1 webapp deploy/redeploy.
When, from console, I upload the war the server undeploy and redeploy an EJB,
then try to deploy the war.
The ejb is used by the webapp and in the war (in WEB-INF/classes) there are the
EJB interfaces.
Is this correct ?
The real problem is that I have to deploy on a 2 node cluster. Deploying from
console automatically target the admin server, the EJB fail the redeploy and the
webapp is not deployed on the nodes.
I tryed to undeploy the EJB before deploying the webapp and another EJB (not related
to the webapp, developed here, not from bea) id redeployed ! :|
Any idea ?
Thanks
Lorenzo

Lorenzo,
Have you considered using an Enterprise Application (EAR) which includes both your web
app and your ejbs? This way you can undeploy and redeploy at the application level and
let the server worry about the deployment order. See:
http://edocs.bea.com/wls/docs61/programming/packaging.html#1029830
You can turn off the automatic deployment to the admin server. Please read:
http://edocs.bea.com/wls/docs61/adminguide/appman.html#1029683
I hope this helps.
Regards,
Velvet
Developer Relations Engineer
BEA Systems
"\"lorenzo bolzani\" lorenzo.bolzani-at-ethink.it" wrote:
Hi all,
I' got a problem with bea 6.1 webapp deploy/redeploy.
When, from console, I upload the war the server undeploy and redeploy an EJB,
then try to deploy the war.
The ejb is used by the webapp and in the war (in WEB-INF/classes) there are the
EJB interfaces.
Is this correct ?
The real problem is that I have to deploy on a 2 node cluster. Deploying from
console automatically target the admin server, the EJB fail the redeploy and the
webapp is not deployed on the nodes.
I tryed to undeploy the EJB before deploying the webapp and another EJB (not related
to the webapp, developed here, not from bea) id redeployed ! :|
Any idea ?
Thanks
Lorenzo

Can't run the cluster example

          I would appreciate if someone can explanation my long list of questions regarding
          the deployment of EJB in cluster environment.
          I can't run the cluster EJB example( Teller/Account) in a cluster(contains two
          server2). I always get
          java.rmi.RemoteException: Unable to
          resolve examples.cluster.ejb.Account
          Home. Resolved: 'examples.cluster.ejb'
          Unresolved:'AccountHome'
          Following is my setup:
          Machine A: exampleServer:7001 (admin server)
          Machine A: testServer1:8001 (Managed server)
          Machine B: testServer1_B:8001(Managed server)
          MyCluster : testServer1, testServer1_B
          Test Client:
          java examples.cluster.ejb.Client "t3://Machine A:8001"
          ======================
          Q1: Should I use 8001 or 7001 as cluster port number?
          Q2: What will happen when we click "apply" after select/unselect the server in
          the "target", "server" tab?
          Q3: And what will happen if we click deploy/undeploy check box in "configuration"
          tab of EJB item?
          Q4: I check the JNDI tree from all above three servers can't find out JNDI tree
          doesn't reflect the change I did in Q2 or Q3.
          Q5: What is the right way to deploy EJB components, should we select both cluster
          and server in the "target" tab?
          Q6: I got this message from one of the server when I try to undeploy/deploy ejb
          object.
          "examples.cluster.ejb.TellerHome_EO in the jndi tree is non clusterable
          and you have tried to bind more
          once? How could I make it clusterable?
          Q7: Undeploy and EJB doesn't work and sometime I still get " JNDI name in use"
          from the server.
          How could I fix it.
          Thanks


First I can tell you that the ports have to be the same, be on the the
          same network , i.e. Telnet into the other m/c. Next which you probably
          have done is the properties files. Per-cluster ...
          >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
          On 6/7/01, 6:59:48 AM, "James Hsu" <[email protected]> wrote regarding
          Can't run the cluster example:
          > I would appreciate if someone can explanation my long list of
          questions regarding
          > the deployment of EJB in cluster environment.
          > I can't run the cluster EJB example( Teller/Account) in a
          cluster(contains two
          > server2). I always get
          > java.rmi.RemoteException: Unable to
          > resolve examples.cluster.ejb.Account
          > Home. Resolved: 'examples.cluster.ejb'
          > Unresolved:'AccountHome'
          > Following is my setup:
          > Machine A: exampleServer:7001 (admin server)
          > Machine A: testServer1:8001 (Managed server)
          > Machine B: testServer1_B:8001(Managed server)
          > MyCluster : testServer1, testServer1_B
          > Test Client:
          > java examples.cluster.ejb.Client "t3://Machine A:8001"
          > ======================
          > Q1: Should I use 8001 or 7001 as cluster port number?
          > Q2: What will happen when we click "apply" after select/unselect the
          server in
          > the "target", "server" tab?
          > Q3: And what will happen if we click deploy/undeploy check box in
          "configuration"
          > tab of EJB item?
          > Q4: I check the JNDI tree from all above three servers can't find out
          JNDI tree
          > doesn't reflect the change I did in Q2 or Q3.
          > Q5: What is the right way to deploy EJB components, should we select
          both cluster
          > and server in the "target" tab?
          > Q6: I got this message from one of the server when I try to
          undeploy/deploy ejb
          > object.
          > "examples.cluster.ejb.TellerHome_EO in the jndi tree is non
          clusterable
          > and you have tried to bind more
          > once? How could I make it clusterable?
          > Q7: Undeploy and EJB doesn't work and sometime I still get " JNDI
          name in use"
          > from the server.
          > How could I fix it.
          > Thanks
          [att1.html]

FrameworkException/Error in Sun Application Server 8.1

While undeploying an EJB module, I am getting the following problem. While clicking on the "EJB Modules", the right pane is showing
A "com.sun.enterprise.tools.guiframework.exception.FrameworkError" was caught. The message from the exception: "Unable to get View for ViewDescriptor 'ejbModules'"
The root cause is "com.sun.enterprise.admin.common.exception.MBeanConfigException: Component not registered"
See the HTML source for more detailed (stack trace) information.
and while clicking on that EJB module from the tree view of the left pane, the right pane is showing
A "com.sun.enterprise.tools.guiframework.exception.FrameworkException" was caught. The message from the exception: "Unabled to handle pre-compiled JSP '/jsp/ejbModulesEdit.jsp'. Expected pre-compiled classname: 'org.apache.jsp.jsp.ejbModulesEdit_jsp'."
The root cause is "com.sun.enterprise.admin.common.exception.MBeanConfigException: Component not registered"
See the HTML source for more detailed (stack trace) information.
I have restarted the server but nothing happens.

if you download SJAS 8.2, Derby is included and pre-configured as a DataSource
Using 8.1, you will need to add the jars to either the lib or domains/domains1/lib/ext directory and manually configure a DataSource using
javax.sql.DataSource org.apache.derby.jdbc.ClientDataSource
javax.sql.XADataSource org.apache.derby.jdbc.ClientXADataSource

BMP Entity never execute unsetEntityContext

hi,
i'm using BMP Entity beans
1. these seems never executing the unsetentitycontext method.
2. when undeploying my EJB or stopping my weblogic instance,
i would like to close properly some sockets, but no events
occurs.
What's happening, is it a unfixed problem? or a deployment problem?
I'm using weblogic server 6.1.1.0 SP1
thanks in advance

Entity beans are moved to a pool at the end of a transaction. When talking
to an entity bean directly, the transaction is a single method call. An
entity bean is attached at the server on demand (pulled from the pool and
activated)... and only stays attached during a transaction. So, when you
make the method call, the server attaches an entity bean, runs the method,
calls ejbStore(), and releases the bean back to the pool by calling
ejbPassivate(). Finally, beans that are in the 'pooled' state are garbage
collected by the server at it's discretion and the unsetEntityContext() is
called.
Hence, you have to release all your resources in ejbPassivtae().
"F Cahon" <[email protected]> wrote in message
news:3c62ad4e$[email protected]..
>
hi,
i'm using BMP Entity beans
1. these seems never executing the unsetentitycontext method.
2. when undeploying my EJB or stopping my weblogic instance,
i would like to close properly some sockets, but no events
occurs.
What's happening, is it a unfixed problem? or a deployment problem?
I'm using weblogic server 6.1.1.0 SP1
thanks in advance

Timer Services

Hi All,
EjbTimerService in 2.1 says that Timers are persistent. If the server is shut down (or even crashes), timers are saved and will become active again when the server is restarted. If a timer expires while the server is down, the container will call ejbTimeout when the server is restarted.
I need to know that what feature we are supposed to add in order to allow undeployment to treat persisted timers as entities that exist beyond the lifetime of the ejb deployment.
I could not find any article for same. Please tell me, where i can get the documentation in details about how Jboss handles the Timer services especially when such condition occurs.
All suggestions are welcome.
Thanks.

I am not sure I completely understand your question, but this might help...
JBoss stores the timers in a database table named TIMER. When undeploying an EJB-JAR containing an EJB for which there is an active timer, JBoss removes the correponding row from the TIMER table. So it is not possible that a timer is triggered for an EJB that is not deployed anymore.
But I am not sure how JBoss handles this if you simply deletes the EJB-JAR file from the deploy folder when JBoss is not running.
Also, there is a timer section in the J2EE tutorial at http://java.sun.com/j2ee/1.4/docs/tutorial/doc/Session5.html
Bruno
http://www.practicalsoftwarearchitect.com

Redeploy of exploded enterprise app

Hi people
I`m working with WL6.1sp1 on WinNT and Solaris.
I would like to deploy a web application and several ejbs so that:
1 there is no long copying of files when the server starts.
2 web components can use ejb components.
3 everything (html, jsp, servlets, page beans, ejbs) is hot-updatable without
much trouble.
The closest approximation that I have arrived at is using an exploded enterprise
application containing an exploded web application and several pack ejb jars.
I use auto-deploy.
html, jsp, servlets, and page beans can be updated simply by copying the new files
in the right places.
But how can I update an EJB-jar?
I tried simply replacing the EJB-jar, deploying and undeploying the EJB in the
console, and touching a REDEPLOY file sitting in the root of the enterprise application.
Still, clients see the old ejb!
Thanks in advance for any help.
Alex

If you are running in the Development mode, then you should be able to update your ejb by
copying a new jar over it and then by undeploying and deploying through the console. or you
can use the weblogic.deploy utility to hot deploy the ejb.
Touching the REDEPLOY file is meant only for webApps.
thanks,
Mihir
Alexander Bunkenburg wrote:
Hi people
I`m working with WL6.1sp1 on WinNT and Solaris.
I would like to deploy a web application and several ejbs so that:
1 there is no long copying of files when the server starts.
2 web components can use ejb components.
3 everything (html, jsp, servlets, page beans, ejbs) is hot-updatable without
much trouble.
The closest approximation that I have arrived at is using an exploded enterprise
application containing an exploded web application and several pack ejb jars.
I use auto-deploy.
html, jsp, servlets, and page beans can be updated simply by copying the new files
in the right places.
But how can I update an EJB-jar?
I tried simply replacing the EJB-jar, deploying and undeploying the EJB in the
console, and touching a REDEPLOY file sitting in the root of the enterprise application.
Still, clients see the old ejb!
Thanks in advance for any help.
Alex

How to UnDeploy EJBs deployed in XI

i have deployed some EJBs for java proxy, adapter module, etc, in SAP J2EE engine of XI 3.0 using NWDS,
is there any way to undeploy those EARs, either through NWDS or some other tools
Thanks Forum,

i have no idea about using SDM, can u provide a bit detail of how to undeploy a EAR using SDM...
i thought of deleting those EARs in the server itself.....but was confused to see the same EAR files in multiple location..

Code to undeploy EJB modules only works outside of weblogic

I have three applications, which we'll call "ejbapp", "deploysa", and "deployear" for reference. The "ejbapp" is just composed of individual EJB modules, using "classloader-structure" elements to put each EJB module in its own ClassLoader (to allow each EJB module to be individually undeployed). The "deploysa" is a standalone app that just uses "DeployerRuntimeMBean" to stop and start individual EJB modules in "ejbapp". The "deployear" app is an ear containing basically the same deployment logic that "deploysa" contains.
When I run "deploysa", I can see it successfully undeploy an individual EJB module in "ejbapp".
When I run "deployear", however, when it executes the "stop()" method, I see the following exception:
NoAccessRuntimeException: Access not allowed for subject: principals=[], on ResourceType: DeployerRuntime Action: execute, Target: stop
I've tried several variations of this. There are three overloaded versions of "DeployerRuntime.getDeployerRuntime()", and I've tried all three of them, including the one taking "user, pwd, url", which is the one that "deploysa" uses (successfully).
I've googled for this error, but the only occurrences I've found are people reporting a problem like this, but without finding a solution.

I've resolved this. As JPDs normally run with "anonymous" permissions, you have to set the "run-as" element on the underlying session bean to "weblogic". This can be done with the following in the javadoc comment block:
@common:security run-as="weblogic"
I believe it can also be set in the WLI console.

Dynamically Undeploying EJBs / MDBs

Hi,
Is there a way to programmatically undeploy EJBs or MDBs. I am working with WLS6.1.
I have a Message Driven Bean which should take messages from the Queue and parse
the XML body of the message and save it into the database.
In the MDB, onMessage(), I am checking if the Database is available, if it is
not available, I am rolling back the message. But the problem is the message
is consumed again. So I want to undeploy the MDB after some retries.
Can I programmatically undeploy a Message Driven Bean or EJB.
Thanks in advance
Venkatesan

Hi,
Is there a way to programmatically undeploy EJBs or MDBs. I am working with WLS6.1.
I have a Message Driven Bean which should take messages from the Queue and parse
the XML body of the message and save it into the database.
In the MDB, onMessage(), I am checking if the Database is available, if it is
not available, I am rolling back the message. But the problem is the message
is consumed again. So I want to undeploy the MDB after some retries.
Can I programmatically undeploy a Message Driven Bean or EJB.
Thanks in advance
Venkatesan

EJBs still bound even after undeploying application

Hi,
I am using WebLogic 10.0 MP2 notice that if I undeploy an ear containing Stateless Session EJBs there are still entries for these EJBs in the JNDI server tree. The entries look like <name of Bean>#<full package name of Bean>.
I am undeploying using the WebLogic Console (Deployments->Delete) and see in the log that the deployment goes from STATE_PREPARED to STATE_NEW.
I can fix the issue by deleting the EJBCompilerCache directory but would like to know why they don't get removed as part of the undeploy.
Thanks for any help
Mandy

Hi,
Not I'm not using the autodeploy directory, I am uploading from my local machine to the uploads/ directory.
I don't seem to get any problems when I redeploy the application in a single server but on a cluster I get this issue..
<01-Dec-2010 23:04:35 o'clock GMT> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '129124****2336' for task '19'. Error is: 'weblogic.application.ModuleException: Exception activating module: EJBModule(sampleejbs-ejb-0.0.1-SNAPSHOT.jar)
Unable to deploy EJB: JmsAPIConnPoolSonicJmsStatelessSessionBean from sampleejbs-ejb-0.0.1-SNAPSHOT.jar:
[EJB:011008]Unable to bind EJB Home Interface to the JNDI name: sampleejbs-ear-0sampleejbs-ejb-0_0_1-SNAPSHOT_jarJmsAPIConnPoolSonicJmsStatelessSessionBean_HOME.
javax.naming.NameAlreadyBoundException: sampleejbs-ear-0sampleejbs-ejb-0_0_1-SNAPSHOT_jarJmsAPIConnPoolSonicJmsStatelessSessionBean_HOME is already bound; remaining name ''and this:
<01-Dec-2010 23:04:35 o'clock GMT> <Error> <Cluster> <BEA-000123> <Conflict start: You tried to bind an object under the name WLPooledWLJmsStatelessSessionBean#com.xx.xxx.test.samples.JmsMessageSender in the JNDI tree. The object from -769998****8669S:xxx05bb01-wl01:[7021,7021,-1,-1,-1,-1,-1]:jcrxxbus1:xxx05bb01-bus1 is non-clusterable, and you have tried to bind more than once from two or more servers. Such objects can only be deployed from one server.>Any ideas much appreciated!
Many thanks
Mandy

UNdeploying an EJB

Similar Messages

Maybe you are looking for