February 2008 - jboss-dev-forums - Jboss List Archives

[Design of POJO Server] - Re: Datasource Connection Properties using CollectionMetaTyp

by scott.stark＠jboss.org

It turns out the ManagedProperty.setValue call is not validating the input MetaValue against the ManagedProperty MetaType, so if you input the right value it works as the server side ManagedProperty is of the correct type. I'll update the template types anyway. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4127611#4127611 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4127611

18 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: Datasource Connection Properties using CollectionMetaTyp

by scott.stark＠jboss.org

It looks like the xa ds template xa-datasource-properties should also have the wrong type, but those appear to be working. I'll look into why. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4127607#4127607 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4127607

18 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: Datasource Connection Properties using CollectionMetaTyp

by scott.stark＠jboss.org

Oh, yes, let me check that. It will be a problem because you would create the input connection-properties from the template, and the type would be wrong. One of the things we need to fix is that the template info properties are not derived from the management annotations, and therefore have to be duplicated and they get out of sync. The ManagementProperty annotation needs an includeInTemplate flag: http://jira.jboss.com/jira/browse/JBMICROCONT-239 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4127602#4127602 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4127602

18 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: Datasource Connection Properties using CollectionMetaTyp

by bytor99999

When I print out the actual values from the DefaultDS ManagedComponent, I do see it as a Map. So I wonder what I saw in the DeploymentTemplateInfo? Could they be different and cause any problems? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4127593#4127593 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4127593

18 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: Datasource Connection Properties using CollectionMetaTyp

by scott.stark＠jboss.org

I added logging of the untested ManagedPropertys and this shows the following types: | 1763 [main] WARN ProfileServiceUnitTestCase - testAddNoTxDataSource> untested properties: [connectionDestroyedCount, local-transaction, security-domain, maxConnectionsInUseCount, connection-properties, connectionCreatedCount, inUseConnectionCount, metadata, availableConnectionCount, minSize, maxSize, config-property, poolJndiName, connectionCount] | 1763 [main] INFO ProfileServiceUnitTestCase - ManagedProperty{connectionDestroyedCount,connectionDestroyedCount,metaType=SimpleMetaType:java.lang.Integer} | 1763 [main] INFO ProfileServiceUnitTestCase - ManagedProperty{local-transaction,localTransactions,metaType=SimpleMetaType:java.lang.Boolean} | 1763 [main] INFO ProfileServiceUnitTestCase - ManagedProperty{security-domain,securityMetaData,metaType=GenericMetaType:org.jboss.managed.api.ManagedObject} | 1763 [main] INFO ProfileServiceUnitTestCase - ManagedProperty{maxConnectionsInUseCount,maxConnectionsInUseCount,metaType=SimpleMetaType:java.lang.Long} | 1763 [main] INFO ProfileServiceUnitTestCase - ManagedProperty{connection-properties,dataSourceConnectionProperties,metaType=MapCompositeMetaType{java.util.Map}} | 1764 [main] INFO ProfileServiceUnitTestCase - ManagedProperty{connectionCreatedCount,connectionCreatedCount,metaType=SimpleMetaType:java.lang.Integer} | 1764 [main] INFO ProfileServiceUnitTestCase - ManagedProperty{inUseConnectionCount,inUseConnectionCount,metaType=SimpleMetaType:java.lang.Long} | 1764 [main] INFO ProfileServiceUnitTestCase - ManagedProperty{metadata,DBMSMetaData,metaType=MutableCompositeMetaType{org.jboss.resource.metadata.mcf.DBMSMetaData items=[name=typeMapping type=java.lang.String]}} | 1764 [main] INFO ProfileServiceUnitTestCase - ManagedProperty{availableConnectionCount,availableConnectionCount,metaType=SimpleMetaType:java.lang.Long} | 1765 [main] INFO ProfileServiceUnitTestCase - ManagedProperty{minSize,minSize,metaType=SimpleMetaType:java.lang.Integer} | 1765 [main] INFO ProfileServiceUnitTestCase - ManagedProperty{maxSize,maxSize,metaType=SimpleMetaType:java.lang.Integer} | 1765 [main] INFO ProfileServiceUnitTestCase - ManagedProperty{config-property,managedConnectionFactoryProperties,metaType=MapCompositeMetaType{java.util.Map}} | 1765 [main] INFO ProfileServiceUnitTestCase - ManagedProperty{poolJndiName,poolJndiName,metaType=SimpleMetaType:java.lang.String} | 1765 [main] INFO ProfileServiceUnitTestCase - ManagedProperty{connectionCount,connectionCount,metaType=SimpleMetaType:java.lang.Integer} | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4127591#4127591 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4127591

