Re: [drlvm] getting activeMQ to run

[Geir Magnusson Jr.]

On Sep 23, 2006, at 12:00 AM, Nathan Beyer wrote:





-Original Message-
From: Gregory Shimansky [mailto:[EMAIL PROTECTED]
Sent: Friday, September 22, 2006 7:43 PM
On Saturday 23 September 2006 04:20 Geir Magnusson Jr. wrote:


Hm.

LogManger's initializer does

   Logger root = Logger.getLogger();

and Logger has

   public final static Logger global = Logger.getLogger(global);

which eventually executes

LogManager man = LogManager.getLogManager();

and around we go.

So why don't we always run aground with this?  Why is this the first
time we see this?


I think that only stack trace of NPE can show the real reason of the
problem... If it is NPE (uninitialized field has to be null),  
otherwise my

guess could be wrong.


Wouldn't a simple approach to fixing this be create the root logger  
with a
custom implementation of Logger instead of using Logger.getLogger 
() to

create it. Also, the same thing would be done for the global logger
initialization. This could be done with a package-private  
constructor just
for this special purpose. This way the initialization of LogManager  
can use

Logger, but the initialization of Logger doesn't use LogManager.



How would the root logger be a Logger?

geir



-Nathan



The workaround for such cases is simple, in methods like

void m () {
f.m2();
}

it is necessary to write

void m () {
if (f == null)
initf();

f.m2();
}

This, in case may cause infinite recursion because in case  
initialization

of
field f may still refer to method m in other classes, but it is  
easier to

resolve.

--
Gregory Shimansky, Intel Middleware Products Division

-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: harmony-dev- 
[EMAIL PROTECTED]



-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [drlvm] getting activeMQ to run

[Geir Magnusson Jr.]

Now I'm seeing it :)

On Sep 22, 2006, at 5:29 PM, Nikolay Kuznetsov wrote:


Ok then, it was suse 9,  ia32.

On 9/23/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:

what platform?  I'm not seeing that...

On Sep 22, 2006, at 4:01 PM, Nikolay Kuznetsov wrote:

  core dumps in debug and prints something like this in release:
  WARN  DefaultJDBCAdapter - Could not create JDBC
 tables;
  they could already exist. Failure was: 

 That might be simply because you created the tables needed when  
you

 ran the first time?

 I don't know for sure, but J9 works fine w/o any warnings:

 INFO  JDBCPersistenceAdapter - Database driver recognized:
 [apache_derby_embedded_jdbc_driver]
 INFO  JournalPersistenceAdapter  - Journal Recovery Started  
from:

 Active Journal: using 5 x 20.0 Megs at:
 /nfs/pb/home/nakuznet/disk_j/workspace/harmony.orig/incubator-
 activemq-4.0.1/activemq-data/journal
 ...

 ... and the fact that debug version core dumps, also looks
 suspicious :)

 Nik.

  , but finally starts:
  INFO  BrokerService  - ActiveMQ JMS Message  
Broker

  (localhost, ID:pbtmrte007-57413-1158949586838-1:0) started
 
  Will continue investigate.

 So this look ok...

 My tests w/ the patch show it running, and I was able to run
 producer/
 consumer tests

 geir

 
  Nik.
 
  On 9/22/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:
  First, thanks so much for the fast response and good solution.
 
  I don't see any problem with this patch, but you're right - I
 don't
  understand why we have it, since Logger should set it's  
global

  field to getLogger(global) in the static initialization.
 
  I have the same problem with J9, so I don't think it's a VM
 problem.
 
  If no one complains, I'm going to test it, apply it, and add a
 JIRA
  to look at the fact that global isn't set...or tell me why it
  shouldn't be
 
  geir
 
 
  On Sep 22, 2006, at 1:51 PM, Nikolay Kuznetsov wrote:
 
   Hello,
  
   I was able to run ActiveQM on Linux with patch attached.
 Looks like
   something is broken in logger static initialization sequence.
  Though
   this patch helpps in running ActiveQM, I would treat this
 patch as
   workaround, this issue requires some more analysis and  
testing.

  
   Nik.
   On 9/22/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:
  
   On Sep 22, 2006, at 12:47 AM, Vladimir Gorr wrote:
  
On 9/22/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:
   
   
On Sep 22, 2006, at 12:37 AM, Vladimir Gorr wrote:
   
 On 9/22/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:

 Even though we have the jar issue fixed w/t he  
launcher-

  based
build,
 I still can't run ActiveMQ using release build on  
Ubuntu.


 Can anyone else report success?  Or a patch? :)


 I was succesfull on Windows. No success exist for Linux
  however.
   
What do you see on linux?
   
   
ACTIVEMQ_HOME: /nfs/ins/proj/drl/coreapi/vgorr/Tools/
 incubator-
activemq-4.0
Loading message broker from: xbean:activemq.xml
ERROR: java.lang.RuntimeException: Failed to execute start
 task.
Reason:
org.springframework.beans.factory.BeanCreationException:
 Error
creating bean
with name
  'org.apache.activemq.store.PersistenceAdapterFactoryBean'
defined
in class path resource [activemq.xml]: Instantiation of  
bean

   failed;
...
  
   Yah, that's what I get.  We really need to get this kind of
 thing
   worked out, and fast...
  
   geir
  
snipped
...
   
Steps I do are the following:
 1. unset JAVA_HOME
 2. set PATH=.../jre/bin;PATH
 3. cd .../activemq-3.2.3\bin; activemq

 Are these steps correct?
   
Close enough.  I set JAVA_HOME to the harmony jre  
directory

   (deploy/
jre), added bin to the path, and then
   
  sh bin/activemq
   
But I'm using activeMQ 4.0.something
   
   
   
Yes, it seems this version doesn't work correctly. At
 least on
   Linux.
I'll try this on Windows as well.
   
Thanks,
Vladimir.
   
   
   
 Thanks,
 Vladimir.


 geir



   
  
 
  
-

 Terms of use : http://incubator.apache.org/harmony/
  mailing.html
 To unsubscribe, e-mail: harmony-dev-
[EMAIL PROTECTED]
 For additional commands, e-mail: harmony-dev-
 [EMAIL PROTECTED]


   
   
   
  
 
  
-

Terms of use : http://incubator.apache.org/harmony/
 mailing.html
To unsubscribe, e-mail: harmony-dev-
   [EMAIL PROTECTED]
For additional commands, e-mail: harmony-dev-
[EMAIL PROTECTED]
   
   
  
  
  
 
  
-
   Terms of use : http://incubator.apache.org/harmony/ 
mailing.html

   To unsubscribe, e-mail: harmony-dev-
  [EMAIL PROTECTED]
   For additional commands, e-mail: harmony-dev-
  

RE: [drlvm] getting activeMQ to run

[Nathan Beyer]

The global logger and root logger would just be constructed using new
Logger() and then LogManager would set the parent relationship in it static
initialization. I'm playing around with it a bit now.

Also, it seems that the application of a patch to create revision 436703
seems to have broken another application, in this case Tomcat. The public
readConfiguration method was replaced with a call to readConfigurationImpl,
which means the LogManager override mechanism won't work correctly. I'm
fixing that on.

