Can't get Portal+AS binary to run on windows

[style.x7]

Dear all,

I've downloaded the latest JBoss Portal 2.7.0 + JBoss AS 4.2.3 binary bundle and followed the reference guide but got the following error when I run 'run.bat'.

===============================================================================

 JBoss Bootstrap Environment

 JBOSS_HOME: C:\jboss-portal-2.7.0.GA

 JAVA: C:\Program Files\Java\jdk1.6.0_01\bin\java

 JAVA_OPTS: -Dprogram.name=run.bat -server -Xms128m -Xmx512m -Dsun.rmi.dgc.cli
ent.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000

 CLASSPATH: C:\Program Files\Java\jdk1.6.0_01\lib\tools.jar;C:\jboss-portal-2.7
.0.GA\bin\run.jar

===============================================================================

11:38:32,312 INFO [Server] Starting JBoss (MX MicroKernel)...
11:38:32,312 INFO [Server] Release ID: JBoss [Trinity] 4.2.3.GA (build: SVNTag=
JBoss_4_2_3_GA date=200807181417)
11:38:32,312 INFO [Server] Home Dir: C:\jboss-portal-2.7.0.GA
11:38:32,312 INFO [Server] Home URL: file:/C:/jboss-portal-2.7.0.GA/
11:38:32,312 INFO [Server] Patch URL: null
11:38:32,312 INFO [Server] Server Name: default
11:38:32,312 INFO [Server] Server Home Dir: C:\jboss-portal-2.7.0.GA\server\def
ault
11:38:32,312 INFO [Server] Server Home URL: file:/C:/jboss-portal-2.7.0.GA/serv
er/default/
11:38:32,312 INFO [Server] Server Log Dir: C:\jboss-portal-2.7.0.GA\server\defa
ult\log
11:38:32,312 INFO [Server] Server Temp Dir: C:\jboss-portal-2.7.0.GA\server\def
ault\tmp
11:38:32,312 INFO [Server] Root Deployment Filename: jboss-service.xml
11:38:32,906 INFO [ServerInfo] Java version: 1.6.0_01,Sun Microsystems Inc.
11:38:32,906 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.6.0_01-b06
,Sun Microsystems Inc.
11:38:32,906 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
11:38:34,218 INFO [Server] Core system initialized
11:38:38,156 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083
/
11:38:38,171 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resour
ce:jboss-log4j.xml
ERROR: invalid console appender config detected, console stream is looping

It hangs there. I tried the solution from: http://raykrueger.blogspot.com/2007/01/jboss-console-stream-is-looping-error.html. The looping error is gone but there's a lot of errors:

State: CONFIGURED
 I Depend On:
 portal:deployer=PortalWebApp
 portal:service=LayoutService

ObjectName: portal:deploymentFactory=Theme
 State: CONFIGURED
 I Depend On:
 portal:deployer=PortalWebApp
 portal:service=ThemeService

ObjectName: portal:deployer=Adapter
 State: CONFIGURED
 I Depend On:
 jboss.web:service=WebServer
 portal:deployer=PortalWebApp
 portal:service=EntityResolver

ObjectName: jboss.mq:service=InvocationLayer,type=HTTP
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=Invoker
 jboss.web:service=WebServer

ObjectName: jboss:service=KeyGeneratorFactory,type=HiLo
 State: CONFIGURED
 I Depend On:
 jboss:service=TransactionManager
 jboss.jca:service=DataSourceBinding,name=DefaultDS

ObjectName: jboss.mq:service=StateManager
 State: CONFIGURED
 I Depend On:
 jboss.jca:service=DataSourceBinding,name=DefaultDS
 Depends On Me:
 jboss.mq:service=DestinationManager