18 years, 2 months

1
0
0 / 0

[Design of Clustering on JBoss (Clusters/JBoss)] - Re: JBAS-4228 Preferred master node for HASingleton

by galder.zamarreno＠jboss.com

"bstansberry(a)jboss.com" wrote : I want it to keep extending HASingletonElectionPolicySimple. That really is the new default, in the sense that a call to isDRMMasterReplica() is basically the same as a HASEPS with a default 0 position. Extending HASEPS lets us have the simple added feature of that class. Fair point. "bstansberry(a)jboss.com" wrote : Yeah, give it an MBean interface. Let people change the preferred master via the JMX console. Changing a string attribute is a lot simple to support via tools vs. having to plug in a new polcy instance. Ok. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4127589#4127589 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4127589

18 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: Datasource Connection Properties using CollectionMetaTyp

by scott.stark＠jboss.org

When I look at the connection-properties its a MapCompositeMetaType: | connection-properties=ManagedProperty{connection-properties,dataSourceConnectionProperties,metaType=MapCompositeMetaType{java.lang.Map}} | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4127585#4127585 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4127585

18 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: Another startup time regression

by dimitris＠jboss.org

The latest 2.0.0.CR7 doesn't seem to offer significat improvement: | 23:14:21,000 INFO [TransactionManagerService] Recovery manager started | 23:14:21,000 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference | 23:14:36,687 INFO [AspectDeployer] Deploying xml into org.jboss.aop.AspectManager | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4127581#4127581 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4127581

18 years, 2 months

1
0
0 / 0

[Design of JBoss Remoting, Unified Invokers] - Problem in jboss integration with minimal deployment integra (Repost)

by nithyaraj

