RE: [JBoss-user] jboss not starting with IBM jdk

2003-03-24 Thread Marko Strukelj 
Title: RE: [JBoss-user] jboss not starting with IBM jdk



Check 
this again:

http://sourceforge.net/tracker/index.php?func=detailaid=679705group_id=22866atid=376685


I 
posted the solution to the problem.



  -Original Message-From: Jordi Valldaura i Riqué 
  [mailto:[EMAIL PROTECTED]Sent: Friday, March 21, 2003 11:52 
  AMTo: [EMAIL PROTECTED]Subject: Re: 
  [JBoss-user] jboss not starting with IBM jdk
  Ok, I have libc-2.3.1 I will install libc 
  2.3.2.
  
  Thank you very much
  
- Original Message - 
From: 
Marko 
Strukelj 
To: '[EMAIL PROTECTED]' 

Sent: Friday, March 21, 2003 10:52 
AM
Subject: RE: [JBoss-user] jboss not 
starting with IBM jdk

libc is the real problem. Maybe I wasn't specific enough about 
that. You should install libc 2.3.2. That should solve the 11 thing. 


I 
advised you thegcc upgrade because if we do have the same Debian 
distribution it will help a lot to make your system stable. It did for mine 
- namely the existing gcc had all the symbols screwed up in the shared 
libgcc_s.so.1.


  -Original Message-From: Jordi Valldaura i Riqué 
  [mailto:[EMAIL PROTECTED]Sent: Thursday, March 20, 2003 
  6:17 PMTo: [EMAIL PROTECTED]Subject: 
  Re: [JBoss-user] jboss not starting with IBM jdk
  I've installet gcc 3.2.2 and removed 
  liggcc_s.so.1 but the problem still persists. I've submited a bug report 
  to Sun. Do you know any hint, it's my linux configuration fault in 
  
  windows everything works fine 
  
  
  Thanks in advance
  
- Original Message - 
From: 
Marko 
Strukelj 
To: '[EMAIL PROTECTED]' 

Sent: Thursday, March 20, 2003 1:00 
PM
Subject: RE: [JBoss-user] jboss not 
starting with IBM jdk

You should recompile the gcc (3.2.2) and remove the libgcc_s.so.1 
in /lib (of course after the recompilation of the 
gcc).

And here is why IBM doesn't work: http://sourceforge.net/tracker/index.php?func=detailaid=679705group_id=22866atid=376685(thanks 
to Rasputin)


  -Original Message-From: Jordi Valldaura i 
  Riqué [mailto:[EMAIL PROTECTED]Sent: Thursday, March 
  20, 2003 12:43 PMTo: 
  [EMAIL PROTECTED]Subject: Re: [JBoss-user] 
  jboss not starting with IBM jdk
  Hi Marko
  
  So if I want to use Blackdown or Sun I 
  must us libc 2.3.1 without getting Error:11 sometimes, isn't it? I'm 
  running a debian too, and my libc is 2.2.5.
  
  Thanks in Advance
  
  
- Original Message - 
From: 
Marko 
Strukelj 
To: '[EMAIL PROTECTED]' 

Sent: Thursday, March 20, 2003 
12:14 PM
Subject: RE: [JBoss-user] jboss 
not starting with IBM jdk

The same thing happens to me with IBM jdk 1.4.0. 
Didn't investigate yet. 
Regarding Sun and Blackdown I have experienced the 
very same thing. Turned out my experimental Debian system was using 
libc 2.5.5 and either the jvm or Oracle OCI driver that I was using 
was looking for libc 2.3. I recompiled libc and error 11 was gone. 
Then the system started getting unstable due to incredible memory 
consumption by the jvm, although that's another story. Looks like 
Blackdown at least never frees the memory claimed from the system. 
If total memory consumption as reported by JVM raises to 70 Mb for 
example this translate to 400Mb of system memory (physical + caches) 
on the linux system. The thing is even if jvm reports that the total 
memory consumption has dropped the jvm will still consume 400Mb of 
system memory.
 -Original Message-  From: Jordi Valldaura i Riqué [mailto:[EMAIL PROTECTED]] 
 Sent: Thursday, March 20, 2003 9:24 AM 
 To: [EMAIL PROTECTED] 
 Subject: [JBoss-user] jboss not starting with 
IBM jdk   
 After getting frustrated because of an 
error 11 getting  thrown using Sun 
and  Blackdown JDK's I decided to try 
IBM's jdk. But when I try to  start 
jboss I  get the following Error: 
  09:24:32,034 
ERROR [MainDeployer] could not start deployment:  file:/mnt/sda1/ecampus-jboss/jboss-3.0.6/server/default/conf/j 
 boss-service.x  
ml  
java.lang.AbstractMethodError:  
org/jboss/deployment/scanner/AbstractDeploymentScanner.scan

RE: [JBoss-user] jboss not starting with IBM jdk

2003-03-21 Thread Marko Strukelj 
Title: RE: [JBoss-user] jboss not starting with IBM jdk



libc 
is the real problem. Maybe I wasn't specific enough about that. You should 
install libc 2.3.2. That should solve the 11 thing. 

I 
advised you thegcc upgrade because if we do have the same Debian 
distribution it will help a lot to make your system stable. It did for mine - 
namely the existing gcc had all the symbols screwed up in the shared 
libgcc_s.so.1.


  -Original Message-From: Jordi Valldaura i Riqué 
  [mailto:[EMAIL PROTECTED]Sent: Thursday, March 20, 2003 6:17 
  PMTo: [EMAIL PROTECTED]Subject: Re: 
  [JBoss-user] jboss not starting with IBM jdk
  I've installet gcc 3.2.2 and removed 
  liggcc_s.so.1 but the problem still persists. I've submited a bug report to 
  Sun. Do you know any hint, it's my linux configuration fault in 
  windows everything works fine 
  
  Thanks in advance
  
- Original Message - 
From: 
Marko 
Strukelj 
To: '[EMAIL PROTECTED]' 

Sent: Thursday, March 20, 2003 1:00 
PM
Subject: RE: [JBoss-user] jboss not 
starting with IBM jdk

You should recompile the gcc (3.2.2) and remove the libgcc_s.so.1 in 
/lib (of course after the recompilation of the gcc).

And here is why IBM doesn't work: http://sourceforge.net/tracker/index.php?func=detailaid=679705group_id=22866atid=376685(thanks 
to Rasputin)


  -Original Message-From: Jordi Valldaura i Riqué 
  [mailto:[EMAIL PROTECTED]Sent: Thursday, March 20, 2003 
  12:43 PMTo: [EMAIL PROTECTED]Subject: 
  Re: [JBoss-user] jboss not starting with IBM jdk
  Hi Marko
  
  So if I want to use Blackdown or Sun I must 
  us libc 2.3.1 without getting Error:11 sometimes, isn't it? I'm running a 
  debian too, and my libc is 2.2.5.
  
  Thanks in Advance
  
  
- Original Message - 
From: 
Marko 
Strukelj 
To: '[EMAIL PROTECTED]' 

Sent: Thursday, March 20, 2003 
12:14 PM
Subject: RE: [JBoss-user] jboss not 
starting with IBM jdk

The same thing happens to me with IBM jdk 1.4.0. Didn't 
investigate yet. 
Regarding Sun and Blackdown I have experienced the very 
same thing. Turned out my experimental Debian system was using libc 
2.5.5 and either the jvm or Oracle OCI driver that I was using was 
looking for libc 2.3. I recompiled libc and error 11 was gone. Then the 
system started getting unstable due to incredible memory consumption by 
the jvm, although that's another story. Looks like Blackdown at least 
never frees the memory claimed from the system. If total memory 
consumption as reported by JVM raises to 70 Mb for example this 
translate to 400Mb of system memory (physical + caches) on the linux 
system. The thing is even if jvm reports that the total memory 
consumption has dropped the jvm will still consume 400Mb of system 
memory.
 -Original Message-  From: Jordi Valldaura i Riqué [mailto:[EMAIL PROTECTED]] 
 Sent: Thursday, March 20, 2003 9:24 AM 
 To: [EMAIL PROTECTED] 
 Subject: [JBoss-user] jboss not starting with IBM 
jdk   
 After getting frustrated because of an 
error 11 getting  thrown using Sun 
and  Blackdown JDK's I decided to try IBM's 
jdk. But when I try to  start jboss I 
 get the following Error:   09:24:32,034 ERROR 
[MainDeployer] could not start deployment:  
file:/mnt/sda1/ecampus-jboss/jboss-3.0.6/server/default/conf/j 
 boss-service.x  
ml  java.lang.AbstractMethodError: 
 
org/jboss/deployment/scanner/AbstractDeploymentScanner.scan 
 
at  
org.jboss.deployment.scanner.AbstractDeploymentScanner.startSe 
 rvice(Abstract  
DeploymentScanner.java:261)  at 
 
org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport 
 .java:165)  at 
sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) 
 
at  
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth 
 odAccessorImpl  
.java:40)  at 
java.lang.reflect.Method.invoke(Method.java:335)  at 
 
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(Reflec 
 tedMBeanDispat  
cher.java:284)  at 
 
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517) 
 
