• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

JBoss 5.1.0.GA startup error messages

 
Mary Taylor
Ranch Hand
Posts: 327
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Although I can access the JMX console, I see these error messages when starting a new JBoss 5.1.0.GA installation. I'd like to understand why they are happening.

DEPLOYMENTS MISSING DEPENDENCIES:
Deployment "jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3_endpoint" is missing the f
ollowing dependencies:
Dependency "jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3" (should be in state "Co
nfigured", but is actually in state "**ERROR**")
Deployment "jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3_endpoint" is missing the foll
owing dependencies:
Dependency "jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3" (should be in state "Confi
gured", but is actually in state "**ERROR**")
Deployment "jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3" is missing the following dep
endencies:
Dependency "<UNKNOWN jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3>" (should be in st
ate "Described", but is actually in state "** UNRESOLVED Demands 'jndi:SecureManagementView/remote-org.jboss.deployers.spi.m
anagement.ManagementView' **")
Deployment "jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3_endpoint" is missing the foll
owing dependencies:
Dependency "jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3" (should be in state "Confi
gured", but is actually in state "PreInstall")
Deployment "jboss.jca:name=JmsXA,service=ConnectionFactoryBinding" is missing the following dependencies:
Dependency "jboss.jca:name=JmsXA,service=TxCM" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.jca:name=JmsXA,service=ManagedConnectionFactory" is missing the following dependencies:
Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.jca:name=JmsXA,service=ManagedConnectionPool" is missing the following dependencies:
Dependency "jboss.jca:name=JmsXA,service=ManagedConnectionFactory" (should be in state "Create", but is actually in stat
e "Configured")
Deployment "jboss.jca:name=JmsXA,service=TxCM" is missing the following dependencies:
Dependency "jboss.jca:name=JmsXA,service=ManagedConnectionPool" (should be in state "Create", but is actually in state "
Configured")
Deployment "jboss.messaging.connectionfactory:service=ClusterPullConnectionFactory" is missing the following dependencies:

Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "Configured")
Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.messaging.connectionfactory:service=ClusteredConnectionFactory" is missing the following dependencies:
Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "Configured")
Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.messaging.connectionfactory:service=ConnectionFactory" is missing the following dependencies:
Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "Configured")
Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.messaging.destination:name=DLQ,service=Queue" is missing the following dependencies:
Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "Configured")
Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.messaging.destination:name=ExpiryQueue,service=Queue" is missing the following dependencies:
Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create", but is actually in state "Configured")
Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.messaging:service=PostOffice" is missing the following dependencies:
Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.messaging:service=ServerPeer" is missing the following dependencies:
Dependency "jboss.messaging:service=PersistenceManager" (should be in state "Create", but is actually in state "**ERROR*
*")
Dependency "jboss.messaging:service=JMSUserManager" (should be in state "Create", but is actually in state "**ERROR**")
Deployment "jboss.mq:service=DestinationManager" is missing the following dependencies:
Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create", but is actually in state "Configured")

DEPLOYMENTS IN ERROR:
Deployment "<UNKNOWN jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3>" is in error due to
the following reason(s): ** UNRESOLVED Demands 'jndi:SecureManagementView/remote-org.jboss.deployers.spi.management.Managem
entView' **
Deployment "jboss.messaging:service=JMSUserManager" is in error due to the following reason(s): **ERROR**, java.lang.Secur
ityException: Unauthenticated caller:null
Deployment "jboss.messaging:service=PersistenceManager" is in error due to the following reason(s): **ERROR**, java.lang.S
ecurityException: Unauthenticated caller:null
Deployment "jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3" is in error due to the follo
wing reason(s): **ERROR**, java.lang.SecurityException: Unauthenticated caller:null
Deployment "jboss:service=KeyGeneratorFactory,type=HiLo" is in error due to the following reason(s): java.lang.SecurityExc
eption: Unauthenticated caller:null
Deployment "jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3" is in error due to the fo
llowing reason(s): **ERROR**, java.lang.SecurityException: Unauthenticated caller:null

14:04:35,229 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
14:04:35,245 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
14:04:35,260 INFO [ServerImpl] JBoss (Microcontainer) [5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221053)] Started i
n 30s:297ms

I'm a new JBoss user so thank you for any help.
 
Vijitha Kumara
Bartender
Posts: 3913
9
Chrome Fedora Hibernate
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Is this a fresh installation that you run for the first time or do you have any other applications deployed already?
 
Mary Taylor
Ranch Hand
Posts: 327
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It is a new installation; nothing has been deployed.
 
Vijitha Kumara
Bartender
Posts: 3913
9
Chrome Fedora Hibernate
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Have you modified any config files? From what I see there seems to be some issues with JMS configuration. If so try with a clean copy again...
 
Mary Taylor
Ranch Hand
Posts: 327
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am sorry; I forgot that I did try to deploy the HelloWorld ESB project; that did not work so I undeployed the ESB platform from JBoss. Still, JBoss starts with a lot of errors as shown in the initial post. When you advise "starting with a clean copy", what do you mean a clean copy of? I didn't follow your advice there.
 
Alpesh Gediya
Greenhorn
Posts: 24
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator


Download fresh copy from JBoss site. Unzip downloaded zip file to your desired location and try to start Jboss.
There are changes you might have accidentally changed any xml file.
 
Mary Taylor
Ranch Hand
Posts: 327
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
So you're suggesting to start with a fresh copy of JBoss? I didn't quite understand that the first time. I will do that and then try to install the ESB again, then go to the deploy the ESB HelloWorld.

Do I just delete the current JBoss directory to remove it or should I run an uninstall script?

Thanks.
 
Vijitha Kumara
Bartender
Posts: 3913
9
Chrome Fedora Hibernate
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Mary Taylor wrote:...Do I just delete the current JBoss directory to remove it ...

Yes thats fine, and remember to remove any environment variables you added, specially JBOSS_HOME...
Once you install a fresh copy first try to startup and go to the jboss console to make sure the installation is fine.
 
Mary Taylor
Ranch Hand
Posts: 327
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
why would I have to remove JBOSS_HOME if I want to create the same directory for the second install? Do I remove the environment variable and then add it back after the new installation?
 
Vijitha Kumara
Bartender
Posts: 3913
9
Chrome Fedora Hibernate
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Mary Taylor wrote:why would I have to remove JBOSS_HOME if I want to create the same directory for the second install?...

If it's the same location with the same distro as before then no problem, It's that incase if you install it somewhere else there might be conflicts
 
Peter Johnson
author
Bartender
Posts: 5852
7
Android Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Don't set JBOSS_HOME. The run script will set it automatically. If you set it manually, then weird things can happen (you might end up using the wrong JBoss AS installation.)
 
Mary Taylor
Ranch Hand
Posts: 327
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I didn't unset it since I was using the same directory for the second install; seemed to work well. What a painless install! Get some error messages when I access the admin page; will post those tomorrow if I can't google and resolve them. Thanks for your help!
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic