August 2006 - jboss-user - Jboss List Archives

[Persistence, JBoss/CMP, Hibernate, Database] - howto get jdbc connection from PerstenceContext / EntityMana

by fbadt

Given a stateless session bean with an injected PersistenceContext @PersistenceContext() private EntityManager em; How can a new JDBC Connection be retrieved? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967650#3967650 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967650

19 years, 8 months

1
0
0 / 0

[JBoss Getting Started Documentation] - Re: Deploymnet tooks long time

by Ullrich

after a long time i tried again to start my jboss server - and look what happens: the server starts, and dukes bank was depolyed without any error. i dont know what changed the mind of jboss but now i can get on ... =) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967649#3967649 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967649

19 years, 8 months

1
0
0 / 0

[JBoss Seam] - Re: Can I forace a method to be invoked everytime a page is

by jschuetter

problem solved. I used my own seam jboss-seam.jar debug version. It didn't include the faces-config.xml which I was surprised to find in the original jar archive ... Jens View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967647#3967647 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967647

19 years, 8 months

1
0
0 / 0

[J2EE Design Patterns] - Missing Request Parameters in multithreaded application

by johar111

My WebApplication is deployed on JBoss. I am spawning threads from the servlet each of which perform specific tasks. Only one Main thread writes to output stream. Problem is that when this first state output(a form with method=post) is submitted to the same servlet, HttpServletRequest's getParameterNames() method is returning empty enumeration which it should not. The parameters are being shown in Browser title bar and HttpServletRequest's getQueryString() method does return the query string but doing getParameterNames() or getParameter(<param_name>) doesn't yield anything. It's quite wierd. Can someone explain wht's wrong with Jboss? Why it's not populating request parameters? Also doing HttpUtils.getRequestURL(m_request); doesn't work. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967646#3967646 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967646

19 years, 8 months

1
0
0 / 0

[JBossWS] - Problem deploying Web service

by achyutj

Hi, I am facing the following problem while deploying the webservice. 17:11:03,578 INFO [WSDLFilePublisher] WSDL published to: file:/E:/ProgramFiles/jboss-4.0.2/server/default/data/wsd | l/OIM-xell-WS.ear/WebServices.war/FIDMProvisioning.wsdl | 17:11:03,671 ERROR [ServiceDeployer] Cannot startup webservice for: WebServices.war | org.jboss.deployment.DeploymentException: Cannot deploy webservice; - nested throwable: (javax.xml.rpc.JAXRPCExcept | ion: Cannot unmarshal jaxrpc-mapping-file: WEB-INF/FIDMProvisioning_mapping.xml) | at org.jboss.webservice.ServiceDeployer.deployWebservices(ServiceDeployer.java:379) | at org.jboss.webservice.ServiceDeployer.startWebservice(ServiceDeployer.java:233) | at org.jboss.webservice.ServiceDeployer.handleNotification(ServiceDeployer.java:112) | at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:324) | at org.jboss.mx.notification.NotificationListenerProxy.invoke(NotificationListenerProxy.java:138) | at $Proxy30.handleNotification(Unknown Source) | at org.jboss.mx.util.JBossNotificationBroadcasterSupport.handleNotification(JBossNotificationBroadcasterSup | port.java:112) | at org.jboss.mx.util.JBossNotificationBroadcasterSupport.sendNotification(JBossNotificationBroadcasterSuppo | rt.java:95) | at org.jboss.deployment.SubDeployerSupport.emitNotification(SubDeployerSupport.java:238) | at org.jboss.deployment.SubDeployerSupport.start(SubDeployerSupport.java:206) | at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:410) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:956) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738) | at sun.reflect.GeneratedMethodAccessor49.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:324) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:121) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) | at $Proxy8.deploy(Unknown Source) | at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:325) | at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:501) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.ja | va:204) | at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:277) | at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272) | at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222) | at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:324) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) | at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:897) | at $Proxy0.start(Unknown Source) | at org.jboss.system.ServiceController.start(ServiceController.java:418) | at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:324) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) | at $Proxy4.start(Unknown Source) | at org.jboss.deployment.SARDeployer.start(SARDeployer.java:273) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:722) | 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:324) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:121) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) | at $Proxy5.deploy(Unknown Source) | at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:434) | at org.jboss.system.server.ServerImpl.start(ServerImpl.java:315) | at org.jboss.Main.boot(Main.java:195) | at org.jboss.Main$1.run(Main.java:463) | at java.lang.Thread.run(Thread.java:534) | Caused by: javax.xml.rpc.JAXRPCException: Cannot unmarshal jaxrpc-mapping-file: WEB-INF/FIDMProvisioning_mapping.xm | l | at org.jboss.webservice.metadata.WebserviceDescriptionMetaData.getJavaWsdlMapping(WebserviceDescriptionMeta | Data.java:180) | at org.jboss.webservice.AxisService.getServiceDescription(AxisService.java:517) | at org.jboss.webservice.AxisService.deployService(AxisService.java:353) | 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:324) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) | at org.jboss.mx.util.JMXInvocationHandler.invoke(JMXInvocationHandler.java:273) | at $Proxy24.deployService(Unknown Source) | at org.jboss.webservice.ServiceDeployer.deployWebservices(ServiceDeployer.java:373) | ... 80 more | Caused by: org.jboss.xml.binding.JBossXBException: Failed to parse source. | at org.jboss.xml.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:138) | at org.jboss.xml.binding.Unmarshaller.unmarshal(Unmarshaller.java:116) | at org.jboss.webservice.metadata.jaxrpcmapping.JavaWsdlMappingFactory.parse(JavaWsdlMappingFactory.java:63) | | at org.jboss.webservice.metadata.WebserviceDescriptionMetaData.getJavaWsdlMapping(WebserviceDescriptionMeta | Data.java:175) | ... 94 more | Caused by: org.xml.sax.SAXException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'class | -type'. One of '{"http://java.sun.com/xml/ns/j2ee":java-type}' is expected. @ *unknown*[8,22] | at org.jboss.xml.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:231) | at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source) | at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) | at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) | at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown Source) | at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source) | at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source) | at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source) | at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) | at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) | | at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) | at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) | at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) | at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) | at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) | at org.jboss.xml.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:134) | The relevant content of the FIDMProvisioning_mapping.xml file: | <?xml version="1.0" encoding="UTF-8"?> | <java-wsdl-mapping xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.1" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://www.ibm.com/webservices/xsd/j2ee_jaxrpc_mapping_1_1.xsd"> | <package-mapping> | <package-type>com.my.provisioning.ws.server</package-type> | <namespaceURI>http://xmlns.my.com/FIDM/provisioning</namespaceURI> | </package-mapping> | <java-xml-type-mapping id="JavaXMLTypeMapping_1155126326141"> | <class-type>javax.xml.soap.SOAPElement[]</class-type> | <root-type-qname id="RootTypeQname_1155126326141"> | <namespaceURI>http://www.w3.org/2001/XMLSchema</namespaceURI> | <localpart>any</localpart> | </root-type-qname> | <qname-scope>complexType</qname-scope> | </java-xml-type-mapping> | . | . | . | </java-wsdl-mapping> | Based on the error above, it seems that the parsing error is seen while parsing the arraytype class on line 8. But, absed on the xsd for jaxprc mapping file, array types can be specified. Is this a known problem or is there something that I am missing? Are there any workarounds? Thanks in advance, -Achyut. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967645#3967645 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967645

