[Installation, Configuration & DEPLOYMENT] - Scoped Deployment settings cuase LinkageError
by Martinator
Hi everyone, I'm trying to run multiple scoped single application ear deployments (using servlets) on a single JBoss 3.2.4 server so I can run different release levels at the same time.
Each app already has the class-loading loader-repository settings (excluding the java2ParentDelegation setting) in the jboss-app.xml file in the web-inf folder of the war file, but that does not make it work.
I then set the Isolated and CallByValue attribues to true in conf/jboss-service.xml and the Java2ClassLoadingCompliance and UseJBossWebLoader attributes to false in tomcat50.sar/meta-inf/jboss-service.xml. That seems to work fine after the first jboss restart.
The problem I'm getting is that after a new deployment is added or JBoss is restarted, the apps start up fine, but I get the followng error when I try to access the application URL:
"java.lang.LinkageError: loader constraints violated when linking javax/servlet/ServletOutputStream class) executing org.apache.jk.common.SocketConnection@3ba002, terminating thread"
Any ideas would be appreciated.
Thank you.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174438#4174438
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4174438
17 years, 10 months
[Remoting] - sun.security.validator.ValidatorException: No trusted certif
by vbatista
"vbatista" wrote : Hello,
| I am using JBoss-4.2.2.GA with Java 1.6.0_04. My application implements a WS client which needs to integrate with an external Web Service. This communication needs to be handled through https.
|
| I have created a jks keystore with the server certificate, and passed its details to JBoss through the System Properties:
|
|
| | -Djavax.net.ssl.trustStore=/Path-to-file -Djavax.net.ssl.trustStorePassword=password
| |
|
| On my development environment I can call the Web Service correctly.
| Although, on the production environment, I amgetting the following exception:
|
|
| | javax.xml.ws.WebServiceException: java.io.IOException: Could not transmit message
| | at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:317)
| | at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:255)
| | at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:164)
| | at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
| | at $Proxy171.send(Unknown Source)
| | at com.xpto.integration.SmsHelper.send(SmsHelper.java:57)
| | at com.xpto.services.sms.SMSSenderServiceMBean.run(SMSSenderServiceMBean.java:106)
| | at java.lang.Thread.run(Thread.java:619)
| | Caused by: java.io.IOException: Could not transmit message
| | at org.jboss.ws.core.client.RemotingConnectionImpl.invoke(RemotingConnectionImpl.java:204)
| | at org.jboss.ws.core.client.SOAPRemotingConnection.invoke(SOAPRemotingConnection.java:77)
| | at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:337)
| | at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:243)
| | ... 6 more
| | Caused by: org.jboss.remoting.CannotConnectException: Can not connect http client invoker.
| | at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:333)
| | at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:135)
| | at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
| | at org.jboss.remoting.Client.invoke(Client.java:1634)
| | at org.jboss.remoting.Client.invoke(Client.java:548)
| | at org.jboss.ws.core.client.RemotingConnectionImpl.invoke(RemotingConnectionImpl.java:183)
| | ... 9 more
| | Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: No trusted certificate found
| | at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174)
| | at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1591)
| | at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:187)
| | at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:181)
| | at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:975)
| | at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:123)
| | at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:516)
| | at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:454)
| | at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:884)
| | at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1096)
| | at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1123)
| | at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1107)
| | at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:405)
| | at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:166)
| | at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:832)
| | at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java:230)
| | at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:275)
| | ... 14 more
| | Caused by: sun.security.validator.ValidatorException: No trusted certificate found
| | at sun.security.validator.SimpleValidator.buildTrustedChain(SimpleValidator.java:304)
| | at sun.security.validator.SimpleValidator.engineValidate(SimpleValidator.java:107)
| | at sun.security.validator.Validator.validate(Validator.java:218)
| | at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:126)
| | at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:209)
| | at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:249)
| | at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:954)
| | ... 26 more
| |
|
| Both systems are configured with the same JBoss, JVM, ...
|
| The certificate details are:
|
|
| | Owner=
| | CN=*...., OU=..., O=..., L=..., ST=..., C=PT
| | Issuer=
| | CN=..., O=..., C=PT
| | Version=3
| | Serial Number=BC81A81843E26C2597CD10354588F61E
| | Valid From=Monday, 3 March 2008 18:50
| | Valid Until=Tuesday, 3 March 2009 18:50
| | Signature Algorithm=SHA1withRSA
| |
| | Fingerprints=
| | MD5: 0A:A6:89:92:A4:CF:17:74:7C:4E:20:63:6B:81:AE:85
| | SHA1: 35:01:74:8C:35:AB:9F:02:7B:23:3F:15:5E:73:C6:4D:DD:BB:C0:7A
| | Key Usage= critical
| | List:
| | . digitalSignature
| | . keyEncipherment
| | . dataEncipherment
| | . keyAgreement
| | Extended Key Usage= none
| |
|
| On production I have also tried adding the following properties:
|
|
| | -Djavax.net.ssl.keyStore=/Path-to-file -Djavax.net.ssl.keyStorePassword=password
| |
|
| But I still get the error.
|
| Any one has any hint for this problem? Is there any property which I can define to ignore untrusted certificates?
|
| Any help would really be welcome.
| Thanks in advance.
|
| Best regards,
| Victor Batista
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174437#4174437
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4174437
17 years, 10 months
[Remoting] - Caused by: sun.security.validator.ValidatorException: No tru
by vbatista
Hello,
I am using JBoss-4.2.2.GA with Java 1.6.0_04. My application implements a WS client which needs to integrate with an external Web Service. This communication needs to be handled through https.
I have created a jks keystore with the server certificate, and passed its details to JBoss through the System Properties:
| -Djavax.net.ssl.trustStore=/Path-to-file -Djavax.net.ssl.trustStorePassword=password
|
On my development environment I can call the Web Service correctly.
Although, on the production environment, I amgetting the following exception:
| javax.xml.ws.WebServiceException: java.io.IOException: Could not transmit message
| at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:317)
| at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:255)
| at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:164)
| at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
| at $Proxy171.send(Unknown Source)
| at com.xpto.integration.SmsHelper.send(SmsHelper.java:57)
| at com.xpto.services.sms.SMSSenderServiceMBean.run(SMSSenderServiceMBean.java:106)
| at java.lang.Thread.run(Thread.java:619)
| Caused by: java.io.IOException: Could not transmit message
| at org.jboss.ws.core.client.RemotingConnectionImpl.invoke(RemotingConnectionImpl.java:204)
| at org.jboss.ws.core.client.SOAPRemotingConnection.invoke(SOAPRemotingConnection.java:77)
| at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:337)
| at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:243)
| ... 6 more
| Caused by: org.jboss.remoting.CannotConnectException: Can not connect http client invoker.
| at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:333)
| at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:135)
| at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
| at org.jboss.remoting.Client.invoke(Client.java:1634)
| at org.jboss.remoting.Client.invoke(Client.java:548)
| at org.jboss.ws.core.client.RemotingConnectionImpl.invoke(RemotingConnectionImpl.java:183)
| ... 9 more
| Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: No trusted certificate found
| at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174)
| at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1591)
| at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:187)
| at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:181)
| at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:975)
| at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:123)
| at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:516)
| at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:454)
| at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:884)
| at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1096)
| at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1123)
| at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1107)
| at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:405)
| at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:166)
| at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:832)
| at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java:230)
| at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:275)
| ... 14 more
| Caused by: sun.security.validator.ValidatorException: No trusted certificate found
| at sun.security.validator.SimpleValidator.buildTrustedChain(SimpleValidator.java:304)
| at sun.security.validator.SimpleValidator.engineValidate(SimpleValidator.java:107)
| at sun.security.validator.Validator.validate(Validator.java:218)
| at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:126)
| at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:209)
| at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:249)
| at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:954)
| ... 26 more
|
Both systems are configured with the same JBoss, JVM, ...
The certificate details are:
| Owner=
| CN=*...., OU=..., O=..., L=..., ST=..., C=PT
| Issuer=
| CN=..., O=..., C=PT
| Version=3
| Serial Number=BC81A81843E26C2597CD10354588F61E
| Valid From=Monday, 3 March 2008 18:50
| Valid Until=Tuesday, 3 March 2009 18:50
| Signature Algorithm=SHA1withRSA
|
| Fingerprints=
| MD5: 0A:A6:89:92:A4:CF:17:74:7C:4E:20:63:6B:81:AE:85
| SHA1: 35:01:74:8C:35:AB:9F:02:7B:23:3F:15:5E:73:C6:4D:DD:BB:C0:7A
| Key Usage= critical
| List:
| . digitalSignature
| . keyEncipherment
| . dataEncipherment
| . keyAgreement
| Extended Key Usage= none
|
On production I have also tried adding the following properties:
| -Djavax.net.ssl.keyStore=/Path-to-file -Djavax.net.ssl.keyStorePassword=password
|
But I still get the error.
Any one has any hint for this problem? Is there any property which I can define to ignore untrusted certificates?
Any help would really be welcome.
Thanks in advance.
Best regards,
Victor Batista
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174436#4174436
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4174436
17 years, 10 months
[EJB 3.0] - Exception initializing interceptors (EJB3InterceptorsFactory
by pdeshmuk
We are currently running JBoss 4.2.2 and using EJB 2.0 with BMP. We are also in the process of introducing EJB 3.0 and would like to package EJB 2.0 and EJB 3.0 in the same JAR. I set the version attribute of our existing ejb-jar.xml to 3.0:
<ejb-jar version="3.0"
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
| xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee/ejb-jar_3_0.xsd">
Some of my existing EJB 2.0 beans now fail to deploy. Here is the exception message:
16:40:27,430 WARN [ServiceController] Problem creating service jboss.j2ee:ear=EMS.ear,jar=Server.jar,name=TrainingWebService,service=EJB3
| java.lang.RuntimeException: An exception occurred initialising interceptors for class com.creativesolutions.ems.webservice.training.TrainingWebServiceBean.getTrainingEnrollmentWSOs
| at org.jboss.ejb3.interceptor.EJB3InterceptorsFactory.createPerJoinpoint(EJB3InterceptorsFactory.java:108)
| at org.jboss.aop.advice.AspectFactoryDelegator.createPerJoinpoint(AspectFactoryDelegator.java:119)
| at org.jboss.aop.advice.ScopedInterceptorFactory.create(ScopedInterceptorFactory.java:113)
| at org.jboss.aop.Advisor.createInterceptorChain(Advisor.java:618)
| at org.jboss.aop.Advisor.pointcutResolved(Advisor.java:888)
| at org.jboss.aop.Advisor.resolveMethodPointcut(Advisor.java:650)
| at org.jboss.ejb3.interceptor.InterceptorInfoRepository.getBeanClassAroundInvokes(InterceptorInfoRepository.java:136)
| at org.jboss.ejb3.interceptor.EJB3InterceptorsFactory.createPerJoinpoint(EJB3InterceptorsFactory.java:101)
| ... 102 more
Here is the code of the failing EJB method:
public TrainingEnrollmentWSO[] getTrainingEnrollmentWSOs(int trainingClassID, boolean showConfirmedOnly, String clauseType) {
| try {
| return new TrainingEnrollmentDAO().getTrainingEnrollmentWSOs(trainingClassID, showConfirmedOnly, clauseType);
| }
| catch(Exception e) {
| ErrorLogger.error(this,e.getMessage(),e);
| return null;
| }
| }
If required, I will be happy to give more information regarding my setup and will appreciate any thoughts that can resolve this issue.
thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174429#4174429
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4174429
17 years, 10 months
[Persistence, JBoss/CMP, Hibernate, Database] - Re: jboss-4.2.3.GA with MySQL Server 5.0 configuration probl
by dan jboss
"PeterJ" wrote : Both hajndi-jms-ds.xml and jms-ds.xml should not have ended up in the deploy directory. There should be only one of them, depending on if you are clustering or not. Because of the install command line you gave:
|
| ant -f release-admin.xml -Dmessaging.config.source=all -Dmessaging.config.name=jms
|
| the hajndi-jms-ds.xml is the correct file and jms-ds.xml is incorrect (and should be removed).
|
| The 'all' configuration includes clustering support. The 'default' configuration contains everything except clustering. You did not by any chance run release-admin.xml twice, once without any options? That would explain the duplication.
|
Yes I have run release-admin.xml multiple times and generated different configurations as I was trying to start over after suspecting a mess in the current one. Initially I ran it without parameters, then as the old configuration was in the way I started running it with parameters on the same installation of JBoss. You explanation is totally consistent.
Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174428#4174428
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4174428
17 years, 10 months
[EJB/JBoss] - JBoss 4.2.2 not reading standardjboss.xml
by shreyasshinde
I have a JBoss 4.2.2 install on Redhat Linux (RHEL4). I am seeing that the configuration properties (specifically the container-configuration like MaximumSize, strictMaximumSize) are not getting enforced. So basically, I am not able to configure my Stateless Session Bean Container to create upto a certain number of beans.
There was another user who was stumbling across the same issue but she had not got any response.
After going through the JBoss EJB container source, I see that the class should through an exception if standardjboss.xml is not found. But I don't see that happening (even after deleting the file - I see no errors).
Is there anything I am missing? I need to set the container pool size across the board for a specific type of container. I cannot use jboss.xml on a per application basis.
Config: all
Version: 4.2.2
Platform: Linux
Thanks,
Shreyas
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174426#4174426
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4174426
17 years, 10 months