[Design of JBoss ESB] - Re: How to store EPRs in the registry?
by tfennelly
I was asking Kurt about this yesterday and he informed me that the requested behavior re EPR lookups from the registry was that the list of returned EPRs would only include services that are currently up and running i.e. services are supposed to register and deregister from the registry as they come up and go down.
If I understand this correctly, this creates a usability issue from the perspective of this ESB Admin Console App. Basically, it will mean that configurations associated with a particular EPR cannot be created while that Service/EPR is down/offline/deregistered.
Is there a way around this e.g. instead of just having a register and deregister, could we also have "online" and "offline" states/steps. So the following service lifecycle events could apply... "register"... "online"... "offline"... "online"... "offline"... etc... "unregister"
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985853#3985853
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985853
19 years, 4 months
[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Application Server Integration Tests
by rachmatowicz@jboss.com
I tried scoping the deployment of jmsra.jar by adding a <loader-repository> element to the jboss.xml file in the jar. It seems to deploy the jar in a scoped fashion:
2006-11-14 11:15:45,806 DEBUG [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/home/rachmatowicz/jm\s-trunk/testsuite/output/lib/jmsra.jar
2006-11-14 11:15:45,806 DEBUG [org.jboss.deployment.MainDeployer] Starting deployment (init step) of package at: file:/home/\rachmatowicz/jms-trunk/testsuite/output/lib/jmsra.jar
2006-11-14 11:15:45,807 DEBUG [org.jboss.deployment.MainDeployer] Copying file:/home/rachmatowicz/jms-trunk/testsuite/output\/lib/jmsra.jar -> /home/rachmatowicz/jms-trunk/build/output/jboss-5.0.0.Beta/server/messaging/tmp/deploy/tmp50978jmsra.jar
2006-11-14 11:15:45,811 DEBUG [org.jboss.ejb3.deployment.EJB3ClientDeployer] accepts jmsra.jar
2006-11-14 11:15:45,866 DEBUG [org.jboss.deployment.MainDeployer] using deployer MBeanProxyExt[jboss.ejb:service=EJBDeployer\]
2006-11-14 11:15:45,866 DEBUG [org.jboss.ejb.EJBDeployer] init, jmsra.jar
2006-11-14 11:15:45,870 DEBUG [org.jboss.ejb.EJBDeployer] looking for nested deployments in : file:/home/rachmatowicz/jms-tr\unk/testsuite/output/lib/jmsra.jar
2006-11-14 11:15:45,872 DEBUG [org.jboss.deployment.DeploymentInfo] createLoaderRepository from config: LoaderRepositoryConf\ig(repositoryName: jboss.messaging:loader=ScopedLoaderRepository, repositoryClassName: org.jboss.mx.loading.HeirarchicalLoad\erRepository3, configParserClassName: org.jboss.mx.loading.HeirarchicalLoaderRepository3ConfigParser, repositoryConfig: java\2ParentDelegation=false)
2006-11-14 11:15:45,872 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.He\irarchicalLoaderRepository3@178655, cl=org.jboss.mx.loading.UnifiedClassLoader3@205df9{ url=file:/home/rachmatowicz/jms-trun\k/build/output/jboss-5.0.0.Beta/server/messaging/tmp/deploy/tmp50978jmsra.jar ,addedOrder=0}
2006-11-14 11:15:45,873 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.He\irarchicalLoaderRepository3@178655, cl=org.jboss.mx.loading.UnifiedClassLoader3@205df9{ url=file:/home/rachmatowicz/jms-trun\k/build/output/jboss-5.0.0.Beta/server/messaging/tmp/deploy/tmp50978jmsra.jar ,addedOrder=0}
2006-11-14 11:15:45,873 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] Adding org.jboss.mx.loading.UnifiedClassLoader\3@205df9{ url=file:/home/rachmatowicz/jms-trunk/build/output/jboss-5.0.0.Beta/server/messaging/tmp/deploy/tmp50978jmsra.jar \,addedOrder=0}
2006-11-14 11:15:45,877 DEBUG [org.jboss.deployment.MainDeployer] found 0 subpackages of file:/home/rachmatowicz/jms-trunk/t\estsuite/output/lib/jmsra.jar
Thus, unless i'm doing something wrong, Messaging is deployed in a scoped fashion, the destinations used in tests are deployed in a scoped fashion, and the jmsra.jar is deployed in a scoped fashion. All scoping using the same loader-repository: ScopedLoaderRepository.
But when the test is run, the same error appears.
11:15:46,279 INFO [EjbModule] Deploying PublisherCMP
11:15:46,428 INFO [EjbModule] Deploying JMSSession
11:15:46,453 INFO [EjbModule] Deploying QueuePublisher
11:15:46,465 INFO [EjbModule] Deploying TopicPublisher
11:15:46,477 INFO [EjbModule] Deploying QueueRec
11:15:46,485 INFO [EjbModule] Deploying TopicAdapter
11:15:47,453 INFO [ProxyFactory] Bound EJB Home 'PublisherCMP' to jndi 'PublisherCMP'
11:15:47,469 INFO [ProxyFactory] Bound EJB Home 'JMSSession' to jndi 'JMSSession'
11:15:47,488 INFO [ProxyFactory] Bound EJB Home 'QueuePublisher' to jndi 'TxPublisher'
11:15:47,496 INFO [ProxyFactory] Bound EJB Home 'TopicPublisher' to jndi 'TxTopicPublisher'
11:15:47,510 INFO [ProxyFactory] Bound EJB Home 'QueueRec' to jndi 'QueueRec'
11:15:48,959 INFO [EJBDeployer] Deployed: file:/home/rachmatowicz/jms-trunk/testsuite/output/lib/jmsra.jar
11:15:49,317 ERROR [ServerThread] failed to process invocation.
java.io.OptionalDataException
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1316)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.receiveObject(JavaSerializationManager.java:1\28)
at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.read(SerializableUnMarshaller.java:66)
at org.jboss.invocation.unified.marshall.InvocationUnMarshaller.read(InvocationUnMarshaller.java:48)
at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:350)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:398)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985841#3985841
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985841
19 years, 4 months