[Design of Messaging on JBoss (Messaging/JBoss)] - Re: MBean Servic cannot open jms session
by adrian@jboss.org
The JIRA issues says this is fixed.
But I still see it running in JBoss Head with the new claasloader:
| 2008-01-10 15:48:33,126 ERROR [org.jboss.messaging.core.impl.clusterconnection.ClusterConnectionManager] Failed to start connection info
| java.lang.NullPointerException
| at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:87)
| at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:106)
| at org.jboss.jms.client.delegate.ClientConnectionDelegate$start_N8025343665958530775.invokeNext(ClientConnectionDelegate$start_N8025343665958530775.java)
| at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
| at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:106)
| at org.jboss.jms.client.delegate.ClientConnectionDelegate$start_N8025343665958530775.invokeNext(ClientConnectionDelegate$start_N8025343665958530775.java)
| at org.jboss.jms.client.delegate.ClientConnectionDelegate.start(ClientConnectionDelegate.java)
| at org.jboss.jms.client.JBossConnection.start(JBossConnection.java:121)
| at org.jboss.messaging.core.impl.clusterconnection.ClusterConnectionManager$ConnectionInfo.start(ClusterConnectionManager.java:664)
| at org.jboss.messaging.core.impl.clusterconnection.ClusterConnectionManager.ensureAllConnectionsCreated(ClusterConnectionManager.java:426)
| at org.jboss.messaging.core.impl.clusterconnection.ClusterConnectionManager.notify(ClusterConnectionManager.java:247)
| at org.jboss.messaging.core.impl.DefaultClusterNotifier.sendNotification(DefaultClusterNotifier.java:72)
| at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.putReplicantLocally(MessagingPostOffice.java:1167)
| at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.put(MessagingPostOffice.java:1420)
| at org.jboss.jms.server.connectionfactory.ConnectionFactoryJNDIMapper.registerConnectionFactory(ConnectionFactoryJNDIMapper.java:240)
| at org.jboss.jms.server.connectionfactory.ConnectionFactory.startService(ConnectionFactory.java:201)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:299)
| at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:196)
|
What is the issue with scoping why does it make a difference?
Seems like you (or aop) have a bad assumption related to classloading?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118698#4118698
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118698
18 years, 2 months
[Design of Messaging on JBoss (Messaging/JBoss)] - Re: NPE booting Embedded JBoss from trunk
by kabir.khan@jboss.com
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)
| ...
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118667#4118667
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118667
18 years, 2 months