-Nathan

 -Original Message-
 From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED]
 Sent: Saturday, September 23, 2006 5:48 AM
 To: harmony-dev@incubator.apache.org
 Subject: Re: [drlvm] getting activeMQ to run
 
 
 On Sep 23, 2006, at 12:00 AM, Nathan Beyer wrote:
 
 
 
  -Original Message-
  From: Gregory Shimansky [mailto:[EMAIL PROTECTED]
  Sent: Friday, September 22, 2006 7:43 PM
  On Saturday 23 September 2006 04:20 Geir Magnusson Jr. wrote:
 
  Hm.
 
  LogManger's initializer does
 
 Logger root = Logger.getLogger();
 
  and Logger has
 
 public final static Logger global = Logger.getLogger(global);
 
  which eventually executes
 
  LogManager man = LogManager.getLogManager();
 
  and around we go.
 
  So why don't we always run aground with this?  Why is this the first
  time we see this?
 
  I think that only stack trace of NPE can show the real reason of the
  problem... If it is NPE (uninitialized field has to be null),
  otherwise my
  guess could be wrong.
 
  Wouldn't a simple approach to fixing this be create the root logger
  with a
  custom implementation of Logger instead of using Logger.getLogger
  () to
  create it. Also, the same thing would be done for the global logger
  initialization. This could be done with a package-private
  constructor just
  for this special purpose. This way the initialization of LogManager
  can use
  Logger, but the initialization of Logger doesn't use LogManager.
 
 
 How would the root logger be a Logger?
 
 geir
 
 
  -Nathan
 
 
  The workaround for such cases is simple, in methods like
 
  void m () {
  f.m2();
  }
 
  it is necessary to write
 
  void m () {
  if (f == null)
  initf();
 
  f.m2();
  }
 
  This, in case may cause infinite recursion because in case
  initialization
  of
  field f may still refer to method m in other classes, but it is
  easier to
  resolve.
 
  --
  Gregory Shimansky, Intel Middleware Products Division
 
  -
  Terms of use : http://incubator.apache.org/harmony/mailing.html
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: harmony-dev-
  [EMAIL PROTECTED]
 
 
  -
  Terms of use : http://incubator.apache.org/harmony/mailing.html
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 -
 Terms of use : http://incubator.apache.org/harmony/mailing.html
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [drlvm] getting activeMQ to run

[Geir Magnusson Jr.]

On Sep 23, 2006, at 1:24 PM, Nathan Beyer wrote:


The global logger and root logger would just be constructed using new
Logger() and then LogManager would set the parent relationship in  
it static

initialization. I'm playing around with it a bit now.


Sorry for being dense, but how is that different from what we have now?



Also, it seems that the application of a patch to create revision  
436703
seems to have broken another application, in this case Tomcat. The  
public
readConfiguration method was replaced with a call to  
readConfigurationImpl,
which means the LogManager override mechanism won't work correctly.  
I'm

fixing that on.

-Nathan


-Original Message-
From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED]
Sent: Saturday, September 23, 2006 5:48 AM
To: harmony-dev@incubator.apache.org
Subject: Re: [drlvm] getting activeMQ to run


On Sep 23, 2006, at 12:00 AM, Nathan Beyer wrote:





-Original Message-
From: Gregory Shimansky [mailto:[EMAIL PROTECTED]
Sent: Friday, September 22, 2006 7:43 PM
On Saturday 23 September 2006 04:20 Geir Magnusson Jr. wrote:


Hm.

LogManger's initializer does

   Logger root = Logger.getLogger();

and Logger has

   public final static Logger global = Logger.getLogger(global);

which eventually executes

LogManager man = LogManager.getLogManager();

and around we go.

So why don't we always run aground with this?  Why is this the  
first

time we see this?


I think that only stack trace of NPE can show the real reason of  
the

problem... If it is NPE (uninitialized field has to be null),
otherwise my
guess could be wrong.


Wouldn't a simple approach to fixing this be create the root logger
with a
custom implementation of Logger instead of using Logger.getLogger
() to
create it. Also, the same thing would be done for the global logger
initialization. This could be done with a package-private
constructor just
for this special purpose. This way the initialization of LogManager
can use
Logger, but the initialization of Logger doesn't use LogManager.



How would the root logger be a Logger?

geir



-Nathan



The workaround for such cases is simple, in methods like

void m () {
f.m2();
}

it is necessary to write

void m () {
if (f == null)
initf();

f.m2();
}

This, in case may cause infinite recursion because in case
initialization
of
field f may still refer to method m in other classes, but it is
easier to
resolve.

--
Gregory Shimansky, Intel Middleware Products Division

--- 
--

Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev- 
[EMAIL PROTECTED]

For additional commands, e-mail: harmony-dev-
[EMAIL PROTECTED]



 
-

Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: harmony-dev- 
[EMAIL PROTECTED]





-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: harmony-dev- 
[EMAIL PROTECTED]



-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [drlvm] getting activeMQ to run

[Nathan Beyer]

 -Original Message-
 From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED]
 On Sep 23, 2006, at 1:24 PM, Nathan Beyer wrote:
 
  The global logger and root logger would just be constructed using new
  Logger() and then LogManager would set the parent relationship in
  it static
  initialization. I'm playing around with it a bit now.
 
 Sorry for being dense, but how is that different from what we have now?

It eliminates the circular execution between the static initializers and
makes the code more simple and straightforward by having only one path for
initialization, instead of two paths that execute based which class is
loaded first. I have the code done and all of the tests passing. I'll check
it in and if it's disliked, we can roll it back.

-Nathan

 
 
  Also, it seems that the application of a patch to create revision
  436703
  seems to have broken another application, in this case Tomcat. The
  public
  readConfiguration method was replaced with a call to
  readConfigurationImpl,
  which means the LogManager override mechanism won't work correctly.
  I'm
  fixing that on.
 
  -Nathan
 
  -Original Message-
  From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED]
  Sent: Saturday, September 23, 2006 5:48 AM
  To: harmony-dev@incubator.apache.org
  Subject: Re: [drlvm] getting activeMQ to run
 
 
  On Sep 23, 2006, at 12:00 AM, Nathan Beyer wrote:
 
 
 
  -Original Message-
  From: Gregory Shimansky [mailto:[EMAIL PROTECTED]
  Sent: Friday, September 22, 2006 7:43 PM
  On Saturday 23 September 2006 04:20 Geir Magnusson Jr. wrote:
 
  Hm.
 
  LogManger's initializer does
 
 Logger root = Logger.getLogger();
 
  and Logger has
 
 public final static Logger global = Logger.getLogger(global);
 
  which eventually executes
 
  LogManager man = LogManager.getLogManager();
 
  and around we go.
 
  So why don't we always run aground with this?  Why is this the
  first
  time we see this?
 
  I think that only stack trace of NPE can show the real reason of
  the
  problem... If it is NPE (uninitialized field has to be null),
  otherwise my
  guess could be wrong.
 
  Wouldn't a simple approach to fixing this be create the root logger
  with a
  custom implementation of Logger instead of using Logger.getLogger
  () to
  create it. Also, the same thing would be done for the global logger
  initialization. This could be done with a package-private
  constructor just
  for this special purpose. This way the initialization of LogManager
  can use
  Logger, but the initialization of Logger doesn't use LogManager.
 
 
  How would the root logger be a Logger?
 
  geir
 
 
  -Nathan
 
 
  The workaround for such cases is simple, in methods like
 
  void m () {
  f.m2();
  }
 
  it is necessary to write
 
  void m () {
  if (f == null)
  initf();
 
  f.m2();
  }
 
  This, in case may cause infinite recursion because in case
  initialization
  of
  field f may still refer to method m in other classes, but it is
  easier to
  resolve.
 
  --
  Gregory Shimansky, Intel Middleware Products Division
 
  ---
  --
  Terms of use : http://incubator.apache.org/harmony/mailing.html
  To unsubscribe, e-mail: harmony-dev-
  [EMAIL PROTECTED]
  For additional commands, e-mail: harmony-dev-
  [EMAIL PROTECTED]
 
 
  
  -
  Terms of use : http://incubator.apache.org/harmony/mailing.html
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: harmony-dev-
  [EMAIL PROTECTED]
 
 
 
  -
  Terms of use : http://incubator.apache.org/harmony/mailing.html
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: harmony-dev-
  [EMAIL PROTECTED]
 
 
  -
  Terms of use : http://incubator.apache.org/harmony/mailing.html
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 -
 Terms of use : http://incubator.apache.org/harmony/mailing.html
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [drlvm] getting activeMQ to run

[Geir Magnusson Jr.]

I just gave it a quick look.  Given that you've taken the creation of  
Loggers away from Logger via it's factory, and now moved it into  
LogManager, how can we be sure we never have more than one root logger?


geir

On Sep 23, 2006, at 2:18 PM, Nathan Beyer wrote:


-Original Message-
From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED]
On Sep 23, 2006, at 1:24 PM, Nathan Beyer wrote:

The global logger and root logger would just be constructed using  
new

Logger() and then LogManager would set the parent relationship in
it static
initialization. I'm playing around with it a bit now.


Sorry for being dense, but how is that different from what we have  
now?


It eliminates the circular execution between the static  
initializers and
makes the code more simple and straightforward by having only one  
path for

initialization, instead of two paths that execute based which class is
loaded first. I have the code done and all of the tests passing.  
I'll check

it in and if it's disliked, we can roll it back.

-Nathan





Also, it seems that the application of a patch to create revision
436703
seems to have broken another application, in this case Tomcat. The
public
readConfiguration method was replaced with a call to
readConfigurationImpl,
which means the LogManager override mechanism won't work correctly.
I'm
fixing that on.

