WebLogic hangs around after shutdown process appears to complete - Message Driven Bean related

On my current project we have some Ant scripts that automatically
start and stop WebLogic. The stop script equates to (not exactly but
close enough):
java weblogic.Admin -url localhost:8001 -password password -username
username SHUTDOWN
WebLogic is start and shutdown for each system module. All modules
use the exact same script for these two actions. Some of the modules
use Message Driven Beans and consequently, since these use JMS, a
JMSxxx.dat file is generated in the jms_store directory. As part of
the cleanup process the jms_store directory and all files in it are to
be deleted AFTER WebLogic shuts down.
The shutdown process works fine in all cases where JMS is not used and
in all cases where JMS IS used but there are NO message driven beans.
However, when there is a message driven bean the server does not shut
down in a timely manner, sometimes not at all (no error messages are
produced), and the JMSxx.dat file
remains locked. Consequently, all of the tests run via the ant script
for modules come to a grinding halt (i.e. environment could not be
cleaned so further tests would be skewed).
Can anyone shed some light on a definitive order of events during
WebLogic's shutdown process? What is the best way to test for the
server being up? I know there is a ping utility for weblogic - should
this be used or should a connection to a JNDI or JMS listening port do
the trick? Any other ideas would be welcome.
Thanks in advance,
Mark

Similar Messages

Using work managers to process WorkItems in a message driven bean