19 years, 8 months

1
0
0 / 0

[Remoting] - Re: Newbie question: How to deploy

by NautilusIII

God, how stupid... Problem solved... I just executed the Server and the Client from within Eclipse referencin the usual jbossall-client.jar... Works perfectly... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967643#3967643 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967643

19 years, 8 months

1
0
0 / 0

[JBoss Seam] - Re: Class leakage on redeployment

by raja05

Yeah, it throws a OOME -- PermGen Space Filled errors after some 10 - 15 redeployments. I had a read at the Resin site that it could be due to Debuggers if any , and I use a fair amount of debugging with IDE, so I thought that could lead to this, but yeah I get this error too. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967642#3967642 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967642

19 years, 8 months

1
0
0 / 0

[Performance Tuning] - Re: No ManagedConnections available within configured blocki

by sauser

Hi, I am using Jboss 4.0.2 and encountering the same No ManagedConnections exception after the blocking timeout which I believe leads to Transaction Timeout and Transaction Rollback exception - Conn-pool configurations are Min-pool-Size = 10 Max-pool-Size = 80 Blocking timeout = 30000 ms stateless session bean configurations are as follows : Max Bean instance pool size = 80 There does not seem to be any connection leaks in the application. I have also tried adding strictMaximumSize in the session beans dd so as to restrict the concurrent beans accessing the connection pool but that does not solve the problem. The expected load on application is somewhere around 300 concurrent threads (atmost). Will altering of Basic Thread pool configurations help? Are there any other configurations which I might be missing or have misconfigured? Awaiting reply??? Regards, sauser View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967641#3967641 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967641

19 years, 8 months

1
0
0 / 0

[JBoss Seam] - Re: Best practise - Where to put authorization code

by ngolovin

You could use the Seam standard component "isUserInRole" to decide whether to render the elements on the pages. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967640#3967640 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967640

19 years, 8 months

1
0
0 / 0

[JBoss Seam] - Re: Any experiences with the Tomahawk components?

by ngolovin

If you have any success in using th AJAX components, please share the experience with us! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967639#3967639 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967639

19 years, 8 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 August 2006