Hi all,
I am upgrading from TeamSite 6.7.2 SP2 to 7.2.1, and I am having some challenges with jboss. I have searched devnet and found a few threads on this topic, but they all seem to be on Windows installation, and I am installing on Solaris 10.
I run the through the install, and things seemed to go fine all they way through until it starts to apply the changes. The problem starts with jboss not starting up. The following is a snippet of the error log:
2011-05-27 09:38:42,613 DEBUG org.jnp.interfaces.NamingContext - Failed to connect to darter:1099
javax.naming.CommunicationException: Failed to connect to server darter:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server darter:1099 [Root exception is java.net.ConnectException: Connection refused]]
It keeps retrying until it finally times out. The install continues on and then I get some error messages about IR service not starting up. It continues to try restarting until it times out. I have posted the installer.log for anyone's reading pleasure.
After doing some searching on devnet and knowledge docs, I found out that there was another log file for jboss and I found the following error in there:
Error occurred during initialization of VM
Could not reserve enough space for object heap
When I look at the available memory on the server, there is over 6 Gb. In the iwjboss.log, I noticed the start command is as follows:
JAVA_OPTS: -Dprogram.name=iw_jboss_run.sh -server -Xms1200m -Xmx1200m -XX:MaxPermSize=256m -XX:NewSize=256m -XX:MaxNewSize=768m -XX
urvivorRatio=6 -Djava
.class.path=/lcl/...
When doing some debugging with my jboss guru, he tries to use the command listed above to have it return the version of jboss, he gets the same error (not enough space for object heap). He then removes the 2 "New" parameters off and the command works just fine.
Upon his recommendation, I had the server physically rebooted and ran the install again. The install recognized that it only had to apply the configurations and tried to start up jboss and it failed again with the same errors above.
I don't know if anyone out there has ran into similar issues, but I would appreciate any assistance offered.
Thanks all
