[JBoss Messaging] - Re: Problems after Migration from WebSphere to JBoss (Broken
by dahm
Hi,
here's the completx remoting-bisocket.xml:
| <mbean code="org.jboss.remoting.transport.Connector" name="jboss.messaging:service=Connector,transport=bisocket"
| display-name="Bisocket Transport Connector">
| <attribute name="Configuration">
| <config>
| <invoker transport="bisocket">
|
| <!--
| There should be no reason to change these parameters - warning! Changing them may stop JBoss Messaging working
| correctly
| -->
| <attribute name="marshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat
| </attribute>
| <attribute name="unmarshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat
| </attribute>
| <attribute name="dataType" isParam="true">jms</attribute>
| <attribute name="socket.check_connection" isParam="true">false</attribute>
| <attribute name="serverBindAddress">${jboss.bind.address}</attribute>
| <attribute name="serverBindPort">14457</attribute>
| <attribute name="clientSocketClass" isParam="true">org.jboss.jms.client.remoting.ClientSocketWrapper
| </attribute>
| <attribute name="serverSocketClass">org.jboss.jms.server.remoting.ServerSocketWrapper
| </attribute>
|
| <attribute name="numberOfCallRetries" isParam="true">1</attribute>
|
| <!--
| Siehe Posting von Alphonse: https://www.spree.de/wbb3/index.php?page=Thread&postID=184&highlight=read...
| -->
| <attribute name="pingFrequency" isParam="true">60000</attribute>
| <attribute name="pingWindowFactor" isParam="true">2</attribute>
| <attribute name="onewayThreadPool">org.jboss.jms.server.remoting.DirectThreadPool
| </attribute>
| <!-- End immutable parameters -->
|
| <attribute name="stopLeaseOnFailure" isParam="true">true</attribute>
|
| <!-- Periodicity of client pings. Server window by default is twice this figure -->
| <attribute name="clientLeasePeriod" isParam="true">10000</attribute>
| <attribute name="validatorPingPeriod" isParam="true">10000</attribute>
| <attribute name="validatorPingTimeout" isParam="true">5000</attribute>
| <attribute name="registerCallbackListener">false</attribute>
|
| <attribute name="timeout" isParam="true">0</attribute>
|
| <!--
| Number of seconds to wait for a connection in the client pool to become free Offenbar nicht mehr in JBoss-Remoting
| 2.5.1: 11:19:50,109 WARN [MicroSocketClientInvoker] numberOfRetries is no longer used <attribute
| name="numberOfRetries" isParam="true">10</attribute>
| -->
|
| <!--
| Max Number of connections in client pool. This should be significantly higher than the max number of
| sessions/consumers you expect
| -->
| <attribute name="JBM_clientMaxPoolSize" isParam="true">200</attribute>
|
| <!-- The maximum time to wait before timing out on trying to write a message to socket for delivery -->
| <attribute name="callbackTimeout">10000</attribute>
|
| <!--
| Use these parameters to specify values for binding and connecting control connections to work with your
| firewall/NAT configuration <attribute name="secondaryBindPort">xyz</attribute> <attribute
| name="secondaryConnectPort">abc</attribute>
| -->
|
| </invoker>
| <handlers>
| <handler subsystem="JMS">org.jboss.jms.server.remoting.JMSServerInvocationHandler
| </handler>
| </handlers>
| </config>
| </attribute>
| </mbean>
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4227009#4227009
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4227009
17 years
[Management, JMX/JBoss] - Re: JBoss 5: MBean depends on EJB3 Staleless Bean according
by ike
"jaikiran" wrote :
| Is that all you see? Is there any more error message or exception stacktrace (earlier maybe) with more details? If there is any, please post the same.
| Check in the jmx-console whether a service with this name does exist.
Just enabled debug log and attached some related below. There is NO exceptions in the log at all.
If I locate the service in the jmx-console and start it manually by invoking Start method it starts and scheduled service starts also. Is there any new configuration parameter, i.e. mbean auto-start?
In log you can see INFO [dmd] (main) DispatcherService created that is printed by my service's create() method, the same must be for start() but it isn't there so it was not called by the server.
| 2009-04-27 18:37:19,015 DEBUG [org.jboss.system.deployers.SARDeployer] (main) <server>
| <mbean code='com.m1.aloe.dm.jmx.DispatcherService' name='jboss.aloe:service=DispatcherServiceMBean'>
| <attribute name='TimeInterval'>3000</attribute>
| <attribute name='MaxDownloadSpeed'>20</attribute>
| <depends>jboss.j2ee:ear=dm.ear,jar=com.m1.aloe.dm-ejb.jar,name=aloe/com.m1.aloe.dm.core.DownloadMgr,service=EJB3</depends>
| </mbean>
| </server>
|
| 2009-04-27 18:37:20,000 DEBUG [org.jboss.system.deployers.SARDeployer] (main) <server>
| <mbean code='org.jboss.varia.scheduler.Scheduler' name='jboss.aloe:service=AloeDispatcherScheduler'>
| <attribute name='StartAtStartup'>true</attribute>
| <attribute name='SchedulableClass'>com.m1.aloe.dm.schedulable.DispatcherSchedulable</attribute>
| <attribute name='SchedulableArguments'/>
| <attribute name='SchedulableArgumentTypes'/>
| <attribute name='InitialStartDate'>0</attribute>
| <attribute name='SchedulePeriod'>60000</attribute>
| <attribute name='InitialRepetitions'>-1</attribute>
| <attribute name='FixedRate'>true</attribute>
| <depends>jboss.aloe:service=DispatcherServiceMBean</depends>
| </mbean>
|
| 2009-04-27 18:37:26,531 DEBUG [org.jboss.deployers.structure.spi.helpers.AbstractDeploymentContext] (main) Added component jboss.aloe:service=DispatcherServiceMBean to vfszip:/C:/ProgramFilesNoInstall/jboss-5.0.1.GA/server/default/deploy/dmd-dispather.sar/
| 2009-04-27 18:37:26,531 DEBUG [org.jboss.system.ServiceCreator] (main) About to create bean: jboss.aloe:service=DispatcherServiceMBean with code: com.m1.aloe.dm.jmx.DispatcherService
| 2009-04-27 18:37:26,546 DEBUG [org.jboss.system.ServiceCreator] (main) Created mbean: jboss.aloe:service=DispatcherServiceMBean
| 2009-04-27 18:37:26,546 DEBUG [org.jboss.system.ServiceConfigurator] (main) TimeInterval set to 3000 in jboss.aloe:service=DispatcherServiceMBean
| 2009-04-27 18:37:26,546 DEBUG [org.jboss.system.ServiceConfigurator] (main) MaxDownloadSpeed set to 20.0 in jboss.aloe:service=DispatcherServiceMBean
| 2009-04-27 18:37:26,546 DEBUG [org.jboss.system.ServiceController] (main) Creating service jboss.aloe:service=DispatcherServiceMBean
| 2009-04-27 18:37:26,546 DEBUG [org.jboss.system.ServiceController] (main) Waiting in create of jboss.aloe:service=DispatcherServiceMBean on jboss.j2ee:ear=dm.ear,jar=com.m1.aloe.dm-ejb.jar,name=aloe/com.m1.aloe.dm.core.DownloadMgr,service=EJB3
| 2009-04-27 18:37:26,546 DEBUG [org.jboss.system.ServiceController] (main) starting service jboss.aloe:service=DispatcherServiceMBean
| 2009-04-27 18:37:26,546 DEBUG [org.jboss.system.ServiceController] (main) Waiting in start of jboss.aloe:service=DispatcherServiceMBean on
|
| 2009-04-27 18:37:31,234 DEBUG [org.jboss.system.ServiceCreator] (main) About to create bean: jboss.aloe:service=AloeDispatcherScheduler with code: org.jboss.varia.scheduler.Scheduler
| 2009-04-27 18:37:31,281 DEBUG [org.jboss.system.ServiceCreator] (main) Created mbean: jboss.aloe:service=AloeDispatcherScheduler
| 2009-04-27 18:37:31,281 DEBUG [org.jboss.system.ServiceConfigurator] (main) StartAtStartup set to true in jboss.aloe:service=AloeDispatcherScheduler
| 2009-04-27 18:37:31,281 DEBUG [org.jboss.system.ServiceConfigurator] (main) SchedulableClass set to com.m1.aloe.dm.schedulable.DispatcherSchedulable in jboss.aloe:service=AloeDispatcherScheduler
| 2009-04-27 18:37:31,281 DEBUG [org.jboss.system.ServiceConfigurator] (main) InitialStartDate set to 0 in jboss.aloe:service=AloeDispatcherScheduler
| 2009-04-27 18:37:31,296 DEBUG [org.jboss.varia.scheduler.Scheduler] (main) Initial Start Date is set to: Thu Jan 01 03:00:00 MSK 1970
| 2009-04-27 18:37:31,296 DEBUG [org.jboss.system.ServiceConfigurator] (main) SchedulePeriod set to 60000 in jboss.aloe:service=AloeDispatcherScheduler
| 2009-04-27 18:37:31,296 DEBUG [org.jboss.system.ServiceConfigurator] (main) InitialRepetitions set to -1 in jboss.aloe:service=AloeDispatcherScheduler
| 2009-04-27 18:37:31,296 DEBUG [org.jboss.system.ServiceConfigurator] (main) FixedRate set to true in jboss.aloe:service=AloeDispatcherScheduler
| 2009-04-27 18:37:31,296 DEBUG [org.jboss.system.ServiceController] (main) Creating service jboss.aloe:service=AloeDispatcherScheduler
| 2009-04-27 18:37:31,296 DEBUG [org.jboss.system.ServiceController] (main) Waiting in create of jboss.aloe:service=AloeDispatcherScheduler on jboss.aloe:service=DispatcherServiceMBean
| 2009-04-27 18:37:31,296 DEBUG [org.jboss.system.ServiceController] (main) starting service jboss.aloe:service=AloeDispatcherScheduler
| 2009-04-27 18:37:31,296 DEBUG [org.jboss.system.ServiceController] (main) Waiting in start of jboss.aloe:service=AloeDispatcherScheduler on
|
| 2009-04-27 18:37:46,828 DEBUG [org.jboss.beans.metadata.plugins.AbstractInjectionValueMetaData] (main) jboss.j2ee:ear=dm.ear,jar=com.m1.aloe.dm-ejb.jar,name=aloe/com.m1.aloe.dm.core.DownloadMgr,service=EJB3: Contextual injection usage (class -> classloader): interface javax.transaction.TransactionManager -> BaseClassLoader@5f3bad{vfsfile:/C:/ProgramFilesNoInstall/jboss-5.0.1.GA/server/default/conf/jboss-service.xml} defined by AbstractPropertyMetaData@db6d37{name=transactionManager value=AbstractInjectionValueMetaData@1df5f59{value=null injectionType=BY_CLASS propertyMetaData=transactionManager}}
| 2009-04-27 18:37:46,843 DEBUG [org.jboss.system.ServiceController] (main) Creating service jboss.aloe:service=DispatcherServiceMBean
| 2009-04-27 18:37:46,843 INFO [org.jboss.ejb3.session.SessionSpecContainer] (main) Starting jboss.j2ee:ear=dm.ear,jar=com.m1.aloe.dm-ejb.jar,name=aloe/com.m1.aloe.dm.core.DownloadMgr,service=EJB3
|
| 2009-04-27 18:37:46,875 DEBUG [org.jboss.system.ServiceController] (main) Waiting in create of jboss.aloe:service=DispatcherServiceMBean on
| 2009-04-27 18:37:46,890 INFO [dmd] (main) DispatcherService created
|
| 2009-04-27 18:37:54,890 ERROR [org.jboss.system.server.profileservice.ProfileServiceBootstrap] (main) Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
|
| DEPLOYMENTS MISSING DEPENDENCIES:
| Deployment "jboss.aloe:service=AloeDispatcherScheduler" is missing the following dependencies:
| Dependency "jboss.aloe:service=DispatcherServiceMBean" (should be in state "Start", but is actually in state "Create")
| Dependency "jboss.aloe:service=DispatcherServiceMBean" (should be in state "Start", but is actually in state "Create")
|
| DEPLOYMENTS IN ERROR:
| Deployment "jboss.aloe:service=DispatcherServiceMBean" is in error due to the following reason(s): Create
|
My mbean is deployed in sar file, both ejb and web service are in separate ear. The same works fine in JBoss 4.2 but failed in 5.0.1.GA's default configuration.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226996#4226996
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226996
17 years
[Performance Tuning] - Re: Physical vs Virtual Memory
by PeterJ
I think this has to do with how Windows allocates memory. When the JVM first comes up it will as for the 1GB or memory for the heap but it will not immediately make use of that memory. Usually what happens is the OS marks that 1GB of memory as "committed" but physically allocates only a fraction of that to the JVM. As the heap fills up, the OS will allocate more memory to the JVM (that is, swap in memory from the swap file). Of course, the JVM will never really use the full 1GB (probably at most round 3/4GB).
One thing you could try is to allocate, say, 2GB of RAM to a virtual machine and do not allocate any paging file within the OS. That should for at least the Windows running in the VM to not play with the pagefile. If the host OS is also Windows, you can try the same trick there. (That should work - I ran my desktop for a while without any pagefile, didn't even notice it until I tried to run too many VMs are ran out of memory.)
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226983#4226983
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226983
17 years