November 2006 - jboss-user - Jboss List Archives

[JNDI/Naming/Network] - problem with finding datasource via JNDI

by ivan_yatskevich

I have a problem! How to obtain datasource from JNDI, when a jar from lib directory is loaded? I have quartz jar and quartz.properties in this jar. In this file I should specify a JNDI url of CMT datasource. I've made a new file postgres-ds.xml and put it in deploy directory. There is a datasource called PostgresDS. But when jboss starts it loads quartz.jar before binding a datasource! So the following exception occures ERROR [JNDIConnectionProvider] Error looking up datasource: PostgresDS not bound | javax.naming.NameNotFoundException: PostgresDS not bound | at org.jnp.server.NamingServer.getBinding(NamingServer.java:529) | at org.jnp.server.NamingServer.getBinding(NamingServer.java:537) | at org.jnp.server.NamingServer.getObject(NamingServer.java:543) | at org.jnp.server.NamingServer.lookup(NamingServer.java:296) | at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625) | at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587) | at javax.naming.InitialContext.lookup(InitialContext.java:351) | at org.quartz.utils.JNDIConnectionProvider.init(JNDIConnectionProvider.java:127) | at org.quartz.utils.JNDIConnectionProvider.<init>(JNDIConnectionProvider.java:103) | at org.quartz.impl.StdSchedulerFactory.instantiate(StdSchedulerFactory.java:742) | at org.quartz.impl.StdSchedulerFactory.getScheduler(StdSchedulerFactory.java:1152) | at org.jboss.resource.adapter.quartz.inflow.QuartzResourceAdapter.start(QuartzResourceAdapter.java:56) | at org.jboss.resource.deployment.RARDeployment.startService(RARDeployment.java:109) | at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) | at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) | at org.jboss.system.ServiceDynamicMBeanSupport.invoke(ServiceDynamicMBeanSupport.java:124) | at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) | at $Proxy0.start(Unknown Source) | at org.jboss.system.ServiceController.start(ServiceController.java:417) | at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy23.start(Unknown Source) | at org.jboss.deployment.SimpleSubDeployerSupport.startService(SimpleSubDeployerSupport.java:345) | at org.jboss.deployment.SimpleSubDeployerSupport.start(SimpleSubDeployerSupport.java:127) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771) | at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy6.deploy(Unknown Source) | | at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) | at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) | at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) | at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) | at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) | at $Proxy0.start(Unknown Source) | at org.jboss.system.ServiceController.start(ServiceController.java:417) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy4.start(Unknown Source) | at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808) | | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:755) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy5.deploy(Unknown Source) | at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) | at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) | at org.jboss.Main.boot(Main.java:200) | at org.jboss.Main$1.run(Main.java:464) | at java.lang.Thread.run(Thread.java:595) | how can I change the order of loading jars and binding names? Or what should I do to make quartz find my datasource? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989781#3989781 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989781

19 years, 5 months

1
0
0 / 0

[EJB 3.0] - Composite primary key from foreign keys

by xmaniac

I'm unable to figure out how to implement this. I have 3 tables in my DB: Team (surrogate pk), Period (surrogate pk) and TeamPeriods (pk composed of both foreign keys). I need to create an entity from the third table so I can then query the Team objects and receive a collection of TeamPeriods (and then Periods if needed). I don't want to create a surrogate key and an index for this table. I've seen the @Embeddable annotation but I'm still unsure on how to apply it in this case. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989780#3989780 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989780

19 years, 5 months

1
0
0 / 0

[Performance Tuning] - Re: Identifying performance bottlenecks

by jshrinivas

Yes. The throughput is less than expected. Let me put it this way: The load driver can load the JBoss machine with as much load as it can handle. So ideally the CPU utilization on JBoss machine should be close to 100% unless there is any bottleneck. In this particular case even if requests are around 2K the throughput is little over 1K. In essence the App Server is not able to handle all the client requests because it is choking somewhere. I have tried increasing the load from 2K to more than 2K and that doesnt makes any difference on CPU utilization/throughput. Thanks, -Shrinivas View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989779#3989779 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989779

19 years, 5 months

1
0
0 / 0

[Installation, Configuration & Deployment] - Re: jboss startup web-console.war deployment errors

by alex.pinkin＠jboss.com

Bug report is at http://jira.jboss.com/jira/browse/JBINSTALL-135 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989778#3989778 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989778

19 years, 5 months

1
0
0 / 0

[Beginners Corner] - Re: Preferred method for JBoss shutdown

by jmillet

Thank you for the reply. CTRL-C work well when running the application in the foreground, however I have had no luck killing the process when it runs as a daemon with kill -s INT %run.sh_pid%. It seems that the shell script will only respond to kill -9 %run.sh_pid%. If I do kill the run.sh script with a kill -9, I still have to kill the initial java process that was spawned, or they remain running indefinetly. Any suggestions on safe killing of JBoss as a daemon? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989777#3989777 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989777

19 years, 5 months

1
0
0 / 0

[JBossWS] - Re: 1.0.4 integration problem with EJB-3RC8

by MmarcoM

Hello, got same problems and found solution it is in this thread http://www.jboss.com/index.html?module=bb&op=viewtopic&t=95953 hth marco View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989776#3989776 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989776

19 years, 5 months

1
0
0 / 0

[JBossWS] - Re: java.lang.NoSuchMethodError: javax.jws.WebService.portNa

by MmarcoM

hi all, i found solution (and i apologize for not being more proactive..) i have downloaded ejb3.0-rc9fd and haveupdated followign files: - ejb3-persistence.jar - jboss-ejb3-client.jar - ejb3.deployer (directory) - jboss-aop-jdk50.deployer (directory) in jbossAS 4.0.4GA. all files above comes with ejb3.0-rc9fd or with microcontainer rc9 hth marco View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989775#3989775 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989775

19 years, 5 months

1
0
0 / 0

[Performance Tuning] - Re: Identifying performance bottlenecks

by otaylor

I think I'm missing something about the situation. You say that you have a limited workload (2000 requests per second are sent), and that you application processes them without error. Why do you then expect 100% (or more) CPU utilization? Is your application falling behind the workload? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989774#3989774 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989774

19 years, 5 months

1
0
0 / 0

[JBossWS] - java.lang.NoSuchMethodError: javax.jws.WebService.portName()

by MmarcoM

hi all, been havign this exception after upgrading jbossws to 1.0.4 i have read similar threads that suggest to replace ejb3 files.... i have downloaded ejb3-rc9, replaced ejb3-persistence.jar and jboss-ejb3-client wherever i could, but i am still getting same exception... i think i am missing something... mayb some jboss-j2ee jars? can anyone help me out? thanks in advance and regards Marco View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989773#3989773 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989773

19 years, 5 months

1
0
0 / 0

[JBoss jBPM] - Re: Roadmap for releasing BPEL support

by alex.guizar＠jboss.com

The project roadmap is published in our issue tracking system. We update it regularly to keep our community informed of the status of the project. Earlier versions of the BPEL distribution up to 1.1.Beta2 were released under an LGPL variant with several major ammendments to fit the licensing terms of the BPEL specification, hence the 'custom' denomination. Future versions will switch to CPL v1.0 because it fits the specification licensing terms better. Please read the JBoss EULA for more details. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989772#3989772 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989772

19 years, 5 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-user November 2006