-Nathan


-Original Message-
From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED]
Sent: Saturday, September 23, 2006 5:48 AM
To: harmony-dev@incubator.apache.org
Subject: Re: [drlvm] getting activeMQ to run


On Sep 23, 2006, at 12:00 AM, Nathan Beyer wrote:





-Original Message-
From: Gregory Shimansky [mailto:[EMAIL PROTECTED]
Sent: Friday, September 22, 2006 7:43 PM
On Saturday 23 September 2006 04:20 Geir Magnusson Jr. wrote:


Hm.

LogManger's initializer does

   Logger root = Logger.getLogger();

and Logger has

   public final static Logger global = Logger.getLogger 
(global);


which eventually executes

LogManager man = LogManager.getLogManager();

and around we go.

So why don't we always run aground with this?  Why is this the
first
time we see this?


I think that only stack trace of NPE can show the real reason of
the
problem... If it is NPE (uninitialized field has to be null),
otherwise my
guess could be wrong.


Wouldn't a simple approach to fixing this be create the root  
logger

with a
custom implementation of Logger instead of using Logger.getLogger
() to
create it. Also, the same thing would be done for the global  
logger

initialization. This could be done with a package-private
constructor just
for this special purpose. This way the initialization of  
LogManager

can use
Logger, but the initialization of Logger doesn't use LogManager.



How would the root logger be a Logger?

geir



-Nathan



The workaround for such cases is simple, in methods like

void m () {
f.m2();
}

it is necessary to write

void m () {
if (f == null)
initf();

f.m2();
}

This, in case may cause infinite recursion because in case
initialization
of
field f may still refer to method m in other classes, but it is
easier to
resolve.

--
Gregory Shimansky, Intel Middleware Products Division

- 
--

--
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-
[EMAIL PROTECTED]
For additional commands, e-mail: harmony-dev-
[EMAIL PROTECTED]



-- 
--

-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev- 
[EMAIL PROTECTED]

For additional commands, e-mail: harmony-dev-
[EMAIL PROTECTED]




--- 
--

Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev- 
[EMAIL PROTECTED]

For additional commands, e-mail: harmony-dev-
[EMAIL PROTECTED]



 
-

Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: harmony-dev- 
[EMAIL PROTECTED]





-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: harmony-dev- 
[EMAIL PROTECTED]



-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [drlvm] getting activeMQ to run

[Nathan Beyer]

This may be considered a bug, maybe not, but if you write a simple program
that only references the Logger.global field, nothing will be logged out on
Sun's RI 5.0_8 implementation. However, if you lookup the global logger
(Logger.getLogger(global)), then data will be logged out.

Here's the test - run this and nothing will be written:
public class GlobalLogger {
public static void main(String[] args) {
Logger global = Logger.global;
global.severe(hello);
}
}


Now, if you run this, the a message will be written to the console:
public class GlobalLogger {
public static void main(String[] args) {
Logger global = Logger.getLogger(global);
global.severe(hello);
}
}

And if you extend it a bit farther with this example, the first message
isn't logged, but the second two are.
public class GlobalLogger {
public static void main(String[] args) {
Logger global = Logger.global;
global.severe(hello);

global = Logger.getLogger(global);
global.severe(hello again);

global = Logger.global;
global.severe(and again);
}
}

Then add another variation by looking up an arbitrary logger (to spark the
LogManager up); here the output is the same as before
public class GlobalLogger {
public static void main(String[] args) {
Logger global = Logger.global;
global.severe(hello);

global = Logger.getLogger(not_global);
global.severe(hello again);

global = Logger.global;
global.severe(and again);
}
}

The last variation then is to use the LogManager instead Logger to get the
global logger; again, the output is the same (only the last two messages are
printed).
public class GlobalLogger {
public static void main(String[] args) {
Logger global = Logger.global;
global.severe(hello);

global = LogManager.getLogManager().getLogger(global);
global.severe(hello again);

global = Logger.global;
global.severe(and again);
}
}

This tells me that the global logger is instantiated, but not initialized
with the LogManager's configuration until something calls the LogManager to
start off initialization.

The javadoc alludes to this behavior [1] by stating The global logger is
initialized by calling Logger.getLogger(global).. It seems that the
guarantee here may just be that the field is available, but it won't be
guaranteed to actually do anything until LogManager is initialized.

An additional test proves how uninitialized the global field is; this test
shows that the global field's parent logger is null (it should be root()),
but after LogManager is loaded, the parent logger is set and it is the root
logger.
public class GlobalLogger {
public static void main(String[] args) {
Logger global = Logger.global;
global.severe(hello);
System.err.println(global.getParent());

global = LogManager.getLogManager().getLogger(global);
global.severe(hello again);
System.err.println(global.getParent());

global = Logger.global;
global.severe(and again);
System.err.println(global.getParent());
}
}

The point of this whole story; regardless of what we do with the root
logger, I think our initialization of the Logger.global was incorrect, or at
least not consistent with the RI. Note, with my change it is now consistent.

-Nathan 
[1] file:///C:/install/jdk/5.0/docs/api/java/util/logging/Logger.html#global

 -Original Message-
 From: Nathan Beyer [mailto:[EMAIL PROTECTED]
 Sent: Saturday, September 23, 2006 2:38 PM
 To: harmony-dev@incubator.apache.org
 Subject: RE: [drlvm] getting activeMQ to run
 
  -Original Message-
  From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED]
 
  I just gave it a quick look.  Given that you've taken the creation of
  Loggers away from Logger via it's factory, and now moved it into
  LogManager, how can we be sure we never have more than one root logger?
 
 Keep in mind the Logger class is NOT the managing authority of Logger
 instances; this really belongs to LogManager. Logger just provides a
 helper
 method for the prescribed algorithm of LogManager.getLogger() if null
 LogManager.addLogger(new Logger()), return logger.
 
 Anyway, the LogManager is guaranteed never to maintain more than one
 instance of the root () logger because once the logger is constructed in
 LogManager static initializer, it's added to the pool of known loggers.
 Any
 subsequent calls to LogManager.addLogger() will then fail.
 
 -Nathan
 
 
  geir
 
  On Sep 23, 2006, at 2:18 PM, Nathan Beyer wrote:
 
   -Original Message-
   From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED]
   On Sep 23, 2006, at 1:24 PM, Nathan Beyer wrote:
  
   The global logger and root logger would just be constructed using
   new
   Logger() and then LogManager would set the parent relationship

Re: [drlvm] getting activeMQ to run

[Geir Magnusson Jr.]

On Sep 23, 2006, at 3:58 PM, Nathan Beyer wrote:

[1] file:///C:/install/jdk/5.0/docs/api/java/util/logging/ 
Logger.html#global


/me tries to mount a c-drive on my mac... :)

geir



-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [drlvm] getting activeMQ to run

[Nathan Beyer]

In case you're still struggling -
http://java.sun.com/j2se/1.5.0/docs/api/java/util/logging/Logger.html#global

 -Original Message-
 From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED]
 Sent: Saturday, September 23, 2006 3:48 PM
 To: harmony-dev@incubator.apache.org
 Subject: Re: [drlvm] getting activeMQ to run
 
 
 On Sep 23, 2006, at 3:58 PM, Nathan Beyer wrote:
 
  [1] file:///C:/install/jdk/5.0/docs/api/java/util/logging/
  Logger.html#global
 
 /me tries to mount a c-drive on my mac... :)
 
 geir
 
 
 
 -
 Terms of use : http://incubator.apache.org/harmony/mailing.html
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [drlvm] getting activeMQ to run

[Ivan Volosyuk]

Getting back to original topic.
I have managed to get following message on activemq-4.0.2 in release
build of drlvm:

ica-50215-1159047303002-1:0) started

Is that it? What is the exact scenario to try with activemq?

--
Ivan

On 9/24/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:


On Sep 23, 2006, at 3:58 PM, Nathan Beyer wrote:

 [1] file:///C:/install/jdk/5.0/docs/api/java/util/logging/
 Logger.html#global

/me tries to mount a c-drive on my mac... :)

geir



-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Ivan
Intel Middleware Products Division

-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [drlvm] getting activeMQ to run

[Geir Magnusson Jr.]

On Sep 23, 2006, at 5:39 PM, Ivan Volosyuk wrote:


Getting back to original topic.
I have managed to get following message on activemq-4.0.2 in release
build of drlvm:

ica-50215-1159047303002-1:0) started