at  
org.jboss.system.ServiceController$ServiceProxy.invoke(Service 
 Controller.jav  
a:1003)  at 
$Proxy0.start(Unknown Source)  at 
 
org.jboss.system.ServiceController.start(ServiceController.java:413) 
 at 
sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source

Re: [JBoss-user] jboss not starting with IBM jdk

2003-03-21 Thread Jordi Valldaura i Riqué 
Title: RE: [JBoss-user] jboss not starting with IBM jdk



Ok, I have libc-2.3.1 I will install libc 
2.3.2.

Thank you very much

  - Original Message - 
  From: 
  Marko 
  Strukelj 
  To: '[EMAIL PROTECTED]' 
  
  Sent: Friday, March 21, 2003 10:52 
  AM
  Subject: RE: [JBoss-user] jboss not 
  starting with IBM jdk
  
  libc 
  is the real problem. Maybe I wasn't specific enough about that. You 
  should install libc 2.3.2. That should solve the 11 thing. 

  
  I 
  advised you thegcc upgrade because if we do have the same Debian 
  distribution it will help a lot to make your system stable. It did for mine - 
  namely the existing gcc had all the symbols screwed up in the shared 
  libgcc_s.so.1.
  
  
-Original Message-From: Jordi Valldaura i Riqué 
[mailto:[EMAIL PROTECTED]Sent: Thursday, March 20, 2003 6:17 
PMTo: [EMAIL PROTECTED]Subject: Re: 
[JBoss-user] jboss not starting with IBM jdk
I've installet gcc 3.2.2 and removed 
liggcc_s.so.1 but the problem still persists. I've submited a bug report to 
Sun. Do you know any hint, it's my linux configuration fault in 

windows everything works fine 

Thanks in advance

  - Original Message - 
  From: 
  Marko 
  Strukelj 
  To: '[EMAIL PROTECTED]' 
  
  Sent: Thursday, March 20, 2003 1:00 
  PM
  Subject: RE: [JBoss-user] jboss not 
  starting with IBM jdk
  
  You should recompile the gcc (3.2.2) and remove the libgcc_s.so.1 
  in /lib (of course after the recompilation of the 
gcc).
  
  And here is why IBM doesn't work: http://sourceforge.net/tracker/index.php?func=detailaid=679705group_id=22866atid=376685(thanks 
  to Rasputin)
  
  
