Re: [jboss-user] [Beginner's Corner] - where can I find sun java ee deployment tool ?
by Peter Johnson
Peter Johnson [http://community.jboss.org/people/peterj] replied to the discussion
"where can I find sun java ee deployment tool ?"
To view the discussion, visit: http://community.jboss.org/message/542144#542144
--------------------------------------------------------------
If you are using Eclipose, I recommend that you install the JBoss Tools plugin and read through the JBoss Tools documentation - they contain many tutorials on using Toolks to develop and deploy applications.
Personally, I recommend that you do not use any IDEs, tools or wizards and instead use only a text editor (using Eclipse as a text editor is fine) to edit all files, inlcuding source files and configuration files. Then use command line tools (javac, jar, etc.) to build, package and deploy your apps. I guess that it would be alright to use Ant or Maven to do some of that for you, provided you understand exactly what they are doing. Only after that would I say that you are ready to do Java EE development with Eclipse. I say this because at this point is appears that you are fighting with Eclipse rather than accomplishing your goal of developing Java EE apps.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/542144#542144]
Start a new discussion in Beginner's Corner at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 11 months
[JBoss Portal] - Appserver Queues Filling Up
by Ben Knight
Ben Knight [http://community.jboss.org/people/rem2500] created the discussion
"Appserver Queues Filling Up"
To view the discussion, visit: http://community.jboss.org/message/542132#542132
--------------------------------------------------------------
Apache version: 2.2.3
JBoss version: 5
JBoss Web: http://2.1.3.ga/ 2.1.3.GA
mod_jk: 1.2.30
Dear community,
We are having a Wicket-based Java application deployed in a production server cluster using Apache (2.2.3) with mod_jk (1.2.30) as load balancing component w/ sticky session and Jboss 5 as application container for the Java application.
We are inconsistently seeing an issue in our production environment where our AJP queues between Apache and Jboss as shown in the JMX console fill up with requests to the point where the application server is no longer taking on any new requests. When looking at all involved system components (overall traffic, load db, process list db, load of all clustered application server nodes) nothing points towards a capacity issue which would explain why the calls are being stalled in the AJP queue. Instead all systems appear sufficiently idle.
So far, our only remedy to this issue is to restart the appservers and the load balancer which only occasionally clears the AJP queues.
We are trying to figure out why the queues are filling up to the point that no calls get returned to the end user although the system is not under a high load.
Has anyone else experienced similar problems?
Are there any other system metrics we should monitor that could explain the queuing behavior?
Is this potentially a mod_jk issue? If so, is it advisable to swap mod_jk with mod_cluster to resolve the issue?
Any advice is highly appreciated. If I can provide additional information for the sake of troubleshooting I would be more than willing to do so.
/Ben
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/542132#542132]
Start a new discussion in JBoss Portal at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 11 months
[JBoss Web Services] - XML Content handler only supports a StreamSource content object
by Eugene McKissick
Eugene McKissick [http://community.jboss.org/people/elm3d] created the discussion
"XML Content handler only supports a StreamSource content object"
To view the discussion, visit: http://community.jboss.org/message/542127#542127
--------------------------------------------------------------
All,
I recently converted an existing web service from CXF to JBossWS Native. The service is up and running, however whenever I try to call the web service I get the following error:
[RequestHandlerImpl] Error processing web service request
org.jboss.ws.WSException: java.io.IOException: XML Content handler only supports a StreamSource content object
....
Caused by: java.io.IOException: XML Content handler only supports a StreamSource content object
at org.jboss.ws.core.soap.attachment.XmlDataContentHandler.writeTo(XmlDataContentHandler.java:101)
at javax.activation.ObjectDataContentHandler.writeTo(DataHandler.java:883)
at javax.mail.internet.MimeBodyPart.writeTo(MimeBodyPart.java:1350)
at javax.mail.internet.MimeBodyPart.writeTo(MimeBodyPart.java:845)
at javax.mail.internet.MimeMultipart.wrtieTo(MimeMultipart.java:361)
at org.jboss.ws.core.soap.attachment.MultipartRelatedEncoder.writeTo(MultipartRelatedEncoder.java:123)
at org.jboss.ws.core.soap.SOAPMessageImpl.writeTo(SOAPMessageImpl.java:343)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.sendResponse(RequestHandlerImpl.java:401)
...24 more
We are currently using JBoss 5.1 with JDK 6.
The method in the web service impl. that triggers this error is
public void getXmlDocs(DocParams params, Holder<ReturnType> outDocument, Holder<String> xmlAttach)
{
List<String> docIDs = params.getDocID().getItem();
for (String s: docIDs) {
System.out.println(s);
}
ReturnType retType = new ReturnType();
retType = this.populateReturnType();
outDocument.value = retType;
xmlAttach.value = <Read xml from text file>;
System.out.println(xmlAttach.value); //Prints out contents of file as string correctly
}
Everything seems fine in the method, but when JBoss tries to create the response the error occurs. Turning on debug I see the ReturnType object being serialized by the JAXBSerializer. The [ObjectContent] xmlFragment statement contains xml for the ReturnType wrapped in the getDocResponse header. Before END handleRequest is logged.
Associated WSDL chunk
<!-- *************************** Type Definitions ******************************* -->
<types>
<complexType name="ReturnType">
<sequence>
<element name="returnInfo" type="xsd:String">
<element name="returnStatus" type="xsd:String">
</sequence>
</complexType>
<complexType name="getDocResponse" type="tns:ReturnType" />
<!--***************************Message Definitions******************************** -->
<message name="getDocResponse">
<part name="outDocument" element="tns:getDocResponse"/>
part name="xmlAttach" type="xsd:string"/>
</message>
<!--***************************Binding Definitions******************************** --
<output name="getDocResponse">
<mime:multipartRelated>
<mime:part>
<soap:body parts="outDocument" use="literal" />
</mime:part>
<mime:part>
<mime:content part="xmlAttach" type="text/xml"/>
</mime:part>
</mime:multipartRelated>
</output>
I apologize for the limited information...the errors and code reside on the server, so I had to retype the code (hence the pseudocode). Any help or suggestions would be greatly appreciated.
Regards,
Eugene
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/542127#542127]
Start a new discussion in JBoss Web Services at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 11 months
Re: [jboss-user] [JBoss Microcontainer Development] - ClassPool bootstrap refactoring
by Kabir Khan
Kabir Khan [http://community.jboss.org/people/kabir.khan%40jboss.com] replied to the discussion
"ClassPool bootstrap refactoring"
To view the discussion, visit: http://community.jboss.org/message/542120#542120
--------------------------------------------------------------
I ran the tests. In AS 4 it is fine apart from
>
> $more output/reports/TEST-org.jboss.test.aop.test.ScopedAttachUnitTestCase.txt
>
> Testsuite: org.jboss.test.aop.test.ScopedAttachUnitTestCase
>
> Tests run: 6, Failures: 0, Errors: 1, Time elapsed: 2.041 sec
>
>
>
> Testcase: testPOJOAdvised1 took 0.276 sec
>
> Testcase: testPOJOAdvised2 took 0.115 sec
>
> Testcase: testExpectedValues1 took 0.088 sec
>
> Testcase: testExpectedValues2 took 0.073 sec
>
> Testcase: testScoped1 took 0.324 sec
>
> Testcase: testScoped2 took 0.275 sec
>
> Caused an ERROR
>
> null
>
> javax.management.RuntimeMBeanException
>
> at org.jboss.mx.interceptor.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.java:176)
>
> at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:163)
>
> 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.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:266)
>
> 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.jmx.connector.invoker.SerializableInterceptor.invoke(SerializableInterceptor.java:74)
>
> 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.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179)
>
> 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.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:818)
>
> at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:419)
>
> at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305)
>
> at sun.rmi.transport.Transport$1.run(Transport.java:159)
>
> at java.security.AccessController.doPrivileged(Native Method)
>
> at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
>
> at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
>
> at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
>
> at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
>
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>
> at java.lang.Thread.run(Thread.java:637)
>
> Caused by: java.lang.RuntimeException: Error generating joinpoint class for joinpoint Constructor[constructor=public org.jboss.test.aop.scopedattach.POJO()]
>
> at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:310)
>
> at org.jboss.aop.instrument.JoinPointGenerator.access$300(JoinPointGenerator.java:77)
>
> at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$2.generateJoinPointClass(JoinPointGenerator.java:1730)
>
> at org.jboss.aop.instrument.JoinPointGenerator.generateJoinPointClass(JoinPointGenerator.java:250)
>
> at org.jboss.aop.GeneratedClassAdvisor.generateJoinPointClass(GeneratedClassAdvisor.java:1059)
>
> at org.jboss.test.aop.scopedattach.POJO$POJOAdvisor.POJOAdvisor_new_$aop(POJO$POJOAdvisor.java)
>
> at org.jboss.test.aop.scopedattach.POJO.POJO_new_$aop(POJO.java)
>
> at org.jboss.test.aop.scopedattach.ScopedTester.testScoped(ScopedTester.java:113)
>
> at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
>
> ... 44 more
>
> Caused by: javassist.CannotCompileException: Error compiling. Code
>
> {super($);isForInstanceAdvisor=($1.getAdvisor() instanceof org.jboss.aop.InstanceAdvisor);around2 = getAround2();around3 = getAround3();around4 = getAround4();around5 = getAround5();around6 = getAround6();}
>
> at org.jboss.aop.instrument.JoinPointGenerator.createPublicConstructor(JoinPointGenerator.java:1120)
>
> at org.jboss.aop.instrument.JoinPointGenerator.createConstructors(JoinPointGenerator.java:1019)
>
> at org.jboss.aop.instrument.JoinPointGenerator.generateJoinpointClass(JoinPointGenerator.java:370)
>
> at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:285)
>
> ... 56 more
>
> Caused by: javassist.CannotCompileException: [source error] no such a constructor
>
> at javassist.CtBehavior.setBody(CtBehavior.java:409)
>
> at javassist.CtBehavior.setBody(CtBehavior.java:375)
>
> at javassist.CtConstructor.setBody(CtConstructor.java:216)
>
> at javassist.CtNewConstructor.make(CtNewConstructor.java:102)
>
> at org.jboss.aop.instrument.JoinPointGenerator.createPublicConstructor(JoinPointGenerator.java:1113)
>
> ... 59 more
>
> Caused by: compile error: no such a constructor
>
> at javassist.compiler.MemberCodeGen.atMethodCallCore2(MemberCodeGen.java:593)
>
> at javassist.compiler.MemberCodeGen.atMethodCallCore(MemberCodeGen.java:575)
>
> at javassist.compiler.MemberCodeGen.atCallExpr(MemberCodeGen.java:523)
>
> at javassist.compiler.JvstCodeGen.atCallExpr(JvstCodeGen.java:243)
>
> at javassist.compiler.ast.CallExpr.accept(CallExpr.java:45)
>
> at javassist.compiler.CodeGen.atStmnt(CodeGen.java:337)
>
> at javassist.compiler.ast.Stmnt.accept(Stmnt.java:49)
>
> at javassist.compiler.CodeGen.atStmnt(CodeGen.java:350)
>
> at javassist.compiler.ast.Stmnt.accept(Stmnt.java:49)
>
> at javassist.compiler.CodeGen.atMethodBody(CodeGen.java:291)
>
> at javassist.compiler.Javac.compileBody(Javac.java:222)
>
> at javassist.CtBehavior.setBody(CtBehavior.java:401)
>
> ... 63 more
>
>
>
>
In AS 5 all tests are fine apart from
> $more output/reports/TEST-org.jboss.test.aop.test.RemotingUnitTestCase.txt
> Testsuite: org.jboss.test.aop.test.RemotingUnitTestCase
> Tests run: 4, Failures: 0, Errors: 4, Time elapsed: 6.848 sec
>
> Testcase: testRemoting took 0.227 sec
> Caused an ERROR
> org/jboss/classpool/spi/ClassPoolRepositoryCallback
> java.lang.NoClassDefFoundError: org/jboss/classpool/spi/ClassPoolRepositoryCallback
> at org.jboss.aop.AspectManager.initManager(AspectManager.java:267)
> at org.jboss.aop.AspectManager.instance(AspectManager.java:246)
> at org.jboss.aop.AspectManager.instance(AspectManager.java:235)
> at org.jboss.aop.proxy.ClassProxyFactory.getProxyClass(ClassProxyFactory.java:111)
> at org.jboss.aop.proxy.ClassProxyFactory.newInstance(ClassProxyFactory.java:152)
> at org.jboss.aop.proxy.ClassProxyFactory.newInstance(ClassProxyFactory.java:146)
> at org.jboss.aop.proxy.MarshalledClassProxy.readResolve(MarshalledClassProxy.java:58)
> at java.io.ObjectStreamClass.invokeReadResolve(ObjectStreamClass.java:1061)
> at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1762)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
> at java.rmi.MarshalledObject.get(MarshalledObject.java:142)
> at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:134)
> at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
> at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
> at org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
> at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
> at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
> at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
> at $Proxy0.invoke(Unknown Source)
> at org.jboss.test.aop.test.RemotingUnitTestCase.testRemoting(RemotingUnitTestCase.java:62)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> at junit.extensions.TestSetup.run(TestSetup.java:25)
> Caused by: java.lang.ClassNotFoundException: org.jboss.classpool.spi.ClassPoolRepositoryCallback
> at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:315)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:330)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:250)
> at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:398)
>
The same error occurs for the other tests in RemotingUnitTestCase as well. ClassPoolRegistryCallback has been there since Alpha1, so I guess it is a classloader issue. I think remember Flavia mentioning something once, but not exactly what?
I'll try to dig in to the errors tomorrow, although I am not sure how much time I will spend on this since we are only really targeting AS 6 with the current AOP releases, supporting previous AS versions is just us "being nice".
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/542120#542120]
Start a new discussion in JBoss Microcontainer Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 11 months