[JBoss Tools (users)] - Re: Launching JBoss AS 5.0.1 from within Eclipse
by rob.stryker＠jboss.com
When the server is first starting, typically there is no connection at all from JNDI because the server hasn't even started JNDI yet. This is why you get the javax.naming.CommunicationException:
A few seconds later, JNDI is bound, but JMX is not. JNDI responds to the request, and the request responds that, javax.naming.NameNotFoundException: jmx not bound
To be clear, these are not failures. This is the expected flow as the server starts up.
After a while, JMX is bound, and I get the Server mbean and ask if the server is started yet. At first, the response is no.... the server has not completed starting. When the server is completely started, however, the poller responds that the server is started, and the server's state switches to "Started" instead of "Starting".
To be clear, is your complain that these status errors are logged? You havent' said whether or not there's a problem in the view. This is not a bug unless the server's view is not updating the server's status when the server is completely started.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226852#4226852
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226852
17 years, 2 months
[EJB 3.0] - Deployment error using Service beans
by rnicholson10
If I remove a service bean jar from an ears application.xml and redeploy, I get deployment errors for the missing jar file as if it should still exist.
Here's the first ear I deploy:
| <?xml version="1.0" encoding="UTF-8"?>
| <application xmlns="http://java.sun.com/xml/ns/javaee"
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="5"
| xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
| http://java.sun.com/xml/ns/javaee/application_5.xsd">
| <display-name>SPE Test</display-name>
|
| <module>
| <web>
| <web-uri>spe-test.war</web-uri>
| <context-root>/spe-test</context-root>
| </web>
| </module>
|
| <module>
| <ejb>spe-test.jar</ejb>
| </module>
|
| <module>
| <ejb>spe-input.jar</ejb>
| </module>
|
| <library-directory>lib</library-directory>
|
| </application>
|
Then if I remove "spe-input.jar" from the ear file and change this file to reflect this change and redeploy:
| <?xml version="1.0" encoding="UTF-8"?>
| <application xmlns="http://java.sun.com/xml/ns/javaee"
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="5"
| xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
| http://java.sun.com/xml/ns/javaee/application_5.xsd">
| <display-name>SPE Test</display-name>
|
| <module>
| <web>
| <web-uri>spe-test.war</web-uri>
| <context-root>/spe-test</context-root>
| </web>
| </module>
|
| <module>
| <ejb>spe-test.jar</ejb>
| </module>
|
| <library-directory>lib</library-directory>
|
| </application>
|
I get this error:
| DEPLOYMENTS MISSING DEPENDENCIES:
| Deployment "spe-input:service=inputServiceBean" is missing the following dependencies:
| Dependency "<UNKNOWN spe-input:service=inputServiceBean>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'jboss.j2ee:ear=spe-test.ear,jar=spe-input.jar,name=InputServiceBean,service=EJB3' **")
|
| DEPLOYMENTS IN ERROR:
| Deployment "<UNKNOWN spe-input:service=inputServiceBean>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.j2ee:ear=spe-test.ear,jar=spe-input.jar,name=InputServiceBean,service=EJB3' **
|
Surely the jar I removed from the ear should be undeployed as it no longer exists as part of the ear?
The only way to stop the error is to either restart JBoss or add the jar back into the ear and deploy it again.
I'd be gratefult of any insight into this.
Thanks,
Ross
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226848#4226848
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226848
17 years, 2 months
[Security & JAAS/JBoss] - Re: Regarding the SubjectFactory and SecurityDomainJndiName
by jeff.zhang
The reason is you use mbean to configure datasource, so you should inject the subjectFactory, try this:
add line
| <attribute name="SubjectFactory"><inject bean="JBossSecuritySubjectFactory"/></attribute>
|
see if it works
BTW: if you use *-ds.xml to deploy datasource, you wouldn't see this fails.
anonymous wrote :
| <mbean code="org.jboss.resource.connectionmanager.TxConnectionManager" display-name="Broadvision TX data source: bv_framework.bvdbPool" name="bv.ds:service=LocalTxCM,name=bv_framework.bvdbPool">
| <depends optional-attribute-name="ManagedConnectionPool">bv.ds:service=ManagedConnectionPool,name=bv_framework.BVRuntimeDBPool
| <depends optional-attribute-name="CachedConnectionManager">jboss.jca:service=CachedConnectionManager
| <depends optional-attribute-name="TransactionManagerService">jboss:service=TransactionManager
| bv/bv_framework/dataSource/bvdbPool
| bvdb-password-encrypted
| <depends optional-attribute-name="JaasSecurityManagerService">jboss.security:service=JaasSecurityManager
| true
| true
|
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226847#4226847
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226847
17 years, 2 months
[Performance Tuning] - Physical vs Virtual Memory
by ntnlljboss
Good morning,
i'm configuring JBoss 4.0.2 on Windows Server 2003 and i have a lot of problem concerning the memory managment. On this server are configured 10 VM for JBoss instances with this configuration:
-Xmn1024m -Xms1024m -Xmx1100m -XX:PermSize=512m -XX:MaxPermSize=512m -XX:+UseParallelGC
The server seem to allocate VM reserved XMX memory (1024MB*10) in the virtual memory instead on the physical memory. Only the MaxPermSize space (512*10) seem to be loaded in RAM, indeed, the related JBoss process use only 512MB of system physical memory. This results in an high swap file utilization, very low physical memory usage and in frequent OOME error. The paging usage peak is at 100% and the memory usage is always on 60% of 16GB avalaible.
I'm googling without find anything regarding. What's wrong?
Thanks in advance
Antonello
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226845#4226845
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226845
17 years, 2 months
[JBoss Messaging] - Bridge - Cannot get once and only once working
by rnicholson10
I am using the latest beta release 5.1.0.Beta of AS5. On the previous stable release there was a bug with bridges where a bridge would not correctly deploy on startup of JBoss. This issue no longer exists on the beta.
I have a bridge setup between two different physical machines. Everything works fine once the QualityOfServiceMode in the bridge configuration is set to QOS_AT_MOST_ONCE or QOS_DUPLICATES_OK. If I set QualityOfServiceMode to QOS_ONCE_AND_ONLY_ONCE then I get the following error:
| 2009-04-21 12:59:49,157 ERROR [org.jboss.resource.adapter.jms.inflow.JmsActivation] (WorkManager(2)-2) Unable to reconnect org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@12324c2(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter(a)a5061b destination=queue/speQueueDownstreamIn destinationType=javax.jms.Queue tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5)
| javax.jms.JMSSecurityException: User null is NOT authenticated
| at org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore.authenticate(JBossASSecurityMetadataStore.java:223)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
| at java.lang.reflect.Method.invoke(Unknown Source)
| at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(Unknown Source)
| at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(Unknown Source)
| at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(Unknown Source)
| at com.sun.jmx.mbeanserver.PerInterface.invoke(Unknown Source)
| at com.sun.jmx.mbeanserver.MBeanSupport.invoke(Unknown Source)
| at javax.management.StandardMBean.invoke(Unknown Source)
| at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy109.authenticate(Unknown Source)
| at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegateInternal(ServerConnectionFactoryEndpoint.java:233)
| at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegate(ServerConnectionFactoryEndpoint.java:171)
| at org.jboss.jms.server.endpoint.advised.ConnectionFactoryAdvised.org$jboss$jms$server$endpoint$advised$ConnectionFactoryAdvised$createConnectionDelegate$aop(ConnectionFactoryAdvised.java:108)
| at org.jboss.jms.server.endpoint.advised.ConnectionFactoryAdvised.createConnectionDelegate(ConnectionFactoryAdvised.java)
| at org.jboss.jms.wireformat.ConnectionFactoryCreateConnectionDelegateRequest.serverInvoke(ConnectionFactoryCreateConnectionDelegateRequest.java:91)
| at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143)
| at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908)
| at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
| at org.jboss.remoting.Client.invoke(Client.java:1708)
| at org.jboss.remoting.Client.invoke(Client.java:612)
| at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:171)
| at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeTarget(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)
| at org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:81)
| at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect_z_handleCreateConnectionDelegate_8584105.invoke(StateCreationAspect_z_handleCreateConnectionDelegate_8584105.java)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
| at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java)
| at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:205)
| at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:101)
| at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:95)
| at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setupDLQConnection(AbstractDLQHandler.java:137)
| at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setup(AbstractDLQHandler.java:83)
| at org.jboss.resource.adapter.jms.inflow.dlq.JBossMQDLQHandler.setup(JBossMQDLQHandler.java:48)
| at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDLQ(JmsActivation.java:413)
| at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:351)
| at org.jboss.resource.adapter.jms.inflow.JmsActivation.handleFailure(JmsActivation.java:292)
| at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:733)
| at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:205)
| at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260)
| at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
| at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
| at java.lang.Thread.run(Unknown Source)
|
|
This mode worked on the previous release I used 5.0.1.GA.
I have added the following to the "jta" properties in "conf/jbossts-properties.xml":
| <property name="com.arjuna.ats.jta.recovery.XAResourceRecovery.JBMESSAGING1"
| value="com.jboss.jms.server.recovery.MessagingXAResourceRecovery;java:/DefaultJMSProvider"/>
| <property name="com.arjuna.ats.jta.recovery.XAResourceRecovery.JBMESSAGING2"
| value="com.jboss.jms.server.recovery.MessagingXAResourceRecovery;java:/RemoteJMSProvider"/>
|
I thought that this was the only configuration change required for QOS_ONCE_AND_ONLY_ONCE bridging.
Here is one of my bridge configurations:
| <mbean code="org.jboss.jms.server.bridge.BridgeService" name="jboss.messaging:service=Bridge,name=EngineToHandlerBridge" xmbean-dd="xmdesc/Bridge-xmbean.xml">
|
| <depends optional-attribute-name="SourceProviderLoader">jboss.messaging:service=JMSProviderLoader,name=JMSProvider</depends>
| <depends optional-attribute-name="TargetProviderLoader">jboss.messaging:service=JMSProviderLoader,name=RemoteJMSProvider</depends>
|
| <attribute name="SourceDestinationLookup">/queue/speQueueToHandler</attribute>
| <!-- <attribute name="SourceUsername">guest</attribute>
| <attribute name="SourcePassword">guest</attribute> -->
| <attribute name="TargetDestinationLookup">/queue/speQueueFromEngine</attribute>
| <!-- <attribute name="TargetUsername">guest</attribute>
| <attribute name="TargetPassword">guest</attribute> -->
| <attribute name="QualityOfServiceMode">2</attribute>
| <attribute name="MaxBatchSize">1</attribute>
| <attribute name="MaxBatchTime">-1</attribute>
| <attribute name="FailureRetryInterval">5000</attribute>
| <attribute name="MaxRetries">-1</attribute>
| <attribute name="AddMessageIDInHeader">false</attribute>
| </mbean>
|
|
Is there anything else required for a bridge of this type in the new release? I'm stumped as to how to get this to work.
Thanks,
Ross.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226840#4226840
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226840
17 years, 2 months
[EJB 3.0] - Re: NullPointerException in JavaEEComponentHelper with JBoss
by japase
Hi again,
I have now recreated the problem with a somewhat smaller application and the previously mentioned version of JBoss. The server.log file and console output are attached, as before, to the JIRA 1751 (japase.zip).
Content of the application.xml file:
| <?xml version="1.0" encoding="UTF-8"?>
| <!DOCTYPE application PUBLIC '-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN' 'http://java.sun.com/dtd/application_1_3.dtd'>
| <application>
| <display-name>IFS Connect</display-name>
| <description>IFS Connect</description>
| <module>
| <ejb>applicationsupport-ejb.jar</ejb>
| </module>
| <module>
| <ejb>connectadministration-ejb.jar</ejb>
| </module>
| <module>
| <ejb>connectdevelopment-ejb.jar</ejb>
| </module>
| <module>
| <ejb>connectruntimeservices-ejb.jar</ejb>
| </module>
| <module>
| <ejb>connectsenders-ejb.jar</ejb>
| </module>
| <module>
| <ejb>connecttestorder-ejb.jar</ejb>
| </module>
| <module>
| <ejb>connectivityservices-ejb.jar</ejb>
| </module>
| <module>
| <web>
| <web-uri>ifsclientgateway.war</web-uri>
| <context-root>/fndcn</context-root>
| </web>
| </module>
| </application>
|
Content of the ear file:
anonymous wrote :
| H:\>jar -tf E:\ifs_home_WS\jboss-5.1.0.CR1\server\dev\deploy\ifsapp.ear
| META-INF/
| META-INF/MANIFEST.MF
| META-INF/jboss-app.xml
| META-INF/orion-application.xml
| ifs-fnd-j2ee.jar
| ifs-fnd-common.jar
| ifs-fnd-connect.jar
| ifsclientgateway.war
| applicationsupport-ejb.jar
| fndbas-enumerations.jar
| META-INF/application.xml
| documentlifecycle.jar
| batchqueuemethod.jar
| batchqueue.jar
| batchschedulemethodparameter.jar
| batchschedulemethod.jar
| queryhintview.jar
| reportlayout.jar
| reportlayoutdefinition.jar
| reportresultgenconfig.jar
| reportschema.jar
| reportdefinition.jar
| reportfontdefinition.jar
| installedmodule.jar
| batchschedulechain.jar
| batchschedulechainstep.jar
| batchschedulechainpar.jar
| batchscheduleparameter.jar
| batchschedule.jar
| languagefontmapping.jar
| termusageidentifier.jar
| termusagedefinition.jar
| termtranslateddefinition.jar
| termtranslatedname.jar
| languagecode.jar
| termalertindicator.jar
| termdomain.jar
| fnduser.jar
| languagemodule.jar
| termowner.jar
| termstoplist.jar
| term.jar
| entitystate.jar
| filter.jar
| storageattribute.jar
| storagepackage.jar
| tableindex.jar
| storageobject.jar
| logicalunit.jar
| plsqlpackage.jar
| plsqlparameter.jar
| plsqlmethod.jar
| serverpackage.jar
| view.jar
| validationobject.jar
| handlermethod.jar
| handler.jar
| clientplugin.jar
| widget.jar
| feature.jar
| clientpackage.jar
| entitypackage.jar
| j2eeapplication.jar
| module.jar
| activitypackage.jar
| activity.jar
| modelimportlog.jar
| stereotype.jar
| entityattribute.jar
| entityassociation.jar
| searchdomain.jar
| entity.jar
| connecttestorder-ejb.jar
| messagearchivesearch.jar
| messagearchive.jar
| messagemedia.jar
| messagequeue.jar
| recurrenceagenda.jar
| recurrencepattern.jar
| target.jar
| applicationmessage.jar
| configparameterinstance.jar
| configparameterarea.jar
| fndsessionruntime.jar
| connectsenders-ejb.jar
| ftp.jar
| activation.jar
| mail.jar
| xercesImpl.jar
| jsch-0.1.31.jar
| routeaddress.jar
| routecondition.jar
| connectruntimeservices-ejb.jar
| messageclass.jar
| inmessage.jar
| outmessageline.jar
| outmessage.jar
| connectivityservices-ejb.jar
| connectadministration-ejb.jar
| connectdevelopment-ejb.jar
|
Log level is set to TRACE for EJB3 in jboss-log4j.xml:
| <category name="org.jboss.ejb3">
| <priority value="TRACE"/>
| </category>
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226838#4226838
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226838
17 years, 2 months