[JBoss Seam] - Re: DOCTYPE definition on *pages.xml performance warning/imp
by lowecg2004
I added some basic timing code to Pages.class for the following methods. Both call getDocumentRoot():
| package org.jboss.seam.core;
|
| ...
|
| public class Pages {
| ...
|
| private void parse(InputStream stream)
| {
| long t1 = System.nanoTime();
|
| ...
|
| long t2 = System.nanoTime();
|
| System.out.println("pages1: handling = " + (t2 - t1) / 1000000);
| }
|
| private void parse(InputStream stream, String viewId)
| {
| long t1 = System.nanoTime();
| ...
| long t2 = System.nanoTime();
|
| System.out.println("pages2: handling = " + (t2 - t1) / 1000000);
| }
|
| ...
| }
My test is to define 2 simple pages that had a linked to each other. So clicking the link should produce test output for request and response phases and hopefully show the cost of parsing for a page transition.
Test 1: DOCTYPE was correct for verion 1.3 for pages.xml and test.page.xml - average time spent parsing and processing *pages.xml for a request/response cycle was 48ms.
Test 2: DOCTYPE was set to 1.2 for for pages.xml and test.page.xml; running CVS Seam 1.3 - average time spent parsing and processing *pages.xml for a request/response cycle was 958ms.
More detailed data is below:
Test 1: DOCTYPE was correct for verion 1.3
t1 -> t2
pages1: handling = 11
pages2: handling = 12
pages2: handling = 8
pages1: handling = 9
pages2: handling = 7
total: 47ms
t2 -> t1
pages1: handling = 9
pages2: handling = 10
pages2: handling = 15
pages1: handling = 11
pages2: handling = 9
total: 54ms
t1 -> t2
pages1: handling = 9
pages2: handling = 8
pages2: handling = 9
pages1: handling = 15
pages2: handling = 10
total: 51ms
t2 -> t1
pages1: handling = 9
pages2: handling = 12
pages2: handling = 7
pages1: handling = 9
pages2: handling = 5
total: 42ms
----------------------
Test 2: DOCTYPE was incorrect for verion 1.3
t1 -> t2
pages1: handling = 415
pages2: handling = 138
pages2: handling = 141
pages1: handling = 145
pages2: handling = 140
total: 976ms
t2 -> t1
pages1: handling = 366
pages2: handling = 129
pages2: handling = 129
pages1: handling = 132
pages2: handling = 129
total: 885ms
t1 -> t2
pages1: handling = 405
pages2: handling = 149
pages2: handling = 142
pages1: handling = 145
pages2: handling = 143
total: 984ms
t2 -> t1
pages1: handling = 411
pages2: handling = 144
pages2: handling = 141
pages1: handling = 146
pages2: handling = 146
total: 988ms
Test was done an a dual Xeon 2.8Ghz/2Gb RAM. App was warmed by navigating between test pages 10 times before taking timings.
[ServerInfo] Java version: 1.6.0_01,Sun Microsystems Inc.
[ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.6.0_01-b06,Sun Microsystems Inc.
[ServerInfo] OS-System: Windows XP 5.1,x86
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050463#4050463
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4050463
18Â years, 10Â months
[JBoss Portal] - Re: from hibernate to sybase
by Sonal K.
These are the errors I m getting when i'm starting my Jboss
16:08:54,773 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
--- Incompletely deployed packages ---
org.jboss.deployment.DeploymentInfo@63b6fff6 { url=file:/D:/jboss-portal-
/server/default/deploy/portal-sybase-ds.xml }
deployer: org.jboss.deployment.XSLSubDeployer@392814
status: null
state: FAILED
watch: file:/D:/jboss-portal-2.6-CR2/server/default/deploy/portal-sybas
l
altDD: null
lastDeployed: 1180694322288
lastModified: 1180694322273
mbeans:
--- MBeans waiting for other MBeans ---
ObjectName: portal:name=User,service=Interceptor,type=Server
State: CONFIGURED
I Depend On:
portal:service=Module,type=IdentityServiceController
Depends On Me:
portal:service=InterceptorStackFactory,type=Server
ObjectName: portal:service=InterceptorStackFactory,type=Server
State: CONFIGURED
I Depend On:
portal:name=SessionLock,service=Interceptor,type=Server
portal:name=Transaction,service=Interceptor,type=Server
portal:name=UserEvent,service=Interceptor,type=Server
portal:name=SessionInvalidator,service=Interceptor,type=Server
portal:name=User,service=Interceptor,type=Server
portal:name=Locale,service=Interceptor,type=Server
portal:name=ContentType,service=Interceptor,type=Server
ObjectName: portal:service=Hibernate
State: CONFIGURED
I Depend On:
jboss.jca:name=PortalDS,service=DataSourceBinding
Depends On Me:
portal:service=Module,type=IdentityServiceController
ObjectName: portal:service=Hibernate,type=Instance
State: CONFIGURED
I Depend On:
jboss.jca:name=PortalDS,service=DataSourceBinding
Depends On Me:
portal:container=Instance
ObjectName: portal:service=Hibernate,type=PortalObject
State: CONFIGURED
I Depend On:
jboss.jca:name=PortalDS,service=DataSourceBinding
Depends On Me:
portal:container=PortalObject
ObjectName: portal:service=Hibernate,type=Portlet
State: CONFIGURED
I Depend On:
jboss.jca:name=PortalDS,service=DataSourceBinding
Depends On Me:
portal:service=PersistenceManager,type=Producer
ObjectName: portal:service=Module,type=IdentityServiceController
State: CONFIGURED
I Depend On:
portal:service=Hibernate
portal:service=IdentityEventManager
Depends On Me:
portal:name=User,service=Interceptor,type=Server
portal:service=Module,type=Mail
portal:service=CustomizationManager
ObjectName: portal:service=Module,type=Mail
State: CONFIGURED
I Depend On:
jboss:service=Mail
portal:service=Module,type=IdentityServiceController
ObjectName: portal:container=Instance
State: CONFIGURED
I Depend On:
portal:service=Hibernate,type=Instance
portal:service=InterceptorStackFactory,type=Instance
portal:service=PortletInvoker,type=Federating
portal:service=PortalAuthorizationManagerFactory
portal:service=AuthorizationDomainRegistry
Depends On Me:
portal:container=PortalObject
portal:service=CustomizationManager
portal:service=ContentRenderer,type=portlet
portal:service=Controller
portal:deployer=PortalWebApp
portal:deploymentFactory=PortletApp
ObjectName: portal:container=PortalObject
State: CONFIGURED
I Depend On:
portal:service=Hibernate,type=PortalObject
portal:service=PortalAuthorizationManagerFactory
portal:service=AuthorizationDomainRegistry
portal:container=Instance
portal:service=ContentProviderRegistry
Depends On Me:
portal:service=CustomizationManager
portal:commandFactory=DefaultPortal
portal:commandFactory=PortalObject
portal:service=ResponseHandler,type=Ajax
portal:service=Controller
portal:deployer=PortalWebApp
portal:deploymentFactory=Object
ObjectName: portal:service=CustomizationManager
State: CONFIGURED
I Depend On:
portal:service=PortalAuthorizationManagerFactory
portal:container=Instance
portal:container=PortalObject
portal:service=Module,type=IdentityServiceController
Depends On Me:
portal:service=ContentRenderer,type=portlet
portal:service=IdentityDashboardBridge
portal:service=Controller
ObjectName: portal:service=ContentRenderer,type=portlet
State: CONFIGURED
I Depend On:
portal:service=ContentProviderRegistry
portal:service=CustomizationManager
portal:container=Instance
ObjectName: portal:service=IdentityDashboardBridge
State: CONFIGURED
I Depend On:
portal:service=IdentityEventManager
portal:service=CustomizationManager
ObjectName: portal:commandFactory=DefaultPortal
State: CONFIGURED
I Depend On:
portal:commandFactory=Delegating
portal:container=PortalObject
Depends On Me:
portal:service=Controller
ObjectName: portal:commandFactory=PortalObject
State: CONFIGURED
I Depend On:
portal:container=PortalObject
Depends On Me:
portal:commandFactory=Delegate,path=portal
ObjectName: portal:commandFactory=Delegate,path=portal
State: CONFIGURED
I Depend On:
portal:commandFactory=Delegating
portal:commandFactory=PortalObject
ObjectName: portal:service=PersistenceManager,type=Producer
State: CONFIGURED
I Depend On:
portal:service=Hibernate,type=Portlet
Depends On Me:
portal:service=PortletInvoker,type=Producer
ObjectName: portal:service=PortletInvoker,type=Producer
State: CONFIGURED
I Depend On:
portal:service=PortletInvoker,type=Container
portal:service=PersistenceManager,type=Producer
portal:service=StateManagementPolicy,type=Producer
portal:service=StateConverter,type=Producer
Depends On Me:
portal:id=local,service=PortletInvokerRegistration
ObjectName: portal:id=local,service=PortletInvokerRegistration
State: CONFIGURED
I Depend On:
portal:service=PortletInvoker,type=Producer
portal:service=PortletInvoker,type=Federating
Depends On Me:
portal:deploymentFactory=PortletApp
ObjectName: portal:service=ResponseHandler,type=Ajax
State: CONFIGURED
I Depend On:
portal:service=PageService
portal:container=PortalObject
Depends On Me:
portal:service=ResponseHandler,type=Selector
ObjectName: portal:service=ResponseHandler,type=Selector
State: CONFIGURED
I Depend On:
portal:service=ResponseHandler,type=Classic
portal:service=ResponseHandler,type=Ajax
Depends On Me:
portal:service=Controller
ObjectName: portal:service=Controller
State: CONFIGURED
I Depend On:
portal:service=PageService
portal:commandFactory=DefaultPortal
portal:urlFactory=Delegating
portal:service=InterceptorStackFactory,type=Command
portal:container=PortalObject
portal:container=Instance
portal:service=PortalAuthorizationManagerFactory
portal:service=CustomizationManager
portal:service=ContentProviderRegistry
portal:service=ResponseHandler,type=Selector
Depends On Me:
portal:service=ControllerFactory
ObjectName: portal:service=ControllerFactory
State: CONFIGURED
I Depend On:
portal:service=Controller
ObjectName: portal:deployer=PortalWebApp
State: CONFIGURED
I Depend On:
jboss.system:service=MainDeployer
portal:container=PortalObject
portal:container=Instance
portal:service=Server
Depends On Me:
portal:deploymentFactory=Object
portal:deploymentFactory=PortletApp
portal:deploymentFactory=Layout
portal:deploymentFactory=LayoutFeatures
portal:deploymentFactory=Theme
portal:deployer=Adapter
ObjectName: portal:deploymentFactory=Object
State: CONFIGURED
I Depend On:
portal:deployer=PortalWebApp
portal:container=PortalObject
portal:service=ContentProviderRegistry
portal:service=EntityResolver
ObjectName: portal:deploymentFactory=PortletApp
State: CONFIGURED
I Depend On:
portal:id=local,service=PortletInvokerRegistration
portal:deployer=PortalWebApp
portal:service=WebAppRegistry
portal:service=ServerConfig
portal:service=PortletSecurityService
portal:container=Instance
portal:service=EntityResolver
ObjectName: portal:deploymentFactory=Layout
State: CONFIGURED
I Depend On:
portal:deployer=PortalWebApp
portal:service=LayoutService
ObjectName: portal:deploymentFactory=LayoutFeatures
State: CONFIGURED
I Depend On:
portal:deployer=PortalWebApp
portal:service=LayoutService
ObjectName: portal:deploymentFactory=Theme
State: CONFIGURED
I Depend On:
portal:deployer=PortalWebApp
portal:service=ThemeService
ObjectName: portal:deployer=Adapter
State: CONFIGURED
I Depend On:
jboss.web:service=WebServer
portal:deployer=PortalWebApp
portal:service=EntityResolver
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.jca:name=PortalDS,service=DataSourceBinding
State: NOTYETINSTALLED
Depends On Me:
portal:service=Hibernate
portal:service=Hibernate,type=Instance
portal:service=Hibernate,type=PortalObject
portal:service=Hibernate,type=Portlet
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050461#4050461
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4050461
18Â years, 10Â months
[JBossWS] - a question
by sashaxiv
i am updating my aplication from ejb 2.1 to ejb3 anf jboss 4.2. I stop using axis in my server aplication and now i am using jbossws with annotations. The webservices works fine, but i need to change the name of the objects generated in the client aplication in order to avoid changing the client code.
For instance:
the login web service from the server code:
............
@WebService(endpointInterface="com.satdatatelecom.satdataweb.model.session.session.SesionEndPointInterface", targetNamespace = "http://localhost/jboss-net/services/Sesion", serviceName = "LoginService")
@Remote(SesionSession.class)
@RemoteBinding(jndiBinding = "/ejb3/EJB3SesionEndPointInterface")
@Stateless
public class SesionSessionBean implements SesionSession {
@PersistenceContext(unitName = GlobalNames.PERSISTENCE_UNIT)
private EntityManager entityManager;
@WebMethod
@WebResult
public LoginVO loginUsuario(String idEmpresa, String loginName, String password, String session) throws EmpresaNotFoundException, UsuarioNotFoundException, PasswordException, SessionException, ConcesionException, ConcesionEmpresaException, RemoteException, com.satdatatelecom.satdataweb.model.session.exceptions.SessionException {
try{
LoginUsuarioAction action = new LoginUsuarioAction(idEmpresa, loginName, password,
session, entityManager);
LogMessages.info("login", "El usuario "+loginName+" realiza login", true);
return action.execute();
}catch (EmpresaNotFoundException e){
throw e;
}catch (UsuarioNotFoundException e){
throw e;
}
}
}
jboss publish the service , but when the client uses axis to create the objects needed as LoginVo, which is returned by the login service, i would wish to change the type forn loginvo to LoginVOWS, because in the past all the client aplication worked with it in its code.
In the Ejb 2.1 sercer aplication i used in LoginVO:
/**
* @jboss-net.xml-schema
* urn = "satdataweb:LoginVOWS"
*/
to change the name type
now, i tried to use @WebMethod(name="loginVOWs) but it only changes the name in the wsdl document :
..................................
...........................
if i wanted the type to be loginVOWs i need to change the wsdl document by myself.
...................
..................................
...........................
What can i do?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050459#4050459
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4050459
18Â years, 10Â months
symLink outside webapp
by Giorgio Ponza
Hello
I am using jboss4.0.5 with tomcat5.5 embedded.
My first step was to deploy a webapp outside the box, and i succeeded.
Now this application should show graphs created by a monitor daemon that
are located OUTSIDE the webapp dir.
Lets say the webapp is in /var/webapps/test/ROOT.war
and the images are in /var/mrtg/
I've created a symlink in the ROOT.war dir, modified the server.xml and
added the attribute allowLinking="true" in the DefaultContext of that
web-app but with no luck.
I've seen in the mail archive someone had the same problem but haven't
seen a solution.
So i would like to know if there is a solution for this problem or
really jboss doesn't allow symlinks.
I know is not a good practice to access content outside the webapp, but
these are only graphs and i cannot install Apache only to serve that
images :D
Thanks in advance
Giorgio Ponza
18Â years, 10Â months
[Clustering/JBoss] - startup takes @ 3+ minutes for one of the clustered instance
by rajeshchande
Hello,
I have 2 JBoss instance in cluster, everything is perfectly running fine.
JBoss Version: 4.0.3SP1
OS: Solaris
While startup one of the instance is taking @ 4 minutes to startup and the other takes @ 1 minute.
Instance 1
| 2007/05/24 11:05:22 | 11:05:22,454 INFO [Server] Server Name: devl-01
| 2007/05/24 11:05:22 | 11:05:22,454 INFO [Server] Server Home Dir: /apps/jboss/4.0.3sp1/server/devl-01
| 2007/05/24 11:05:22 | 11:05:22,455 INFO [Server] Server Home URL: file:/apps/jboss/4.0.3sp1/server/devl-01/
| 2007/05/24 11:05:22 | 11:05:22,455 INFO [Server] Server Temp Dir: /apps/jboss/4.0.3sp1/server/devl-01/tmp
| 2007/05/24 11:05:22 | 11:05:22,456 INFO [Server] Root Deployment Filename: jboss-service.xml
| 2007/05/24 11:05:23 | 11:05:23,096 INFO [ServerInfo] Java version: 1.5.0_01,Sun Microsystems Inc.
| 2007/05/24 11:05:23 | 11:05:23,096 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_01-b08,Sun Microsystems Inc.
| 2007/05/24 11:05:23 | 11:05:23,097 INFO [ServerInfo] OS-System: SunOS 5.10,sparc
| Received a packet PING : ping
| Send a packet PING : ok
| Received a packet PING : ping
| Send a packet PING : ok
| ...
| ...
| ...
| ...for almost 3 minutes..
| ..
| Received a packet PING : ping
| Send a packet PING : ok
|
| 2007/05/24 11:08:44 | 11:08:44,391 INFO [Server] Core system initialized
Instance 2:
| 2007/05/24 11:14:50 | 11:14:50,385 INFO [Server] Server Name: devl-02
| 2007/05/24 11:14:50 | 11:14:50,386 INFO [Server] Server Home Dir: /apps/jboss/4.0.3sp1/server/devl-02
| 2007/05/24 11:14:50 | 11:14:50,387 INFO [Server] Server Home URL: file:/apps/jboss/4.0.3sp1/server/devl-02/
| 2007/05/24 11:14:50 | 11:14:50,388 INFO [Server] Server Temp Dir: /apps/jboss/4.0.3sp1/server/devl-02/tmp
| 2007/05/24 11:14:50 | 11:14:50,390 INFO [Server] Root Deployment Filename: jboss-service.xml
| 2007/05/24 11:14:51 | 11:14:51,761 INFO [ServerInfo] Java version: 1.5.0_06,Sun Microsystems Inc.
| 2007/05/24 11:14:51 | 11:14:51,762 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_06-b05,Sun Microsystems Inc.
| 2007/05/24 11:14:51 | 11:14:51,763 INFO [ServerInfo] OS-System: SunOS 5.10,sparc
| 2007/05/24 11:14:53 | 11:14:53,640 INFO [Server] Core system initialized
|
How can I reduce the startup time required for the first instance?
During this 3 minutes the server is doing a ping..
Any suggestions?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050455#4050455
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4050455
18Â years, 10Â months
