RE: [JBoss-user] deployment problem
Title: RE: [JBoss-user] deployment problem Make sure you have META-INF directory (all caps) and not meta-inf. Marko. -Original Message- From: David Li [mailto:[EMAIL PROTECTED]] Sent: Friday, May 04, 2001 2:16 AM To: [EMAIL PROTECTED] Subject: [JBoss-user] deployment problem Hi, veteran. Can someone explain to me why I got this problem? I used Jar tool to generate a EAR file that contains one jar file and one war file, and meta-inf/applicatoin.xml deployment descriptor. But, everytime when I put the EAR file to deploy folder of JBoss+Tomcat ver 2.2 and always got the following error: ... [Auto deploy] org.jboss.deployment.J2eeDeploymentException: no deployment descriptor found but file that could be ment as: meta-inf/application.xml - META-INF/application.xml [Auto deploy] ar org.jboss.deployment.Installer.determineType(Installer.java:397) ... But, if I used J2EE's GUI-based deploytool to generate the EAR file containing the same components, the jBoss deployed it just fine. Thanks for your help. DL ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] SQL SERVERPOOL NAME BINDING HANGS the JBOSS initialization process (using weblogic jdbc driver )
Title: RE: [JBoss-user] SQL SERVERPOOL NAME BINDING HANGS the JBOSS initialization process (using weblogic jdbc driver ) I tried using wl driver once, didn't manage to make it work fully, but the first obstacle similar to your symptoms was that the licence file was not found on classpath. I fixed the situation by putting the jar with the driver explicitly on the classpath in run.bat file. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 17, 2001 12:09 PM To: [EMAIL PROTECTED] Subject: [JBoss-user] SQL SERVERPOOL NAME BINDING HANGS the JBOSS initialization process (using weblogic jdbc driver ) Hi Which is the real URl syntax in the jboss.cml file for a Weblogic Type Driver 4 based connection pool - beacuse I have a troublesome situation namely that the BINDING of the SQL SERVERPOOL HANGS the JBOSS initialization process. Note that the driver signature in the weblogic.jar file is weblogic.jdbc.mssqlserver4.Driver ( i have put the jar in the lib/ext dir )and attribute name=Driversorg.hsql.jdbcDriver,org.enhydra.instantdb.jdbc. idbDriver,webl ogic.jdbc.mssqlserver4.Driver/attribute ## JBOSS JCML (w/TOMCAT) ## mbean code=org.jboss.jdbc.XADataSourceLoader name=DefaultDomain:service=XADataSource,name=SQLServerPool attribute name=DataSourceClassorg.opentools.minerva.jdbc.xa.wrapper.X ADataSourceImp l/attribute attribute name=PoolNameSQLServerPool/attribute attribute name=URLjdbc:weblogic:mssqlserver4:vnserverdb@localhost:143 3/attribute ^^^ where is this JBOSS advised order coming from - is it NOT supposed to be relevant to the signature of the driver class ?? ^ .. /mbean then the JDBC driver is indeed loaded up AND the [SQLServerPool] is Initialized ... JBOSS 2.2.1. with Tomcat ... [JDBC provider] Loaded JDBC-driver:weblogic.jdbc.mssqlserver4.Driver OK . [SQLServerPool] Initializing [SQLServerPool] Initialized OK . .. BUT ... the SQL BINDING does not happen - it just HANGS in there: [JDBC provider] Starting [JDBC provider] Started [Hypersonic] .. [InstantDB] XA Connection pool InstantDB bound to java:/InstantDB ... #[DefaultDS] Starting [DefaultDS] XA Connection pool DefaultDS bound to java:/DefaultDS [DefaultDS] Started [SQLServerPool] Starting [SQLServerPool] XA Connection pool SQLServerPool bound to java:/SQLServerPool ?? @ IT HANGS HERE @@@ and in strandardjaws.xml I have : ## in STANDARDJAWS.XML # ?xml version=1.0 encoding=UTF-8? jaws datasourcejava:/SQLServerPool/datasource type-mappingMS SQLSERVER/type-mapping !--datasourcejava:/DefaultDS/datasource-- commented OUT !--type-mappingHypersonic SQL/type-mapping-- commented OUT .. .. . I did not modif. jboss.conf because the JBOSS documentation for 2.2.1 says I shouldn't put anything in there ... Any ideas anybody, please ? Do I need to declare smth else in other config. files ?? (APART from jboss.jcml AND standardjaws.xml ???) is JBOSS_AUTO.JCML involved in this ? TiA Val N. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.251 / Virus Database: 124 - Release Date: 26/04/2001 ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] JNDI name bindings are not working properly on deployment
Title: RE: [JBoss-user] JNDI name bindings are not working properly on deployment You are talking about the OLD bean jndi. If you mean you've deployed a jar and all the jndi bindings were correct, then you changed something and restarted, but the changes don't seem to have effect... Take a look in lib/ext - if you put the same jar there (for your mbean maybe because it needs client interfaces) - make sure that jar only has interfaces - no deployment descriptor and no bean implementation classes. Actually you should check your whole classpath for that and not only lib\ext. -Original Message- From: Scott M Stark [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 31, 2001 1:41 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] JNDI name bindings are not working properly on deployment Show your ejb-jar.xml and jboss.xml deployment descriptors. - Original Message - From: Selvarajah Vahees [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, May 31, 2001 1:27 AM Subject: [JBoss-user] JNDI name bindings are not working properly on deployment Hello folks, I have a few EJBs and I am trying to deploy it on a JBoss2.2 with embedded tomcat3.2.1. My deployment goes fine. But my JNDI name bindings are not getting place. It always puts one of my OLD bean JNDI on the Namespace. And also all my beans are getting that beans Namespace,which I feel that each individual beans should get their own. As a result only that OLD JNDI name under the +--invokers list. Basically JNDI name bindings are not working properly on deployment. So I am getting a NameNotfound Exception ---MyEJB (Not Bound) I tried the following 1..removing tmp/deploy dir itself 2.restarting the Mbean service for JNDI 3.restarting and deployments serveral time of the Server and last restarting the machine even. :-) Any idea what is really wrong? Thanks in advance R Vahees ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] Deploying MBeans together with ears, jars...
Title: RE: [JBoss-user] Deploying MBeans together with ears, jars... Thanks a lot. I'll take a look at it and give feedback. It will probably take a week though. I'm very busy right now. Marko. -Original Message- From: David Jencks [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 08, 2001 5:19 AM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] Deploying MBeans together with ears, jars... Hi, I've done some work in this direction, see patch 443701. This lets you deploy and undeploy mini-jcml files. As far as I know, the code for the mbeans has to be on the classpath when jboss starts. With this patch, you could easily modify j2eeDeployer to deploy a mini-jcml file from your ear, containing configuration for app-specific mbeans (such as connection factories). To make this complete, you need to be able to include the mbean codebase in the ear and deploy that too. My impression is that this will be a simple adaptation or use of the web installation/clustering stuff Marc is working on. I'm waiting to see what he comes up with. I think it may be desirable to create an application-specific namespace in the mbean namespace for mbeans deployed as part of an application, perhaps by including a key something like application=name in the ObjectName. I'd appreciate any comments/feedback david jencks On 2001.08.07 02:36:50 -0400 Marko Strukelj wrote: Hi all, I'm not familiar with the latest jsr efforts, but since working with jBoss and tasting the power of using MBeans as services together with EJBs the thing I'm waiting for now is to be able to bundle MBeans together with EJBs and deploy them in an application context. That way I can deploy a whole application in one single stroke and have multiple applications each with its own set of MBeans coexist in the same server. Now, there is no way that I know of, to have a sort of descriptor and deploy a package of multiple MBeans at anytime runtime. Are there any specs in the making that will solve this at J2EE level? Or are there any plans to support that as an extra non-spec feature? Thanks for any feedback, Marko. !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 3.2//EN HTML HEAD META HTTP-EQUIV=Content-Type CONTENT=text/html; charset=iso-8859-1 META NAME=Generator CONTENT=MS Exchange Server version 5.5.2650.12 TITLEDeploying MBeans together with ears, jars.../TITLE /HEAD BODY BR PFONT SIZE=2Hi all,/FONT /P PFONT SIZE=2I'm not familiar with the latest jsr efforts, but since working with jBoss and tasting the power of using MBeans as services together with EJBs the thing I'm waiting for now is to be able to bundle MBeans together with EJBs and deploy them in an quot;application contextquot;. That way I can deploy a whole application in one single stroke and have multiple applications each with its own set of MBeans coexist in the same server. /FONT/P PFONT SIZE=2Now, there is no way that I know of, to have a sort of descriptor and deploy a package of multiple MBeans at anytime runtime./FONT/P PFONT SIZE=2Are there any specs in the making that will solve this at J2EE level? Or are there any plans to support that as an extra non-spec feature?/FONT/P BR PFONT SIZE=2Thanks for any feedback,/FONT /P BR Pnbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; FONT SIZE=2Marko./FONT /P /BODY /HTML ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] issue with look up
Title: RE: [JBoss-user] issue with look up Obviously there is no naming variables set and there is no jndi.properties in the right place on your classpath. You can try passing these global properties to jvm when you run java: java -Djava.naming.factory.initial=org.jnp.interfaces.NamingContextFactory -Djava.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces -Djava.naming.provider.url=localhost com.zeborg.labor.unittests.RequestManagerJUnit Or whatever main class you run. Although it looks like you are running this through ant. For that you need to see reference for java task (http://jakarta.apache.org/ant/manual/index.html) To see how you pass global properties to jvm. Marko. -Original Message- From: Mahesh Agarwal [mailto:[EMAIL PROTECTED]] Sent: Monday, October 22, 2001 2:10 PM To: [EMAIL PROTECTED] Subject: [JBoss-user] issue with look up hi can anyone pls tell me why this error is [java] .the error in testCreateNodeForNonContractedSkill() method is java.l ang.RuntimeException: Error:javax.naming.NoInitialContextException: Need to spec ify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial [java] at javax.naming.spi.NamingManager.getInitialContext(NamingManage r.java:643) [java] at javax.naming.InitialContext.getDefaultInitCtx(InitialContext. java:246) [java] at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialCon text.java:283) [java] at javax.naming.InitialContext.lookup(InitialContext.java:350) [java] at com.zeborg.util.Util.getFromJNDI(Util.java:33) [java] at com.zeborg.labor.ejb.entity.EntityUtil.getSkillHome(EntityUti l.java:129) [java] at com.zeborg.labor.unittests.RequestManagerJUnit.testCreateNode ForNonContractedSkill(RequestManagerJUnit.java:281) [java] at java.lang.reflect.Method.invoke(Native Method) [java] at junit.framework.TestCase.runTest(TestCase.java:166) [java] at junit.framework.TestCase.runBare(TestCase.java:140) [java] at junit.framework.TestResult$1.protect(TestResult.java:106) [java] at junit.framework.TestResult.runProtected(TestResult.java:124) [java] at junit.framework.TestResult.run(TestResult.java:109) [java] at junit.framework.TestCase.run(TestCase.java:131) [java] at junit.framework.TestSuite.runTest(TestSuite.java:173) [java] at junit.framework.TestSuite.run(TestSuite.java:168) [java] at junit.textui.TestRunner.doRun(TestRunner.java:74) [java] at junit.textui.TestRunner.run(TestRunner.java:200) [java] at com.zeborg.labor.unittests.RequestManagerJUnit.main(RequestMa nagerJUnit.java:318) thanks in advance mahesh ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] jboss not starting with IBM jdk
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) at
RE: [JBoss-user] jboss not starting with IBM jdk
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
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