ObjectName: jboss.mq:service=DestinationManager
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=MessageCache
 jboss.mq:service=PersistenceManager
 jboss.mq:service=StateManager
 jboss.mq:service=ThreadPool
 jboss:service=Naming
 Depends On Me:
 jboss.mq.destination:service=Topic,name=testTopic
 jboss.mq.destination:service=Topic,name=securedTopic
 jboss.mq.destination:service=Topic,name=testDurableTopic
 jboss.mq.destination:service=Queue,name=testQueue
 jboss.mq.destination:service=Queue,name=A
 jboss.mq.destination:service=Queue,name=B
 jboss.mq.destination:service=Queue,name=C
 jboss.mq.destination:service=Queue,name=D
 jboss.mq.destination:service=Queue,name=ex
 jboss.mq:service=SecurityManager
 jboss.mq.destination:service=Queue,name=DLQ

ObjectName: jboss.mq:service=PersistenceManager
 State: CONFIGURED
 I Depend On:
 jboss.jca:service=DataSourceBinding,name=DefaultDS
 Depends On Me:
 jboss.mq:service=DestinationManager

ObjectName: jboss.mq.destination:service=Topic,name=testTopic
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=DestinationManager
 jboss.mq:service=SecurityManager

ObjectName: jboss.mq.destination:service=Topic,name=securedTopic
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=DestinationManager
 jboss.mq:service=SecurityManager

ObjectName: jboss.mq.destination:service=Topic,name=testDurableTopic
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=DestinationManager
 jboss.mq:service=SecurityManager

ObjectName: jboss.mq.destination:service=Queue,name=testQueue
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=DestinationManager
 jboss.mq:service=SecurityManager

ObjectName: jboss.mq.destination:service=Queue,name=A
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=DestinationManager

ObjectName: jboss.mq.destination:service=Queue,name=B
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=DestinationManager

ObjectName: jboss.mq.destination:service=Queue,name=C
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=DestinationManager

ObjectName: jboss.mq.destination:service=Queue,name=D
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=DestinationManager

ObjectName: jboss.mq.destination:service=Queue,name=ex
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=DestinationManager

ObjectName: jboss.mq:service=Invoker
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=TracingInterceptor
 jboss:service=Naming
 Depends On Me:
 jboss.mq:service=InvocationLayer,type=HTTP
 jboss.mq:service=InvocationLayer,type=JVM
 jboss.mq:service=InvocationLayer,type=UIL2

ObjectName: jboss.mq:service=TracingInterceptor
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=SecurityManager
 Depends On Me:
 jboss.mq:service=Invoker

ObjectName: jboss.mq:service=SecurityManager
 State: CONFIGURED
 I Depend On:
 jboss.security:service=JaasSecurityManager
 jboss.mq:service=DestinationManager
 Depends On Me:
 jboss.mq.destination:service=Topic,name=testTopic
 jboss.mq.destination:service=Topic,name=securedTopic
 jboss.mq.destination:service=Topic,name=testDurableTopic
 jboss.mq.destination:service=Queue,name=testQueue
 jboss.mq:service=TracingInterceptor
 jboss.mq.destination:service=Queue,name=DLQ

ObjectName: jboss.mq.destination:service=Queue,name=DLQ
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=DestinationManager
 jboss.mq:service=SecurityManager

ObjectName: jboss.mq:service=InvocationLayer,type=JVM
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=Invoker

ObjectName: jboss.mq:service=InvocationLayer,type=UIL2
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=Invoker

ObjectName: jboss.jca:service=LocalTxCM,name=DefaultDS
 State: CONFIGURED
 I Depend On:
 jboss.jca:service=ManagedConnectionPool,name=DefaultDS
 jboss.jca:service=CachedConnectionManager
 jboss.security:service=JaasSecurityManager
 jboss:service=TransactionManager
 Depends On Me:
 jboss.jca:service=DataSourceBinding,name=DefaultDS

ObjectName: jboss.jca:service=ManagedConnectionPool,name=DefaultDS
 State: CONFIGURED
 I Depend On:
 jboss.jca:service=ManagedConnectionFactory,name=DefaultDS
 Depends On Me:
 jboss.jca:service=LocalTxCM,name=DefaultDS

