[Installation, Configuration & DEPLOYMENT] - Jboss4.2.2.GA and Mysql with DefaultDS
by suuuper
Hi to all,
I configure the jboss to use Mysql how DefaultDS.
I read this page:
http://wiki.jboss.org/wiki/Wiki.jsp?page=SetUpMysqlAsDefaultDS
But when i start the default Instance, I have the following error:
| 14:35:57,757 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
| 14:35:57,993 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=MySqlDS' to JNDI name 'java:MySqlDS'
| 14:35:58,036 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
| 14:35:58,198 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.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=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
| 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: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
|
|
| 14:35:59,163 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8081
| 14:35:59,229 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-18009
| 14:35:59,251 INFO [Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)] Started in 49s:997ms
|
Any ideas?
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4107058#4107058
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4107058
18 years, 8 months
[JBossWS] - Re: JAX-WS from Sessions Bean fails due to missing org/jboss
by dkane
"ejb3workshop" wrote :
| A search in the forums and the web makes suggestions to include the jboss-common-clients.jar in the classpath. I tried added this jar to the /server/default/lib folder as well as include it within the EAR / application.xml, of which neiter worked.
|
"ejb3workshop" wrote : java.lang.NoClassDefFoundError: org/jboss/logging/Logger
| at javax.xml.soap.FactoryLoader.(FactoryLoader.java:47)
| at javax.xml.soap.SOAPFactory.newInstance(SOAPFactory.java:64)
|
I have the same problem, although web-service is being invoked remotely.
Adding jboss-common-client.jar or jbossall-client.jar to JBoss classpath does not help.
Then I tried to put this jar to lib/endorsed, next to jars required for JBossWS on Java 1.6 , and JBoss failed to start at all.
Somehow, endorsed classes does not "see" JBoss classpath ... How to solve this problem ?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4107055#4107055
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4107055
18 years, 8 months
[JBoss Seam] - Re: Seam + Trinidad + Richfaces: IllegalStateException
by fredatwork
Sebastian,
I have a very similar issue:
12:10:48,390 ERROR [[Faces Servlet]] "Servlet.service()" pour la servlet Faces Servlet a généré une exception
| java.lang.IllegalStateException: No page context active
I'm using RichFaces 3.1.2 SP1 and Seam 2.0.0 GA.
I have a simple JSF page with a rich table (<rich:dataTable>) that renders a ListDataModel that has been outjected by a Seam component in the session scope (e.g. list manager) using the @DataModel(scope=ScopeType.PAGE) annotation. The data model component is in the page scope.
Everyhting works until I add a a <rich:datascroller> to the footer of the data table and bind it as an attribute of the list manager (in the session scope). I receive the exception java.lang.IllegalStateException: No page context active.
I believe this is the same bug as discussed in this thread. Does 3.1.2 SP1 fixes JIRA RF-1109 and RF-2083 ?
Fred
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4107052#4107052
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4107052
18 years, 8 months
[EJB/JBoss] - Problem deploying Session Bean
by breako
Hi,
I have a very simpl ear, test.ear which packages up the following:
test.ear
-enterprise.jar
---- AddressDAI
---- AddressDAOImpl
---- // other java files
-enterprise.war
---- // usual web stuff
- meta - inf
---- application.xml
My session bean interface is
| @Remote
| public interface AddressDAO {
| public void createAddress(Address address);
| }
|
My Session bean implementation is:
| @Stateless
| @TransactionManagement(TransactionManagementType.BEAN)
| public class AddressDAOImplBMT implements AddressDAO{
| public void createAddress(Address address) {
| // java code
| }
| }
|
I deploy my .ear. I check the JBoss JMX console to see if I can see my Session bean.
I expect to see it under:
| java:comp namespace of the test.ear/test.war application
|
But I don't.
I see it under:
| Global JNDI Namespace
| +- test (class: org.jnp.interfaces.NamingContext)
| | +- AddressDAOImplBMT (class: org.jnp.interfaces.NamingContext)
|
Consequently I have problems using the Session bean.
If I try to do:
| Object ref = ctx.lookup("java:comp");
| ref = ctx.lookup("test/AddressDAOImplBMT");
| AddressDAO dao = (AddressDAO)PortableRemoteObject.narrow(ref, AddressDAOImplBMT.class);
|
I get a class cast exception,
| java.lang.ClassCastException: Class AddressDAOImplBMT is not a valid remote interface
|
any ideas would be greatly appreciated - thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4107046#4107046
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4107046
18 years, 8 months
[Messaging, JMS & JBossMQ] - Dynamic Listener creation?
by Lajcik
Hello, im building a functionality where a person connects to the server, sends a request. the server then starts some business logic which produces jms messages for him. The user then connects to the sockect and receives that information through a stream from a message listener with a selector.
The socket part is implemented as fllows:
User ----[socket]----> Service Mbean ----[local]----> Stateless Session Bean ----[delegate]----> POJO -----[create]----> JMS Message Listener
My problem is - i cant find a satisfying way to dynamically create and destroy message listeners...
Tried creating message consumers with jmstemplate, but i get no messages :/
| jmsTemplate.execute(new SessionCallback() {
| public Object doInJms(Session session) throws JMSException {
| MessageConsumer mc = session.createConsumer(
| incomingQueue, "id='" + id + "'"
| );
| mc.setMessageListener(node);
| return null;
| }
|
I tried both - keeping the message consumer and suspending a thread on wait() inside the session callback - to no avail. Im running out of ideas and hits in google :)
I chose this approach because this way the jms queue can manage the message lifetime and distribution for me, i only register listeners with an appropriate selector... Is this a good approach or should i message driven pojo and manage incoming messages (their distribution and lifetime) manually? (which seems tedious and error-prone)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4107039#4107039
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4107039
18 years, 8 months