Is that it? What is the exact scenario to try with activemq?


release runs - I as able to do some pub/sub tests yesterday (even  
with our sub-standard patch to Logger... :)


The problem is in debug build...

geir



--
Ivan

On 9/24/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:


On Sep 23, 2006, at 3:58 PM, Nathan Beyer wrote:

 [1] file:///C:/install/jdk/5.0/docs/api/java/util/logging/
 Logger.html#global

/me tries to mount a c-drive on my mac... :)

geir



-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: harmony-dev- 
[EMAIL PROTECTED]






--
Ivan
Intel Middleware Products Division

-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [drlvm] getting activeMQ to run

[Nikolay Kuznetsov]

Hello,

I was able to run ActiveQM on Linux with patch attached. Looks like
something is broken in logger static initialization sequence. Though
this patch helpps in running ActiveQM, I would treat this patch as
workaround, this issue requires some more analysis and testing.

Nik.
On 9/22/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:


On Sep 22, 2006, at 12:47 AM, Vladimir Gorr wrote:

 On 9/22/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:


 On Sep 22, 2006, at 12:37 AM, Vladimir Gorr wrote:

  On 9/22/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:
 
  Even though we have the jar issue fixed w/t he launcher-based
 build,
  I still can't run ActiveMQ using release build on Ubuntu.
 
  Can anyone else report success?  Or a patch? :)
 
 
  I was succesfull on Windows. No success exist for Linux however.

 What do you see on linux?


 ACTIVEMQ_HOME: /nfs/ins/proj/drl/coreapi/vgorr/Tools/incubator-
 activemq-4.0
 Loading message broker from: xbean:activemq.xml
 ERROR: java.lang.RuntimeException: Failed to execute start task.
 Reason:
 org.springframework.beans.factory.BeanCreationException: Error
 creating bean
 with name 'org.apache.activemq.store.PersistenceAdapterFactoryBean'
 defined
 in class path resource [activemq.xml]: Instantiation of bean failed;
 ...

Yah, that's what I get.  We really need to get this kind of thing
worked out, and fast...

geir

 snipped
 ...

 Steps I do are the following:
  1. unset JAVA_HOME
  2. set PATH=.../jre/bin;PATH
  3. cd .../activemq-3.2.3\bin; activemq
 
  Are these steps correct?

 Close enough.  I set JAVA_HOME to the harmony jre directory (deploy/
 jre), added bin to the path, and then

   sh bin/activemq

 But I'm using activeMQ 4.0.something



 Yes, it seems this version doesn't work correctly. At least on Linux.
 I'll try this on Windows as well.

 Thanks,
 Vladimir.



  Thanks,
  Vladimir.
 
 
  geir
 
 
 
 -
  Terms of use : http://incubator.apache.org/harmony/mailing.html
  To unsubscribe, e-mail: harmony-dev-
 [EMAIL PROTECTED]
  For additional commands, e-mail: harmony-dev-
  [EMAIL PROTECTED]
 
 


 -
 Terms of use : http://incubator.apache.org/harmony/mailing.html
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: harmony-dev-
 [EMAIL PROTECTED]




-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Index: modules/logging/src/main/java/java/util/logging/LogManager.java
===
--- modules/logging/src/main/java/java/util/logging/LogManager.java 
(revision 448895)
+++ modules/logging/src/main/java/java/util/logging/LogManager.java 
(working copy)
@@ -197,7 +197,13 @@
 
// if global logger has been initialized, set 
root as its parent
 Logger root = Logger.getLogger(); //$NON-NLS-1$
-Logger.global.setParent(root);
+Logger global = Logger.global;
+
+if (Logger.global == null) {
+global = Logger.getLogger(global);
+}
+
+global.setParent(root);
return null;
}
});
-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [drlvm] getting activeMQ to run

[Geir Magnusson Jr.]

First, thanks so much for the fast response and good solution.

I don't see any problem with this patch, but you're right - I don't  
understand why we have it, since Logger should set it's global  
field to getLogger(global) in the static initialization.


I have the same problem with J9, so I don't think it's a VM problem.

If no one complains, I'm going to test it, apply it, and add a JIRA  
to look at the fact that global isn't set...or tell me why it  
shouldn't be


geir


On Sep 22, 2006, at 1:51 PM, Nikolay Kuznetsov wrote:


Hello,

I was able to run ActiveQM on Linux with patch attached. Looks like
something is broken in logger static initialization sequence. Though
this patch helpps in running ActiveQM, I would treat this patch as
workaround, this issue requires some more analysis and testing.

Nik.
On 9/22/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:


On Sep 22, 2006, at 12:47 AM, Vladimir Gorr wrote:

 On 9/22/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:


 On Sep 22, 2006, at 12:37 AM, Vladimir Gorr wrote:

  On 9/22/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:
 
  Even though we have the jar issue fixed w/t he launcher-based
 build,
  I still can't run ActiveMQ using release build on Ubuntu.
 
  Can anyone else report success?  Or a patch? :)
 
 
  I was succesfull on Windows. No success exist for Linux however.

 What do you see on linux?


 ACTIVEMQ_HOME: /nfs/ins/proj/drl/coreapi/vgorr/Tools/incubator-
 activemq-4.0
 Loading message broker from: xbean:activemq.xml
 ERROR: java.lang.RuntimeException: Failed to execute start task.
 Reason:
 org.springframework.beans.factory.BeanCreationException: Error
 creating bean
 with name 'org.apache.activemq.store.PersistenceAdapterFactoryBean'
 defined
 in class path resource [activemq.xml]: Instantiation of bean  
failed;

 ...

Yah, that's what I get.  We really need to get this kind of thing
worked out, and fast...

geir

 snipped
 ...

 Steps I do are the following:
  1. unset JAVA_HOME
  2. set PATH=.../jre/bin;PATH
  3. cd .../activemq-3.2.3\bin; activemq
 
  Are these steps correct?

 Close enough.  I set JAVA_HOME to the harmony jre directory  
(deploy/

 jre), added bin to the path, and then

   sh bin/activemq

 But I'm using activeMQ 4.0.something



 Yes, it seems this version doesn't work correctly. At least on  
Linux.

 I'll try this on Windows as well.

 Thanks,
 Vladimir.



  Thanks,
  Vladimir.
 
 
  geir
 
 
 
  
-

  Terms of use : http://incubator.apache.org/harmony/mailing.html
  To unsubscribe, e-mail: harmony-dev-
 [EMAIL PROTECTED]
  For additional commands, e-mail: harmony-dev-
  [EMAIL PROTECTED]
 
 


  
-

 Terms of use : http://incubator.apache.org/harmony/mailing.html
 To unsubscribe, e-mail: harmony-dev- 
[EMAIL PROTECTED]

 For additional commands, e-mail: harmony-dev-
 [EMAIL PROTECTED]




-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: harmony-dev- 
[EMAIL PROTECTED]



LogManager.patch

-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [drlvm] getting activeMQ to run

[Geir Magnusson Jr.]

On Sep 22, 2006, at 3:17 PM, Nikolay Kuznetsov wrote:


Looks like there are still some problems...
Frankly I was debugging this issue with J9 too, J9 works fine now,  
while drlvm

core dumps in debug and prints something like this in release:
WARN  DefaultJDBCAdapter - Could not create JDBC tables;
they could already exist. Failure was: 


That might be simply because you created the tables needed when you  
ran the first time?




, but finally starts:
INFO  BrokerService  - ActiveMQ JMS Message Broker
(localhost, ID:pbtmrte007-57413-1158949586838-1:0) started

Will continue investigate.


So this look ok...

My tests w/ the patch show it running, and I was able to run producer/ 
consumer tests


geir



Nik.

On 9/22/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:

First, thanks so much for the fast response and good solution.

I don't see any problem with this patch, but you're right - I don't
understand why we have it, since Logger should set it's global
field to getLogger(global) in the static initialization.

I have the same problem with J9, so I don't think it's a VM problem.

If no one complains, I'm going to test it, apply it, and add a JIRA
to look at the fact that global isn't set...or tell me why it
shouldn't be

geir


On Sep 22, 2006, at 1:51 PM, Nikolay Kuznetsov wrote:

 Hello,

 I was able to run ActiveQM on Linux with patch attached. Looks like
 something is broken in logger static initialization sequence.  