ObjectName: jboss.jca:service=ManagedConnectionFactory,name=DefaultDS
 State: CONFIGURED
 I Depend On:
 jboss:service=Hypersonic,database=localDB
 jboss.jca:service=RARDeployment,name='jboss-local-jdbc.rar'
 Depends On Me:
 jboss.jca:service=ManagedConnectionPool,name=DefaultDS

ObjectName: jboss.jca:service=DataSourceBinding,name=DefaultDS
 State: CONFIGURED
 I Depend On:
 jboss.jca:service=LocalTxCM,name=DefaultDS
 Depends On Me:
 jboss.ejb:service=EJBTimerService,persistencePolicy=database
 jboss:service=KeyGeneratorFactory,type=HiLo
 jboss.mq:service=StateManager
 jboss.mq:service=PersistenceManager



ObjectName: jboss.jca:service=TxCM,name=JmsXA
 State: CONFIGURED
 I Depend On:
 jboss.jca:service=ManagedConnectionPool,name=JmsXA
 jboss.jca:service=CachedConnectionManager
 jboss.security:service=JaasSecurityManager
 jboss:service=TransactionManager
 Depends On Me:
 jboss.jca:service=ConnectionFactoryBinding,name=JmsXA

ObjectName: jboss.jca:service=ManagedConnectionPool,name=JmsXA
 State: CONFIGURED
 I Depend On:
 jboss.jca:service=ManagedConnectionFactory,name=JmsXA
 Depends On Me:
 jboss.jca:service=TxCM,name=JmsXA

ObjectName: jboss.jca:service=ManagedConnectionFactory,name=JmsXA
 State: CONFIGURED
 I Depend On:
 jboss.jca:service=RARDeployment,name='jms-ra.rar'
 Depends On Me:
 jboss.jca:service=ManagedConnectionPool,name=JmsXA

ObjectName: jboss.jca:service=ConnectionFactoryBinding,name=JmsXA
 State: CONFIGURED
 I Depend On:
 jboss.jca:service=TxCM,name=JmsXA

ObjectName: jboss.jca:service=LocalTxCM,name=PortalDS
 State: CONFIGURED
 I Depend On:
 jboss.jca:service=ManagedConnectionPool,name=PortalDS
 jboss.jca:service=CachedConnectionManager
 jboss:service=TransactionManager
 Depends On Me:
 jboss.jca:service=DataSourceBinding,name=PortalDS

ObjectName: jboss.jca:service=ManagedConnectionPool,name=PortalDS
 State: CONFIGURED
 I Depend On:
 jboss.jca:service=ManagedConnectionFactory,name=PortalDS
 Depends On Me:
 jboss.jca:service=LocalTxCM,name=PortalDS

ObjectName: jboss.jca:service=ManagedConnectionFactory,name=PortalDS
 State: CONFIGURED
 I Depend On:
 jboss.jca:service=RARDeployment,name='jboss-local-jdbc.rar'
 Depends On Me:
 jboss.jca:service=ManagedConnectionPool,name=PortalDS

ObjectName: jboss.jca:service=DataSourceBinding,name=PortalDS
 State: CONFIGURED
 I Depend On:
 jboss.jca:service=LocalTxCM,name=PortalDS
 Depends On Me:
 portal:service=Hibernate,type=CMS
 portal:service=CMS
 portal:service=Hibernate,type=Workflow
 portal:service=Hibernate,type=WSRPConsumer
 portal:service=Hibernate
 portal:service=Hibernate,type=Instance
 portal:service=Hibernate,type=PortalObject
 portal:service=Hibernate,type=Portlet

--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.web:service=WebServer
 State: FAILED
 Reason: org.jboss.xb.binding.JBossXBRuntimeException: Failed to create a new S
AX parser
 Depends On Me:
 portal:deployer=Adapter
 jboss.mq:service=InvocationLayer,type=HTTP

