-
1. Re: cannot deploy Entity Beans
adrian.brock Jan 23, 2002 7:47 AM (in response to dporter)You can ignore the message. It is just telling you,
there is a bug in the JMX server.
There is some workaround code in JBoss that
correctly determines whether an attribute is writable.
Now what is the error message when you try to deploy
your beans?
Regards,
Adrian -
2. Re: cannot deploy Entity Beans
dporter Jan 23, 2002 8:53 AM (in response to dporter)I dont get any error messages in the server window itself. I see no reference to my beans at all. What I see is below. Hope that explains it.
Thanks
JBOSS_CLASSPATH=;run.jar;../lib/crimson.jar
jboss.home = C:\JBoss-2.4.4
Using JAAS LoginConfig: file:/C:/JBoss-2.4.4/conf/default/auth.conf
JBoss release: JBoss-2.4.4 CVSTag=JBoss_2_4_4
JBoss version: 2.4.4.2001-12-29 02:04:40 PST
Using configuration "default"
[INFO,root] Started Log4jService, config=file:/C:/JBoss-2.4.4/conf/default/log4j
.properties
[INFO,Info] Java version: 1.3.1_01,Sun Microsystems Inc.
[INFO,Info] Java VM: Java HotSpot(TM) Client VM 1.3.1_01,Sun Microsystems Inc.
[INFO,Info] System: Windows 2000 5.0,x86
[INFO,Shutdown] Shutdown hook added
[INFO,ServiceControl] Initializing 48 MBeans
[INFO,WebService] Initializing
[INFO,WebService] Initialized
[INFO,NamingService] Initializing
[INFO,NamingService] Initialized
[INFO,JNDIView] Initializing
[INFO,JNDIView] Initialized
[INFO,TransactionManagerService] Initializing
[INFO,TransactionManagerService] Initialized
[INFO,ClientUserTransactionService] Initializing
[INFO,ClientUserTransactionService] Initialized
[INFO,JaasSecurityManagerService] Initializing
[INFO,JaasSecurityManagerService] Initialized
[INFO,JdbcProvider] Initializing
[INFO,JdbcProvider] Loaded JDBC-driver:org.hsqldb.jdbcDriver
[INFO,JdbcProvider] Loaded JDBC-driver:oracle.jdbc.driver.OracleDriver
[INFO,JdbcProvider] Initialized
[INFO,HypersonicDatabase] Initializing
[INFO,HypersonicDatabase] Initialized
[INFO,DefaultDS] Initializing
[INFO,DefaultDS] Initialized
[INFO,ThesaurusPool] Initializing
[INFO,ThesaurusPool] Initialized
[INFO,ServerDataCollector] Initializing
[INFO,ServerDataCollector] Initialized
[INFO,ContainerFactory] Initializing
[INFO,ContainerFactory] Initialized
[INFO,JBossMQService] Initializing
[INFO,JBossMQService] Initialized
[INFO,StateManager] Initializing
[INFO,StateManager] Initialized
[INFO,PersistenceManager] Initializing
[INFO,PersistenceManager] Initialized
[INFO,JVMServerILService] Initializing
[INFO,JVMServerILService] Initialized
[INFO,RMIServerILService] Initializing
[INFO,RMIServerILService] Initialized
[INFO,OILServerILService] Initializing
[INFO,OILServerILService] Initialized
[INFO,UILServerILService] Initializing
[INFO,UILServerILService] Initialized
[INFO,TopicManager] Initializing
[INFO,TopicManager] Initialized
[INFO,TopicManager] Initializing
[INFO,TopicManager] Initialized
[INFO,TopicManager] Initializing
[INFO,TopicManager] Initialized
[INFO,QueueManager] Initializing
[INFO,QueueManager] Initialized
[INFO,QueueManager] Initializing
[INFO,QueueManager] Initialized
[INFO,QueueManager] Initializing
[INFO,QueueManager] Initialized
[INFO,QueueManager] Initializing
[INFO,QueueManager] Initialized
[INFO,QueueManager] Initializing
[INFO,QueueManager] Initialized
[INFO,QueueManager] Initializing
[INFO,QueueManager] Initialized
[INFO,QueueManager] Initializing
[INFO,QueueManager] Initialized
[INFO,QueueManager] Initializing
[INFO,QueueManager] Initialized
[INFO,QueueManager] Initializing
[INFO,QueueManager] Initialized
[INFO,QueueManager] Initializing
[INFO,QueueManager] Initialized
[INFO,NamingAlias] Initializing
[INFO,NamingAlias] Initialized
[INFO,NamingAlias] Initializing
[INFO,NamingAlias] Initialized
[INFO,JMSProviderLoader] Initializing
[INFO,JMSProviderLoader] Initialized
[INFO,ServerSessionPoolLoader] Initializing
[INFO,ServerSessionPoolLoader] Initialized
[INFO,J2eeDeployer] Initializing
[INFO,J2eeDeployer] Initialized
[INFO,RARDeployer] Initializing
[INFO,RARDeployer] Initialized
[INFO,ConnectionManagerFactoryLoader] Initializing
[INFO,MinervaNoTransCMFactory] Initialized
[INFO,ConnectionManagerFactoryLoader] Initializing
[INFO,MinervaSharedLocalCMFactory] Initialized
[INFO,ConnectionManagerFactoryLoader] Initializing
[INFO,MinervaXACMFactory] Initialized
[INFO,ConnectionFactoryLoader] Initializing
[INFO,MinervaDS] Initialized
[INFO,ConnectionFactoryLoader] Initializing
[INFO,JmsXA] Initialized
[INFO,AutoDeployer] Initializing
[INFO,AutoDeployer] Initialized
[INFO,JMXAdaptorService] Initializing
[INFO,JMXAdaptorService] Initialized
[INFO,RMIConnectorService] Initializing
[INFO,RMIConnectorService] Initialized
[INFO,MailService] Initializing
[INFO,MailService] Initialized
[INFO,ServiceControl] Initialized 48 services
[INFO,ServiceControl] Starting 48 MBeans
[INFO,WebService] Starting
[INFO,WebService] Started webserver with address: null port: 8083
[INFO,WebService] Codebase set to: http://dporter:8083/
[INFO,WebService] Started
[INFO,NamingService] Starting
[INFO,NamingService] Starting jnp server
[INFO,NamingService] Started jnpPort=1099, rmiPort=0, backlog=50, bindAddress=nu
ll, Client SocketFactory=null, Server SocketFactory=null
[INFO,NamingService] InitialContext Environment:
[INFO,NamingService] key=java.naming.factory.initial, value=org.jnp.interfaces.N
amingContextFactory
[INFO,NamingService] key=java.naming.factory.url.pkgs, value=org.jboss.naming:or
g.jnp.interfaces:org.jboss.naming:org.jnp.interfaces
[INFO,NamingService] Naming started on port 1099
[INFO,NamingService] Started
[INFO,JNDIView] Starting
[INFO,JNDIView] Started
[INFO,TransactionManagerService] Starting
[INFO,TransactionManagerService] Started
[INFO,ClientUserTransactionService] Starting
[INFO,ClientUserTransactionService] Started
[INFO,JaasSecurityManagerService] Starting
[INFO,JaasSecurityManagerService] startService, securityMgrCtxPath=java:/jaas
[INFO,JaasSecurityManagerService] startService, cachePolicyCtxPath=java:/timedCa
cheFactory
[INFO,JaasSecurityManagerService] startService, SecurityProxyFactory=org.jboss.s
ecurity.SubjectSecurityProxyFactory@78f7db
[INFO,JaasSecurityManagerService] Started
[INFO,JdbcProvider] Starting
[INFO,JdbcProvider] Started
[INFO,HypersonicDatabase] Starting
[INFO,Default] Server 1.6 is running
[INFO,Default] Press [Ctrl]+[C] to abort
[INFO,HypersonicDatabase] Database started
[INFO,HypersonicDatabase] Started
[INFO,DefaultDS] Starting
[INFO,DefaultDS] XA Connection pool DefaultDS bound to java:/DefaultDS
[INFO,DefaultDS] Started
[INFO,ThesaurusPool] Starting
[INFO,ThesaurusPool] XA Connection pool ThesaurusPool bound to java:/ThesaurusPool -
3. Re: cannot deploy Entity Beans
adrian.brock Jan 23, 2002 9:08 AM (in response to dporter)If this is the end of the log,
there is something wrong with the ThesaurusPool
you do not get the message
[INFO,Thesaurus] Started
This might be because the database "DefaultDS" isn't
configured correctly.
Can you post the relevant configuration from jboss.jcml?
You can also look in c:\JBoss-2.4.4\log\server.log
for debug messages. The console doesn't display debug
messages.
You'll probably get some better answers on pool
configuration if you post in the database forum.
Regards,
Adrian -
4. Re: cannot deploy Entity Beans
dporter Jan 23, 2002 9:28 AM (in response to dporter)Thanks Adrian.
<!-- ==================================================================== -->
<!-- JDBC -->
<!-- ==================================================================== -->
org.hsqldb.jdbcDriver,oracle.jdbc.driver.OracleDriver
1476
true
default
false
DefaultDS
org.jboss.pool.jdbc.xa.wrapper.XADataSourceImpl
jdbc:hsqldb:hsql://localhost:1476
1200000
sa
10
false
false
false
true
120000
1800000
false
false
1.0
0
ThesaurusPool
org.jboss.pool.jdbc.xa.wrapper.XADataSourceImpl
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(HOST=xxx)(PROTOCOL=xxx)(PORT=xxx))(CONNECT_DATA=(SID=xxx))) 1200000
xxx
10
xxx
false
false
false
true
120000
1800000
false
false
1.0
0 -
5. Re: cannot deploy Entity Beans
adrian.brock Jan 23, 2002 9:58 AM (in response to dporter)Oracle database configuration is "greek" to me :-)
But it looks like you only have a
hypersonic datasource configured (DefaultDS)
But then in the pool you are using an Oracle jdbc
url?
If you search the database forum you might find an
example that is correct configuration.
Also the second MBean DefaultDomain:service=Hypersonic
starts hypersonic as an embedded database. So don't
try to change this to use Oracle :-)
Regards,
Adrian -
6. Re: cannot deploy Entity Beans
dporter Jan 23, 2002 10:13 AM (in response to dporter)Thanks
It's ALL greek to me, not just the database config. Knew I should've stuck to fork-lift driving. I'll take a look at the other posts and see if I can find an example configuration.