Though

 this patch helpps in running ActiveQM, I would treat this patch as
 workaround, this issue requires some more analysis and testing.

 Nik.
 On 9/22/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:

 On Sep 22, 2006, at 12:47 AM, Vladimir Gorr wrote:

  On 9/22/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:
 
 
  On Sep 22, 2006, at 12:37 AM, Vladimir Gorr wrote:
 
   On 9/22/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:
  
   Even though we have the jar issue fixed w/t he launcher- 
based

  build,
   I still can't run ActiveMQ using release build on Ubuntu.
  
   Can anyone else report success?  Or a patch? :)
  
  
   I was succesfull on Windows. No success exist for Linux  
however.

 
  What do you see on linux?
 
 
  ACTIVEMQ_HOME: /nfs/ins/proj/drl/coreapi/vgorr/Tools/incubator-
  activemq-4.0
  Loading message broker from: xbean:activemq.xml
  ERROR: java.lang.RuntimeException: Failed to execute start task.
  Reason:
  org.springframework.beans.factory.BeanCreationException: Error
  creating bean
  with name  
'org.apache.activemq.store.PersistenceAdapterFactoryBean'

  defined
  in class path resource [activemq.xml]: Instantiation of bean
 failed;
  ...

 Yah, that's what I get.  We really need to get this kind of thing
 worked out, and fast...

 geir

  snipped
  ...
 
  Steps I do are the following:
   1. unset JAVA_HOME
   2. set PATH=.../jre/bin;PATH
   3. cd .../activemq-3.2.3\bin; activemq
  
   Are these steps correct?
 
  Close enough.  I set JAVA_HOME to the harmony jre directory
 (deploy/
  jre), added bin to the path, and then
 
sh bin/activemq
 
  But I'm using activeMQ 4.0.something
 
 
 
  Yes, it seems this version doesn't work correctly. At least on
 Linux.
  I'll try this on Windows as well.
 
  Thanks,
  Vladimir.
 
 
 
   Thanks,
   Vladimir.
  
  
   geir
  
  
  
 
  
-
   Terms of use : http://incubator.apache.org/harmony/ 
mailing.html

   To unsubscribe, e-mail: harmony-dev-
  [EMAIL PROTECTED]
   For additional commands, e-mail: harmony-dev-
   [EMAIL PROTECTED]
  
  
 
 
 
  
-

  Terms of use : http://incubator.apache.org/harmony/mailing.html
  To unsubscribe, e-mail: harmony-dev-
 [EMAIL PROTECTED]
  For additional commands, e-mail: harmony-dev-
  [EMAIL PROTECTED]
 
 


  
-

 Terms of use : http://incubator.apache.org/harmony/mailing.html
 To unsubscribe, e-mail: harmony-dev- 
[EMAIL PROTECTED]

 For additional commands, e-mail: harmony-dev-
 [EMAIL PROTECTED]


 LogManager.patch
  
-

 Terms of use : http://incubator.apache.org/harmony/mailing.html
 To unsubscribe, e-mail: harmony-dev- 
[EMAIL PROTECTED]
 For additional commands, e-mail: harmony-dev- 
[EMAIL PROTECTED]



-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: harmony-dev- 
[EMAIL PROTECTED]





-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
Terms of use : 

Re: [drlvm] getting activeMQ to run

[Geir Magnusson Jr.]

Why does this even run?

Logger.global is a public final static...  How can it be set like this?

geir

On Sep 22, 2006, at 1:51 PM, Nikolay Kuznetsov wrote:


Hello,

I was able to run ActiveQM on Linux with patch attached. Looks like
something is broken in logger static initialization sequence. Though
this patch helpps in running ActiveQM, I would treat this patch as
workaround, this issue requires some more analysis and testing.

Nik.
On 9/22/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:


On Sep 22, 2006, at 12:47 AM, Vladimir Gorr wrote:

 On 9/22/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:


 On Sep 22, 2006, at 12:37 AM, Vladimir Gorr wrote:

  On 9/22/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:
 
  Even though we have the jar issue fixed w/t he launcher-based
 build,
  I still can't run ActiveMQ using release build on Ubuntu.
 
  Can anyone else report success?  Or a patch? :)
 
 
  I was succesfull on Windows. No success exist for Linux however.

 What do you see on linux?


 ACTIVEMQ_HOME: /nfs/ins/proj/drl/coreapi/vgorr/Tools/incubator-
 activemq-4.0
 Loading message broker from: xbean:activemq.xml
 ERROR: java.lang.RuntimeException: Failed to execute start task.
 Reason:
 org.springframework.beans.factory.BeanCreationException: Error
 creating bean
 with name 'org.apache.activemq.store.PersistenceAdapterFactoryBean'
 defined
 in class path resource [activemq.xml]: Instantiation of bean  
failed;

 ...

Yah, that's what I get.  We really need to get this kind of thing
worked out, and fast...

geir

 snipped
 ...

 Steps I do are the following:
  1. unset JAVA_HOME
  2. set PATH=.../jre/bin;PATH
  3. cd .../activemq-3.2.3\bin; activemq
 
  Are these steps correct?

 Close enough.  I set JAVA_HOME to the harmony jre directory  
(deploy/

 jre), added bin to the path, and then

   sh bin/activemq

 But I'm using activeMQ 4.0.something



 Yes, it seems this version doesn't work correctly. At least on  
Linux.

 I'll try this on Windows as well.

 Thanks,
 Vladimir.



  Thanks,
  Vladimir.
 
 
  geir
 
 
 
  
-

  Terms of use : http://incubator.apache.org/harmony/mailing.html
  To unsubscribe, e-mail: harmony-dev-
 [EMAIL PROTECTED]
  For additional commands, e-mail: harmony-dev-
  [EMAIL PROTECTED]
 
 


  
-

 Terms of use : http://incubator.apache.org/harmony/mailing.html
 To unsubscribe, e-mail: harmony-dev- 
[EMAIL PROTECTED]

 For additional commands, e-mail: harmony-dev-
 [EMAIL PROTECTED]




-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: harmony-dev- 
[EMAIL PROTECTED]



LogManager.patch

-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [drlvm] getting activeMQ to run

[Geir Magnusson Jr.]

ignore this question please... I was multi-tasking on a conference  
call...


geir

On Sep 22, 2006, at 3:52 PM, Geir Magnusson Jr. wrote:


Why does this even run?

Logger.global is a public final static...  How can it be set like  
this?


geir

On Sep 22, 2006, at 1:51 PM, Nikolay Kuznetsov wrote:


Hello,

I was able to run ActiveQM on Linux with patch attached. Looks like
something is broken in logger static initialization sequence. Though
this patch helpps in running ActiveQM, I would treat this patch as
workaround, this issue requires some more analysis and testing.

Nik.
On 9/22/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:


On Sep 22, 2006, at 12:47 AM, Vladimir Gorr wrote:

 On 9/22/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:


 On Sep 22, 2006, at 12:37 AM, Vladimir Gorr wrote:

  On 9/22/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:
 
  Even though we have the jar issue fixed w/t he launcher-based
 build,
  I still can't run ActiveMQ using release build on Ubuntu.
 
  Can anyone else report success?  Or a patch? :)
 
 
  I was succesfull on Windows. No success exist for Linux  
however.


 What do you see on linux?


 ACTIVEMQ_HOME: /nfs/ins/proj/drl/coreapi/vgorr/Tools/incubator-
 activemq-4.0
 Loading message broker from: xbean:activemq.xml
 ERROR: java.lang.RuntimeException: Failed to execute start task.
 Reason:
 org.springframework.beans.factory.BeanCreationException: Error
 creating bean
 with name  
'org.apache.activemq.store.PersistenceAdapterFactoryBean'

 defined
 in class path resource [activemq.xml]: Instantiation of bean  
failed;

 ...

Yah, that's what I get.  We really need to get this kind of thing
worked out, and fast...

geir

 snipped
 ...

 Steps I do are the following:
  1. unset JAVA_HOME
  2. set PATH=.../jre/bin;PATH
  3. cd .../activemq-3.2.3\bin; activemq
 
  Are these steps correct?

 Close enough.  I set JAVA_HOME to the harmony jre directory  
(deploy/

 jre), added bin to the path, and then

   sh bin/activemq

 But I'm using activeMQ 4.0.something



 Yes, it seems this version doesn't work correctly. At least on  
Linux.

 I'll try this on Windows as well.

 Thanks,
 Vladimir.



  Thanks,
  Vladimir.
 
 
  geir
 
 
 
  
 
-
  Terms of use : http://incubator.apache.org/harmony/ 