ObjectName: jboss.jca:service=RARDeployment,name='jboss-local-jdbc.rar'
 State: NOTYETINSTALLED
 Depends On Me:
 jboss.jca:service=ManagedConnectionFactory,name=DefaultDS
 jboss.jca:service=ManagedConnectionFactory,name=PortalDS

ObjectName: jboss.jca:service=RARDeployment,name='jms-ra.rar'
 State: NOTYETINSTALLED
 Depends On Me:
 jboss.jca:service=ManagedConnectionFactory,name=JmsXA

ObjectName: portal:service=JAASLoginModule
 State: FAILED
 Reason: org.jboss.security.auth.login.ParseException: Encountered "<?xml" at l
ine 1, column 1.
Was expecting one of:
 <EOF>
 <IDENTIFIER> ...

 I Depend On:
 jboss.security:service=XMLLoginConfig
 jboss.security:service=JaasSecurityManager
 Depends On Me:
 portal:service=CMS
 portal:service=IdentitySecurityBridge


11:44:20,281 INFO [Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBos
s_4_2_3_GA date=200807181417)] Started in 48s:47ms

Please help me with this as I'm evaluating JBoss Portal software for my undergrad final year project. I'm using windows xp sp3 and other portal software like Liferay are able to run without much issues. Thanks :)

[theute]

Did you check the md5sum ? Try to download the package again

[peterj]

You are using a very old version of JDK 6. I recommend either updating you JDK to 6u7 or 6u10, or perhaps going with the latest JDK 5.

Also,what you posted was the deployment report which rarely indicates why the deployments failed. Earlier in the console log there should be an exception stack trace earlier in the console log which gives the real cause. You might have to increase the buffer size for the command prompt to prevent the stack trace from scrolling off of the window (I set mine to 900 lines), or you can redirect stdout to a file. So if you are still having problems, please post the first exception stack from the console log.

[style.x7]

Hi Thomas and Peter!

I did the checksum using FastSum and the package is good:

C:\>fsum "c:\jboss-portal-2.7.0.GA-bundled.zip"
MD5 Checksum calculation and verification utility. [1.9.0.149] EN
(C) 2003-2005 Kirill Zinov and Vitaly Rogotsevich. Web site: www.fastsum.com

c:\jboss-portal-2.7.0.GA-bundled.zip 0B1521EFA362FE30068A076501D46EB5



Calculation summary:
 Processed 1 files in 0 folders with total size 167.23 Mb.
 Elapsed time: 00:00:07 Average speed: 21.62 Mb\Sec.

I managed to get over the looping problem by updating to JDK 6u11 and server can be started. But when I went into http://localhost:8080/portal, there's lots of errors. I also tried JDK 5 (jdk1.5.0_17) as the quickstart doc indicate to use JDK 1.4/1.5 but I still get http 500 internal server error.

Here's the zip file containing the stdout (from server start to errors while loading portal): http://www.fileden.com/files/2008/12/9/2216582/stdout.zip

Please have a look and let me know what went wrong, thanks :) There are out of memory exceptions but I don't think my laptop is having too low specs, have 1GB rams and before run.bat, the memory consumption was at ~330MB.

p.s. Really like JBoss portal documentation, so far the best I have seen. But if I can't get it running, I can't convince my professor >< Please help~

[/img]

[theute]

You are running out of PermGen space, your machine is not the culprit, but you need to specify your JVM to let it use more memory than the low default.

See the FAQ:
http://www.jboss.org/community/docs/DOC-10701

Q: I get "java.lang.OutOfMemoryError: PermGenSpace" errors

A: Increase your max perm gen space in run.conf (on Windows, you need to edit run.bat as run.conf is not taken into account on Windows systems) by adding the following option to JAVA_OPTS:

-XX:MaxPermSize=128m

[style.x7]

Thank you Thomas!

Finally it's up and running :)