-Original Message-From: Jordi Valldaura i 
Riqué [mailto:[EMAIL PROTECTED]Sent: Thursday, March 20, 
2003 12:43 PMTo: 
[EMAIL PROTECTED]Subject: Re: [JBoss-user] 
jboss not starting with IBM jdk
Hi Marko

So if I want to use Blackdown or Sun I must 
us libc 2.3.1 without getting Error:11 sometimes, isn't it? I'm running 
a debian too, and my libc is 2.2.5.

Thanks in Advance


  - Original Message - 
  From: 
  Marko 
  Strukelj 
  To: '[EMAIL PROTECTED]' 
  
  Sent: Thursday, March 20, 2003 
  12:14 PM
  Subject: RE: [JBoss-user] jboss 
  not starting with IBM jdk
  
  The same thing happens to me with IBM jdk 1.4.0. 
  Didn't investigate yet. 
  Regarding Sun and Blackdown I have experienced the 
  very same thing. Turned out my experimental Debian system was using 
  libc 2.5.5 and either the jvm or Oracle OCI driver that I was using 
  was looking for libc 2.3. I recompiled libc and error 11 was gone. 
  Then the system started getting unstable due to incredible memory 
  consumption by the jvm, although that's another story. Looks like 
  Blackdown at least never frees the memory claimed from the system. If 
  total memory consumption as reported by JVM raises to 70 Mb for 
  example this translate to 400Mb of system memory (physical + caches) 
  on the linux system. The thing is even if jvm reports that the total 
  memory consumption has dropped the jvm will still consume 400Mb of 
  system memory.
   -Original Message-  From: Jordi Valldaura i Riqué [mailto:[EMAIL PROTECTED]] 
   Sent: Thursday, March 20, 2003 9:24 AM 
   To: [EMAIL PROTECTED] 
   Subject: [JBoss-user] jboss not starting with 
  IBM jdk   
   After getting frustrated because of an 
  error 11 getting  thrown using Sun 
  and  Blackdown JDK's I decided to try 
  IBM's jdk. But when I try to  start jboss 
  I  get the following Error: 
09:24:32,034 ERROR 
  [MainDeployer] could not start deployment:  file:/mnt/sda1/ecampus-jboss/jboss-3.0.6/server/default/conf/j 
   boss-service.x  
  ml  java.lang.AbstractMethodError: 
   
  org/jboss/deployment/scanner/AbstractDeploymentScanner.scan 
   
  at  
  org.jboss.deployment.scanner.AbstractDeploymentScanner.startSe 
   rvice(Abstract  
  DeploymentScanner.java:261)  at 
   
  org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport 
   .java:165)  at 
  sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) 
   
  at  
  sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth 
   odAccessorImpl  
  .java:40)  at 
  java.lang.reflect.Method.invoke(Method.java:335)  at 
   
  org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(Reflec

Re: [JBoss-user] jboss not starting with IBM jdk

2003-03-21 Thread Jordi Valldaura i Riqué 
Title: RE: [JBoss-user] jboss not starting with IBM jdk



Ok, I have libc-2.3.1 I will install libc 
2.3.2.

Thank you very much

  - Original Message - 
  From: 
  Marko 
  Strukelj 
  To: '[EMAIL PROTECTED]' 
  
  Sent: Friday, March 21, 2003 10:52 
  AM
  Subject: RE: [JBoss-user] jboss not 
  starting with IBM jdk
  
  libc 
  is the real problem. Maybe I wasn't specific enough about that. You 
  should install libc 2.3.2. That should solve the 11 thing. 

  
  I 
  advised you thegcc upgrade because if we do have the same Debian 
  distribution it will help a lot to make your system stable. It did for mine - 
  namely the existing gcc had all the symbols screwed up in the shared 
  libgcc_s.so.1.
  
  
-Original Message-From: Jordi Valldaura i Riqué 
[mailto:[EMAIL PROTECTED]Sent: Thursday, March 20, 2003 6:17 
PMTo: [EMAIL PROTECTED]Subject: Re: 
[JBoss-user] jboss not starting with IBM jdk
I've installet gcc 3.2.2 and removed 
liggcc_s.so.1 but the problem still persists. I've submited a bug report to 
Sun. Do you know any hint, it's my linux configuration fault in 

windows everything works fine 

Thanks in advance

  - Original Message - 
  From: 
  Marko 
  Strukelj 
  To: '[EMAIL PROTECTED]' 
  
  Sent: Thursday, March 20, 2003 1:00 
  PM
  Subject: RE: [JBoss-user] jboss not 
  starting with IBM jdk
  
  You should recompile the gcc (3.2.2) and remove the libgcc_s.so.1 
  in /lib (of course after the recompilation of the 
gcc).
  
  And here is why IBM doesn't work: http://sourceforge.net/tracker/index.php?func=detailaid=679705group_id=22866atid=376685(thanks 
  to Rasputin)
  
  
-Original Message-From: Jordi Valldaura i 
Riqué [mailto:[EMAIL PROTECTED]Sent: Thursday, March 20, 
2003 12:43 PMTo: 
[EMAIL PROTECTED]Subject: Re: [JBoss-user] 
jboss not starting with IBM jdk
Hi Marko

So if I want to use Blackdown or Sun I must 
us libc 2.3.1 without getting Error:11 sometimes, isn't it? I'm running 
a debian too, and my libc is 2.2.5.

Thanks in Advance


  - Original Message - 
  From: 
  Marko 
  Strukelj 
  To: '[EMAIL PROTECTED]' 
  
  Sent: Thursday, March 20, 2003 
  12:14 PM
  Subject: RE: [JBoss-user] jboss 
  not starting with IBM jdk
  
  The same thing happens to me with IBM jdk 1.4.0. 
  Didn't investigate yet. 
  Regarding Sun and Blackdown I have experienced the 
  very same thing. Turned out my experimental Debian system was using 
  libc 2.5.5 and either the jvm or Oracle OCI driver that I was using 
  was looking for libc 2.3. I recompiled libc and error 11 was gone. 
  Then the system started getting unstable due to incredible memory 
  consumption by the jvm, although that's another story. Looks like 
  Blackdown at least never frees the memory claimed from the system. If 
  total memory consumption as reported by JVM raises to 70 Mb for 
  example this translate to 400Mb of system memory (physical + caches) 
  on the linux system. The thing is even if jvm reports that the total 
  memory consumption has dropped the jvm will still consume 400Mb of 
  system memory.
   -Original Message-  From: Jordi Valldaura i Riqué [mailto:[EMAIL PROTECTED]] 
   Sent: Thursday, March 20, 2003 9:24 AM 
   To: [EMAIL PROTECTED] 
   Subject: [JBoss-user] jboss not starting with 
  IBM jdk   
   After getting frustrated because of an 
  error 11 getting  thrown using Sun 
  and  Blackdown JDK's I decided to try 
  IBM's jdk. But when I try to  start jboss 
  I  get the following Error: 
09:24:32,034 ERROR 
  [MainDeployer] could not start deployment:  file:/mnt/sda1/ecampus-jboss/jboss-3.0.6/server/default/conf/j 
   boss-service.x  
  ml  java.lang.AbstractMethodError: 
   
  org/jboss/deployment/scanner/AbstractDeploymentScanner.scan 
   
  at  
  org.jboss.deployment.scanner.AbstractDeploymentScanner.startSe 
   rvice(Abstract  
  DeploymentScanner.java:261)  at 
   
  org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport 
   .java:165)  at 
  sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) 
   
  at  
  sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth 
   odAccessorImpl  
  .java:40)  at 
  java.lang.reflect.Method.invoke(Method.java:335)  at 
   
  org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(Reflec

RE: [JBoss-user] jboss not starting with IBM jdk

2003-03-20 Thread Marko Strukelj 
Title: RE: [JBoss-user] jboss not starting with IBM jdk






The same thing happens to me with IBM jdk 1.4.0. Didn't investigate yet. 



Regarding Sun and Blackdown I have experienced the very same thing. Turned out my experimental Debian system was using libc 2.5.5 and either the jvm or Oracle OCI driver that I was using was looking for libc 2.3. I recompiled libc and error 11 was gone. Then the system started getting unstable due to incredible memory consumption by the jvm, although that's another story. Looks like Blackdown at least never frees the memory claimed from the system. If total memory consumption as reported by JVM raises to 70 Mb for example this translate to 400Mb of system memory (physical + caches) on the linux system. The thing is even if jvm reports that the total memory consumption has dropped the jvm will still consume 400Mb of system memory.





 -Original Message-
 From: Jordi Valldaura i Riqué [mailto:[EMAIL PROTECTED]]
 Sent: Thursday, March 20, 2003 9:24 AM
 To: [EMAIL PROTECTED]
 Subject: [JBoss-user] jboss not starting with IBM jdk
 
 
 After getting frustrated because of an error 11 getting 
 thrown using Sun and
 Blackdown JDK's I decided to try IBM's jdk. But when I try to 
 start jboss I
 get the following Error:
 
 09:24:32,034 ERROR [MainDeployer] could not start deployment:
 file:/mnt/sda1/ecampus-jboss/jboss-3.0.6/server/default/conf/j
 boss-service.x
 ml
 java.lang.AbstractMethodError:
 org/jboss/deployment/scanner/AbstractDeploymentScanner.scan
 at
 org.jboss.deployment.scanner.AbstractDeploymentScanner.startSe
 rvice(Abstract
 DeploymentScanner.java:261)
 at
 org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport
 .java:165)
 at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth
 odAccessorImpl
 .java:40)
 at java.lang.reflect.Method.invoke(Method.java:335)
 at
 org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(Reflec
 tedMBeanDispat
 cher.java:284)
 at
 org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
 at
 org.jboss.system.ServiceController$ServiceProxy.invoke(Service
 Controller.jav
 a:1003)
 at $Proxy0.start(Unknown Source)
 at
 org.jboss.system.ServiceController.start(ServiceController.java:413)
 at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth
 odAccessorImpl
 .java:40)
 at java.lang.reflect.Method.invoke(Method.java:335)
 at
 org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(Reflec
 tedMBeanDispat
 cher.java:284)
 at
 org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
 at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
 at $Proxy2.start(Unknown Source)
 at 
 org.jboss.deployment.SARDeployer.start(SARDeployer.java:230)
 at 
 org.jboss.deployment.MainDeployer.start(MainDeployer.java:814)
 at 
 org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:627)
 at 
 org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:591)
 at 
 org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:575)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess
 orImpl.java:61
 )
 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth
 odAccessorImpl
 .java:40)
 at java.lang.reflect.Method.invoke(Method.java:335)
 at
 org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(Reflec
 tedMBeanDispat
 cher.java:284)
 at
 org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
 at 
 org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:325)
 at 
 org.jboss.system.server.ServerImpl.start(ServerImpl.java:222)
 at org.jboss.Main.boot(Main.java:148)
 at org.jboss.Main$1.run(Main.java:381)
 at java.lang.Thread.run(Thread.java:566)
 09:24:32,081 ERROR [Server] start failed
 org.jboss.deployment.DeploymentException: Could not create deployment:
 file:/mnt/sda1/ecampus-jboss/jboss-3.0.6/server/default/conf/j
 boss-service.x
 ml; - nested throwable: (java.lang.AbstractMethodError:
 org/jboss/deployment/scanner/AbstractDeploymentScanner.scan)
 at 
 org.jboss.deployment.MainDeployer.start(MainDeployer.java:835)
 at 
 org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:627)
 at 
 org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:591)
 at 
 org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:575)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess
 orImpl.java:61
 )
 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth
 odAccessorImpl
 .java:40)
 at java.lang.reflect.Method.invoke(Method.java:335)
 at
 org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(Reflec
 tedMBeanDispat
 cher.java:284)
 at
 org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
 at 
 org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:325