mailing.html

  To unsubscribe, e-mail: harmony-dev-
 [EMAIL PROTECTED]
  For additional commands, e-mail: harmony-dev-
  [EMAIL PROTECTED]
 
 


  
 
-

 Terms of use : http://incubator.apache.org/harmony/mailing.html
 To unsubscribe, e-mail: harmony-dev- 
[EMAIL PROTECTED]

 For additional commands, e-mail: harmony-dev-
 [EMAIL PROTECTED]




 
-

Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: harmony-dev- 
[EMAIL PROTECTED]



LogManager.patch

-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: harmony-dev- 
[EMAIL PROTECTED]



-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [drlvm] getting activeMQ to run

[Nikolay Kuznetsov]

 core dumps in debug and prints something like this in release:
 WARN  DefaultJDBCAdapter - Could not create JDBC tables;
 they could already exist. Failure was: 

That might be simply because you created the tables needed when you
ran the first time?


I don't know for sure, but J9 works fine w/o any warnings:

INFO  JDBCPersistenceAdapter - Database driver recognized:
[apache_derby_embedded_jdbc_driver]
INFO  JournalPersistenceAdapter  - Journal Recovery Started from:
Active Journal: using 5 x 20.0 Megs at:
/nfs/pb/home/nakuznet/disk_j/workspace/harmony.orig/incubator-activemq-4.0.1/activemq-data/journal
...

... and the fact that debug version core dumps, also looks suspicious :)

Nik.


 , but finally starts:
 INFO  BrokerService  - ActiveMQ JMS Message Broker
 (localhost, ID:pbtmrte007-57413-1158949586838-1:0) started

 Will continue investigate.

So this look ok...

My tests w/ the patch show it running, and I was able to run producer/
consumer tests

geir


 Nik.

 On 9/22/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:
 First, thanks so much for the fast response and good solution.

 I don't see any problem with this patch, but you're right - I don't
 understand why we have it, since Logger should set it's global
 field to getLogger(global) in the static initialization.

 I have the same problem with J9, so I don't think it's a VM problem.

 If no one complains, I'm going to test it, apply it, and add a JIRA
 to look at the fact that global isn't set...or tell me why it
 shouldn't be

 geir


 On Sep 22, 2006, at 1:51 PM, Nikolay Kuznetsov wrote:

  Hello,
 
  I was able to run ActiveQM on Linux with patch attached. Looks like
  something is broken in logger static initialization sequence.
 Though
  this patch helpps in running ActiveQM, I would treat this patch as
  workaround, this issue requires some more analysis and testing.
 
  Nik.
  On 9/22/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:
 
  On Sep 22, 2006, at 12:47 AM, Vladimir Gorr wrote:
 
   On 9/22/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:
  
  
   On Sep 22, 2006, at 12:37 AM, Vladimir Gorr wrote:
  
On 9/22/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:
   
Even though we have the jar issue fixed w/t he launcher-
 based
   build,
I still can't run ActiveMQ using release build on Ubuntu.
   
Can anyone else report success?  Or a patch? :)
   
   
I was succesfull on Windows. No success exist for Linux
 however.
  
   What do you see on linux?
  
  
   ACTIVEMQ_HOME: /nfs/ins/proj/drl/coreapi/vgorr/Tools/incubator-
   activemq-4.0
   Loading message broker from: xbean:activemq.xml
   ERROR: java.lang.RuntimeException: Failed to execute start task.
   Reason:
   org.springframework.beans.factory.BeanCreationException: Error
   creating bean
   with name
 'org.apache.activemq.store.PersistenceAdapterFactoryBean'
   defined
   in class path resource [activemq.xml]: Instantiation of bean
  failed;
   ...
 
  Yah, that's what I get.  We really need to get this kind of thing
  worked out, and fast...
 
  geir
 
   snipped
   ...
  
   Steps I do are the following:
1. unset JAVA_HOME
2. set PATH=.../jre/bin;PATH
3. cd .../activemq-3.2.3\bin; activemq
   
Are these steps correct?
  
   Close enough.  I set JAVA_HOME to the harmony jre directory
  (deploy/
   jre), added bin to the path, and then
  
 sh bin/activemq
  
   But I'm using activeMQ 4.0.something
  
  
  
   Yes, it seems this version doesn't work correctly. At least on
  Linux.
   I'll try this on Windows as well.
  
   Thanks,
   Vladimir.
  
  
  
Thanks,
Vladimir.
   
   
geir
   
   
   
  
 
 -
Terms of use : http://incubator.apache.org/harmony/
 mailing.html
To unsubscribe, e-mail: harmony-dev-
   [EMAIL PROTECTED]
For additional commands, e-mail: harmony-dev-
[EMAIL PROTECTED]
   
   
  
  
  
 
 -
   Terms of use : http://incubator.apache.org/harmony/mailing.html
   To unsubscribe, e-mail: harmony-dev-
  [EMAIL PROTECTED]
   For additional commands, e-mail: harmony-dev-
   [EMAIL PROTECTED]
  
  
 
 
 
 -
  Terms of use : http://incubator.apache.org/harmony/mailing.html
  To unsubscribe, e-mail: harmony-dev-
 [EMAIL PROTECTED]
  For additional commands, e-mail: harmony-dev-
  [EMAIL PROTECTED]
 
 
  LogManager.patch
 
 -
  Terms of use : http://incubator.apache.org/harmony/mailing.html
  To unsubscribe, e-mail: harmony-dev-
 [EMAIL PROTECTED]
  For additional commands, e-mail: harmony-dev-
 [EMAIL PROTECTED]


 -
 Terms of use : http://incubator.apache.org/harmony/mailing.html
 To unsubscribe, e-mail: [EMAIL 

Re: [drlvm] getting activeMQ to run

[Geir Magnusson Jr.]

what platform?  I'm not seeing that...

On Sep 22, 2006, at 4:01 PM, Nikolay Kuznetsov wrote:


 core dumps in debug and prints something like this in release:
 WARN  DefaultJDBCAdapter - Could not create JDBC  
tables;

 they could already exist. Failure was: 

That might be simply because you created the tables needed when you
ran the first time?


I don't know for sure, but J9 works fine w/o any warnings:

INFO  JDBCPersistenceAdapter - Database driver recognized:
[apache_derby_embedded_jdbc_driver]
INFO  JournalPersistenceAdapter  - Journal Recovery Started from:
Active Journal: using 5 x 20.0 Megs at:
/nfs/pb/home/nakuznet/disk_j/workspace/harmony.orig/incubator- 
activemq-4.0.1/activemq-data/journal

...

... and the fact that debug version core dumps, also looks  
suspicious :)


Nik.


 , but finally starts:
 INFO  BrokerService  - ActiveMQ JMS Message Broker
 (localhost, ID:pbtmrte007-57413-1158949586838-1:0) started

 Will continue investigate.

So this look ok...

My tests w/ the patch show it running, and I was able to run  
producer/

consumer tests

geir


 Nik.

 On 9/22/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:
 First, thanks so much for the fast response and good solution.

 I don't see any problem with this patch, but you're right - I  
don't

 understand why we have it, since Logger should set it's global
 field to getLogger(global) in the static initialization.

 I have the same problem with J9, so I don't think it's a VM  
problem.


 If no one complains, I'm going to test it, apply it, and add a  
JIRA

 to look at the fact that global isn't set...or tell me why it
 shouldn't be

 geir


 On Sep 22, 2006, at 1:51 PM, Nikolay Kuznetsov wrote:

  Hello,
 
  I was able to run ActiveQM on Linux with patch attached.  
Looks like

  something is broken in logger static initialization sequence.
 Though
  this patch helpps in running ActiveQM, I would treat this  
patch as

  workaround, this issue requires some more analysis and testing.
 
  Nik.
  On 9/22/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:
 
  On Sep 22, 2006, at 12:47 AM, Vladimir Gorr wrote:
 
   On 9/22/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:
  
  
   On Sep 22, 2006, at 12:37 AM, Vladimir Gorr wrote:
  
On 9/22/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:
   
Even though we have the jar issue fixed w/t he launcher-
 based
   build,
I still can't run ActiveMQ using release build on Ubuntu.
   
Can anyone else report success?  Or a patch? :)
   
   
I was succesfull on Windows. No success exist for Linux
 however.
  
   What do you see on linux?
  
  
   ACTIVEMQ_HOME: /nfs/ins/proj/drl/coreapi/vgorr/Tools/ 
