[Installation, Configuration & DEPLOYMENT] - Re: Doubts about deployment on the server
by Marcos_APS
"PeterJ" wrote : You can continue to use port 8080.
I've just followed your instruction and I still don't have success. Below are some configuration that I'm using. Maybe I'm doing something wrong:
jboss-web.xml
<jboss-web>
| <context-root>/laboratorioinformatica</context-root>
| <virtual-host>labinf</virtual-host>
| </jboss-web>
{JBOSS_HOME}\server\default\deploy\jboss-web.deployer\server.xml
<Server>
| <Service name="jboss.web">
| <Connector port="8080" address="${jboss.bind.address}"
| maxThreads="250" maxHttpHeaderSize="8192"
| emptySessionPath="true" protocol="HTTP/1.1"
| enableLookups="false" redirectPort="8443" acceptCount="100"
| connectionTimeout="20000" disableUploadTimeout="true" />
|
| <Engine name="jboss.web" defaultHost="localhost">
|
| <Host name="labinf"
| autoDeploy="false" deployOnStartup="false" deployXML="false"
| configClass="org.jboss.web.tomcat.security.config.JBossContextConfig"
| >
|
| <Alias>mydomain.com</Alias>
| <Valve className="org.jboss.web.tomcat.service.jca.CachedConnectionValve"
| cachedConnectionManagerObjectName="jboss.jca:service=CachedConnectionManager"
| transactionManagerObjectName="jboss:service=TransactionManager" />
|
| </Host>
|
| </Engine>
|
| </Service>
|
| </Server>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145963#4145963
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4145963
18 years
[JBoss Portal] - MembershipModule getUsers bug?
by rcarmichael
I believe that there is a bug in the getUsers function of MembershipModule. If you have a portlet (like below) using the getUsers function, then go to the admin portlet and assign a user to a role (in this example, 'testrole'), this portlet will continue to return a list of size 0 until you restart jboss. Once you restart jboss, the user you just assigned to the role will be in the list. However, if you remove that user from the list, this function will continue to return that user until (again) you restart jboss. This is using JBoss Portal 2.6.4.
Has anyone had this problem or am I doing something fundamentally wrong? If not, I will file it on JIRA.
| @Override
| protected void doView(RenderRequest request, RenderResponse response)
| throws PortletException, PortletSecurityException, IOException {
| response.setContentType("text/html");
| response.getWriter().println("Testing membershipmodule");
|
| try {
| InitialContext ic = new InitialContext();
| TransactionManager tm = (TransactionManager)ic.lookup("java:/TransactionManager");
| MembershipModule mm = (MembershipModule)ic.lookup("java:portal/MembershipModule");
| RoleModule roleMod = (RoleModule)ic.lookup("java:portal/RoleModule");
|
| tm.begin();
|
| Set<User> users = mm.getUsers(roleMod.findRoleByName("testrole"));
|
| for (User user : users) {
| System.out.println("user=" + user.getUserName());
| }
|
| tm.commit();
| } catch (Exception ex) {
| ex.printStackTrace();
| }
| }
|
- Ryan
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145958#4145958
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4145958
18 years
[JBoss Messaging] - Problem with Using Jboss Messaging
by paradisonoir
Hi,
I am using my Jboss Application Serer (Version: 4.2.2.GA) to run my JMS application. As long as I am using "jnp://localhost:1099", it works, but when I change localhost to the IP address ("jnp://132.205.93.311:1099") of the same machine, it gives me the following error. I also changed the jndi.properties like this:
Hashtable props = new Hashtable();
|
| props.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
| props.put(Context.PROVIDER_URL, "jnp://132.205.93.311:1099");
| props.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces");
Error :
javax.naming.CommunicationException: Could not obtain connection to any of these urls: 132.205.93.31:1099 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timedout] [Root exception is javax.naming.CommunicationException: Failed to connect to server 132.205.93.31:1099 [Root exception is javax.naming.ServiceUnavailableEx
ception: Failed to connect to server 132.205.93.31:1099 [Root exception is java.net.ConnectException: Connection refused: connect]]]
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145957#4145957
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4145957
18 years
[JBoss Messaging] - Re: OutOfMemoryError with JBoss Messaging
by harish43
The test is processing xml documents.
There is a servlet that is being fed one or more XML documents in every request. The servlet then creates a JMS message containing the document(s) and puts it on a queue. The MDB(s) listening on this queue is the controller. It sends a message corresponding to each step in the process to a different queue and there are MDBs that consume from each of the different queues. When the MDBs in each step is done with the message they send a message back to the control queue.
The documents are normally 1K in size but occasionally can be larger or smaller than that.
The first MDB is called the Dispatcher. It only is used if the request contained more than one document. It splits the request data into multiple documents and sends a message to the controller for each document.
The second MDB is called the Master Processor. This is where each XML document is validated, compressed and persisted in the Sybase database. It sends a message to the controller after it is done.
The third MDB is the Access Processor. This is where the XML document is converted to ASN.1 format and persisted in the Sybase database.
All the queues are persistent.
I tried setting the FullSize to 100 and the PageSize and DownCacheSize to 20 and the behavior is still the same.
I keep getting a lot of errors as below and I am not sure why they are occuring and whether they have anything to do with the memory issue.
ERROR [org.jboss.jms.client.container.ClosedInterceptor]
ClosedInterceptor.ClientSessionDelegate[jr-i9awncff-1-q3osncff-g5axfp-2b2r6q3]: method createMapMessage() did not go through, the interceptor is CLOSED
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145956#4145956
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4145956
18 years
[JBoss Portal] - SynchronizingLoginModule synchronize always
by ameo
Hello,
the reference guide says that the SynchronizingLoginModule try to synchronize authenticated user into portal store using portal identity modules. I follow from this sentence, that it will only synchronize authenticated users. But i made other experience.
When my custom LoginModule delivers false, the synchronization occurs however. If the custom LoginModule delivers false, then I want that the authentication fails. But on my example, the authentication takes place and a user is created by the Sync-Module and the portal shows the pages and portlets.
I have a custom login module like this one..
|
| public class CustomIdentityModule extends UsernamePasswordLoginModule {
| ..
| public boolean login() throws LoginException {
| super.loginOk = true/false;
| return true/false;
|
| }
| protected Group[] getRoleSets() throws LoginException {}
| ...
| }
|
the login-config.xml
|
| <login-module code = "org.login.CustomIdentityModule" flag="requisite"
| <module-option name="dsJndiName">java:/CSDS</module-option>
| <module-option name="principalsQuery">SELECT PASSWD FROM USERS WHERE USERNAME=?</module-option>
| <module-option name="rolesQuery">SELECT userroles, 'Roles' FROM userroles where username =?</module-option>
| <!--
| <module-option name="hashAlgorithm">MD5</module-option>
| <module-option name="hashEncoding">HEX</module-option>
| -->
| <module-option name="additionalRole">Authenticated</module-option>
| </login-module>
|
|
| <login-module code="org.jboss.portal.identity.auth.SynchronizingLoginModule" flag="optional">
| <module-option name="synchronizeIdentity">true</module-option>
| <module-option name="synchronizeRoles">true</module-option>
| <module-option name="preserveRoles">true</module-option>
| <module-option name="additionalRole">Authenticated</module-option>
| <module-option name="defaultAssignedRole">User</module-option>
| <module-option name="userModuleJNDIName">java:/portal/UserModule</module-option>
| <module-option name="roleModuleJNDIName">java:/portal/RoleModule</module-option>
| <module-option name="membershipModuleJNDIName">java:/portal/MembershipModule</module-option>
| <module-option name="userProfileModuleJNDIName">java:/portal/UserProfileModule</module-option>
| </login-module>
|
|
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145953#4145953
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4145953
18 years