I get the following deployment exception (going from 3.0.0 to 3.0.1). I
also inserted the jboss-service.xml it complains about at the bottom.
11:23:54,718 ERROR [Server] start failed
org.jboss.deployment.DeploymentException: Could not create deployment:
file:/C:/
armanta-3rdparty/jboss-3.0.1/server/abp/conf/jboss-service.xml; - nested
throwab
le: (java.lang.NoSuchFieldError: localCl)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:816)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:616)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:580)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:564)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
nDispatcher.java:284)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:324)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:221)
at org.jboss.Main.boot(Main.java:142)
at org.jboss.Main$1.run(Main.java:375)
at java.lang.Thread.run(Thread.java:536)
Caused by: java.lang.NoSuchFieldError: localCl
at org.jboss.resource.RARDeployer.init(RARDeployer.java:116)
at org.jboss.deployment.MainDeployer.init(MainDeployer.java:662)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:604)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:580)
at sun.reflect.GeneratedMethodAccessor16.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
nDispatcher.java:284)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491)
at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
at $Proxy4.deploy(Unknown Source)
at
org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen
tScanner.java:427)
at
org.jboss.deployment.scanner.URLDeploymentScanner.scanDirectory(URLDe
ploymentScanner.java:648)
at
org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS
canner.java:499)
at
org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(A
bstractDeploymentScanner.java:238)
at
org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:1
64)
at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
nDispatcher.java:284)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491)
at
org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
ler.java:967)
at $Proxy0.start(Unknown Source)
at
org.jboss.system.ServiceController.start(ServiceController.java:396)
at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
nDispatcher.java:284)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491)
at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
at $Proxy3.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:249)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:796)
... 14 more
11:23:54,734 ERROR [STDERR] org.jboss.deployment.DeploymentException: Could
not
create deployment:
file:/C:/armanta-3rdparty/jboss-3.0.1/server/abp/conf/jboss-s
ervice.xml; - nested throwable: (java.lang.NoSuchFieldError: localCl)
11:23:54,734 ERROR [STDERR] at
org.jboss.deployment.MainDeployer.start(MainD
eployer.java:816)
jboss-service.xml:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE server>
<!-- $Id: jboss-minimal.xml,v 1.1.2.1 2002/05/30 18:05:26 starksm Exp $ -->
<!--
===================================================================== -->
<!-- -
->
<!-- Minimal JBoss Server
-->
<!-- -
->
<!-- Note: This configuration required the addition of jboss.jar
-->
<!-- minimal/lib in order for the class loader to find the logging
lass -->
<!-- -
->
<!--
===================================================================== -->
<server>
<!--
| The Classpath element is needed for http based installations
| we need to list all the archives that the server needs at boot
| if the installation is local and the configuration is from file
| then there is no need to list the files and it should commented
-->
<!-- Load all content from the server lib -->
<classpath codebase="lib" archives="*"/>
<!--
==================================================================== -->
<!-- The
-->
<!--
==================================================================== -->
<!-- Main Deployer and SARDeployer are provided by main -->
<!-- EJB deployer, remove to disable EJB behavior-->
<mbean code="org.jboss.ejb.EJBDeployer"
name="jboss.ejb:service=EJBDeployer">
<attribute name="VerifyDeployments">true</attribute>
<attribute name="ValidateDTDs">false</attribute>
<attribute name="MetricsEnabled">false</attribute>
<attribute name="VerifierVerbose">true</attribute>
<attribute name="BeanCacheJMSMonitoringEnabled">false</attribute>
</mbean>
<!-- EAR deployer, remove if you are not using Web layers -->
<mbean code="org.jboss.deployment.EARDeployer"
name="jboss.j2ee:service=EARDeployer">
</mbean>
<!--
==================================================================== -->
<!-- Log4j
-->
<!--
==================================================================== -->
<mbean code="org.jboss.logging.Log4jService"
name="jboss.system:type=Log4jService,service=Logging">
<attribute name="ConfigurationURL">resource:log4j.xml</attribute>
</mbean>
<!--
==================================================================== -->
<!-- Class
-->
<!--
==================================================================== -->
<mbean code="org.jboss.web.WebService"
name="jboss:service=Webserver">
<attribute name="Port">8083</attribute>
<!-- Should resources and non-EJB classes be downloadable -->
<attribute name="DownloadServerClasses">true</attribute>
</mbean>
<!--
==================================================================== -->
<!--
-->
<!--
==================================================================== -->
<mbean code="org.jboss.naming.NamingService"
name="jboss:service=Naming">
<attribute name="Port">1099</attribute>
</mbean>
<mbean code="org.jboss.naming.JNDIView"
name="jboss:service=JNDIView"/>
<!--
==================================================================== -->
<!--
-->
<!--
==================================================================== -->
<mbean code="org.jboss.security.plugins.SecurityConfig"
name="jboss.security:name=SecurityConfig">
<attribute
name="LoginConfig">jboss.security:name=XMLLoginConfig</attribute>
</mbean>
<mbean code="org.jboss.security.auth.login.XMLLoginConfig"
name="jboss.security:name=XMLLoginConfig">
<attribute name="ConfigResource">login-config.xml</attribute>
</mbean>
<!-- JAAS security manager and realm mapping -->
<mbean code="org.jboss.security.plugins.JaasSecurityManagerService"
name="jboss.security:name=JaasSecurityManager">
<attribute name="SecurityManagerClassName">
org.jboss.security.plugins.JaasSecurityManager
</attribute>
</mbean>
<!--
==================================================================== -->
<!--
-->
<!--
==================================================================== -->
<mbean code="org.jboss.tm.TransactionManagerService"
name="jboss:service=TransactionManager">
<attribute name="TransactionTimeout">3600</attribute>
<!-- Use this attribute if you need to use a specific Xid
implementation
<attribute name="XidClassName">oracle.jdbc.xa.OracleXid</attribute>
-->
</mbean>
<!--
| Uncomment to use Tyrex (tyrex.exolab.org) transaction manager plugin
| instead of the org.jboss.tm.TransactionManagerService and comment out
| the TransactionManagerService above.
| Make sure you have Xerces in lib/. At the moment JBoss does not
| ship Xerces as part of distribution. Version 1.x seems to work fine,
| though 2.x should as well, use whichever you like.
|
<mbean code="org.jboss.tm.plugins.tyrex.TransactionManagerService"
name="jboss:service=TransactionManager">
<attribute
name="ConfigFileName">../conf/default/domain.xml</attribute>
</mbean>
-->
<mbean code="org.jboss.tm.usertx.server.ClientUserTransactionService"
name="jboss:service=ClientUserTransaction">
</mbean>
<!-- The CachedConnectionManager is used partly to relay started
UserTransactions to
open connections so they may be enrolled in the new tx-->
<mbean code="org.jboss.resource.connectionmanager.CachedConnectionManager"
name="jboss.jca:service=CachedConnectionManager">
</mbean>
<!--
==================================================================== -->
<!-- Invokers to the JMX
-->
<!--
==================================================================== -->
<!-- RMI/JRMP invoker -->
<mbean code="org.jboss.invocation.jrmp.server.JRMPInvoker"
name="jboss:service=invoker,type=jrmp">
<attribute name="RMIObjectPort">4444</attribute>
<!--
<attribute name="RMIClientSocketFactory">custom</attribute>
<attribute name="RMIServerSocketFactory">custom</attribute>
<attribute name="RMIServerSocketAddr">custom</attribute>
-->
</mbean>
<mbean code="org.jboss.invocation.local.LocalInvoker"
name="jboss:service=invoker,type=local">
</mbean>
<!--
==================================================================== -->
-->
<!-- Deployment
-->
-->
<!-- Use URLDirectoryScanner if you need to specify which urls
-->
<!-- directories to scan, and which are urls to be deployed
ctly. -->
-->
<!-- URLDeploymentScanner assumes that all directories are to be
scanned, -->
<!-- which can cause problems if you deploy exploded
-->
-->
<!--
==================================================================== -->
<mbean code="org.jboss.deployment.scanner.URLDeploymentScanner"
name="jboss.deployment:type=DeploymentScanner,flavor=URL">
<depends
optional-attribute-name="Deployer">jboss.system:service=MainDeployer</depend
s>
<!-- The URLComparator can be used to specify a deployment ordering
for deployments found in a scanned directory. The class specified
must be an implementation of java.util.Comparator, it must be able
to compare two URL objects, and it must have a no-arg constructor.
Two deployment comparators are shipped with JBoss:
- org.jboss.deployment.DeploymentSorter
Sorts by file extension, as follows:
"sar", "service.xml", "rar", "jar", "war", "wsr", "ear",
"zip",
"*"
- org.jboss.deployment.scanner.PrefixDeploymentSorter
If the name portion of the url begins with 1 or more digits,
those
digits are converted to an int (ignoring leading zeroes), and
files are deployed in that order. Files that do not start with
any digits will be deployed last, and they will be sorted by
extension as above with DeploymentSorter.
-->
<attribute
name="URLComparator">org.jboss.deployment.DeploymentSorter</attribute>
<!-- The Filter specifies a java.io.FileFilter for scanned
directories. Any file not accepted by this filter will not be
deployed. The org.jboss.deployment.scanner.DeploymentFilter
rejects the following patterns:
"#*", "%*", ",*", ".*", "_$*", "*#", "*$", "*%", "*.BAK",
"*.old", "*.orig", "*.rej", "*.bak", "*,v", "*~",
".make.state",
".nse_depinfo", "CVS", "CVS.admin", "RCS", "RCSLOG", "SCCS",
"TAGS", "core", "tags"
-->
<attribute
name="Filter">org.jboss.deployment.scanner.DeploymentFilter</attribute>
<attribute name="ScanPeriod">5000</attribute>
<!--
| URLs are comma seperated and unprefixed arguments are considered
| file URLs and resolve relative to server home unless the given path
| is absolute. Comment this out if using URLDirectoryScanner.
-->
<attribute name="URLs">
./deploy
</attribute>
<!-- Use this for URLDirectoryScanner. Each entry specifies either a
dir (directory to be scanned), or url (url to be deployed). Like
the URLs for the DeploymentScanner above, a file: protocol will
be assumed if not specified otherwise. Uncomment for use with
URLDirectoryScanner .
-->
<!--
<attribute name="URLs">
<urls>
<dir name="./deploy" />
<url name="./deploy/examples/myapp.ear" />
<dir name="./deploy/examples" />
<url name="http://www.test.com/samples/myapp.ear"; />
</urls>
</attribute>
-->
</mbean>
</server>
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Kim, Yong
Sent: Wednesday, September 11, 2002 11:08 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [JBoss-user] Which one to upgrade to? 3.0.1 or 3.0.2
I have upgraded from 3.0.0 to 3.0.2 with no problem. What was the issue
with the configuration? I might have misseed something.
Mitchell Kim
-----Original Message-----
From: Eric Kaplan [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 11, 2002 10:52 AM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-user] Which one to upgrade to? 3.0.1 or 3.0.2
On a related note, I'd like to upgrade from 3.0.0 to 3.0.2 as well, but when
I try the app server doesn't even start. It's as if my configuration that
works
under 3.0.0 is invalid under 3.0.2. If this is a minor release, why would
the
configuration parameters have changed, and is there a guidebook on what to
do.
This seems to happen anytime we upgrade.
Eric
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Saroj Kumar
Sent: Wednesday, September 11, 2002 10:09 AM
To: [EMAIL PROTECTED]
Subject: [JBoss-user] Which one to upgrade to? 3.0.1 or 3.0.2
Hi All,
We are faced with a dillema.
We are working on a big project which is having around 200 tables and
125 use cases. We have been using 3.0.0 but We found that 3.0.1 fixes
the Char Problem with ORACLE.
Now, 3.0.2 is also out.
We have to decide which one to use: 3.0.1 or 3.0.2. It is very important
that none of the code written for 3.0.0 breaks.
As we are a big team(20 members) and working on a very tight schedule,
it is very important for us to know which one is more stable.
Please help me take the wise decision.
Thanks,
Saroj
-------------------------------------------------------
In remembrance
www.osdn.com/911/
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
-------------------------------------------------------
In remembrance
www.osdn.com/911/
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
-------------------------------------------------------
In remembrance
www.osdn.com/911/
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
-------------------------------------------------------
In remembrance
www.osdn.com/911/
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
