-
30. Re: Problems deploying my older application on Jboss 7 (Failed to define class)
erasmomarciano Jun 11, 2013 8:43 AM (in response to chandrasachin16)Try to modify JAVA_OPTS
set "JAVA_OPTS=-Xms64M -Xmx1303M -XX:MaxPermSize=512
replace JAVA_OPTS as following
"JAVA_OPTS=-Xms64M -Xmx1303M -XX:NewSize=256m -XX:MaxNewSize=256m -XX:PermSize=256m -XX:MaxPermSize=512m -XX:+DisableExplicitGC"
-
31. Re: Problems deploying my older application on Jboss 7 (Failed to define class)
sfcoy Jun 11, 2013 9:27 PM (in response to chandrasachin16)Sachin Chandra wrote:
Hi Stephen,
...
I wanted to ask one question may be it's a very silly question.My question is I am building the schemas as well as webservices using old jaxb jars, axis jars and wsdl4j-1.5.1 jars using ant which are kept in a custom folder called buildtimejar .But there are few other jars which are referred from Jboss7 jars( xalan.jar and more in modules folder ) to build web services and which are not available in this buildtime folder.Earlier I used to point to jboss 5 bundeled library jars which used to contain xalan jars, but now it is building the webservices using the new xalan jars and perhaps few more jars of jboss 7,but schemas are build using older jars, so do you think this could cause some problem, or rather would it be a wise thing to use jboss 5 jars to build webservices rather than the jboss 7 and then deploy it in jboss 7.
Need your suggestions.
Sachin
Are you using JAX-WS? If so, you do not need any jars at all because everything you need is provided by the Java 6/7 JDK.
-
32. Re: Problems deploying my older application on Jboss 7 (Failed to define class)
sfcoy Jun 11, 2013 9:46 PM (in response to chandrasachin16)Sachin Chandra wrote:
Hi Stephen,
Sorry couldn't update you on this front. I reverted the settings to
set "JAVA_OPTS=-Xms64M -Xmx1303M -XX:MaxPermSize=512M" the standard settings but didn't had any luck . I still get the same error--
...
Everytime we change this the failure point does seem to change.
Please:
- attach a complete copy of your boot.log file
- provide the output of jar -tf xmes.ear for your current application and all of it's component war files.
In the meantime, let's bump the memory again: -Xmx1536M -XX:MaxPermSize=640M and see what happens.
I suspect that a 3GB machine will not be big enough, however, as the above is about as large as you can go on 32bit Windows.
-
33. Re: Problems deploying my older application on Jboss 7 (Failed to define class)
chandrasachin16 Jun 12, 2013 7:32 AM (in response to sfcoy)Hi,
We are using axis to build the web services. I found the list of jars used to build the webservices in a different xml file and these are as follows
log4j-1.2.13.jar, commons-logging-1.1.jar, axis.jar, jaxrpc.jar, wsdl4j-1.5.1.jar, commons-discovery-0.4.jar, saaj.jar (7 jars).
First of all tried with this
"JAVA_OPTS=-Xms64M -Xmx1303M -XX:NewSize=256m -XX:MaxNewSize=256m -XX:PermSize=256m -XX:MaxPermSize=512m -XX:+DisableExplicitGC"
but didn't had any luck
Then tried with
"JAVA_OPTS=-Xms64M -Xmx1536M -XX:MaxPermSize=640M"
but still no luck . I have attached the boot log and the server log.
The xmes.ear contains the following
servicelayer.jar
OperatorUI_Services.war
OperatorUI_EJB.jar
adminui.war
META-INF
mes-engine.jar
lib
Thanks
Sachin
-
xmes.ear_list_of classes.txt.zip 16.4 KB
-
log.rar.zip 35.1 KB
-