incubator-

   activemq-4.0
   Loading message broker from: xbean:activemq.xml
   ERROR: java.lang.RuntimeException: Failed to execute start  
task.

   Reason:
   org.springframework.beans.factory.BeanCreationException:  
Error

   creating bean
   with name
 'org.apache.activemq.store.PersistenceAdapterFactoryBean'
   defined
   in class path resource [activemq.xml]: Instantiation of bean
  failed;
   ...
 
  Yah, that's what I get.  We really need to get this kind of  
thing

  worked out, and fast...
 
  geir
 
   snipped
   ...
  
   Steps I do are the following:
1. unset JAVA_HOME
2. set PATH=.../jre/bin;PATH
3. cd .../activemq-3.2.3\bin; activemq
   
Are these steps correct?
  
   Close enough.  I set JAVA_HOME to the harmony jre directory
  (deploy/
   jre), added bin to the path, and then
  
 sh bin/activemq
  
   But I'm using activeMQ 4.0.something
  
  
  
   Yes, it seems this version doesn't work correctly. At  
least on

  Linux.
   I'll try this on Windows as well.
  
   Thanks,
   Vladimir.
  
  
  
Thanks,
Vladimir.
   
   
geir
   
   
   
  
 
  
-

Terms of use : http://incubator.apache.org/harmony/
 mailing.html
To unsubscribe, e-mail: harmony-dev-
   [EMAIL PROTECTED]
For additional commands, e-mail: harmony-dev-
[EMAIL PROTECTED]
   
   
  
  
  
 
  
-
   Terms of use : http://incubator.apache.org/harmony/ 
mailing.html

   To unsubscribe, e-mail: harmony-dev-
  [EMAIL PROTECTED]
   For additional commands, e-mail: harmony-dev-
   [EMAIL PROTECTED]
  
  
 
 
 
  
-

  Terms of use : http://incubator.apache.org/harmony/mailing.html
  To unsubscribe, e-mail: harmony-dev-
 [EMAIL PROTECTED]
  For additional commands, e-mail: harmony-dev-
  [EMAIL PROTECTED]
 
 
  LogManager.patch
 
  
-

  Terms of use : http://incubator.apache.org/harmony/mailing.html
  To unsubscribe, e-mail: harmony-dev-
 [EMAIL PROTECTED]
  For additional commands, e-mail: harmony-dev-
 [EMAIL PROTECTED]


  

Re: [drlvm] getting activeMQ to run

[Nikolay Kuznetsov]

Ok then, it was suse 9,  ia32.

On 9/23/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:

what platform?  I'm not seeing that...

On Sep 22, 2006, at 4:01 PM, Nikolay Kuznetsov wrote:

  core dumps in debug and prints something like this in release:
  WARN  DefaultJDBCAdapter - Could not create JDBC
 tables;
  they could already exist. Failure was: 

 That might be simply because you created the tables needed when you
 ran the first time?

 I don't know for sure, but J9 works fine w/o any warnings:

 INFO  JDBCPersistenceAdapter - Database driver recognized:
 [apache_derby_embedded_jdbc_driver]
 INFO  JournalPersistenceAdapter  - Journal Recovery Started from:
 Active Journal: using 5 x 20.0 Megs at:
 /nfs/pb/home/nakuznet/disk_j/workspace/harmony.orig/incubator-
 activemq-4.0.1/activemq-data/journal
 ...

 ... and the fact that debug version core dumps, also looks
 suspicious :)

 Nik.

  , but finally starts:
  INFO  BrokerService  - ActiveMQ JMS Message Broker
  (localhost, ID:pbtmrte007-57413-1158949586838-1:0) started
 
  Will continue investigate.

 So this look ok...

 My tests w/ the patch show it running, and I was able to run
 producer/
 consumer tests

 geir

 
  Nik.
 
  On 9/22/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:
  First, thanks so much for the fast response and good solution.
 
  I don't see any problem with this patch, but you're right - I
 don't
  understand why we have it, since Logger should set it's global
  field to getLogger(global) in the static initialization.
 
  I have the same problem with J9, so I don't think it's a VM
 problem.
 
  If no one complains, I'm going to test it, apply it, and add a
 JIRA
  to look at the fact that global isn't set...or tell me why it
  shouldn't be
 
  geir
 
 
  On Sep 22, 2006, at 1:51 PM, Nikolay Kuznetsov wrote:
 
   Hello,
  
   I was able to run ActiveQM on Linux with patch attached.
 Looks like
   something is broken in logger static initialization sequence.
  Though
   this patch helpps in running ActiveQM, I would treat this
 patch as
   workaround, this issue requires some more analysis and testing.
  
   Nik.
   On 9/22/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:
  
   On Sep 22, 2006, at 12:47 AM, Vladimir Gorr wrote:
  
On 9/22/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:
   
   
On Sep 22, 2006, at 12:37 AM, Vladimir Gorr wrote:
   
 On 9/22/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:

 Even though we have the jar issue fixed w/t he launcher-
  based
build,
 I still can't run ActiveMQ using release build on Ubuntu.

 Can anyone else report success?  Or a patch? :)


 I was succesfull on Windows. No success exist for Linux
  however.
   
What do you see on linux?
   
   
ACTIVEMQ_HOME: /nfs/ins/proj/drl/coreapi/vgorr/Tools/
 incubator-
activemq-4.0
Loading message broker from: xbean:activemq.xml
ERROR: java.lang.RuntimeException: Failed to execute start
 task.
Reason:
org.springframework.beans.factory.BeanCreationException:
 Error
creating bean
with name
  'org.apache.activemq.store.PersistenceAdapterFactoryBean'
defined
in class path resource [activemq.xml]: Instantiation of bean
   failed;
...
  
   Yah, that's what I get.  We really need to get this kind of
 thing
   worked out, and fast...
  
   geir
  
snipped
...
   
Steps I do are the following:
 1. unset JAVA_HOME
 2. set PATH=.../jre/bin;PATH
 3. cd .../activemq-3.2.3\bin; activemq

 Are these steps correct?
   
Close enough.  I set JAVA_HOME to the harmony jre directory
   (deploy/
jre), added bin to the path, and then
   
  sh bin/activemq
   
But I'm using activeMQ 4.0.something
   
   
   
Yes, it seems this version doesn't work correctly. At
 least on
   Linux.
I'll try this on Windows as well.
   
Thanks,
Vladimir.
   
   
   
 Thanks,
 Vladimir.


 geir



   
  
 
 -
 Terms of use : http://incubator.apache.org/harmony/
  mailing.html
 To unsubscribe, e-mail: harmony-dev-
[EMAIL PROTECTED]
 For additional commands, e-mail: harmony-dev-
 [EMAIL PROTECTED]


   
   
   
  
 
 -
Terms of use : http://incubator.apache.org/harmony/
 mailing.html
To unsubscribe, e-mail: harmony-dev-
   [EMAIL PROTECTED]
For additional commands, e-mail: harmony-dev-
[EMAIL PROTECTED]
   
   
  
  
  
 
 -
   Terms of use : http://incubator.apache.org/harmony/mailing.html
   To unsubscribe, e-mail: harmony-dev-
  [EMAIL PROTECTED]
   For additional commands, e-mail: harmony-dev-
   [EMAIL PROTECTED]
  
  
   LogManager.patch
  
 
 

Re: [drlvm] getting activeMQ to run

[Gregory Shimansky]

On Friday 22 September 2006 22:39 Geir Magnusson Jr. wrote:
 First, thanks so much for the fast response and good solution.

 I don't see any problem with this patch, but you're right - I don't
 understand why we have it, since Logger should set it's global
 field to getLogger(global) in the static initialization.

Static initialization doesn't guarantee that the field is initialized when you 
need it. I've seen it several times in classlib initialization. It happens 
because clinit method is called only once in the stack of the calling 
methods (or there could be infinite recursion). If clinit is somewhere up 
the stack it won't be called again. But if some field of the class which is 
executing clinit up the stack already is needed down the stack by some 
other called classes' methods (called from the up the stack clinit), it may 
be still uninitialized.

I could write a real java test to show that this is possible but this is too 
late at night and I can't think straight. Just trust my word :)

I think such conditions can happen not only on classlib initialization.

-- 
Gregory Shimansky, Intel Middleware Products Division

-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [drlvm] getting activeMQ to run

[Geir Magnusson Jr.]

On Sep 22, 2006, at 7:32 PM, Gregory Shimansky wrote:


