[Design of JBoss Wiki] - Installing Wiki Error. wikiService
by indyJones
JRE - 1.5
JBoss AS - 4.0.5 GA
JBoss Portal - 2.4.1
EJB - 3.0 RC 8
Trying to install JBoss Wiki...
I get the following error..
|
| 11:11:50,031 INFO [TomcatDeployer] deploy, ctxPath=/wiki, warUrl=.../deploy/wiki.ear/wiki.war/
| 11:11:50,153 ERROR [WikiFileAccessFilter] Couldn't find WikiManagement
| org.jboss.wiki.exceptions.WikiManagementNotFoundException: java.lang.RuntimeException: Error creating MBeanProxy: wiki:service=wikiService
| at org.jboss.wiki.WikiCommon.getWikiManagement(WikiCommon.java:72)
|
|
...and...
|
| 11:11:51,384 INFO [WikiEngine] Loaded wikiPageDictionary: org.jboss.wiki.FileWikiPageDictionary@1289697
| 11:11:51,385 INFO [WikiEngine] Loaded credentialsClass: class org.jboss.wiki.JBossPortalCredentials
| 11:11:51,394 INFO [PortletAppDeployment] These instances have been found in -object.xml, you should put them in the file /home/jboss/JBoss Portal 2.4 - YourEncore/jboss-4.0.5.GA/server/default/./deploy/wiki.ear/wiki.war/WEB-INF/portlet-instances.xml
| 11:11:51,394 INFO [PortletAppDeployment] <?xml version="1.0" encoding="utf-8" standalone="yes"?>
| <deployments>
| <deployment>
| <instance>
| <instance-id>WikiPortletInstance</instance-id>
| <portlet-ref>WikiPortlet</portlet-ref>
| </instance>
| </deployment>
| </deployments>
|
| 11:11:52,052 INFO [EARDeployer] Started J2EE application: file:/home/jboss/JBoss Portal 2.4 - YourEncore/jboss-4.0.5.GA/server/default/deploy/wiki.ear/
| 11:11:52,054 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
|
| --- Packages waiting for a deployer ---
| org.jboss.deployment.DeploymentInfo@7caa2d { url=file:/home/jboss/JBoss Portal 2.4 - YourEncore/jboss-4.0.5.GA/server/default/deploy/wiki.ear/wiki.ejb3 }
| deployer: null
| status: Starting
| state: START_SUBDEPLOYMENTS
| watch: file:/home/jboss/JBoss Portal 2.4 - YourEncore/jboss-4.0.5.GA/server/default/deploy/wiki.ear/wiki.ejb3
| altDD: null
| lastDeployed: 1171296709722
| lastModified: 1171296709000
| mbeans:
|
Any ideas?
Thanks
Indy
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015155#4015155
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4015155
19 years, 1 month
[Design of JBoss Transaction Services] - Transaction Timeout Simulation not working
by juser2007
Hi,
As part of a debugging process, I am trying to enforce Transaction Time out. I am using Jboss-3.2.3 and have changed the following configurations.
The beans are Container managed.
jboss-service.xml - with "TransactionTimeout" attribute set to 45 sec.
<mbean code="org.jboss.tm.TransactionManagerService" name="jboss:service=TransactionManager" xmbean-dd="resource:xmdesc/TransactionManagerService-xmbean.xml">
45
<depends optional-attribute-name="XidFactory">jboss:service=XidFactory
jboss.xml in META-INF -
<ejb-name>TestSessionBean</ejb-name>
<jndi-name>TestService/TestSession</jndi-name>
<exception-on-rollback>true</exception-on-rollback>
true
<method-attributes>
<method-name>testOverriddenTimeoutExpires</method-name>
<transaction-timeout>5</transaction-timeout>
<method-name>testOverriddenTimeoutDoesNotExpire</method-name>
<transaction-timeout>5</transaction-timeout>
</method-attributes>
I have tried to trace the Transaction Log by appending in log4j.xml, but could not find any relevant information.
I have added code to make sure that the processing would take more than a minute, but still haven't been able to simulate the transaction time out.
Please let me know what else is needed to be done.
Thanks for your help.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015135#4015135
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4015135
19 years, 1 month
[Design of POJO Server] - Re: Relating configuration and monitoring
by adrian@jboss.org
"scott.stark(a)jboss.org" wrote : Yes, but I"m not sure what else might need to be updated to support this yet. I believe the existing jmx notification based stuff should map over to an aspect that exposes a ManagedDeployment and its ManagedComponents as the jsr77 mbeans.
I think we should really be doing this on the ManagedObjects?
We already have a type, so once we have the notion of scope in the ManagedObjects
it should be relatively trivial to map them to the jsr77 tree/naming convention?
I think the only issue is whether we enforce that the POJOs/MBeans should implement
the jsr77 classes, e.g. the statistics classes or whether we do some adaption in the jsr77 facade?
I'd favour the latter simply because it allows the implementation to provide
custom extra statistics and seperate the invocation/pooling/caching stats
while still being able to map them to the standard classes for jsr77.
The downside is that it is going to require some knowledge (hard wiring)
of the real implementation in the jsr77 facade to make this work.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015054#4015054
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4015054
19 years, 1 month