JBossDeveloper

Embeddability of JBM is one of our major tasks for JBM 2.0.

JBM 2.0 is just a simple set of POJOs with a very small set of dependencies. The idea is that it can be embedded in any third party program that requires messaging, and of special interest to OEMs,

JBM 1.4 was never designed to be embeddable, but you may be able to get there with enough hacking. Good luck! And tell me how it goes... :)

"pete.muir@jboss.org" wrote:

I only saw this when running with Java 6. http://in.relation.to/Bloggers/EmbeddedJBossUpdate.

The problem is related to the StateCreationAspect not being applied when the jms activation connection is created. Its in the aop config that is loaded, but seems to be applied too late.

Hi Pete
Do the messaging queues and topics still get deployed ok in JBAS5 embedded, or are they bust as well? I realise that they won't be usable since the JMS server won't start, but it would be useful if they could be deployed so they are at least accessible from a management perspective.

Thanks

This will require more time debugging this...

I have taken the action of looking into this, and there is something going on with aop.


Our aspects are being deployed, but for some reason the PerVM aspect we use is not being applied here.


I have added a trace to our code, and I could see where the connection is created:

[testng] 2008-01-09 14:45:02,131 13889 INFO [org.jboss.jms.delegate.ConnectionFactoryDelegate] @WorkManager(1)-2 connectionDelegate created = ConnectionDelegate[31261706, ID=g-iasbc8bf-1-aqkbc8bf-ssqw43-110j3, SID=0] state = null
 [testng] java.lang.Exception: trace
 [testng] at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:197)
 [testng] at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java)
 [testng] at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:205)
 [testng] at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:101)
 [testng] at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:95)
 [testng] at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setupDLQConnection(AbstractDLQHandler.java:137)
 [testng] at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setup(AbstractDLQHandler.java:83)
 [testng] at org.jboss.resource.adapter.jms.inflow.dlq.JBossMQDLQHandler.setup(JBossMQDLQHandler.java:48)
 [testng] at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDLQ(JmsActivation.java:401)
 [testng] at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:339)
 [testng] at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:692)
 [testng] at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
 [testng] at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260)
 [testng] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
 [testng] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
 [testng] at java.lang.Thread.run(Thread.java:595)
 [testng] 2008-01-09 14:45:02,151 13909 WARN [org.jboss.resource.adapter.jms.inflow.JmsActivation] @WorkManager(1)-2 Failure in jms activation org.jboss.resour

I am looking at it. Has this ever worked with Embedded?

I have built https://svn.jboss.org/repos/jbossas/branches/EMBEDDED_JBOSS_BETA3
but am unsure what to do to to reproduce the error?

Running the tests, I get quite a lot of errors like

Testsuite: org.jboss.embedded.test.bootstrap.unit.BootstrapTestCase
Tests run: 0, Failures: 0, Errors: 1, Time elapsed: 9.141 sec
------------- Standard Output ---------------
WARN 10-01 14:06:58,937 (UnifiedLoaderRepository3.java:addClassLoader:713) -Tried to add non-URLClassLoader. Ignored
WARN 10-01 14:07:00,734 (TxControl.java:<clinit>:302) -[com.arjuna.ats.arjuna.coordinator.TxControl_1] - Name of XA node not defined. Using a21061b:8ab:47862684:0
WARN 10-01 14:07:01,812 (AspectManagerService.java:baseAop:228) -Could not find base-aspects.xml file in the resources of sun.misc.Launcher$AppClassLoader@92e78c
ERROR 10-01 14:07:05,890 (AbstractController.java:incrementState:755) -Error installing to Configured: name=jboss.messaging:service=ServerPeer state=Instantiated mode=Manual requiredState=Configured
org.jboss.deployment.DeploymentException: No Attribute found with name: UseXAForMessagePull for jboss.messaging:service=ServerPeer, attributes: [ProviderVersion, DefaultExpiryQueue, DefaultMaxDeliveryAttempts, JMSProviderName, FailoverCompleteTimeout, JMSVersion, DefaultRedeliveryDelay, StrictTck, Destinations, SecurityDomain, FailoverStartTimeout, MessageStatistics, RecoverDeliveriesTimeout, DefaultPreserveOrdering, DefaultSecurityConfig, DefaultMessageCounterHistoryDayLimit, DefaultDLQ, SuckerPassword, Instance, DefaultTopicJNDIContext, ServerPeerID, ClusterPullConnectionFactoryName, PostOffice, PersistenceManager, MessageCounters, ProviderMajorVersion, JMSMajorVersion, DefaultQueueJNDIContext, JMSUserManager, JMSMinorVersion, SupportsFailover, MessageCounterSamplePeriod, ProviderMinorVersion]
 at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:130)
...

I missed the first two pages of this thread... I will read those

This has been fixed. Seam will need to update the embedded distribution and to enable the two lines commented with "Enable following embedded upgrade" in bootstrap/deployers/aspect-deployer-beans.xml.

http://jira.jboss.com/jira/browse/EMB-5