Hi, I have problem in integration of minimal deployement with webservice integration.can u give solution for this? --------------- C:\Documents and Settings\nithyaraj>run -c minimal =============================================================================== JBoss Bootstrap Environment JBOSS_HOME: E:\myjboss\jboss-4.2.2.GA JAVA: E:\JDK1.5\jdk1.5.0_08\bin\java JAVA_OPTS: -Dprogram.name=run.bat -server -Xms128m -Xmx512m -Dsun.rmi.dgc.cli ent.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 CLASSPATH: E:\JDK1.5\jdk1.5.0_08\lib\tools.jar;E:\myjboss\jboss-4.2.2.GA\bin\r un.jar =============================================================================== 17:20:45,406 INFO [Server] Starting JBoss (MX MicroKernel)... 17:20:45,406 INFO [Server] Release ID: JBoss [Trinity] 4.2.2.GA (build: SVNTag= JBoss_4_2_2_GA date=200710221139) 17:20:45,406 INFO [Server] Home Dir: E:\myjboss\jboss-4.2.2.GA 17:20:45,406 INFO [Server] Home URL: file:/E:/myjboss/jboss-4.2.2.GA/ 17:20:45,406 INFO [Server] Patch URL: null 17:20:45,406 INFO [Server] Server Name: minimal 17:20:45,406 INFO [Server] Server Home Dir: E:\myjboss\jboss-4.2.2.GA\server\mi nimal 17:20:45,406 INFO [Server] Server Home URL: file:/E:/myjboss/jboss-4.2.2.GA/ser ver/minimal/ 17:20:45,406 INFO [Server] Server Log Dir: E:\myjboss\jboss-4.2.2.GA\server\min imal\log 17:20:45,406 INFO [Server] Server Temp Dir: E:\myjboss\jboss-4.2.2.GA\server\mi nimal\tmp 17:20:45,406 INFO [Server] Root Deployment Filename: jboss-service.xml 17:20:45,968 INFO [ServerInfo] Java version: 1.5.0_08,Sun Microsystems Inc. 17:20:45,968 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_08-b03 ,Sun Microsystems Inc. 17:20:45,968 INFO [ServerInfo] OS-System: Windows XP 5.1,x86 17:20:47,125 INFO [Server] Core system initialized 17:20:51,250 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resour ce:jboss-log4j.xml 17:20:53,312 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc. 17:20:53,312 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer 17:20:53,687 INFO [TransactionManagerService] Starting recovery manager 17:20:53,843 INFO [TransactionManagerService] Recovery manager started 17:20:53,843 INFO [TransactionManagerService] Binding TransactionManager JNDI R eference 17:20:59,421 INFO [STDOUT] no object for null 17:20:59,421 INFO [STDOUT] no object for null 17:20:59,453 INFO [STDOUT] no object for null 17:20:59,500 INFO [STDOUT] no object for {urn:jboss:bean-deployer}supplyType 17:20:59,546 INFO [STDOUT] no object for {urn:jboss:bean-deployer}dependsType 17:21:02,218 INFO [NativeServerConfig] JBoss Web Services - Native 17:21:02,218 INFO [NativeServerConfig] jbossws-native-2.0.1.SP2 (build=20071021 0837) 17:21:03,687 INFO [Embedded] Catalina naming disabled 17:21:04,015 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java .library.path: E:\JDK1.5\jdk1.5.0_08\bin;.;C:\WINNT\system32;C:\WINNT;C:\WINNT\s ystem32;C:\WINNT;C:\WINNT\System32\Wbem;E:\JDK1.5\jdk1.5.0_08\bin;E:\myjboss\jbo ss-4.2.2.GA\bin;E:\apache-ant-1.7.0\bin; 17:21:04,187 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0 .1-8080 17:21:04,203 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-80 09 17:21:04,203 INFO [Catalina] Initialization processed in 520 ms 17:21:04,203 INFO [StandardService] Starting service jboss.web 17:21:04,218 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.1.GA 17:21:04,359 INFO [Catalina] Server startup in 148 ms 17:21:04,578 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-w eb.deployer/ROOT.war/ 17:21:06,703 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/ http-invoker.sar/invoker.war/ 17:21:07,921 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../deploy/ jbossws.sar/jbossws-context.war/ 17:21:08,390 INFO [RARDeployment] Required license terms exist, view META-INF/r a.xml in .../deploy/jboss-local-jdbc.rar 17:21:09,593 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jb oss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS' 17:21:09,656 ERROR [URLDeploymentScanner] Incomplete Deployment listing: --- MBeans waiting for other MBeans --- ObjectName: jboss.ejb3:service=EJB3Deployer State: CONFIGURED I Depend On: jboss.aop:service=AspectDeployer jboss.ejb:service=EJBDeployer jboss.ejb3:service=JarsIgnoredForScanning Depends On Me: jboss.ws:service=DeployerInterceptorEJB3 ObjectName: jboss.ws:service=DeployerInterceptorEJB21 State: CONFIGURED I Depend On: jboss.ejb:service=EJBDeployer ObjectName: jboss.ws:service=DeployerInterceptorEJB3 State: CONFIGURED I Depend On: jboss.ejb3:service=EJB3Deployer ObjectName: jboss.jdbc:service=metadata,datasource=DefaultDS State: CONFIGURED I Depend On: jboss.jdbc:service=metadata --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- ObjectName: jboss.ejb:service=EJBDeployer State: NOTYETINSTALLED Depends On Me: jboss.ejb3:service=EJB3Deployer jboss.ws:service=DeployerInterceptorEJB21 ObjectName: jboss.jdbc:service=metadata State: NOTYETINSTALLED Depends On Me: jboss.jdbc:service=metadata,datasource=DefaultDS 17:21:09,968 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8 080 17:21:10,000 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009 17:21:10,015 INFO [Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBos s_4_2_2_GA date=200710221139)] Started in 24s:609ms View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125492#4125492 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4125492

18 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: Datasource Connection Properties using CollectionMetaTyp

by bytor99999

In the ProfileServiceUnitTestCase class, it is only testing xa connection properties, but doesn't test NonXA connection properties. I was noticing in the NoTx template DeploymentTemplateInfo noTXinfo = mgtView.getTemplate("NoTxDataSourceTemplate"); that connections properies looked like it is now a CollectionMetaType of CompositeMetaTypes. So a List of Maps. Am I just seeing things, or am I missing something? I am currently coding a test that logs out all the values and types for the DefaultDS ManagedComponent, just to make sure I saw what I thought I saw. :) Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4127576#4127576 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4127576

18 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums February 2008