[JBoss Portal] - Re: instances problem
by habicht
The modifications for PostgreSQL are made and the driver is under /jboss/server/default/lib. JBoss created all tables and filld them with data. to make sure that it's not the DB I set the DB config back to hypersonic (original xml-files from the zip). It produced the same problem.
About the stack trace:
During the jboss start I receive the error below but I don't know if it related to my problem. It is the only error I get during starting jboss, deploying the projects and calling the pages with my browser. If you meant something different please tell me. I'm still not very familiar with the whole topic.
christof
07:30:19,718 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
--- MBeans waiting for other MBeans ---
ObjectName: jboss.ejb:service=EJBTimerService,persistencePolicy=database
State: CONFIGURED
I Depend On:
jboss.jca:service=DataSourceBinding,name=DefaultDS
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.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
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.jca:service=DataSourceBinding,name=DefaultDS
State: NOTYETINSTALLED
Depends On Me:
jboss.ejb:service=EJBTimerService,persistencePolicy=database
jboss:service=KeyGeneratorFactory,type=HiLo
jboss.mq:service=StateManager
jboss.mq:service=PersistenceManager
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054604#4054604
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4054604
18Â years, 10Â months
[EJB 3.0] - Any way to do global overrides for EJB3 defaults?
by dbudworth
I think I just realized that I've been barking up the wrong tree for a few months with the issues I'm having with using a foreign JCA provider
it appears that standardjboss.xml is for EJB 2 only, yes?
And, as far as I can tell, for EJB3 I can do:
Annotate my MDBs
or
Use ejb-jar.xml
or
combo annotation/ejb-jar.xml
problem is, I have 200+ MDBs that I want to apply the SAME setting for each.
ie: I want to set the jca inflow config they use, which rar they use, define them to default to Queues, change the DLQ to go to the same place.
Is there any place I can set new 'defaults' for the activation properties? Or do I need to explicitly name each mdb in ejb-jar.xml / modify annotations
I suppose I might be able to mixin the annotations using aspectj/jbossaop, not sure how I'd an item to the activationConfig array via aop, plus it would make the ability to change those defaults kind of tough for some co-workers.
left no other choice, I suppose I could generate my ejb-jar.xml file by scanning the source tree, but that feels like a throw back to the xdoclet days.
I'd probably change the JBoss source and recompile first I suppose.
Any one have better ideas? Or is there actually a file I can create that I can put defaults in to?
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054602#4054602
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4054602
18Â years, 10Â months