Re: [JBoss-user] jboss not starting with IBM jdk

2003-03-20 Thread Jordi Valldaura i Riqué 
Title: RE: [JBoss-user] jboss not starting with IBM jdk



Hi Marko

So if I want to use Blackdown or Sun I must us libc 
2.3.1 without getting Error:11 sometimes, isn't it? I'm running a debian too, 
and my libc is 2.2.5.

Thanks in Advance


  - Original Message - 
  From: 
  Marko 
  Strukelj 
  To: '[EMAIL PROTECTED]' 
  
  Sent: Thursday, March 20, 2003 12:14 
  PM
  Subject: RE: [JBoss-user] jboss not 
  starting with IBM jdk
  
  The same thing happens to me with IBM jdk 1.4.0. Didn't 
  investigate yet. 
  Regarding Sun and Blackdown I have experienced the very same 
  thing. Turned out my experimental Debian system was using libc 2.5.5 and 
  either the jvm or Oracle OCI driver that I was using was looking for libc 2.3. 
  I recompiled libc and error 11 was gone. Then the system started getting 
  unstable due to incredible memory consumption by the jvm, although that's 
  another story. Looks like Blackdown at least never frees the memory claimed 
  from the system. If total memory consumption as reported by JVM raises to 70 
  Mb for example this translate to 400Mb of system memory (physical + caches) on 
  the linux system. The thing is even if jvm reports that the total memory 
  consumption has dropped the jvm will still consume 400Mb of system 
  memory.
   -Original Message-  
  From: Jordi Valldaura i Riqué [mailto:[EMAIL PROTECTED]] 
   Sent: Thursday, March 20, 2003 9:24 AM  To: [EMAIL PROTECTED]  
  Subject: [JBoss-user] jboss not starting with IBM jdkAfter 
  getting frustrated because of an error 11 getting  
  thrown using Sun and  Blackdown JDK's I decided to 
  try IBM's jdk. But when I try to  start jboss 
  I  get the following Error:   09:24:32,034 ERROR [MainDeployer] 
  could not start deployment:  file:/mnt/sda1/ecampus-jboss/jboss-3.0.6/server/default/conf/j 
   boss-service.x  ml 
   java.lang.AbstractMethodError:  org/jboss/deployment/scanner/AbstractDeploymentScanner.scan 
   
  at  
  org.jboss.deployment.scanner.AbstractDeploymentScanner.startSe 
   rvice(Abstract  
  DeploymentScanner.java:261)  at 
   
  org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport 
   .java:165)  at 
  sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)  at 
   
  sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth 
   odAccessorImpl  
  .java:40)  at 
  java.lang.reflect.Method.invoke(Method.java:335)  at 
   
  org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(Reflec 
   tedMBeanDispat  
  cher.java:284)  at 
   
  org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517) 
   
  at  
  org.jboss.system.ServiceController$ServiceProxy.invoke(Service 
   Controller.jav  
  a:1003)  at 
  $Proxy0.start(Unknown Source)  at 
   
  org.jboss.system.ServiceController.start(ServiceController.java:413) 
   at 
  sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)  at 
   
  sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth 
   odAccessorImpl  
  .java:40)  at 
  java.lang.reflect.Method.invoke(Method.java:335)  at 
   
  org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(Reflec 
   tedMBeanDispat  
  cher.java:284)  at 
   
  org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517) 
   at 
  org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)  at 
  $Proxy2.start(Unknown Source)  at 
   
  org.jboss.deployment.SARDeployer.start(SARDeployer.java:230)  at 
   
  org.jboss.deployment.MainDeployer.start(MainDeployer.java:814) 
   at 
   
  org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:627) 
   at 
   
  org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:591) 
   at 
   
  org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:575) 
   at 
  sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)  at 
   
  sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess 
   orImpl.java:61  ) 
   
  at  
  sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth 
   odAccessorImpl  
  .java:40)  at 
  java.lang.reflect.Method.invoke(Method.java:335)  at 
   
  org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(Reflec 
   tedMBeanDispat  
  cher.java:284)  at 
   
  org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517) 
   at 
   
  org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:325) 
   at 
   
  org.jboss.system.server.ServerImpl.start(ServerImpl.java:222)  at 
  org.jboss.Main.boot(Main.java:148)  at 
  org.jboss.Main$1.run(Main.java:381)  at 
  java.lang.Thread.run(Thread.java:566)  
  09:24:32,081 ERROR [Server] start failed  
  org.jboss.deployment.DeploymentException: Could not create deployment: 
   file:/mnt/sda1/ecampus-jboss/jboss-3.0.6/server/default/conf/j 
   boss-service.x  ml; - nested 
  throwable: (java.lang.AbstractMethodError:  
  org/jboss/deployment/scanner/AbstractDeploymentScanner.scan)  at 
   
  org.jboss.deployment.MainDeployer.start(MainDeployer.java:835

Re: [JBoss-user] jboss not starting with IBM jdk

2003-03-20 Thread Rasputin 
* Jordi Valldaura i Riqu? [EMAIL PROTECTED] [0306 09:06]:
 After getting frustrated because of an error 11 getting thrown using Sun and
 Blackdown JDK's I decided to try IBM's jdk. But when I try to start jboss I
 get the following Error:

Try building source on that JDK and seeing if it can run it then - I have the same 
problem
if I build under 1.4 and try to run on 1.3.

Unfortunately, if I try running on 1.4 it hangs, and building 1.3 gives sig11s when
xdoclet kicks in
  
 09:24:32,034 ERROR [MainDeployer] could not start deployment:
 file:/mnt/sda1/ecampus-jboss/jboss-3.0.6/server/default/conf/jboss-service.x
 ml
 java.lang.AbstractMethodError:
 org/jboss/deployment/scanner/AbstractDeploymentScanner.scan
 at
 org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(Abstract
 DeploymentScanner.java:261)
 at
 org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:165)
 at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
 .java:40)
 at java.lang.reflect.Method.invoke(Method.java:335)
 at
 org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat
 cher.java:284)
 at
 org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
 at
 org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.jav
 a:1003)
 at $Proxy0.start(Unknown Source)
 at
 org.jboss.system.ServiceController.start(ServiceController.java:413)
 at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
 .java:40)
 at java.lang.reflect.Method.invoke(Method.java:335)
 at
 org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat
 cher.java:284)
 at
 org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
 at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
 at $Proxy2.start(Unknown Source)
 at org.jboss.deployment.SARDeployer.start(SARDeployer.java:230)
 at org.jboss.deployment.MainDeployer.start(MainDeployer.java:814)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:627)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:591)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:575)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61
 )
 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
 .java:40)
 at java.lang.reflect.Method.invoke(Method.java:335)
 at
 org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat
 cher.java:284)
 at
 org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
 at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:325)
 at org.jboss.system.server.ServerImpl.start(ServerImpl.java:222)
 at org.jboss.Main.boot(Main.java:148)
 at org.jboss.Main$1.run(Main.java:381)
 at java.lang.Thread.run(Thread.java:566)
 09:24:32,081 ERROR [Server] start failed
 org.jboss.deployment.DeploymentException: Could not create deployment:
 file:/mnt/sda1/ecampus-jboss/jboss-3.0.6/server/default/conf/jboss-service.x
 ml; - nested throwable: (java.lang.AbstractMethodError:
 org/jboss/deployment/scanner/AbstractDeploymentScanner.scan)
 at org.jboss.deployment.MainDeployer.start(MainDeployer.java:835)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:627)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:591)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:575)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61
 )
 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
 .java:40)
 at java.lang.reflect.Method.invoke(Method.java:335)
 at
 org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat
 cher.java:284)
 at
 org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
 at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:325)
 at org.jboss.system.server.ServerImpl.start(ServerImpl.java:222)
 at org.jboss.Main.boot(Main.java:148)
 at org.jboss.Main$1.run(Main.java:381)
 at java.lang.Thread.run(Thread.java:566)
 Caused by: java.lang.AbstractMethodError:
 org/jboss/deployment/scanner/AbstractDeploymentScanner.scan
 at
 org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(Abstract
 DeploymentScanner.java:261)
 at