On Friday 22 September 2006 22:39 Geir Magnusson Jr. wrote:

First, thanks so much for the fast response and good solution.

I don't see any problem with this patch, but you're right - I don't
understand why we have it, since Logger should set it's global
field to getLogger(global) in the static initialization.


Static initialization doesn't guarantee that the field is  
initialized when you

need it.
I've seen it several times in classlib initialization. It happens
because clinit method is called only once in the stack of the  
calling
methods (or there could be infinite recursion). If clinit is  
somewhere up
the stack it won't be called again. But if some field of the class  
which is
executing clinit up the stack already is needed down the stack by  
some
other called classes' methods (called from the up the stack  
clinit), it may

be still uninitialized.


Hm.

LogManger's initializer does

  Logger root = Logger.getLogger();

and Logger has

  public final static Logger global = Logger.getLogger(global);

which eventually executes

   LogManager man = LogManager.getLogManager();

and around we go.

So why don't we always run aground with this?  Why is this the first  
time we see this?




I could write a real java test to show that this is possible but  
this is too

late at night and I can't think straight. Just trust my word :)

I think such conditions can happen not only on classlib  
initialization.


--
Gregory Shimansky, Intel Middleware Products Division

-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [drlvm] getting activeMQ to run

[Gregory Shimansky]

On Saturday 23 September 2006 04:20 Geir Magnusson Jr. wrote:
 On Sep 22, 2006, at 7:32 PM, Gregory Shimansky wrote:
  On Friday 22 September 2006 22:39 Geir Magnusson Jr. wrote:
  First, thanks so much for the fast response and good solution.
 
  I don't see any problem with this patch, but you're right - I don't
  understand why we have it, since Logger should set it's global
  field to getLogger(global) in the static initialization.
 
  Static initialization doesn't guarantee that the field is
  initialized when you
  need it.
  I've seen it several times in classlib initialization. It happens
  because clinit method is called only once in the stack of the
  calling
  methods (or there could be infinite recursion). If clinit is
  somewhere up
  the stack it won't be called again. But if some field of the class
  which is
  executing clinit up the stack already is needed down the stack by
  some
  other called classes' methods (called from the up the stack
  clinit), it may
  be still uninitialized.

 Hm.

 LogManger's initializer does

Logger root = Logger.getLogger();

 and Logger has

public final static Logger global = Logger.getLogger(global);

 which eventually executes

 LogManager man = LogManager.getLogManager();

 and around we go.

 So why don't we always run aground with this?  Why is this the first
 time we see this?

I think that only stack trace of NPE can show the real reason of the 
problem... If it is NPE (uninitialized field has to be null), otherwise my 
guess could be wrong.

The workaround for such cases is simple, in methods like

void m () {
f.m2();
}

it is necessary to write

void m () {
if (f == null)
initf();

f.m2();
}

This, in case may cause infinite recursion because in case initialization of 
field f may still refer to method m in other classes, but it is easier to 
resolve.

-- 
Gregory Shimansky, Intel Middleware Products Division

-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [drlvm] getting activeMQ to run

[Nathan Beyer]

 -Original Message-
 From: Gregory Shimansky [mailto:[EMAIL PROTECTED]
 Sent: Friday, September 22, 2006 7:43 PM
 To: harmony-dev@incubator.apache.org
 Subject: Re: [drlvm] getting activeMQ to run
 
 On Saturday 23 September 2006 04:20 Geir Magnusson Jr. wrote:
  On Sep 22, 2006, at 7:32 PM, Gregory Shimansky wrote:
   On Friday 22 September 2006 22:39 Geir Magnusson Jr. wrote:
   First, thanks so much for the fast response and good solution.
  
   I don't see any problem with this patch, but you're right - I don't
   understand why we have it, since Logger should set it's global
   field to getLogger(global) in the static initialization.
  
   Static initialization doesn't guarantee that the field is
   initialized when you
   need it.
   I've seen it several times in classlib initialization. It happens
   because clinit method is called only once in the stack of the
   calling
   methods (or there could be infinite recursion). If clinit is
   somewhere up
   the stack it won't be called again. But if some field of the class
   which is
   executing clinit up the stack already is needed down the stack by
   some
   other called classes' methods (called from the up the stack
   clinit), it may
   be still uninitialized.
 
  Hm.
 
  LogManger's initializer does
 
 Logger root = Logger.getLogger();
 
  and Logger has
 
 public final static Logger global = Logger.getLogger(global);
 
  which eventually executes
 
  LogManager man = LogManager.getLogManager();
 
  and around we go.
 
  So why don't we always run aground with this?  Why is this the first
  time we see this?
 
 I think that only stack trace of NPE can show the real reason of the
 problem... If it is NPE (uninitialized field has to be null), otherwise my
 guess could be wrong.

Wouldn't a simple approach to fixing this be create the root logger with a
custom implementation of Logger instead of using Logger.getLogger() to
create it. Also, the same thing would be done for the global logger
initialization. This could be done with a package-private constructor just
for this special purpose. This way the initialization of LogManager can use
Logger, but the initialization of Logger doesn't use LogManager.

-Nathan

 
 The workaround for such cases is simple, in methods like
 
 void m () {
 f.m2();
 }
 
 it is necessary to write
 
 void m () {
 if (f == null)
 initf();
 
 f.m2();
 }
 
 This, in case may cause infinite recursion because in case initialization
 of
 field f may still refer to method m in other classes, but it is easier to
 resolve.
 
 --
 Gregory Shimansky, Intel Middleware Products Division
 
 -
 Terms of use : http://incubator.apache.org/harmony/mailing.html
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[drlvm] getting activeMQ to run

[Geir Magnusson Jr.]

Even though we have the jar issue fixed w/t he launcher-based build,  
I still can't run ActiveMQ using release build on Ubuntu.


Can anyone else report success?  Or a patch? :)

geir


-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [drlvm] getting activeMQ to run

[Vladimir Gorr]

On 9/22/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:


Even though we have the jar issue fixed w/t he launcher-based build,
I still can't run ActiveMQ using release build on Ubuntu.

Can anyone else report success?  Or a patch? :)



I was succesfull on Windows. No success exist for Linux however.
Steps I do are the following:
1. unset JAVA_HOME
2. set PATH=.../jre/bin;PATH
3. cd .../activemq-3.2.3\bin; activemq

Are these steps correct?

Thanks,
Vladimir.


geir



-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [drlvm] getting activeMQ to run

[Geir Magnusson Jr.]

On Sep 22, 2006, at 12:47 AM, Vladimir Gorr wrote:


On 9/22/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:



On Sep 22, 2006, at 12:37 AM, Vladimir Gorr wrote:

 On 9/22/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:

 Even though we have the jar issue fixed w/t he launcher-based  
build,

 I still can't run ActiveMQ using release build on Ubuntu.

 Can anyone else report success?  Or a patch? :)


 I was succesfull on Windows. No success exist for Linux however.

What do you see on linux?



ACTIVEMQ_HOME: /nfs/ins/proj/drl/coreapi/vgorr/Tools/incubator- 
activemq-4.0

Loading message broker from: xbean:activemq.xml
ERROR: java.lang.RuntimeException: Failed to execute start task.  
Reason:
org.springframework.beans.factory.BeanCreationException: Error  
creating bean
with name 'org.apache.activemq.store.PersistenceAdapterFactoryBean'  
defined

in class path resource [activemq.xml]: Instantiation of bean failed;
...


Yah, that's what I get.  We really need to get this kind of thing  
worked out, and fast...


geir


snipped
...


Steps I do are the following:
 1. unset JAVA_HOME
 2. set PATH=.../jre/bin;PATH
 3. cd .../activemq-3.2.3\bin; activemq

 Are these steps correct?

Close enough.  I set JAVA_HOME to the harmony jre directory (deploy/
jre), added bin to the path, and then

  sh bin/activemq

But I'm using activeMQ 4.0.something




Yes, it seems this version doesn't work correctly. At least on Linux.
I'll try this on Windows as well.

Thanks,
Vladimir.




 Thanks,
 Vladimir.


 geir


  
-

 Terms of use : http://incubator.apache.org/harmony/mailing.html
 To unsubscribe, e-mail: harmony-dev- 
[EMAIL PROTECTED]

 For additional commands, e-mail: harmony-dev-
 [EMAIL PROTECTED]




-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: harmony-dev- 
[EMAIL PROTECTED]






-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]