[JBoss Remoting] - Native Netty based server / Embedded Tomcat
by Eugene Adams
Eugene Adams [http://community.jboss.org/people/hanhanter] created the discussion
"Native Netty based server / Embedded Tomcat"
To view the discussion, visit: http://community.jboss.org/message/549674#549674
--------------------------------------------------------------
Hi,
I have a custom server which relies heavily on threading(with Netty as IOLayer). Now this server has run as an independent server as a client of JBoss for a few years, but I am toying around with embedding this server inside JBoss, same as the native Tomcat service. What do I have to look out for and where do I start? I have deployed the service as a .sar, but it gives me exceptions like the following after I try to hit the JMX console :
2010-06-25 09:35:09,401 ERROR org.apache.coyote.http11.Http11AprProtocol org.apache.coyote.http11.Http11AprProtocol (http-jmx.my.server.domain%2F192.168.1.100-8080-1) Error reading request, ignoredjava.lang.ExceptionInInitializerError at java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:288) at org.apache.coyote.http11.InternalAprInputBuffer.(DirectByteBuffer.java:33) ... 7 more
The error is on Bits.java:592 :
static boolean unaligned() {
if (unalignedKnown)
return unaligned;
PrivilegedAction pa
= new sun.security.action.GetPropertyAction("os.arch");
String arch = (String)AccessController.doPrivileged(pa);
unaligned = arch.equals("i386") || arch.equals("x86") || arch.equals("amd64"); <<<<<<<<<<<<<<<<
unalignedKnown = true;
return unaligned;
}
How do I configure my service in jboss as a native embedded application and ... why is it giving this error?
Thanks!
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/549674#549674]
Start a new discussion in JBoss Remoting at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 10 months
[Datasource Configuration] - Encrypting Datasource Password
by Knut Klünker
Knut Klünker [http://community.jboss.org/people/schlumpf] created the discussion
"Encrypting Datasource Password"
To view the discussion, visit: http://community.jboss.org/message/549647#549647
--------------------------------------------------------------
Hi all,
I encrypted the datasource password with the SecureIdentityLoginModule in a JBoss 5.1.GA. Everything works fine but it doesn't work with one datasource. I checked everything in the configuration and also the generated password. But it was ok.
The datasource are all Oracle 10g datasources.
In the log there is the following error:
2010-06-24 15:46:54,577 xxxxxxxx INFO [VerboseError is false
2010-06-24 15:46:55,755 xxxxx ERROR [org.jboss.resource.security.AbstractPasswordCrede
ntialLoginModule] xxxxxx: The ConnectionManager mbean: *jboss.jca:name=xxxxxx,service=XATxCM specified in a ConfiguredIdentityLoginModule could not be found. ConnectionFactory will be unusable!*
javax.management.InstanceNotFoundException: *jboss.jca:name=xxxxx,service=XATxCM* is not registered.
at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:526)
at org.jboss.mx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:559)
at org.jboss.resource.security.AbstractPasswordCredentialLoginModule.getMcf(AbstractPasswordCredentialLoginModule.java
:118)
at org.jboss.resource.security.AbstractPasswordCredentialLoginModule.initialize(AbstractPasswordCredentialLoginModule.
java:88)
at org.jboss.resource.security.SecureIdentityLoginModule.initialize(SecureIdentityLoginModule.java:80)
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 javax.security.auth.login.LoginContext.invoke(LoginContext.java:756)
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
at org.jboss.security.plugins.auth.JaasSecurityManagerBase.defaultLogin(JaasSecurityManagerBase.java:552)
at org.jboss.security.plugins.auth.JaasSecurityManagerBase.authenticate(JaasSecurityManagerBase.java:486)
at org.jboss.security.plugins.auth.JaasSecurityManagerBase.isValid(JaasSecurityManagerBase.java:365)
at org.jboss.security.plugins.JaasSecurityManager.isValid(JaasSecurityManager.java:160)
at org.jboss.security.integration.JBossSecuritySubjectFactory.createSubject(JBossSecuritySubjectFactory.java:90)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.getSubject(BaseConnectionManager2.java:687)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:495)
at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectio
nManager2.java:941)
at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:89)
The datasource was bound:
2010-06-24 15:44:22,391 main INFO [org.jboss.resource.connectionmanager.ConnectionFactoryBindingService] --: Bound Connection
Manager 'jboss.jca:service=DataSourceBinding,name=xxxx' to JNDI name 'java:xxxx'
And the in jmx-console under jca you can find the datasource under the name.
In the login-config.xml is the following policy entry:
...
<application-policy name="NAMExxxx">
<authentication>
<login-module code="org.jboss.resource.security.SecureIdentityLoginModule" flag="required">
<module-option name="username">xxxx</module-option>
<module-option name="password">xxxxxx</module-option>
<module-option name="managedConnectionFactoryName">jboss.jca:name=xxxx,service=XATxCM</module-option>
</login-module>
</authentication>
</application-policy>
....
Username and password are correct.
I changed the password for testing, so that is was wrong, but the ERROR messages are the same.
Can somebody help me?
Best regards
Knut
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/549647#549647]
Start a new discussion in Datasource Configuration at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 10 months
Re: [jboss-user] [JBoss Web Services CXF] - ClassCastException: MyImpl cannot be cast to javax.servlet.Servlet
by Alessio Soldano
Alessio Soldano [http://community.jboss.org/people/alessio.soldano%40jboss.com] replied to the discussion
"ClassCastException: MyImpl cannot be cast to javax.servlet.Servlet"
To view the discussion, visit: http://community.jboss.org/message/549632#549632
--------------------------------------------------------------
> Chet Vora wrote:
>
> Alessio
>
> On the RHN site, 5 EAP is what seems to be the latest official version, as far as I could tell. Also, I couldn't locate the CXF bundled version. Again, its possible I'm looking in the wrong place. Do you happen to know where this bundled version is?
Honestly, I don't know exactly. Try asking for the EAP 5 CXF Tech preview to the support / your Red Hat product contact.
> I installed CXF by running the ant install from the binary distribution. I picked 500 as the choice of version.
Technically speaking, the version that would probably work is 510, as the number refers to the community AS versions. I said "probably", because -again- you're trying to install a community version on top of the product, which is not a supported procedure.
> I'll try out the few changes you suggested to see if I can get things to work.
Any news here?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/549632#549632]
Start a new discussion in JBoss Web Services CXF at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 10 months