Hi, I'm trying to get to grips with using a work manager (in 10.3) to process WorkItems concurrently, with the whole process being triggered by a JMS message. I've got everything working using the default work manager but I'm having problems switching over to using a work manager that I've created myself, using annotations to provide the resource ref.
My current setup, using the default work manager, is (roughly) this:
@MessageDriven(mappedName = "jms/tsrd.DependencyWorker", activationConfig = {
        @ActivationConfigProperty(propertyName = "connectionFactoryJndiName", propertyValue = "jms/connectionFactory"),
        @ActivationConfigProperty(propertyName = "ejbName", propertyValue = "tsrd.DependencyWorker"),
        @ActivationConfigProperty(propertyName = "destinationJndiName", propertyValue = "jms/tsrd.DependencyWorker"),
        @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue") })
@Interceptors(SpringBeanAutowiringInterceptor.class)
public class DependencyWorker implements MessageListener {
    private WorkManager workManager;
    @Required
    @Resource(name = "taskExecutor")
    public void setWorkManager(final WorkManager workManager) {
        this.workManager = workManager;
    public void doOperation(final WorkflowControlMessage msg) throws Exception {
         Work myWork = new ...
         workManager.schedule(myWork, listener);
}With my spring config including this bean:
<bean id="taskExecutor" class="org.springframework.scheduling.commonj.WorkManagerTaskExecutor">
    <property name="workManagerName" value="wm/default"/>
    <property name="resourceRef" value="true"/>
</bean>And this works fine: when the JMS message is received I send a load of WorkItems to the default work manager and they get processed.
Now what I'd like to do is change the spring config to this:
<bean id="taskExecutor" class="org.springframework.scheduling.commonj.WorkManagerTaskExecutor">
    <property name="workManagerName" value="wm/MyWorkManager"/>
    <property name="resourceRef" value="true"/>
</bean>Where I've already created MyWorkManager as a global work manager for the server, and it's visible on the admin server for the deployment.
From the examples I've seen I know I need to add a resource ref for the MDB so that it can lookup the work manager using JNDI. We mainly use annotations, so I'd like to just be able to add this line to the MDB:
@Resource(name = "MyWorkManager", type = commonj.work.WorkManager.class, authenticationType = Resource.AuthenticationType.CONTAINER, shareable = true)But when I try that my server refuses to start:
Unable to deploy EJB: DependencyWorker from tsrd-mdb.jar:
[EJB:011026]The EJB container failed while creating the java:/comp/env namespace for this EJB deployment.
weblogic.deployment.EnvironmentException: [EJB:010176]The resource-env-ref 'MyWorkManager' declared in the ejb-jar.xml descriptor or annotation has no JNDI name mapped to it. The resource-ref must be mapped to a JNDI name using the resource-description element of the weblogic-ejb-jar.xml descriptor or corresponding annotation.So is there a way to fully configure my work manager just using the @Resource annotation, or do I need to add a weblogic-ejb.jar.xml file and put some specific config in there? Presumably if I do need to add an xml file then I'd need to put something like this in it?
<wls:weblogic-enterprise-bean>
    <wls:ejb-name>DependencyWorker</wls:ejb-name>
    <wls:resource-description>
        <wls:res-ref-name>MyWorkManager</wls:res-ref-name>
        <wls:jndi-name>wm/MyWorkManager</wls:jndi-name>
    </wls:resource-description>
</wls:weblogic-enterprise-bean>Am I also right in thinking that I don't need to add a dispatch policy to the MDB specifying MyWorkManager, because I don't actually want to dispatch the MDB to that manager, I just want the manager to be available to the MDB.
Thanks.

Hi, so I've added a weblogic-ejb.jar.xml file with a reference to the JNDI name of the work manager:
<?xml version="1.0" encoding="UTF-8"?>
<wls:weblogic-ejb-jar xmlns:wls="http://xmlns.oracle.com/weblogic/weblogic-ejb-jar" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd http://xmlns.oracle.com/weblogic/weblogic-ejb-jar http://xmlns.oracle.com/weblogic/weblogic-ejb-jar/1.0/weblogic-ejb-jar.xsd">
    <wls:weblogic-enterprise-bean>
        <wls:ejb-name>DependencyWorker</wls:ejb-name>
        <wls:resource-description>
            <wls:res-ref-name>MyWorkManager</wls:res-ref-name>
            <wls:jndi-name>wm/MyWorkManager</wls:jndi-name>
        </wls:resource-description>
    </wls:weblogic-enterprise-bean>
</wls:weblogic-ejb-jar>But I still get exactly the same error when I try to start my server. The example you referred to kind of cryptically suggests that adding a plan.xml suddenly fixed everything, but what am I missing here that actually hooks the work manager up to JNDI? am I getting these problems because I'm using annotations, or are people not supposed to access work managers in this way?
Thanks,
Edited by: 806682 on 05-Nov-2010 08:57

WebLogic 10 and EJB 3.0 for Message Driven Bean

Hi,
I am trying to deploy Message Driven Bean using EJB3.0 on weblogic 10. I am using annotations and don't want to use deployment descriptors.
The Bean class:
CalculatorBean.java
import javax.ejb.*;
import javax.jms.*;
import java.sql.Timestamp;
import java.util.StringTokenizer;
@MessageDriven(activationConfig =
@ActivationConfigProperty(propertyName="destinationType",
propertyValue="javax.jms.Queue"),
@ActivationConfigProperty(propertyName="destination",
propertyValue="queue/mdb")
public class CalculatorBean implements MessageListener {
public void onMessage (Message msg) {
TextMessage tmsg=null;
try {
if (msg instanceof TextMessage) {
tmsg = (TextMessage) msg;
System.out.println
("MESSAGE BEAN1: Message received: "
+ tmsg.getText());
} else {
System.out.println
("Message of wrong type1: "
+ msg.getClass().getName());
catch (JMSException e) {
e.printStackTrace();
catch (Throwable te) {
te.printStackTrace();
My client:
import javax.naming.*;
import javax.naming.InitialContext;
import java.text.*;
import javax.jms.*;
public class MsgClient {
public static void main(String args[])
QueueConnection cnn=null;
QueueSender sender=null;
QueueSession sess=null;
Queue queue=null;
try {
java.util.Properties p = new java.util.Properties();
p.put("java.naming.factory.initial","weblogic.jndi.WLInitialContextFactory");
p.put("java.naming.provider.url","t3://10.6.74.79:7001");
Context ctx=new InitialContext(p);
//InitialContext ctx=new InitialContext(p);
queue = (Queue)ctx.lookup("queue/mdb");
QueueConnectionFactory factory = (QueueConnectionFactory)ctx.lookup("ConnectionFactory");
cnn = factory.createQueueConnection();
sess= cnn.createQueueSession(false, QueueSession.AUTO_ACKNOWLEDGE);
sender = sess.createSender(queue);
TextMessage message = sess.createTextMessage();
message.setText("This is message by Gurumurthy" );
System.out.println("Sending message: " +message.getText());
sender.send(message);
sess.close();
catch (Exception e)
e.printStackTrace();
I am compiling and creating jar file for this class. Then I am creating a .ear file for this.
The meta-inf/application.xml contains the following:
<?xml version="1.0" encoding="UTF-8"?>
<application xmlns="http://java.sun.com/xml/ns/j2ee" version="1.4"
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/application_1_4.xsd">
<display-name>MDBWorking1</display-name>
<description>Application description</description>
<module>
<ejb>MDBWorking1.jar</ejb>
</module>
</application>
I don't want to use deployment descriptor (ejb-jar.xml or weblogic-ejb-jar-xml), because I want to utilize the annotation feature of EJB3.0
So, after creating the .ear file for this, and try to deploy on weblogic 10, I get the following error:
An error occurred during activation of changes, please see the log for details.
Exception preparing module: EJBModule(MDBWorking1.jar) Unable to deploy EJB: CalculatorBean from MDBWorking1.jar: [EJB:011113]Error: The Message Driven Bean 'CalculatorBean(Application: MDBWorking1, EJBComponent: MDBWorking1.jar)', does not have a message destination configured. The message destination must be set using a message-destination-link, destination-resource-link, destination-jndi-name or a resource-adapter-jndi-name.
Substituted for missing class [EJB - 11113]Error: The Message Driven Bean 'CalculatorBean(Application: MDBWorking1, EJBComponent: MDBWorking1.jar)', does not have a message destination configured. The message destination must be set using a message-destination-link, destination-resource-link, destination-jndi-name or a resource-adapter-jndi-name.
How to solve this?
Note:
I don't want to use Deployment Descriptor and all I want to use is EJB3.0's annotation feature.
Thanks,
Guru

Dear gurubbc,
I don't know if it still matters to you but you can use the javax.ejb.MessageDriven annotation to point your bean on your queue. I had the same issue like you but i could not solve it properly by switchihg to weblogic.ejb.MessageDriven.
Use the following annotation and it should work out:
@MessageDriven
(mappedName = "queue/mdb",
name = "CalculatorBean",
activationConfig = {
@ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue")
Here you can see that the mappedName is the JNDI name of the queue you are trying to connect to. The name is the name for your Bean, and the only property passed is the destination type.
Hope this helps.
Cheers,
Istvan

My problem in Weblogic and Message Driven Bean for Topic

Hello to all
I used this page (http://www.ecomputercoach.com/index.php/component/content/article/90-weblogic-jms-queue-setup.html?showall=1)
for setup JMS Server, Queue, Connection Factory on Weblogic Server
and I created a Message Driven Bean ,I used those Queue , and all things was OK
But I wanted to setup a Topic and use it in this manner
I created a Topic like previous steps for setup Queue
(http://www.ecomputercoach.com/index.php/component/content/article/90-weblogic-jms-queue-setup.html?showall=1)
Except in Step 3 ,I selected Topic instead of Queue
then I created a Message Driven Bean in JDeveloper , my Message Driven Bean is like this:
@MessageDriven(mappedName = "jndi.testTopic")
<p>
public class aliJMS1_MessageDrivenEJBBean implements MessageListener {
    public void onMessage(Message message) {
      if(message instanceof TextMessage ){
        TextMessage txtM=(TextMessage) message;
        try{
          System.out.println(txtM.getText());
        }catch(Exception ex){
          ex.printStackTrace();
</p>
When I deploy the Application , Weblogic shows me this error:
+<Aug 30, 2011 11:32:28 AM PDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: aliJMS1_MessageDrivenEJBBean is unable to connect to th+
e JMS destination: jndi.testTopic. The Error was:
+[EJB:011011]The Message-Driven EJB attempted to connect to the JMS destination with the JNDI name: jndi.testTopic. However, the object with+
the JNDI name: jndi.testTopic is not a JMS destination, or the destination found was of the wrong type (Topic or Queue).>
And when I send message to the topic The Message Dirven Bean dosen't work
But when I create an ordinary Java application like this (it uses that Tpoic) :
import java.io.*;
import java.util.*;
import javax.transaction.*;
import javax.naming.*;
import javax.jms.*;
public class TopicReceive implements MessageListener
    public final static String JNDI_FACTORY =
        "weblogic.jndi.WLInitialContextFactory";
    public final static String JMS_FACTORY =
        "jndi.testConnectionFactory";
    public final static String TOPIC = "jndi.testTopic";
    private TopicConnectionFactory tconFactory;
    private TopicConnection tcon;
    private TopicSession tsession;
    private TopicSubscriber tsubscriber;
    private Topic topic;
    private boolean quit = false;
    public void onMessage(Message msg) {
        try {
            String msgText;
            if (msg instanceof TextMessage) {
                msgText = ((TextMessage)msg).getText();
            } else {
                msgText = msg.toString();
            System.out.println("JMS Message Received: " + msgText);
            if (msgText.equalsIgnoreCase("quit")) {
                synchronized (this) {
                    quit = true;
                    this.notifyAll();
        } catch (JMSException jmse) {
            jmse.printStackTrace();
    public void init(Context ctx, String topicName) throws NamingException,
                                                           JMSException {
        tconFactory = (TopicConnectionFactory)ctx.lookup(JMS_FACTORY);
        tcon = tconFactory.createTopicConnection();
        tsession = tcon.createTopicSession(false, Session.AUTO_ACKNOWLEDGE);
        topic = (Topic)ctx.lookup(topicName);
        tsubscriber = tsession.createSubscriber(topic);
        tsubscriber.setMessageListener(this);
        tcon.start();
    public void close() throws JMSException {
        tsubscriber.close();
        tsession.close();
        tcon.close();
    public static void main(String[] args) throws Exception {
        InitialContext ic = getInitialContext("t3://127.0.0.1:7001");
        TopicReceive tr = new TopicReceive();
        tr.init(ic, TOPIC);
        System.out.println("JMS Ready To Receive Messages (To quit, send a \"quit\" message).");
        synchronized (tr) {
            while (!tr.quit) {
                try {
                    tr.wait();
                } catch (InterruptedException ie) {
        tr.close();
    private static InitialContext getInitialContext(String url) throws NamingException {
        Hashtable env = new Hashtable();
        env.put(Context.INITIAL_CONTEXT_FACTORY, JNDI_FACTORY);
        env.put(Context.PROVIDER_URL, url);
        env.put("weblogic.jndi.createIntermediateContexts", "true");
        return new InitialContext(env);
It's OK and shows messages When I send message to the Topic
Now I want know why the Message Driven Bean doesn't work for those Topic
I want create a Message Driven Bean for Topic in the same way I created for Queue
I don't know what is problem , please advice me
Thanks

Could you try adding a activationconfig to the message-driven bean, for example,
@MessageDriven(mappedName = "jndi.testTopic", activationConfig = {
        @ActivationConfigProperty(propertyName = "destinationName", propertyValue = "jndi.testTopic"),
        @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Topic")
public class aliJMS1_MessageDrivenEJBBean implements MessageListener {
    public void onMessage(Message message) {
      if(message instanceof TextMessage ){
        TextMessage txtM=(TextMessage) message;
        try{
          System.out.println(txtM.getText());
        }catch(Exception ex){
          ex.printStackTrace();
}

HT1923 after following the instructions to completing uninstall iTunes and related components, and I'd restarted and reinstalled iTunes, i received the error message that iTunes couldn't load because the deleted Apple Application Support wasn't present. W

After following the instructions to completly uninstall iTunes and related components, I restarted computerand reinstalled iTunes, Then I received the error message that iTunes couldn't load because program file Apple Application Support (deleted as per instructions) wasn't present. What now?

With the Error 2, let's try a standalone Apple Application Support install. It still might not install, but fingers crossed any error messages will give us a better idea of the underlying cause of the issue.
Download and save a copy of the iTunesSetup.exe (or iTunes64setup.exe) installer file to your hard drive:
http://www.apple.com/itunes/download/
Download and install the free trial version of WinRAR:
http://www.rarlab.com/download.htm
Right-click the iTunesSetup.exe (or iTunes64Setup.exe), and select "Extract to iTunesSetup" (or "Extract to iTunes64Setup"). WinRAR will expand the contents of the file into a folder called "iTunesSetup" (or "iTunes64Setup").
Go into the folder and doubleclick the AppleApplicationSupport.msi to do a standalone AAS install.
Does it install properly for you?
If instead you get an error message during the install, let us know what it says. (Precise text, please.)

B2B using JMS and Processing Messages with Message Driven Beans

We want to be able to use B2B to send messages to a JMS queue and then process messages from B2B using a Message Driven Bean. Is this supported.
We are using B2B 10.2.0.2 with Patchset 4.

Hello,
In 10.1.2.0.2 B2B , as part of the internal Delivery channel B2B can only send and receive messages from JMS queues.
Rgds,Ramesh

JMS / Message Driven Bean not processing message

I am having a problem getting an MDB to work on Weblogic Server 7x.
          Basically I have written a simple Bean which simply prints a message.
          I have a JMS client which creates a message (javax.jms.TextMessage)
          and successfully adds it to the queue (javax.jms.Queue). The code
          looks as follows:
          public void sendText(String message) throws Exception
          TextMessage textMessage = getQueueSession().createTextMessage();
          System.out.println("Created Message: "+message);
          textMessage.clearBody();
          textMessage.setText(message);
          System.out.println("Sending Message");
          getQueueSender().send(textMessage);
          System.out.println("Sent Message");
          The message is getting onto the queue as we can monitor this from the
          weblogic console, everytime we run the JMS Test client the number of
          messages on the queue increases however these message never seem to be
          processed. Here is a sample of the ejb-jar.xml
          <message-driven>
          <display-name>JMSBatchReceiver</display-name>
          <ejb-name>JMSBatchReceiver</ejb-name>
          <ejb-class>com.batch.JMSBatchReceiverBean</ejb-class>
          <transaction-type>Container</transaction-type>
          <message-driven-destination>
          <destination-type>javax.jms.Queue</destination-type>
          </message-driven-destination>
          </message-driven>
          Here is a sample from the weblogic-ejb-jar.xml
          <weblogic-enterprise-bean>
          <ejb-name>JMSBatchReceiver</ejb-name>
          <message-driven-descriptor>
          <pool>
          <max-beans-in-free-pool>5</max-beans-in-free-pool>
          </pool>
          <destination-jndi-name>jms/BatchQueue</destination-jndi-name>
          <connection-factory-jndi-name>jms/BatchQueueConnectionFactory</connection-factory-jndi-name>
          </message-driven-descriptor>
          </weblogic-enterprise-bean>
          And here is an excerpt from the config.xml;
          <JMSConnectionFactory JNDIName="jms/BatchQueueConnectionFactory"
          Name="jms/BatchQueueConnectionFactory" Targets="myserver"/>
          <JMSServer Name="JMSBatchServer" Targets="myserver">
          <JMSQueue DeliveryModeOverride="Persistent"
          JNDIName="jms/BatchQueue" Name="jms/BatchQueue"/>
          </JMSServer>
          Any ideas.....
          Best Regards
          Brian


Check the UserTransactions and XATransactions checkbox for your custom connection factory.
          Tom Barnes wrote:
          > Confirm that the bean is deployed by checking the server's
          > deployments on the console.
          >
          > Check your server log for messages. If the MDB is failing to
          > attach, it will log errors and warnings.
          >
          > I wonder if the "/" in your descriptor jars is messing things
          > up as a special character? Try naming your JNDI resources
          > without slashes.
          >
          > Note that there is no need to specify a connection factory for
          > MDBs - the default one is usually fine.
          >
          > Tom
          >
          > Brian Seery wrote:
          > > I am having a problem getting an MDB to work on Weblogic Server 7x.
          > > Basically I have written a simple Bean which simply prints a message.
          > > I have a JMS client which creates a message (javax.jms.TextMessage)
          > > and successfully adds it to the queue (javax.jms.Queue). The code
          > > looks as follows:
          > >
          > > public void sendText(String message) throws Exception
          > > {
          > > TextMessage textMessage = getQueueSession().createTextMessage();
          > > System.out.println("Created Message: "+message);
          > > textMessage.clearBody();
          > > textMessage.setText(message);
          > > System.out.println("Sending Message");
          > > getQueueSender().send(textMessage);
          > > System.out.println("Sent Message");
          > > }
          > >
          > > The message is getting onto the queue as we can monitor this from the
          > > weblogic console, everytime we run the JMS Test client the number of
          > > messages on the queue increases however these message never seem to be
          > > processed. Here is a sample of the ejb-jar.xml
          > >
          > > <message-driven>
          > > <display-name>JMSBatchReceiver</display-name>
          > > <ejb-name>JMSBatchReceiver</ejb-name>
          > > <ejb-class>com.batch.JMSBatchReceiverBean</ejb-class>
          > > <transaction-type>Container</transaction-type>
          > > <message-driven-destination>
          > > <destination-type>javax.jms.Queue</destination-type>
          > > </message-driven-destination>
          > > </message-driven>
          > >
          > > Here is a sample from the weblogic-ejb-jar.xml
          > >
          > > <weblogic-enterprise-bean>
          > > <ejb-name>JMSBatchReceiver</ejb-name>
          > > <message-driven-descriptor>
          > > <pool>
          > > <max-beans-in-free-pool>5</max-beans-in-free-pool>
          > > </pool>
          > > <destination-jndi-name>jms/BatchQueue</destination-jndi-name>
          > > <connection-factory-jndi-name>jms/BatchQueueConnectionFactory</connection-factory-jndi-name>
          > > </message-driven-descriptor>
          > > </weblogic-enterprise-bean>
          > >
          > > And here is an excerpt from the config.xml;
          > > <JMSConnectionFactory JNDIName="jms/BatchQueueConnectionFactory"
          > > Name="jms/BatchQueueConnectionFactory" Targets="myserver"/>
          > > <JMSServer Name="JMSBatchServer" Targets="myserver">
          > > <JMSQueue DeliveryModeOverride="Persistent"
          > > JNDIName="jms/BatchQueue" Name="jms/BatchQueue"/>
          > > </JMSServer>
          > >
          > > Any ideas.....
          > >
          > > Best Regards
          > >
          > > Brian
          Rajesh Mirchandani
          Developer Relations Engineer
          BEA Support

Photoshop.exe Process Hanging Around After Exit - Chris Cox

It happens from time to time, and this time I was able to breakpoint it to show where it's hung up. I'm posting this not looking for help, but primarily to pass the information on to Chris Cox on the outside chance it might help Adobe fix the issue...
-Noel

Highly useful for international work: http://www.google.com/language_tools
Translation:
In Photoshop cs5 has encountered a problem and needs to close. We apologize for the inconvenience
and
You were engaged in an operation. This information might be lost
-Noel

Firefox tabs hang around after closing them

When I have multiple tabs open, and I close a tab, the tab browser still shows the page of the closed tab, while the tab is removed from the tab bar. The only way of changing the view is to navigate to the next tab. If there is a flash playing on the page, it continues to play until it's finished, even after you navigate to the next tab.
== This happened ==
Every time Firefox opened
== July 17, 2010. After watching a video on screencastslonline.com, I noticed this as an issue. See full link below.

You can check for problems with the sessionstore.js and sessionstore.bak files in the Firefox profile folder that store session data.
Delete the sessionstore.js file and possible sessionstore-##.js files with a number and sessionstore.bak in the Firefox profile folder.
*Help > Troubleshooting Information > Profile Directory: Show Folder (Open Directory)
*http://kb.mozillazine.org/Profile_folder_-_Firefox
*http://kb.mozillazine.org/Multiple_profile_files_created
Deleting sessionstore.js will cause App Tabs and Tab Groups and open and closed (undo) tabs to get lost and you will have to recreate them (make a note or bookmark them).

Tecra M5 hangs during the shutdown process

Thanks to those to responded to my query. With your advice, I've now uninstalled Norton Ghost - and the problem has gone away, my machine now shuts down, goes into standy and hibernates correctly and wakes up again correctly. The next question to be investigated is why this should happen with Ghost and this is something I intend to take up with Norton. If I come up with answer, I'll post again. Cheers

I have also installed the Norton Ghost on my notebook but I have never had any problems with the shut downs.
I think the Ghost was started always while the Windows was booted up and the ghost was running in the background.
This could be disabled in the registry.
I have removed the ghost registry entry in Hkey current machine software Microsoft windows current version - run

When will IAS support Message Driven Beans? My group needs to port an application from WebLogic to iPlanet which is using MDBs. Also, when will all of the EJB 2.0 specification be implmented?

Tim,
We will have development-only support for MDBs in the 6.5 release which is scheduled to release this month. The full EJB 2.0 spec will be supported in the next iteration of the product which is scheduled to be released in the summer.

I am having problems shutting down my MacBook Pro. I go to the apple and click shutdown or restart, it appears the shutdown process starts, the screen goes blue and the little circle keeps going round and round, but nothing happens even after 30 minutes.

I am having problems shutting down my MacBook Pro. I go to the apple and click shutdown or restart, it appears the shutdown process starts, the screen goes blue and the little circle keeps going round and round, but nothing happens even after 30 minutes.

Make sure you quit all your applications before shutting down.
And try resetting the SMC.
Intel-based Macs: Resetting the System Management Controller (SMC)

[SOLVED]Shutdown process became noisy after an update of systemd

Hello all.
I recently found that there is a bit more output than before while shutdown process -- As far as I remember, in February, there are only two-line-output randomly while shutdown process.
But now it seems a bit more noisy , when I run 「halt」, I'll get several lines output almost full in one screen. After downgrade many many packages, I found that an systemd update (208-11 -> 209-2) cause this problem. Here is the output after upgrade to testing/systemd 209-2:
Sending SIGTERM to remaining processes...
Sending SIGKILL to remaining processes...
Unmounting file systems.
Unmounting /oldroot/sys/fs/cgroup/blkio.
Unmounting /oldroot/sys/fs/cgroup/net_cls.
Unmounting /oldroot/sys/fs/cgroup/freezer.
Unmounting /oldroot/sys/fs/cgroup/devices.
Unmounting /oldroot/sys/fs/cgroup/memory.
Unmounting /oldroot/sys/fs/cgroup/cpu,cpuacct.
Unmounting /oldroot/sys/fs/cgroup/cpuset.
Unmounting /oldroot/sys/fs/pstore.
Unmounting /oldroot/sys/fs/cgroup/systemd.
Unmounting /oldroot/sys/fs/cgroup.
Unmounting /oldroot/dev/pts.
Unmounting /oldroot/dev/shm.
Unmounting /oldroot/sys/kernel/security.
Unmounting /oldroot.
Unmounting /oldroot/run.
Unmounting /oldroot/dev.
Unmounting /oldroot/sys.
Unmounting /oldroot/proc.
Unmounting /oldroot.
All filesystems unmounted.
Deactivating swaps.
All swaps deactivated.
Detaching loop devices.
All DM devices detached.
Storage is finalized.
Powering off.
(there may be typo in above output, because I don't know how to get the log while shutdown process(Update: See serial console) -- so I type them here manually )
Addition information:
Here is my output of grep -v '^#' /etc/mkinitcpio.conf|sed '/^$/d':
MODULES=""
BINARIES=""
FILES=""
HOOKS="base udev autodetect modconf block filesystems keyboard"
COMPRESSION="xz"
also, cat /proc/cmdline:
BOOT_IMAGE=/arch/root0/boot/vmlinuz-linux rw root=LABEL=20140102 rootflags=subvol=arch/root0 ro quiet
Before update to systemd 209, there is not such a lot of output(only two-line-randomly). Does anyone know how to hide these additional output after systemd 209 ?
Update:
on 2014-10-24, fixed upstream:
https://bugs.freedesktop.org/show_bug.cgi?id=79582
http://cgit.freedesktop.org/systemd/sys … c578555ac5
Last edited by izmntuk (2014-10-24 14:37:38)

Scimmia wrote:
testing/systemd 209-2? Are we talking about Arch here? Arch is up to 212 in Core and 213 in Testing.
Anyway, this was discussed before, you should be able to find it with a search for "oldroot".
Thanks for keyword.
Yesterday I downgrade my another Arch Linux in Virtualbox from 2014/05 to 2014/02 (via A.R.M), just want to find that which update cause the 「quiet」 parameter has no effect on systemd-shutdown. I've been found some upstream changes which likely to change the behaviour since systemd 206: this commit(perhaps I misunderstand something)... Anyway I'll try to resolve this problem though it is a bit difficult for me

Have Photoshop 7.0.1 - recently quit saving as or saving photos after changes. Just hangs until i kill process with task manager. Have uninstalled and reinstalled. Any suggestions? I don't want to upgrade to CC as I hate subscription services and often ha

Just hangs until i kill process with task manager. Have uninstalled and reinstalled. Any suggestions? I don't want to upgrade to CC as I hate subscription services and often have internet connection services interuppted.

Which operating system are you using?
Resetting the photoshop preferences might cure the problem.
Press and hold down the Shift+Ctrl+Alt keys down just after starting the launch of photoshop 7
(Shift-Command-Option on a mac)
Keep holding the keys down until you get a dialog asking if you want to delete the adobe photoshop settings file
Press Yes

Left speaker no sound, no wi-fi, hang up after first or second booting then blue screen appears

hi there! my laptop always hangs up everytime I open it. Sometimes it open up after minutes of waiting then gradually hangs up before blue screen appears. I had to long press the start button again and again before I could use it.
By the way, there are times I had to switch into safe mode and found out that the audio is not working anymore. During normal mode, only the left speaker is operational. Lastly, wi-fi signal will constantly disappear after rebooting.
please help
robert

Hi,
Have not seen any reports of negative experiences (unlike recent Microsoft updates) from the last batch of Windows Updates.
I would guess you have a coincidental hardware problem.
A failed HDD would yield an error at boot. You would still be able to boot to the BIOS if you desired.
Normally failed devices (memory, GPU, CPU) will give audible and visual error codes. Exceptions will always happen.
Could be the battery, power supply, or maybe the motherboard has bit the dust. You will probably receive no visual or audible error messages when the motherboard fails.
Try booting with one monitor.
Jaco
****I am not an HP employee****
Please give a" Kudos, Thumbs Up" if advice received is relevant or" Accept as Solution" to assist other forum users having a similar problem.
Errare humanum est.

WebLogic hangs around after shutdown process appears to complete - Message Driven Bean related

Similar Messages

Maybe you are looking for