Re: [JBoss-user] jboss not starting with IBM jdk

2003-03-20 Thread Jordi Valldaura i Riqué 
Title: RE: [JBoss-user] jboss not starting with IBM jdk



I've installet gcc 3.2.2 and removed liggcc_s.so.1 
but the problem still persists. I've submited a bug report to Sun. Do you know 
any hint, it's my linux configuration fault in 
windows everything works fine 

Thanks in advance

  - Original Message - 
  From: 
  Marko 
  Strukelj 
  To: '[EMAIL PROTECTED]' 
  
  Sent: Thursday, March 20, 2003 1:00 
  PM
  Subject: RE: [JBoss-user] jboss not 
  starting with IBM jdk
  
  You 
  should recompile the gcc (3.2.2) and remove the libgcc_s.so.1 in /lib (of 
  course after the recompilation of the gcc).
  
  And 
  here is why IBM doesn't work: http://sourceforge.net/tracker/index.php?func=detailaid=679705group_id=22866atid=376685(thanks 
  to Rasputin)
  
  
-Original Message-From: Jordi Valldaura i Riqué 
[mailto:[EMAIL PROTECTED]Sent: Thursday, March 20, 2003 12:43 
PMTo: [EMAIL PROTECTED]Subject: Re: 
[JBoss-user] jboss not starting with IBM jdk
Hi Marko

So if I want to use Blackdown or Sun I must us 
libc 2.3.1 without getting Error:11 sometimes, isn't it? I'm running a 
debian too, and my libc is 2.2.5.

Thanks in Advance


  - Original Message - 
  From: 
  Marko 
  Strukelj 
  To: '[EMAIL PROTECTED]' 
  
  Sent: Thursday, March 20, 2003 12:14 
  PM
  Subject: RE: [JBoss-user] jboss not 
  starting with IBM jdk
  
  The same thing happens to me with IBM jdk 1.4.0. Didn't 
  investigate yet. 
  Regarding Sun and Blackdown I have experienced the very 
  same thing. Turned out my experimental Debian system was using libc 2.5.5 
  and either the jvm or Oracle OCI driver that I was using was looking for 
  libc 2.3. I recompiled libc and error 11 was gone. Then the system started 
  getting unstable due to incredible memory consumption by the jvm, although 
  that's another story. Looks like Blackdown at least never frees the memory 
  claimed from the system. If total memory consumption as reported by JVM 
  raises to 70 Mb for example this translate to 400Mb of system memory 
  (physical + caches) on the linux system. The thing is even if jvm reports 
  that the total memory consumption has dropped the jvm will still consume 
  400Mb of system memory.
   -Original Message-  From: Jordi Valldaura i Riqué [mailto:[EMAIL PROTECTED]] 
   Sent: Thursday, March 20, 2003 9:24 AM 
   To: [EMAIL PROTECTED] 
   Subject: [JBoss-user] jboss not starting with IBM 
  jdk   
   After getting frustrated because of an error 
  11 getting  thrown using Sun and 
   Blackdown JDK's I decided to try IBM's jdk. But when 
  I try to  start jboss I  get the following Error:  
   09:24:32,034 ERROR [MainDeployer] could not 
  start deployment:  file:/mnt/sda1/ecampus-jboss/jboss-3.0.6/server/default/conf/j 
   boss-service.x  
  ml  java.lang.AbstractMethodError: 
   
  org/jboss/deployment/scanner/AbstractDeploymentScanner.scan 
   
  at  
  org.jboss.deployment.scanner.AbstractDeploymentScanner.startSe 
   rvice(Abstract  
  DeploymentScanner.java:261)  at 
   
  org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport 
   .java:165)  at 
  sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) 
   
  at  
  sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth 
   odAccessorImpl  
  .java:40)  at 
  java.lang.reflect.Method.invoke(Method.java:335)  at 
   
  org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(Reflec 
   tedMBeanDispat  
  cher.java:284)  at 
   
  org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517) 
   
  at  
  org.jboss.system.ServiceController$ServiceProxy.invoke(Service 
   Controller.jav  
  a:1003)  at 
  $Proxy0.start(Unknown Source)  at 
   
  org.jboss.system.ServiceController.start(ServiceController.java:413) 
   at 
  sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) 
   
  at  
  sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth 
   odAccessorImpl  
  .java:40)  at 
  java.lang.reflect.Method.invoke(Method.java:335)  at 
   
  org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(Reflec 
   tedMBeanDispat  
  cher.java:284)  at 
   
  org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517) 
   at 
  org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)  at 
  $Proxy2.start(Unknown Source)  at 
   
  org.jboss.deployment.SARDeployer.start(SARDeployer.java:230) 
   at 
   
  org.jboss.deployment.MainDeployer.start(MainDeployer.java:814) 
   at 
   
  org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:627